Focus Ratio: the only productivity metric that matters

Focus Ratio is the share of your team's working hours spent in deliberate, single-task focus blocks. Track this one number and most other productivity metrics become noise — leading indicators of the same underlying state.

The teams that ship the most aren't the ones who optimise their sprint velocity. They're the ones whose people get long unbroken stretches of attention against a single task.

The formula

For a given week, Focus Ratio is:

Focus hours / total working hours

A "focus hour" is one hour spent on one task with the rest of the workspace closed. If a Builder spends 8 hours in the office and 3 of those were in single-task focus blocks, their Focus Ratio for the day was 3 / 8 = 37.5%.

Team Focus Ratio is the average of all Builders' ratios. We don't weight by seniority — every distracted hour costs the same in aggregate.

What it doesn't measure

Focus Ratio is not a proxy for output, hours worked, or "productivity" in any moralised sense. A team that ships nothing can still have a 70% Focus Ratio. A burned-out team can have a high one.

What it does measure is whether the working hours your team puts in are getting concentrated effort or scattered attention. That's the precondition for everything else.

Why most other metrics are noise

Sprint velocity, throughput, lines of code, story points completed — these are downstream of focus. When focus drops, all of them drop in lockstep, but they drop later. By the time velocity is visibly off, you're already in the post-mortem.

The leading indicator is focus itself. So measure that.

How to track it without instrumentation

You don't need software to start. Hand every Builder a piece of paper for the week. They write down:

1. When they started a focus block
2. What task it was for
3. When it ended (or was interrupted)

At the end of the week, sum the focus minutes and divide by total working minutes. Average across the team.

This is crude, but it's enough to see a real number. Most teams measuring for the first time are surprised — the typical small-team baseline is 25–35%.

The 5-step protocol

Once you have a baseline, here's the protocol we run with new agencies:

1. Pick one task per Builder per day for the next two weeks. That task gets a 2-hour focus block, scheduled.
2. Cancel the daily standup for the same two weeks. Replace it with reading the board.
3. Define one interrupt channel. Everything urgent goes there; everything else waits.
4. Re-measure at the end of week 2. The number will be higher. By how much is the team's signal.
5. Pick a target. 60% is realistic for small high-output teams. 80% is fictional.

If you want this protocol enforced rather than self-imposed, that's what Focus Mode does — same idea, but with a timer the team can see and a board that updates as soon as anyone hits "start".

What changes when you cross 60%

Around the 60% Focus Ratio mark, the team's relationship with work changes:

• Standups disappear. The board carries the same information faster.
• Status meetings disappear. Nobody needs to ask what shipped this week.
• Recruiting changes. The bar moves toward people who can sustain focus, not people who can survive chaos.

The reverse is also true: when Focus Ratio drops, every coordination ritual quietly returns. Standups grow back. Slack threads thicken. The team starts feeling busy without feeling productive.

The metric is the early warning.

Where to start

Pick one Builder. Measure their Focus Ratio next week on paper. Compare to what you would have guessed. The gap between those two numbers is usually the most useful data your team will collect this quarter.

When you're ready to make focus the default state rather than the exception, the Focus Mode deep-dive walks through the ritual we ship with.