AI has made building easier.
But building the right thing is still hard.
Ten articles every week on what is happening across product, research, design and engineering. Curated by Rory Madden to help teams decide what to build.
Explore the editions ↓The archive
The Playbook For AI Transformation by John VetanAI transformation stalls when companies treat it as scattered pilots instead of a repeatable cross-functional system. Dedicated facilitators, small decision-making pods, and structured workflow sprints help teams kill weak ideas ear
Read edition ↗The Science Of Social Loafing: Why Groups Kill Individual Effort by Joost MinnaarTeams work better when individual contributions are visible, coordination stays manageable, and people can see how their effort connects to a meaningful goal. Small teams, clear ownership, transparen
Read edition ↗Redesigning Workflows For AI by Jakob NielsenAI creates more value when teams redesign the whole workflow instead of just speeding up one task at a time. Removing handoffs, automating the glue work, and shifting people toward higher-judgment exceptions can unlock bigger gains tha
Read edition ↗Finally, The Handoff Is Dead by Luke WroblewskiAI does not fix collaboration on its own. Teams work better when design decisions, development standards, and project context are carried in a shared system so people can contribute in parallel without losing alignment or creating ha
Read edition ↗Who In The C-Suite Should Own AI? by Toby E. StuartAI initiatives work better when companies stop treating them as the responsibility of one function alone. Clear ownership, shared accountability, and tighter coordination across technology, operations, risk, data, and finance hel
Read edition ↗Demand Mix, Shaping, And AI As (Dys)function Multiplier by John CutlerOrgs spend a lot of time talking about dependencies, intake, predictability, “discovery,” capacity, and so on. But far less time talking about the harder questions around the mix of demand teams are dealing wit
Read edition ↗Organizational Silos: What The Titanic Teaches Us About Information That Never Arrives by Joost MinnaarSilos are usually created by structure, not bad intent, when teams optimize for local metrics instead of shared outcomes. Shorter paths between signals and decisions, more trans
Read edition ↗Will Claude Code Ruin Our Team? by Justin JacksonAI coding is collapsing role boundaries across design, product, and engineering, so teams need new ways of collaborating that preserve shared judgment and respect instead of letting tool access turn cross-functional work into turf
Read edition ↗AI Doesn’t Reduce Work—It Intensifies It by Aruna Ranganathan and Xingqi Maggie AI can make teams faster, but without clear boundaries, it also expands workload, increases context switching, and makes it harder to switch off. Leaders need stronger norms around pace, focus, and re
Read edition ↗When companies launch transformational initiatives, they typically assign them to existing leaders who are already measured on current business KPIs. This creates an inevitable conflict: leaders will always prioritize the metrics they're evaluated on over new strategic projects.
Read edition ↗When companies empower teams without providing strategic context, a predictable pattern emerges: teams make logical decisions based on incomplete information while leadership sees these choices as misguided.
Read edition ↗The most effective visions paint vivid pictures of customer transformation through a systematic four-step approach:
Read edition ↗Most product visions end up as abstract statements that sound impressive but fail to inspire action or drive decision-making. To understand what makes a vision truly powerful, we analysed SpaceX's Mars mission video, which transforms the company from a transportation logistics pr
Read edition ↗