How do you communicate with engineers without losing them?
Give them the problem and the constraints — then trust them with the how.
Engineers aren't being difficult when they push back on a vague request — they're hunting for the spec you left out. The messages that land hand them the problem and the boundaries, and leave the implementation to the people who'll build it.
The problem, not the solution
“Users can’t find checkout” invites better answers than “move the button up.”
Explicit constraints
Deadline, scale, edge cases, non-negotiables — the boundaries they design within.
The why behind the ask
Context lets them catch a flaw you didn't and propose a cheaper path.
What’s decided vs. open
Be clear which choices are theirs; ambiguity gets re-litigated in review.
Solutions dressed as requirements
Prescribing the implementation wastes their best skill and hides the real goal.
Fake urgency
“ASAP” on everything means nothing is actually prioritized.
Hand-wavy scope
“Just a small change” is the phrase that precedes every two-week project.
Decisions by meeting volume
Loud consensus isn't a spec. Write the decision down.
A PM asking for a change to the signup flow.
Before
Can we make signup faster? It feels slow and clunky and users are complaining. Maybe remove some steps? Would be great to get this in soon.
Tuned for Engineers
Problem: 30% drop-off on signup step 2 (analytics linked). Goal: cut that, ideally this sprint. Constraint: we must still capture email + plan. The how is yours — fewer fields, async validation, whatever you judge best. Open question: can we defer company-name to onboarding? Your call.
Have a message to send an engineer?
Paste it into Appree and tune it to this channel — same facts, reframed in the voice they’re wired for.
Tune a message →Why do engineers push back on requirements?
Usually because the requirement specifies a solution instead of a problem, or omits a constraint they’ll hit later. Give the goal and the boundaries and the pushback drops.
How technical should my message be?
As technical as the constraints require, no more. You don't need their vocabulary — you need a precise problem, real numbers, and clear priorities.
How do I say something is urgent?
Tie it to a concrete date and reason, and say what to deprioritize to make room. Urgency without a trade-off is just pressure.
Search for anyone you need to reach — we’ll point you to the channel, or you can tune a message to them directly.