Explaining Tech to Non-Tech People: it-clefts and wh-clefts for jargon-free answers
About this lesson
Using it-clefts and wh-clefts, this C1 English for IT lesson plan teaches how to explain tech to people outside IT.
- Grammar
- It-clefts (It's the old ledger that slows every release down.), wh-clefts (What we need is three more months.), all-clefts, reversed wh-clefts and The reason… is that…
- Topic
- A CFO who wants plain answers about late payouts and a long migration, with phrases such as the bottom line, a ballpark figure and boil down to.
- Activities
- A CFO's email and a blog post to read, a meeting to hear, self-checking drills, a chat and a wheel of jargon-free explanations, then an email to sales and a recording.
What's inside
Chapter 1Warm-up: lost in translation
Chapter 2Reading: the CFO wants answers
Chapter 3Listening: one engineer in four
Chapter 4Grammar: what matters is the focus
- Study the scheme: cleft sentencesGrammar schemeTry it
- Choose the correct option to complete each cleft sentenceChoose the optionUnlock
- Drag the phrases into the gaps: Maya's answers to GrahamDrag and dropTry it
- Complete the cleft sentences with one word in each gapFill in the gapsUnlock
- Choose the correct answer: focus, meaning and formQuizUnlock
Chapter 5Speaking: is the API down??
Chapter 6Homework: plain English, please
- Match the beginnings and endings of the cleft sentencesMatchUnlock
- Drag the phrases into the gaps: notes from the Ledger v2 teamDrag and dropUnlock
- Find the matching pairs: jargon and plain EnglishMemory gameUnlock
- Write an email to the sales team in plain EnglishWriting, checked by the teacherUnlock
- Record yourself explaining your project to a friendSpeaking, checked by the teacherUnlock
Vocabulary
10 words and phrases from the lesson, each with a picture and audio in edio.
+7 more with pictures and audio in the lessonMore words
- a ballpark figure
- technical debt
- a stopgap
- under the hood
- walk someone through
- dumb down
- the cutover
Grammar: it-clefts and wh-clefts
A cleft splits one sentence into two parts to put a spotlight on the part that matters: the real cause, what you need, or the correction to a rumor. Learners build five kinds, check the form that follows is or was, and save them for the one point a listener must remember.
Cleft sentences: put the focus where you want it
Split one sentence into two parts to stress the key point, correct a wrong idea or prepare your listener.
Five ways to build a cleft
An it-cleft puts the focus straight after It is or It was; a wh-cleft holds it back until the end: What we need is three more months. An all-cleft means only (All we did was add a cache.), and a reversed wh-cleft opens with the focus.
| Pattern | Form | Example |
|---|---|---|
| it-cleft | It is / It was + focus + that / who + the rest | It was a configuration change, not an attack, that delayed the payouts. |
| wh-cleft | What + clause + is / was + focus | What we need is three more months. |
| all-cleft (= only) | All + clause + is / was + focus | All we did was add a cache. |
| reversed wh-cleft | focus + is / was + what + clause | Three more months is what we need. |
| reason / thing | The reason (why)… is that… / The thing is, … | The reason we didn't know is that nothing looked broken. |
Why use a cleft?
A cleft can correct a wrong idea, draw a contrast or stress a late time: It's not the new code that takes the time. It's the checking. Keep it for the point that matters most; a reply full of clefts sounds defensive.
Why use a cleft?
Plain sentence
- A configuration change delayed the payouts.
- The checking takes the time.
- We noticed the problem on Tuesday.
Cleft: the focus is clear
- It was a configuration change, not an attack, that delayed the payouts. (corrects a wrong idea)
- It's not the new code that takes the time. It's the checking. (contrast)
- It wasn't until Tuesday that we noticed. (= only on Tuesday, later than expected)
Don't overdo it
A cleft is a spotlight: use it for the one point that matters. If every sentence is a cleft, nothing stands out, and you start to sound defensive.
What comes after is or was?
The verb in the first part decides: after need or want, a noun or to + verb (What we need is to migrate the last services); after do or did, the base verb (What we did was roll back the release); after happened, a full clause.
- need / want / plan in the first part → a noun or to + verb: What we need is a date. What we need is to migrate the last services.
- do / did in the first part → the base verb (to is possible, but less common): What we did was roll back the release. All you have to do is enter the code.
- happened in the first part → (that) + a full clause: What happened was (that) one setting changed.
- suggest in the first part → that we + verb: What I'd suggest is that we test the cutover first.
It-clefts: the details
It is or It was stays singular, but the verb after that agrees with the focus: It's the old services that slow us down. It wasn't until takes a positive verb: It wasn't until Tuesday that anyone noticed, not nobody noticed.
- It is / It was stays singular: It was the API keys that expired.
- The verb after that agrees with the focus: It's the old services that slow us down. It's the ledger that slows us down.
- For things, use that (which is possible); for people, who or that: It was Priya who spotted the bug.
- It wasn't until + a time or an event + that + a positive verb: It wasn't until Tuesday that anyone noticed.
Typical mistakes
What we need is migrate the old services.
What we need is to migrate the old services.
After need / want: a noun or to + verb.
The reason is because the job didn't run.
The reason is that the job didn't run.
“Reason” and “because” say the same thing twice: use “is that.”
It's the old ledger what slows us down.
It's the old ledger that slows us down.
In it-clefts, use that or who, never what.
It wasn't until Tuesday that nobody noticed.
It wasn't until Tuesday that anyone noticed.
The negative is already in wasn't.
Try the it-clefts and wh-clefts exercises
Try them yourself: these are the same exercises your students do in edio.
What's in the lesson
- 11 auto-checked exercises
- 3 games
- 2 teacher-checked tasks
- 1 real-life document
- 1 article
- 1 grammar scheme
- 1 set of word cards
- 1 audio clip
- 1 picture
- 1 transcript
The main objectives of this lesson are to:
- correct a wrong idea with an it-cleft: It was a configuration change, not an attack, that delayed the payouts.
- save the key point for the end with a wh-cleft or an all-cleft: What I'd suggest is that we test the cutover first. All we did was add a cache.
- choose the right form after is or was: What we need is to migrate…, What we did was roll back…, The reason is that…
- explain a technical problem to a non-technical manager in terms of money, time and risk, without jargon: Nobody lost a cent. What they lost was a day.
Lesson 3 completes the unit Talking to the team in English for IT C1 · Across the Company, after async updates and code review. It returns to the cleft sentences of English for IT B2 lesson 14, which gave a tech talk its emphasis, and points them at listeners outside IT; the next lesson opens the unit Shipping and incidents with conditionals without if. A finance chief who needs one sentence for the board wants the key point in the spotlight, and a cleft puts it there.
A box of questions about explaining tech to outsiders opens the lesson, then ten phrases with pictures and audio, from in plain English and a ballpark figure to under the hood and the cutover, and synonyms to match. Students read the CFO's email asking for straight answers and the engineering manager's blog post that gives them, then hear the two meet in an AI-voiced dialogue. The scheme leads into four self-checking drills, among them the manager's answers to complete with cleft phrases. In the chat, students calm a CFO who thinks the API is down, and a wheel asks them to explain an API, latency or technical debt without jargon.
Homework has three self-checking exercises, cleft sentences to match, the lesson's phrases to drag into the team's notes and a memory game of jargon and plain English, then two tasks the teacher reviews: an email to sales about two-factor authentication, and a recording that explains a real project to a friend.
- Grammar:
- cleft sentences · it-clefts · wh-clefts
- Topic:
- explaining tech · talking to stakeholders · plain English
Teaching tips
- Collect the class's own jargon first: each learner names three terms that colleagues outside IT ask about, and the class explains them with What it does is… or All you have to do is…
- Play the CFO for five minutes: fire questions from the email, such as Were we attacked? or Would more people make it faster?, and accept only answers with a cleft and no acronyms.
- Cleft one plain sentence three ways at the board: We noticed the problem on Tuesday becomes It was on Tuesday that…, What we noticed on Tuesday was… and It wasn't until Tuesday that…
- One-to-one, ask for an analogy: how would the learner explain their own system to a relative? Then compare it with the blog post's restaurant kitchen, which explains a migration that can't close the business for a night.
Liked it?
Teach the whole lesson in edio
23 exercises in 6 chapters, ready to teach. edio is an online platform for language schools and teachers: ready-made interactive lessons, live classes, homework and student progress in one place.
Start a free trial
7 days, no credit card.
Open the lesson
Find it in the library of 621 ready lessons. Teach it as it is, or copy any chapter into your own lessons.
Teach it live or as homework
Students work in their own accounts, in sync with you during the lesson, and the practice exercises check themselves.
The whole course: English for IT C1 · Across the Company
15 lessons at C1 for people who build software, in American English, with definitions instead of translations. The people of Kestrel Cloud, a fictional payments startup, write updates, reviews, RFCs and postmortems, explain tech to non-tech colleagues and negotiate scope. Real cases include the CrowdStrike outage and the xz backdoor.See the course
Unit 1 Talking to the team
async updates, code review and plain explanations: the future perfect, hedging, cleft sentences
Lesson 1Async Stand-ups: Status Updates People Can Act OnFuture forms for status updates
Lesson 2Code Review Without the DramaHedging in code review
Lesson 3 · you're hereExplaining Tech to Non-Tech PeopleIt-clefts and wh-clefts
Unit 2 Shipping and incidents
estimates, releases and outages: conditionals without if, phrasal verbs, modal perfects
Unit 3 Security and design
advisories, trade-offs and RFCs: passive reporting structures, concession and contrast, nominalization
Unit 4 Docs, metrics and meetings
READMEs, dashboards and follow-ups: participle clauses, describing trends, reporting verbs
Unit 5 Retros, interviews and AI
looking back and ahead: wish and would rather, inversion, formal obligation and permission











