Choose the most professional way to say no or decline requests in 5 real workplace scenarios.
The professional 'no': explain + offer + close
Explain why: capacity, priority conflict, wrong person — not just 'I don't want to'
Offer an alternative: a different timeline, a different person, a smaller scope
Close clearly: don't leave it ambiguous — 'I can't take this on right now' not 'I'll see what I can do'
Don't over-apologise: one apology is professional; three sounds like guilt
0 / 5 completed
1 / 5
A colleague asks you to take on an additional feature during the current sprint. You're already at 100% capacity. How do you decline professionally?
Why C is the professional decline: honest + context + alternatives
A professional "no" to extra work has three parts:
Be direct: "I don't have capacity" — not vague or apologetic
Show your current load: "my current commitments are [tasks]" — makes it concrete, not an excuse
Offer alternatives: escalate for descoping OR take it in the next sprint
Why B is worse than a no: accepting work you know you can't complete misleads the team, affects sprint goals, and damages your reliability. A clear "no" is more professional than a misleading "yes".
Capacity vocabulary:
"I'm at full capacity this sprint — I can't add more without dropping something."
"I don't have bandwidth for this right now."
"Could we revisit this next sprint?"
"If this is urgent, something else would need to come off my plate first."
2 / 5
A stakeholder adds a new requirement at the end of a sprint that would require significant rework. You need to decline adding it to the current sprint scope. What do you say?
Why C is the professional response: validate the request, explain the cost, propose the right process
This is a classic scope creep scenario. The professional approach:
Acknowledge the request positively: "important addition" — not dismissive
Explain the cost: "rework" and "risk to the sprint goal" — concrete reasons, not bureaucracy
Propose the correct process: backlog, estimation, prioritisation — shows you know how to handle this
Offer to take action: create the ticket, flag to PM — you're solving, not just declining
Scope management vocabulary:
"This is out of scope for this sprint — let's add it to the backlog."
"Adding this now would put our sprint commitment at risk."
"I'd like this to go through proper estimation before we commit to it."
"Can we capture this as a follow-up story for next sprint?"
3 / 5
You receive a meeting invitation for a 1-hour meeting where you're listed as an optional attendee. The topic doesn't require your input and you have a deadline today. How do you decline the invitation professionally?
Why C is the professional decline: context + no-regret offer
Optional attendees exist for a reason — declining is appropriate when you have a good reason:
Reference your status: "listed as optional" — grounds the decline in the meeting itself
Give a brief reason: "delivery deadline today" — relevant context, not over-justification
Offer async contribution: "share notes, contribute via doc" — shows willingness to participate differently, not avoidance
Why accepting when you won't contribute (A) is wasteful: it wastes your time and doesn't add value to the meeting. If you're listed as optional and have a good reason to decline, do so — with professionalism.
Meeting decline phrases:
"I'll skip this one — please keep me in the loop via the notes."
"I have a conflict — can you share the recording or summary afterwards?"
"Could you add me to the notes thread instead of the call?"
4 / 5
Your manager asks you to take on a task that is outside your area of expertise and could be done better by a colleague with the right skills. How do you redirect the request professionally?
Why C is the professional response: honest + team-first + constructive alternative
This response demonstrates team-first thinking:
Frame it around quality: "make sure this task gets the best result" — the motivation is the project, not personal avoidance
Be specific about who can do it better: name the colleague and the specific area of expertise
Offer to stay involved: "happy to support them" — not completely opting out
Propose a redistribution: take on an alternative task — shows you're still contributing
This is not avoiding work — it's optimising task allocation. Good engineering teams match skills to tasks.
Redirection phrases:
"I think [Name] is better placed for this — they have experience with [X]."
"I can do this, but I'd need significant time to upskill. Would [colleague] be a better fit?"
"I want to flag that this isn't my strongest area — how would you like to handle that?"
5 / 5
A colleague repeatedly asks you for help outside your working hours, including weekends. You want to establish a boundary without damaging the relationship. What do you say?
Why C is the professional boundary-setting: clear, kind, and offers a process
Setting working hours boundaries is a professional skill that protects you and models healthy team norms:
Start positively: "glad to help during working hours" — not a rejection of the person
Name the boundary clearly: "I don't check messages on weekends" — direct, not apologetic
Give a reason: "important for my recovery" — honest without over-sharing
Provide the alternative: escalation path for urgent issues — ensures the colleague isn't left stranded
Set the expectation: "Monday morning" — explicit so they know what to expect
Why continuing to respond (A) is harmful: it implicitly tells the colleague that weekend messages are acceptable and normalises out-of-hours availability. This is unsustainable.
Boundary phrases:
"My working hours are [X] to [Y]. I'll respond to messages within that window."
"For urgent issues outside hours, please use [channel/person]."