Skip to content
Miguel CoronelChief Technology Officer

Transformation systems

A banking transformation is not held together by a picture of the destination. It is held together by the sequence that reaches it, the system that builds it and the governance that can stop it.

What it is made of

  1. 01

    Business capability

    Transformation starts from what the bank does, not from the systems it owns. The capability is the unit that survives a replatform; the system is not.

  2. 02

    Current-state constraints

    Legacy, core, integrations, regulation and operational risk. These bound what can move and at what pace — the as-is informs the target architecture; it should not imprison it.

  3. 03

    Target architecture

    Defined independently of what exists today, so the destination is not a slightly tidier version of the current estate.

  4. 04

    Transition architecture

    Explicit intermediate states, each one viable on its own. Plateaus and work packages turn a destination into a sequence somebody can actually execute.

  5. 05

    Operating model

    Who builds it, with what capability, under which standards and gates. An architecture without a delivery system behind it stays a drawing.

  6. 06

    Governance

    Explicit authority, declared criteria, evidence and gates — including the ability to stop an irreversible decision before it is taken.

  7. 07

    Execution enablement

    Contracts, provisioned repositories, archetypes and quality gates, so teams can build without re-deciding the same things on every service.

  8. 08

    Production evidence

    Claimed only where it exists. One of the transformations below is in production; the others are stated as what they are.

Technology operating models

Beyond the architecture itself, the delivery system that produces it: how work enters, how it is sized, who builds it and under which standards and gates it reaches production.

IntakeDimensioningTeam formationOnboardingExecutionDeliverySupport / evolution
Support and evolution feed back into intake: the model is a cycle, not a line that ends at delivery.

What it can integrate

  • Managed engineering capacity
  • API / service delivery capability
  • Team formation
  • Capability provisioning
  • Technical professionalization
  • Engineering standards
  • Quality and security gates
  • AI-assisted delivery
  • Governance

Transformations