Find insights, training programs, and workshops
How to build, read, and use the full picture of what an organisation runs — every application, platform, integration, and technology — and how they depend on each other.
Quick Navigation Start here — Why landscape mapping matters What to capture How to build the landscape Reading the landscape Technology...
The AI tools landscape — what the major platforms are, how they actually differ, and how to choose the right one for the right job. Stop chasing every new launch. Start making deliberate choices.
Quick Navigation Why the landscape feels overwhelming — and how to fix that Layer 1 — Foundation models: the engines underneath Layer...
Most platform teams build internal products their engineering teams never chose. Platform adoption is not a marketing problem. It is a product governance problem. Here is the model that fixes it.
...None of these appear in the platform report. They do not appear anywhere — until someone maps the full landscape and discovers that the organisation is maintaining five deployment pipelines, three secret...
How to document what exists today, define what must exist tomorrow, and design the transition states that get you there — the discipline of architecture that connects present reality to future goals.
...points explicitly. Outdated — documented 2 years ago, never updated. Fix: link to living artefacts — landscape, dependency maps. Too detailed — every class and method documented. Fix: focus on significant...
Applying AI in real work contexts — across roles, tasks, and teams. Move from knowing what AI is to using it every day, without hype, without fear, and without wasting time on the wrong things.
...your desk has your name on it, not AI's. That's the whole model. Everything else in this guide is an application of it. Try it yourself — The colleague test Think of the last AI output you used without...
How architecture manages technical risk and meets regulatory obligations — covering architectural risk analysis, compliance by design, privacy by design, security controls as decisions, operational risk, control points, and demonstrating compliance through architecture.
Quick Navigation Start here — What architectural risk is Regulatory landscape Privacy by design Security controls as decisions Operational risk Control points Demonstrating...
How the structure of technology teams shapes the structure of the systems they build — covering Conway's Law, centralised vs federated models, platform teams, product operating models, team topologies, and designing the organisation that produces the architecture you want.
...that teams adopt without deciding. Clear boundaries — platform provides the foundation; teams own the application. Platform team responsibilities: CI/CD — pipeline templates, deployment automation. They...