Change type and boundary
4 min read
Lesson objectives
- Classify the change and define its boundary and justify the decision using case evidence.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
The previous lesson produced a testable problem. Now we must decide **what will actually change**. A manager may call a one-field edit an “organizational transformation,” while a small tool may move decision rights across several departments. The label does not determine scale. Draw a boundary around the behaviors, processes, decisions and data that will differ after implementation, then identify the people and systems that depend on them. A clear boundary prevents promises the intervention cannot deliver and protects adjacent work from accidental change.
One useful distinction is between **incremental improvement**, which adjusts an existing way of working while its basic purpose and structure remain, and **transformation**, which reorganizes how value is produced or how decisions and services connect across parts of an organization. Transformation is not inherently better because it sounds larger. Its reach usually demands more coordination, learning and risk control. A series of improvements might reveal a structural problem and require a revised classification. Treat the category as a planning hypothesis to test against actual work, not as a promotional badge.
Create a “today/tomorrow” table with four angles: who starts the work, who decides, which data are used, and how the user knows the service is complete. Add an impact column: none, limited or substantial. Trace dependencies on both sides of the handoff. A change to intake fields may affect the front-line worker, the back-office reviewer, the system owner and the person responsible for data-retention policy. Leaving one out can produce an interface that works technically but fails at the handoff. A dependency does not automatically justify expanding the project; it means agreeing on the interface with the owner of the adjacent process.
After mapping, write explicit boundaries: what the initiative includes, what it touches but another team owns, and what will stay as it is. For example: “We will change the request description and pre-handoff validation for Team A; we will not change customer eligibility or the accounting system.” Connect each desired result to a behavior that changes. If the target is fewer returned cases, how will the extra field achieve that? It may prevent incomplete handoffs, but it cannot fix a transfer process that loses data. This is a causal chain to test: specified change → new behavior → intermediate effect → result. If the chain breaks, narrow the promise or extend diagnosis before rollout.
Finally, distinguish the initiative’s boundary from the **first pilot’s** boundary. The intended destination may be a common process at five sites, while the pilot begins at one site where results can be measured and the old procedure restored safely. State a condition for expansion: returns fall without exceeding a service-time guardrail, and staff can demonstrate the new task. A small pilot does not reveal every effect of wider adoption. New dependencies and incentives can emerge at scale, so update the map at each stage.
Lesson summary
Classify the change and define its boundary with stated assumptions and verification.