Loading
Loading
Most organisations accumulate digital infrastructure the same way they accumulate any other asset: one decision at a time, in response to immediate operational needs, without a governing architecture. A new sales team needs a CRM — one is purchased. A new website is needed — an agency is engaged. Marketing wants automation — a platform is selected. Finance needs reporting — a dashboard is built. Each decision is locally sensible. The aggregate is a fragmented digital environment where systems do not communicate, data cannot flow between functions, and the cost of operating and maintaining the infrastructure grows every year. An enterprise systems architect addresses this at the level of the whole — not any individual system, but the structure of how all systems relate to each other and serve the organisation's strategic objectives.
At the strategic level, systems architecture involves mapping an organisation's current digital infrastructure — every system, every data flow, every integration, every vendor relationship — and assessing how effectively this infrastructure serves the organisation's operational and strategic objectives. It then involves designing a target architecture: what the infrastructure should look like to serve those objectives more effectively, and a prioritised roadmap for getting from the current state to the target state. At the execution level, systems architecture involves designing the specific technical systems that implement the strategic architecture — the data models, the integration patterns, the API contracts, the deployment infrastructure. And at the oversight level, it involves ensuring that technology decisions made across the organisation are consistent with the governing architecture, and that individual system decisions do not create problems for the whole.
Not every organisation needs an enterprise systems architect. Small organisations with simple digital infrastructure and modest growth ambitions may find that good execution of individual systems is sufficient. But the need for systems architecture expertise typically emerges at specific inflection points. When digital infrastructure complexity has grown to the point where changes in one system regularly break other systems. When data that should flow between functions requires manual extraction and re-entry. When the cost and effort of maintaining existing systems is consuming budget that should be available for new investment. When the organisation is about to make a significant technology investment and wants to ensure it fits into a coherent architecture. When a platform migration is on the horizon and the risk of getting it wrong is significant.
An engagement with an enterprise systems architect typically begins with a discovery phase — a structured assessment of the organisation's current digital infrastructure, its strategic objectives, and the gap between the two. This produces a current-state architecture map and an initial assessment of the most significant architectural issues. It is followed by a target architecture design — what the infrastructure should look like to serve the organisation's objectives — and a prioritised roadmap for implementation. The architect may then be retained to oversee implementation, making architecture decisions as the build progresses and ensuring that the final system matches the intended design. Or the roadmap may be implemented by internal teams or specialist vendors, with the architect available for architectural review and decision support.
The most important qualification for a systems architect, beyond technical competence, is independence. An architect employed by a technology vendor will design architectures that favour their employer's products. An architect employed by a system integrator will design architectures that generate implementation work. An independent architect — with no vendor relationships and no downstream revenue from implementation — can assess the options honestly and recommend what genuinely serves the organisation's interests. For consequential architectural decisions, this independence is not a minor consideration. It is the difference between counsel you can trust and counsel that is shaped by incentives you may not be aware of.
Independent systems architect and digital strategist. I build digital infrastructure for organisations that cannot afford to get it wrong.