Enterprise · Solution · Security Architecture
Architecture at enterprise scale
27 years designing and delivering complex enterprise solutions across applications, data, integration, cloud, infrastructure, identity, AI and cyber security — from current-state assessment and option analysis through target architecture, technical decisions, governance and implementation support.
I am an architect first.
Enterprise architecture connects the business, technology and security decisions. Cybersecurity, OT security and AI security are integrated into that design.
Architecture in numbers
Architecture domains
My architecture work spans the full lifecycle: Discover → Define → Assess → Design → Decide → Govern → Deliver → Assure → Evolve.
Enterprise Architecture
Strategy translation, capability alignment, target states, transition architectures, roadmaps, architecture principles and portfolio-level governance.
ARCHITECTEDDELIVERED
Solution Architecture
End-to-end designs across application, data, integration, infrastructure and security domains with option analysis, non-functional requirements and Architecture Decision Records.
ARCHITECTEDDELIVERED
Data & Integration
Information flows, logical/physical models, API-first design, event-driven architecture, SCIM, SAML/OIDC, Kafka/AMQP, Azure Service Bus, hybrid and legacy integration.
ARCHITECTEDDELIVERED
Cloud & Platform
Azure landing zones, hybrid architectures, workload migration, identity, network, compute, containers, data platforms and platform services.
ARCHITECTEDDELIVERED
Security Architecture
SABSA · TOGAF · Zero Trust · identity · PAM · segmentation, cloud security, security-by-design and resilience.
ARCHITECTEDDELIVERED
AI Architecture
Azure OpenAI · Azure AI Search · Document Intelligence · Semantic Kernel · RAG · enterprise AI platforms with access controls, data protection, observability and governance.
ARCHITECTEDDELIVERED
Architecture artefacts I produce
Architecture work is made tangible through artefacts, not adjectives. Every substantial engagement produces a defined artefact set:
Vision & Strategy
- Architecture Vision
- Business Capability Map
- Architecture Principles
- Technology strategy
Current & Target
- Current-State Architecture
- Target-State Architecture
- Transition Architecture
- Reference Architecture
Solution
- Solution Context Diagram
- Application Architecture
- Integration Architecture
- Deployment Architecture
Data
- Data Flow Diagram
- Logical Data Model
- Information classification
- Data governance controls
Security
- Trust Boundary Model
- Identity Architecture
- Threat Model
- Security control mapping
Governance
- Architecture Decision Records
- Non-Functional Requirements
- Technology Options Assessment
- Risk & Dependency Register
- Architecture Roadmap
Architecture Principles I work by
01 · Start with the problem, not the technology.
Technology selection follows business outcomes, constraints and measurable requirements — not vendor pressure.
02 · Architect for the whole context.
Applications, data, integration, infrastructure, identity, security, operations, users and organisational constraints must be considered together.
03 · Prefer reuse to reinvention.
Existing platforms, capabilities, patterns and standards should be reused where they provide appropriate strategic fit.
04 · Make decisions explicit.
Important architectural decisions require documented context, alternatives, rationale and consequences — every time.
05 · Design for change.
Architecture should accommodate evolution rather than optimising only for the immediate release.
06 · Security is a design property.
Identity, privacy, resilience and threat controls belong inside the solution architecture — not bolted on afterwards.
07 · Delivery validates architecture.
Architecture is only successful when engineering teams can implement and operate it.
08 · Make trade-offs visible.
There is rarely one perfect architecture; cost, risk, performance, complexity and time are balanced deliberately, in writing.
Architecture with delivery depth
I have remained technically close to implementation throughout my architecture career. Depending on programme scope, hands-on architecture work has included:
- Prototyping architecture decisions and validating Azure configurations
- Reviewing APIs, integration specifications, schemas and data flows
- Writing and reviewing KQL, interrogating logs and telemetry
- Validating network / security / identity controls and reviewing deployment pipelines
- Defining infrastructure and platform configurations
- Troubleshooting design-to-production issues with engineering, platform and vendor teams
Explore
Architecture Patterns & Playbooks
Reusable architecture assets — Enterprise Identity Control Plane, Azure Secure Landing Zone, RAG Reference Architecture, Operational Resilience and more.
Data & Integration Architecture
Information architecture, APIs, event-driven systems, data platforms, analytics and governed data exchange.
Public Sector Architecture
Alignment with public-sector digital-service, cloud, interoperability and data-standards principles.
Case Studies
Programme-level architecture evidence — problem, decisions, artefacts, delivery role, outcome.