Genchi vs manual status reports and spreadsheets

Why manual reports are everywhere

Project status doesn't live in one place. It's spread across Jira, Asana, Slack threads, email and hallway conversations, and no single system sees all of it. Automating the report would mean connecting every one of those sources and still missing the conversations nobody wrote down. So a person does it by hand: gathers what they can, applies their judgment and writes it up. It works, sort of, and that's why almost every organization still runs on it.

Genchi doesn't try to pull status information out of every system. The people doing the work already hold the whole picture, including the parts that never reach a tracker. A 1-click confidence vote captures their judgment directly. It's far less effort than writing a report, it provides a consistent signal, and it comes from everyone on the project rather than one author.

What manual reports do well

• They work. They get a status to the people who need it, and have done for decades.
• Free and already in place. Nobody has to buy or learn anything.
• Flexible. Any format, for any audience.
• Narrative and context. Why something changed, what's needed and who has to decide.
• One named person accountable. Someone owns the update.
• Familiar. Stakeholders already know how to read them.

Where they break

• One author, usually the person accountable for the date. Writers of status reports are subject to well-documented biases: optimism bias, the planning fallacy, anchoring on the original plan, escalation of commitment, and reluctance to deliver bad news. Software project status reports are biased about 60% of the time, and optimism is twice as likely as pessimism (Snow, Keil & Wallace, 2007). The biases behind status reports →
• Softened on the way up. Nobody has to lie. People are reluctant to be the bearer of bad news, and each layer rounds the uncertainty off a little more. Why bad news gets softer →
• Stale on arrival. A report captures the status at one moment, and the project keeps moving. Friday's report is still what leaders are reading on Monday, and often until the next one arrives.
• Expensive. In our interviews, one team spent an hour every Friday filling in its report, and one leadership group spent eight hours a week on its status review. What status reporting really costs →
• Green until it's red. Moving a project from green to amber is a public step with a cost, so it gets put off. Why projects stay green →
• Spreadsheets add a staleness problem of their own. Each row is only as current as the last time someone remembered to update it, and there's no trend, only the latest value.

Side by side

Why asking everyone works better than asking one person

Independent judgments from the people closest to the work tend to beat a single forecast, because individual errors cancel out. HP, Siemens and Google all tested asking their own people to predict outcomes, and the crowd beat the official forecasts. Genchi keeps that principle, with independent, anonymous votes combined without an editor, and replaces the machinery with a 1-click confidence vote. Does asking the team actually work? →

When to use which

• Keep a short narrative update where stakeholders need context, decisions or asks: executive reviews, customer commitments, board updates.
• Use Genchi to answer "is it on track?" every week, across the whole portfolio, including which projects are drifting and which teams to leave alone.
• Use both. Shorten the report to the narrative that matters and let Genchi carry the status. The report author can draw on Genchi's trend, comments and blockers instead of chasing people for input.

What Genchi won't do

• Tell you the truth if the whole team is confidently wrong. Genchi measures belief, not reality, and faithfully shows shared optimism.
• Work without a clear goal. If people can't say what "done" means, their confidence can't mean much either.
• Work as well without a deadline. The vote asks whether the team will achieve the goal by the deadline. Without a date, confidence has less to anchor to, though the trend still shows whether the team is gaining or losing it.
• Write the narrative. Comments and blockers add context, and they're attributed so someone can follow up.

Genchi is our product. Manual reporting is the most common alternative, and in most organizations it won't disappear entirely. This page is about which job each should do.