Hard to Fire

SOFT LANDING · CHAPTER 15 · TWELVE OUTPUTS, NOT NINETY DAYS OF MOTION

The 90-Day Soft Landing Plan

Turn the first ninety days into twelve weekly outputs, four phase reviews, and one dated next decision.

Output: One capstone plan routing the accepted chapter tools through twelve inspectable weekly records.

Time: One weekly record and Friday review; four phase decisions

Weeks scheduledOpen
Weekly recordsOpen
Phase reviewsOpen
Day 91Open
PlanOpen

The plan still has an unscheduled weekly record.

Next: schedule Week 1.

Four phases

The calendar doesn't promise an offer by Day 90. It preserves sequence, evidence, and the next decision.

StabilizeWeeks 1-2

Protect the first seventy-two hours and the separation decision.

OrganizeWeeks 3-4

Make the story, evidence, materials, and first channel legible.

ActivateWeeks 5-8

Run the portfolio, record interview evidence, diagnose channels, and close the block.

AccelerateWeeks 9-12

Give capacity to evidence, repair the bottleneck, reopen constraints, and write Day 91.

Every week ends with one output, one feedback loop, and one decision rule.

The twelve weekly records

Week 1: Establish the Record

Stabilize

Trigger: Memory is fresh; agreement and deadlines must become legible before action.

Required output: Dated control packet with separation record, marked agreement, baseline and stress runway, filing action, account inventory, and Deadline Tracker.

Source home: Chapters 1, 2, 5, 6

Owner, date, and status unresolved.

Week 2: Protect the Decision

Stabilize

Trigger: Agreement terms, coverage, equity, and household facts must be legible before signing or acting.

Required output: Decision packet with coverage comparison, benefits and equity dates, household alignment, counsel decision, and counterproposal record.

Source home: Chapters 3, 4, 5, 6

Owner, date, and status unresolved.

Week 3: Make the Story and Evidence Legible

Organize

Trigger: A network can't route an opportunity toward a target you haven't named.

Required output: Three narratives, rehearsed Professional version, Search Strategy Matrix, source-grounded target packet, and five translated accomplishments.

Source home: Chapters 8, 9, 10, 13

Owner, date, and status unresolved.

Week 4: Prepare Materials and Open the First Channel

Organize

Trigger: Materials and targets must be ready before opening the relationship channel.

Required output: Source-controlled résumé set, sent first-cycle messages, promise log, target evidence, and active-or-not-active independence route.

Source home: Chapters 9, 10, 11, 14

Owner, date, and status unresolved.

Week 5: Run the First Full Portfolio Cycle

Activate

Trigger: Readiness gates are satisfied and all four search channels are allocated.

Required output: Complete channel record with time, actions, human signals, open promises, and unresolved source questions.

Source home: Chapters 7, 9, 10, 11

Owner, date, and status unresolved.

Week 6: Add Interview and Pattern Evidence

Activate

Trigger: A live interview is scheduled.

Required output: Preparation record for each live interview, six-question debrief after each completed interview, and evidence-only Pattern Log entries when applicable.

Source home: Chapters 12, 13

Owner, date, and status unresolved.

Week 7: Diagnose the Channels

Activate

Trigger: Enough channel data exists to compare evidence classes.

Required output: Channel-diagnosis memo naming one plausible cause, evidence, and the smallest next test for each weak channel.

Source home: Chapters 9, 10, 11

Owner, date, and status unresolved.

Week 8: Close the First Activation Block

Activate

Trigger: Four weekly outputs and an updated runway record are available.

Required output: Phase review with runway, deadlines, channel evidence, interview stage, closed promises, emotional status, and one allocation decision.

Source home: Chapters 5, 6, 7, 9, 11, 12

Owner, date, and status unresolved.

Week 9: Intensify One Proven Route

Accelerate

Trigger: One route produced a meaningful signal.

Required output: Revised one-week allocation with one intensified route, comparison channels, and evidence supporting the change.

Source home: Chapters 9, 10, 11

Owner, date, and status unresolved.

Week 10: Diagnose the Bottleneck

Accelerate

Trigger: A specific stage repeatedly stalls or fails to produce signal.

Required output: One bottleneck memo tied to a specific stage, repeated evidence, and one bounded repair.

Source home: Chapters 9, 12

Owner, date, and status unresolved.

Week 11: Reopen the Constraints

Accelerate

Trigger: Runway, deadlines, or offer status require a constraint review.

Required output: Constraint register marked load-bearing, testable, or unresolved, plus an updated employment-versus-independence decision when applicable.

Source home: Chapters 5, 6, 13, 14

Owner, date, and status unresolved.

Week 12: Write the Next Operating Decision

Accelerate

Trigger: The full twelve-week record is available.

Required output: Dated Day 91 plan naming active track, runway, deadlines, strongest channel, bottleneck, allocation, and one stop decision.

Source home: Full record

Owner, date, and status unresolved.

The four phase reviews

A block review never substitutes for the weekly output.

Stabilize phase review

After Weeks 1-2
Phase review open.

Organize phase review

After Weeks 3-4
Phase review open.

Activate phase review

After Weeks 5-8
Phase review open.

Accelerate phase review

After Weeks 9-12
Phase review open.

Day 91

Completion test

Finish twelve weekly records, four phase reviews, the Day 91 record, and one dated next decision. A block review never substitutes for a weekly output.

Monday Move

Open Week 1. Produce the control packet before the search acquires seventeen browser tabs and a personality.

This tool stays in this browser with LocalStorage until you clear it.