Working With People
Product managers, designers, stakeholders and the engineers next to you: how to write for people who will not read past the first line, disagree and still commit, run a demo that changes a decision, and give feedback that lands.
The PM owns the why and the priority; you bring the cost curve, the smaller version and the question behind the ticket — and when there is no PM, you say out loud which of their jobs you are now doing.
Tell the designer which part is expensive and why, in their terms, and offer the version that keeps the intent — before the mockup is signed off, not in week two of the build.
The first line is the decision you need or the thing that changed for them; everything after it is optional reading for whoever wants the detail.
Disagree once, in writing, before the decision; then build it as if it were yours, and agree in advance what would show which of you was right.
A demo exists to get a decision, not applause: show the path a real customer takes, ask the one question you need answered, and leave out everything that does not bear on it.
Feedback that lands is specific, about the work rather than the person, and says what effect it had — and you ask for it the same way: about one piece of work, with one concrete question.