Resolve a Cross-Functional Data Disagreement

The source reported repeated questions about cross-functional collaboration in a senior-level hiring-manager screen, but not their exact wording. Use this representative practice prompt: Tell me about a high-stakes data decision where Product, Engineering, Operations, or another partner disagreed with your recommendation. How did you uncover the real disagreement, use data without overstating it, and help the group reach and execute a decision? ### Constraints & Assumptions - Use a real example involving at least two functions. - The conflict must concern a meaningful decision, not merely a scheduling inconvenience. - Do not portray partners as irrational or make yourself the lone hero. - Separate facts, assumptions, values, and ownership boundaries. - A good outcome can be a clearer decision, a safe test, or a reasoned decision not to proceed; unanimous agreement is not required. ### Clarifying Questions to Ask - Would you prefer an example involving metric definition, launch risk, prioritization, or technical feasibility? - Should I emphasize the disagreement itself or the execution after the decision? - How much organizational context would be useful? ### Part 1: Diagnose the Disagreement Explain the decision, stakeholders, incentives, and consequences. Identify whether the disagreement was about evidence, uncertainty, goals, constraints, or risk tolerance. **Hint:** People can agree on the data and still disagree because they optimize different outcomes. #### What This Part Should Cover ```premium-lock What This Part Should Cover ``` ### Part 2: Create a Decision Process Describe how you established common metrics, tested disputed assumptions, communicated uncertainty, and proposed options. Explain how you influenced without misusing analytical authority. **Hint:** Pair each unresolved claim with evidence, an owner, or a reversible experiment. #### What This Part Should Cover ```premium-lock What This Part Should Cover ``` ### Part 3: Execute and Reflect State the decision, your contribution to execution, the measured outcome, and what happened to the working relationship. Explain what you learned and what you would change. **Hint:** Include post-decision ownership; alignment that disappears at implementation is incomplete. #### What This Part Should Cover ```premium-lock What This Part Should Cover ``` ### What a Strong Answer Covers ```premium-lock What a Strong Answer Covers ``` ### Follow-up Questions 1. What was the other stakeholder right about? 2. Which evidence would have caused you to reverse your recommendation? 3. How did you respond when data could not resolve the core trade-off? 4. When did you escalate, or why did you choose not to? 5. What happened when execution deviated from the agreement? 6. How did this disagreement change the way you worked together afterward?