Step 3: Build the Realignment Plan

Purpose

Using the gaps from Step 2, restructure the user's delivery schedule so their highest-value work arrives before the decisions it should inform. The output is a concrete, implementable delivery schedule — not theory.

Prerequisites

Steps 1 and 2 must be complete. Read both:

• outputs/decision-cadence-map.md
• outputs/delivery-timing-audit.md

Interview Questions

Prioritizing the Shifts

1. "Looking at the gaps, which 2-3 would change your client's experience of you the most if you closed them?"
2. "For each of those — what would it take to move your deliverable earlier? Is it a production change, a data dependency, or just a scheduling shift?"
3. "Are any of these shifts things you could do this week without changing your scope or your fee?"

Practical Constraints

1. "What stops you from delivering earlier right now? Data availability? Team capacity? Client expectations about when things land?"
2. "If you add or shift a deliverable, what would you stop doing or compress to make room? Every shift needs to fit within your current capacity."
3. "Does this client have any formal meetings or review cycles where your work should be on the table? Board meetings, partner meetings, quarterly reviews?"
4. "If you shifted your delivery timing, would you need to tell the client, or could you just start landing work earlier?"

The Anchor Deliverable

1. "If you could only shift ONE deliverable to land before ONE decision — the move that would most change how this client sees you — which would it be?"
2. "What would it look like if that deliverable arrived 5 days before the decision instead of 3 days after?"

Building the Realignment Plan

After the interview, build this deliverable:

# Decision-Driven Delivery Plan: [Client Name]

**Built:** [Date]
**Current Model:** Calendar-driven ([monthly/weekly/quarterly])
**Target Model:** Decision-driven (anchored to [client name]'s decision cycle)

## The Three Shifts

### Shift 1: [Highest-Impact Change]
**Decision:** [The decision this serves]
**Current timing:** [When the deliverable lands now]
**New timing:** [When it needs to land]
**What changes:** [Specific production/scheduling change]
**Effort to shift:** [Low/Medium/High]
**Client communication needed:** [Yes/No — and what to say if yes]

### Shift 2: [Second Priority]
**Decision:** [The decision this serves]
**Current timing:** [When the deliverable lands now]
**New timing:** [When it needs to land]
**What changes:** [Specific production/scheduling change]
**Effort to shift:** [Low/Medium/High]
**Client communication needed:** [Yes/No — and what to say if yes]

### Shift 3: [Third Priority]
**Decision:** [The decision this serves]
**Current timing:** [When the deliverable lands now]
**New timing:** [When it needs to land]
**What changes:** [Specific production/scheduling change]
**Effort to shift:** [Low/Medium/High]
**Client communication needed:** [Yes/No — and what to say if yes]

## Restructured Delivery Calendar

| Week | What You Deliver | Decision It Precedes | Landing Target |
|------|-----------------|---------------------|----------------|
| [Week/Date] | [Deliverable] | [Decision] | [X days before] |
| [Week/Date] | [Deliverable] | [Decision] | [X days before] |
| [Week/Date] | [Deliverable] | [Decision] | [X days before] |

## The Anchor

**Your anchor deliverable:** [The ONE thing that lands before the ONE decision that matters most]
**Why this changes everything:** [When this deliverable arrives before this decision, the client experiences you as the advisor who shaped their thinking — not the one who documented what they already decided]

## First Move

**This week:** [The single action that starts the shift — specific, concrete, doable in under an hour]

Confirmation

Show the completed plan. Ask:

• "Is this doable? Not in theory — could you actually make Shift 1 happen this month?"
• "If you made just the anchor shift and nothing else, would this client experience you differently?"
• "What would it feel like to walk into the next conversation knowing your work was already on the table before they made the call?"

Once confirmed, save to outputs/realignment-plan.md.

Then deliver the wrap-up summary from SKILL.md, including the bridge to the workshop.