LEARN. PRACTICE. GROW.Concept and mechanism
To analyze change, describe the current state with enough evidence to explain the problem. Include people, rules, information, and technology. A server diagram does not show who resolves exceptions or why a decision waits. Define the future state through observable outcomes and capabilities, keeping confirmed constraints distinct from assumptions still needing validation. A gap may require training, process changes, data access, or technology. A sponsor’s preferred solution is an option to evaluate unless an authorized constraint makes it mandatory. Use risk analysis to make uncertainty explicit: possible cause, event, consequence, exposure, and response. A favorable assumption is not a fact merely because it fits the plan.
Guided application
Consider a team able to reconcile 400 transactions per day. Parallel operation during transition would require 650. The plan needs an answer for the 250 gap even when the final architecture is suitable. Compare phasing, temporary capacity, or controlled volume reduction while assessing business effects. Define criteria for leaving each transitional state and owners for that decision. Do not assume technical readiness means operational readiness: access, skills, schedules, and inter-team agreements matter too. In an expected-cost exercise, 20% probability and a 50-thousand-euro impact produce 10 thousand euros of exposure; that value helps compare options but does not remove tolerance limits for rare losses.
A viable final solution can have an unworkable transition.
Common pitfalls
Architecture treated as the full state; assumption treated as commitment; expected value treated as tolerance.
Related topics: Plan analysis and decisions · Elicitation, evidence, and collaboration · Life cycle, priorities, and changes
Explain the gap and show how to cross the transition.
Reference: Predictive adaptive and hybrid approaches · Six-knowledge-area blueprint / handbook May 2026