How to Define the Initiative

The first time the idea gets meeting time, write one sentence naming the problem and one naming what will be different once it works. Cut any word describing effort your team performs: 'run a weekly session' is activity, 'new reps reach quota in two months instead of four' is an outcome. It reads right when no verb in the outcome is one your team does.

Before work begins, write the out-of-scope list, and add each adjacent idea that surfaces in discussion to it rather than leaving it undecided. Put one person on the owner line the same day; if two names feel necessary, split it into two initiatives with two definitions. Scope holds when every new request gets measured against the exclusions.

Once the outcome exists, record two to four success criteria, each with a baseline, a target, and a date. Capture the baseline while you still can, because a target with none cannot show movement later. Stop when a colleague could score the initiative met or missed from those rows alone, without asking what you meant.

After drafting, send the definition to a stakeholder outside the core team and ask them to say what it is and why it matters. Where their version differs, edit the document rather than correcting them; the gap is in the writing. You are done when two people who never spoke to each other give back the same essentials.

Strip your two best definitions to the headings they share, save the result as a template in a shared location, and keep one completed example beside it. Point the next owner who asks for help at the template rather than writing their definition for them. It has taken hold when a definition arrives in the format from someone you never briefed.