When a stakeholder asks for a change to the software I’m building, my typical
responses are, in order: “Got it.” Then: “I’m working on that issue.”
Finally: “It’s done.” Here’s an alternative: skip the first two conversations and
go straight to the third. As soon as you can, just do the thing, and respond
with: “It’s done.”