Remove Agile Remove Feedback Loop Remove Information Remove Product Research
article thumbnail

Feedback Loops Help When to Centralize or Decentralize Product-Based Decisions

Johanna Rothman

When I think about agile approaches to work, I think about how fast we can change and the cost of those changes. That's why an agile approach with deliverables every day or week doesn't fit with some kinds of projects, such as events. See the lifecycle series for more information.). Some Centralization for the Product Roadmap.

article thumbnail

How Agile Managers Use Uncertainty to Create Better Decisions Faster

Johanna Rothman

Strategy and Product Feedback Loops Many of my middle-management and senior leadership clients want certainty about future work. Does that sound like an agile team to you? However, managers don't create features as agile teams do. Agile teams don't assume they make a final product the first time out.

Agile 95
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Jobs To Be Done in Product Design

UX Planet

5-step process The Jobs to Be Done (JTBD) is a powerful tool in product design that helps teams focus on understanding the needs and objectives of their customers rather than just the product itself. Here’s how to use the JTBD framework in product design: [link] 1. Why do they want to use your product? Who are they?

article thumbnail

Feature Rollout: What Is It and How to Conduct It? (+Best Practices)

Userpilot

Even if you’ve been a product manager for a while, a new feature rollout can be a challenging experience. We explain what a feature rollout is, why it is important for product teams, and how to conduct them. Thanks to that, the development team can collect user feedback and test the feature before rolling it out to all users.

article thumbnail

Tired of Fake Agility? Choose When to Experiment and When to Deliver

Johanna Rothman

I have a new book: Project Lifecycles: How to Reduce Risks, Release Successful Products, and Increase Agility. I wrote it because I'm concerned about what I see in too many supposedly agile teams: Crazy-long backlogs and roadmaps. See Manage Unplanned Feedback Loops to Reduce Risks and Create Successful Products.)

article thumbnail

What Lifecycle or Agile Approach Fits Your Context? Part 3, Incremental Lifecycles

Johanna Rothman

Teams can get some feedback from one feature set to inform the next set—but that's not a primary lever. Once the team completes that highest priority feature(s), the team can release the product. When we release, we can regroup and figure out what to do next for this product. Fork another product. (I

article thumbnail

Use Deliveries to Offer New Decision Points for Tactics and Strategy

Johanna Rothman

However, the more often we deliver in short feedback loops, the more often we can make strategic decisions. Finishing a story creates a new decision point, for both the product and the corporate strategy. The more often we iterate strategically, the more we exhibit business agility. Here's an example. You can change.