Clearly describe the overall project in a few sentences. What’s the vision? Why is this important? How does it move forward the long-term goals of the company?
<aside> 💡 Objectives should not define tactics. Instead, they should clearly define an outcome (a state of existence). The “how” of achieving the objective belongs in the scope.
</aside>
| Driver | |
|---|---|
| Approver | |
| Contributors | |
| Informed |
<aside> 💡 The DACI framework helps clarify who is responsible and who the final approver is for the work. If you find yourself adding multiple drivers or multiple approvers, that’s a warning sign that the project will run into trouble later.
</aside>
| How do we measure success? | Start (Q3) | Target (end of Q4) |
|---|---|---|
| Increase % of new users who try at least one advanced feature within a week of signup | 9% | 15% |
| Increase daily active users by 10% | 13,500 | 14,850 |
<aside> 💡 A good metric is measurable, timeboxed, and provides both a starting point (where the metric was at the project outset) and a target (where the metric should be by the project end date).
</aside>
<aside> 🗝️ Legend: ✅ Done ➡️ In progress 🔲 Not started
Marking milestones with an emoji to indicate high-level status can help communicate quickly to leadership and help focus attention when sharing the doc.
</aside>
<aside> 💡 Milestones should have unambiguous ownership, a short timeline (1–3 weeks), and a clear definition of done. Milestones should be completed sequentially and should build on the success of previous milestones.
</aside>