This one is deceptively long and I think I spent too much time on the setup and ran out of steam before getting to the actual disagreement part, which is clearly what they care about.
Choose a project with clear cross-boundary complexity and a measurable outcome, then narrate it as a story: context, conflict, resolution, result, reflection. Emphasize how you built trust and aligned incentives rather than just coordinating tasks, and be explicit about what you learned about influence without authority.
Pro tip: Meta values impact and self-awareness—quantify the outcome (e.g., shipped X weeks earlier, saved Y engineering hours) and show you understand the other teams' priorities, not just your own. End with a specific, actionable change you've already applied to a later project.
Briefly describe the project, its importance, and the cross-boundary scope (orgs, geographies, functions). State the concrete goal and why it required alignment across teams.
Name the key stakeholders and their priorities, then pinpoint where those priorities conflicted. Show empathy by explaining why each side held their position.
Explain the specific actions you took to get everyone aligned: e.g., facilitated a workshop, created a shared doc, ran a pilot, or found a compromise that addressed core concerns.
Walk through a specific disagreement and how you resolved it—e.g., by escalating with data, reframing the problem, or building consensus one-on-one. Highlight your communication style.
Quantify the result (e.g., shipped on time, reduced risk, improved process). Reflect on what you learned about influencing without authority and what you would do differently next time.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.