Sign up for freeSign up

Write down the why: mixed conditionals for explaining decisions

Mixed conditionals join a past decision to its result today in this B2 English for IT lesson plan on architecture decision records.

Grammar
A past cause with a present result (If we hadn't cached the payments list, merchants wouldn't see their payments today) or a present state with a past result, beside the third conditional.
Topic
A mobile team letting merchants start refunds offline, and recording why, with words such as constraint, downside and supersede.
Activities
A decision record to read, a call arguing the decision, self-checking drills, a chat with support and role cards for a decision meeting, then an ADR to write and an argument to record.

What's inside

  1. Chapter 1Warm-up: Decisions at Work

    • PictureUnlock
    • Spin the wheel and talk about decisions at workSpin the wheelUnlock
    • Study the words for decision recordsVocabularyTry it
    • Look at the pictures and choose the wordChoose by pictureUnlock

  2. Chapter 2The Story: Write Down the Why

    • Read the story of Nygard's decision recordsArticleUnlock
    • Choose the correct answer about the storyQuizUnlock

  3. Chapter 3At Work: ADR 15, Offline Refunds

    • Read the mobile team's ADRArticleUnlock
    • True or false? Check the ADRTrue or falseUnlock
    • Sort the sentences into ADR sectionsSort into columnsUnlock

  4. Chapter 4Listen: The Devil's Advocate

    • Listen to Kenji and Priya argue the decisionListeningTry it
    • Transcript, for the teacherUnlock
    • Choose the correct answer about the callQuizUnlock

  5. Chapter 5Grammar: Then and Now

    • Study the scheme: mixed conditionalsGrammar schemeTry it
    • Choose the times: what is each half about?QuizUnlock
    • Fill in the gaps: rewrite the facts as mixed conditionalsFill in the gapsTry it
    • Choose the correct form: third or mixed?Choose the optionUnlock
    • Fill in the gaps with mixed conditionals: ADR 16's ConsequencesFill in the gapsUnlock

  6. Chapter 6Speak Up: Argue It, Record It

    • Choose the right replies to the support leadChatTry it
    • Open a box: role cards for the decision meetingOpen the boxUnlock

  7. Chapter 7Homework: Your Own ADR

    • Read your phrase bankReal-life documentTry it
    • Do you remember? Choose the correct answerQuizUnlock
    • Is the sentence correct? True or falseTrue or falseUnlock
    • Match the words and their meaningsMatchUnlock
    • Write an ADR for a decision at your workWriting, checked by the teacherUnlock
    • Record yourself arguing your decisionSpeaking, checked by the teacherUnlock

25 exercises in 7 chapters. Start a 7-day free trial to open all of them, copy any part into your own lessons, and teach the lesson live.

Vocabulary

12 words and phrases from the lesson, each with a picture and audio in edio.

+9 more with pictures and audio in the lessonMore words

  • a constraint
  • a consequence
  • a downside
  • offline mode
  • a sync conflict
  • supersede
  • revisit
  • go with
  • look back on

Grammar: mixed conditionals for looking back on decisions

A mixed conditional is an unreal if-sentence whose two halves sit in different times. Decisions need it, because a past choice shapes the system today: If we had built offline refunds first, we'd still be fixing sync bugs now. Learners ask which time each half is about, set both mixed patterns beside the third conditional and use them to explain why a team chose what it did.

Mixed conditionals: then and now

When you look back on a decision, the if-part and the result can be about different times.

Three unreal if-sentences

The third conditional keeps both halves in the past. A mixed conditional moves one half: a past cause with a present result (If we hadn't cached the payments list, merchants wouldn't see their payments today), or the reverse, a present state with a past result.

TimesIf-partResultExample
Past → past (third conditional)If + had + past participlewould have + past participleIf the app had saved the refund, Bruno wouldn't have walked outside yesterday.
Past cause → present resultIf + had + past participlewould + verb / would be + -ingIf we hadn't cached the payments list, merchants wouldn't see their payments today.
Present state → past resultIf + past simple (were)would have + past participleIf our team were smaller, we would have gone with drafts.

Present state, past result

