When to Say No: Scope Control for Embedded Engineers
Forward-deployed engineers must push back on scope creep. Here is a practical framework that preserves trust.
Embedded engineers earn trust by shipping. They keep trust by setting boundaries. Saying yes to every adjacent request is the fastest way to miss the mission demo—and burn out the one customer team that advocated for you.
Why scope creep hits FDSE teams hardest
You sit in the room when someone says, “While you are here, could you also…” Headquarters is distant; escalation paths are fuzzy; heroes are rewarded until they collapse. Without a framework, every request feels urgent.
The three-question filter
Before accepting new work, ask:
- Mission link: Does this move the agreed success metric this quarter?
- Owner: Who operates it after you leave—do they have capacity?
- Risk: Does this touch auth, PII, or production SLAs without a change window?
If two answers are weak, default to no for now—with a documented alternative.
How to say no without sounding like a blocker
Use yes, and with trade-offs:
“We can add that export—but it pushes the dashboard milestone by one week. Which outcome matters more for the briefing on the 15th?”
Write the trade-off in email or Slack the same day. Ambiguity is what kills relationships, not refusal.
Tools that help
- Single backlog visible to champion and executives.
- Non-goals section in every roadmap (review weekly).
- Change request template: requester, benefit, cost, decision owner, date.
When you must say yes
Regulatory fixes, security findings, and production outages override roadmap politics. Label them incident or compliance so stakeholders understand why other work paused.
Practice scenario
Your champion asks for a second integration to a legacy system “just for a pilot.” You have two weeks until go-live on workflow A.
Draft your response before reading further: what do you defer, what do you offer, and who signs the priority call?
Strong answers name a decision maker, quantify delay, and propose a pilot boundary (read-only, one user group, fixed duration).
Related guides
- FDSE interview prep — scope questions appear often in loops
- What is FDSE? — role expectations vs classic product engineering