| REFLECTIONS | Culture 2 Teams using Hydrodynamics and Thermodynamics - bdemirjian/apbr2 GitHub Wiki

Purpose

Provide an analogy for culture and teams that can help leaders understand systems thinking, through the lens of the Theory of Constraints.

hydro1

Hydrodynamics of an organization The Oiled Wheels approach

Hydrodynamics of Local Optimization

Unaided water draining from an inverted wine bottle.

Key take-aways

A small amount drains, then a vacuum forms causing a stoppage of the flow of water, until a bubble of air passes all the way through to relieve it. This Stop-Start-Stop-Start whiplashing causes the entire system to THRASH with LOCAL OPTIMIZATIONS!

System Characteristics | Local Optima

  • Turmoil inside the system (notice the vortices/turbulence, very much like when a wave crashes on the beach)
  • There is a lot of activity but it does not increase the rate of flow.
  • There are many unproductive conflicts
  • Many internal processes that do not add value
  • Becomes captive of its own internal processes (think TPS report, silliness)

Spin Assist | Alignment of the Org to flow

Key take-aways

2x improvement over unaided approach. Effectively subordinates all other priorities to flow.

System Characteristics | Naturally Fastest Flow

  • In the neck of the bottle both air and water are moving at the same time, and in opposite directions
  • Air has it's own continuous uninterrupted path
  • Water has it's own continuous uninterrupted path
  • All parts of the system are aligned to facilitate the continual paths of both Water and Air

Intentional Assist | Straw-breather with starting "Puff"

Key take-aways

4x improvement over unaided and 2x over spin assisted approach.

System Characteristics | intentionally fastest

  • The system is calm and stable
  • Note the absence of both turmoil and pressure
  • Doing the right things right

Thermodynamically Stable Team Test (Rayleigh-Bernard Convection)

Ideally once a calm and stable system is established, the focus can shift to developing atomic teams.

Top View

rbc

Profile view

profile

Video explanation

Steve Mould

Key take-aways

The teams are stable and change over long periods of time. Work flows through teams at a very fast pace.

System Characteristics | intentionally fastest

  • Atomic teams, in that all the parts to deliver the "large" work item are within the team, minimal dependencies.
  • System defined guardrails are set to best serve the teams balanced by preventing local optimizations.
  • Teams are making decisions within the framework of the system defined guardrails.
⚠️ **GitHub.com Fallback** ⚠️