Leveraging Lean UX to Lead Successful Agile Teams

The old waterfall approach (and its scrum-friendly variants) to product development is dead. The new way is a collaborative, continuous cycle of concepting, delivering, learning, and iterating. In this workshop Jeff Gothelf will show you how to use product discovery practices to build a stronger collaboration with product development teams. Challenge current ways of working to improve the integration of UX, product management and engineering in the Agile process. You will develop management strategies to ensure the customer is present in every product conversation and ensure cross-functional collaboration is present at the leadership level.

The day in details

During the first half of the day, you’ll work individually and in small groups to understand how Lean UX should work by defining work as a problem statement to solve, declaring assumptions, writing Objectives and Key Results (OKRs), forming hypotheses, creating proto-personas, brainstorming opportunities, and designing experiments using “the two key questions” method. In the afternoon, you’ll use these same techniques to identify your current challenges implementing and leading your agile practices in your organizations and define ways to improve them along with clear, human-centric measures of success (OKRs).

You’ll see how to

Implement OKRs successfully and use this goal-setting technique to ensure Lean UX happens in every initiative.

Encourage cross-functional collaboration based on real data.

Structure experiments to test your hypotheses and continuously iterate.

Implement Lean UX in a way your development and leadership teams can buy into.

Use the ideas of continuous learning and iteration to change how you lead your design teams.

Use behavior–not just for customers but for your team too–to determine how well the process is working and what needs to change.

Lead the adoption of customer-centered practices in your company’s Agile process.

Focus relentlessly on outcomes.

Collaborate on building a customer-centric backlog of features by forming assumptions and testing hypotheses.