Many of my management clients tell me, “time is money.” That is only partially correct. Once you decide to invest a dollar, that dollar has the same value as any other dollar. Instead of focusing on the expense of a dollar, look for the value that dollar can return. (Because no one ever knows how […]
This is Johanna Rothman’s March 2026 Pragmatic Manager newsletter. The unsubscribe link is at the bottom of this email. Most of us have heard of—or suffered through—schedule delays. That’s when the project or program feels tremendous pressure to deliver some specific value by a specific date. To achieve those dates, we often heard lies such
Do you use schedule or tracking tools to predict the future? None of them can predict the future. Worse, too many of them hide the past, especially the recent past. A schedule or tracking tool can only predict one thing: the first possible date you cannot prove you cannot finish the project/story by. Let me
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
This is the March 2025 Pragmatic Manager Newsletter, from Johanna Rothman. The Unsubscribe link is at the bottom of this email. Susan, a product leader, has a big problem. One of the senior managers, Tim, often wants to know the cost (or time) required for a new feature or a new product. So he asks
I have never found Gantt charts to be useful. When I say that to my clients, some of them tell me they do find use in Gantt charts. Specifically, the people who like Gantt charts say they can predict where the project is headed. In addition, they can see the various interdependencies across the work.
In Effective Agility Requires Cultural Changes: Part 1, I said that real agile approaches require cultural change to focus on flow efficiency, where we focus on watching the work, not the people. Too few organizations can do that. But teams can change how they work—in any approach. Here are three suggestions to emulate flow efficiency
In How Centralization Decisions Create Friction, Increase Cycle Time, and Cost Money, Part 1, I discussed how removing support staff for departments and managers created longer cycle times. (And sometimes, increased friction so much that people could not easily do their jobs.) Removing those support staff was one indication the companies fell into the Economies
In the first post, How Centralization Decisions Create Friction, Increase Cycle Time, and Cost Money, Part 1, I explained how centralizing even relatively small decisions to centralize has high costs. Why do organizations centralize? To supposedly capitalize on “economies of scale.” That’s the problem of understanding the cost of work—but not the value of that
I started this series with the issues of trying to estimate/predict a specific backlog item quarters away, not even weeks away. (Even weeks away is iffy because the entropy is the default state for the world.) In Part 1, I suggested that the team can use cycle time, but even with cycle time, we need