This mix starts from a present fact: if + past simple, then would have + past participle, as in If the API didn't take those keys, I wouldn't have brought this to you. Questions work too: If your team were still that small, would you have chosen this?

  • If we hadn't made that decision, merchants with a weak signal wouldn't see their payments today.past cause → present result
  • If we had built offline refunds first, we'd still be fixing sync bugs now.past cause → an action going on now
  • If the API didn't take those keys, I wouldn't have brought this to you.present state → past result
  • If your team were still that small, would you have chosen this?present state → past result, as a question
  • If the app had saved the refund, Bruno wouldn't have walked outside yesterday.past → past: the third conditional

Which time is each half about?

Ask what time the if-part is about, then the result. Now, today and still call for would + verb or would be + -ing; yesterday and in the first version call for would have. Careful writing uses were for every person: If the team were bigger.

Which time is each half about?

Ask two questions: when is the if-part about, and when is the result about? Time words help: now, today, still → would + verb or would be + -ing; yesterday, last month, in the first version → would have + past participle. In the if-part, careful writing uses were for every person (If the team were bigger); was is common in speech.

If we chose, would have been: the traps

A past cause needs had + past participle: If we had chosen a managed database last year, not If we chose. A result with now takes would be, not would have been. And, as in the third conditional, the if-part has no would: If we had chosen drafts.

  • If we chose a managed database last year, we wouldn't be patching servers now.

    If we had chosen a managed database last year, we wouldn't be patching servers now.

    A past cause needs had + past participle.

  • If we had built offline refunds first, we would have been fixing sync bugs now.

    If we had built offline refunds first, we would be fixing sync bugs now.

    A present result: would + verb or would be + -ing, not would have.

  • If we would have chosen drafts, the app would be simpler now.

    If we had chosen drafts, the app would be simpler now.

    No would in the if-part.

  • If our team were bigger, we would build it last year.

    If our team were bigger, we would have built it last year.

    A past result needs would have + past participle.

More lessons on this grammar: Third and mixed conditionals lessons and exercises

Try the mixed conditionals exercises

Try them yourself: these are the same exercises your students do in edio.

More exercises

What's in the lesson

  • 13 auto-checked exercises
  • 2 games
  • 2 teacher-checked tasks
  • 1 real-life document
  • 2 articles
  • 1 grammar scheme
  • 1 set of word cards
  • 1 audio clip
  • 1 picture
  • 1 transcript

The main objectives of this lesson are to:

  • link a past decision to a present result: If we hadn't cached the payments list, merchants wouldn't see their payments today.
  • link a present fact to a past choice: If our team were smaller, we would have gone with drafts.
  • tell a mixed conditional from the third conditional by the time words in each half, such as now, still and yesterday
  • argue a decision and record it as an ADR: context, decision, status and consequences, the downsides included

Lesson 12 closes Architecture and trade-offs, unit 4 of English for IT B2 · Beyond the Code, with its work task: argue a decision and record it as an ADR. It builds on lesson 9's third conditional, now the if-part of the first pattern, and on the second conditional's if + past simple from English for IT B1 lesson 24. The homework reviews the whole unit. An ADR records a past decision and its effects now, the two times a mixed conditional joins.

A wheel of questions about decisions at work and twelve words with pictures and audio, from decision log to look back on, open the lesson, with a picture quiz. The story is Michael Nygard's 2011 post on architecture decision records. At work, students read the mobile team's ADR on offline refunds and sort sentences into ADR sections, then hear a tech lead argue it with a devil's advocate in an AI-voiced call. Four self-checking drills follow the scheme, among them facts to rewrite as mixed conditionals. Students then answer a support lead in a chat and hold a decision meeting from role cards.

Homework opens with a phrase bank for arguing a decision, then a quiz, a true-or-false set and a word match that check themselves. Last, students write an ADR for a real decision at work and record themselves arguing for it, and the teacher reviews both.

Grammar:
mixed conditionals · third conditional
Topic:
architecture decision records · trade-offs · offline mode

