Good operating rhythm isn't built from dashboards. It's built from a handful of questions, asked often enough — and answered honestly enough — that the truth has somewhere to surface before it becomes a crisis.
A dashboard tells you what happened. It rarely tells you what people saw coming, what they're quietly worried about, or where the real bottleneck sits. Those things live in conversation, and they only come out if a leader asks for them on purpose. These five questions are the ones we find earn their keep, week after week.
The five questions
1. "What did you expect to happen, and what actually happened?"
This separates the plan from reality without assigning blame. It treats a missed forecast as information rather than a failure, which is the only way to keep getting honest forecasts. Over time, the gap between expected and actual is the single most useful signal a team produces about how well it understands its own work.
2. "What are you waiting on — and from whom?"
Most delays aren't caused by slow work; they're caused by waiting. This question drags hidden dependencies into the open: the approval that's been sitting for a week, the answer that never came, the handoff that quietly stalled. You usually can't fix what you can't see, and bottlenecks are remarkably good at staying invisible.
3. "If you had to cut this in half, what would you keep?"
Forced prioritization reveals what someone actually believes is essential. The answer tells you where the value really is — and, just as usefully, how much of the current plan is padding that no one has felt safe enough to question.
4. "What would you do if it were entirely your call?"
People withhold judgment when they're unsure of their authority, and that withheld judgment is often the best thinking in the room. This question gives permission to say it. If the answer is consistently sharper than what's actually being done, you've found a place where ownership is unclear — and that's worth fixing.
5. "What's getting worse that no one's talking about?"
This is the early-warning question, and the hardest to ask in a way that gets a real answer. It invites the uncomfortable truth — the slow degradation, the workaround that's becoming permanent, the morale problem no one wants to name. Ask it often, and act on what you hear, and people will start telling you while there's still time to do something.
Most operational failures are not surprises. They are things several people saw coming and no one was asked about in time.
How you ask matters as much as what you ask
The questions are only as good as the conditions around them. Ask them on a regular cadence, not just when something is already on fire, so the answers stay calm and candid. Make it genuinely safe to say the awkward thing — the first time honesty is punished is the last time you'll hear it. And above all, act on what you learn. A team that watches its answers disappear into nothing will, very sensibly, stop giving you real ones.
None of this requires a new system or another tool. It requires a leader willing to ask plainly, listen without flinching, and then do something about the answer. That, more than any dashboard, is what keeps a business honest with itself.