Saying No Professionally: Setting Boundaries & Managing Workload
5 exercises on key boundary-setting phrases. Choose the most natural and professional option.
0 / 5 completed
1 / 5
Your sprint is already full and someone asks you to take on another task. Which response is most professional?
I don't have capacity this sprint — could this wait until next? This phrase is assertive without being abrupt. "Don't have capacity" is the standard professional term for being at full workload — it's neutral and process-oriented rather than personal. Offering "could this wait until next?" shows willingness to help while being honest about constraints. Option A ("too busy") sounds casual and slightly dismissive. Option C is blunt without context. Option D may be true but sounds defensive and territorial. Always give a reason and, when possible, offer an alternative timeline — it turns a "no" into a "not now."
2 / 5
A manager asks you to take on a new feature. You're willing, but only if another task is deprioritised. Which phrase communicates this clearly?
I'd need to deprioritise X to take this on — is that okay? This is the professional way to surface a trade-off without refusing the request. "Deprioritise" is the correct workplace term for moving something down the list. Ending with "is that okay?" puts the decision back with your manager, where it belongs. It shows you understand your capacity and respect the decision-making hierarchy. Option A ("something will suffer") is negative and vague. Option B says yes without flagging the real constraint. Option C refuses without offering a path forward. Naming the trade-off explicitly makes you a more trustworthy teammate.
3 / 5
Someone asks you for help with a Kubernetes issue, but your expertise is in frontend. What's the most helpful and honest response?
This is outside my area of expertise — let me connect you with someone who can help. This phrase does three things: it's honest about your limits ("outside my area of expertise"), it's professional (not "I don't know"), and it's helpful — you offer to bridge the gap by connecting them to someone appropriate. Option B is honest but passive — you're not adding value beyond the admission. Option C deflects with a structural argument, which can feel cold. Option D is dismissive. In professional culture, redirecting someone to the right expert is a service — always offer to help find the right person rather than just closing the door.
4 / 5
You've been asked to take on a project that will put your current deadline at risk. You want to flag this transparently. Which phrase is best?
I want to be transparent: taking this on risks the current deadline. Leading with "I want to be transparent" is a powerful professional signal — it shows you're not hiding information and invites a real conversation about trade-offs. It puts the risk on the table without blame or complaint. Option A sounds overwhelmed and personal. Option B ("no guarantees") is vague and doesn't surface the actual risk clearly. Option D deflects and may come across as unwilling. Flagging risks early and clearly is a mark of professional maturity — managers and stakeholders rely on engineers to surface these tensions proactively.
5 / 5
Multiple stakeholders have asked you to prioritise their tasks and you're unclear which matters most. What do you say?
Can we align on priorities first? This short phrase is deceptively powerful. It pauses the task-taking, surfaces the real problem (conflicting priorities), and frames resolution as a collaborative process ("align"). It respects everyone involved without accusation. Option A is a workaround that avoids the real problem. Option C ("sort it out among yourselves") is appropriate in some contexts, but too hands-off and slightly abrupt. Option D is passive and makes you sound blocked rather than proactive. "Align on priorities" is the professional way to call a quick conversation that will save hours of misdirected work.