In this episode of the Product Design for Learning Podcast, host Greg Arthur speaks with Arash Mazanani, a dynamic learning leader from Aggreko, about the critical Understand Phase in product design, particularly in the context of learning solutions. They dive into the importance of this phase, which involves thoroughly exploring problems and defining requirements before moving into solution-building. Arash shares his insights on how to guide stakeholders, ask the right questions, and ensure that learning products meet both business objectives and employee needs.

Arash Rezeai-Mazanani is a learning professional with over a decade of experience in FTSE 100 and private equity companies. He specialises in leadership development, global transformation, and human-centred design. His approach centres on experimentation and disruptive thinking to create meaningful, business-aligned solutions that address employee challenges.

• The Understand Phase serves as a North Star, helping guide teams by clarifying project goals and focusing efforts.
• Asking the right questions during this phase is critical to uncovering the real problem behind requests.
• Arash stresses the importance of curiosity and using techniques like the Toyota "5 Whys" to dig deep into stakeholders' needs.
• Starting with what people need to do rather than what they need to know ensures that learning solutions are practical and impactful.
• Stakeholder management is key: defining who should be involved and why helps streamline projects and avoid late-stage derailments.
• Don’t rush the Understand Phase; it's vital to get a comprehensive understanding before moving to the next phase.

Arash explains how everyone has a "swanky" version of their job title but emphasises the daily challenges professionals face, including doubt and striving for improvement.

Arash describes the Understand Phase as a guiding force that provides direction and clarity. Without defining the problem, projects risk scope creep or lack of focus.

Arash emphasises curiosity and asking lots of questions to really get to the heart of the problem. Understanding assumptions and the true drivers behind requests is essential.

Arash advises avoiding this by ensuring key stakeholders are involved from the start. He shares strategies for addressing late-stage interventions if they occur.

Arash discusses the importance of identifying stakeholders with clear roles and responsibilities. Keeping stakeholder groups tight helps avoid unnecessary delays and misalignment.

Arash stresses the importance of asking whether all aspects of the problem have been fully explored, using the "think, feel, do" model to make sure no stone is left unturned.

Arash suggests encouraging stakeholders to share all their ideas upfront, then parking those ideas until the appropriate phase. This allows for a more focused problem-solving approach.

Arash recommends staying curious, enjoying the journey, and making the Understand Phase a non-negotiable...