# Strategy-to-Roadmap Cascade System — AI Context Brief (v5)

An AI Context Brief for standing up a recurring strategy-to-roadmap operating system — an annual strategic frame, quarterly WSJF rescoring, a weekly drift check, and a recalibration trigger rule — delivered as a single step-by-step implementation guide. Applicable to any team or function running a competing-priorities portfolio, not just technology teams.

v5 adds the corrected reference diagram below to the package — same prompt as v4, now paired with the System Summary visual as it should actually render: no stray unlabeled elements, and diagram text sized to match the surrounding body copy instead of reading as a shrunken afterthought.

```
You are helping me design and stand up a recurring Strategy-to-Roadmap
Cascade System for my organization — not a one-time roadmap document, but an
operating rhythm I'll actually run every quarter (and check on weekly). Don't
hand back a generic OKR philosophy essay or a set of disconnected worksheets —
deliver a single step-by-step implementation guide that tells me exactly how
to run this, not just what it is.

MY SITUATION — YOUR STRATEGIC INPUTS
Before asking me anything below, check whether I've attached reference
materials — a current project/initiative list, documentation on existing
systems, prior strategy decks, cascaded goals from the CEO/board/executive
team, or a general org profile. If I have, extract as much of the information
below as you can directly from those documents rather than making me retype
it, and tell me which fields came from my documents versus which you're
asking me directly, so I can correct anything misread. If a document only
covers part of what's needed, ask only for what's genuinely missing. If
something in a document conflicts with what I tell you directly, flag the
conflict and ask which is current — don't silently pick one. Don't assume an
uploaded document is exhaustive; if it only covers some initiatives or a
partial history, ask whether there's more before treating the picture as
complete.

Organization Profile
- Organization size: [employee count] / [team, division, or scope this system
  covers] — often in an org profile document, if attached.

Current State
- What exists today: [nothing formal / an annual roadmap that goes stale / a
  rough backlog with no scoring] — often answered by an existing project or
  initiative list or systems documentation, if attached.

Strategic Choices (do not invent these)
- Do you already have defined answers for Winning Aspiration, Where to Play,
  How to Win, Capabilities Needed, and Management Systems? Often already
  answered in a prior strategy deck or a cascaded goals document from the
  CEO, board, or executive team — check uploads first. If yes (from an upload
  or direct answer), give them to me as-is. If no, say so explicitly — don't
  let me guess at placeholder language for you. Instead, walk me through a
  structured working session to draft first-pass answers I can bring to my
  leadership team for confirmation.

Tier, Tools & Platform
- Tier or investment approach: [Lean — no new software spend / Mid-market —
  open to a modest new tool / Enterprise — have or can get budget for a
  dedicated platform]
- Systems already in place: [list what you actually have licensed or use today
  — check systems documentation, if attached]
- Platform for ongoing tracking: [name one if you have it — most support Excel
  or CSV import. If you don't name one, I'll build a working Excel workbook
  with live formulas instead.]

Reporting, Scale & Meeting Cadence
- Who this reports to or gets reviewed by: [CEO, board, steering committee, my
  own leadership team]
- Roughly how many competing initiatives are in play at once: [a number or
  range — check an attached project/initiative list first]
- Existing recurring meeting(s) this could attach to: [name one, or say none
  exists yet]

CONSTRAINTS
- Never recommend adopting a new platform. My goal is documents and steps that
  slot into whatever I already run, not a tool decision.
- Never invent my Strategic Choices. If I haven't given them to you or they
  aren't in what I uploaded, run the working-session exercise instead of
  filling the boxes in yourself.
- Match the review cadence to real bandwidth. If I can't credibly commit to a
  weekly check-in, tell me what I lose by going biweekly or monthly instead,
  and let me choose.
- If I haven't given you initiative-level cost/value data — directly or in an
  upload — don't invent scores. Ask me for the real initiatives and their
  rough business value, time-criticality, effort, and whether any carry a
  hard compliance, contractual, or vendor deadline, or mark those fields as
  placeholders I need to fill in.

DESIGN I NEED — DELIVERED AS ONE STEP-BY-STEP HTML IMPLEMENTATION GUIDE

1. Your Strategic Inputs — restate what I gave you (directly or from uploads)
   organized by category, at the top of the guide, noting the source of each,
   so I can confirm accuracy before reading the rest.

2. Annual Strategic Frame — built from my actual Strategic Choices (direct
   answer or upload), or from the working-session exercise if neither existed.
   Include one short paragraph on when and how to operationalize this: who
   reviews it, how often, and what happens if a box is contested.

3. Quarterly Rescoring Worksheet — WSJF (Cost of Delay ÷ Job Size, where Cost
   of Delay = Business Value + Time Criticality + Risk Reduction/Opportunity
   Enablement), plus a Must-Do flag column for hard compliance/contractual/
   vendor deadlines. Include step-by-step directions: who submits initiatives
   and by when, who scores them, and exactly how to load the result into the
   platform I named (or the live-formula Excel version if I didn't name one).

4. Weekly Drift Check — the check questions, plus directions on how to use
   them: attach to an existing recurring meeting or suggest creating one.
   Include a week-over-week tracking template — a running grid, not a
   single-use checklist.

5. Recalibration Trigger Rule (not "re-cascade") — restate the trigger
   conditions as a standing question on the same meeting agenda as the drift
   check, then give an explicit recalibration procedure as a decision path:
   which conditions only require updating the Quarterly Rescoring Worksheet,
   versus which require rerunning this brief and regenerating the Annual
   Strategic Frame — and be explicit about who does which step.

6. System Summary — a recap of every template and tool this guide produced,
   plus a simple diagram showing how they connect across the annual/quarterly/
   weekly cycle, including where each recalibration path feeds back in. Keep
   every element on the diagram tied to something labeled — no decorative
   marks (dimension ticks, rules, brackets) that don't carry a number or a
   name — and size the diagram's text close to the surrounding body copy so
   it reads as content, not as a shrunken thumbnail.

WHAT GOOD OUTPUT LOOKS LIKE
One HTML guide I could hand to my team and follow start to finish without
another conversation. The Strategic Frame reflects my real strategic choices
— from what I typed or what I uploaded — or an honest working session, never
invented language. The weekly section includes something I can fill in week
after week. The recalibration section tells me exactly what to do, in what
order. The closing section is a recap and a diagram, not a product
recommendation.
```

