Strategy Mode: Make Better Decisions
Strategy Mode is about analysis and decision-making. While Plan Mode organizes how to execute, Strategy Mode helps you decide what to do and why. It’s your thinking partner for choices that matter.
What Strategy Mode Is For
Strategy Mode excels at:
- Technology decisions: “Should we use PostgreSQL or MongoDB for this project?”
- Business choices: “Should we focus on new features or improving retention?”
- Architecture decisions: “Monolith or microservices for our new platform?”
- Career decisions: “Should I specialize in ML or stay as a generalist?”
- Investment decisions: “Is this tool worth the cost?”
- Problem framing: “What questions should I be asking about this situation?”
The common thread: weighing options, analyzing tradeoffs, and reaching justified conclusions.
Strategy vs. Other Modes
flowchart TD
A[Ask] --> |"Tell me about X"| B[Information]
C[Plan] --> |"How do I do X?"| D[Steps]
E[Strategy] --> |"Should I do X or Y?"| F[Recommendation]
G[Vision] --> |"What could be possible?"| H[Possibilities]- Ask Mode provides information (inputs to decisions)
- Plan Mode sequences actions (after decision is made)
- Strategy Mode analyzes options and recommends choices
- Vision Mode explores possibilities (before narrowing to options)
Strategy Mode sits between exploration and execution.
The Strategy Mode Framework
flowchart LR
A[Situation] --> B[Options]
B --> C[Analysis]
C --> D[Recommendation]
D --> E[Action Path]1. Situation
What’s the context? What decision needs to be made? What constraints exist?
2. Options
What are the alternatives? What could you choose?
3. Analysis
What are the pros and cons? What criteria matter most?
4. Recommendation
Given the analysis, what should you do?
5. Action Path
What are the immediate next steps?
Strategy Mode Patterns
The Decision Matrix Pattern
Evaluate multiple options against defined criteria.
Template:
Help me decide between [options].
Context: [situation and background]
Constraints: [limitations]
Priority criteria:
1. [Most important factor]
2. [Second most important]
3. [Third most important]
For each option, analyze:
- Pros and cons
- How it scores on each criterion
- Hidden risks or benefits
Provide:
- Comparison summary (table format)
- Recommended choice
- Key factors driving the recommendation
- What would change the recommendationExample:
Help me decide between PostgreSQL and MongoDB for our new application.
Context: Building a B2B SaaS product for project management.
Will have users, projects, tasks, comments, and real-time collaboration.
Team has more SQL experience but is open to learning.
Constraints:
- Must scale to 100K users in 2 years
- Budget is limited (prefer managed services)
- Need good TypeScript integration
Priority criteria:
1. Data integrity and consistency (transactional operations important)
2. Developer productivity (time to ship)
3. Operational complexity at scale
For each option, analyze pros/cons and scoring.
Provide comparison table and clear recommendation.The Risk Assessment Pattern
Evaluate a proposed course of action.
Template:
Assess the risks of [proposed action].
Context: [situation and background]
Stakes: [what's at risk if this goes wrong]
Analyze:
- What could go wrong?
- How likely is each risk?
- What's the impact if it occurs?
- How can each risk be mitigated?
Provide:
- Risk matrix (likelihood vs. impact)
- Top 3 risks to watch
- Mitigation strategy for each
- Go/no-go recommendationExample:
Assess the risks of migrating our production database from MySQL to PostgreSQL.
Context:
- 200GB database
- Supports live SaaS application with 10K users
- Team has limited PostgreSQL experience
- Planned for next month
Stakes: Extended downtime could lose major customers
Analyze risks with likelihood and impact.
Provide top risks, mitigations, and whether we should proceed.The Opportunity Analysis Pattern
Evaluate whether to pursue something new.
Template:
Analyze this opportunity: [opportunity description]
Context: [current situation]
Investment required: [what it would take]
Alternative uses: [what else could you do with those resources]
Analyze:
- Potential upside
- Required investment
- Probability of success
- Opportunity cost
- Alignment with goals
Provide:
- Opportunity score (1-10) with justification
- Key assumptions that drive the score
- What would need to be true for this to succeed
- Recommendation: pursue / skip / investigate moreExample:
Analyze this opportunity: Expanding our product to the European market.
Context:
- US-only SaaS product with $2M ARR
- Strong product-market fit domestically
- Some inbound interest from EU companies
Investment required:
- GDPR compliance ($50K + ongoing)
- EU-based support (hire 2 people)
- Localization (3 languages)
Alternative uses: Could invest same resources in new product features
Analyze upside, investment, and opportunity cost.
Should we pursue this now?The Problem Framing Pattern
Clarify what problem you’re actually solving.
Template:
Help me frame this problem correctly: [initial problem statement]
Context: [background]
Symptoms: [what you're observing]
Assumptions: [what you currently believe]
Help me:
- Distinguish symptoms from root causes
- Identify the real problem to solve
- Surface hidden assumptions
- Reframe the problem if needed
- Generate better questions to askExample:
Help me frame this problem: "Our users aren't using our new feature"
Context:
- Launched new collaboration feature 2 months ago
- Adoption is 5% (expected 30%)
- Feature works as designed, no major bugs
Symptoms:
- Low usage numbers
- Few support questions about it
- Sales mentions it but doesn't seem to close deals
Assumptions:
- Users would want this if they knew about it
- The problem the feature solves is real
Help me identify the real problem and what questions to ask.The Tradeoff Analysis Pattern
Understand the costs of different choices.
Template:
Analyze the tradeoffs between [approach A] and [approach B].
Context: [situation]
Goal: [what you're trying to achieve]
For each approach:
- What do you gain?
- What do you sacrifice?
- Under what conditions is it the better choice?
Provide:
- Clear comparison of gains and sacrifices
- Decision criteria: "Choose A if... Choose B if..."
- What you'd need to know to decideExample:
Analyze the tradeoffs between building in-house vs. buying a solution.
Context: Need email marketing automation for our SaaS
Goal: Send personalized email sequences based on user behavior
For "build in-house":
- Full control, custom fit
- Engineering time, ongoing maintenance
For "buy" (e.g., Customer.io, Sendgrid):
- Quick start, less engineering
- Monthly cost, less customization
When is each the better choice?Crafting Effective Strategy Prompts
Provide Rich Context
The quality of strategic advice depends entirely on context:
Not: "Should I use AWS or GCP?"
Better: "Should I use AWS or GCP for a startup building a
real-time data platform? We're a 3-person team with AWS experience.
Primary needs: managed Kubernetes, real-time streaming,
managed PostgreSQL. Budget: <$5K/month initially, scaling
to $50K/month at full capacity."Define Your Criteria
What matters most to you? Saying it explicitly improves recommendations:
Priority criteria:
1. Time to market (most important)
2. Total cost over 2 years
3. Team learning curve
4. Long-term scalabilityAsk for Reasoning
Don’t just ask for answers—ask for the logic:
Provide:
- Your recommendation
- The key factors driving it
- What would change your recommendation
- What assumptions you're makingSurface Blind Spots
Explicitly ask what you might be missing:
Also identify:
- Questions I should be asking but haven't
- Risks I might be underestimating
- Assumptions I should validateCommon Strategy Mode Mistakes
1. Too Little Context
Poor: “Which is better, React or Vue?” Better: “For our team (3 devs, strong Angular background), building an enterprise dashboard with complex data grids and charts, which is better: React or Vue? We prioritize long-term maintainability.”
2. Undefined Criteria
Without knowing what matters, any answer is correct. Define priorities.
3. Premature Strategy
If you haven’t explored possibilities (Vision) or understood options (Ask), strategic analysis may be premature.
4. Analysis Paralysis
Strategy Mode can produce endless analysis. Set a decision deadline:
I need to decide by Friday. Given that constraint,
what's most important to analyze?5. Ignoring “Good Enough”
Sometimes any reasonable option works. Ask:
Are these options meaningfully different, or would any of them work?
What's the cost of choosing "wrong"?Practice Exercise
Create three Strategy Mode prompts for decisions you’re facing:
1. Technology/Tool Decision Identify a technical decision you need to make. Write a prompt that includes:
- Full context about your situation
- The specific options you’re considering
- Your priority criteria
- Request for comparison and recommendation
2. Business/Career Decision Identify a non-technical decision. Write a prompt that includes:
- Your situation and goals
- Options on the table
- Constraints and tradeoffs you’re aware of
- Request for analysis and recommendation
3. Problem Framing Identify a problem you’re struggling with. Write a prompt that:
- Describes the symptoms you’re seeing
- States your current understanding
- Asks for help identifying root causes
- Requests better questions to ask
Review: Did you provide enough context? Define your criteria? Ask for reasoning?
Key Takeaways
- Strategy Mode analyzes options and recommends decisions
- Good strategy prompts include: situation, options, criteria, and request for reasoning
- Use patterns: Decision Matrix, Risk Assessment, Opportunity Analysis, Problem Framing, Tradeoff Analysis
- Rich context dramatically improves recommendation quality
- Ask for reasoning, not just answers
- Define decision criteria explicitly
- Avoid analysis paralysis—sometimes “good enough” is right
Next lesson: Vision Mode—exploring long-term possibilities and big-picture thinking.