Strategist

Most strategy documents bury the recommendation on page 12. This track teaches you to write like a consultant—lead with the answer, back it up, get decisions made.

5 levels 6-10 weeks artifact: Executive-ready strategic brief

Demonstrated, not asserted

  • Blueprint install Its strategy-document stages — charter, prescription, strategy summary — are consulting-grade docs generated with an agent, publicly inspectable on its live self-demo. npx @nino-chavez-labs/blueprint-cli init verified 2026-07-15

Who this is for

This path is for you if

  • ·You advise clients or stakeholders on strategy
  • ·You write for executives who need to make decisions
  • ·You want to communicate recommendations clearly and persuasively
  • ·You come from consulting, advisory, or leadership roles

Probably not if

  • ·You're building software, not advising on it (that's the Builder track)
  • ·You need technical architecture documentation (that is the Architect track)
  • ·You're exploring AI for self-understanding (that is the Explorer track)
  • ·You prefer showing data without recommending action

The Consultant Voice

Strategic writing isn't about being right — it's about being clear enough to be useful. Don't write "There are several options to consider, each with various trade-offs..."; write "We recommend Option B. Here's why, and here's what it costs." Your job is to synthesize complexity into actionable recommendations — not to transfer the complexity to your reader.

The levels

0 Learn the Consultant Voice 1-2 days

Understand how consultants write differently than engineers or academics.

Voice patterns to learn

  • BLUF — Bottom Line Up Front: lead with the recommendation
  • Options + Recommendation — present choices, then advocate for one
  • So What? — every data point needs an implication
  • Confident Uncertainty — "Based on X, we recommend Y," not "maybe try Y?"
  • Structured Assertions — numbered lists, clear hierarchy, scannable

Anti-patterns to avoid

  • ·Hedging without a position ("There are many options...")
  • ·Data dumps without synthesis
  • ·Academic distance ("Research suggests...")
  • ·Burying the recommendation at the end

Where the agent does the work

  • Register check — the agent drafts, then a reviewer pass flags hedging, academic distance, and buried recommendations against the methodology's voice rules before the doc ships
  • What stays yours — the position. The agent enforces the voice; you decide what the doc argues. Blueprint runs reviewer agents over every generated doc for exactly this gate

Checkpoints

  • ·Read 2-3 consulting POVs or strategy docs
  • ·Identify which patterns they use
  • ·Note what feels different from technical writing

Done when — You can identify 5 voice patterns in a sample POV

1 Write Your First POV 1-2 weeks

Produce a 2,000 word point-of-view document with clear recommendations.

POV structure

  • Executive Summary — 200-300 words: the entire argument in miniature
  • Context & Problem — what triggered this? why does it matter?
  • Options Analysis — 2-3 approaches with trade-offs
  • Recommendation — what you advise and why
  • Next Steps — specific, actionable, time-bound

Requirements

  • ·Pick a real problem (your company, a client, a domain you know)
  • ·Have a genuine opinion about what should be done
  • ·Be willing to be wrong — POVs are stakes in the ground

Where the agent does the work

  • Draft from a corpus, not a blank page — the agent assembles a research corpus first, then drafts the doc from it; Blueprint's Stage 1 research feeds the Stage 2 charter and prescription so the first draft starts from evidence
  • What stays yours — the opinion. The agent gathers and drafts; you own the stake in the ground it is arguing for

Checkpoints

  • ·2,000+ word document with all 5 sections
  • ·Clear recommendation (not "it depends")
  • ·Someone unfamiliar with the topic can understand your position

Done when — You have a POV someone could act on without asking you clarifying questions

2 Cross-Domain Pattern Recognition 2-3 weeks

Draw insights from multiple industries to strengthen your arguments.

Techniques

  • Analogical Reasoning — "This is like when X industry faced Y..."
  • Pattern Extraction — identify the abstract principle, apply to a new context
  • Counter-Example — show where the pattern broke down and why

Where to find patterns

  • ·Industry reports (Gartner, Forrester, McKinsey)
  • ·Case studies from adjacent domains
  • ·Historical precedents (tech history, business history)
  • ·Your own past projects (if you can abstract the pattern)

Where the agent does the work

  • The scan is generated — the agent runs the cross-context pass; Blueprint's research stage produces a competitive analysis and market comparables, so the patterns you cite come from an assembled scan
  • What stays yours — relevance. The agent surfaces the analogies; you judge which ones add credibility and which are decoration

Checkpoints

  • ·Write a POV that references 3 different industries/contexts
  • ·Each reference adds credibility (not just decoration)
  • ·You can explain why each analogy is relevant

Done when — Your POVs reference patterns from 3+ different contexts

3 Strategic Briefs with Options 2-3 weeks

Present multiple strategic options with clear trade-off analysis.

Strategic brief structure

  • Situation — what's happening? what's at stake?
  • Options — 3 distinct approaches (not variations of one)
  • Analysis — trade-off matrix across key dimensions
  • Recommendation — which option and why
  • Risks & Mitigations — what could go wrong with your recommendation

Trade-off dimensions

  • ·Cost (implementation + ongoing)
  • ·Timeline (time to value)
  • ·Risk (technical, organizational, market)
  • ·Capability required (skills, resources)
  • ·Strategic fit (alignment with direction)

Where the agent does the work

  • Options table — the agent fills benefit / trade-off / risk across your dimensions; Blueprint's prescription stage emits prescription items carrying those trade-offs
  • Risk register — the agent lists each recommendation's riskiest assumptions and the evidence class behind each; Blueprint's docs stage emits exactly this as a validation script
  • What stays yours — the decision. Options must be genuinely different (not "do it fast" vs "do it slow"); the agent fills the matrix, you pick the row

Checkpoints

  • ·Brief with 3 genuinely different options
  • ·Trade-off matrix covering 4+ dimensions
  • ·Clear recommendation with risk acknowledgment
  • ·Decision-maker can choose without additional research

Done when — You have a brief with options matrix that a decision-maker could use

4 Executive Communication 3+ weeks

Write for board-level audiences who have 5 minutes and high stakes.

Executive communication principles

  • Pyramid Principle — start with the conclusion, then supporting points, then details
  • One Page Rule — if they read only one page, they get the full picture
  • Appendix Depth — details exist but don't interrupt the main argument
  • Visual Hierarchy — scanning should reveal structure and priority

The executive package

  • One-Pager — the entire recommendation on one page
  • Executive Summary — 2-3 page expansion with key evidence
  • Full Brief — the complete analysis (10-20 pages)
  • Appendices — data, methodology, detailed options

Where the agent does the work

  • Layered in one pass — the agent generates the package at multiple depths; Blueprint's charter is the one-page executive read while its prescription and strategy summary carry the full analysis and appendix depth
  • The pyramid holds — the summary derives from the same source as the detail rather than being written separately, so the one-pager cannot contradict the full brief. All of it is inspectable on the live self-demo

Checkpoints

  • ·Executive package with all 4 components
  • ·One-pager is self-sufficient
  • ·Full brief adds depth without contradicting the summary
  • ·Someone at C-level could make a decision from this

Done when — You have an executive package (summary + appendix) that works at multiple depths

Start at Level 0 npx @nino-chavez-labs/blueprint-cli init

Tool links and level references live in a dated data file checked by the link sensor on every build — this page can't silently point at a moved doc or a dead demo.