Original framework
Capability Architecture
The structural layer above individual learning solutions.
Purpose
Organizations accumulate learning solutions without an architecture connecting them. Capability Architecture is the working discipline I use to design that connective layer — how pathways, resources, governance, technology, and support relate to one another.
Core idea
A capability system has structure whether or not anyone designed it. Making that structure explicit — its pathways, ownership boundaries, dependencies, and failure points — is what allows individual interventions to compound instead of accumulate. This is the discipline that connects KSA Flow, AOAS, and EAAS into a single practice.
System architecture
01
Diagnose
Locate the real constraint before designing anything.
02
Map
Make the existing system visible to the people inside it.
03
Architect
Design pathways, layers, and ownership deliberately.
04
Build
Produce the experiences, tools, and support the design requires.
05
Sustain
Maintenance, feedback, and evolution as part of the design.
Application
- Learning ecosystems with overlapping ownership
- Organizations scaling capability beyond a single function
- Post-merger or post-reorganization learning consolidation
- Multi-year capability investment planning
Availability
The public model presents the architectural relationships and representative applications. Implementation tooling, assessment instruments, and the consulting process remain proprietary and are explored in a working conversation.
Evidence and related thinking
Contact
Let's talk about what you want to achieve.
Whether you're building a stronger team, improving onboarding, or looking for someone to lead the work, I'd welcome the conversation.