There’s a version of OGSM that works before product-market fit — and it fits on a whiteboard.
Most strategic frameworks were built for organisations that already know what they’re doing. OGSM is no exception — it was designed for Procter & Gamble, not for a two-person team pivoting every 90 days. But that doesn’t mean it’s useless before you hit product-market fit. It means you have to strip it back.
This post walks through what pre-PMF OGSM looks like in practice, what to cut, and when you should forget OGSM entirely.
Can OGSM Work Before You Have Product-Market Fit?
Yes — with significant caveats.
OGSM’s strength is alignment. It forces a team to agree on one Objective, a small number of Goals that define what success looks like, a handful of Strategies that describe how you’ll get there, and Measures that tell you whether your Strategies are working.
At the pre-PMF stage, the alignment problem is real. Co-founders argue about whether to prioritise the enterprise deal or the self-serve funnel. The first engineer builds for scale while the founders are still testing whether anyone wants the product. A one-page strategic document can cut through that noise faster than any amount of Slack discussion.
But here’s where it gets complicated. In a mature organisation, every element of an OGSM is grounded in data — historical performance, market research, validated positioning. Pre-PMF, you don’t have that. Your Objective, Goals, and Strategies are all hypotheses. Nothing is validated. The market may tell you in month three that your core assumption was wrong, and you’ll need to rewrite the whole thing.
That’s fine. The OGSM is not a contract — it’s a shared bet. The value is the alignment it creates now, not the accuracy it guarantees later. But to get that value without the overhead, your pre-PMF OGSM needs to feel less like a three-year plan and more like a focused hypothesis for the next six months. Horizon matters enormously here. Cut it to 90–180 days maximum and commit to reviewing it at the end of that window.
What Does a Pre-PMF OGSM Actually Look Like?
Here’s a worked example for a pre-revenue B2B SaaS startup building a compliance automation tool for SMEs.
Objective: Become the compliance automation tool that professional services SMEs trust to manage their audit trails.
Goals:
- Achieve 10 paying customers (minimum £99/month) by end of month five
- Reach NPS > 50 among pilot users after 60 days of use
Strategies:
- Direct outreach to compliance managers in legal and accounting firms via founder-led LinkedIn outreach — 20 targeted messages per founder per week, no automation
- Ship fortnightly based on pilot feedback — biweekly releases tied directly to the highest-friction moments identified in customer interviews
- Run a 30-day free pilot with white-glove onboarding — reduce time-to-value so pilots convert before fatigue sets in
Measures:
- Outreach response rate (target: ≥15%)
- Pilot-to-paid conversion rate (target: ≥40%)
- Weekly active users among pilot cohort (target: ≥70%)
Notice what this OGSM is doing — and what it isn’t.
The Objective is qualitative and directional. It describes the position you want to own in your market, not a number you want to hit by a date. That logic belongs in Goals. Goals are where the measurable commitments live — 10 customers, NPS above 50. They tell you whether you’re on track to reach the Objective.
Each Strategy is a real bet: a specific channel, a specific cadence, a specific go-to-market mechanism. There’s no hedging. If you chose LinkedIn outreach, you chose it over cold email, paid ads, and inbound SEO. That trade-off is the strategy. If every option still looks equally valid, you haven’t made a decision yet.
The Measures are leading indicators, not lagging ones. Outreach response rate tells you whether your messaging is resonating before you know whether it converts. Pilot-to-paid conversion tells you whether the product earns its price before you’ve closed enough deals to know if the model works. That’s the point — Measures should give you signal early enough to change course.
That’s it. One Objective. Two Goals. Three Strategies. A handful of Measures. It fits on one page. It could fit on a whiteboard. Nothing here requires a planning retreat or a strategy consultant — just a shared answer to the question: what are we actually trying to prove, and how?
What Should You Strip Out of a Pre-PMF OGSM?
Cascading Measures. In a full OGSM implementation, every Strategy has its own Measure set, and you may cascade further down into team or function-level Measures. Skip this entirely. You don’t have enough stable KPIs yet, and you’ll spend more time debating which metric belongs to which Strategy than you will running experiments. At this stage, pick three to five Measures that collectively tell you whether the Objective is on track — and leave it there. (For reference on what strong Measures look like at a later stage, see 7 OGSM Mistakes That Kill Your Strategy — the most common one is Measures that are outputs, not leading indicators.)
More than three Strategies. If you have five or six Strategies pre-PMF, you’re either hedging or you haven’t made a real bet yet. Three Strategies is a hard cap. Preferably two. Each Strategy should represent a real trade-off — something you’re choosing to do instead of something else. If every option looks equally valid, you haven’t done the hard prioritisation work. Pick the bets with the most signal-per-effort and cut the rest.
More than three Goals. Your Goals define what success looks like. Two to three Goals forces you to get specific about what actually matters in the next 90–180 days. More than that and you’re writing a wish list, not a strategy. If you have five Goals and they’re all “critical,” none of them are. Ruthlessly narrow it down to the two outcomes that would genuinely change what you do next.
Long time horizons. Don’t write a three-year OGSM at the pre-PMF stage. You don’t have the data to justify it, and it will be out of date before the ink is dry. Stick to 90–180 days. Review it at the end of that period. If your hypothesis has changed — and it probably will — update your Objective and reset.
How Do You Build Your First Pre-PMF OGSM?
You don’t need a facilitated off-site. You need a half-day session with your co-founders and a shared document. Here’s a simple sequence that works.
Start with the Objective. Before anything else, spend 30–45 minutes on the Objective alone. Write it individually, then compare. The Objective should describe the strategic position you’re trying to own — qualitative, directional, no dates. If you and your co-founder write different Objectives, that’s the most important conversation you’ll have all quarter. Don’t paper over it by merging both into a long sentence. Decide.
Draft the Goals together. Once the Objective is agreed, Goals follow relatively quickly. Goals answer: what does success look like in numbers, by when? Aim for two Goals maximum at this stage. If you find yourself wanting a third, ask whether it’s really a Measure in disguise.
Challenge every Strategy. For each proposed Strategy, ask: what is this instead of? If you can’t answer that, it’s not a Strategy — it’s a preference. A genuine Strategy has an opportunity cost. Write the alternative you rejected next to each Strategy you kept, and make sure the team understands why you chose this one.
Set your Measures last. Measures are often written first because they feel concrete and comfortable. Write them last. Start from your Strategies and ask: what would tell us, within 30 days, whether this Strategy is working? The answer to that question is your Measure. If you can’t answer it, your Strategy isn’t specific enough yet.
The whole session should take three to four hours maximum. If it’s taking longer, you’re probably arguing about the Objective — which means you skipped the most important step.
What If You Don’t Know Your Objective Yet?
This is the real test.
OGSM’s entire structure hangs on the Objective. Everything else — Goals, Strategies, Measures — is in service of that one sentence. If you can’t write a clear Objective that your co-founders agree on, you’re not ready for OGSM yet.
And that’s not a failure. It’s useful information.
If you and your co-founder spend 45 minutes trying to write the Objective and can’t agree, you’ve just uncovered a misalignment that would have derailed any planning process. The OGSM template has done its job without you completing it.
Common pre-PMF blockers to a clear Objective:
- Disagreement about whether you’re targeting enterprises or SMEs
- Uncertainty about whether you’re selling a product or a service
- No shared view of the time horizon you’re planning against
- An Objective that’s really a Goal (“grow to 100 customers”) rather than a directional statement (“become the default compliance tool for UK professional services firms”)
That last one trips up a lot of founding teams. An Objective describes a position — where you want to be in the market, and for whom. A Goal describes a result — what you will achieve by a specific date. If your Objective has a number in it, it’s probably a Goal. For worked examples of how to write a strong OGSM Objective at different stages, see OGSM Objectives Examples.
If you’re still stuck, don’t force the OGSM. Work on the Objective first — even if that means a half-day offsite with your co-founders before you open the template.
What’s the Alternative at the Very Earliest Stage?
If your team is fewer than five people, you’ve spoken to fewer than twenty potential customers, and you’re still testing your core value hypothesis — you might not need OGSM at all yet.
Two simpler tools worth trying first:
A one-pager. One sentence on the problem you’re solving, one sentence on the customer you’re solving it for, one sentence on your hypothesis about the solution, and three bullet points on what you’ll do in the next 30 days to test it. Fits in Notion. Can be updated in five minutes. Does not require a planning process.
A hypothesis map. A simple visual structure: your assumption (customers in segment X will pay for Y to solve Z), the experiments you’re running to test it, and what you’ll conclude from each outcome. This is close enough to strategic planning for the very early stage without the overhead of a full OGSM structure.
Neither of these replaces OGSM. They’re pre-OGSM — the planning work you do before you have enough signal to build a real strategy. Think of them as the foundation you lay so that, when you do write your first OGSM, it’s grounded in real customer understanding rather than founder assumptions.
When Should You Graduate to a Full OGSM?
Watch for three signals:
1. A validated Objective. You know who your customer is, what job they’re hiring your product to do, and you have paying customers (not just pilots) who confirm it. Your Objective is no longer a hypothesis — it’s a direction the business has already started moving in.
2. Stable KPIs. Your core metrics aren’t changing every sprint. You’ve settled on the two or three numbers that actually tell you whether the business is working — churn, CAC payback, NRR, whatever fits your model. Stable Measures are the prerequisite for a meaningful Measures cascade. If your definition of a “good week” changes month to month, you’re not there yet.
3. A team that needs alignment. If it’s two co-founders and a contractor, informal alignment is probably fine. Once you’re hiring fast enough that people are making decisions without full context, OGSM starts earning its overhead. The first sign is usually when you realise two team members have conflicting assumptions about the strategy — and neither of them is wrong, they just never compared notes.
Once you hit those three signals, you’re ready for the full version — Goals that cascade into team-level goals, Measures for each Strategy, and a quarterly planning process that involves the whole leadership team. For a detailed guide to what that looks like at the 20–100 person stage, see Is OGSM Right for Your Scale-Up?.
OGSM is a focused tool. Used at the pre-PMF stage, it works best when it’s small, honest about uncertainty, and reviewed often. The goal isn’t to have a perfect strategy. It’s to have a shared bet — one that everyone on the founding team can recite from memory and hold each other accountable to.
Rock on.
