Slide 1
Slide 1 text
Towards Architecture Topologies for
Sustainable Fast Flow of Change
Eduardo da Silva, PhD
Independent consultant on sociotechnical systems, architecture & leadership modernization
(esilva.net consulting | [email protected])
NewCrafts, 2024/05/16
Slide 2
Slide 2 text
Towards Architecture Topologies for
Sustainable Fast Flow of Change
Eduardo da Silva, PhD
Independent consultant on sociotechnical systems, architecture & leadership modernization
(esilva.net consulting | [email protected])
NewCrafts, 2024/05/16
Ability to respond fast &
sustainably to the environment
Slide 3
Slide 3 text
esilva.net 3
Photo by Simon Berger on Unsplash
Slide 4
Slide 4 text
esilva.net 4
Photo by Simon Berger on Unsplash
Learning:
“learning about
the problems &
opportunities in
the environment”
Slide 5
Slide 5 text
esilva.net 5
Photo by Simon Berger on Unsplash
Learning:
“learning about
the problems &
opportunities in
the environment”
Designing:
“explore and
design options to
address the
problem or
opportunity”
Slide 6
Slide 6 text
esilva.net 6
Photo by Simon Berger on Unsplash
Learning:
“learning about
the problems &
opportunities in
the environment”
Designing:
“explore and
design options to
address the
problem or
opportunity”
Decision-Making:
“decide on designs
and take action to
make things
happen”
Slide 7
Slide 7 text
esilva.net
‼ Modern orgs that are not nurturing conditions for
sustainable Learning, designing and decision-making
will struggle to respond to their environment
7
Photo by Cole Patrick on Unsplash
Learning:
“learning about
the problems &
opportunities in
the environment”
Designing:
“explore and
design options to
address the
problem or
opportunity”
Decision-Making:
“decide on designs
and take action to
make things
happen”
Slide 8
Slide 8 text
esilva.net
In our lives, we are continuously
Learning, designing and deciding
…to respond to unexpected events
8
Slide 9
Slide 9 text
esilva.net 9
Slide 10
Slide 10 text
esilva.net
Strange
burning
smell…
10
Slide 11
Slide 11 text
esilva.net 11
Learning…
Slide 12
Slide 12 text
esilva.net 12
Designing
&
Deciding…
Slide 13
Slide 13 text
esilva.net 13
Learning…
Slide 14
Slide 14 text
esilva.net 14
Designing
&
Deciding…
Slide 15
Slide 15 text
esilva.net 15
4:32 AM
(first coffee)
Slide 16
Slide 16 text
esilva.net 16
Slide 17
Slide 17 text
esilva.net 17
Slide 18
Slide 18 text
esilva.net 18
9:14 AM
(workshop
starts at
9:30)
Slide 19
Slide 19 text
esilva.net 19
I made it
(~20 min
late)
Slide 20
Slide 20 text
esilva.net 20
Slide 21
Slide 21 text
esilva.net 21
Photo by Simon Berger on Unsplash
Slide 22
Slide 22 text
esilva.net 22
💡Move towards org cultures, structures and incentives
that allow us (particular people close to problems) to
navigate and respond to the uncertain & fast changing
environments we “live in”
Photo by Ronaldo de Oliveira on Unsplash
Slide 23
Slide 23 text
esilva.net
🎯 Sustainable Fast Flow of Change Operating Models 🌳
23
Sociotechnical Systems Evolution & Architecture, Eduardo da Silva
Slide 24
Slide 24 text
esilva.net
🎯 Sustainable Fast Flow of Change Operating Models 🌳
24
Sociotechnical Systems Evolution & Architecture, Eduardo da Silva
Learning
Designing
Decision-
making
Slide 25
Slide 25 text
esilva.net
🎯 Sustainable Fast Flow of Change Operating Models 🌳
25
Sociotechnical Systems Evolution & Architecture, Eduardo da Silva
Learning
Designing
Decision-
making
🎯We want to
continuously
go fast &
sustainably
over this
“cycle”
(from ideas
to value in
front of the
customer)
Slide 26
Slide 26 text
esilva.net
🎯 Sustainable Fast Flow of Change Operating Models 🌳
26
Sociotechnical Systems Evolution & Architecture, Eduardo da Silva
Learning
Designing
Decision-
making
🎯We want to
continuously
go fast &
sustainably
over this
“cycle”
(from ideas
to value in
front of the
customer)
How can we do that?
Slide 27
Slide 27 text
esilva.net
🎯 Sustainable Fast Flow of Change Operating Models 🌳
27
Sociotechnical Systems Evolution & Architecture, Eduardo da Silva
“Language” to help us
discuss how we
organize and evolve
our teams (& org) to
support sustainable
fast flow of change
Learning
Designing
Decision-
making
Slide 28
Slide 28 text
esilva.net
❓But, how are we understanding, discussing and improving our
approaches to architecture (Learning, Designing and Decision-making)?
28
In the teams
Across teams
Across the org
Slide 29
Slide 29 text
esilva.net
Architecture Topologies
🎯 Thinking models and practices to
understand and evolve the approach
to Architecture (Learning, Designing
and Decision-making) in the
different scopes of the organization
🔗 esilva.net/architecture-topologies
29
Slide 30
Slide 30 text
esilva.net
“Language” to
help us discuss
how we
understand and
improve our
approach to
architecture to
support
sustainable fast
flow of change
Architecture Topologies ❤ Team Topologies
30
Learning
Designing
Decision-
making
“Language” to
help us discuss
how we organize
and evolve our
teams (& org) to
support
sustainable fast
flow of change
…towards a Sustainable Fast Flow
of Change Operating Models
Slide 31
Slide 31 text
esilva.net
Architecture Topologies (ATs) Map
31
💡 example of
visualization we
can use to discuss
& understand
existing approaches
and points for
improvement
ℹ this is just one
example of visualization,
we can use other
practices, such as Team
Topologies Interaction
Models, and other things
Slide 32
Slide 32 text
esilva.net
Architecture Topologies (ATs) Map
32
Maturity of
Architecture
Capability
Slide 33
Slide 33 text
esilva.net 33
*Would you like architects with your architecture? | images credits: Gregor Hohpe
Some Categories of Approaches to Architecture*
(Stefan Toth)
💡this is a
gradual
evolution…
which will
take years
to develop,
and will
vary from
team to team
(Architecture Capability
for Sustainable Fast Flow of Change)
💡does not
mean there
is no clear
ownership!
Slide 34
Slide 34 text
esilva.net
❓what about “architecture” across teams, or across the org?
34
In the teams
Across teams
Across the org
Slide 35
Slide 35 text
esilva.net
Architecture Topologies (ATs) Map
35
How are we
approaching
Architecture on the
different scopes of
the org (and across
them)?
Slide 36
Slide 36 text
esilva.net
Architecture Topologies (ATs) Map
36
💡We use this together with
people involved in these
different scopes, to
understand and identify
opportunities to improve our
approach to architecture?
Slide 37
Slide 37 text
esilva.net
Architecture Topologies (ATs) Map
37
⚠Architecture
from outside the
scope
Architecture
Approach
Slide 38
Slide 38 text
esilva.net
Architecture Topologies (ATs) Map
38
⚠Architecture
from outside the
scope
Architecture
Approach
Learning
Designing
Decision-making
“learning about
the problems &
opportunities in
the environment”
“explore and design
options to address
the problem or
opportunity”
“decide on designs
and take action to
make things happen”
Slide 39
Slide 39 text
esilva.net 39
Architecture
Approach
Learning
Designing
Decision-making
ℹ example of a mapping from
a big org, with many teams
and architects working with
multiple teams
Slide 40
Slide 40 text
esilva.net 40
Architecture
Approach
Learning Designing Decision-making
💡different
parts of the
same
organization
have different
ways of
approaching
architecture…
and different
challenges
Slide 41
Slide 41 text
esilva.net 41
Architecture
Approach
Learning Designing Decision-making
Outcome of this collaborative mapping:
⇢ Identification of important constraints 🚫
After this, we can:
⇢ Explore options to address constraints 📈
⇢ Define how to continue doing this 🔁
Slide 42
Slide 42 text
esilva.net
…having ways of improving how we approach
Architecture is key… as it is/should be changing, as
things in and around the company are changing
42
Slide 43
Slide 43 text
esilva.net 43
bol.com 1999 - 2019
Slide 44
Slide 44 text
esilva.net 44
bol.com 1999 - 2019
🧐 I joined the
company in 2017.
A year of
interesting
product releases…
📚🍻👠
Slide 45
Slide 45 text
esilva.net 45
Tech
Arch
Org
(&
Way
of
Work)
Prod
&
Events
Tech
Org
(&
Way
of
Work)
bol.com 1999 - 2019 (Org + Tech + Architecture evolution)
Arch.
Slide 46
Slide 46 text
esilva.net 46
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall
Phase 1 (1999 - ~2010): Waterfall, monoliths & centralized arch
Arch. Centralized (by Architects)
Prod
&
Events
Slide 47
Slide 47 text
esilva.net 47
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall
Phase 1 (1999 - ~2010): Waterfall, monoliths & centralized arch
Arch. Centralized (by Architects)
⚠
“need for scaling”
Prod
&
Events
Slide 48
Slide 48 text
esilva.net 48
Architects
doing all
the design
& decision
making
Slide 49
Slide 49 text
esilva.net 49
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall
Phase 1 (1999 - ~2010): Waterfall, monoliths & centralized arch
Arch. Centralized (by Architects)
⚠
“need for scaling”
Prod
&
Events
Slide 50
Slide 50 text
esilva.net 50
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall Agile DevOps Teams
(Micro)services
~30
~10
Phase 2 (~2010 - ~2018): Autonomous Teams
Arch. Centralized (by Architects) Teams + Archs
“need for scaling”
Prod
&
Events
⭐ these are structural
changes - org + tech +
arch, it is not just
introducing yet another
process!
Slide 51
Slide 51 text
esilva.net 51
Architecture
in teams
done by the
teams;
architects
doing
architecture
around teams
Slide 52
Slide 52 text
esilva.net 52
Architecture
in teams
done by the
teams;
architects
doing
architecture
around teams
Slide 53
Slide 53 text
esilva.net 53
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall Agile DevOps Teams
(Micro)services
~30
~10
Phase 2 (~2010 - ~2018): Autonomous Teams
Arch. Centralized (by Architects) Teams + Archs
“need for scaling”
Prod
&
Events
Slide 54
Slide 54 text
esilva.net 54
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall Agile DevOps Teams
(Micro)services
~30
~10
Phase 2 (~2010 - ~2018): Autonomous Teams
Arch. Centralized (by Architects) Teams + Archs
“need for scaling”
Teams capable of
iterating
quickly on their
scope
Prod
&
Events
Slide 55
Slide 55 text
esilva.net 55
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall Agile DevOps Teams
(Micro)services
~30
~10
Phase 2 (~2010 - ~2018): Autonomous Teams
Arch. Centralized (by Architects) Teams + Archs
“need for scaling”
Teams capable of
iterating
quickly on their
scope
Able to deploy
quickly and
independently
Prod
&
Events
Slide 56
Slide 56 text
esilva.net 56
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall Agile DevOps Teams
(Micro)services
~30
~10
Phase 2 (~2010 - ~2018): Autonomous Teams
Arch. Centralized (by Architects) Teams + Archs
“need for scaling”
Teams capable of
iterating
quickly on their
scope
Able to deploy
quickly and
independently
Teams able to
design and
decide things
on their scope
Prod
&
Events
Slide 57
Slide 57 text
esilva.net 57
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall Agile DevOps Teams
(Micro)services
~30
~10
Phase 2 (~2010 - ~2018): Autonomous Teams
Arch. Centralized (by Architects) Teams + Archs
“need for scaling”
Many
teams
Prod
&
Tech
Silos
Prod
&
Events
Slide 58
Slide 58 text
esilva.net 58
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall Agile DevOps Teams
(Micro)services
~30
~10
Phase 2 (~2010 - ~2018): Autonomous Teams
Arch. Centralized (by Architects) Teams + Archs
“need for scaling”
Many
teams
Prod
&
Tech
Silos
Organic net of
Microservices
Prod
&
Events
Slide 59
Slide 59 text
esilva.net 59
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall Agile DevOps Teams
(Micro)services
~30
~10
Phase 2 (~2010 - ~2018): Autonomous Teams
Arch. Centralized (by Architects) Teams + Archs
“need for scaling”
Many
teams
Prod
&
Tech
Silos
Organic net of
Microservices
Architects
overwhelmed
“keeping
things
together
around teams”
Prod
&
Events
Slide 60
Slide 60 text
esilva.net 60
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Tech
Org
(&
Way
of
Work)
Waterfall Agile DevOps Teams
(Micro)services
~30
~100
~10 ~600
Phase 2 (~2010 - ~2018): Autonomous Teams
Arch. Centralized (by Architects) Teams + Architects (anything around teams)
⚠
⚠
⚠
⚠
“need for
sustainable fast
flow of change”
Prod
&
Events
Slide 61
Slide 61 text
esilva.net 61
Architects
managing a
lot of the
“things”
around the
teams &
teams being
“islands”
Slide 62
Slide 62 text
esilva.net
● Team scope has all
disciplines needed
(⭐including “product” and
“tech” => NO SILOS!)
● Product scope groups teams
working on related value
streams (e.g., Inspire to
Buy has Recommendation and
Search Teams), with
Enabling Product Leadership
Improving Organization Structure & Architecture
62
Product Taxonomy, Ross Clanton, Amy Walters, Jason Zubrick, Pat Birkeland, Mik Kersten, Alan Nance, and Anders Wallgren
Slide 63
Slide 63 text
esilva.net 63
Teams owning
architecture
on their
scope with
clearer
alignment to
the
multi-team
scope they
are part of
(with
Enabling
Architects,
PMs & EMs)
Slide 64
Slide 64 text
esilva.net 64
Teams owning
architecture
on their
scope with
clearer
alignment to
the
multi-team
scope they
are part of
(with
Enabling
Architects,
PMs & EMs)
Slide 65
Slide 65 text
esilva.net 65
Teams owning
architecture
on their
scope with
clearer
alignment to
the
multi-team
scope they
are part of
(with
Enabling
Architects,
PMs & EMs)
💡“Architecture
as Enabling Team”
Slide 66
Slide 66 text
esilva.net 66
Tech
Arch
Org
(&
Way
of
Work)
Monoliths
Products
Tech
Org
(&
Way
of
Work)
Waterfall Agile
Product Teams
DevOps Teams
(Micro)services
~30
~100
~10 ~600 ~50
Phase 3 (~2017 - ??): Product organization
Arch. Centralized (by Architects) Teams + Architects (anything around teams)
Teams (+ Enabling Product Architects)
“need for
sustainable fast
flow of change”
Prod
&
Events
Slide 67
Slide 67 text
esilva.net
Products
Waterfall Agile
Product Teams
DevOps Teams
~30
~100
bol.com 1999 - 2019
67
“need for scaling” “sustainable fast
flow of change”
💡change is
continuous and
takes time and
support from
leadership
Slide 68
Slide 68 text
esilva.net 68
⭐ Our business changes, and so is the way we organize
our teams and systems and how we approach architecture
(learning, designing and decision-making)
Slide 69
Slide 69 text
esilva.net 69
⚠ Change & Uncertainty will not stop
✅ Embrace it, and make sure you evolve your
organization structures & approach Architecture to
address that (▶ Sustainable Fast Flow Operating models)
Photo by Ronaldo de Oliveira on Unsplash
Slide 70
Slide 70 text
esilva.net
Thank you!
Eduardo da Silva, PhD
Independent consultant on sociotechnical systems, architecture & leadership modernization
Team Topologies Valued Practitioner (TTVP)
# esilva.net consulting
# [email protected] | emgsilva
esilva.net/products ⬇
ℹmore products
coming soon
ℹthe topic of this talk is
covered in these workshops &
sessions:
https://esilva.net/products/effe
ctive-architecture-topologies
https://academy.teamtopologies.com/
courses/effective-enabling-teams