LEARN. PRACTICE. GROW.Concept and mechanism
A practice supplies capabilities that may contribute across several value streams. Change enablement can participate in an urgent fix and a new application without making each practice an isolated stream. The complete journey combines activities to produce an outcome. Observe people and organization, information and technology, partners and suppliers, and the streams and processes themselves. Changing tool states does not necessarily resolve access, ownership, or poorly defined handoffs. If a request takes ten days with only 90 minutes of active work, investigate waits and returns. Ten elapsed days do not equal ten person-days of effort.
Guided application
Automation should be evaluated within that journey. When requests return because information is ambiguous, understand and simplify intake, test its effect, and automate suitable stable steps. A 40% reduction in the first team may transfer corrections and maintenance to APS. Include that effort, risk, and outcome effect before expanding. A bounded pilot enables learning without assuming everything must be automated at once. If feedback contradicts an assumption, review the next increment while retaining relevant objectives and constraints. Do not silently change the goal to make results look better or abandon all direction because one local assumption failed.
Routing an incomplete request faster may accelerate rework arriving at the next team.
Common pitfalls
Practice as isolated stream; tool as transformation; local gain as global; automation before understanding intake.
Related topics: Direction, planning, and outcomes · Scope, objectives, and authority
Measure the effect on the complete service and use feedback to adjust the intervention.
Reference: Google SRE Workbook: Eliminating Toil · ITIL 4 DPI; observed JA v1.3.1, current detailed revision comparison pending