Most projects encounter problems at some point, regardless of the size of the team and the people’s capabilities. For example, in a six-person team, TeamA, Tom resigned to follow his wife to her new job. Dick became quite ill and went out on short-term disability for the next three months. And Harry needed significant time […]
Three Planning Ideas to Support Your Future Decisions Many organizations use deliverable-based planning, specifying the various features or products the teams expect to deliver and when. I’m a fan of short-term deliverable-based planning because it focuses everyone on the (few) deliverables. But the pandemic taught us a critical idea: while long-term deliverable-based planning can illuminate
If we want more ease and better results, we need to be able to change when the world changes. Yet, we don’t always notice these changes, so we don’t create options and experiment. Too often, we feel as if the world drags us down. We double-down on what we’ve been doing. Instead, we need to
I started this series by realizing managers have (too) many decisions to make. The longer it takes managers to make any single decision, the longer it might take to make all the decisions. That’s Little’s Law, applied to decisions. In Part 1, I recommended that managers start with their oldest possible decision and decide what
Many managers feel pressure to deliver finished work. They plan and replan—and ask the teams to plan and replan. They plan to be able to predict the future. But there are several problems with all this planning: These plans require prediction at all levels, from strategy to product to what the team delivers. That’s a
Your company is planning a layoff, and you’re one of the managers who has to decide and deliver the bad news. What do you say? What do you do? Almost everyone I know who has to do the laying-off feels terrible about that. But you can create a congruent environment and make it possible for
Most managers I see feel a ton of pressure for delivery. The managers need to “deliver” more projects, products, and features. That pressure rolls down to the teams. Too often, the team hears, “Can you just do a little more?” That often leads to the so-called “quiet quitting” problem. The problem isn’t quiet quitting. The
My clients all have too much work to do. So they ask the product or project leaders to write a business case for each effort. The clients claim this information helps them decide which work to do and not do. However, everyone knows each business case is at least partially fiction. That’s because the writer
Acme’s project portfolio team was stuck. Three months ago, they’d funded five experimental projects at $150k each. The portfolio team hoped those projects might offer the organization new customers and revenue streams. Now, the project teams reported several concerns: The technology was more complex than anyone had expected. Instead of the teams’ typical 2-4 days
We often think that finishing a story from the backlog is “just” tactical. 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