90‑Day Transformation Kickoff Kit

Welcome — Start Strong, Learn Fast

This kickoff kit helps teams launch a focused 90‑day transformation that moves work from ad‑hoc fixes to a repeatable learning loop. Use this kit to align stakeholders, set measurable baselines, assign ownership, and begin discovery experiments that teach the organization how to improve decisions and outcomes.

Why a structured kickoff matters

A clear kickoff reduces noise, prevents orphaned pilots, and focuses scarce attention on a few high‑value experiments. It creates shared expectations about metrics, decision rights, cadence, and follow‑up so the team can iterate with confidence.

What’s included (starter list)

• Kickoff agenda (90‑minute template plus optional 45‑minute version)
• Stakeholder alignment script and simple stakeholder map format
• 30/60/90 sprint templates (experiment backlogs, owners, success criteria)
• Baseline metric capture sheet (recommended categories and sample KPIs)
• Quick diagnostic checklist to prioritize work
• Decision rights RACI template for the initiative
• Communication cadence and sample announcement/weekly update language
• Templates for weekly syncs and retrospectives
• Tailoring notes for small teams, midsize initiatives, and enterprise pilots

Kickoff agenda — 90‑minute template

1. Opening (10 min) — Purpose, expected outcomes, and what success looks like at 90 days.
2. Context & Quick Diagnostic (15 min) — Brief framing of the problem, customer impact, and a 5‑question diagnostic (see checklist below) to confirm scope.
3. Stakeholders & Roles (15 min) — Walk stakeholder map, clarify who needs to be informed, consulted, and empowered.
4. Baseline Metrics (15 min) — Agree on 2–5 primary metrics and how to capture the baseline this week.
5. 30/60/90 Sprints (20 min) — Identify initial experiments, owners, expected outcomes, and quick success criteria.
6. Cadence & Decision Rights (10 min) — Confirm weekly sync, who makes which decisions, escalation path, and communications.
7. Next Steps & Commitments (5 min) — Immediate actions, owners, and timing for first data capture.

45‑minute quick kickoff (when time is tight)

Compress the agenda: combine Context & Diagnostic with Stakeholders, limit metrics to a single measurable baseline, and capture 1–2 experiments for the first 30 days. Reserve detailed RACI and extended experiment definition for follow‑up working sessions.

Stakeholder map (simple format)

Use a two‑axis map or a table. Example columns:

• Stakeholder (name/role)
• Interest (high/medium/low)
• Impact (high/medium/low)
• Preferred involvement (Lead / Consult / Inform)
• Critical requirements or concerns

Baseline metric capture — recommended categories & sample KPIs

Choose a small set (2–5) of primary metrics that reflect customer value or process health. Capture baseline this week and log the measurement method.

• Quality: defect rate, first‑pass yield
• Speed: cycle time, lead time
• Reliability: uptime, incident frequency
• Customer experience: NPS, on‑time delivery
• Cost/Efficiency: cost per unit, overtime hours

For each metric record: name, definition, data source, current value (baseline), owner, and measurement frequency.

30/60/90 sprint templates (how to fill)

Each sprint entry should include:

• Experiment title and brief hypothesis (If we X, then Y will improve by Z)
• Owner and contributors
• Success criteria (metric change, qualitative signal, learning outcome)
• Required support or blockers
• Planned end date and review meeting

Quick Diagnostic Checklist (use during kickoff)

1. Is the problem tied to a measurable outcome customers or operations care about?
2. Do we have credible data to measure change in the next 30 days?
3. Is there at least one clear owner who can make or coordinate changes?
4. Will an experiment be safe and low‑cost enough to run quickly?
5. Are key stakeholders aware and minimally aligned with the goal?

Decision‑rights RACI (simple template)

Map major decisions and assign RACI roles: Responsible (does the work), Accountable (final sign‑off), Consulted, and Informed. Example decisions:

• Which metrics to prioritize
• Approval of experiment scope
• Budget use for pilots
• Operational changes or rollouts

Weekly sync template

Keep weekly meetings short (30–45 min). Suggested structure:

• Quick metric check (5 min)
• Experiment updates (owner, status, blockers) (15–20 min)
• New learnings and decisions needed (10 min)
• Action items and owners (5 min)

End‑of‑sprint retro prompts

• What did we expect and what actually happened?
• What did we learn about the hypothesis or the metric?
• What should we stop, start, or continue next sprint?
• Any changes to measurement or decision rights?

Communication plan samples

Frequency and channels:

• Weekly team update (email or shared doc): short metric snapshot + 2–3 bullets.
• Monthly stakeholder summary (15–30 min): key results and escalations.
• Project space (shared doc or THE collection): living record of experiments, data, decisions.

Sample announcement language: "We're launching a focused 90‑day improvement to reduce [problem]. We'll run small experiments, measure progress weekly, and share short updates. Key owners: [names]. First baseline measurement: [date]."

Tailoring guidance

Small teams: Favor a short kickoff, one primary metric, and a single weekly sync. Midsize initiatives: Use the full 90‑minute kickoff, 2–3 experiments in parallel, and a lightweight RACI. Enterprise pilots: Add formal stakeholder briefings, automated metric dashboards, and a steering group for governance.

How to use this kit with platform capabilities

Make the kit interactive where useful: use structured forms to capture baseline metrics and experiment definitions, save weekly submissions for historical comparison, and allow teams to copy and tailor the toolkit for their site. Recommended next steps:

• Create an interactive baseline metric capture form (fields: metric name, definition, data source, baseline value, owner, frequency).
• Build a reusable 30/60/90 experiment template as a form so teams can submit and track experiments.
• Store weekly sync notes and retro outputs as saved submissions for trend analysis.

Next steps — immediate checklist

1. Schedule the kickoff and invite identified stakeholders.
2. Agree on the 2–5 primary metrics and capture baselines within 7 days.
3. Define the first set of experiments for the 30‑day sprint and assign owners.
4. Set weekly sync cadence and confirm who will record the updates.

Final note

This kit is a practical starting point. Copy it into your team space, tailor the templates to local language and constraints, and focus relentlessly on short learning cycles that inform decisions. If you want, consider converting the baseline and experiment templates into interactive forms so your team can capture and track results consistently over time.