Where we start
A discovery meeting produces two things: what is in your notes, and what is in her head. The bench in session 3 counted the first. The brief is how the second is fixed in place before it fades, and it is also the first piece of work she sees from you, which makes it her first evidence about whether the next nine weeks are worth her time. For a data scientist the brief carries one extra weight: she asked for a prediction, and the honest first step is not one. Harbourline and Adeline Tan are constructed, as on every page here; the brief you write tonight is for a real request if you have one, and for hers if you do not. The corridor the brief is built on, the Six Doors ↗, is drawn in full in the analyst's session 1.
★ What you walk out with tonight. One scored run of the full meeting with your own sheet, a one-page brief ready to send whose first step records the thing nobody has recorded, and the eight-row ship gate that says whether it goes out tomorrow morning or needs another hour first.
Your meeting, read against the ladder
5 min liveOpen the bench on session 3 in a second tab, reset the lower half, and run the whole 45 minutes with your printed sheet beside you. Do not look at the preset transcripts first. When the clock reaches zero, write down four numbers: net value, false beliefs, doors opened, and the value in your notes at minute 20. Then read them against the ladder below, which is this bank's and nobody else's.
LiveReading your four numbers3 min▶
False beliefs first. Any number above zero means a leading question slipped through, and on this bank each one is a modelling decision you will get wrong in week six. "So you want to forecast sales, right?" records the costliest of the five: the target is a stock-out, not sales, and last year's vendor already built the sales forecast nobody used. Find the leading question in the transcript, write the open version on your sheet, and carry that version into the real meeting.
Doors opened. Six is the only answer that lets you write a brief without guessing. A shut door is a block of the brief you cannot fill. In the 200 shuffles on this bank, the doors most often left shut are constraints and decision, and decision is the one a scientist cannot afford: it holds the Thursday van, and a prediction that arrives on Friday is useless.
Net value against the ladder. The Six Doors in printed order score 46 blind; tuned for a scientist, outcome first and widest, 55. A run in that region means the sheet works. A run near the shuffle's 27.5 means the questions are good and the order is not: usually the outcome door was opened late, or the technical opener crept in early and spent trust the rest of the meeting needed. The technical opener, labels and class imbalance first, scores 10, below the efficient interview's 15.
The 20-minute counter. The tuned order puts 24 points in your notes by minute 20; the printed order, 20. If she is called away halfway, that is the meeting you actually had. The efficient interview sits at -5 at minute 20, because its five wrong beliefs are recorded in the first ten minutes and its facts come later.
Self-studyWhat the bench cannot see, and what even the best order misses2 min▶
The bench scores what you asked and what came back. It does not hear your tone, see whether you looked at her or at your laptop, or notice the moment she leaned forward because a question was about her actual Thursday. Those matter, and no widget measures them honestly. The run is a rehearsal for the order and the kinds, not a verdict on you as an interviewer.
Even the tuned order leaves gaps, and they matter for the brief. It asks eleven open questions in 45 minutes and stops before the lead-time question, the "when do you next have to show something upward?" question and the question about who holds the POS login. So its notes have no five and nine days of supplier lead time, no six-week board date, and nothing about Kenneth. The brief must not write those as facts. They go in the covering note as questions, which is where session 5 said they would go.
The rehearsal that found the leading question. A constructed case. A data scientist ran the bench twice before a real discovery meeting about a forecast. The first run had one false belief: "accuracy is what matters most, yes?" had slipped onto her sheet as a check she meant to make at the end. She rewrote it as "when it happens, what does it cost you? And what does it cost when an outlet orders too much?" and moved it up to the second question. In the real meeting that open question produced two costs of very different sizes, and the brief she sent the next morning asked for agreement on the ratio between them instead of promising an accuracy figure nobody on the business side could check.
One page, in her words, sent within 24 hours
6 min liveThe brief is not minutes and it is not a model proposal. It is the meeting handed back to her in a form she can check, correct and forward to the board without rewriting. It has six blocks, each fed by a door, and every sentence in it is either something she said or something you will do. If she reads it and says "yes, that is what I meant", the gap from session 1 is closed. If she corrects a block, it was worth sending for that alone. For a scientist, block 4 carries the weight: it tells a person who asked for a prediction that the first step records the thing a prediction would need.
LiveThe six blocks, and the rule for each4 min▶
1 · What you told me, in your words. Two or three sentences she said, quoted. Not your summary, and not your restatement of the target. "We keep getting caught" and "a patient turns up and the shelf is empty" are hers; "predict stock-out events at outlet-product grain" is you tapping the tune. The base rate goes here too, in the form she gave it: roughly 30 a month across the 38 outlets, and she knows because each one becomes a complaint call. If you misheard, this is the block she corrects, and it costs one email instead of six weeks.
2 · The decision this will serve. The action, the person, the deadline, from door 2. One line: the area manager moves stock between outlets on Thursday's van run, per outlet per product, once a week. If you cannot write it, you did not open the door, and the brief should say "I still need to understand who acts on this and by when" rather than invent a daily forecast nobody asked for.
3 · What has been recorded, and for how long. Session 2's ladder, as five lines, each marked recorded, typed or not recorded, with the baseline written in: today the pharmacist looks at the shelf and WhatsApps the area manager, and that catches most of them. End with one question: "which of these is wrong?"
4 · What I will build first, and what I will not. The pilot from session 5 in one sentence: a daily stock-out log in four outlets, the Johor pharmacist first. Then one sentence naming what you are deliberately not doing yet: no model, until eight weeks of logged stock-outs exist and a plain rule has a record to beat. Saying "no model yet" out loud, to a person who asked for a prediction and a board that wants the word AI on a slide, is the most useful line in the brief. It is also the line that most needs her agreement, so ask for it by name.
5 · How we will both know. Her success test, in her words: the complaint calls about empty shelves go down, and she counts them herself. Then the guard rail, written as your reading for her to correct: an over-order costs expiry write-off, which head office measures her on, so the calls must not come down by filling every shelf. Both costs of a wrong guess, in one block. Not an accuracy figure.
6 · Who does what next week. Names, a day, a time, one task each. Fitzpatrick's test for whether a conversation went anywhere, as reported, is whether the other side committed something: time, a name, an introduction. The Johor pharmacist already did, before you asked; this block is where that offer, and Priya's two hours a week, are written down so they cannot quietly lapse.
LiveWhy 24 hours, and why one page2 min▶
Within a day she still remembers what she meant, so a correction is cheap and specific. After a week she remembers that you came by, and a brief arriving then reads as a proposal to be evaluated rather than a record to be checked. No study is quoted for the 24 hours; it is a working norm, and the reason is the one above.
One page because she will read it on her phone. Her area managers read everything on their phones, in the van, and so does she between outlets. Two pages is a document; a document goes into a folder to be read later; later is after the board. If a block needs more than three lines, the detail goes in an attachment she can ignore.
Self-studyWhat the brief must never contain2 min▶
A word from the jargon column of session 4: labels, class imbalance, precision, recall, a holdout. An accuracy figure, promised or estimated, for a model that has nothing to learn from yet. A number you have not seen stated as if you had, including the supplier lead times and the board date if your run never reached them. A timeline longer than the date she gave you. And a fact she told you in confidence, most importantly the one about Kenneth leaving in January, if trust ever ran high enough for her to say it: it shapes block 4, because the first step must not depend on a login that disappears, but it goes into your plan and not into a page she may forward to a team she has not told. The brief is hers to forward. Write it as if it will be.
The "no model yet" line that got a yes. A constructed case, with the shape that recurs. A scientist sent a brief whose block 4 said, plainly, that the first nine weeks would record stock-outs rather than predict them. The reply came the same afternoon, and it was not a push back. It was a correction to block 3, a fourth copy of the stock spreadsheet nobody had mentioned, and one line under block 4: "good, that is the slide I can defend". The board wanted AI; she wanted something she could stand behind in the room. A record from four of her own outlets was that.
The ship gate for a scientist's brief
4 min liveEight rows, each scored 0, 1 or 2 against your own brief. Five are the scientist's: the target in her words, the base rate, both costs of a wrong guess, the baseline, and no model promised before there is anything to learn from. Three are shared with every discovery brief: no unconfirmed leading question, the read-aloud test, names and days. This gate is strict on purpose: a brief that half-names the target is read by the business as a brief that has one, and the gap it leaves opens again in week six. Anything under 16 of 16 gets another hour before it goes out.
Write the brief she reads tomorrow morning
★ 22 min · everyone writesSix blocks, one page, built from the three artifacts you already have: the Six Doors sheet from session 1, the recorded-data ladder from session 2, the tree, grid and pilot from session 5. Nothing new is invented tonight. Every line is either something she said or something you will do, and anything your run never reached goes in the covering note as a question. The worked example below is Adeline's, written from her fact sheet, and the days and times in block 6 are constructed.
Block 1, her words and her count. Open your sheet and copy two or three of her sentences exactly. Pick the ones closest to the outcome, not the request: the request is "predict", the outcome is the empty shelf. Add the base rate in the form she gave it. If your sheet has no quote in her words, that is the first thing to fix, and the brief should ask rather than guess.
Blocks 2 and 3, the decision and the ladder. One line for the decision, with its day. Five lines for what has been recorded, each marked recorded, typed or not recorded, with today's check written in as the baseline, ending with the question.
Block 4, first and not yet. The pilot from session 5 in one sentence, then one sentence naming what you are not building, with the condition that would change it. The first step must need no budget this quarter and must not depend on a single login. Then ask for her agreement to the second sentence, by name.
Blocks 5 and 6, how we know and who does what. Her test in her words, then the guard rail as your reading for her to correct. Names, a day, a time and one task each.
Read it on your phone, then score it. Send the draft to yourself, read it on the phone standing up, and run it through the eight-row gate above. Anything under 16 gets fixed before it is sent. Then send it, within 24 hours of the meeting, with a covering note that carries the questions your run never reached.
The reply is the second meeting. Whatever she corrects is the most valuable fact you will get this month, because it is the one you would otherwise have built wrong. Put it straight into the sheet, the ladder or the tree, and send a one-line thank-you that says what changed.
After the sessions
1 week- Run the real meeting. Take your sheet to the real request, open the outcome door first and widest, walk the rest, and send the brief within 24 hours. Score it on the gate before it goes.
- Log the reply. Write down every correction and which block it was in. Block 1 corrections mean you heard the request and missed the target; block 3 corrections mean the ladder was guessed; a push back on block 4 means the "no model yet" line needs a conversation, not a rewrite.
- Re-run the bench with the question you would now ask first, and compare the run with your session 3 attempt. The gap is what five sessions bought.
- Teach one teach-back line to a colleague on the modelling side, and ask them to use it in their next meeting. The one worth starting with: "How often it happens is the first number any prediction is judged against. If it is rare, a model that says 'never' looks accurate and is useless."
Three questions
Clear all three and session 6 gets stamped in your passport.
1 · Your run on the bench scores higher on net value than a colleague's, but it records two false beliefs, one of them "the target is sales". Your colleague's records none. Whose meeting was better, and what do you do next?
Read false beliefs before net value. The efficient interview opens every door on this bank and still scores 15, below the shuffle's mean of 27.5, because its five false beliefs are subtracted from what it found. "The target is sales" is the costliest of them: it is the forecast last year's vendor built and nobody used.
2 · She asked "can we predict which outlets are going to run out of stock?" Why does block 4 of your brief say "no model yet", and why do you ask for her agreement to that line by name?
The POS holds three years of sales, which is plenty of history for the wrong question. The stock spreadsheet is overwritten every Friday and the only record of a stock-out is a complaint call. The pharmacist catches most of them, not all, which is exactly why a model might one day be worth scoring against her check, once there is a log to score it on.
3 · Suppose trust ran high enough that Adeline told you Kenneth, the only IT person and the holder of the POS admin login, is leaving in January, and that she has not told the team. Where does that fact go?
The fact shapes the work and does not appear in the document. On this bank it needs the highest trust of any fact, and even the tuned order does not reach the question that surfaces it in 45 minutes. When you do hear it, write the brief as if it will be forwarded, because it will be.
What this session teaches, and where it came from
Every fact on this page, and its verification tier, is recorded in the course's source map.
Session 6 cheat sheet · pin this
The same corridor, the same company and the same bench run for three other roles, each opening a different door widest. A data analyst starts at the decision: who acts on a number, and by when, in Asking the Right Questions as a Data Analyst ↗. A data engineer starts at the data state: every system a sale touches and which copy is real, in as a Data Engineer ↗. An AI developer starts at the current way: one real thread, end to end, and which replies a person must keep, in as an AI Developer ↗. Everything else on the shelf is at Learn with Phoebe ↗.