Bottleneck Battlecards
Recall constraint-management responses that explain why non-bottleneck improvements can wait.
Objection Our team is overloaded too. Why are we only talking about the bottleneck? A non-bottleneck team feels dismissed. Your line Your load matters. For this improvement cycle, we are asking which change increases total flow. If your work feeds the bottleneck, improving input quality is part of the constraint plan. Saying 'you are not the bottleneck' can sound like 'your problem is not real.' It validates local pain while keeping the decision rule tied to throughput. The bottleneck team should just work faster. Stakeholders blame the visible waiting step. Maybe, but first we should ask what starves, interrupts, or…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in