Hundred Day Plan Drafter

Turn what you learned before the start into what somebody owns on Monday. A 100-day plan built directly from the diligence or planning record and the business case — so every assumption that justified the decision has a workstream, an owner, and a milestone — plus the leadership-ready one-pager and a refresh cycle that keeps it a working document rather than a folder nobody opens after week three.

Why this skill exists

The 100-day plan usually gets written in the exhausted week after the start — after the deal closes, after the offer is accepted, after the steering committee approves the program — from memory, by people who are already being pulled onto the next thing. The predictable result: the plan reflects what the author remembers rather than what the diligence or planning found, and half the assumptions that justified the decision never become anybody's job. Nobody notices, because the assumptions live in a spreadsheet tab or a business-case appendix and the plan lives in a deck, and no one ever puts the two side by side.

The second failure is timing. Plans written in week one commit to execution before the new leader, owner, or team knows anything from the inside — decisions made on a fact base assembled from outside the organization by people the organization was managing, or on a business case written to win approval. The plans that work treat the first month as fact-building and sequence execution behind it.

This drafts from the primary record, forces the business-case-to-workstream reconciliation, and builds in the refreshes.

Inputs

Required:

• At least one of: the business case, decision memo, or thesis; the diligence, assessment, or discovery readouts; or the model's benefits summary. More is better; all three is the intended case.

Optional, in rough order of value:

• The business case's benefits bridge — how the plan gets from today's baseline to the promised outcome, broken into its drivers: revenue, cost, margin, capacity, quality, cycle time, enrollment, retention, or whatever the case was built on. This is what makes the traceability check possible and it is the input most worth chasing down.
• Diligence, assessment, or discovery readouts by workstream, including the issues that were noted but not resolved before the start
• Any financial or operational baseline review, particularly adjustments that assumed a change the organization had not yet made
• Leadership and team assessment: who is staying, who is uncertain, what gaps were identified
• The organization's current reporting — what it actually produces monthly today, and in what format
• Who is available to do the work: the sponsor, the program lead, a chief of staff, integration or transformation resources, interim staff, budget for advisors
• Start date, first leadership or board review date, and fiscal or academic calendar
• Any commitments made to staff, customers, funders, lenders, or the board during the process
• The organization's own 100-day template or a prior plan

Missing-input behavior: Without the business case's benefits bridge, the traceability check — arguably the most valuable output — cannot run. Say so explicitly and ask once; a summary of the drivers is enough, the full model is not needed. Without a leadership assessment, draft the organizational workstream with owners marked [OWNER TBD] rather than assigning work to people whose roles you are inferring. Never invent an organizational metric, a headcount, or a financial figure.

How it works

1. Extract the benefits bridge into a list of discrete assumptions. Each one: what it assumes, how much it contributes to the promised outcome, and by when the business case expects it. This list is the spine of the plan.
2. Extract the open items from diligence or planning — everything flagged as unresolved, conditional, or "confirm after start." These become week-one workstreams, because they are the things that could change the plan.
3. Design the fact base for weeks 1–4. What the new leader or owner needs to know from the inside that diligence or planning could not establish: real customer- or program-level economics, actual pipeline quality, true capacity utilization, the state of the data, who actually makes decisions, where the informal power sits. Be specific to this organization and this business case, not generic.
4. Specify the KPI baseline and reporting cadence to install, which is the highest-leverage thing that happens in the first month. Which metrics, defined how, produced by whom, on what day of the month, in what format — and what has to change in the organization's systems to produce them. A metric that cannot be produced monthly is not a KPI.
5. Identify quick wins, each tied to a specific business-case assumption or diligence finding. A quick win with no line in the business case is a distraction; say so.
6. Surface leadership and organization decisions with a decide-by date. These are the decisions that get deferred and then cost a year.
7. Build the workstreams across the standard categories below, each with a named owner, a weekly milestone sequence, and the dependency that would block it.
8. Run the traceability check. Every business-case assumption mapped to a workstream; every workstream mapped back to an assumption or a finding. Report both directions — unmapped assumptions are promises nobody owns, and unmapped workstreams are effort nobody justified.
9. Sequence realistically against capacity. Count the workstreams against the people actually available and flag over-commitment. Most 100-day plans fail on capacity, not on ideas.
10. Write the leadership-ready one-pager, and set up the day 30/60/90 refresh structure.

Refresh mode: when run at day 30, 60, or 90 with actuals, compare planned milestones to what happened, re-baseline what has slipped, retire what is done, surface what the inside fact base has changed about the business case, and flag any assumption that now looks unachievable — early, while there is still time to respond.

Output format

# [Organization / role / program] — 100-Day Plan
Start: [date] | Plan date: [date] | First leadership or board review: [date]
Sources: [business case / decision memo, readouts, model — list with dates]
Not provided: [list]

## Leadership one-pager
[The whole plan on one page: the three things that must be true at day 100,
the KPI baseline being installed, the top quick wins with their business-case
impact, the leadership decisions and their dates, and the biggest risk to the
plan.]

## Business-case assumptions
| # | Assumption | Impact on the promised outcome | Expected by when | Workstream | Status |
|---|---|---|---|---|---|
**Assumptions with no workstream: [list — or "none"]** ← the critical output

## Weeks 1–4: build the fact base
| # | What we need to know | Why diligence or planning couldn't establish it | Who | By |
|---|---|---|---|---|
Open items carried into the start: [list, each assigned]