Teaching tips

  • Ask the two time questions for every example: when is the if-part about, and when is the result? Learners answer before they name the pattern, which keeps mixed and third conditionals apart.
  • Hold the decision meeting with a real goal: the FOR card sums up the ADR aloud at the end (context, decision, status, consequences), and the other roles push until the decision is clear.
  • In company classes, revisit one of the group's decisions, such as a tool they chose or a meeting they dropped, and have each learner write one If we hadn't…, we wouldn't… now sentence about it.
  • One-to-one, be the devil's advocate yourself: challenge each point of the learner's ADR as the staff engineer does on the call, and ask for a mixed conditional in every answer.

Liked it?

Teach the whole lesson in edio

25 exercises in 7 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.

  1. Start a free trial

    7 days, no credit card.

  2. 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.

  3. 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.

Teach it free for 7 days

The whole course: English for IT B2 · Beyond the Code

24 lessons at B2 for software teams, in American English. A year on at Kestrel Cloud, a fictional payments startup, Iryna and her team estimate work, write docs and postmortems, argue trade-offs, give demos and negotiate scope. Each lesson starts from a real case, from the Apollo 11 alarms to Conway's law.See the course

  1. Unit 1 Planning and estimates

    estimates and deadlines: approximating numbers, the future continuous and perfect, likelihood

    1. Lesson 1It always takes longerApproximating numbers in estimates
    2. Lesson 2By New Year's Eve, we'll have fixed itFuture continuous and future perfect
    3. Lesson 3Let's play planning pokerLikelihood with bound to, likely to and may well

  2. Unit 2 Docs people read

    specs and design docs: modals for requirements, participle clauses, plain English

    1. Lesson 4MUST, SHOULD or MAY?Modal verbs for requirements in specs
    2. Lesson 5Four kinds of docsParticiple clauses in documentation
    3. Lesson 6Just a request for commentsPlain English for design docs

  3. Unit 3 Incidents and postmortems

    telling an incident without blame: narrative tenses, the passive, the third conditional

    1. Lesson 7The 1202 alarmNarrative tenses for incident stories
    2. Lesson 8Blameless by designActive vs passive voice in a postmortem
    3. Lesson 9If we had had an alert…The third conditional: a different past

  4. Unit 4 Architecture and trade-offs

    comparing options and recording decisions: contrast linkers, modals of deduction, mixed conditionals

    1. Lesson 10Your system copies your org chartContrast linkers for comparing options
    2. Lesson 11It's always DNSModals of deduction for troubleshooting
    3. Lesson 12 · you're hereWrite down the whyMixed conditionals for looking back on decisions

  5. Unit 5 Demos and tech talks

    a clear structure on stage: signposting, cleft sentences, describing trends

    1. Lesson 13The mother of all demosSignposting language for demos
    2. Lesson 1420 slides, 15 secondsCleft sentences for emphasis
    3. Lesson 15Numbers that tell a storyDescribing graphs and trends

  6. Unit 6 Stakeholders and scope

    saying no and finding yes: diplomatic language, as long as and unless, negotiating

    1. Lesson 16Pay down the debtDiplomatic language for hard messages
    2. Lesson 17Why meetings argue about the bike shedAs long as, provided, unless and otherwise
    3. Lesson 18Yes, if…Negotiating language for scope and deadlines

  7. Unit 7 AI, security and ethics

    AI tools, passwords and team rules: be used to and get used to, past modals of deduction, purpose linkers

    1. Lesson 19Your new pair programmerUsed to, be used to and get used to
    2. Lesson 20Change your password? Maybe notPast modals of deduction
    3. Lesson 21Rules for AI at workPurpose linkers for rules with a reason

  8. Unit 8 Growing your career

    feedback, retros and goals: phrasal verbs, reporting verbs, wish and if only

    1. Lesson 22Your next levelCareer phrasal verbs and goal frames
    2. Lesson 23Feedback that helpsReporting verbs and their patterns
    3. Lesson 24Start, stop, continueWish and if only for wishes and regrets

Questions about this lesson

