Woody Zuill is the leading advocate of mob programming, now called software teaming, an approach in which the whole team works together on the same thing at the same time on the same computer. A software developer for over 40 years, Woody is the co-author of Software Teaming: A Mob Programming, Whole-Team Approach (with Kevin Meadows) and a globally recognized speaker, trainer, and coach who has delivered workshops on every continent except Antarctica. He’s also an instigator behind the #NoEstimates discussion and a lifelong student of what makes teams actually work.
Episode Description
What happens when you put the whole team at one keyboard and keep them there? In this wide-ranging conversation, Woody Zuill traces the path from his earliest experiments with pair programming in the late 1990s through the accidental discovery of mob programming at Hunter Industries to his current thinking on software teaming, AI, and the art of storytelling. Along the way, he reveals how a children’s book illustrator, a musical instrument factory, and a very specific kind of stubbornness about teamwork shaped one of the most distinctive practices in modern software development.
Woody shares the origin story of mob programming with refreshing honesty: how the name was borrowed from someone else’s article, how the practice emerged from simply not wanting to stop working together, and how his early struggles with public speaking led to a decades-long commitment to iterating on the same talks until they shine. The conversation moves through the concept of Team Flow (and why it validated what Woody’s teams were already experiencing), how different teams around the world have adapted software teaming to fit their own rhythms, and why the question “how can five people at one computer be productive?” might be the wrong question entirely.
Whether you’re curious about what mob programming actually looks like in practice, wondering whether AI changes the case for working together, or just want to hear why Woody thinks we’ll stop writing code in programming languages altogether someday, this episode delivers the kind of hard-won, experience-tested insight that only comes from someone who’s been doing the work, and paying attention, for four decades.
Links & Resources
Guest Links
Software Teaming: A Mob Programming, Whole-Team Approach by Woody Zuill & Kevin Meadows
Books & Articles Mentioned
Teaming: How Organizations Learn, Innovate, and Compete in the Knowledge Economy by Amy Edmondson — the book that made Woody wish he’d called it “teaming” from the start
Extreme Programming Perspectives — edited collection containing the original “Mob Programming” article by ThoughtWorks practitioners
Pair Programming Illuminated — early book on pair programming that influenced Llewellyn Falco’s thinking
Team Flow: The Psychology of Optimal Collaboration by Jef van den Hout & Orin C. Davis — research on achieving shared psychological flow in teams
“Big Ball of Mud” by Brian Foote & Joseph Yoder — the classic 1997 paper on the most common software architecture pattern
Tools, Frameworks & Concepts
Software Teaming / Mob Programming — a whole-team approach to software development at one computer
Strong-Style Pairing — Llewellyn Falco’s driver-navigator technique: “For an idea to go from your head into the computer, it must go through someone else’s hands.”
FAST Agile — Fluid Adaptive Scaling Technology, developed by Ron Quartel, is closely related to software teaming
#NoEstimates — discussion and movement around rethinking estimation in software, originated by Woody
Driver-Navigator Pattern — the foundational collaboration technique for pair and mob programming
Team Flow — research concept from Jef van den Hout on achieving collective psychological flow in teams
People Referenced
Llewellyn Falco — inventor of Strong-Style Navigation, creator of ApprovalTests, recommended by Woody for an interview
Amy Edmondson — Harvard professor, author of Teaming
Linda Rising — speaker and author who advised Woody early on to tell stories in presentations
Ken Schwaber — Scrum co-creator; Woody trained with him at the 2007 Scrum Gathering in Portland
Ron Quartel — creator of the FAST framework and experimented with dynamic teaming in Seattle
Jef van den Hout — Dutch researcher at Eindhoven University of Technology, developed the Team Flow model
Mihaly Csikszentmihalyi — psychologist who originated the concept of psychological flow
James Herr — Woody’s collaborator on talks about mob programming and AI
Fred Zuill — Woody’s brother, who described AI as “a rather faulty, somewhat moderately skilled collaboration partner.”
Andrea Zuill — Woody’s wife, children’s book author and illustrator (Wolf Camp, Sweety, Dog vs. Strawberry, and others)
Kevin Meadows — co-author of Software Teaming
Brian Foote & Joseph Yoder — authors of the “Big Ball of Mud” paper
Taiichi Ohno — Toyota Production System pioneer (referenced by Dave)
Topics Discussed
The Art of Iterating on a Talk
Woody opens up about his journey from someone who couldn’t speak in front of five people to a presenter who has addressed audiences of over a thousand. His approach—repeating the same talk title while continually refining the content—runs counter to the conference circuit norm of always delivering something new, but mirrors the iterative principles at the heart of Agile itself.
Key points:
Early advice from fellow speakers (including Linda Rising) shaped his approach: speak about what you know deeply, tell stories, and start with friendly audiences
His wife Andrea’s illustrations became a signature element of his presentations, helping audiences connect emotionally even before absorbing the content
The process of noting audience questions after every talk and incorporating answers into future versions created a natural feedback loop spanning years
From Pair Programming to Software Teaming
The origin story of mob programming traces back through Woody’s pair programming experiments in the late 1990s, an article in Extreme Programming Perspectives, and a series of increasingly larger team experiments that culminated at Hunter Industries around 2011-2012. The naming journey—from mob programming to software teaming—reflects both practical concerns and a deeper philosophical shift.
Key points:
The “mob programming” name came from an article in Extreme Programming Perspectives (circa 2001-2002) by ThoughtWorks practitioners who experimented with groups larger than pairs
Woody dropped “programming” because it excluded testers, product people, and designers; he dropped “mob” because it means “bullying” in some European languages
Amy Edmondson’s Teaming (2012) captured what Woody was already seeing: the ability to work effectively as a team at any moment, not just being assigned to one
The real insight wasn’t a method—it was noticing that software teams never actually worked like teams in other industries (construction crews, bands, sign installation teams)
Team Flow and the Prerequisites for Great Teamwork
Woody connects his team’s experience at Hunter Industries to Jef van den Hout’s research on Team Flow at Eindhoven University of Technology. The academic framework validated what Woody’s teams had felt intuitively—and gave language to the conditions that make it possible.
Key points:
Team Flow requires collective ambition (shared life values), a common goal (the work itself), personal goal alignment, high skill integration, open communication, and mutual commitment
The rock band analogy: shared ambition to be a band, common goal of the music, and personal goals that complement rather than compete (you don’t put six bass players in a group)
Once these conditions are met, continuous improvement happens naturally — you don’t need to impose it through retrospectives or process mandates
Woody reads extensively but approaches research skeptically; Team Flow resonated because it matched his direct experience
Variations in Practice Around the World
Having conducted workshops on every continent except Antarctica, Woody has observed that people everywhere respond similarly to working as a real team—but the specific practices vary widely. Three teams at one San Francisco company each found completely different approaches to the same core idea.
Key points:
One team used timers, one switched drivers on request (”I don’t want to type anymore”), and a third kept one driver until a discrete task was complete—all valid
Cultural differences exist (some cultures discourage challenging your boss, others expect it), but Woody encourages teams to speak their native language while coding for clearer thinking
Woody never intended his starting guidelines to become rules; like Ken Schwaber told his 2007 Scrum class, the framework is a starting spot, not a destination
Ron Quartel’s FAST framework represents a compelling variation: dynamic reteaming every few days based on what the work demands
AI, Learning Debt, and the Enduring Value of Working Together
The conversation turns to AI with both curiosity and caution. Woody sees clear parallels between the navigator role in software teaming and prompting an AI — but warns that speed without understanding creates its own set of problems.
Key points:
The navigator/driver separation in mob programming was essentially prompting before prompting existed: staying at the higher abstraction level while someone (or something) handles the details
Fred Zuill’s description of AI as “a rather faulty, somewhat moderately skilled collaboration partner” captures the current state well
Dave introduces the concept of “learning debt” — when AI generates code using models, libraries, and constructs that the developer doesn’t understand, creating a new and dangerous form of technical debt
Woody references the “Big Ball of Mud” pattern: AI-generated code risks producing an instant version of the architectural mess that normally takes years to develop
The deeper concern: teams may be getting more done, but not more of the right things done — echoing a pattern Woody has seen throughout his career
Storytelling as the Next Frontier
The episode closes with Woody’s emerging interest in storytelling workshops, inspired by watching his wife Andrea’s process as a children’s book illustrator. Her approach—drawing a character thousands of times until it becomes a living thing—mirrors the kind of deep, iterative practice that has defined Woody’s own career.
Key points:
Andrea Zuill’s path from selling prints on Etsy to publishing children’s books began when people kept asking, “What book is that picture from?” — demand preceded supply
Woody sees storytelling as a natural extension of his work: conference talks depend on stories, and many practitioners want to develop this skill
Dave suggests product management as a particularly promising audience for storytelling workshops—great product managers tell stories that bring people on board with vision and customer pain
Woody’s honest reflection on his career’s current inflection point: demand for traditional Agile training is declining, and he’s exploring what comes next while staying true to what he cares about
Hard Boiled Software is hosted by Dave Laribee.
