I started this series bemoaning the fact that we have too few product managers. That leads to no product leaders for a team. Worse, some teams have either strategic product thinkers or tactical thinkers—but not both. Instead, we can consider several possible product value teams to prevent insufficient product leadership. I already discussed the Vertical
This is Johanna Rothman’s November 2025 Pragmatic Manager newsletter. The Unsubscribe link is at the bottom of this email. I’ve been working with Stephanie, a senior leader who’s trying to nudge her organization to more organizational agility. Not because agility is so “good,” but because they want to quickly launch new products and new versions
The whole point of product management is to increase the product capabilities over time. Those capabilities will expand the customer base by offering new value. More customers means more revenue. That’s why the product vision for this release is so critical. That product vision requires strategic product leadership. The backlog is the tactical implementation of
In my recent project charter series, I said we need a product vision to drive the project charter effort so the customers can get this container of value. Who creates that product vision? The product leader. However, too many supposedly agile teams lack an effective product leader. Here’s what I’ve seen: A part-time product manager
As far as I can tell, all organizations have the appetite for more work than they have people or time to do that work. It does not matter if the organization is one person or thousands. We all want to accomplish more than we have people. That’s why we need a product vision to drive
I started this series by saying a team can create a useful project charter in less time than you think. So what prevents teams from doing so? Too often, the project is not ready. The team might be ready, but the project is not. In effect, the project starts with scarcity. (I used to think
Does your team have a project charter so they know what to do for this project? I see too many teams try to start work without one. That leads to feature factories, apparently random work that does not add value, or worse, a product that’s partly done in too many areas. Teams start without project
I’ve been working with several supposedly “agile” teams and their managers. Everyone knows their project is in trouble. And they have no idea what to do about it. The team members say, “We’re on a death march. We have no predictability. Everything takes longer than we think it will.” The managers say, “We have no
This is Johanna Rothman’s August 2025 Pragmatic Manager newsletter. The Unsubscribe link is at the bottom of this email. Amy, a project manager, said, “With all the changes going on, no one is quite sure of their next steps. The portfolio team is stuck because they can’t predict for a year anymore. The product leader
This is Johanna Rothman’s July 2025 Pragmatic Manager newsletter. The Unsubscribe link is at the bottom of this email. Mike, a new senior leader, wants to know when Engineering will deliver specific projects. He would prefer more accurate estimates, but he’s okay with relative sizing, such as: Small projects: Not more than a quarter (12