This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Management & Leadership

The Improvement Flywheel

Improvement flywheel system diagram

A few weeks ago on Twitter, John Cutler posted what he called "the wicked loop" of product development problems.

A team doesn’t execute well, which leads to pressures to deliver things faster. Those pressures come from both inside and outside the team.

In an attempt to deliver value and relieve this pressure, the team becomes reactionary to requests, trying to do more at once, and starts paying more attention to their output than what outcomes they want. They see small holes in their schedule and try and fill those with extra work.

The result is high work in progress, with everyone doing something slightly different. What used to be seen as teamwork starts becoming an interruption, and everyone spends half the day is doing things that aren’t known to the rest of the team. And because everything is depending on everything else, shipping gets harder and batch sizes increase.

The list of missed promises grows, less gets delivered, and because the team isn’t executing well, pressures increase.

Wicked Loop diagram

This feedback loop drives the team to become worse, not better.

But what John calls a Wicked Loop is also an incredible flywheel for improvement. Set it in motion and things will get better faster than you can imagine. The same things that cause a cascade of poor performance can also cause a cascade of improvements in the other direction.

Pick some quick wins and ship those fast. This starts gaining trust within the team and outside it that the team is capable of building quickly.

Use this trust to go back over the outstanding requests and reset expectations. Start telling customers and internal stakeholders, "not now, ask again later." This reduces the pressure on the team and slows the tide of reacting to the loudest customer. The team can now align around some larger goals instead of jumping when a wheel squeaks.

Because you’re not reacting, you’re not trying to jam lots of things into the schedule, so your work in progress drops. You make all the Work in Progress visible and discuss with the team what’s causing that and how to do less at once. By doing less at once, you experience less context switching and you start working as a team again instead of a collection of individuals. Working as a whole team reduces handoffs and improves flow.

Your better flow means that your main efforts aren’t delayed any longer, that the team starts gaining a reputation for executing well.

You’ve built an Improvement Flywheel. (Click image for full size)

Improvement flywheel system diagram

You’ll fail at this if you try and change everything at once. You have to do it incrementally, especially where trust from outside the team is concerned. Pick off one thing from each of the four boxes and aim at that. You’ll find the rest starts falling into place.

Recently Written

Your OKR Cascade is Breaking Your Strategy
Aug 1: Most companies cascade OKRs down their org chart thinking it creates alignment. Instead, it fragments strategy and marginalizes supporting teams. Here's what works better than the waterfall approach.
Your Prioritization Problem Is a Strategy Problem
Jul 23: Most teams struggle with prioritization because they're trying to optimize for everything at once. The real problem isn't having too many options—it's not having a clear strategy to choose between them. Without strategy, every decision feels equally important. With strategy, most decisions become obvious.
Behind schedule
Jul 21: Your team is 6 weeks late and still missing features. The solution isn't working harder—it's accepting that your deadlines were fake all along. Ship what you have. Cut ruthlessly. Stop letting "one more day" turn into one more month.
VC’s Future Lies In Building Winners
Jun 21: AI and megafunds are about to kill the traditional venture model, forcing smaller VCs to stop hunting for hidden gems and start rolling up their sleeves to fix broken companies instead.
Should individual people have OKRs?
May 14: A good OKR describes and measures an outcome, but it can be challenging to create an outcome-focused OKR for an individual.
10 OKR traps and how to avoid them
May 8: I’ve helped lots of teams implement OKRs or fix a broken OKR process. Here are the 10 most common problems I see, and what to do instead.
AI is Smart, But Wisdom Requires Judgement
May 3: AI can process data at lightning speed, but wisdom comes from human judgment—picking the best imperfect option when facts alone don’t point the way.
Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.

Older...

What I'm Reading