I already have standups, 1:1s and OKRs — why add another signal?

The objection, as it was put to us

This came up more than any other challenge in our research, and from the most senior people we spoke to.

"I have a lot of signals. Will this one be more useful?" — head of engineering, 130–250 engineers

"This is another signal to organisations that already have lots of signals. Why is this signal different?" — engineering leader

"It's a new ritual. How does this fit with existing rituals?" — senior engineering leader

They're right to ask. Most organisations don't lack information about their projects; they're drowning in it. Adding another stream that says roughly what the existing ones say is worse than useless, because it costs the team effort and gives the leader another dashboard to ignore.

So the burden is on any new signal to demonstrate that it fails in a different way from the ones you have. Here is the honest accounting.

What each existing signal is good at, and where it breaks

The daily standup

Excellent for coordination and for immediate blockers. If someone is stuck today, the standup surfaces it today. One engineering leader told us that most issues he needed to deal with were raised there, and that's a real strength.

Where it breaks: it reaches only the people in the room, and it depends on someone choosing to speak. Growing unease that isn't yet a blocker rarely gets said out loud, because standup is a status round and "I'm vaguely less confident than I was" isn't a status. It also degrades as teams grow. Three separate people described splitting theirs:

"Fifteen members in our standup — it became too long, too big. We split it into three." — developer

And when it splits, the cross-team awareness that made it valuable is exactly what's lost.

One-to-ones

The richest signal available. Depth, trust, and the things nobody would write down. A group project manager told us that if a team was completely blocked she would hear about it in her weekly one-to-ones, and that's true.

Where it breaks: it's one person's perspective at a time, filtered through their relationship with you, and it doesn't scale. A leader with twelve teams cannot hold enough one-to-ones to cover them, so they sample — and sampling means hearing from whoever they meet most often, which is rarely the person closest to the problem.

OKRs

Good for alignment and for making the destination explicit. A leader we spoke to rated his own company's use of them 5.5 out of 10, which was one of the more generous assessments we heard.

Where it breaks: the cadence. Quarterly or monthly reviews tell you the score after the quarter has largely happened. OKRs are a scoring mechanism, not an early warning system, and they're not intended to be one.

Status reports

Covered at length in why bad news gets softer as it travels up. In short: one person's summary, produced under social pressure, days before you read it.

The shared failure mode

Line those up and the pattern is uncomfortable. All four depend on someone deciding to say something. Standups need a person to raise it. One-to-ones need a person to raise it. OKR reviews need a person to mark a key result at risk. Status reports need a person to write down that things aren't going well.

Every one of them therefore has the same blind spot: the situation where a team is becoming less confident but nobody yet has anything concrete enough to justify saying so. That's not an edge case. In our research it's the normal way a project goes wrong — gradually, then suddenly, with a long quiet period in which everyone involved is slightly uneasy and nobody has grounds to escalate.

And they're correlated. The pressures that keep someone quiet in standup — not wanting to be the pessimist, not being certain, not wanting to trigger attention — are the same pressures operating in the one-to-one and in the status field. They don't fail independently. They fail together, on the same projects, at the same time.

What makes a signal different

Four properties, and it's worth holding any new signal to all four — including this one.

• It doesn't require anyone to speak up. A response is requested from everyone, on a schedule. Saying "I'm slightly less confident" is a default action rather than an act of courage.
• It's anonymous, so honesty is cheap. This is the property that separates it most sharply from the other four. In a standup, a one-to-one, an OKR review or a status field, your name is attached to your assessment. Registering doubt costs you something — you might be wrong, you might look like the pessimist, you might trigger attention nobody wanted. Aggregated responses remove that cost entirely, which is the only reliable way we know to stop "fine" being the default answer.
• It's forward-looking. Standups, reports and OKR reviews all report on what happened. "How confident are you that we'll hit the goal?" asks about the future, which is the only thing you can still change.
• It's automatic, regular, and kept. The other four produce moments — a conversation, a meeting, a document — and nothing that persists in comparable form. A check-in that runs on a schedule and is recorded every time produces a line rather than a series of dots, and a line is the only way to see slow change.

Why the record matters more than any single reading

Slow drift is invisible to the people inside it. A team whose confidence erodes over six weeks doesn't experience six weeks of erosion — it experiences six ordinary weeks, each slightly worse than the last, none different enough from the one before to be worth mentioning. That's precisely why nobody speaks up: there was never a day on which things noticeably changed.

This is the failure the other four signals cannot address, because all four are point-in-time and mediated by human recollection. Nobody at a standup says "I'm marginally less optimistic than I was five weeks ago," because nobody carries a five-week baseline in their head.

An automatic, recorded signal does carry it. The comparison is arithmetic rather than memory, so the slow boil becomes visible while it's still slow — and that, rather than any single week's reading, is the thing you're buying.

A signal with those properties fails in different circumstances from the four above. It won't catch what a one-to-one catches — the nuance, the thing someone will only say to your face. It will catch the thing none of them catch: distributed, low-grade unease that hasn't yet found a spokesperson.

When you genuinely shouldn't add it

Some honest disqualifiers.

If you run one team of five and sit with them daily, you already have this signal. You can see it. One developer told us plainly that the value seemed more apparent higher up, "because I already have that information from a standup" — and for his situation, he was right.

If your organisation punishes bad news, a new channel for reporting it will produce the same green readings as the old ones. Fix that first; no tool substitutes.

If you won't act on it, don't collect it. A signal that produces no response teaches the team that responding was pointless, and you'll have spent their goodwill for nothing.

How Genchi fits alongside the rest

Genchi isn't a replacement for standups, one-to-ones or OKRs. It replaces the status-reporting portion of them — the round where everyone reports how their work is going — and leaves the parts those rituals are genuinely good at.

The intended sequence: the confidence signal tells you where to look, and the existing rituals are where you look. A trend that turns downward is a prompt for the one-to-one you'd otherwise have spent on general catch-up.