A founding team uses AI to help build their annual strategic plan. They provide their mission, their revenue goals, and a list of priorities they have discussed. The output is a well-formatted plan: objectives, key results, strategic pillars, quarterly milestones. Everything important to the business appears somewhere in the document. When they start Q1, they realize the plan does not help them make any of the decisions that actually come up: which of two product opportunities to pursue first, whether to hire ahead of revenue or wait for a trigger, how to allocate limited engineering capacity between new features and technical debt. The plan named their goals. It did not make choices.
A plan that does not say no to anything is a list of hopes, not a strategy.
Why Strategic Plans Without Trade-offs Don’t Guide Decisions
A strategic plan has one practical job: to help the team make better decisions faster by resolving trade-offs in advance. The team that has agreed, in planning, that technical foundation takes priority over new feature development this half — and has documented why — makes the resource allocation decision in five minutes when it comes up. The team whose plan includes both as equal priorities argues about it every time and reaches an inconsistent set of outcomes across the year.
AI produces plans that include everything important because everything on the input list is important to the team that provided it. Resolving the trade-offs — deciding that this priority ranks above that one, and articulating specifically why — is the hard intellectual work of planning that the team has to do before the plan can be useful. A brief that contains only goals and priorities asks AI to organize them. A brief that contains a set of resolved trade-offs asks AI to document and structure a strategy the team has actually made.
What a Strategic Plan Brief Needs to Contain
A useful strategic planning brief requires the team to do the hardest work before AI is involved: identifying the core tension and resolving it.
Every company at any stage has one fundamental strategic tension — the trade-off that, if unresolved, will cause the most inconsistency in decision-making. For an early-stage company, it is often growth versus sustainability. For a scaling company, it might be breadth of product versus depth of solution for the core customer. For a mature company, it might be defend the core versus invest in the next category. The planning brief should name this tension explicitly and document how the team has resolved it for the planning period.
The brief should also contain the constraints that are real and non-negotiable for the period: budget, headcount, external commitments, regulatory factors. Plans built without constraints are aspirational documents. Plans built within real constraints make choices that are actually executable.
What a Properly Briefed Strategic Plan Request Looks Like
Role: You are helping a 25-person SaaS startup structure an annual
strategic plan for the next fiscal year.
Company context: $4M ARR, growing 60% year-over-year, B2B focus,
two product lines (core product and a newer analytics module launched
9 months ago that is gaining traction but is not yet fully built out).
The core strategic tension we have resolved: We debated whether to
invest this year in accelerating growth (more sales, more marketing,
expand geographically) or in deepening the product for existing
customers (finish the analytics module, improve onboarding, reduce
churn). We have decided: product depth this year. Rationale: our
NPS is 61, we have an 18% annual churn rate we believe is product-driven,
and we do not want to pour growth investment into a leaky bucket.
Growth acceleration moves to next year once churn is under 10%.
What this means for resource allocation: Engineering prioritizes
analytics module completion (Q1-Q2) and onboarding redesign (Q3).
Sales continues at current pace — no new headcount. Marketing
focus shifts to retention content and case studies rather than
top-of-funnel acquisition.
Real constraints: Budget for 2 additional engineering hires only.
No geographic expansion this year. Product team has committed to
shipping the analytics module by end of Q2 — this is a hard
commitment to three enterprise customers.
Build a strategic plan structure that reflects these choices —
not one that tries to include everything. Where we have made
trade-offs, the plan should reflect what we chose and what we
explicitly deprioritized, so we can refer back to it when
those debates come up again mid-year.The plan from this brief reflects choices. When the debate about expanding the sales team comes up in March, the team has a documented answer: not this year, here is why, here is what we prioritized instead.
A Strategy Is a Set of Choices, Not a Set of Goals
Goals tell you where you want to go. A strategy tells you how you are getting there given real constraints and trade-offs. The brief that contains resolved trade-offs and explicit deprioritizations produces a plan that guides decisions. The brief that contains goals and priorities produces an organized aspiration document that cannot answer the hard questions the team will actually face. The hard work of strategy — deciding what you are not doing this year — belongs in the brief before AI builds the plan around it.
For leadership teams doing annual or quarterly planning, Briefing Fox structures the brief so the core strategic tension and resolved trade-offs are captured before any plan framework is generated.
Before Your Next Planning Cycle
Before asking AI to help structure any strategic plan, write down the one core trade-off your team has been arguing about and how you have resolved it for this period. That resolution is the brief. The plan that actually guides your decisions is built around a choice that was made, not a list of everything that matters.
Try Briefing Fox free at www.briefingfox.com.
A goals list says what you want to achieve. A strategic plan says what you’re choosing to do and what you’re choosing not to do, given real constraints and trade-offs. A plan that doesn’t say no to anything isn’t a strategy — it’s a wish list.
Because the hard trade-offs were never resolved in the planning process. When two priorities conflict in Q2, a plan that listed both without ranking them leaves the team arguing rather than deciding. The plan’s value is in the choices made before the year starts.
The core strategic tension the team has been debating and how it’s been resolved for this period, the real non-negotiable constraints, and explicitly what is being deprioritized and why. Plans built on these inputs reflect actual choices rather than aspirations.
Quarterly is a common cadence for checking whether the priorities still make sense given what’s been learned. The plan shouldn’t change every quarter, but the assumptions behind it should be tested against new information. Brief AI for a quarterly review by including what’s changed since the plan was built and whether the core trade-offs still hold.