A connected set of practitioner frameworks for understanding the problem landscape, testing what is genuinely feasible, assessing whether the technology and organisation are ready, and converting the resulting opportunities into a sequenced transformation roadmap.
The tools are designed to work independently, but they are most powerful when used as a sequence. Each addresses a different decision that transformation leaders need to make before committing resources, technology and organizational capacity.
The methodology intentionally separates opportunity from feasibility, and feasibility from readiness. A high-value use case is not automatically ready to automate; a feasible solution is not automatically supported by the technology estate; and a technically ready program is not automatically supported by the operating model or organization.
Decompose a complex process or problem landscape into L1, L2 and L3 issues, attach demand and complexity data, and identify where root-cause analysis, process redesign or deeper automation assessment should begin. Includes a fully populated retail-banking example.
Test shortlisted issues at workflow-path level using process clarity, path probability, data/API access, business rules, human judgment, risk, ROI confidence, implementation effort and realistic automation coverage.
Determine whether architecture, APIs, environments, engineering practices, AI platforms, security, data foundations and production operations are sufficiently ready to support transformation at scale.
Test whether leadership, sponsorship, operating model, change capacity, program governance, AI controls and benefits mechanisms are strong enough for the transformation to take hold and sustain value.
Convert a portfolio of initiatives into a more executable roadmap by evaluating value, delivery complexity, capacity demand and cross-workstream dependencies before deciding what should move first.
Use the issue-tree framework to understand where demand, friction or failure really sits. This creates a disciplined candidate universe before solution selection begins.
Use the Level-2 feasibility assessment to determine which issues or workflow paths can actually be automated safely, economically and with sufficient coverage.
Assess both the technology estate and the organization. A viable automation opportunity can still fail if APIs, environments, engineering practices, ownership, adoption or governance are weak.
Once the viable initiatives and remediation actions are known, use Level-3 sequencing to manage dependencies, delivery capacity and priorities across the transformation portfolio.
Each framework is intended to force a useful conversation about the evidence behind a transformation assumption. The issue tree should change where investigation starts. The feasibility assessment should change what gets automated. Readiness diagnostics should change the implementation plan. Prioritization should change the sequence.
A score is useful only when it leads to a better decision: proceed, narrow the scope, remediate a prerequisite, introduce stronger controls, change the operating model, defer an initiative or sequence the roadmap differently.
Explore each framework in detail, understand when it should be used and download the underlying practitioner toolkit from its dedicated page.
