2 exercises — build compelling business cases for refactoring and infrastructure investment using ROI and risk language.
0 / 7 completed
1 / 7
Engineering wants to dedicate a full quarter to refactoring the payment module. How do you make the business case to leadership?
Option C is the professional ROI case for technical investment. The structure is:
1. Quantify the current cost of NOT fixing it — "$96,000/quarter in incidents" — this is the "cost of doing nothing" 2. Quantify the engineering cost — "2 engineers × 12 weeks ≈ $60,000" — makes it concrete 3. Project the ROI — "70% reduction in P1s = $67,200 savings → pays back in one quarter" 4. Mention compound benefits — "faster feature velocity" — secondary payoff
Leadership approves technical work when it can be expressed as a financial decision: cost of problem vs. cost of fix vs. expected benefit.
Technical debt language that works with leadership: • "We're currently spending X hours/week on workarounds for this — that's N engineer-weeks/year" • "Every new feature in this module takes 2× longer than it should because of X" • "The current architecture limits us to Y transactions/second — to hit our Q4 target of 2Y, we need to rearchitect sooner or face re-doing this work under pressure"
2 / 7
The VP of Engineering asks: "Should we invest in upgrading our Kubernetes cluster to version 1.28 or defer it?" Which response gives the best infrastructure investment argument?
Option B is the professional infrastructure investment argument. It frames the decision around risk and compliance timelines, not technical preference:
• Hard deadline — "EOL in December, compliance audit in February" — creates urgency with external forcing functions • Risk quantification — "known CVEs on unpatched software" — security risk is a real business cost • Comparison of doing it now vs. deferring — "3 days now" vs "high-pressure, high-risk upgrade in January" • ROI framed as risk avoidance — "cost of breach or compliance failure dwarfs 3 days" — doesn't require exact numbers because the asymmetry is obvious
Infrastructure investment arguments work best when they appeal to: 1. Compliance obligations — non-negotiable, regulatory 2. Risk avoidance — security breach, SLA penalty 3. Compound cost of deferral — "costs $10K now or $100K under pressure in 6 months" 4. Enabling future revenue — "this is a prerequisite for the Series B data room"
3 / 7
Sarah from Product just messaged you: 'The new user onboarding flow is *slow*. Users are dropping off before they even finish the tutorial. Can we fix it?' As a backend engineer, what's the most appropriate initial response to give her?
The key here is to gather more information. Simply stating you'll fix it immediately without understanding the scope of the problem isn't effective. Asking for metrics demonstrates that you're approaching the issue with data and helps determine if this is a truly urgent priority or part of an ongoing effort. Option D is inappropriate as it deflects responsibility.
4 / 7
David, the lead developer on your team, has just posted a code review comment: 'This function uses synchronous I/O. Consider using asynchronous operations to avoid blocking the main thread.' What is David *really* suggesting?
While David's comment seems direct, it's fundamentally about performance. Synchronous I/O can block the main thread, leading to unresponsive applications. The core issue isn't just 'rewriting the function'; it's recognizing and addressing a known performance problem – a technical debt related to blocking operations. Option A is incorrect because David has provided feedback; option D is completely unrelated.
5 / 7
You're writing the description for a Pull Request introducing a new caching layer in your API. Which of the following statements best explains the rationale behind this change?
PR descriptions need to clearly articulate *why* the change was made. While a caching layer *does* improve response times and reduce database load (addressing technical debt), stating that it's simply 'adding a new feature' is too vague. Option D is overly optimistic – scaling isn't guaranteed by just adding caching; option C misrepresents the purpose.
6 / 7
During a standup meeting, your team lead asks: 'What progress have you made on reducing technical debt in the user authentication service?' How should you respond?
This question tests your ability to translate technical debt into business-understandable terms. Simply saying you fixed bugs isn't sufficient. Providing a specific example – refactoring the session management module – demonstrates that you're actively addressing the problem and using relevant terminology (refactoring). Option A is too vague; option D indicates a lack of commitment.
7 / 7
You've discovered a significant amount of duplicated code in a legacy module. You need to explain this issue to the development team during a sprint planning session. Which phrasing is most effective?
Framing the duplicated code as 'redundant' and directly linking it to increased maintenance efforts and potential inconsistencies clearly communicates the problem. This highlights the technical debt aspect without being overly critical. Option A is a directive; option C is subjective, and option D avoids responsibility.
This exercise, "Technical Debt Language", tests your understanding of tech-to-business vocabulary and phrasing through 7 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 7 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.