Busy is the enemy of progress

A seed founder showed me a Linear board last month with 147 tickets closed in the quarter. The team had run twelve sprints. Retros were healthy. Standups ran. MRR had moved from $9.4k to $9.6k. She asked me why the board said one thing and the P&L said another. Forty minutes in she said the sentence every stalled founder eventually says out loud. 'I don't actually know what we've decided in the last two months.'

Activity and progress feel identical from the inside. From the outside, and from the bank account, they are not the same artefact. A team can look productive for a quarter while the company stops moving, and the velocity chart will never tell you the difference.

Decision count is the metric

When I am trying to work out whether a team is actually progressing or just busy, I do not look at velocity charts or OKR scorecards. I look at one number. How many hard decisions did the founder make last week?

A hard decision is one where the trade-off was uncomfortable and the founder had to pick. Not 'which feature next' (that is a priority call, usually reversible). Something closer to: kill this customer segment. Fire this vendor. Double the price. Stop building X and start selling Y. Calls that cost something, and that the founder will defend in twelve months or apologise for.

A good week has three of those. A great week has one that nobody agreed with at the time and looked right a month later. A bad week has none. The team was busy. The standups ran. The product shipped. Nothing irreversible happened.

Why shipping looks like progress when it isn't

Engineering teams know how to execute. Tickets in, tickets out. The feedback loop is tight and satisfying. Standups surface blockers. Retros improve throughput. Velocity stabilises. It feels like the company is working.

What the velocity chart cannot show you is whether the features you shipped changed anything for anyone. You can ship a clean, high-velocity sprint into a void for six months. The team will still feel busy. The founder will still feel productive. The runway will not care.

• If your sprint board looks healthy and your pipeline is flat, you are busy, not progressing.
• If your team can name three decisions they made last week without checking Notion, you are progressing.
• If every week looks like the last, you are on a treadmill, and the treadmill is running out of power.

The Monday email test

The simplest diagnostic I know is the Monday email test. On a Monday morning, before standup, draft an email to your lead investor. One paragraph. What changed in the business last week? Not what you built. What changed.

If the email writes itself in two minutes, you had a good week. If you struggle for fifteen minutes and end up listing features shipped, you were busy. If the email only reads sensibly once you reframe it as a corporate update, you are in activity theatre, not progress. The investor will not write back to correct you.

I am not telling you to shut the engineering team down. I am telling you that every Monday, you should ask whether the last seven days produced a decision or a deliverable. If it has been four Mondays without a decision, that is the signal. Stop. Call the week. Change the shape of how the team works until the decisions start showing up again. The founder I started with did exactly that in November. Her MRR moved from $9.6k to $31k in the sixteen weeks that followed. Not because the team got faster. Because she started killing things on Mondays.

Runway is a finite set of weeks. Each week is a decision or a deliverable. Deliverables without decisions are how companies run out of money while their JIRA boards look fine.