About a year ago, I was leading my first discovery workshop for the Clarios project. I had meticulously prepared the agenda, mapped out the frameworks, and brought all the technical context to the room. But mid-session, while navigating a complex discussion with stakeholders, I froze. The momentum stalled, and for a brief moment, I couldn’t find the way forward.

My manager stepped in, reframed the question, and seamlessly got the room moving again.

That moment stayed with me. At first, it felt like a tactical stumble. But looking back, it turned out to be one of the most pivotal leadership lessons of my career. It completely reshaped how I view my role as a Lead Product Designer and Process Architect.

Here are three core shifts in perspective that came out of that experience:

1. From “Problem Solver” to “Facilitator of Clarity”

As designers, we are conditioned to believe our value lies in delivering immediate, polished solutions. When faced with stakeholder ambiguity, the instinct is to jump in and show the “right way.”

The truth is, design leadership isn’t about having all the answers on the spot. It’s about building a structured space where non-designers—engineers, business analysts, domain experts—can articulate their constraints and ideas. Your job isn’t to be the smartest person in the room; it’s to synthesize collective intelligence into actionable direction.

2. Embracing the Pause Without Panic

Freezing during a workshop usually happens when you try to solve a multi-layered problem live in front of an audience.

Learning to pause, ask clarifying questions, or even say, “Let’s map this constraint on the board before we jump to solutions,” turns potential friction into a collaborative exercise. Silence or uncertainty during discovery isn’t failure; it’s a signal that you’ve reached the core complexity that needs unravelling.

3. Managing Ideas Is Service Design for Teams

Every stakeholder enters a discovery session with a different mental model, priority, and fear. When ideas clash or conversation stalls, it is rarely due to a lack of technical expertise—it is a lack of alignment.

Guiding a team through discovery is essentially applying Service Design principles to human collaboration. By visualizing workflows, aligning definitions, and helping people organize their own thoughts, you empower the team to own the solution together.

Final Thoughts

Great facilitation isn’t about executing a perfect deck without hesitation. It’s about being comfortable in the ambiguity, listening deeply, and helping everyone in the room find clarity.

Leadership is not declaring the path forward—it’s helping the team build it.