A PM asks: "How long will this feature take?" You have done initial scoping but there are major unknowns. Which response is most professional?
Option C is the professional estimation with uncertainty. It models the three-tier estimation approach:
• Tier 1: Current rough estimate — "3–5 weeks" — gives the PM something to plan with immediately • Tier 2: Named unknowns — "third-party API integration", "auth system" — explains why the range is wide (not incompetence, but unresolved questions) • Tier 3: De-risking offer — "2-day spike to nail down unknowns" — turns uncertainty into a time-boxed investigation • Commitment to tighten — "tighter estimate by Friday" — the PM gets a date for a better answer
Estimation uncertainty phrases: • "My estimate is X, assuming [condition]. If [alternative], add Y days." • "This is a rough order of magnitude — I'd need to investigate [X] before committing" • "I can give you a confident estimate after a spike. The spike itself will take 2 days." • "Best case X, worst case Y, most likely Z"
Option D ("exactly 4 weeks") is the most dangerous — false precision destroys trust when wrong.
2 / 11
A deadline has been set by the business that you believe is not achievable. Which response manages expectations most effectively?
Option C is the professional deadline management response. It reframes "can you do it?" into scope × time trade-off discussion:
1. Sets up the framing — "I want to set realistic expectations so the business can plan accurately" — positions this as being helpful, not obstructive 2. States the honest baseline — "6 weeks, not 4" — with no hedging 3. Offers three concrete options: — Cut scope to hit original deadline — Full scope, extended deadline — Phased delivery (best of both) 4. Asks the PM/stakeholder to choose — respects their ability to make the call based on business context you don't have
Option A ("we'll do our best") sets up failure — you ship late or poor quality, without forewarning. Option D ("somehow") is even worse. Option B is honest but unhelpful — it says no without giving options.
The key insight: Most deadlines are not fixed constraints — they're the PM's first preference. When you give three options, you allow the PM to make an informed decision. This is collaborative, not adversarial.
3 / 11
Stakeholders ask: "Why do estimates always go wrong? Can't you just be more accurate?" Which explanation is most professional?
Option C is the professional explanation of why estimation is inherently uncertain. Key points:
• Names the fundamental cause — "discovering unknowns not visible during scoping" — this is accurate and not an excuse • Positions it correctly — "property of creative/knowledge-based work", not a professional failure • Avoids defensiveness — acknowledges the concern without being combative • Proposes concrete improvements — ranges, spikes, calibration tracking • Ends collaboratively — "would it help to discuss how we communicate confidence levels?" — moves to solution
The "confidence level" framing is particularly effective: instead of asking "will it take 2 weeks?", planning with "we have 80% confidence we can deliver in 3 weeks, and we'll know in 2 days whether the auth integration changes that" gives everyone useful information.
Analogies that help non-engineers understand this: • "It's like estimating a home renovation — you find surprises once the walls come down" • "It's a research and development activity, not manufacturing"
4 / 11
Sarah (Senior Frontend Developer) comments on your PR:
'This component looks good, but the performance metrics are concerning. Can you investigate and provide a timeline for optimization?' Which of the following responses best addresses Sarah's feedback while maintaining professional communication?
This question tests your ability to respond to feedback constructively. Option A is dismissive and doesn't acknowledge Sarah's concerns. Option B avoids responsibility and offers no concrete action. Option C demonstrates a proactive approach by scheduling a discussion and prioritizing the issue—this is key for collaborative development. Option D ignores the feedback entirely, which is unprofessional.
5 / 11
Mark (Product Manager) sends you this Slack message:
'We need to ship this API endpoint by Friday. Can you get it done?' You've just discovered a complex dependency injection issue that will require significant refactoring. Which response is most effective in managing expectations?
This question tests your ability to communicate realistic timelines. Option A demonstrates a lack of awareness and sets unrealistic expectations. Option B provides an honest assessment of the time required, which is crucial for effective project management. Options C and D are evasive and avoid taking responsibility. Setting clear boundaries is important when dealing with external pressures.
6 / 11
You're presenting an estimated timeline for a new microservice to the engineering team. After your presentation, David (Lead Engineer) asks: 'How did you arrive at that estimate? It seems quite optimistic.' Which of the following responses best explains your estimation process while maintaining transparency?
This question tests your ability to explain your reasoning. Option A is unprofessional and undermines your credibility. Option B provides a clear explanation of the estimation process, demonstrating transparency and confidence. Options C and D are evasive and lack accountability. Clearly communicating your methodology builds trust with the team.
7 / 11
Daniel, a junior developer, posts in the #general Slack channel: 'Just finished implementing this feature. It's done!' What's the most appropriate response to encourage further discussion and ensure clarity for the product owner?
The correct response prompts for more detail – Daniel's statement lacks crucial context. Options A and D are dismissive; option B is too casual. Option C invites a concise explanation from Daniel which helps the product owner understand the feature's scope and any potential issues before further development or testing.
8 / 11
You're writing a PR description for a refactoring of an authentication module. The changes improve performance but also introduce a new dependency on a third-party library. Which statement best summarizes the impact and next steps?
The key here is transparency – developers need to understand the *change* introduced. Simply stating 'performance improved' isn't sufficient. Option B clearly communicates the new dependency, which is critical for future maintenance and potential issues. Options A and C are too vague, while option D lacks specifics.
9 / 11
During a standup meeting, you're updating the team on your progress. Your teammate, Emily (Lead Backend Engineer), asks: 'What level of detail are you planning to provide regarding the database schema changes for this new API?' Which response demonstrates effective communication and manages expectations?
Option 2 is evasive and doesn't acknowledge Emily's concern about schema impact. The correct response proactively offers further detail while setting a reasonable initial level of explanation. Options A and D are incomplete; option B is dismissive.
10 / 11
You receive the following API response:
{
"status": "error",
"code": 400,
"message": "Invalid request parameters. Field 'user_id' is required."
}
What's the most appropriate way to respond in a Slack message to the API developer, Chris?
The API response clearly identifies the problem – a missing parameter. Option 1 is incorrect and ignores the feedback. Option 2 provides the precise information from the response to guide Chris in fixing the issue. Options 'Fixed!' and 'Thanks for the notification' are unhelpful and do not address the underlying problem.
11 / 11
You've been asked to estimate the effort required to migrate a legacy application to a new microservice architecture. After initial investigation, you identify significant technical debt and integration challenges. Which response is most professional when discussing this with your manager?
Option 1 is unrealistic given the identified complexities. Option 2 acknowledges the challenges while offering a realistic assessment – it highlights the need for further investigation and discussion about potential risks and impacts on the timeline. Options A and D are evasive and don't address the seriousness of the situation.
This exercise, "Estimation Language", tests your understanding of tech-to-business vocabulary and phrasing through 11 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 11 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Tech-to-Business exercise for?
It's designed for IT professionals and learners who want to sound natural discussing tech-to-business topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Tech-to-Business exercises?
Browse the full Tech-to-Business exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.