Lexis Lesson · Explain It to the New Guy

01

Warm-up · 4 min

Your wall

Name the retaining wall assembly you prepared and its main layers, in any order for now.

Predict

Before you name your layers, predict:

1. What changes when you explain a wall to someone who has never built one, compared to a colleague?

Nothing — the explanation is identical You add the why at each step, not just the what You use more technical jargon

02

Input · 8 min

Explaining to someone new

What changes when the listener has never done this before

To a colleague: "Base, geogrid, first course, backfill, repeat."

To someone new: "First, we compact the base — that has to be solid before anything else happens. Then a layer of geogrid goes down; that’s what stops the wall from sliding forward over time. Once that’s in, the first course of block goes on top of it."

The second version adds the why at each step, not just the what. A new crew member who understands why the geogrid matters is less likely to skip it under time pressure later.

Discovery Check

Check what you just read.

1. What does the geogrid stop, according to the "someone new" version?

The wall from cracking The wall from sliding forward over time The base from washing out

2. Why does explaining the "why" matter for a new crew member?

It sounds more professional Someone who understands why is less likely to skip it under time pressure later It is required by code

03

Focus on Form · 8 min

Adding the reason

Explaining why, not just what

Listen and repeat.

When to Use It

Match each phrase to when you would use it.

Explaining what a step prevents

Explaining a dependency between steps

Warning about a consequence

Giving a direct justification

04

Controlled Practice · 12 min

What or why?

MCQ Reading

Choose the explanation that would actually help someone new.

1. Explaining the geogrid layer to someone who has never installed one:

"Geogrid goes here." "A layer of geogrid goes down — that’s what stops the wall from sliding forward over time." "You need geogrid for this kind of wall."

2. Why explain the reason for a step, not just the step itself, to someone new?

It takes longer, which looks more thorough. Understanding why a step matters makes someone less likely to skip it under pressure later. It is required by code.

05

Pushed Output · 18 min

Explain it to the new guy

Live, no drawing, someone who has never done this before.

Task card

Marcus, a new crew member, on his first day — invented for this exercise

Explain the full retaining-wall assembly, step by step, with a reason at each step.

Base to top, in order — this is Lesson 2’s bottom-to-top habit, spoken now instead of read.
Every step gets a "why," even briefly.
Marcus will ask "why" out loud at least once. Answer him properly, not with "because that’s how it’s done."

Before You Start

Complete this reminder before Marcus arrives.

Base to top, in — this is Lesson 2's habit, spoken now instead of read. Every step gets a " ," even briefly.

Teacher note Play Marcus as genuinely curious rather than difficult — ask "why" once, mid-explanation, on whichever step seems least justified. Watch whether she has a real answer ready or falls back on "that’s just how it’s done," which is not actually an explanation.

06

Feedback · 6 min

Did you answer the why?

When Marcus asked "why," did you give a real reason or fall back on "that’s how it’s done"? If the second, what would the real reason have been?

Real Reason or Not?

Match each response to what it actually is.

Names what the step prevents

Avoids giving any real reason

Names a dependency between steps

07

Wrap-up · 4 min

Before the next lesson

Homework. Say "stacked," "poured" and "compacted" out loud, slowly. Notice the sound at the end of each one — they are not the same.

Quick Check

One check before you go.

1. What should you notice when you say "stacked," "poured" and "compacted" aloud?

Their meaning The sound at the end of each one How fast you can say them