Turning a vague business problem into a shippable increment, and deciding what not to build.
3 questions in Forward Deployed Engineering.
Separate a disagreement about the mechanism from a disagreement about the goal, then test your objection cheaply rather than argue it: a week spent proving the request will not move the number is usually worth more than either refusing or complying in silence.
Decide on the prototype's foundations rather than its polish: if the data model and the correctness boundaries are sound, hardening is cheaper and keeps the users you have, and if they are not, no amount of testing and monitoring will make it safe to keep.
Convert the sentence into a named decision somebody makes today, find out how that decision is made now and what a better one is worth, then ship the narrowest thing that changes it — and say out loud what you are deliberately not building.