What are mixed conditionals?
Mixed conditionals are unreal if-sentences whose two halves are about different times. A past cause with a present result: If we hadn't cached the payments list, merchants wouldn't see their payments today. A present state with a past result: If our team were smaller, we would have gone with drafts. The B2 English for IT lesson Write down the why on edio.ai uses them to look back on design decisions.
How do you make mixed conditional sentences?
To make a mixed conditional, build each half for its own time. Past cause, present result: if + had + past participle, then would + verb or would be + -ing (If we had built offline refunds first, we'd still be fixing sync bugs now). Present state, past result: if + past simple, then would have + past participle (If the API didn't take those keys, I wouldn't have brought this to you).
What tense is "if I had"?
It depends on what follows: a participle points to the past; a noun means now. If I had known or If I had chosen is the past perfect, for a past that didn't happen. If I had more time is the past simple of have, for a present that isn't true. The result takes its own time: If we had chosen drafts, the app would be simpler now.
What are some examples of mixed conditionals?
Good examples put one half in the past and the other now: If we hadn't written down the reasons, new developers would still be asking about the cache. If the first version had had offline refunds, the team would be fixing sync bugs now. If the API didn't accept idempotency keys, we wouldn't have chosen offline refunds. Each if-part turns a fact around.
What's the difference between the third conditional and a mixed conditional?
In the third conditional, both halves are about the past; in a mixed conditional, one half moves to the present. Third: If the app had saved the refund, Bruno wouldn't have walked outside yesterday. Mixed: If we had built offline refunds first, we'd still be fixing sync bugs now. Time words decide: yesterday means would have; now and still mean would. A drill in Write down the why on edio.ai asks “third or mixed?”
Is it "If we chose" or "If we had chosen" for a past decision?
For a decision in the past, use had + past participle: If we had chosen. If we had chosen a managed database last year, we wouldn't be patching servers now. If we chose is the past simple, which after if describes an unreal present or future: If we chose drafts today, we'd write less code. The time of the choice decides the if-part; the time of the result decides the other half.
Is it "would be" or "would have been" with now?
With now, the result takes would be or would + verb: If we had built offline refunds first, we would be fixing sync bugs now, not would have been fixing. Would have + past participle is for a past result: If our team were bigger, we would have built it last year. A true-or-false item in the homework of Write down the why on edio.ai sets exactly this trap.
What is an architecture decision record?
An architecture decision record, or ADR, is a short document about one design choice and its reasons. Michael Nygard described the format in 2011: a title, the context in neutral language, the decision in sentences that start We will…, the status (proposed, accepted, deprecated or superseded) and all the consequences, good, bad and neutral. ADRs are numbered and kept with the code; a changed decision gets a new ADR that supersedes the old one.
How do you argue for a technical decision in English?
Give the context, the decision and its honest cost: The problem we're solving is refunds with no signal. We considered drafts and online-only. We went with offline refunds because the API takes keys. Name the downside and accept it (The cost of this is more sync code. We accept that support gets some calls.), then look ahead: We'll revisit this when we have three months of numbers.
How do I teach mixed conditionals to B2 adults?
Start from two facts at different times: We built the cache. Merchants see their payments today. Learners imagine the opposite of the past fact and keep the present result: If we hadn't built the cache, merchants wouldn't see their payments today. Then set it beside a third conditional, and give working adults a real decision from their jobs to look back on.
What's good homework for practicing mixed conditionals?
Good homework is a decision record that looks back: context, decision, status and consequences, with one If we hadn't…, we wouldn't… now sentence and a date to revisit it. Write down the why, a B2 English for IT lesson on edio.ai, asks for that ADR and a recording that argues for it, both for the teacher to review, after a quiz, a true-or-false set and a word match that check themselves.
Are there interactive exercises for mixed conditionals?
Yes: gap-fills and chats that check each form help learners match each half to its time. Without an account, this page plays four parts of Write down the why, a B2 English for IT lesson on edio.ai: Kenji and Priya arguing the decision, a gap-fill that rewrites facts as mixed conditionals, a chat with the support lead and the phrase bank for arguing a decision. The other drills are locked.
Unlock full lesson

Teach this lesson with your students

Book a demoStart free trial

No credit card required