*What good output looks like: an HTML guide styled with your own brand system, containing every template plus operational instructions for running it — not a text explanation of what the system is.*

---

## Reference Diagram — System Summary Visual (Corrected)

The System Summary diagram from the populated example, as it should actually render: the annual → quarterly → weekly cascade in black with right-angle connectors, the two recalibration paths in dashed teal, and no unlabeled decoration. Text sizes are set so the primary labels (Strategic Frame, WSJF Rescoring Worksheet, Drift Check + Recalibration Question) render close to a 16px body-copy size rather than reading as a smaller, separate visual register. Drop this in directly wherever the guide's `<div class="diagram">` block goes.

```html
<div class="diagram">
<svg viewBox="0 0 700 460" xmlns="http://www.w3.org/2000/svg" width="100%" style="max-width:740px;">
  <defs>
    <marker id="arrowB" markerWidth="9" markerHeight="9" refX="7" refY="3" orient="auto" markerUnits="strokeWidth">
      <path d="M0,0 L0,6 L8,3 z" fill="#000000"/>
    </marker>
    <marker id="arrowA" markerWidth="9" markerHeight="9" refX="7" refY="3" orient="auto" markerUnits="strokeWidth">
      <path d="M0,0 L0,6 L8,3 z" fill="#0A6556"/>
    </marker>
  </defs>

  <!-- Annual box -->
  <rect x="220" y="20" width="260" height="60" fill="#ffffff" stroke="#000000" stroke-width="1.5"/>
  <text x="350" y="42" text-anchor="middle" font-family="Poppins, sans-serif" font-size="14" letter-spacing="2" fill="#000">ANNUAL</text>
  <text x="350" y="60" text-anchor="middle" font-family="Georgia, serif" font-size="15" fill="#000">Strategic Frame</text>
  <text x="350" y="74" text-anchor="middle" font-family="Poppins, sans-serif" font-size="10" letter-spacing="1" fill="#7f7f7f">REVIEWED YEARLY</text>

  <line x1="350" y1="80" x2="350" y2="150" stroke="#000" stroke-width="1.5" marker-end="url(#arrowB)"/>

  <!-- Quarterly box -->
  <rect x="200" y="150" width="300" height="60" fill="#ffffff" stroke="#000000" stroke-width="1.5"/>
  <text x="350" y="172" text-anchor="middle" font-family="Poppins, sans-serif" font-size="14" letter-spacing="2" fill="#000">QUARTERLY</text>
  <text x="350" y="190" text-anchor="middle" font-family="Georgia, serif" font-size="15" fill="#000">WSJF Rescoring Worksheet</text>
  <text x="350" y="204" text-anchor="middle" font-family="Poppins, sans-serif" font-size="10" letter-spacing="1" fill="#7f7f7f">RESCORED EVERY QUARTER</text>

  <line x1="350" y1="210" x2="350" y2="280" stroke="#000" stroke-width="1.5" marker-end="url(#arrowB)"/>

  <!-- Weekly box -->
  <rect x="180" y="280" width="340" height="70" fill="#ffffff" stroke="#000000" stroke-width="1.5"/>
  <text x="350" y="304" text-anchor="middle" font-family="Poppins, sans-serif" font-size="14" letter-spacing="2" fill="#000">WEEKLY</text>
  <text x="350" y="322" text-anchor="middle" font-family="Georgia, serif" font-size="15" fill="#000">Drift Check + Recalibration Question</text>
  <text x="350" y="338" text-anchor="middle" font-family="Poppins, sans-serif" font-size="10" letter-spacing="1" fill="#7f7f7f">STANDING 15-MIN SYNC</text>

  <!-- Minor recalibration: right-angle, accent -->
  <path d="M520,300 L 600,300 L 600,180 L 500,180" fill="none" stroke="#0A6556" stroke-width="1.5" stroke-dasharray="5,4" marker-end="url(#arrowA)"/>
  <text x="606" y="240" font-family="Poppins, sans-serif" font-size="11" letter-spacing="1" fill="#0A6556" text-anchor="middle" transform="rotate(90 606,240)">MINOR RECALIBRATION</text>

  <!-- Major recalibration: right-angle, accent -->
  <path d="M180,300 L 90,300 L 90,50 L 218,50" fill="none" stroke="#0A6556" stroke-width="1.5" stroke-dasharray="5,4" marker-end="url(#arrowA)"/>
  <text x="70" y="175" font-family="Poppins, sans-serif" font-size="11" letter-spacing="1" fill="#0A6556" text-anchor="middle" transform="rotate(-90 70,175)">MAJOR — RERUN THE BRIEF</text>

  <text x="350" y="425" text-anchor="middle" font-family="Poppins, sans-serif" font-size="10" letter-spacing="0.5" fill="#7f7f7f">BLACK = CASCADE  ·  TEAL DASHED = RECALIBRATION FEEDBACK</text>
</svg>
</div>
```
