The One Page Growth Plan: a step-by-step guide.
32 pages, one format. How a 47-point roadmap becomes three levers: step by step, with examples from practice.
A complete guide to setting up the One Page Growth Plan with your leadership team in a single morning. With examples from three industries, the fill-in canvas, and three typical pitfalls we’ve seen across more than 60 engagements.
47 points become three levers: Klartext over completeness.
Contents
- Why one page is enough
- The four fields in detail
- Workshop flow for your team
- Three real examples (anonymized)
- Common pitfalls
- Handover into the operating rhythm
- Appendix: canvas to print
PDF, 32 pages, free. No newsletter requirement, no tracking theater.
Frequently asked questions
What is in the One Page Growth Plan guide?
A complete 32-page walkthrough: why one page is enough, the four fields in detail, a workshop sequence for your own team, three anonymised examples from different industries, the most common pitfalls, the handover into the operating rhythm, and the canvas to print.
How long does a leadership team need to set the plan up?
One morning. The guide is built for that format and walks through the workshop step by step. The effort comes afterwards: the plan has to be defended against new ideas over several quarters.
Which companies is the guide written for?
Leadership teams in mid-sized companies that want to turn a long initiative list into three levers. The examples come from three industries, the pitfalls from more than 60 engagements. The sequence assumes a leadership team that can decide together.
What are the most common pitfalls with the One Page Growth Plan?
Three come up regularly and are covered in the guide. The most frequent one: the plan is created in the workshop and then never defended. Two forces erode it reliably, the opportunistic "could we not also do" and the emotional "but surely we cannot drop that unit".
Do I have to leave my email address?
No. The PDF is freely available, with no newsletter requirement and no tracking.