Describe a time you faced significant resistance or conflict from a key stakeholder or team regarding a critical operational change you were championing. How did you navigate this disagreement, what framework (e.g., CIRCLES, SCARF) did you employ to understand their perspective, and what was the ultimate outcome?

Employ the CIRCLES framework: Comprehend the situation by actively listening to concerns. Identify the stakeholder's underlying motivations and fears (e.g., job security, resource allocation). Report back their concerns to confirm understanding. Create a solution collaboratively, incorporating their valid points. Lead the implementation, ensuring their involvement. Evaluate the impact and share credit. This structured approach ensures all perspectives are heard and integrated into a more robust solution, fostering buy-in.

I once championed a significant operational shift to an agile methodology across our product development and engineering teams. The Head of Engineering, a key stakeholder, expressed strong resistance, citing concerns about increased overhead, loss of control, and potential delays to critical roadmap items. I employed the SCARF (Status, Certainty, Autonomy, Relatedness, Fairness) framework to understand his perspective. I recognized his 'Status' was challenged by a new process, 'Certainty' was low due to unknown outcomes, and 'Autonomy' felt threatened. I addressed these by involving him in the agile steering committee, providing clear training roadmaps and pilot project data to increase 'Certainty,' and empowering his team to customize certain agile ceremonies to maintain 'Autonomy.' We collaboratively developed a phased implementation plan, starting with a non-critical project. The ultimate outcome was a successful transition, leading to a 20% reduction in time-to-market for new features within six months, and the Head of Engineering became a vocal advocate for agile practices.