Skip to content

Search

Find insights, training programs, and workshops

Application & Technology Landscape
All levels — SA, EA, TS4-5 hoursApplication landscape register + technology heat map + dependency matrix

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.

...application and technology landscape is the full picture of what an organisation runs — every application, platform, integration, and technology — and how they depend on each other. It's the foundation for every...

1 dayIntensive
PracticalLandscape exercise
Technology, Infrastructure, Cloud & Security Design
Intermediate to Advanced (SA, EA)6-8 hoursInfrastructure decision framework + cloud pattern reference + security controls map

Where abstract architecture meets physical reality — choosing the platforms, compute, networking, and security controls that make the solution work at scale.

...onto Architecture decisions live in the abstract until they're made real by technology choices — the platforms, the compute, the networking, the security controls. I've seen teams choose technology for...

2 DaysIntensive
PracticalSA · EA
AI-Native Teams Don't Need New Titles. They Need Named Owners.
AI-Native Teams Don't Need New Titles. They Need Named Owners.

AI-native team redesigns keep adding new job titles and calling it done. The actual failure mode sits at the decision boundary. Here is what changes when you apply AIDRA to team design instead of headcount.

Executive Summary Who this is for: CTOs, VPs of Engineering, Heads of Platform, Engineering Directors, Team Leads adopting agentic workflows Problem it solves: AI-native team...

Developer Experience Is Not a Perk. It Is a Delivery Control System.
Developer Experience Is Not a Perk. It Is a Delivery Control System.

Developer experience is not about making developers happy. It is about controlling the conditions that determine delivery output. Organizations that treat DX as a perk have removed the control system from their delivery engine without knowing it.

Executive Summary Who this is for: CTOs, Engineering Leads, Platform Engineering Teams, Architecture Review Boards, Engineering Managers Problem it solves: Organizations...

Monitoring Added After Deployment Is Not Observability. It Is Archaeology.
Monitoring Added After Deployment Is Not Observability. It Is Archaeology.

Observability is not a monitoring add-on. It is an architectural constraint. Systems built without observability baked in cannot be understood, cannot be governed, and cannot be improved. The OSAF model tells you exactly where your architecture is blind.

Executive Summary Who this is for: CTOs, Platform Engineers, Enterprise Architects, Engineering Leads, System Design Owners Problem it solves:...

Security Is Not a Gate. It Is an Architecture Property.
Security Is Not a Gate. It Is an Architecture Property.

Security is treated as a gate at the end of delivery. It should be an architecture property designed into three distinct boundaries. Here is the model that fixes the friction between security and delivery.

Executive Summary Who this is for: CTOs, CISOs, Enterprise Architects, Platform Engineering Leads, Heads of Engineering Problem it solves: Security is treated as a gate at...

AI Procurement, Vendor Evaluation & Tool Selection
Beginner to Intermediate3-4 hoursVendor evaluation scorecard + tool selection checklist + risk review template

Choosing AI tools is not a beauty contest. Learn how to evaluate vendors, compare capabilities, assess risk, avoid lock-in, and buy systems that your organisation can actually govern and adopt.

...integration Running pilots that reveal the truth How to run a sane selection process The politics of platform choice The selection model in one diagram Cheat sheet Before we start — why buying AI is unusually...

Half DayDecision Focused
Vendor SelectionPractical
Cognitive Load & Team Interfaces
VP Engineering, Platform Leads, Engineering Managers, Principal Engineers3-4 hoursCognitive load assessment per team, an interaction model, and a platform team charter naming what the platform does and does not own

A team can only hold so much — and the interaction modes between teams are what decide whether that limit is respected or quietly exceeded.

...carrying Four team shapes that respect the limit Three interaction modes — the interface is the design The platform as the load-absorbing interface Golden paths, dirt roads, and the museum problem Measuring whether...

1 DayIntensive
CapacityWhat a team can hold
Developer Experience as a Control System
CTOs, Engineering Leads, Platform Engineering Teams, Engineering Managers3-4 hoursA delivery friction map across four sprints, one named constraint pillar, and a traced DX-to-delivery signal

DevEx is not a perk — it is the set of operating conditions that governs how fast and how safely change moves through your delivery system.

...is holding the yield down. Two things make this cheaper to sustain than to start. Friction that a platform can absorb should be absorbed there rather than measured forever — which is where this joins...

1 DayIntensive
ConditionsNot satisfaction
Batch vs Real-Time Is the Wrong Debate.
Batch vs Real-Time Is the Wrong Debate.

Organisations debate batch versus real-time as if it is a technical preference. It is not. It is a structural mismatch between data freshness and decision cadence — and the mismatch is where the cost lives.

Executive Summary Who this is for: CTOs, Data Architects, Enterprise Architects, Platform Engineering Leads Problem it solves: Organisations choosing data pipeline patterns based on...

123···9