Product development consumes too many resources—and no one knows exactly where they’re going

Does this sound familiar?

  • Your top people are constantly swamped—but the results fall short of expectations
  • New “urgent” issues keep getting pushed into ongoing projects
  • Consultations, committees, meetings: lots of effort, few decisions
  • Rework becomes the norm (late changes, unclear requirements, interface issues)
  • In the end, it seems like you need more staff—but what’s really missing is flow

It’s not complexity that drains resources, but a system that rewards parallel work, rework, and waiting times.

A possible approach:

1) Transparency instead of gut feeling

We make visible where capacity is actually going: parallel projects, meeting overload, rework, waiting times, unresolved decisions.

2) Limit WIP – increase throughput

Start fewer things at once. Complete more reliably. 

This reduces stress, minimizes context switching, and makes teams more predictable.

3) Systematically reduce rework

Clear requirements, clean interfaces, early validation, and a functioning change/variant system—before costs spiral out of control.

4) Stabilize control & decision-making

Clear priorities, short decision-making paths, and well-defined roles—so projects aren’t “coordinated in circles.”