Is there a less painful way to do project status reporting?

What the ritual actually costs

We didn't ask the 29 engineering leaders in our research how long status reporting took. They volunteered it, usually with visible irritation.

"People set aside an hour to fill in the status tool on a Friday." — group project manager, 180–200 engineers

"Eight hours a week." — product lead describing his company's weekly status process

"Usually takes about an hour or two to stay current. You can spend as much time as you want on it. Don't get that much interaction on the page — a few comments here and there." — team lead, 7 engineers

That's the production side. There's a consumption side too, and one group project manager captured both:

"It turned into a big deal to fill in and a big deal to consume."

Then the meetings. A principal project manager described his week: a 30-minute scrum-of-scrums with the leadership team every morning at nine, daily leadership standups with all PMs and team leads, plus the written updates. His summary of the whole arrangement:

"Keeping abreast of status: a lot of effort and a pain in the ass."

Add it up for a mid-sized organisation. Thirty team leads at an hour a week each is roughly a full-time role, spent producing documents that one developer we interviewed described as follows:

"Doubt anyone read it."

What the ritual is actually for

Before replacing it, it's worth separating what the status meeting genuinely does.

Routine transmission. Moving the fact that things are broadly fine from the people doing the work to the people who need to know. This is the bulk of it by volume, and it's pure overhead — a meeting to communicate the absence of news.

Exception handling. The occasional item that genuinely needs discussion: a decision, a trade-off, a request for help. This is the valuable part, and it's a small fraction of the time spent.

Social function. Contact, visibility, the feeling of being kept in the loop. Real, but usually better served by something other than a recurring status meeting.

Compliance theatre. Filling in the form because there is a form. One leader described having to enforce this "ruthlessly" at his organisation. If a process needs ruthless enforcement, the people doing it have concluded the value isn't there.

The opportunity is that the first and fourth categories — the majority of the time — can be handled without a meeting or a document.

What replaces it

Routine transmission is a data problem, not a conversation problem. If the question is "is this on track?", then asking everyone on the team to answer that question directly, on a schedule, answers it better than one person writing prose about it.

Practically, that means:

• One question, asked of everyone. Not a form, not a narrative — a single confidence rating that takes seconds.
• On a schedule, not on request. Nobody has to remember to ask, and nobody has to remember to send.
• Recorded, so the trend is visible. The direction is more informative than any single reading.
• Visible to everyone who needs it, rather than pushed up one reporting line at a time.

The nearest familiar analogue is NPS — not in what it measures, but in its shape. One question, asked on a schedule, answered in seconds, aggregated across people and tracked over time. Customer satisfaction got a standing metric decades ago; project delivery never did, and has run on narrative and gut feel ever since. (The comparison stops at the shape: NPS measures loyalty and uses its own promoter-and-detractor arithmetic, neither of which applies here.)

With that in place, the recurring status meeting has nothing left to do that the signal doesn't do better and faster. What replaces it is a shorter, sharper conversation that happens because the signal indicated something — a meeting with a reason, rather than a meeting on a calendar.

What not to remove

Three things are worth defending, and a signal doesn't replace any of them.

The conversation after a bad signal. The number tells you where to look, never what's wrong. The diagnosis still happens between people. See what to do when the trend goes down.

The coordination part of standup. Standups do two jobs — reporting status and unblocking each other. Only the first is replaceable, and removing the second would be a mistake.

One-to-ones. They cover ground no measurement reaches. What changes is that they stop being spent on status recitation and start from better information.

The objection worth taking seriously

A senior leader put the counter-argument to us more precisely than we would have:

"The tax on me is nothing. But on my group? I'm going to make 500 people spend five minutes doing this. So it needs to work."

Exactly right. Replacing one ritual with another is only worthwhile if the new one is dramatically cheaper. The arithmetic: a weekly two-second check-in across 500 people is well under an hour in aggregate — roughly what a single team currently spends producing one status report. If the replacement takes five minutes per person, it isn't a replacement, it's a second tax.

Which is why the cost per person is the whole design constraint, and why anything asking for a written update in a structured form — however nicely presented — is a smaller version of the same problem.

How Genchi does this

Genchi asks each team member one question at your chosen cadence — daily, weekly, or whatever fits — delivered in Slack, email or the app. One to five. About two seconds.

The responses aggregate into a current signal for each initiative, with the trend across recent check-ins and any blockers people raised. Leadership sees the whole portfolio colour-coded, without anyone writing a report and without a meeting to collect it.

Teams typically use it to replace the status portion of standup and the weekly written update, and keep everything else.