Why This Mode Exists
Most strategy projects start with too much confidence and too little clarity. Teams jump into competitive analysis or creative briefs without first establishing what they actually know versus what they're assuming.
The Context Dump exists to slow you down at exactly the right moment. It's the discipline of saying "let me make sure I understand the situation before I start analyzing it."
The problem with skipping context
When you skip structured context gathering, you end up with analysis built on unstated assumptions. The competitive audit focuses on the wrong competitors because nobody questioned the category definition. The brief solves a problem the client didn't actually have because nobody asked who wrote it and what they're accountable for.
Every piece of weak strategy work I've seen traces back to the same root cause: insufficient understanding of the situation, masked by premature sophistication in the analysis.
How It Works
Five areas of understanding
The Context Dump organizes information into five buckets: the brand (what they sell, how they position, internal beliefs), the category (definition, dynamics, key players), the competitive set (direct, indirect, substitute behaviors), historical context (what's been tried, what worked), and constraints (budget, timeline, sacred cows).
Gaps are findings
The most valuable output of a Context Dump isn't what you document — it's the open questions you surface. "We don't know who our indirect competitors are" is a strategic finding. "Nobody can articulate the current positioning" is a finding. These gaps tell you where the real work needs to happen.
Terminology matters
Strategy work is plagued by jargon that means different things to different people. When the client says "premium," do they mean price point, perception, or quality? When they say "millennials," do they mean 25-year-olds or 40-year-olds? The Context Dump flags ambiguous terminology so you're building on shared definitions, not false agreement.
When to Use This Standalone
Even outside the full WRKFLW sequence, a structured Context Dump is valuable at the start of any project. Use it to onboard a new team member, prepare for a client meeting, or simply organize your own thinking before diving into analysis.
The goal isn't comprehensiveness — it's clarity about what you know, what you don't, and what you're assuming.