OMG: outcome, milestones, groundwork
A simple way to keep activity from masquerading as progress.
1 min read
Define the measurable outcome first, choose milestones that prove movement toward it, and only then decide the groundwork that can cause those milestones.
Teams routinely confuse work with progress. A long task list can feel productive even when nothing important has changed.
I use a simple hierarchy: Outcome, Milestones, Groundwork.
O: Outcome
State the external result you want in measurable terms. It should describe what will be different, not what you plan to do.
M: Milestones
Milestones are smaller external results that prove you are getting closer to the outcome. They should be countable or observable.
G: Groundwork
Groundwork is the work you do to cause the milestones: research, posts, calls, product changes, campaigns, meetings and experiments.
If a milestone can be completed without moving the outcome, it is probably groundwork wearing a better title.
