01 · Purpose
Why and when to use it
Why?
It prevents a manageable process problem from expanding into an attempt to fix the whole organisation.
When?
Use it in Define before committing the team to detailed measurement. Revisit it when new findings challenge the boundaries.
Who takes part? The leader, process owner and people working at the process boundaries agree the frame; affected stakeholders check its consequences.
02 · Application
How to apply it
Start with: A draft problem statement, process start and end points, affected segments, constraints and available resources.
- Name the process and its trigger and endpoint.
- List the relevant locations, product groups, customer groups and working periods.
- Separate included and excluded elements with reasons.
- Record interfaces with other teams and constraints on changes.
- Check whether the defined scope can address the goal.
- Agree how scope changes will be assessed and approved.
03 · Example
A warehouse dispatch project
Original illustrative example. All quantities, targets, roles and timings below are fictional teaching assumptions, not findings from a real project.
| Dimension | Included | Excluded / interface |
|---|---|---|
| Process | Released order to carrier handover | Order entry before release; delivery after handover. |
| Products | Stocked spare parts | Made-to-order assemblies. |
| Location | Main warehouse, both shifts | Regional depot. |
| Performance | Dispatch timeliness and picking accuracy | Carrier transit time. |
| Interface | Sales confirms promised dispatch dates | Supplier lead times are recorded as context. |
04 · Interpretation
What the result tells you
A boundary is useful when a team can decide whether a particular order or activity belongs in the project. Excluding supplier performance does not mean ignoring its influence; it means the team does not own a supplier improvement workstream.
Completion check: An agreed scope table with explicit boundaries, exclusions, interfaces and a change route.
05 · Judgement
Mistakes and limitations
Common mistakes
- Using department names without specifying process boundaries.
- Excluding a major influence without recording an interface.
- Accepting extra work informally while leaving the frame unchanged.
Limits of the tool
A narrow frame can hide system-wide trade-offs. Escalate when improvement inside the boundary shifts delay or workload elsewhere. The label “Project Frame” is not used uniformly across organisations.
07 · Reading
Sources and further reading
Toolset backbone: Six Sigma+Lean Toolset: Mindset for Successful Implementation of Improvement Projects, second edition, edited by Stephan Lunau, with Renata Meran, Alexander John, Olin Roenpage and Christian Staudter (Springer, 2013). This reference identifies the toolset; the book text was not available for a chapter-level comparison in this development pass. The explanations, application sequence and fictional examples here are original LeanTrainingLab teaching material. Linked readings provide background; they do not prescribe every example or target.