Teaching while you ask

Take any teach-back line on your sheet and read it aloud to someone who does not do data work. Any word that makes them say "sorry, what do you mean?" is a jargon cost, and session 3's bench prices it: the question takes five minutes instead of three or four, because you have to explain, and it costs a point of trust, because she is a little less sure you understand her shop. The technical opener asked five of those in a row, spent 25 of the 45 minutes, and scored 15. A teach-back line was meant to earn trust. With one wrong word it spends it.

The engineer's usual offenders, with the plain words that replace each. Pipeline: the steps a number goes through from the till to the report. ETL: copying numbers out of one system, tidying them, and putting them into another. CDC: copying each change as it happens, instead of the whole file once a week. Schema: the list of columns and what each one means. Idempotent: safe to run twice, so running the copy again does not count a sale twice. SLA: the promise about when it arrives. Warehouse: the one place all the copies are kept. Medallion: keeping a raw copy, a tidied copy and a report-ready copy, one on top of the other. None of the plain versions is longer than a breath, and every one describes a thing she already knows exists: a file, a copy, a promise, a place.

The test is not "would a smart person understand this". Adeline runs 38 outlets across two countries; she is a smart person. The test is whether the word is one she uses at work, and the honest way to find out is her face, which is why the reading is done aloud and never on paper.

Douglas Hubbard's definition of measurement, a quantitatively expressed reduction of uncertainty based on one or more observations, is itself a plain sentence. It contains no term of art, and a finance director can check it against her own experience without a glossary. Precision and plainness are not in tension; the words that sound precise to an engineer are usually just familiar to an engineer.

There is a professional reason plain is the norm and not a courtesy. The person paying for the work has to be able to check it, and here the person checking it after her is an auditor. A teach-back line she cannot decode is a claim she cannot test, and a claim she cannot test is one she either accepts on faith or quietly ignores. Both are bad for you: the first because faith runs out on the first number that still does not match, the second because you have spent a sentence and taught nothing. Plain words are how an engineer makes the reasoning behind a build inspectable by the person who has to sign it off.

Look at the five false beliefs the bench records on the fast run, because each one is a concept that was never explained. "The POS is the source of truth" and "finance's number is simply wrong" both attach to timing: the bank file marks both as contradicted by the same fact, that card settlements land two days late and cash is deposited weekly. "Pull everything daily" attaches to freshness: Monday's reorder needs weekly, month-end needs day three. "The vendor API is already in use" attaches to what exists versus what is possible: nobody has ever used it. "Stock lives in the POS" attaches to which copy is real: there are three spreadsheets, and the one Priya trusts is on her laptop. Pick the belief most likely to form in this meeting with this person, and the concept behind it is your one.

For Harbourline the choice is close to forced. The two numbers disagree about timing, not truth, because two of the five beliefs attach to it, because her opening line is literally the question it answers, and because the auditor asked it in writing. On the fast run, "So finance's number is just wrong?" is the fourth question asked and is in the notes by minute 5, before a single true fact. The other candidates are real, and the next meeting can have one of them. Choose one, not two; two concepts at ninety seconds each is a lecture with an interval.

Three sentences, in a fixed order: what it is, why it costs, what it means for her month-end. Written in full for the timing concept, as it would be said right after she answers "where does finance's revenue number come from, step by step?":

What it is. "The till counts a sale the moment it rings up, and finance counts it when the money reaches the bank, so on any given day the two systems are counting sales from different days." Why it costs. "Card money lands two days after the sale, cash goes to the bank once a week, and refunds are only ever entered in the accounting system, so the POS never sees them, and copying either number into a new report faster would only show you the same gap sooner." Her month-end. "Finance posts by the fifth working day, so if we have the numbers by day three we have two days to line up the late card money, the weekly cash and the refunds, and whatever is left after that is the part of the two percent worth a real question."

Ninety seconds, then back to the next question. Notice what the version does not say: it does not say the whole two percent is timing. Her sheet says it is mostly timing, and the honest sentence leaves room for the rest. The tell that it worked is that she uses the word "timing" herself later in the meeting, as a reason rather than an excuse.

Adeline told you that last month the auditor asked which number was right, and she could not tell him. If the one concept landed, next time she can say something like "the two numbers count the same sales on different days; card money lands two days late, cash weekly, and refunds only exist in finance's system." That sentence is the whole test: it is hers, it is short, it carries the reason, and it would survive a sceptical follow-up from a person whose job is sceptical follow-ups. If instead she says "the data team is looking at the sync", the concept was heard and not learned.

Write the sentence you hope she says before the meeting. It forces the ninety seconds to be built backwards from a line a non-data person could carry, and it is the cheapest rehearsal there is. It also checks the choice itself: if you cannot write a one-line version an auditor would accept, you have picked an idea that matters to you and not to her.

Failing, before "who can log in to each of those, and pull an export?": "Credential ownership is usually the critical path on an integration, and if the POS admin account is a single point of failure we would want a service account issued before any CDC or ETL is scoped." True, and it fails all three tests at once: five words she would ask about, two claims joined into one, and a design hiding inside a reason.

Passing, same question, as the bank prints it: "Access is the first blocker on most data projects, so I ask early and I ask by name." Plain, because every word is one she uses; true, because it is how these projects stall; one sentence, so she is answering again within three seconds. On the bench's tuned order this is the seventh question, asked once trust already stands well above the level her most sensitive fact needs, and it is the one that brings out Kenneth: the only IT person, the only POS admin login, leaving in January, and the team has not been told. The failing version would have earned a nod and no name.

There is only one proof that a line taught something, and it is a follow-up question from her. "So if we waited for the card money, would they match?" means timing landed. "Wait, which of the three stock sheets would you use?" means the real-copy line landed. A nod proves nothing, and a polite "makes sense" proves slightly less than nothing, because it closes the topic. Silence after a teach-back line is a reason to ask your next question, not to add a sentence.

On the bench this is the mechanism, not a metaphor. Every open question earns a point of trust, and seven of the 24 facts on her sheet sit behind a trust gate she will not cross unprompted. The teach-back line is where that point is earned: she answers the next question more fully because the last one came with a reason. A lecture spends minutes and earns nothing, which is the same arithmetic as the technical opener in session 3 with a friendlier face.