Problem definition

Scoping canvas

Scoping canvas is licensed CC BY 4.0. Attribution: Katafacts (katafacts.com).

1 · What it is

What it is

A scoping canvas is a one-page definition of what an initiative actually covers, built before anyone starts work on it — not a project plan, and not a full charter, just the boundary-setting document that keeps a team from discovering three weeks in that they disagreed about what was in scope. Unlike most tools in this catalogue, a canvas is genuinely defined by which sections apply to the situation, the same way a real Business Model Canvas or lean scoping exercise is — problem/goal/in-scope/out-of-scope/team/timeline/assumptions is the default set, not a rigid universal structure.

2 · When to use it

When to use it — and when not to

Use it when

An initiative is real enough to commit time to, but its boundaries haven't been written down anywhere a disagreement could be checked against.
Multiple people or teams are involved, and 'what's actually in scope' has already come up as a question once.
You want a fast way to see what's still undefined — a thin section here is a real gap, not just an editing task.

Not when

The initiative is small enough that one person can hold the whole scope in their head with no real risk of drift — a canvas adds ceremony without adding value there.
You need a full charter with a resourced budget and formal sign-off — a kaizen event charter or business case is the right tool for that weight of commitment.
The boundaries are already written down and agreed somewhere else — don't duplicate an existing source of truth.

3 · How to fill it in

How to fill it in

Problem / opportunity: What's the situation, and why does it matter now? One or two sentences, not a full background essay.
Goal statement: What does this initiative need to achieve, specifically enough that you'd know if it succeeded?
In scope: What's genuinely in scope — drafted from your notes, then yours to correct.
Out of scope: What's deliberately excluded, and why — an empty out-of-scope section is itself a finding, not just unfilled.
Team & stakeholders: Who's involved, and in what role?
Timeline: What are the key milestones or phases?
Assumptions & constraints: What has to be true for this to work, or what's constraining it?

4 · What good looks like

What good looks like

The example below scopes a kaizen event that picks up directly where a prior A3's countermeasures left off — tightly bounded to one line, one procedure, explicitly deferring the adjacent line and any capital spend rather than letting scope creep in by default.

Same example, as a downloadable xlsx workbook.

Download .xlsx

Scoping canvas

Scoping canvas — Line 2 paint booth changeover event

Priya Nair, Line Supervisor · 2026-02-20

Problem / opportunity

The A3 on Line 2's on-time shipment rate (2026-02-03) traced the root cause to no standard rule for sequencing small-batch orders into the paint schedule — its two committed countermeasures (a fixed changeover-slot rule, a visual queue board) close the immediate gap but don't touch the underlying changeover time itself.
Even with the new sequencing rule, a full changeover still costs the same ~45 minutes it always has — a kaizen event on the changeover procedure itself is the next lever once the sequencing fix has had time to prove out.

Goal statement

Cut single changeover time on the Line 2 paint booth from ~45 minutes to under 25 minutes within one quarter of the event, without adding headcount.

In scope

The physical changeover procedure itself — setup, color-switch, cleanup steps — for the Line 2 paint booth only.
Tooling and fixture changes that fit within the existing booth footprint.

Out of scope

The small-batch sequencing rule itself — already decided and rolling out via the A3's countermeasures, not re-opened here.
Line 1's paint booth — explicitly deferred in the A3's follow-up actions until Line 2's results are in.
Capital equipment purchases — this event works within existing tooling only.

Team & stakeholders

Marcus Webb (paint booth lead) runs the changeover time studies.
Dana Ruiz (scheduling) confirms any procedure change doesn't conflict with the new sequencing rule.
Oksana Petrova (plant manager) sponsors and clears floor time for the event.

Timeline

Week 1: baseline time study on 5 real changeovers.
Week 2: kaizen event — a single 3-day session to redesign the procedure.
Weeks 3-4: trial the new procedure, adjust based on real changeovers.
End of quarter: confirm sustained time against the 25-minute target.

Assumptions & constraints

Assumes the A3's sequencing rule is holding by the time this event starts — if changeover frequency is still unpredictable, the time-study baseline won't be representative.
No budget assumed for new tooling; any fixture changes have to use materials already on hand or trivially sourced.

Narrative

This event picks up directly where the A3 left off: the sequencing rule stops changeovers from happening at the wrong time, but it doesn't make any single changeover faster. Scoped tightly to the physical changeover procedure on Line 2 only — Line 1 and any capital spend are explicitly deferred — with a short baseline-then-event-then-trial timeline that fits inside one quarter, matching the A3's own effect-confirmation window.

5 · Common mistakes

Common mistakes

Leaving out-of-scope empty because nothing's been explicitly excluded yet.
An empty out-of-scope section almost never means nothing's excluded — it usually means the boundary hasn't been thought through yet, which is exactly the ambiguity this canvas exists to catch before it causes a real disagreement.
Writing a goal statement vague enough that almost any outcome would count as success.
A goal that can't fail isn't a real goal — the same discipline an A3's problem statement or a business case's cost-of-inaction section already holds itself to.
Treating the canvas as a one-time exercise nobody revisits once the initiative starts.
Scope drifts in real work — a canvas that's never checked against again is ceremony, not a working document.

6 · What it connects to

What it connects to

upstream

A3 problem solving
A recurring problem an A3 surfaces sometimes needs work bigger than one countermeasure can carry — that's exactly when it graduates into a scoped initiative of its own.

downstream

Kaizen event charter
Once an initiative is scoped and worth a dedicated event, the charter is where it gets resourced, dated, and given a roster — heavier commitment than a canvas alone implies.
Business case
An initiative whose value needs to be argued for, not just scoped, is where a business case's investment/value-driver discipline takes over.

7 · Where AI helps

Where AI helps

Judgement — stays yours

Deciding where the real boundary between in-scope and out-of-scope actually sits
Deciding whether a goal statement is specific enough to know later whether it was hit

Analysis — AI helps

Drafting each section's bullets from a rough description of the initiative
Flagging a section that's too thin to mean anything yet, rather than padding it

Drudgery — automated

Formatting the canvas and keeping every section on one page
Exporting to xlsx in the house format

9 · Rate this kata