Windy Hill Partners Talk to a Practitioner →
Free Tool · The First-Win Problem

Five candidate projects. One shot at a credible first win.

Your first project sets the reputation of the entire function. Pick something too big and you'll still be "in progress" when leadership loses patience; too small and nobody notices you won. Score your candidates on the five factors that actually predict first-win success.

Score at least two projects to compare.
Recommended First Win

Your recommended first project

You've picked the project. Now protect it.

  1. Charter it in writing before touching the process. Problem statement, scope boundary, baseline metric, and the sponsor's name on one page. Scope creep kills more first wins than bad analysis ever has.
  2. Set the finish line at 90 days or less. If the natural scope runs longer, cut scope — a completed small win beats a promising large one every time.
  3. Baseline in week one. The before-number is the only thing that makes your after-number credible to a skeptical audience.
  4. Pre-plan the victory lap: agree with your sponsor now on where and how the result gets communicated. A win nobody hears about builds no mandate.
Check Your Function's Full Readiness →

First-project selection is the decision of which improvement to attempt first when a program is new. It matters more than the project itself: an early win that is visible, measurable, and finished builds the credibility a program needs, while an ambitious first project that stalls usually ends the program.

What it produces

A ranked comparison of candidate projects, scored on financial impact, effort to complete, organizational visibility, and whether the data needed to prove the result already exists.

Who it is for

Anyone standing up a process improvement or operational excellence function — particularly a first-time transformation leader who needs a result inside one quarter.

How to read the result

Favour the project that finishes. A modest, provable, visible win in eight weeks is worth more to a new program than a large project that reports progress for a year.

What the tool asks for

Common questions

How do you choose your first process improvement project?

Score candidates on impact, effort, visibility, and data availability. The best first project is one you can measurably finish within a quarter and that someone senior will notice — not the largest opportunity.

Why does the first project matter so much?

A new improvement function has no track record. The first project decides whether the organization treats the function as a source of results or as overhead. Credibility earned early buys the room to attempt harder work later.

What makes a bad first project?

Cross-functional scope with no single owner, no existing baseline data, a payoff more than two quarters out, or a sponsor who is not paying attention. Any one of those turns a first project into an open-ended one.

How long should a first project take?

Six to twelve weeks to a demonstrated result. Long enough to be real, short enough that attention has not moved on before it lands.

Related tools

Mandate Clarity Diagnostic · COPQ Calculator — or see the full Windy Hill Toolkit.

Built by Windy Hill Partners, a process improvement consultancy applying Lean Six Sigma and DMAIC. Every tool here is free and ungated at the point of use.