Kevin Jones | Tech Lead
Describe a team structure that you have found works well and why you think it was successful
– The brief
Works well?
What do we measure?
Structuring Teams
What matters when considering your future structure?
Mr Conway
Where do you split the teams, and why?
Cognitive load,
Why does it matters for success?
Team size
What size should it be, what does it impact?
Team anatomy
Does the right anatomy make much difference?
Collaboration
How do you optimise communication between teams?
Flow of value or change through the system.
Metric - Time it takes ideas to reach the customer
Signals that allow you to course correct.
Metric - time to acknowledge incidents.
Cinch is a team of teams
A network of people & systems
Aim for team stability
Aim for efficacy
Avoid Bottlenecks/handovers
Expect it to evolve, experiment
Any organisation that designs a system (defined broadly) will produce a design whose structure is a copy of the organisation’s communication structure.
– Mr Conway, 1968
A product's architecture tends to mirror the structure of the organisation within which it is developed
– Mr MacCormack et al. 2008
7 ± 2
Mr Bezos says 2 pizzas 🍕
Smaller teams
Closer relationships
More trust
Quicker decisions
Less lines of communication
Leans into cognitive load
Avoid overloading teams with complexity. Limit the size of the software system to the cognitive load the team can handle.
– Team Topologies*
– Team Topologies*
* Paraphrased it slightly
Headspace is finite
Performance sweet-spot
Don't overload your small team
Search + Recommendations
So?
Experimentation thrives
Raises team sense of satisfaction
The right people in the right seats, keeps value flowing
Good anatomy creates:
ownership - ship it, own it
autonomy - minimise dependencies & make decisions
Key roles keep the squad aligned with the wider business
Efficiency between teams
Types
Search is value aligned
Enabling teams like the principles or delivery
Platform teams like infra
Complex sub-systems BCA Data (Ziggy)
How we work with these teams
Collaboration
x-as-a-service, low cognitive load
Facilitated by the enablers
Describe a team structure that you have found works well and why you think it was successful
– The brief
Works well
Flow + Feedback
Structuring Teams
Efficient network, stability, avoid bottleneck
Mr Conway
Architecture imitates organisation... teams first
Cognitive load,
Just the right amount..
Performance and happiness lever
Team size
7 +/-2
Trust, quick decisions
Team anatomy
Autonomous, empowered, aligned teams
Collaboration
Efficient, deliberate collaboration across different team types
Always room for improvement though. Every day is a school day
– Me