Enterprise architecture that is useful — not academic, not ceremonial, not a shelf document.

The Challenge

Most organisations that invest in enterprise architecture end up with one of two problems: too much or too little.

Too much: a heavyweight EA programme producing ArchiMate models that nobody reads, a governance body that slows decisions without improving them, and an architecture team disconnected from the delivery teams trying to build things.

Too little: no shared vocabulary for capability conversations, business and IT strategies that diverge quietly over time, duplicate investments nobody notices until the audit, and a technology estate that has grown faster than anyone’s understanding of it.

The right answer is neither extreme. It is just enough architecture, just in time — positioned to serve the business, not to serve the architecture function.

What This Engagement Covers

Enterprise Architecture Consulting is a structured engagement to build or mature your organisation’s EA capability — from establishing the foundations to running a functioning, connected practice that leadership actually uses.

What You Get

  • Capability mapping — A business capability model that provides the shared vocabulary for investment decisions, business-IT alignment, and portfolio rationalisation. Capabilities, not processes or org charts, as the stable organising layer
  • EA landscape assessment — A structured view of where your organisation sits across the enabling/isolation/barrier/losing quadrant. An honest maturity baseline with a clear path forward
  • Business, application, and technology architecture — Documented landscape across all three layers, connected — so a business change can be traced to the applications it affects and the technology it runs on
  • Architecture governance design — Lightweight, decision-useful governance: architecture principles, review cadence, decision rights, and the minimum viable process to ensure architectural coherence without bureaucracy
  • EA framework alignment — Practical application of TOGAF, ArchiMate, and Zachman where they add value, without the certification-driven overhead that slows things down
  • Stakeholder engagement model — How to position EA with the board, with delivery teams, and with the business — so it is seen as a service, not a constraint

Engagement Formats

  • EA foundations — For organisations starting from scratch: vocabulary, governance, first capability model, initial landscape documentation. Typically 6-10 weeks.
  • EA maturity programme — For organisations with an existing EA function that is not delivering the value it should. Assessment, redesign, and embedding. Scoped by current state.
  • Advisory and coaching — Ongoing support for an internal EA team or architect: sounding board, pattern review, stakeholder preparation.

Who This Is For

  • Organisations starting an EA practice who want to do it right from the beginning, without the overhead of a methodology-heavy approach that alienates delivery teams before it delivers value
  • Leadership teams frustrated that IT investment decisions are made without a shared business capability lens — where nobody can answer “which systems support this capability?”
  • CTOs and chief architects inheriting a technology estate that has grown faster than its documentation, and who need a credible way to re-establish strategic clarity
  • EA functions that exist but are stuck in isolation — producing outputs nobody requests and missing the conversations that matter
  • Organisations preparing for a significant programme — digital transformation, M&A integration, platform rationalisation — that need an architectural foundation in place before the change begins

The Pragmatic Difference

Academic EA is about frameworks. Pragmatic EA is about decisions. The question is not “which framework are you using?” It is “what decisions does your leadership need to make, and what architecture do they need to make them well?”

TOGAF, ArchiMate, and Zachman are tools. The goal is a business that makes better technology decisions, faster, with less regret. That starts by understanding where you are in the enabling/isolation/barrier/losing quadrant — and choosing the next step deliberately.

💡 Tip

“Enterprise architecture that your CEO finds useful is more valuable than enterprise architecture that your EA certification body would approve of.”

Start With a Conversation

EA engagements are highly context-dependent. Schedule a free 60-minute discovery call to discuss your current state, what is working, what is not, and what a right-sized EA engagement would look like for your organisation.