Skip to content
KatafactsBeta

Kaizen events

Implementation plan

Implementation plan is licensed CC BY 4.0. Attribution: Katafacts (katafacts.com).

Customise with AISkill file ↓

1 · What it is

What it is

An implementation plan turns a commitment — a countermeasure, a kaizen charter's rollout, a Hoshin catchball agreement — into a real, checkable sequence of milestones converging on a target completion date. Each milestone names who it depends on: your own team, an outside party, or both jointly. Days remaining, which milestones are already overdue, and which have no named owner yet are all computed from what you enter, not asserted. The one check unique to this tool: if every milestone belongs to your own side, that's flagged directly — a plan with zero cross-functional dependency usually means nobody outside the initiating team has actually committed to anything yet, not that the plan is simpler than most.

2 · When to use it

When to use it — and when not to

Use it when

  • A commitment depends on more than one team or person actually doing something, and you want a real, dated sequence instead of a vague understanding.
  • You want to know honestly which milestones are already behind schedule and which have nobody named against them yet.
  • You're rolling out something (a countermeasure, a new standard, a system change) where an outside team's action is a real dependency, not just your own team's work.

Not when

  • Everything genuinely depends on one person or one team — a plan with no real outside dependency doesn't need this structure; a simple task list will do.
  • You don't have a real target completion date yet — pin that down first, or the days-remaining and overdue math has nothing real to measure against.
  • You're still deciding what to do, not how to sequence doing it — that's an A3 or a kaizen charter's job; this tool assumes the commitment is already made.

3 · How to fill it in

How to fill it in

Milestones
Describe the commitment roughly — a first-pass milestone sequence gets drafted, each with who it depends on (you, them, or joint) and a target date. Assign a real named owner to each afterward; that's never guessed for you.
Coverage
Computed from your milestones and dates — nothing to enter here.
Risks
Drafted alongside the milestones — what could realistically cause this plan to slip.
Narrative
Drafted from the plan actually built.

4 · What good looks like

What good looks like

The example below rolls out a new andon escalation rule across a fabrication cell's three shifts — one milestone is already honestly overdue, one has no owner named yet, and the plan is genuinely cross-functional rather than something the improvement team alone could execute.

Same example, as a downloadable xlsx workbook.

Download .xlsx

Implementation plan · Fabrication Cell 3 — andon escalation rollout

Andon escalation rollout — Fabrication Cell 3

Dana Ruiz, Cell Lead · 2026-04-10

Team: Raj Patel, Controls Engineer · Sponsor: Marcus Lee, Quality Manager

Roll out the new andon call-button escalation rule (two unresolved calls in 15 minutes pages the shift supervisor directly) across all three shifts on Fabrication Cell 3, following the kaizen event that designed it.

Milestones

  • Update the andon call-button escalation logic in the Cell 3 PLC

    Overdue

    them · Raj Patel, Controls Engineer · Target: 2026-04-05 · Status: in-progress

  • Train first-shift operators on the new escalation flow

    us · Dana Ruiz, Cell Lead · Target: 2026-04-15 · Status: not-started

  • Train second-shift operators on the new escalation flow

    Unassigned

    them · Unassigned · Target: 2026-04-20 · Status: not-started

  • Confirm andon response-time logging captures the new escalation tiers

    joint · Dana Ruiz & Raj Patel · Target: 2026-04-25 · Status: not-started

  • Go live across all three shifts

    us · Dana Ruiz, Cell Lead · Target: 2026-05-01 · Status: not-started

Coverage

Target completion

2026-05-01 (21 days)

Done

0 / 5

Overdue

1

Unowned

1

Us / Them / Joint

2 / 2 / 1

Risks

  • The PLC logic change depends on Controls' quarterly change-freeze schedule — if it slips past the freeze window, the whole rollout slips a full quarter.
  • Second shift's supervisor turnover last month means there may be nobody who actually owns that shift's training yet — exactly what the unowned milestone above is flagging.

Narrative

One of five milestones — the PLC escalation-logic update — is already overdue relative to today's date, and second-shift training has no named owner yet. The plan is genuinely cross-functional, not something the improvement team could execute alone: two milestones belong to the cell lead, two to outside teams (Controls and second shift), and one is joint. 21 days remain to the May 1 go-live.

5 · Common mistakes

Common mistakes

  • Writing every milestone as something your own team does.

    A plan where every milestone belongs to your own side isn't actually testing whether anyone else has really committed — that's exactly what the mutuality check exists to catch, not a sign the plan is simpler than most.

  • Leaving a milestone unowned and moving on rather than naming the gap.

    An unowned milestone isn't a detail to fill in later — it's a real risk to the completion date, and this tool's whole point is surfacing that honestly instead of letting a plan look more complete than it is.

  • Writing a risk as vague as 'things could change.'

    A risk that isn't specific enough to actually watch for isn't useful — name the real thing that could slip this plan, the same discipline this catalogue applies to every other finding.

6 · What it connects to

What it connects to

upstream

  • A3 problem solving

    A countermeasure an A3 identifies is exactly the kind of commitment that needs a real, dated, cross-functional plan to actually happen.

  • Kaizen event charter

    Once a kaizen event's plan is set, rolling out what it produced across a wider area is what this tool sequences.

downstream

    7 · Where AI helps

    Where AI helps

    Judgement — stays yours

    • Deciding whether a drafted milestone's ownerParty judgement is actually right
    • Deciding which overdue or unowned milestone to chase down first

    Analysis — AI helps

    • Drafting a milestone sequence and real risks from a rough description of the commitment
    • Drafting the narrative from the plan actually built

    Drudgery — automated

    • Computing days to target completion, overdue count, and the ownership split
    • Flagging which milestones have no named owner yet
    • Exporting to xlsx in the house format

    9 · Rate this kata

    Rate this kata