## KPI baseline and reporting cadence
| KPI | Definition | Source system | Owner | Frequency | Available today? | Work to enable |
|---|---|---|---|---|---|---|
Monthly reporting package: [contents, due date, recipients]
Systems or data work required: [ ]

## Quick wins (achievable inside 100 days)
| # | Quick win | Business-case assumption / finding it serves | Owner | Target date | Est. impact |
|---|---|---|---|---|---|

## Leadership & organization decisions
| Decision | Options | Decide by | Decision owner | Consequence of delay |
|---|---|---|---|---|

## Workstreams
### [Workstream name] — Owner: [name] | Sponsor: [name]
Objective at day 100: [ ]
| Week | Milestone | Dependency |
|---|---|---|
[Repeat per workstream.]

## Capacity check
| Owner | Workstreams | Milestones in first 30 days | Over-committed? |
|---|---|---|---|

## Risks to the plan
| Risk | Impact on the plan | Early warning signal | Mitigation |
|---|---|---|---|

## Refresh schedule
Day 30 / 60 / 90 review dates, what gets re-baselined at each, and who attends.

Workstream categories

Draft against these, drop the ones that do not apply to this situation, and never include one just because it is on the list:

• Finance & reporting — KPI baseline, monthly close speed and reliability, budget and forecast process, cash management where liquidity is tight, reporting obligations to funders, lenders, or the board
• Commercial / demand — pricing, sales or enrollment process and pipeline discipline, customer or program-level economics, churn and retention mechanics, team structure and incentives
• Operations & delivery — capacity, throughput, procurement, supply chain, service delivery, clinical or production quality, the specific operational thesis if there is one
• Organization & talent — leadership assessment and gaps, org design, incentive plan, key-person retention, the hires that must happen in year one
• Technology & data — systems that block the KPI baseline, ERP and CRM state, security posture, technical debt that constrains the plan
• Integration / acquisitions — for a merger, acquisition, or roll-up: integration sequencing, target criteria, and whether the organization can absorb the next one yet
• Stakeholders & relationships — for an incoming executive or new program: the relationships that must exist by day 100 with the board, peers, key customers, regulators, funders, unions, or community partners
• Governance — board or steering-committee composition and cadence, reporting pack format, delegation of authority, incentive alignment
• Risk, compliance & insurance — items flagged in legal, tax, regulatory, environmental, safety, or insurance review that need resolution after the start

Guardrails

• Every workstream has a named owner or an explicit [OWNER TBD]. Work assigned to "the team" or "management" does not happen. If the user did not say who is available, mark it TBD rather than inventing an org.
• Never invent organizational facts. No revenue figures, headcounts, customer names, system names, or metrics that were not provided. A plan that misstates the baseline is worse than a plan with gaps.
• The traceability check runs in both directions and is reported even when it is unflattering. Unmapped business-case assumptions are the finding this skill exists to produce.
• Distinguish what diligence or planning established from what interested parties said. Carry the evidence quality forward from the record — a workstream built on an unverified claim from the seller, the previous leader, or the business-case author should say so, because week one may disprove it.
• Sequence discovery before execution. Do not schedule irreversible decisions — reorganizations, pricing changes, system replacements, layoffs, site closures — before the fact base that would inform them exists. Where the business case genuinely demands an early irreversible move, flag it as a risk rather than burying it in a milestone.
• Be honest about capacity. If the plan requires more from a program lead or chief of staff than one person can do, say it in the capacity check rather than distributing the milestones and hoping.
• This is a draft plan, not a directive. The organization's leadership and teams own execution, and a plan imposed without their input rarely survives contact. Note where buy-in is required before a workstream can start.
• Confidentiality: pre-start materials, leadership assessments, and organizational plans are highly sensitive, and the leadership section in particular concerns identifiable individuals. Assume an organization-approved AI environment and handle personnel content accordingly.

Quality checks

• Every business-case assumption appears in the traceability table with a workstream or an explicit gap
• Unmapped assumptions listed prominently, not buried
• Weeks 1–4 are discovery, with irreversible decisions sequenced behind the fact base
• Every KPI has a definition, a source, an owner, and an honest "available today?" answer
• Each quick win names the business-case assumption or finding it serves
• Every workstream has a named owner or [OWNER TBD]
• Leadership decisions carry decide-by dates and the cost of delay
• Capacity check completed and over-commitment flagged
• No invented organizational facts or figures
• The one-pager stands alone for a board member or sponsor who reads nothing else

Example prompts

"I start as COO of a 400-person regional hospital group on the first of the month. Attached: the board's strategic plan, the operational assessment the consultants did, and my offer-stage notes on what the CEO expects. Draft my 100-day plan. I'll have a chief of staff; the CFO is new too."

"We closed on the acquisition last Friday — an industrial services business. Attached: the decision memo, our final commercial and financial diligence readouts, the baseline review, and the model's benefits bridge. Draft the 100-day plan. Our operating lead is full-time on this, the deal team stays involved through the first board meeting, and the CFO is a question mark."

"Day 30 refresh. Here's the original plan and where each milestone actually stands, plus the first monthly reporting package the team produced. What's slipped, what needs re-baselining, and does anything we've learned inside change the business case?"

"The steering committee approved the CRM replacement program yesterday. Business case, vendor selection readout, and the change-impact assessment attached. Draft a kickoff-focused 100-day plan — the head of sales operations will own most of it."

Works well with

decision-memo-drafter produces the business case and assumptions this plan traces against. Run red-team-premortem on the business case before drafting if the decision was contested and the model is aggressive. Use stakeholder-update-generator for the periodic updates once the plan is running.