Fight the big ball of mud with business capability mapping
summary
10+ teams and 60+ developers already produce over 30 services and surface about 40 capabilities; a two-person tech+BA pair reads Confluence, ADRs and diagrams, runs one-hour validation sessions per team, then runs a two-hour workshop in Miro. The result is a visual Miro map that exposes duplication, fragmented and missing capabilities, and ownership confusion so teams reassign responsibilities, remove accidental replicas, and leave with a clearer, progressively maintainable capability map.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:05Business capabilities and uses
- 3:54Problem of no guiding capabilities
- 5:20Project background
- 7:06Five red flags
- 14:16Constraints and need for action
- 16:05Building capability map
- 17:29Research and first draft
- 18:53Visualizing the map
- 23:05Workshop to validate
- 26:59Team conversations
- 28:47Key takeaways
related talks
42mCapability Mapping
59mModelling Stories of the Beautiful Mess
25mHow to Drive Cross Team Techincal Changes
24mBusiness Value Over Architecture?
24mShaped by demand: The power of fluid teams
16mScaling Teams with Ownership
46mEstablishing Business Agility at the Bank
47mMicroservices and the Inverse Conway Manoeuvre