Search

Find insights, training programs, and workshops

Intermediate to Advanced6-8 hoursAgent use case map + architecture blueprint + governance framework

AI agents — what they are, how they work, the protocols shaping them (MCP, A2A), and the governance you need before you let one act on your behalf. The bridge between AI that talks and AI that does.

...Complex multi-step tasks Planning overhead Reflection Generates output, evaluates it, improves it Quality-critical outputs Multiple iterations ReAct is the foundation pattern — most agent frameworks...

2 DaysIntensive

Agent DesignWorkshop

AI Agents Agentic AI MCP A2A Multi Agent Systems AI Orchestration View Details

AI Capabilities, Limitations & Use Cases

Beginner to Intermediate3-4 hoursTask-to-AI fit judgment + reference materials

What AI is genuinely good at, where it will let you down, and how to match the right task to the right tool. The judgment you need before you touch a prompt.

...meeting note, a report, an email thread. Now transform it three ways: Transformation Your prompt Result quality (1-5) e.g. Turn this into a 3-bullet summary e.g. Rewrite for a non-technical audience...

Half DayIntensive

Beginner FriendlyNo math required

Generative AI AI Capabilities AI Limitations Hallucination Use Cases AI Fluency View Details

Build / Buy / Partner / Participate — Ecosystem Strategy

Intermediate to Advanced (SA, EA, TS)5-6 hoursBuild/buy/partner/participate decision framework + vendor and ecosystem evaluation scorecard + exit and switching cost analysis template

How to decide what to build, what to buy, what to access through partners, and what to participate in through ecosystems — covering differentiation vs commodity analysis, vendor evaluation, total cost of ownership, interoperability velocity, exit strategy, and lock-in risk.

...Differentiator Bought Yes — build If your sourcing doesn't match your classification, you're either wasting engineering effort or giving away your advantage. When to build — What to own because it creates competitive...

1 DayIntensive

StrategicSA · EA · TS

Architecture Sourcing Strategy Ecosystem Build vs Buy Vendor Management Strategy View Details

How Architects Think

All levels — SA, EA, TS5-6 hoursSystems thinking toolkit + abstraction ladder + decision heuristics reference card

The cognitive toolkit of architecture — systems thinking, abstraction, balancing business and technical concerns, deciding under uncertainty, and trade-off thinking. Builds the mindset, not just the knowledge.

...communicated three different ways. To an executive: "We are consolidating to reduce cost and risk." To engineering: "We are merging three services into one using the strangler fig pattern over six months."...

1 DayIntensive

MindsetNot just methods

Architecture Foundations Systems Thinking Decision Making View Details

Delivery Metrics That Mean Something

Engineering Managers, Tech Leads, VP Engineering, CTOs3-4 hoursA delivery scorecard — four DORA signals plus a five-dimension maturity baseline with one named bottleneck

How to replace delivery dashboards that measure activity with signals that tell you which dimension is actually holding delivery back — and what to fix first.

...move from insight to execution? This measures the mechanical speed of the decision system, not the quality of the decisions. Low: decisions wait in queues, approvals and review cycles for weeks. High:...

1 DayIntensive

EvidenceNot feeling

Delivery Metrics DORA Architecture Maturity Governance View Details

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.

...Process debt — missing reviews, no CI/CD, manual testing. Detected by process audit. Medium cost — quality and speed impact. Knowledge debt — key-person dependencies, no cross-training. Detected by team...

1 DayIntensive

StrategicSA · EA · TS

Architecture Technical Debt Rationalisation Modernisation Governance View Details

AI in the Workplace

Beginner to Intermediate3-4 hoursPersonal AI workflow map + role-specific use case library

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.

...learn the mode. Naming the mode before you prompt is a small habit with a noticeable effect on output quality. It focuses both your brief and the model's attention on exactly what you need. Try it yourself...

Half DayIntensive

Beginner FriendlyNo math required

AI in the Workplace Generative AI Productivity AI Fluency Use Cases AI Workflows View Details

Paying Down Debt Through Feature Work

CTOs, Engineering Leaders, Enterprise Architects, Product Leaders3-4 hoursA feature-driven debt reduction policy — the rule, the visibility mechanism, and the two questions review asks about every feature

Debt accumulates faster than refactoring projects can remove it. Fund architecture improvement through the product roadmap instead of competing with it.

...in 60 days Putting it all together Cheat sheet Before we start — the one thing to hold onto Every engineering organisation recognises technical debt. Teams say: we should refactor this, this module needs...

1 DayIntensive

ContinuousNot a project

Technical Debt Architecture Evolution Product Delivery Governance View Details

Technology Strategy & Architecture Strategy

Advanced (EA, TS)5-6 hoursTechnology strategy vs architecture strategy distinction map + strategy brief template

How to distinguish technology strategy from architecture strategy, connect both to business strategy, and define a coherent direction for the organisation's technology investments.

...observability). Q2: Integration layer (event broker, API gateway). Q3: Data mesh (domain ownership, quality gates). Q4: Self-service (golden paths, templates)." Architecture strategy = vision + principles...

1.5 DaysIntensive

StrategicEA · TS

Architecture Technology Strategy Business Strategy Direction Enterprise Context View Details

Execution Stability & Structured Refactoring

CTOs, Engineering Directors, Principal Engineers, Engineering Managers3-4 hoursA classified structural risk map — your top friction modules sorted into dicing, slicing and peeling with a governance rule attached

Delivery slows because structural entropy accumulates unmeasured. Classify refactoring into dicing, slicing and peeling to restore predictability.

...because there is no incident to point at. Refactoring is usually treated as cleanup. It is structural engineering for long-term execution stability. Without method, refactoring becomes emotional. With structure,...

1 DayIntensive

LayersNot cleanup

Execution Stability Refactoring Delivery Predictability Structural Risk View Details

1 2 3 4