Kanban Architecture is architecture pulled by need, not pushed by function. It assumes a BCM and CDM are in place, with specialist extensions and refinements to meet a business challenge. The intent is to empower people in Gemba, the same way Ukrainian troops innovate and improve on the fly. They don’t have endless committees and meetings, just the skills, trust, shared purpose, and the will to do it. And do it time and time again.
It uses AI, shared models, and governed knowledge to help people create or adapt architectural views when they need them, in the form they can use.
The purpose is not to replace architects.
It is to make architectural knowledge available at the point of work.
- A team improving a process may need a value stream view.
- A data owner may need the CDM relationships behind a report.
- A manager may need the capability affected by a system change.
- A product team may need to see where AI changes work, decisions, data, and accountability.
- A governance forum may need a consequence map before approving an intervention.
In this model, architecture becomes a pull-based learning system.
- The Knowledge Base provides the foundation.
- AI helps translate that knowledge into useful working views.
- People at Gemba test those views against reality.
- Architects steward the integrity of the underlying models.
- The organisation learns through use.
This is the shift from architecture as artefact to architecture as workwear.
Related Source Notes
- Kanban Architecture
- Governance
- Accountability
- Decision Rights
- Consequential Intervention
- Organisational Coherence
- Trust as Adaptive Infrastructure
- Organisational Awareness
- Triple Bottom Line and the Balanced Scorecard
Related Subject Areas
- Enterprise Architecture & Operating Model
- Organisational Learning Ecosystem
- Sustainability & Regeneration
- Organisational Awareness
- AI, Human Collaboration & Dialogue Design