The document discusses aligning organizational and technical boundaries to maximize team autonomy. It notes there is often an alignment crisis seen in lots of meetings, teams being blocked, integration chaos, and a blame culture. This costs organizations in terms of low motivation, agility, and user experience. The document proposes that whole-team continuous organization design may help solve the alignment crisis. It provides several strategies for improving alignment, such as defining autonomy contexts, evolving boundaries based on new insights, and adapting organization design with technical strategy.
5. THERE IS AN ALIGNMENT CRISIS
Image: Christer Sandahl (cpdm.com), Complex Product Development Model
6. THERE IS AN ALIGNMENT CRISIS
Image: Christer Sandahl (cpdm.com), Complex Product Development Model
Signs
• Lots of meetings
• Teams blocked
• Integration chaos
• Blame culture
Costs
• Low motivation
• Low Agility
• Bad UX
12. @ntcoding
Current State Context Map
Resubmit
Case
Management
Ratepayers Caseworkers
= Digital IT frontend team
= Enterprise IT team
Review
Renegotiate
Rules Engine/
Orchestration
13. @ntcoding
Bounded Context Clues
• contextual language
• data: flow, ownership, uniqueness
• domain expert boundaries
• existing organisation boundaries
• business strategy / core pieces
• business process steps
14. @ntcoding
Future State Context Map
Resubmit
Renegotiate
Review
Ratepayers Case workers
= Full stack team
= Composite application
20. @ntcoding
Finding Service Boundaries: The One Rule
that Matters…
Maximise your ability to frequently deliver
value and get feedback
ntcoding.co.uk/blog/2017/01/finding-service-boundaries-one-rule
23. @ntcoding
No Bottlenecks - Nothing Wrong Here
Search
Web Store
Music
Lovers
Catalogue
Payments
Media
Streaming
API
Platform
24. @ntcoding
“We had 10 teams… we analyzed the
bottlenecks… we ended up with 3 cross-
functional teams… lead times improved
massively
Anna Dick, Coop Digital
@Dixi_chick
25. @ntcoding
“The point of microservices is to unblock
independent queues of work. Both in
the system of services, and the system
of people.
Andrew Clay Shafer
@littleidea
33. @ntcoding
“Trade off collaboration costs [between
teams] with innovation speed based on
current organisational needs
Matthew Skelton
@matthewpskelton
39. @ntcoding
“…provide stable, secure, high
performance services and to deliver,
innovative, technology-intensive services
quickly. Bimodal IT provides a way to
address both
www.gartner.com/it-glossary/bimodal
41. @ntcoding
“Bi-modal is founded on the the idea that
quality is something you trade-off for
speed. It's a common notion, but a false
one.
Martin Fowler
@martinfowler