What's the difference between a 'setback' and a 'stumbling block' in tech contexts?

A setback is something that reverses or halts progress you've already made (e.g., 'The failed security audit was a major setback'). A stumbling block is an obstacle preventing agreement or forward movement, often in discussions (e.g., 'API versioning became a stumbling block in the architecture review').

When should I use 'trade-off' vs 'dilemma' when discussing technical decisions?

Use 'trade-off' when describing the cost-benefit relationship of a choice (e.g., 'The trade-off is higher latency for better reliability'). Use 'dilemma' when facing a difficult choice between two unpleasant options where neither is clearly better (e.g., 'We face a dilemma: cut scope or miss the deadline').

How do I explain technical debt to non-technical stakeholders in English?

Use accessible analogies and vocabulary: 'Technical debt is like taking shortcuts when building a house — it's faster now, but you'll pay for repairs later. The downside of our current approach is that every new feature takes longer because of the workarounds we built previously.'

What's the correct way to use 'difficulty' — singular or plural?

Use singular 'difficulty' with the pattern 'have difficulty in doing something': 'I had difficulty understanding the requirements.' Use plural 'difficulties' as a countable noun: 'We encountered several difficulties during the migration.'

How formal should I be when discussing problems in different work contexts?

Match your register to the context. Slack/team chat: 'What a pain! The build is broken again.' Email to stakeholders: 'We're experiencing issues with the build pipeline.' RFC/formal docs: 'The current implementation presents stability challenges that require attention.'

How to Talk About Difficult Trade-offs in English at Work

Why Tech Professionals Need This Vocabulary

Every sprint planning session, every RFC review, and every stakeholder conversation involves trade-offs. You might need to explain why the team took on technical debt, why you're recommending approach A over approach B, or why delivering everything by Q3 simply isn't realistic.

The challenge? Communicating these difficult realities clearly and diplomatically — especially when English isn't your first language. Using the right vocabulary helps you sound credible, avoid misunderstandings, and navigate tricky conversations with confidence.

Culture Note: Directness Varies

In US tech culture, direct language about trade-offs is expected and respected. In UK contexts, softening language is more common. Know your audience: 'This approach has significant downsides' (US) vs 'This approach might present some challenges' (UK).

Key Nouns for Describing Difficulties

Tech work involves problems of varying severity. Choosing the right noun signals whether you're describing a minor hiccup or a project-threatening blocker.

Term	Severity	Tech Workplace Definition	Example Context
glitch	Minor	A small, often temporary technical malfunction	CI pipeline, deployment, API response
snag	Minor	An unexpected small problem that slows progress	Dependency update, environment setup
hitch	Minor	A temporary delay or obstacle	Third-party service, approval process
setback	Medium	Something that reverses or halts progress	Failed security audit, key engineer leaving
stumbling block	Medium	An issue preventing agreement or forward movement	Cross-team alignment, legal review
pitfall	Variable	A hidden danger or unexpected difficulty	Architecture decisions, vendor lock-in
obstacle	Medium-High	Anything blocking progress (literal or metaphorical)	Budget constraints, legacy system limitations
impediment	Medium-High	Something preventing free action or progress	Process bottleneck, missing documentation
dilemma	High	A difficult choice between unpleasant alternatives	Ship fast vs ship secure, build vs buy
ordeal	High	A severe, painful, or exhausting experience	Major incident response, migration project

Use 'glitch' specifically for technical problems: 'We hit a glitch in the deployment pipeline.'
Use 'dilemma' when there's a genuine choice between two difficult options — not just any problem.
Use 'pitfall' (often plural) when warning about risks: 'There are several pitfalls with this microservices approach.'

Adjectives That Describe Difficulty Precisely

Generic words like 'hard' or 'difficult' lack precision. These adjectives help you communicate exactly what kind of difficulty you're facing.

