Status Maintains Motion. Decisions Create Momentum.

One of the first teams I led had a weekly status meeting.

Twenty people. Sixty minutes. Everyone talked. Nothing changed.

It looked productive. It felt responsible. And the work didn't move an inch faster because of it.

That meeting taught me something I've seen confirmed many times since: most status reporting tells you what people think you want to hear, not what's actually happening.

Why status reports so often say nothing

"Everything is on track. No blockers. Will update next week."

I've read thousands of reports like that. Green lights everywhere - while a project slowly burns behind them.

It isn't because people are dishonest. It's because the format works against the truth:

• People report what they think you want to hear. Nobody wants to be the one with the red light.
• Problems get softened. "Slight delay" covers a lot of ground.
• Context disappears into bullet points and traffic-light colors.
• Real blockers hide behind "working on it" and "almost resolved."

And it's getting easier to produce reports nobody reads. Dashboards update themselves, and AI tools can summarize a week of activity in seconds. That's useful - but a beautifully generated summary of the wrong thing is still the wrong thing. More reporting isn't more visibility.

What I replaced the meeting with

We kept the same time slot and changed its purpose. The hour-long status update became a 30-minute decision review, built around three questions:

1. What is blocked right now?
2. What decision is needed to unblock it?
3. Who owns that decision, and by when?

No demos. No reporting. No slides. Just clarity, a decision and a next step.

What changed:

• Work moved faster, because blockers got cleared in days instead of weeks
• Arguments about the roadmap faded, because decisions were made in the open
• Teams stopped defending their progress and started making it
• Leadership finally saw where priorities were unclear - which, it turned out, was the real cause of most of the blockers

The biggest surprise? People loved it. Not because it was shorter, but because it had a purpose.

Most status meetings exist because nobody is confident in the plan. Once the priorities are clear, you don't need constant justification. You need decisions.

How I get the real picture instead

The decision review handles the blockers people know about. For the ones they don't - or won't say out loud - I use a few other habits.

Ask better questions.

"How's it going?" gets "Fine." Specific questions get real answers:

• "What's the riskiest thing on your plate right now?"
• "What would you do differently if you started this over?"
• "What assumption are you making that might be wrong?"
• "What should I be asking that I'm not?"

Ask to see the work.

Instead of a report, a walkthrough. Show me the actual thing - the code, the design, the test results. Walk me through the hard part. Explain the trade-off you made and why. Ten minutes looking at real work tells me more than a month of status updates.

Watch the patterns.

The data that matters rarely appears in a report:

• Do deadlines keep slipping by the same amount?
• Do the same problems keep showing up across different projects?
• Are people working longer hours but delivering less?
• Are "almost done" tasks staying almost done for weeks?

If you need a written update, change the questions.

Some teams genuinely need a regular written update, especially when people work across time zones. Make it three lines: what changed since last time, what's at risk, and what decision you need from me. It takes less time to write and it's far harder to fill with comforting noise.

None of this works without trust

The real breakthrough comes when people realize you're not looking for someone to blame. You're looking for obstacles to remove.

That's when the conversation shifts from defensive reporting to solving problems together. It takes a few deliberate habits:

• Make it safe to raise problems early - and thank people when they do
• Reward honesty, especially when the news is bad
• Focus on what happens next, not on explanations for what went wrong
• Be available when problems happen, not just at the scheduled update

The most useful things I've learned about projects came from quick hallway conversations, not status meetings. People tell you what's really happening when they trust you'll help rather than judge.

The bottom line

Status reports tell you what happened. Real conversations tell you what's about to happen.

Status maintains motion. Decisions create momentum.

If your calendar is full and your roadmap is stuck, start by killing one status meeting - and replacing it with three questions.

Related reading

• The 45-Minute Tech Spend Checkup Every CEO Should Run
• Do You Need a CIO, or Just CIO-Level Thinking?

If your projects look green on paper but never seem to land, let's talk. Getting honest visibility into delivery is often the quickest win a technology leader can make.