Handling a Hard Ask from the Legal Team Without Derailing Your Product

In an interview for a product manager role at American Express, you are asked how you respond when the legal team comes to you with a request that is hard to accommodate. Explain the method you follow to handle it, ideally illustrated with an example from your own work. ```hint Separate the obligation from the remedy Most legal requests rest on a firm underlying obligation, but there is often room in how that obligation is met. A good method establishes exactly what is required, and why, before anyone debates the specific change. ``` ### Clarifying Questions - What makes the request difficult in this scenario: it threatens a launch date, it would hurt a key metric such as application completion, or it seems to go further than the rule requires? - Is the request tied to a specific law, regulation, regulator commitment or contract, or is it the legal team's own judgment of the risk? - Does the request concern something already live with customers, or a product still in development? - If legal and the business still disagree after discussion, who makes the final call? ### What a Strong Answer Covers - Treating legal as a partner and pinning down the underlying obligation, the risk if it is not met and how firm the request is, before reacting. - Separating what must be achieved from how it is implemented, and generating compliant options with the least cost to customers and the business. - Quantifying the impact on customers, metrics, timelines and other teams, and making the trade-offs explicit to the people accountable for the decision. - A transparent escalation and documentation path when disagreement remains, with no attempt to work around compliance. - Following through, and changing how legal is involved so that similar issues surface earlier next time. ### Follow-up Questions - Two days before launch, legal asks you to remove a feature, and your general manager wants to ship as planned. What do you do? - How would you tell whether a request reflects a hard legal requirement or a conservative reading of the risk, and what would you do differently in each case? - How would you set up your team's process so that legal concerns surface during design rather than right before launch?