A regional bank used a phased approach for its loan-underwriting assistant: envision defined the business case, experiment tested it with one branch's underwriters, and launch expanded it to a regional cluster of branches with formal monitoring in place. Leadership now asks what the scale phase should focus on. What should the transformation lead recommend?

Scale is the phase where an already-validated operating model, governance approach, and support structure get extended enterprise-wide, which is exactly what this bank has earned the right to do after launch already proved the model across a regional cluster with formal monitoring in place. Repeating the experiment phase in additional branches re-runs a feasibility question that's already been answered twice over — once in the original experiment, and again during launch — so more experiment-style testing at this point is the right instinct applied at the wrong stage. Returning to envision to redefine the business case for the full enterprise is similarly unnecessary, since launch already confirmed the case holds beyond the original branch; there's nothing left to redefine. Limiting further expansion to branches that individually request the tool, with no coordinated plan, lets adoption happen ad hoc rather than through the governance and support model that launch validated, which reintroduces exactly the inconsistency risk the phased approach was built to prevent. The operating principle: once launch validates an operating model, scale means deliberately and consistently extending it, not repeating validation work or letting adoption drift without coordination. Operational check: is expansion following the model that was already proven, or is each new site reinventing its own approach?