Models · No. 05

Momentum over Measurement

For small teams, a simple weekly rhythm of shipping beats heavyweight goal-setting.

OKRs promise direction and measurable outcomes. For small teams they often bring complexity instead, taking time away from the one advantage a small team has: speed.

The alternative is a light rhythm. Plan on Monday, execute through the week, review on Friday. Set weekly deliverables, and keep people accountable without a rigid goal structure.

When execution slows, the cause is rarely a missing OKR. More often the team is spending its time defining key results instead of delivering them.

It doesn’t mean no structure

It means choosing the smallest structure that keeps everyone honest, and adding more only when the team is big enough to need it.

The essay

OKR or no OKR

Why Small Teams Should Focus on Execution, Not Overhead

Feb 14, 2025 · 1 min read

Based on my experience in a few places, I’ve seen small teams operate at a startup pace while being weighed down by OKRs. In theory, OKRs provide direction and measurable outcomes. In reality, they often introduce unnecessary complexity, sucking bandwidth from teams that should be focused on rapid execution. For small teams, spending cycles setting quarterly goals, aligning key results, and tracking progress can be counterproductive when agility is the primary advantage.

Instead of OKRs, a lightweight execution model can be far more effective: set weekly deliverables, plan on Monday, execute through the week, and review progress on Friday. This keeps teams accountable without the burden of rigid goal structures. I’ve seen teams that followed this simple rhythm move faster, adapt quicker, and deliver meaningful results without getting bogged down in process overhead. When the focus shifts from planning for the quarter to shipping every week, the momentum becomes unstoppable.

This doesn’t mean abandoning structure altogether. It means optimising for momentum over measurement. In a few places I’ve worked, whenever execution slowed down, it wasn’t because of a lack of OKRs but because the team was spending too much time defining key results rather than actually delivering. If a team is working towards a big milestone, breaking it into tangible deliverables and shipping incrementally works far better than tracking abstract metrics. The goal should be clarity in execution rather than chasing predefined success indicators.

What can you do?

  1. Ditch quarterly OKRs for now – Set a clear direction, but don’t let formal tracking slow execution.

  2. Adopt a weekly cadence – Plan on Monday morning, execute with focus, and review results on Friday.

  3. Keep accountability lightweight – A simple check-in on Friday to discuss what got done, what didn’t, and what’s next is enough.

  4. Prioritize momentum over tracking – Measure progress by output, not by adherence to predefined metrics.

Speed is a startup’s biggest advantage. Instead of over-engineering goals, keep teams lean, focused, and shipping. If you find OKRs helping, use them. If they slow you down, drop them—execution is what truly matters.

Pairs well with