Page 27 · Module 01, Think Like a Strategist · this screen continues that page

All 108 frameworks
1.2BeginnerModule 01 · Think Like a Strategist

The Context Stack

Your AI outputs feel shallow or off-target even when you've explained the situation. The AI

The prompt

Copy & paste ready
1.2The Context Stack
Situation : [What is happening - current challenge or goal] Background : [Industry, team size, stage, audience, product, region - whatever is relevant] Constraints : [Time, budget, tone, audience level, things to avoid] Output format : [List / paragraph / table / email draft] Now : [YOUR ACTUAL QUESTION OR REQUEST] AI Output Feels Shallow: Missing Context Recurring Tasks No built-in template Reusing Context functionality Stack Requires manual pasting Non-Obvious each time Constraints AI misses important limitations Imprecise Context Stack Leads to imprecise AI output No AI Memory Every prompt starts from zero
LabelsReplace these

LabelsReplace these

Pro tip, from the book

Save your most-used context stacks as text snippets. Paste them at the start of any AI session. This single habit cuts prompt iteration time by half.

Who should run this prompt

Module role profile

Who should reason through this problem? The quality of your thinking is shaped by whose lens you borrow. A strategist and a risk analyst look at the same problem and see completely different things — both useful, both necessary. Before you prompt, choose who you need in the room. These profiles give you six internal perspectives and four outside views that challenge your assumptions before you commit to them.

The roles below are who the book suggests running this prompt — this lesson’s prompt doesn’t open with a single swappable role clause, so pick one and adapt the prompt’s own wording yourself.

Internal rolesThink from inside the organisation
Chief Strategy OfficerLong-term position, trade-offs, competitive moatSetting 3-year direction or evaluating a major pivot
McKinsey Senior PartnerMECE structure, evidence-first, no fluffStructuring a complex problem or board presentation
Product Strategy DirectorMarket timing, feature bets, customer signalDeciding what to build next and why
Strategy ManagerTranslating direction into quarterly prioritiesBreaking a big goal into executable 90-day plans
Research AnalystData quality, pattern recognition, no assumptionsValidating a hypothesis before acting on it
First Principles CoachStripping assumptions, rebuilding from fundamentalsWhen every solution feels like a variation of the same thing
Outside perspectivesChallenge your blind spots
Sceptical InvestorFinds the hole in every planBefore pitching or committing resources
Military Decision AnalystSpeed under uncertainty, clear action biasIn fast-moving situations with incomplete data
Devil's AdvocateArgues the opposite as hard as possibleWhen your team agrees too quickly
Socratic FacilitatorNever answers — asks until you find it yourselfWhen you need to think, not just receive an answer

◆◆◆◆◆ → ◆ seniority, board level down to specialist outside the organisation

How to make any role sharper

  1. Add years of experience: "...with 15 years in enterprise SaaS" produces different depth than just the title.
  2. Add what they care most about: "You care most about [X]" shapes every word of the output.
  3. Add their communication style: "Be direct. Flag risks first. No jargon." changes the tone entirely.
See also: 1.3 Role Prompting - The Expert Chair

Use this when

The problem it solves

is missing crucial background that seems obvious to you.

How the framework works

From the printed page

AI has no memory of who you are. Every prompt starts from zero. The Context Stack is a four-layer background brief: Situation (current state), Background (relevant history and details), Constraints (what limits apply), Output Format (exactly how you want the answer). The more precise your stack, the more precise the output. Constraints is the layer people forget most, which is why AI often suggests things you already know won't work. Background doesn't need to be exhaustive, just the two or three facts that would change the answer if left out. A reused context stack compounds in value across a session, since each new prompt inherits the setup instead of re-explaining it

The method, in four moves

Do these in order
1

Write your context stack before your actual question, treat it as setup.

2

Include industry, company stage, audience, and any non-obvious constraints.

3

Reuse the same context stack across a session by pasting it at the top.

4

For recurring tasks, save your context stack as a reusable template. Why AI gives generic answers and how to fix it Most people give AI context about what they want but not who they are, what they've already tried, or what a good result looks like. AI fills those gaps with assumptions and they're usually wrong. Stack all four layers before you prompt, not after you get a bad result.

Where the framework comes from

Prompt engineering best practice — adapted from AI workflow research, 2023

When this page changes, your copy of the book does not have to.

The book prints the framework. This page keeps it — and keeps the prompt current, because prompting technique moves faster than print does. When it moves, this page is rewritten and the code in your copy keeps pointing at it. No second edition, no replacement purchase, no account.

If something here looks wrong — a prompt that does not match its framework, a figure that reads oddly — tell Raphy. That correction reaches every printed copy at once.

Framework1.2 of 108
Printed onPages 2627
Prompt extracted18 Sept 2026
Costs to readNothing, no account

Copying is free. An account keeps them.

Nothing on this page is behind a login and nothing ever will be. Save any prompt to your own list, pick up on another device, and send a colleague a link with your name on it. No card, no trial, no paywall on the prompts themselves.

See how it works
Save this framework to your own list
Pick up where you left off on another device
Send a colleague a link with your name on it