Frequently Asked Questions About Grapevine Strategy Builder Framework
23 answers covering everything from basics to advanced usage.
// Basics
What exactly is the Strategy Research Sprint?
The Strategy Research Sprint is a time-boxed two-week research process. Week 1 covers external reality: 5 customer interviews, reviewing 3 loss or churned deals, a competitor teardown (direct competitors plus competitive alternatives), and identifying one market trend. Week 2 covers internal reality: a KPI review, an execution breakdown audit, and a tool and knowledge audit. The goal is patterns strong enough to make decisions — not becoming a market analyst.
What is the Decision Filter and how do I write one?
The Decision Filter is a single yes/no question derived from your primary constraint that any team member can apply to any new idea or request. Example: 'Does this directly reduce the dependency on one person manually holding execution together?' Write it once you've picked your primary constraint. If a new opportunity fails the filter, it's noise. If it passes, it earns attention — but not automatic execution.
What is a competitive alternative and why does it matter?
A competitive alternative is a competitor that isn't a company or tool but a behavior or workaround — spreadsheets, pen and paper, or an internally built process. Drawn from 'Crossing the Chasm,' it matters because your real competition is often the status quo, not another vendor. Your teardown must document both direct competitors and these alternatives, including their positioning and who they target.
Who is the 'glue holder' in this framework?
The glue holder is the person or small group who manually pieces together information, tools, and coordination to keep operations running. When this person becomes the system rather than a durable structure, the company is at risk. Identifying the glue holder — as a customer persona or an internal role — is central to diagnosing your primary constraint and often reveals the painkiller problem worth solving.
// How To
How do I run the customer interviews if I only have a handful of users?
Interview whoever you have and supplement with your target persona. If you have no customers, use AI to mine Reddit, LinkedIn, G2, Capterra, Clutch, and X for patterns in that persona's complaints and switching behavior. Focus questions on what people struggle with, what they pay for, and what makes them switch — you're hunting for repeated patterns, not statistically perfect samples.
How do I write a diagnosis that isn't just optimistic spin?
Answer five questions in writing using your sprint outputs — and write reality, not goals: what's changing in your market, what customers consistently struggle with or switch for, where you win and lose given constraints, what competitors do that actually matters, and where execution breaks internally. Be uncomfortable. If the diagnosis feels comfortable, it's probably biased. Discomfort is the signal you're seeing reality clearly.
How do I run a premortem for my strategy?
Assume the strategy has already failed, then write down the most likely reasons — specifically and honestly (e.g. 'built features before getting customers,' 'didn't segment to a specific ICP,' 'vitamin not painkiller'). Pair each failure mode with one mitigation action. It's not pessimism; it's a stress test that prepares your team for the failure modes before they appear.
How do I write a strategic narrative people can actually remember?
Cover five elements in sequence: what changed and why now, what you believe (the thesis), what you're focusing on (pillars in plain language), what you're excluding (from the No List), and what this means for the team's daily work. Keep it short enough that any team member can repeat it from memory. If they can't repeat it, rewrite it — that's the test.
How do I roll out the strategy so it doesn't die after launch?
Execute rollout in three layers: share the narrative async (video plus one-pager) with a live Q&A; have each function cascade the pillars into their own direction feeding OKRs; and lock a cadence of weekly reinforcement, monthly reviews against success metrics, and quarterly resets. Schedule the cadence before launch — if it isn't on calendars, it won't happen.
// Troubleshooting
Why does the framework insist on time-boxing research to two weeks?
Because research becomes a never-ending rabbit hole, especially with AI tools that can generate infinite material. The goal isn't to become a market analyst — it's to find patterns strong enough to make decisions. Two weeks forces you to commit: Week 1 external, Week 2 internal. Analysis paralysis kills more strategies than imperfect data does.
My No List feels too easy to write. What's wrong?
If saying no to your list items feels easy, they weren't real temptations. A good No List should feel slightly uncomfortable because it excludes attractive opportunities that fall outside your constraint boundary. Revisit tempting bets — the profitable side project, the adjacent market, the buzzy feature request — and put those on the list. Involve your team so their buy-in prevents future drift.
I ended up with seven pillars. How do I cut down?
More than five pillars means you don't have a strategy — you have a wish list. Test each pillar against two questions: does it respond directly to the diagnosis, and does it work within your primary constraint? Merge overlapping ones and cut anything that's really a project or task. The framework is a focus game: one trend, one constraint, three to five pillars.
What if I realize my product is a vitamin, not a painkiller?
That's a critical finding — no strategy saves a vitamin. Return to your diagnosis and customer research to find a painkiller problem for a specific person or industry: something happening now with real, immediate consequences that creates urgency. You may need to narrow your beachhead to a segment where the pain is acute. Building strategy on a vitamin misaligns everything downstream.
My team can't repeat the strategy back to me. What do I do?
Rewrite the narrative — that's the framework's explicit rule. If people can't summarize it from memory, it won't drive daily decisions. Simplify to the five narrative elements, cut jargon, and make each pillar explainable without the document. Test by asking a team member to explain the strategy cold. Repeatability is the operational test of whether a strategy is real.
// Comparisons
How does this framework compare to OKRs?
OKRs are a goal-setting and execution layer; this framework is the strategy layer that comes first. Strategy defines the diagnosis, primary constraint, pillars, and tradeoffs; OKRs then translate those pillars into measurable objectives during planning. Setting OKRs without strategy produces well-tracked goals with no foundation. In this framework, the cascade step is exactly where pillars flow into OKRs.
How does this compare to a generic annual planning offsite?
Generic offsites usually start with goals and a long priority list, skipping diagnosis and tradeoffs, so momentum fades within weeks. This framework starts with honest diagnosis, forces one primary constraint and a No List, stress-tests with a premortem, and installs a cadence. The difference is enforced focus and constraints — an offsite generates excitement, this framework generates choices that survive contact with reality.
How is diagnosis different from a SWOT analysis?
SWOT is a static grid that often lists everything without forcing conclusions. Diagnosis in this framework is a written articulation of current reality across market, customer, and company — built from a research sprint — that deliberately precedes goal-setting and drives toward one primary constraint. It's designed to be uncomfortable and decisive, not a comprehensive but inert inventory of strengths and weaknesses.
// Advanced
Should a solo founder use the full framework or a lighter version?
Solo founders should use the full framework but lean on AI for research where they lack customers or KPIs. The steps that matter most are diagnosis, primary constraint, and the No List — because solo founders are most prone to chasing shiny opportunities. You can compress the rollout (no cascade), but keep the narrative and personal cadence so the strategy actually holds.
How do I set success metrics if I have no baseline data?
Use AI to find industry benchmarks for your stage and category, validate them manually before using them, and note explicitly that you're setting a baseline. Then define success across four dimensions: revenue outcome (a specific quantitative target), customer outcome, product outcome (the 'aha' wedge proving you're a painkiller), and operational outcome (systems that don't exist today). Refine targets after your first review cycle.
What is a beachhead and how does it fit the strategy?
A beachhead, from 'Crossing the Chasm,' is the single narrowly defined problem, persona, or market segment you focus on first rather than spreading across use cases. It fits directly into pillar selection and the No List: you commit to the beachhead and explicitly exclude other segments. Expansion is earned from the beachhead, not assumed. Choosing one is how you avoid spray-and-pray targeting.
How do I use the Decision Filter mid-quarter when new opportunities appear?
Apply the filter as a yes/no gate before any discussion of effort or excitement. Ask whether the opportunity addresses your primary constraint. A no means it's noise, regardless of how attractive it looks. A yes means it earns attention — then evaluate cost, fit with pillars, and whether it conflicts with the No List. The filter protects focus between the bigger quarterly resets.
Can distributed and remote teams use this framework effectively?
Yes — it's built with distributed teams in mind. The rollout uses async video plus a one-pager followed by a live Q&A, and the cascade lets each function translate pillars independently. The narrative-people-can-repeat rule matters even more remotely, since you can't rely on hallway reinforcement. Lock the weekly, monthly, and quarterly cadence into calendars before launch so time zones don't erode it.
How often should I reset the strategy after building it?
Commit to your chosen time horizon (recommended: 12 months) rather than a rolling horizon, but review continuously. Reinforce weekly, review against success metrics monthly, and run a full reset quarterly. The premortem findings guide what to watch. A full rebuild is warranted at horizon end, after a pivot, or before a fundraise — not every time urgency tempts you off course.