Talk to us
ServicesCasesPeopleAboutFoundry
EventsFrameworkPerspectivesFor agents
Machine view

Answers are written by AI from our own pages. Privacy

Weeks, not years.

Four steps that take a leadership team from a shared view of where they are to capabilities that stay when the project ends. There is a thorough version and an accelerated twelve-week version; both have the same shape.

source: framework updated 2026-11-04 reviewed by JA markdown permalink

The four steps.

  1. Future Scan

    The vision: where we are and where we want to be.

    A structured assessment in nine dimensions: strategy and leadership, compliance and risk, technology infrastructure, client experience, process digitalisation, people and skills, data, operations, and market. Interviews, value-chain mapping and a strategic baseline.

    Accelerated: Week 1: a hackathon. Day 1 goals and ideas, days 2 to 4 a prototype, day 5 the brief and vision for the programme.

  2. Future Plan

    The strategy: how do we achieve what could be?

    A roadmap that translates the assessment into priorities, milestones and measurable outcomes, with KPIs, governance and resource implications.

    Accelerated: Weeks 2 to 4: the backlog of opportunities, a prioritisation framework, and a business case for each of the top five use cases.

  3. Future Proof

    The pilot: how to prove the value in practice.

    Selected initiatives run as pilots with defined scope, a risk register and feedback loops, in agile iterations, to validate KPIs before scaling.

    Accelerated: Weeks 5 to 8: the first MVP pilot from development to test and production. Prerequisite: working infrastructure.

  4. Future Ready

    The scaling: embed the change and scale what works.

    Validated pilots become firm-wide implementation with governance, training and performance frameworks, and a centre of excellence to keep the capability.

    Accelerated: Week 9 onwards: a full-stack sprint team in four-week cycles. Review the plan, review the backlog, build the top use case, test, launch.

source: framework updated 2026-11-04 permalink

And for AI specifically: ninety days, one bounded process.

  1. Days 1 to 30. Choose one process. Establish the baseline, the owner and the limits. Run a bounded test.

  2. Days 31 to 60. Compare results with the baseline. Improve the workflow and resolve recurring failures.

  3. Days 61 to 90. Decide whether to stop, adjust or expand. Put support and monitoring in place before scaling.

The evidence at each stage determines the next step.

source: perspectives updated 2026-11-04 permalink