Coordination Snapshot
Before you begin
This is not a quiz or an evaluation. There are no right answers.
Answer based on how coordination actually behaves — even if incomplete or uncomfortable.
The goal is orientation, not judgment.
When work stalls in your system, what most often causes the delay?
Think about the last few times something got stuck. What was the structural reason?
How clear are decision rights in practice?
Not how they’re defined on paper — how they work day to day.
When priorities conflict, what usually happens?
Consider what people do, not what they intend.
How does important information typically move through the system?
Think about timing, clarity, and reliability.
How often do misunderstandings require rework?
Think across teams, not just within one role.
When something goes wrong, how quickly is it usually detected?
Think about when issues become visible, not when they’re discussed.
How close is the system to its capacity limits right now?
Think about what the system can realistically handle — not individual effort.
How predictable is timing and rhythm across the system?
Consider schedules, handoffs, and cadence.
Where do problems most often accumulate?
Think about where work tends to slow, break, or loop.
When change is introduced, what usually happens?
Think about how the system responds, not individual reactions.
How aligned are interpretations of “success”?
Think about how people define a good outcome.
Which statement feels most true right now?
Choose the one that best captures the overall pattern.