Flow War Room: analyze and decide
A squad is stuck and the backlog is growing. You are in charge. Find the bottleneck, choose where to act, handle the urgent request without breaking flow, and prioritize what goes first: every decision has a consequence.
A squad is delivering slowly and the backlog is growing. You own the flow. Analyze the situation and make the calls: each has a consequence.
Where is the system bottleneck?
Why a decision mission?
Knowing the theory of bottlenecks, service classes and cost of delay is one thing; deciding under pressure is another. Here you combine the three concepts of the path into a single real situation and see the effect of each choice, which is how learning becomes intuition.
Frequently asked questions
What is a decision mission?
A stalled-flow situation where you choose what to do and see the consequence. There is no text to read first: the learning comes from deciding and getting feedback.
Which concepts does it require?
Three, together: finding the bottleneck from data, handling the urgent request with classes of service, and prioritizing by cost of delay. Separately they are simple; combined in one situation is where they get hard.
Do I need the other experiences first?
It helps, but it is not required. The mission belongs to the "Bottlenecks and Priorities" path, which introduces the three concepts before asking for the decision.
Is there a right answer?
There is a better decision at each point, and it is explained in the feedback. A wrong choice does not block the mission: it shows the effect on the flow, which usually teaches more than getting it right first time.
How long does it take?
About seven minutes, and you can replay it as many times as you like to test another line of decisions.
