The Problem With Most Strategic Plans
Most strategic plans are 40-page PowerPoint decks that take 3 months to create and are forgotten by the time they are finished.
I have seen this pattern at dozens of companies. The leadership team goes on an offsite. They fill whiteboards. They debate market positioning. They come back with a thick document. It goes into a shared drive. Nobody opens it again until next year's offsite.
The problem is not the thinking. The thinking is usually sound. The problem is the format. A strategy that does not fit on one page is a strategy that nobody can remember, communicate, or execute.
Verne Harnish understood this. After studying hundreds of growth companies — from startups to Fortune 500s — he created the One-Page Strategic Plan (OPSP) as part of his Scaling Up methodology. It distills the most important strategic decisions into a single, scannable document that everyone in the company can understand and reference daily.
The 7 Columns of the OPSP
The OPSP is organized into 7 columns, each answering a critical strategic question. Together, they create a complete strategic picture on one page.
Column 1: Core Values
The question: What are the fundamental beliefs that guide every decision we make?
Core values are not aspirational statements. They are descriptions of how you already behave at your best. If you have to "work towards" a core value, it is not a core value — it is an aspiration.
For tech companies, common authentic core values include:
- Ship and iterate: We launch imperfect things and improve based on data, not debate
- Customers over code: We build what solves customer problems, not what is technically elegant
- Transparent by default: Information is shared openly unless there is a specific reason not to
- Own the outcome: We do not pass blame or responsibility
The test: If a top-performing employee consistently violated one of your core values, would you fire them? If the answer is no, it is not a core value.
How many: 3-5 values maximum. If you have more, you have a list, not a set of values.
Column 2: Purpose
The question: Why does this company exist — beyond making money?
Purpose is not a mission statement. Mission statements are about what you do. Purpose is about why it matters.
For tech companies, purpose often connects to a broader impact:
- "We exist because businesses deserve AI that works in the real world, not just in demos"
- "We exist to make manufacturing safer for the people who build things"
- "We exist to give small businesses access to the same data capabilities as Fortune 500 companies"
The test: If your company achieved its purpose, would you feel proud — even if the company never became wildly profitable?
Column 3: BHAG (Big Hairy Audacious Goal)
The question: What is our 10-25 year aspirational goal?
Jim Collins coined BHAG in Built to Last. It is the single, bold, long-term goal that drives everything else. It should be clear, compelling, and slightly terrifying.
Examples for tech companies:
- "Become the default AI infrastructure provider for European mid-market companies by 2036"
- "Prevent 1 million hours of unplanned industrial downtime by 2040"
- "Make contract review 100x faster for every legal team on the planet"
The test: Does this goal make your team simultaneously excited and nervous? If it feels comfortable, it is not big enough.
Column 4: Brand Promises and KPIs
The question: What do we promise our customers, and how do we measure whether we are delivering?
This column has two parts:
Brand Promises: 3-5 specific commitments you make to customers. Not vague ("excellent service") but measurable ("response within 4 hours, resolution within 24 hours").
KPIs: For each brand promise, one measurable indicator.
Example for an AI SaaS company:
| Brand Promise | KPI |
|---|---|
| "We respond within 4 hours" | Average first response time |
| "Our AI works on day one" | Time-to-first-value (median) |
| "99.9% uptime" | Actual uptime percentage |
| "Your data never leaves your environment" | Zero data exfiltration incidents |
Column 5: Profit Per X (Economic Engine)
The question: What is the single economic denominator that best reflects our unit economics?
This comes from Jim Collins' Hedgehog Concept. You need one "Profit per X" metric that drives economic decisions.
Examples for tech companies:
- SaaS: Profit per user per month
- Consulting/services: Profit per engagement
- Platform/marketplace: Profit per transaction
- Hardware + software: Profit per deployed unit
Why one metric: Because one metric creates focus. If you track profit per user AND profit per engagement AND profit per transaction, your team cannot optimize for all three simultaneously. Pick the one that matters most for your current stage.
Column 6: The Sandbox (Playing Field)
The question: Where do we play and where do we NOT play?
The Sandbox defines your strategic boundaries — the geography, customer segments, products, and channels where you compete.
For tech companies, the Sandbox typically includes:
- Geography: Which markets? (EU only? US + EU? Global?)
- Customer segment: Which companies? (SMB? Mid-market? Enterprise? Specific industries?)
- Product scope: What we build vs. what we integrate vs. what we do NOT do
- Technology scope: Which platforms, languages, and architectures
- Channel: How we reach customers (direct sales? PLG? Partners?)
The critical part is what you exclude. "We serve mid-market manufacturing companies in Europe" is powerful because it implicitly says "we do NOT serve SMBs, we do NOT serve non-manufacturing, and we do NOT serve outside Europe (yet)."
Column 7: Key Thrusts and Capabilities
The question: What are the 3-5 strategic moves we must make in the next 3-5 years?
Key Thrusts are the major strategic initiatives that move you toward your BHAG. They are not quarterly projects — they are multi-year investments.
Example for an AI company:
- Build a proprietary training data pipeline: Partner with 50+ industrial customers to create the largest labeled dataset in our vertical
- Achieve SOC 2 Type II and ISO 27001: Become enterprise-ready so we can move upmarket
- Launch a self-serve product tier: Enable PLG motion for smaller companies while enterprise sales handles the top tier
- Expand to DACH markets: Establish presence in Germany, Austria, and Switzerland as our first international markets
How many: 3-5 Key Thrusts maximum. More than 5 means you have not prioritized.
Cascading the OPSP Through the Organization
The OPSP is not just for the executive team. Its power comes from cascading it through every level of the organization.
Company Level OPSP
This is the master document created by the leadership team. It covers all 7 columns and sets the strategic direction for the entire company.
Department Level OPSP
Each department (Engineering, Sales, Marketing, Product, etc.) creates their own OPSP that aligns with the company OPSP. Their core values and purpose are the same, but their KPIs, Sandbox, and Key Thrusts are specific to their function.
Example: The Engineering department's Key Thrusts might be:
- Reduce deployment time from 2 hours to 15 minutes
- Achieve 99.95% uptime (up from 99.5%)
- Build a self-serve API for the PLG product tier
Individual Level (Quarterly Priorities)
Each team member has quarterly priorities that cascade from their department OPSP. These are not tasks — they are outcomes that contribute to the department's Key Thrusts.
The cascade creates alignment: Every individual knows how their daily work connects to the company's 10-year goal. This is the difference between a team that is busy and a team that is building something great.
Building Your OPSP in Practice
The Preparation (1 Week Before)
Before the OPSP workshop, gather:
- Last year's financial performance
- Customer feedback and NPS data
- Competitive analysis
- Team survey results
- Market research or industry trends
Send this data to the leadership team one week before the workshop. They should arrive with informed perspectives, not start from zero.
The Workshop (2 Days)
Day 1: Discovery
- Morning: Review data, identify patterns, discuss market position
- Afternoon: Work through Columns 1-3 (Core Values, Purpose, BHAG)
Day 2: Definition
- Morning: Work through Columns 4-6 (Brand Promises, Profit Per X, Sandbox)
- Afternoon: Define Column 7 (Key Thrusts), cascade to quarterly priorities, assign owners
The Follow-Up (Ongoing)
- Weekly: 15-minute huddle referencing the OPSP priorities
- Monthly: 60-minute review of KPIs and Key Thrust progress
- Quarterly: Half-day session to adjust priorities and cascade new quarterly goals
- Annually: Full 2-day workshop to refresh the OPSP
Common OPSP Mistakes
Mistake 1: Too many priorities. If everything is a priority, nothing is. The OPSP works because it forces brutal prioritization. Five Key Thrusts maximum. Five brand promises maximum. Five core values maximum.
Mistake 2: No owner for each Key Thrust. Every Key Thrust needs a single accountable owner — one person who wakes up every morning thinking about it. "The leadership team owns it" means nobody owns it.
Mistake 3: Creating the OPSP and never looking at it again. The OPSP must be a living document. Reference it in every strategic conversation. Print it and hang it on the wall. Make it the first slide in every all-hands meeting.
Mistake 4: Confusing core values with aspirational values. Core values describe who you ARE, not who you want to be. If your team does not naturally exhibit a value, it is not a core value. Remove it and replace it with something authentic.
How Hyperion Consulting Facilitates OPSP Workshops
At Hyperion Consulting, we facilitate OPSP workshops for tech companies and startups. We bring the framework, the facilitation skills, and the outside perspective to help leadership teams create strategic plans they will actually use.
Our workshop format includes pre-work, a 2-day facilitated session, and 90-day follow-up to ensure the OPSP translates into action.
Ready to get your strategy on one page? Book a free consultation to discuss an OPSP workshop for your leadership team.
