4 exercises — requesting extensions with context, proposing phased delivery, raising dependency risks early, and communicating late-stage delays proactively.
0 / 9 completed
1 / 9
You need to request a 2-week deadline extension for a feature. Your manager asks why. Which explanation is most professional?
Option B uses the original estimate → documented changes → quantified scope growth → two options structure:
1. References the original estimate context: "Based on scope at kickoff" — shows the estimate was reasonable at the time 2. Documents specific changes: "authentication requirement added" and "data model changed twice" — concrete, named changes 3. Quantifies the growth: "40% larger than originally planned" — puts a number on the scope change 4. Offers two options: extension OR ship original scope now — maintains the relationship and the manager's agency
Why A fails: "Underestimated" puts all responsibility on the estimation process without explaining what changed
Why C and D fail: Vague — "longer than expected" and "technical problems" give the manager no information to make a decision
Extension request formula: Original estimate context → Specific changes since → Quantified scope growth → Extension OR partial delivery now
2 / 9
A project deadline is truly impossible to move. You need to negotiate phased delivery instead. Which proposal is strongest?
Option C is an ideal phased delivery proposal:
1. States the constraint honestly: "can't ship without cutting quality in ways I'm not comfortable with" — personal professional commitment, not policy 2. Names each phase clearly: dates, feature names, and what percentage of user value is delivered in Phase 1 — the PM can make an informed decision 3. Identifies the business value of Phase 1: "~70% of user value" — acknowledges that the most important part ships first 4. Interprets the business need: "shippable product for the launch announcement" — connects the phased plan to the likely business reason behind the fixed date 5. Closes with a question: "Would that structure work?" — invites dialogue rather than demanding acceptance
Why A fails: States the problem without offering a solution
Why B fails: Asking "can we get more time" after a fixed deadline is already set is a wasted question
Why D fails: "Try to deliver what we can" is the worst possible commitment — neither the PM nor the engineer knows what "what we can" means
Phased delivery formula: State constraint + why → Phase 1 (date + scope + % of core value) → Phase 2 → Phase N → Ask if structure works
3 / 9
You committed to a deadline but a critical dependency — an external API — has not been delivered by the vendor. How do you raise this?
Option B is a professional dependency risk escalation:
1. Named, specific risk: "payment gateway API due March 1, still not received by March 8" — precise language, no vagueness 2. Quantified impact: "7 days to do 10–12 days of work" — the manager instantly understands the pressure 3. Three numbered options: escalation, parallel development, or timeline revision — shows preparation and analytical thinking 4. States a recommendation: "option 2 to protect deadline while option 1 runs in parallel" — doesn't just list options and walk away; takes a position 5. Returns decision authority: "Your call on how to proceed" — keeps manager in control
Why A fails: Blame language ("the vendor's fault") without a solution plan — doesn't help the situation and sounds defensive
Why C fails: "Might be late" without data or a path forward
Why D fails: "I'll update you when it arrives" is passive risk management — by the time it arrives you'll have no time
Dependency risk formula: Named dependency → Expected vs actual dates → Time impact → Options numbered → Recommendation → Decision returned to manager
4 / 9
After completing a project, you discover the post-release testing will take 2 days longer than planned. The client launch is at risk. How do you communicate this?
Option B is a professional late-stage delivery risk notification:
1. Names the specific problem: "gap in the test suite that requires additional test cases" — not vague "testing issues" 2. Quantifies precisely: "2 additional business days — Wednesday rather than Monday" — exact, not "a couple of days" 3. Proactive timing: "I want to be transparent before Monday arrives rather than after" — giving the client 2 days to react is vastly better than a Monday morning surprise 4. Two options with framing: "proceed Monday with known gaps" OR "wait until Wednesday for full coverage" — presents the stakeholder with a real choice 5. States the recommendation with reasoning: "I recommend Wednesday — a production incident costs more than 2 days" — helps the client make an informed decision 6. Offers urgency path: "I'm available to discuss today if the launch date is critical" — signals responsiveness
Why A and C fail: Describe the symptom without a recommendation or options
Why D fails: Recommendation without context — why? By how long? What are the options?
Late delivery formula: Specific cause → Exact new date → Why transparency now → Two options → Recommendation + reasoning → Offer to discuss urgently
5 / 9
Sarah from the QA team just flagged a significant performance bottleneck in your new microservice. The original deadline was tomorrow morning. Which Slack message is most effective for requesting a brief meeting to discuss mitigation options?
Don't just state the problem; frame it as collaborative.
The best approach acknowledges Sarah's contribution immediately and proposes a collaborative discussion. Options A and D are overly blunt or simply state the problem without offering a solution or inviting input. Option B feels demanding and doesn't demonstrate proactive engagement; requesting a 'sync' is a more professional way to initiate a conversation about complex technical issues.
6 / 9
You're writing the description for a Pull Request adding new database schema. The initial deadline was 3 days ago, and your lead reviewer has requested an update on progress. Which phrasing best balances transparency with acknowledging potential delays?
Be honest about where you are without over-explaining or making excuses.
Option 1 is honest about the delay while providing context without making excuses. It's crucial to acknowledge delays respectfully and briefly explain the underlying reason. Option A sounds dismissive. Option 2 provides too much detail that might be perceived negatively. Option 3 is evasive, and option 4 ignores the reviewer's request for an update.
7 / 9
You've been assigned a task to integrate with a new third-party API. The vendor's documentation is incomplete and their support team has responded slowly. You need to push back on the initial deadline of one week. Which email subject line would be most effective for requesting an extension?
Be direct, but professional, highlighting the dependency.
Option 2 – 'API Integration - Deadline Request' – is clear and immediately conveys the purpose of the email. This avoids ambiguity and allows the recipient to prioritize accordingly. Options A and B are too generic. Option D doesn't indicate the need for an extension.
8 / 9
During a standup meeting, you realize you won't be able to complete your assigned task by Friday. The team lead asks, 'What's the status?' What's the most constructive response?
Focus on what you can deliver and proactively identify roadblocks.
Option 2 demonstrates accountability and a willingness to discuss potential adjustments. It's better than simply saying 'it's going well' (Option A) or immediately requesting a change (Option B). Option D is dishonest and doesn't acknowledge the delay. Providing specific details about the challenge shows you're proactively addressing the issue.
9 / 9
You've been given a new feature to build with a deadline of 5 days. After reviewing the requirements, you realize several key dependencies are missing. You need to communicate this to your product owner. Which statement is most effective?
Focus on impact and propose a solution-oriented approach.
Option 3 is proactive and frames the issue as a potential impact on delivery rather than simply stating an inability. It proposes a meeting to discuss solutions, demonstrating collaboration and responsibility. Options A and B are overly negative or passive. Option D avoids addressing the core problem.
This module focuses on Negotiation English — real workplace phrasing you'll use on the job. It contains 9 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 9 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 Negotiation English exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around negotiation english — 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 Negotiation English exercises?
See the Negotiation English 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.