Webinar: How organisations are meeting
the productivity challenge by applying
Team Topologies
Matthew Skelton and Ben Dodd
1
Slide 2
Slide 2 text
Photo goes here
Ben Dodd
Co-founder & CTO, Armakuni
20 years in technology, product, & engineering
in global & regulated organisations
Slide 3
Slide 3 text
Photo goes here
Matthew Skelton
Founder, Conflux
Co-author of Team Topologies
Slide 4
Slide 4 text
How organisations are meeting the productivity
challenge by applying Team Topologies:
➔ Stop obsessing over individual productivity
and start thinking in terms of multi-team flow
➔ Switch from “managing dependencies” to
“flow unblocking” and “boundary finding”
➔ Accelerate effective adoption via a partner
like Armakuni or Conflux
4
Slide 5
Slide 5 text
5
The actual productivity challenge
Platforms for non-blocking flow
The role of managers: finding flow
Success patterns with TT
Slide 6
Slide 6 text
Team Topologies
Organizing business and
technology teams for fast flow
Matthew Skelton & Manuel Pais
IT Revolution Press, September 2019
Order via stores worldwide:
teamtopologies.com/book
6
Slide 7
Slide 7 text
7
The actual
productivity
challenge
Slide 8
Slide 8 text
Macro: There has been
a productivity challenge
since 2008
8
Slide 9
Slide 9 text
Macro: The need to do more
with the same people
& cost base
9
Slide 10
Slide 10 text
Macro -> Micro:
There is a need to scale &
the status quo doesn’t scale
10
Slide 11
Slide 11 text
Micro: Bring creativity and
joy to our customers and
organisations
11
Slide 12
Slide 12 text
Most business are
fundamentally not designed
for the fast flow of value
12
Slide 13
Slide 13 text
Many organizations have
pre-digital operating
models that are not
suited to fast flow.
13
Slide 14
Slide 14 text
14
Platforms for
non-blocking flow
Slide 15
Slide 15 text
Team Topologies provides:
➔ Language for dealing with flow,
boundaries, architecture, dynamics
➔ Heuristics (clues) for organizing
teams and software
➔ A focus on fast flow as a key driver
15
Slide 16
Slide 16 text
16
Slide 17
Slide 17 text
17
Slide 18
Slide 18 text
18
Flow of change
“Platform grouping”
Slide 19
Slide 19 text
The purpose of a
platform* is to improve
flow and reduce team
cognitive load for teams
using the platform.
* in a Team Topologies sense
19
Slide 20
Slide 20 text
Track dependencies
and separate as
“blocking” vs
“non-blocking”
20
Slide 21
Slide 21 text
⏳ ⏳
Blocking
Non-
Blocking
21
Slide 22
Slide 22 text
Use the 4 Key Metrics
from Accelerate
and add “wait time”
22
Slide 23
Slide 23 text
4 key metrics: ‘Accelerate’
lead time
deployment frequency
Mean Time To Restore
change fail percentage
Organising for atomic teams
& reduced context switching
42
Slide 42
Slide 42 text
Connect your organisation
to the existing communities
that can support you
43
Slide 43
Slide 43 text
Define a new way to engage
partners who can enable you
in realising fast flow
44
Slide 44
Slide 44 text
➔ Visualise flow as a norm
➔ Build shared language
➔ Enable clarity of focus
➔ Invest in community
➔ Find flow-enabling partners
45
Slide 45
Slide 45 text
46
The actual productivity challenge
Platforms for non-blocking flow
The role of managers: finding flow
Success patterns with TT
Slide 46
Slide 46 text
Many organizations have
pre-digital operating
models that are not
suited to fast flow.
47
Slide 47
Slide 47 text
Modern platforms should
be obsessed by flow and
wait times in teams
consuming the platform.
48
Slide 48
Slide 48 text
Managing for flow is
more effective (and
satisfying!) than managing
for deadlines and dates.
49
Slide 49
Slide 49 text
We need to visualise flow
and, with flow-aligned
support, retain new
capabilities to unblock it
50
Slide 50
Slide 50 text
How organisations are meeting the productivity
challenge by applying Team Topologies:
➔ Stop obsessing over individual productivity
and start thinking in terms of multi-team flow
➔ Switch from “managing dependencies” to
“flow unblocking” and “boundary finding”
➔ Accelerate effective adoption via a partner
like Armakuni or Conflux
51