Skip to content

Search

Find insights, training programs, and workshops

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.

...without changing system topology. What it looks like: renaming ambiguous variables; breaking long functions; reducing cyclomatic complexity; eliminating duplication; improving unit test coverage. When...

1 DayIntensive
LayersNot cleanup
Execution StabilityRefactoringDelivery PredictabilityStructural RiskView Details
Architecture Governance
Intermediate to Advanced (SA, EA, TS)5-6 hoursGovernance model canvas + architecture principles register + escalation path template

How to design, implement, and measure architecture governance — the mechanisms that ensure decisions are made consistently, applied correctly, and aligned with strategy.

...defaults, and delegation to enforce standards without human bottlenecks. The lightweight toolkit: Fitness functions — automated tests that verify architecture constraints in CI/CD. Defaults — sensible...

1 DayIntensive
PracticalSA · EA · TS
ArchitectureGovernancePrinciplesDecision MakingControlView 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.

...same two questions can be backed by continuously evaluated checks rather than asked in a meeting — see Fitness Functions Instead of Review Boards. Evidence from practice An e-commerce company I worked with...

1 DayIntensive
ContinuousNot a project
Technical DebtArchitecture EvolutionProduct DeliveryGovernanceView Details
What Architecture Is
All levels — SA, EA, TS3-4 hoursArchitecture definition canvas + what it is / what it isn't reference card

What software and enterprise architecture actually is — its structure, relationships, and decisions — and what it is not. No diagrams. No jargon. Just clarity.

...hold this up: Structure — what the parts are. Components, services, layers, platforms. Not individual functions or classes — the things that teams build around. Relationships — how the parts connect and...

Half-dayIntensive
FoundationFor all roles
ArchitectureFoundationsDecision MakingView Details
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.

...late Design for failure, security, scale Change enablement Every change is expensive Loose coupling, fitness functions, evolutionary design Shared understanding Teams build inconsistent systems ADRs,...

Half-dayIntensive
PurposeWhy it matters
ArchitectureFoundationsComplexityBusiness AlignmentView Details
12