About this episode

The episode explores the disconnect between Agile's original intent and its current practice, emphasizing the importance of design principles in achieving true Agile outcomes.

In this inaugural episode, Pavel and I dig into the history and dysfunction of Agile, not to relitigate waterfall vs. Agile, but to examine why modern Agile practice has drifted so far from its original intent. We explore how the Agile manifesto was written entirely without designers in mind, how the "Scrum industrial complex" turned a flexible philosophy into a rigid checklist, and why two-week sprints often amount to waterfall in disguise. We cover the critical role of feedback loops, the danger of prioritizing outputs over outcomes, and why shared problem understanding is what teams actually need. We also make a case that good design principles are the closest thing we have to a genuine fix, because design is built around the kind of iterative, goal-questioning thinking that Agile always promised and rarely delivered. Guest Bio Pavel Samsonov (he/him) is a Principal Experience Designer at Justworks in New York. His approach to product & UX draws from his research at Nielsen Norman Group, experience building design practice at AWS, and managing product teams at Bloomberg. Pavel often describes himself as a Problem Designer, because the biggest influence on the solution is…

People in this episode

Host: Guy Segal

Guest: Pavel Samsonov

Topics covered

• Agile methodology
• design principles
• feedback loops
• product design
• team collaboration

Keywords

• Agile
• design
• Scrum
• feedback loops
• product teams
• iterative thinking
• problem framing

Mentioned in this episode

Organizations: Justworks, Nielsen Norman Group, AWS, Bloomberg

Explore listener stats, chart rankings, contacts and more on the Design Downtime podcast page.