Tuckman was Wrong — Dynamic Teaming
summary
Claims that Tuckman’s staged model is generally true are rejected with evidence: a comprehensive study finds 2% of teams actually follow forming→storming→norming→performing in order, and storming recurs even on high performers. Concrete costs are measured: context switching (~20% per concurrent project) turns four eight‑hour tasks from 32h into ~48.75h; high utilization degrades throughput. Stable teams clearly cut multitasking and create slack but breed silos, so organizations adopt patterns like mitosis, trading places, and temporary task teams to redistribute skills.
AI-written summary · about
chapters (5)
related talks
01h 00mDynamic Teams - Fluidity for the win
50mBut First, the Team!
49mHow to Speed Up Development and Engage Your Team in Pursuit of Good Results
27mTrust Driven Teams Building High Performance Through Connection
37mBut First, The Team!
49mTeam? What Team?
01h 37mDynamic Reteaming, The Art and Wisdom of Changing Teams
01h 05mSoftware Teaming (Mob Programming) and the Power of Flow.