Saying No Professionally: Setting Boundaries & Managing Workload
5 exercises on key boundary-setting phrases. Choose the most natural and professional option.
0 / 10 completed
1 / 10
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 / 10
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 / 10
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 / 10
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 / 10
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.
6 / 10
Reviewer: 'This code is fantastic! Could you just add a unit test for the authentication flow?'
Which response best sets a professional boundary while acknowledging feedback? A. 'Absolutely, I'll get right on that!' unitTestAdd() B. 'Thanks for the suggestion – I'm currently focused on addressing critical bugs identified in the main branch. Adding tests is definitely on my radar.' C. 'No problem, just push it to the main branch.' D. 'I'll look into it when I have time.'
This scenario highlights a common request during code reviews. Option B politely declines by explaining current priorities without dismissing the suggestion entirely. It's crucial to acknowledge feedback constructively and manage expectations – simply agreeing immediately can lead to overcommitment. Options A & D are too enthusiastic or dismissive.
7 / 10
Slack Message from @Sarah (Product Manager): 'Hey team, could someone quickly investigate the intermittent issue with the user profile loading times? It's impacting conversion rates.'
You are a backend developer. Which response is most professional and manages your workload effectively? A. 'Sure, no problem! I'll look into it ASAP.' profileLoadFix() B. 'I'm currently working on the database migration. Can you provide more details about the issue?' C. 'Sounds good, I'll add it to my task list.' D. 'That's a high priority! Let me know if you need help.'
Sarah's request highlights a potential bottleneck. Option B is best because it politely asks for clarification before committing, gathering crucial information about the issue's scope and impact. It demonstrates an understanding of your existing workload and prevents immediate over-commitment – a key skill in boundary setting.
8 / 10
PR Description: 'This PR adds support for the new payment gateway. It's fully tested and should be straightforward.'
A senior developer asks you to review it. You believe a thorough security audit is needed, but your time is tight. Which of the following responses is most appropriate? A. 'Sounds good! Just let me know if you need anything.' B. 'I'm happy to review, but I think we should prioritize a security scan before merging. Perhaps @John can assist?' C. 'I've already reviewed it and everything looks fine.' D. 'This PR is perfect!'
Security is paramount – this question tests your ability to advocate for best practices without appearing obstructive. Option B clearly states the need for a security scan and suggests collaboration, showing you're proactive while respecting time constraints. It's crucial to frame concerns constructively.
9 / 10
Standup Update: 'Okay team, what did everyone work on yesterday?'
You're assigned a new task to assist with the migration of user data. You realize this will significantly delay your current sprint goal. What do you say? A. 'I'm happy to help!' dataMigration() B. 'I've been tasked with assisting with the data migration, which unfortunately impacts my current sprint timeline.' C. 'Just finished the documentation.' D. 'No updates from me.'
Transparency is key when workload conflicts arise. Option B clearly communicates the impact of the new task on your existing commitments. It avoids vague excuses and allows for a productive discussion about prioritization. It's essential to be upfront about potential delays.
10 / 10
Team Lead: 'I need you to prioritize fixing the login bug and then working on the new reporting feature. Both are critical.'
You're unsure which task is more urgent given the dependencies. Which response demonstrates effective boundary setting? A. 'Okay, I'll do both!' loginFix()reportingFeature() B. 'Could you clarify the priority between the login bug and the reporting feature – are there any known dependencies or deadlines driving that?' C. 'Sounds good to me.' D. 'I'll start with the login bug.'
Without clear prioritization, it's impossible to effectively manage your workload. Option B seeks clarification by asking about dependencies and deadlines – a standard approach when faced with conflicting priorities. This proactive step prevents wasted effort and ensures you're working on the most impactful task.
What will I practise in "Saying No Professionally: Setting Boundaries & Managing Workload"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasebook exercises?
See the Phrasebook hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.