Why Iteration Beats Perfection: Fast Feedback for Sustainable Change

Medium - Requires some preparation Recommended

Early in her career, a young project manager was obsessed with nailing every detail before launching a new internal program. She spent weeks collecting data, aligning with every possible stakeholder, and polishing presentations. When the project rolled out, it was dead on arrival—too late for the market, too generic for the team. After some tough lessons, she adopted a new rhythm: set a short planning window, share a rough draft of the next quarter’s goals, and invite direct feedback.

There were hiccups. The first cycles were messy, but issues were quickly spotted and fixed. Over time, the team learned the value of getting into motion, making quick tweaks, and avoiding endless hypothesis without experimentation. Quarterly retrospectives became routine: one person would always ask, 'What did we assume, and what was actually true?' Each learning—big or small—drove the next cycle.

Research on agile processes and behavioral psychology underscores this pattern: frequent, time-limited experimentation outperforms ponderous perfectionism. The key is visible learning and adaptation—making 'good enough' better, step by step, by focusing more on what’s next than what’s past.

Instead of waiting for perfect clarity, launch your new system, plan, or project as soon as it’s basically workable. Limit your planning and decision-making to a specific, bite-sized window, knowing you’ll have a built-in chance to adapt. Mark your calendar for a regular feedback session to review what happened, tweak the next phase, and celebrate every insight you harvest. Don’t fall into the trap of waiting until 'someday.' Get moving, iterate, and use each mistake as a step up. Challenge yourself to try this with the next project on your plate.

What You'll Achieve

Reduce overthinking and wasted effort, stay nimble in fast-changing contexts, and build a culture of continuous learning and improvement.

Launch Before You’re Ready—Then Adjust Every Quarter

1

Deploy your system as soon as it’s 'good enough.'

Resist waiting for the perfect plan, framework, or metric. Start with a version you can learn from, not a flawless setup.

2

Timebox your planning sessions.

Limit decision-making (e.g., on OKRs, project goals) to a short window—24 hours, one week at most. Avoid analysis paralysis.

3

Hold regular retrospectives to iterate.

After each cycle (week, quarter), gather feedback on what worked, what didn’t, and immediately adjust for the next round.

4

Celebrate learning, not just winning.

Recognize progress and insights—even failed experiments count as forward movement if they lead to a better next step.

Reflection Questions

  • Where am I letting fear of imperfection delay action?
  • How can I timebox my next planning session?
  • What routine will help me learn quickly from each attempt?
  • How will I reframe mistakes as valuable data?

Personalization Tips

  • A software team pushes an early version of a new feature, learns from user feedback, and ships improvements weekly.
  • A writer finishes a first rough draft in one week then revises based on feedback, rather than tinkering endlessly.
  • A group of friends tries a new meeting format for their club, reviews its success after one month, and refines the agenda accordingly.
Radical Focus : Achieving Your Most Important Goals with Objectives and Key Results ( OKRs )
← Back to Book

Radical Focus : Achieving Your Most Important Goals with Objectives and Key Results ( OKRs )

Christina Wodtke
Insight 7 of 8

Ready to Take Action?

Get the Mentorist app and turn insights like these into daily habits.