Adjective	Meaning	Tech Collocations
problematic	Full of problems or difficulties	dependency, integration, relationship with vendor
complex	Difficult because it has many interconnected parts	system, migration, debugging process
convoluted	Unreasonably complicated and hard to follow	codebase, explanation, approval process
arduous	Requiring sustained difficult effort	refactoring task, compliance process, onboarding
gruelling	Extremely tiring and demanding	on-call rotation, incident response, deadline push
tough	Difficult to deal with or accomplish	decision, quarter, conversation with leadership
obstructive	Deliberately creating difficulties	stakeholder, process, legacy team
insufferable	So annoying or painful it's hard to tolerate	technical debt, flaky tests, slow build times

Collocation Matters

Say 'complex system' not 'convoluted system' (unless criticising). Say 'tough decision' not 'arduous decision'. Wrong collocations make you sound unnatural even when the meaning is technically correct.

Slack vs Email: Register Differences

How you describe difficulties changes depending on whether you're messaging a teammate on Slack or writing a formal RFC or stakeholder update.

Informal (Slack/Team Chat)	Formal (RFC/Email/Doc)
What a pain! The API keeps timing out.	We're experiencing intermittent timeout issues with the API.
This legacy code is sheer torture to work with.	The legacy codebase presents significant maintenance challenges.
I've been slogging through this refactor all week.	The refactoring effort has required substantial engineering time.
We're in a bit of a fix with the release schedule.	We're facing constraints with the current release timeline.
The downside is it'll take forever to test.	The trade-off is an extended testing cycle.
What's bugging the CI today?	We're investigating the root cause of the CI failures.
I think we're out of the woods now.	The critical issues have been resolved.

Scenario: Discussing Technical Debt in a Planning Meeting

Imagine you're in a sprint planning meeting. The PM wants to add three new features, but your team has been struggling with slow test suites and fragile deployments caused by shortcuts taken last quarter.

Here's how to frame the conversation using precise vocabulary:

'The technical debt we accumulated last quarter is now a major stumbling block for velocity.'
'We're facing a dilemma: we can push forward with new features or address the flaky tests that are causing a gruelling debugging experience.'
'The convoluted deployment process is an impediment to shipping quickly.'
'If we don't address this now, we'll hit the same pitfalls next quarter.'
'The downside of continuing without refactoring is that every feature will take longer.'

Frame Problems as Trade-offs, Not Complaints

Instead of 'The code is terrible,' say 'We're facing a trade-off between shipping new features and addressing the technical debt that's slowing us down.' This positions you as solution-oriented.

Scenario: Presenting Trade-off Analysis in an RFC

You're writing an RFC comparing two approaches: building a custom solution vs integrating a third-party service. Here's vocabulary for presenting the analysis clearly:

'Option A has lower upfront cost but presents several pitfalls around long-term maintenance.'
'The stumbling block with Option B is the complex integration with our existing authentication system.'
'Both approaches involve trade-offs; there's no obstacle-free path here.'
'Option A is the more arduous path initially but reduces technical debt over time.'
'The key dilemma is whether we optimise for speed-to-market or long-term maintainability.'

Weak Phrasing	Stronger Phrasing
Option A is bad because it's hard.	Option A presents significant complexity in the integration layer.
We have problems with Option B.	Option B has a key stumbling block: vendor lock-in risk.
Both options are difficult.	Both options involve trade-offs that require careful consideration.
I don't like this approach.	This approach has downsides we should weigh against the benefits.

Scenario: Explaining Constraints to a Stakeholder

A product manager asks why you can't deliver all five requested features by the end of the quarter. Here's how to explain constraints professionally:

'We're facing a resource constraint that's an obstacle to delivering all five features.'
'The main stumbling block is that features 3 and 4 share dependencies, creating a complex sequencing problem.'
'There's a dilemma here: we can deliver three features with high quality, or five features with significant technical debt.'
'The downside of rushing all five is that we'll spend Q2 fixing bugs instead of building new capabilities.'
'I want to be transparent about the pitfalls of over-committing — we hit setbacks last quarter when we tried this approach.'

Use 'Difficulty' Correctly

Say 'I'm having difficulty finding the root cause' (singular, with -ing verb). Not 'difficulties' in this construction. 'Difficulties' (plural) works in: 'We encountered several difficulties during the migration.'

English for Developers Bundle