Search

Find insights, training programs, and workshops

Solving Technical Debt Through Feature Development: Turning Product Delivery into Architecture Improvement
Solving Technical Debt Through Feature Development: Turning Product Delivery into Architecture Improvement

A practical framework explaining how organizations can systematically reduce technical debt while delivering new features, instead of running disruptive modernization programs.

...architecture.” But deadlines arrive. Product features take priority. Refactoring is postponed. Months later: Systems become harder to change Development velocity slows Incident risk increases Engineers grow frustrated...

Your On-Call Log Is Your Real Org Chart.
Your On-Call Log Is Your Real Org Chart.

Why on-call rotation data is the most accurate org chart your engineering organisation has — and almost nobody uses it to make structural decisions.

...ownership will work this way. The hypothesis was reasonable when it was formed. Teams were smaller. Systems were newer. The failure modes were unknown. Six months later, the systems have grown. Teams have...

MCP Is Not an AI Protocol. It Is a Governance Layer.
MCP Is Not an AI Protocol. It Is a Governance Layer.

MCP is classified as an AI integration protocol. It is actually a governance primitive — the stable interface layer that architecture fitness functions have been missing for years.

...rewire the entire building. The test point still returns the right answer. The first inspector had deep knowledge of the implementation. The second inspector had a stable interface to the outcome. Most architecture...

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.

...the one thing to hold onto Most organisations don't have an accurate picture of what they're running. Systems were built by different teams, in different years, for different reasons. Nobody mapped the whole...

1 dayIntensive
PracticalLandscape exercise
Why Architecture Exists
All levels — SA, EA, TS3-4 hoursArchitecture purpose framework — complexity · alignment · risk · change · shared understanding

Why architecture exists — managing complexity, aligning technology with business, reducing risk, enabling change, and creating shared understanding across teams.

...together Cheat sheet Before we start — the one thing to hold onto Architecture exists because without it, systems become unmaintainable. I've seen teams add features, take shortcuts, watch people leave, lose...

Half-dayIntensive
PurposeWhy it matters
Effective Prompt Engineering
Beginner to Advanced6-8 hoursFull prompt design framework + personal prompt library

Every major prompt engineering technique — from basic clarity to advanced agentic reasoning. Not a list of tips. A mental model you can apply to any task, any tool, any context.

...answer Step-Back — zoom out first Least-to-Most — build up from simple Advanced techniques — for production systems, agentic workflows, maximum quality Prompt Chaining — one task per prompt Generated Knowledge...

2 DaysIntensive
19 TechniquesComplete Coverage
Application, Integration, API, Interface, Data & Process Design
Intermediate to Advanced (SA, EA)6-8 hoursIntegration design playbook + API design standards + data movement pattern guide

How the components of a solution are structured internally, how they communicate with each other, and how they connect to the data and processes they depend on.

...between them. I've seen clean component models that couldn't implement the business process — and messy systems where every boundary was an illusion because two components could write the same data. Solution...

2 DaysIntensive
ComprehensiveSA · EA
Current State & Target State Architecture
All levels — SA, EA, TS4-5 hoursAs-is / to-be architecture canvas + transition state design + maturity scale + AI readiness assessment

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.

...state: It's always messier than anyone wants to admit. It includes technical debt, workarounds, tribal knowledge, and shadow IT. Documenting it honestly is uncomfortable — but it's the only way to plan realistically....

1 dayIntensive
PracticalCanvas exercise
Technology Leadership & Organizational Excellence
Intermediate to AdvancedLeadership roadmap and team enablement plan

Learn to lead high-performance engineering organizations with clear decision rights, distributed leadership, and AI-augmented team management for the future of work.

...culture erodes. Examples or metaphors: Air traffic control — coordinates from a distance, relies on systems and protocols Orchestra conductor — doesn't play instruments but elicits coordinated performance Gardener...

2 DaysWorkshop
Coming Soon
Technical Debt & Rationalisation
Intermediate to Advanced (SA, EA, TS)5-6 hoursTechnical debt taxonomy + rationalisation prioritisation framework + modernisation criteria

How to understand, measure, prioritise, and reduce technical debt — the accumulated cost of shortcuts, outdated decisions, and deferred maintenance.

Quick Navigation Start here — What technical debt is Types of debt The cost of debt Legacy systems Rationalisation strategies Prioritising debt reduction The politics of technical debt Debt interest...

1 DayIntensive
StrategicSA · EA · TS