Get the free Core Drives in the Wild guide, behavioral design applied to real products: professorgame.com/WildCD
Episode Summary
Rob breaks down why a product can feel stitched together even when every team involved did excellent work, using Conway's Law as the lens: organizations that design systems are constrained to produce designs that copy their own communication structures. He walks through three real cases, a regional sales dashboard at Procter & Gamble where each region had picked a defensible and incompatible way to count sales, a client engagement where technology decision rights sat with a team that carried none of the consequences, and a project where several functions held contradicting views on what the design should optimize for. The argument is that functionality degrades gracefully under that fragmentation while motivational design does not, because the effect lives in the loop between Core Drives rather than in any single mechanic. Listeners learn where organizational seams show up inside the product and how to test for alignment before any design work starts.
About the Host
Rob Alvarez is Head of Engagement Strategy, Europe at The Octalysis Group (TOG), a leading gamification and behavioral design consultancy. A globally recognized gamification strategist and TEDx speaker, he founded and hosts Professor Game, the #1 gamification podcast, and has interviewed hundreds of global experts. He designs evidence-based engagement systems that drive motivation, loyalty, and results, and teaches LEGO® SERIOUS PLAY® and gamification at top institutions including IE Business School, EFMD, and EBS University across Europe, the Americas, and Asia.
Key Takeaways
- Melvin E. Conway argued in Datamation that organizations which design systems are constrained to produce designs that copy their own communication structures, which is why a product built across four departments reaches the user as four products.
- At Procter & Gamble, every region had chosen a defensible way to count sales, with its own aggregation rules and its own view of the target, so a single regional dashboard failed on reconciliation rather than on SKU volume or technical complexity.
- When the team that picks the technology carries none of the consequences of that choice, the decision optimizes for minimizing spend rather than for the problem the product owner is accountable for delivering.
- Functionality degrades gracefully under organizational fragmentation, because a fragmented dashboard is still a working dashboard. Motivational design does not degrade gracefully, because the effect lives in the loop, so reordering or removing pieces collapses it.
- Contradicting business metrics across functions is the failure that stops a project rather than slowing it. Business metrics are the first input to the design, so changing them after delivery means redesigning a significant part of the experience.
- Before any design starts, ask four people from four different departments what this product should optimize for. Matching answers mean design can begin. Different answers mean the alignment work comes first.
Topics Covered
- 0:00 - Opening hook, everybody did great work
- 0:30 - The single sales dashboard problem
- 1:35 - Where Conway's Law comes from
- 2:18 - First case, every region counted sales differently
- 5:06 - Second case, decision rights sat elsewhere
- 8:34 - Why functionality degrades gracefully
- 9:05 - Why motivational design does not
- 11:29 - Third case, contradicting business metrics
- 14:53 - Comparing the three failures
- 16:30 - Specialization and owning the whole result
Mentioned in This Episode
Free Resources and Get in Touch
