Why Genchi exists
I spent years at Atlassian — a company that exceptionally and famously values transparency, running high-pressure projects with strong tooling and disciplined teams.
Even there, I kept seeing the same pattern. A deadline would slip or the delivery would fail to meet the full scope, and when we looked back, the team had known this was coming for weeks. The information was there; there just wasn't a channel to get it to the people who could act on it in time.
It stayed with me long enough that I started writing about it — essays on status reporting, transparency and team confidence, published on HackerNoon in 2019 and 2020.
Conversations with engineering and operations leaders at dozens of other companies, in several countries, confirmed it wasn't an Atlassian problem, it was an everyone problem. While designing Genchi, I interviewed 29 engineering leaders, project managers and developers in depth.
Every one of them had a working process for tracking project status. Almost none of them trusted it, relying more on informal hallway, open-door and watercooler conversations with individual team members.
Existing tools weren't built to surface what teams really believe. So I built one that was.
A known problem, widely documented
This isn't a new problem. It is widely recognized that project status reports are not a reliable predictor of whether a project will be delivered on time and to its full scope.
The reason is one of the best-documented findings in project management. In a study of software project managers, status reports were biased around 60% of the time — twice as likely to be optimistic as pessimistic — most often because of a reluctance to give management bad news (Snow, Keil & Wallace, 2007). Researchers call that reluctance the mum effect. Add the planning fallacy and optimism bias, two of the most widely studied biases in project management, and you get the all-too-common watermelon status report: green on the outside, red in the middle.
This is known, acknowledged and documented — and yet almost every organization still runs some version of the same process: one person, accountable for the date, summarizing — or sanitizing — the current status for the people above them. The full list of biases, with the research behind each, shows why status reports don't reflect what's actually happening.
A different approach: ask the people actually doing the work
Genchi doesn't try to fix every problem with project status reports. It provides an alternative signal — a prediction of whether the project will be delivered on time and to its full scope — that comes directly from the team members doing the work.
The idea is new to project status, but not new. It's the principle behind the wisdom of crowds — independent judgements, combined, often beat a single expert's — and behind planning poker's blind reveal. Companies have tested it directly with internal prediction markets. At Hewlett-Packard, an employee market forecast printer sales more accurately than the official forecast in six of eight cases (JASSS). At Siemens, an internal market predicted a software project would miss its deadline while the planning tools said it would make it (NBER). And Google ran one of the largest corporate experiments of its kind, including markets on whether projects would be completed on time (Review of Economic Studies).
Genchi keeps the principle and drops the machinery — no trading, no currency, just one click. You see the current best guess of every team member, grouped by project and tracked over time. Think of it as a rolling SAFe “fist of five” confidence vote — or a standup status “thumb check” that leaves a record.
What it changes for everyone involved
For engineering leaders — a current, honest delivery prediction for every project in the portfolio. Spot the ones in trouble while there's still time to change course and, just as importantly, know which teams to just leave alone.
For team leaders — an early read from their own team, before a problem becomes a fire drill, and a better option than constantly chasing people for updates. When one person is seeing something the rest aren't, it shows.
For team members — a way to be heard without making it a thing: one click, anonymously. In return, they see how their own project and the teams they depend on are doing, and spend less time in boring status report meetings.
What it asks in return
Genchi works in organizations that strive for transparency and are comfortable hearing bad news early — because that's when something can still be done about it. A worried vote is usually an accurate one. Fix the problem, not the blame, and the signal keeps coming; criticize people for raising a concern, and you've just unscrewed the bulb behind the check engine light.