Milestone
A defined checkpoint marking completion of a project stage.
A checkpoint in the project.
What It Is
In the BWH map, Milestone lives under Execution — Engagement. The working definition is simple: a defined checkpoint marking completion of a project stage.
It is a label with a settled working definition, so the value is in using it the same way every time. Keep it that plain and it will still be true in twelve months.
How It's Used
Milestone comes up in project delivery, scheduling and the handover between people doing the work. It is usually discussed together with Timeline, Deliverable and Approval. The practical test is whether everyone in the room means the same thing by it.
Why It Matters
Getting Milestone wrong is expensive in a quiet way. When it is unclear, work still happens — it just happens twice. It is worth pinning down before anyone builds on top of it.
Think of it as a name on a box. Open the box and this is what is inside: A checkpoint in the project.
Termshift™
How the meaning shifts depending on who is using it, and where.
Practitioners use Milestone as shorthand and expect no explanation — a defined checkpoint marking completion of a project stage.
Outside the industry, most people would just say: a checkpoint in the project.
The Bottom Line
Keep Milestone plain: a checkpoint in the project. That is the version that holds up in a real project.