Learn with Phoebe Β· Data & Analytics

Learn Asking the Right Questions as a Data Analyst with Phoebe

An operations director asks for a sales dashboard. Six weeks later there is a correct dashboard, nobody opens it, and the six outlets that were running out of chronic medication are still running out, because "dashboard" was the only word she had for that and nobody in the meeting asked what would be different if it worked. Most of what goes wrong in data work goes wrong in the first meeting, quietly, with both sides sure they agreed. Six sessions on running that meeting as a data analyst: the six doors every discovery conversation has, the order to open them, the plain second sentence that lets a business person learn how data work thinks while she answers, and a bench that puts one invented operations director with 24 hidden facts in your browser and counts what each way of asking is worth.

6sessions
6doors
24hidden facts
5ways of asking, counted
45min per session

The six sessions 🎯 · from "we need a dashboard" to a brief she can read

The running case is Harbourline, an invented chain of 38 pharmacy and clinic outlets across Singapore and Malaysia, and its operations director Adeline Tan, who has never heard the word pipeline. Every fact on her sheet is printed in the bench's bank file; the course claims the mechanism, never the numbers as facts about pharmacies.

πŸšͺ Session 1 Β· core

Why the gap exists, and the Six Doors

Tappers and listeners, the curse of knowledge on both sides of the table, the six doors every discovery meeting has and the order to open them, and the teach-back line. Build-along: your own Six Doors sheet for a request you have right now.

β–Ά Start herethe framework, canonical
πŸ—ΊοΈ Session 2 Β· core

Reading their data state in plain words

A five-rung ladder of questions that gets the real state of the data out of a person who has never seen a schema: typed on a Friday or recorded by a till, who owns the codes, who holds the only login. You draw the data-state map from her answers.

door 4, opened plainly
πŸŽ›οΈ Session 3 Β· bench night

The analyst's questions, and the bench

Five kinds of question, and one operations director with 24 hidden facts run five ways in your browser. The fast yes-or-no interview scores 15 and records five things that are wrong; the Six Doors score 48; tuned for an analyst, 52. Then you take the chair.

β˜… the bench
πŸ’¬ Session 4 Β· core

Teaching while you ask

The second sentence on every question, rewritten for a person who has never seen a table. The one concept per meeting worth explaining properly, twelve teach-back lines, and how to tell a lesson from a lecture.

one concept per meeting
🌱 Session 5 · core

From pains to three joint projects

Her answers become an opportunity tree, the tree becomes three candidate projects with a first step each, and a prioritisation you write down. Why the first project is a pilot in four outlets and not a rollout to 38.

three candidates, one first step
πŸ“„ Session 6 Β· capstone

The mock meeting and the one-page brief

A full 45-minute run on the bench with your own sheet, scored, then the one-page brief she can read: what you heard, what you will build first, how you will both know, sent within 24 hours. Final scorecard.

πŸ”’ final scorecard
core bench night capstone

Your passport 🎫

Clear all three quiz questions in a session and it gets stamped. Six stamps means you can walk into a meeting with a business person who knows nothing about data, leave with the decision, the current way and the real data state, and send a brief she can read the next morning. Stamps live in this browser only.

Four chairs at the same table πŸͺ‘

The same framework, the same company and the same bench engine, built four times for four roles. Each course marks a different door to open widest and carries its own question bank and fact sheet. The framework itself lives in this course's session 1; the others link to it.

What this is not, so you land in the right place 🧭

If your question isGo here instead
I am the executive. How do I read a number with confidence and brief an analyst?Data Literacy β†—
I have been handed a question. How do I sharpen it and say what the data can and cannot answer?Data Thinking β†—
How do I present findings, handle a room, and influence a decision?Communication β†—
How do I run product discovery as a discipline, week after week?Product Thinking β†—
How do I frame a decision properly, with options, evidence and a call?Decision Intelligence β†—
What is a data maturity model, and how do I run a real assessment?Governance 101 β†—
I am the data person. I have 45 minutes with a business person who knows nothing about data, and I need to leave with something I can build.you are in the right place

The first meeting, run by the data side. The decision, the current way and the real data state, got out of a person in words that teach her something as she answers. Reading numbers, sharpening a handed question, presenting, and discovery as a product discipline are each taught once, in the course that owns them, and linked from here rather than repeated.

Choose your path πŸ—ΊοΈ

Three doors into the same conviction: the way of asking, not the person across the table, decides what you leave with.

πŸšͺ I have a meeting on Monday 1β†’ 3β†’ 6 the sheet, the rehearsal on the bench, the brief you send the next morning
πŸ“Š I keep getting asked for dashboards 1β†’ 2β†’ 5 the outcome behind the request, the real data state, three projects that are not a dashboard
🎯 The whole meeting 1β†’ 2β†’ 3β†’ 4β†’ 5β†’ 6 from the request as received to a brief she can read, with her learning something on the way

What is honest here 🧾

The company is invented and says so on every page that uses it. The bench is counted from a printed file. Where a page rests on a book or a paper, it says which and how it was read, and where a widely quoted number could not be traced, the page says that instead of quoting it.

ClaimStatus
Harbourline, Adeline Tan, and every fact on her sheetConstructed. Written to be typical of a mid-size retail chain; printed in full in the bench's bank file; never a claim about a real business
Every count on the bench: net value, false beliefs, doors, the 20-minute counterReally computed in your browser from the printed bank, and verified headlessly in node before any page quoted a number
Tappers and listeners: about 50 percent predicted, 3 of 120 namedReported from Heath and Heath, Made to Stick (2007), citing Newton's 1990 Stanford dissertation, which was not read at source
Measurement as a reduction of uncertainty about a decisionHubbard, How to Measure Anything (2014), definition as it appears across summaries; the book was not opened here
Ask about the past, not the future; people say yes to be politeFitzpatrick, The Mom Test (2013). Only his verified wording is quoted; a paraphrase that circulates as a quote is not
The analytics translator role and its predicted headcountRole named from the 2018 HBR article; the headcount figure was not read at source and is not quoted
"Data scientists spend 80 percent of their time cleaning data"Not claimed as one figure. Two different sources say two different things, and session 2 quotes both as they stand

The knowledge map 🧠

The whole course at a glance - hover a session to spotlight its concepts, click any node to jump in.