# [Year] operating plan · [Product or portfolio] · OP1 draft v[n] / OP2 **Author:** [Name] **Finance partner:** [Name] **Due:** [Date] **Top-down guidance received:** [Date, link] ## 1. Introduction and thesis (one paragraph) What this product will achieve next year, and the single bet the plan rests on. ## 2. Last year in review | Goal | Target | Actual | Hit / missed | What we learned | |---|---|---|---|---| | | | | | | ## 3. Key metrics (more than 5, fewer than 20) | Metric | Type (input/output) | Owner | Q1 | Q2 | Q3 | Q4 | Year-end target | |---|---|---|---|---|---|---|---| | | | | | | | | | ## 4. Key initiatives | Initiative | Leader | Start / finish | Metric it moves, and by how much | Resources | Elevated goal? (Y/N) | |---|---|---|---|---|---| | | | | | | | ## 5. Resources and organization Headcount by team, hiring plan, operating cost, usage-driven cost (inference, cloud) and any org changes. ## 6. What we will not do | Request or option declined | Who asked | Why not this year | |---|---|---| | | | | ## 7. Risks and dependencies Top risks from the register; dependencies on other teams, with named counterparts and agreed dates. ## 8. FAQ Questions a skeptical reviewer will ask, answered in advance. ## 9. Appendix P&L, initiative detail, headcount table, roadmap. ## Change control After OP2, changing a goal or adding resources requires approval from [role]. Adding an initiative within existing resources requires [role]. ## OP2 revision (January) Variance against Q4 actuals: [summary]. Changes from OP1: [list, with reasons].