Experience

15+ years in technology and 11+ focused on banking. What follows are stages of evolution rather than a list of jobs: what changed at each step is the scope of accountability.

1. Stage 1

   Engineering foundation

   Software, integration and technical discipline.

   Learning what actually breaks in production, which is what later makes an architecture claim credible.

2. Stage 2

   Solution architecture

   Contracts, boundaries, security and integration.

   The unit of work moves from a component to the agreement between components.

3. Stage 3

   Banking architecture

   Domain, core, journeys and regulation.

   Banking complexity is learned across systems, failures, regulations and institutions over time — not in a single engagement.

4. Stage 4

   Enterprise architecture

   BIAN, TOGAF, domains, standards and governance.

   From designing one system to defining the vocabulary and boundaries several systems have to share.

5. Stage 5

   Transformation architecture

   Brownfield, hybrid, transition and modernization.

   The target state stops being the deliverable: the sequence that reaches it without stopping the bank becomes the deliverable.

6. Stage 6

   Architecture leadership

   Governance, decision systems, executive authority and capability.

   Authority has to be instrumented. A committee without gates, evidence and owners is ceremony.

7. Stage 7

   Technology transformation leadership

   Current scope.

   Leading technical leaders, governing decisions across initiatives, and leaving capability installed in the organization.