One per day of the program. Each comes with drills inside Retake; here is the idea, the reason it works and how to do it.
DAY 01 · DELIVERYTrade “um” for silence
Silence does everything a filler does, and it makes you sound like you meant it.
Clark and Fox Tree (Cognition, 2002) treat fillers as signals about upcoming delay, not as errors. A silent pause tells the listener the same thing (“thinking, still my turn”) without marking you as unsure. A coaching heuristic worth knowing: the pause that feels endless from the inside usually measures under a second on the recording, so speakers almost always under-pause.
BEFORE“So, um, basically what we're doing is, like, we're trying to, uh, move onboarding to, you know, a more self-serve kind of model, um, so that sales doesn't have to be in, like, every single deal.”
AFTER“We're moving onboarding to self-serve. [pause] That way, sales doesn't have to be in every deal. [pause] The first version ships in March.”
- Find your top two fillers. Most people have one dominant word; you can't swap what you haven't spotted.
- Close your lips at the end of every sentence. You physically cannot say “um” with your mouth shut.
- Breathe where the filler used to be. Same timing, no sound.
- Slow your first five words. Fillers spike at the start of an answer; a calm opening sets the rhythm for everything after it.
- End sentences sooner. Every “and, um…” is a sentence that wanted to stop.
Try it today: In your next meeting, speak at least once and end every sentence with a closed mouth. Then quietly count a colleague's fillers for one minute. Once you can hear them in other people, you'll start hearing them in yourself.
DAY 02 · DELIVERYSpeak at the speed of meaning
Speed the context, slow the point.
Listeners decode words faster than they integrate ideas. Pace changes and pauses give them time to integrate, and they also act as emphasis: a sudden slowdown marks a sentence as important without you having to say “this is important”. The 140–160 wpm band is a commonly cited heuristic, not a hard finding; the drills here use a band of roughly 130–170.
BEFORE“[one breath, racing] So we checked the numbers and it's actually pretty interesting because churn went down but signups also went down so overall we're flat which is what it is and next week we'll look at pricing.”
AFTER“We checked the numbers. Churn went down. [pause] But signups went down too. [pause] So net, we're flat. [slower] Next week, we test pricing.”
- Find your baseline: record 45 seconds of normal talk and check your wpm. Most people are surprised in one direction.
- Put a full stop where you'd normally say “and”. More sentences means more natural gaps.
- Mark the one sentence that matters most and deliver it at roughly two-thirds speed.
- Pause for a beat after any number, name or decision. Let it land before you move on.
- When you feel yourself racing, lower your pitch slightly. A lower voice is hard to rush.
Try it today: On your next call, find the one sentence you most need people to remember. Say it slower than everything else, then stop and let the silence sit for a beat before you go on.
DAY 03 · DELIVERYThe power pause
Pause before the point to make them lean in; pause after it to make it stick.
Listeners process speech in real time and can't scroll back, so silence after an important sentence is the only processing time they get. A pause before a point works through anticipation: an unexpected gap draws attention to whatever breaks it. The one-to-two-second and over-three-second thresholds are coaching heuristics, not research cut-offs.
BEFORE“We looked at the data and found that forty percent of our support tickets come from the same three bugs, so if we fix those we'd cut the load a lot, which I think is the obvious next step really.”
AFTER“We looked at the support tickets. // Forty percent / come from the same three bugs. // Fix those three, / and we cut the queue almost in half.”
- Before any key number or claim, stop for one beat.
- After it, stop again and look at your listener. Count “one-and” in your head.
- At every change of topic, take a full breath. That is your “//”.
- If you lose your thread, pause instead of filling. Two seconds of silence feels long to you and normal to them.
- Never let a pause pass three seconds. If you need longer, say a bridge line: “Let me think about that for a second.”
Try it today: Next time you share a number or a decision in a meeting, pause before it, say it, then hold eye contact for one full second before you continue. Notice who looks up.
DAY 04 · DELIVERYEscape the monotone
Choose one word per sentence that matters, and make your voice say so.
Listeners use prosody (pitch, stress, timing) to work out what is new and important in a sentence; flat delivery removes those cues, so the listener has to work harder and attention drops. This app measures pitch variety as the spread of your pitch in semitones: under about 2 tends to sound flat, 3 and above sounds lively.
BEFORE“[all on one note] This quarter we grew revenue by twelve percent which is the best quarter we have had and the reason is the new pricing model so we want to roll it out to the other regions.”
AFTER“This quarter we grew revenue by **twelve** percent. [pause] That's our **best** quarter, ever. And the reason is simple: the **new** pricing. So next, we take it to **every** region.”
- Before you speak, pick the one operative word in your key sentence.
- Hit it with one dial: a pitch lift, extra volume, or a pause just before it.
- Practise at 150%: it should feel slightly too much. Listen back before you judge it.
- Drop your pitch at the end of statements. Down means done.
- Smile on the good news. You can hear a smile; it changes the shape of your mouth and the sound with it.
Try it today: Before your next update, write down your key sentence and underline the operative word. When you say it, lift that word and pause just before it.
DAY 05 · DELIVERYDrop the hedge
Say it once, say it plainly, and if you're unsure, say exactly how unsure.
Hedges and tag questions are cues listeners use to judge confidence and competence. William O'Barr's courtroom research (reported in Linguistic Evidence, 1982, and Erickson, Lind, Johnson & O'Barr, 1978) found that “powerless” speech features lowered how credible and convincing a witness seemed, even when the content was identical. Precise uncertainty works because it signals calibration, not doubt.
BEFORE“I just think maybe we could sort of look at pushing the launch a bit? Like, I'm not sure, but it kind of feels like QA might need more time, if that makes sense?”
AFTER“I recommend we push the launch by one week. QA has found four blocking bugs and needs five more days. I'm confident on the bugs; the five days is my best estimate, and I'll confirm it Wednesday.”
- Start with the verb of commitment: “I recommend”, “We should”, “The answer is”.
- Delete “just” and “I think” from any sentence that's still true without them. That's almost all of them.
- Put real uncertainty in one place, with a number or a condition: “70% likely”, “if the vendor delivers”.
- End statements on a falling note. Down means done.
- Replace “does that make sense?” with silence, or “What questions do you have?”
Try it today: Before you send your next message or email, delete every “just”, “I think” and “sorry to bother you”. Then say your next recommendation in a meeting starting with “I recommend”.
DAY 06 · PRESENCEOwn the frame
On camera, the lens is their eyes. Talk to it.
Video flattens presence: you lose height, distance and most of your body, so eye line, framing, face and hands carry far more of the signal than they do in a room. Savitsky and Gilovich (2003) found speakers overestimate how visible their nerves are, and that simply telling them so improved how their speeches were rated. The Mehrabian figures are widely misquoted; see his own book, Silent Messages (1971).
BEFORE“[eyes on the slide, then down at notes, face neutral, hands off-screen] Um, so, hi everyone, I'm going to walk through the roadmap, and, yeah, let's get into it.”
AFTER“[looks into the lens, small smile, open hand in frame] Hi everyone. [pause] In the next five minutes you'll know exactly what we're shipping this quarter, and the one decision I need from you.”
- Set up first: camera at eye level, light in front, eyes about a third from the top of the frame.
- Drag the other person's video window to just below your camera.
- Look into the lens for your opening line, your key point and your close.
- Bring your hands into frame for gestures, then let them rest still.
- Start and end with a real expression, not your concentrating face.
Try it today: Before your next video call, move the other person's window right under your camera and raise your laptop to eye level. Say your opening line into the lens.
DAY 07 · DELIVERYPlay the full instrument
Train one dial until it runs without you, then add the next.
Ericsson and Pool's Peak (2016) describes deliberate practice as focused, feedback-driven work on specific sub-skills at the edge of your ability, which is the opposite of repeating whole performances on autopilot. Short, scored reps with one correction at a time are designed around that idea.
BEFORE“So, um, I think basically the main thing I've, like, been working on is the, uh, the new dashboard, which is kind of going OK? We're sort of on track, I guess.”
AFTER“I'm building the new customer dashboard. [pause] We're on track for the 15th. [pause] The one risk: the data team owes us an export by Friday. If it slips, I'll tell you Monday.”
- Before you start, pick your one focus dial for this rep.
- Open slowly and filler-free. The first five words set the pace.
- Pause at every full stop. Pauses fix fillers and pace at the same time.
- Hit one operative word per sentence.
- Close with a falling statement and silence. Then listen back for which dial broke.
Try it today: Re-record the baseline you made on day one and listen to both back to back. Then use your weakest dial as your one focus in tomorrow's meetings.
DAY 08 · CLARITY & STRUCTUREAnswer first
If you were cut off after one sentence, they should still have the answer.
Listeners hold information in working memory until they know what it's for. Giving the conclusion first gives every later sentence a place to go, which is the core argument of Minto's Pyramid Principle. It also hands the listener control: they can ask for the detail they need instead of sitting through all of it.
BEFORE“So, we started looking at the vendor options back in March, and there were three on the shortlist, and the first one had good pricing but the support was weak, and the second one…”
AFTER“We should go with Vendor B. Two reasons: their support is the only one with a four-hour response time, and they're within budget. Happy to walk through why A and C fell short.”
- Before you speak, find the one-sentence answer. Literally say it to yourself first.
- Match the shape of the question: yes/no, a number, a date, a choice.
- Follow with “because” and your strongest one or two reasons.
- Offer detail rather than force it: “Happy to go deeper on any of that.”
- Stop. The silence invites the follow-up question they actually care about.
Try it today: In your next reply to a question, from a manager, a client or in a chat thread, make the first sentence the answer. Then count how many follow-up questions you get compared to usual.
DAY 09 · CLARITY & STRUCTUREPREP: the four-beat answer
Point, reason, example, point, and the second point should be stronger than the first.
PREP front-loads the answer (as on day 8), limits you to one reason so the listener isn't juggling, and anchors the claim in a concrete case, which is far easier to remember than an abstract argument. It's a widely taught speaking scaffold rather than a research finding; its value is that it's quick enough to apply live.
BEFORE“I mean, I think code reviews are good, but they can be slow, and some people are harsh, and also it depends on the team, but generally, yeah, I think they're worth it, mostly.”
AFTER“Every change should get a code review. The reason: a second pair of eyes catches what tests miss. Last month a review caught a billing bug that would have double-charged 400 customers. So reviews stay, and we'll make them faster with a 24-hour rule.”
- Point: say your answer in one sentence.
- Reason: give your single strongest “because”. Just one.
- Example: one concrete case, name or number that proves it.
- Point: restate it, upgraded with what should happen next.
- Then stop. No “so yeah”.
Try it today: The next time someone asks “what do you think?” in a meeting, take one breath and answer in PREP. Make sure the example is a real, named case.
DAY 10 · CLARITY & STRUCTUREThe rule of three
Group everything into three or fewer, and tell them the number first.
Spoken lists have to survive in working memory, which Cowan (Behavioral and Brain Sciences, 2001) estimated at roughly four chunks. Announcing the count lets listeners pre-allocate those slots and notice when you're done. Parallel phrasing makes each item easier to encode and recall. The specific power of “three” is a rhetorical tradition and a heuristic, not a lab result.
BEFORE“We should move to the new office because it's cheaper, and the commute's better for most people, and there's parking, also more meeting rooms, and the kitchen's nicer, and it's near the station, and the lease is more flexible.”
AFTER“Three reasons to move. It's cheaper: we save about a fifth on rent. It's easier to get to: most of us cut our commute. And it fits how we work: twice the meeting rooms.”
- Dump all your points, then group them into three buckets. Name each bucket.
- Announce the count: “Three things.”
- Phrase the three in parallel: same shape, similar length.
- Order them: strongest last, unless you might be interrupted.
- Recap in one breath at the end: “Cheaper, easier, better fit.”
Try it today: Take the longest list in your next email or update and regroup it into three headed buckets. In your next meeting, start one contribution with “Three things.”
DAY 11 · CLARITY & STRUCTURESignpost: give them the map
If the structure isn't spoken, it doesn't exist.
Listeners build a mental outline as they go; previews tell them how many slots to build, and transitions tell them when to move to the next one. Because spoken language is linear and can't be re-read, redundancy that would feel padded on a page is what makes speech easy to follow.
BEFORE“The onboarding numbers are down and we think it's the new signup form, and support's been busy, and we could roll back, or we could fix the form, and engineering thinks the fix is about a week.”
AFTER“Two parts: what happened, and what we do. What happened: signups dropped after the new form went live. [pause] What we do: we roll back today, and fix the form over the next week. So: roll back now, fix properly, relaunch next Friday.”
- Preview the shape: “Two things”, “Three steps”, “The short answer, then the detail.”
- Mark each transition out loud: “That's the first. Now, the second.”
- Use position words: first, second, finally, the last thing.
- Pause and lift your pitch at the start of each new section.
- Close with a one-breath summary.
Try it today: In your next meeting where you speak for more than 30 seconds, open with a preview (“Two things…”) and say “That's the first” out loud when you finish it.
DAY 12 · CONCISIONSay it in half
Cut the run-up, cut the backstory, end once.
Every extra word competes for the listener's limited attention, so padding actively hides your point. Re-saying the same content in progressively shorter time limits forces prioritisation: you discover which sentence is the message and which are scaffolding. Pascal's line is from Lettres provinciales, letter XVI (1657).
BEFORE“So, yeah, great question. I think, basically, the way I'd describe what we do is, we're a company that, um, helps other companies with their, kind of, payroll, but also more than that, like HR stuff too, and, yeah, so that's basically it, we do payroll and HR, basically.”
AFTER“We run payroll and HR for small companies, so founders don't have to.”
- Start with the answer, not with “So, great question”.
- Ask: does the listener need this context to act? If not, cut it.
- One example, not three.
- Decide your last sentence before you start. Say it, then stop.
- Practise the 60–30–15 ladder on anything you say often.
Try it today: Take the question you get asked most at work (“What do you do?”, “How's the project?”) and prepare a 15-second answer. Use it today, then stop talking.
DAY 13 · CLARITY & STRUCTUREExplain it with an analogy
It's like X, because Y. The difference is Z.
Analogies let a listener reuse a mental model they already have instead of building one from scratch while you talk. The tapping study (Elizabeth Newton's Stanford research, as told in Made to Stick) shows why experts underestimate how much context listeners are missing. Naming the limit of an analogy prevents the misunderstandings analogies otherwise cause.
BEFORE“So an API is basically an interface that lets two software systems communicate by exposing endpoints, and you send a request with parameters and get a response, usually JSON, according to a defined contract.”
AFTER“An API is like a restaurant menu. The kitchen can make lots of things, but you can only order what's on the menu, in the way it's written. The difference: an API's “waiter” is instant and never gets your order wrong.”
- Ask: what does this do, in one plain sentence?
- Find something in the listener's everyday life that does the same job.
- Say: “It's like X, because Y.”
- Add the limit: “The difference is Z.”
- Check with one concrete use: “So when you book a flight online, that's an API at work.”
Try it today: Next time someone outside your team asks what you're working on, answer with “It's like…” and add one sentence on where the comparison breaks.
DAY 14 · CONCISIONThe 60-second brief
A headline has a verb and a point of view; a label has neither.
This combines Minto's answer-first pyramid with Duarte's insistence that a talk's core be a complete, arguable sentence. A headline with a point of view gives listeners something to agree or disagree with, which is what makes them pay attention to the evidence. The 60-second constraint forces the prioritisation from day 12.
BEFORE“OK, so, the Q3 update. Revenue was up, we did 12%, we signed a few new clients, Acme was the big one, churn was about flat, and the team's grown, we hired two people…”
AFTER“Q3 grew 12%, but nearly all of it came from Acme, which makes Acme our biggest risk. Three things: Acme is 40% of revenue. Their contract renews in January. And we have no second deal that size in the pipeline. So: I want two people on Acme renewal and a plan for one more large client by December.”
- Write the headline: a full sentence, with a verb and a point of view.
- Pick up to three supports. One sentence and one specific each.
- Signpost: “Three things.” “First…” “Last…”
- Close with the headline upgraded into an action.
- Stop. Hold the silence for questions.
Try it today: Before your next meeting, write a one-sentence headline (with a verb and a point of view) for what you'll say. Open with it.
DAY 15 · STORYThe one-moment story
Don't summarise a period. Zoom into a moment.
Stephens, Silbert & Hasson (PNAS, 2010) recorded a speaker telling a real-life story and found listeners' brain activity coupled with the speaker's, with stronger coupling predicting better comprehension. The story spine (Kenn Adams, How to Improvise a Full-Length Play, 2007) supplies the beats; zooming into a specific moment supplies the sensory detail that makes a scene easy to imagine.
BEFORE“In my first job I was really bad at saying no, and I took on too much, and eventually I burned out a bit, but then I learned to set boundaries, and now I'm much better at prioritising.”
AFTER“It's 11pm on a Thursday, I'm still at my desk, and my manager walks past and says, “You know nobody asked you to do half of this?” [pause] I went home and made a list of what I'd said yes to. Twenty-three things. The next morning I gave back eleven. I've kept that list ever since.”
- Pick one moment: a specific day, place and decision.
- Open in the moment, not before it: “It's 11pm on a Thursday…”
- Add one sensory detail and, if you can, one line of dialogue.
- Hit the turn: the “but one day” that changes things.
- Close on what changed, and what's true ever since.
Try it today: When someone asks “how was your weekend?” or “how did that go?”, answer with one moment instead of a summary: a time, a place, a detail.
DAY 16 · STORYSTAR without the snooze
Thin Situation, thick Action, a Result with a number, and a lesson.
Behavioural interviewing rests on the idea that specific past behaviour predicts future behaviour, so interviewers score the Action and the Result, not the context. A short setup leaves time for evidence; first-person actions make your individual contribution assessable; a measurable result makes the claim checkable. The 20/60/20 split is a coaching heuristic.
BEFORE“So at my last company we had this big project, and there were a lot of stakeholders, and the timeline was tight, and the team was new, and there were budget issues too, and we worked really hard, and in the end it went well and the client was happy.”
AFTER“Our biggest client was threatening to leave over slow support. I was asked to fix it in a month. I mapped every ticket from the last quarter, found 60% were the same three issues, and wrote fixes for all three with engineering. Response time fell from two days to four hours, and they renewed. Lesson: start with the data, not the meeting.”
- Situation and Task: two sentences, maximum.
- Action: three to four specific things YOU did, in the first person.
- Result: a number, a date or a concrete outcome.
- Lesson: one sentence on what you learned or would do differently.
- Re-check the question: does your story actually show the quality they asked about?
Try it today: Write down your three best work stories in STAR form, each with a number in the result and a one-line lesson. That's your interview (and performance review) toolkit.
DAY 17 · STORYConcrete beats abstract
For every abstract claim, climb down the ladder to one thing they can see.
Small, Loewenstein & Slovic (Organizational Behavior and Human Decision Processes, 2007) found that an identifiable individual drew larger donations than statistics, and that pairing the two reduced giving compared with the individual alone. Concrete language is easier to imagine and remember, a central argument of the Heaths' Made to Stick and of Hayakawa's ladder of abstraction.
BEFORE“Our onboarding has a lot of friction, and customers are generally frustrated, which is impacting activation and overall satisfaction across segments.”
AFTER“Last Tuesday a customer in Leeds spent 40 minutes looking for the invite button. Then she emailed us two words: “I give up.” She's not alone: about a third of new teams never invite a second person.”
- Spot your abstract nouns: frustration, impact, value, efficiency, culture.
- Ask: what did that look like, on one day, for one person?
- Add a name or a place, a number, and if possible a quote.
- Lead with the specific, then (if needed) one number to show the scale.
- Resist stacking statistics. One person, one number.
Try it today: In your next update or proposal, replace one abstract claim with one real example: a specific customer, colleague or moment, with a quote if you have one.
DAY 18 · PERSUASIONProblem, solution, ask
Make them feel the problem and see the future before you ask for anything.
Monroe's motivated sequence (Principles and Types of Speech, 1935) orders persuasion to follow the listener's psychology: attention, then a felt need, then a solution to that need, then a picture of the benefit, then a concrete action. Duarte's Resonate (2010) describes the same tension between what is and what could be. Skipping the need step leaves the solution answering a question nobody asked.
BEFORE“I'd like to propose we introduce a weekly customer call rotation. Everyone would take one call a week. Thoughts?”
AFTER“Last quarter we built two features that almost nobody uses: four months of work. [pause] I propose every one of us spends one hour a week on a customer call. Picture next quarter: every feature we build, someone on this team has heard a customer ask for it. I'd like a yes today to start a four-week trial on Monday.”
- Problem: make the cost of today concrete: time, money, people, a real example.
- Solution: one sentence. What you propose.
- Picture: describe the world three months after it works.
- Ask: the exact decision, who makes it, by when.
- Stop after the ask.
Try it today: For the next thing you want approved, write the four beats (problem, solution, picture, ask) on a sticky note before the conversation. Say all four.
DAY 19 · PERSUASIONHandle the objection
Acknowledge before you answer. An objection heard is half-handled.
Labelling and accusation audits, as described by Chris Voss and Tahl Raz in Never Split the Difference (2016), reduce defensiveness by showing the other side they've been understood, which makes them more open to new information. Immediate rebuttal tends to provoke the opposite. The acknowledge–clarify–answer–check sequence is a widely taught sales and negotiation pattern.
BEFORE“No, no, it's actually not expensive at all, because if you look at the ROI it pays back really quickly, and our competitors are way more expensive, so it's actually really good value.”
AFTER“It sounds like the price is hard to justify right now. [pause] Is it the total, or the timing? [listens] Got it. Then here's the useful number: teams your size typically recover the cost in about four months through saved hours. Would a monthly plan for the first quarter solve the timing?”
- Pause. Don't answer in the first second.
- Label: “It sounds like…” / “It seems you're concerned about…”
- Clarify, if you can: “Is it X or Y?”
- Answer the real concern with one piece of evidence.
- Check: “Does that address it?” Replace “but” with “and”.
Try it today: Next time someone pushes back on you today, start your reply with “It sounds like…” and finish their concern before giving your answer.
DAY 20 · PERSUASIONMake the clear ask
Who, what, by when, because. Then stop talking.
Langer, Blank & Chanowitz (Journal of Personality and Social Psychology, 1978) showed that for a small favour, giving any reason, even an empty one, raised compliance, while for a larger favour only a genuine reason did. A specific ask with a deadline turns agreement into an action, and silence afterwards leaves the decision with the listener instead of letting you withdraw it.
BEFORE“So, yeah, that's kind of the idea. I don't know, maybe have a think about it, and if it makes sense, we could maybe chat at some point? No pressure though.”
AFTER“So here's my ask: can you approve a two-week trial starting Monday? Because if it works, we get back five hours a week for the whole team. [silence]”
- Decide the exact decision you want before the conversation starts.
- Phrase it as who, what, by when.
- Add a real “because”.
- If it's big, ask for the smallest real next step.
- Say it once, then stay silent until they answer.
Try it today: End your next email or meeting with one sentence that has who, what and by when in it. Then stop typing or stop talking.
DAY 21 · PERSUASIONThe 90-second pitch
Make the listener the hero, and give them one tool and one next step.
Duarte's Resonate (2010) argues that audiences engage when they see themselves as the protagonist and the speaker as the mentor. Combining a concrete hook, a felt problem, a single proof and a specific ask follows Monroe's motivated sequence in compressed form. The aim of a short pitch is the next step, not the full sale.
BEFORE“Hi, I'm Sam, I'm the founder of Brightdesk. We started in 2021, we've got a great team of twelve, we built an AI scheduling tool, it has lots of features, we integrate with everything, and we'd love to work with you.”
AFTER“Your team spent about six hours last week scheduling interviews. [pause] Brightdesk does it in one click: the candidate picks a slot, everyone's calendar updates. A team your size got those six hours back in the first week. Can we set up a 20-minute trial with your recruiter on Thursday?”
- Open on their world: a concrete cost or moment.
- One-sentence solution.
- One proof: a number or a named example.
- Name the obvious objection if there is one.
- Ask for the next step: who, what, when.
Try it today: Write the 45-second version of a pitch you actually need this month: for a job, a project, a client or a budget. Say it out loud three times before you use it.
DAY 22 · IMPROMPTUImpromptu with a framework
Pick the shape first; the words will fill it.
Speaking impromptu splits your attention between content and organisation; a pre-learned structure takes the organising off your plate, so working memory goes to content. Abrahams' Think Faster, Talk Smarter (2023) makes the case for reducing the pressure to be perfect and leaning on simple structures such as Problem–Solution–Benefit. Paraphrasing the question buys planning time without dead air.
BEFORE“Oh, um, how's the industry changing? Wow, OK, that's a big one. Um, I guess there's a lot going on, like AI, and, um, remote work, and also, hmm, regulation, I suppose, it's all kind of changing really.”
AFTER“How's the industry changing? [breath] Five years ago, most of our work was done in person. Today, two-thirds of it is remote. Next: my bet is AI writes the first draft of most reports, so the valuable skill becomes judgement, not production.”
- Paraphrase the question out loud. It buys you two seconds.
- Breathe and pick a shape: PREP, Past–Present–Future, or Problem–Solution–Benefit.
- Say your first point plainly. Good, not brilliant.
- Fill the remaining beats in order.
- Close with one sentence and stop.
Try it today: The next time you're asked an unexpected question today, paraphrase it first, then answer in Past–Present–Future or PREP.
DAY 23 · IMPROMPTUWhat? So what? Now what?
A fact isn't an update until you've said why it matters and what happens next.
The structure answers the three questions any listener silently asks of new information: what happened, why should I care, and what do I do. Doing the interpretation for them saves their effort and shows judgement. Abrahams presents What–So What–Now What as a go-to structure in Think Faster, Talk Smarter (2023).
BEFORE“Just a heads up, signups dropped 12% last week.”
AFTER“Signups dropped 12% last week. [pause] So what: if it holds, we miss the quarter's target by about a month. Now what: we've traced it to the new signup form, we roll it back today, and I'll report the numbers Friday.”
- What: one sentence, the fact.
- So what: why it matters to THIS listener.
- Now what: the action, the owner, the date.
- Label the beats out loud if it helps: “So what that means is…”
- Keep the What short. Most of your time goes to So what and Now what.
Try it today: In your next standup or status message, give every item a So What and a Now What, not just the What.
DAY 24 · UNDER PRESSUREAnswer, bridge, communicate
Answer it first, then bridge to what you came to say.
Interviews and Q&A are steered by the questioner; without key messages and a bridge, the speaker only ever responds to an agenda someone else set. Answering first keeps it honest and keeps trust; the bridge then connects that answer to a prepared message. This is standard media-training practice rather than a research finding.
BEFORE“Isn't your product just a cheaper copy of the big players? [answer:] Well, what's really important is that we have a great team and we've grown 300% this year, and our customers love us.”
AFTER“Is it a copy? No. It's built for teams under 20, which the big players don't serve. [bridge] And that's the bigger point: small teams need a tool they can set up in an afternoon. That's why 300 of them switched to us this year.”
- Before the conversation, write down two or three key messages.
- Answer the question in one or two sentences. Honestly.
- Bridge with a short phrase: “What matters most is…”
- Deliver one key message, with one proof point.
- Stop. Don't drift back to the original question.
Try it today: Before your next important meeting, write down the two things you want everyone to leave with. Bridge to one of them at least once.
DAY 25 · UNDER PRESSUREAnswer the actual question
Answer the question they asked, in the shape they asked it, then the question behind it.
Rogers & Norton (Journal of Experimental Psychology: Applied, 2011) found that dodges to similar questions often go unnoticed, but detected dodges cost the speaker trust. Experienced interviewers and executives listen specifically for whether you answered, so matching the question's form is both a relevance signal and a credibility one.
BEFORE“Q: “What's the earliest you could ship?” A: “Well, we've had a lot of challenges with the vendor, and the team's working really hard, and quality is our top priority, so we want to make sure we get it right.””
AFTER“Q: “What's the earliest you could ship?” A: “The 14th, if we cut the export feature. With it, the 28th. I'd ship on the 14th and add export in the next release.””
- Listen to the last words of the question. Identify its shape: yes/no, number, choice, why, how.
- Make your first words that shape: “Yes.” “The 14th.” “Option B.”
- If it's ambiguous, clarify or state your interpretation.
- Add the one reason or condition that matters.
- Then, if useful, answer the question behind the question.
Try it today: In your next meeting, before you answer any question, silently name its shape (yes/no, number, choice). Make your first word match.
DAY 26 · UNDER PRESSUREThe hostile question
Don't repeat the attack. Reframe it neutrally, slow down, answer the room.
Lakoff's Don't Think of an Elephant! (2004) argues that negating a frame activates it, which is why denials that repeat an accusation tend to backfire. Pausing and lowering your pace counteracts the fight-or-flight speed-up that makes defensive answers sound guilty. Answering for the wider audience is a standard media and investor-relations principle.
BEFORE“Q: “Why did you hide the outage from customers?” A: “We absolutely did not hide the outage! There was no hiding, we just, I mean, we weren't trying to cover anything up…””
AFTER“[pause] “The real question is how fast we told customers. We confirmed the cause on Tuesday at 10, and every affected customer had an email by 2. I understand it felt slow from the outside, so we're adding a live status page.””
- Pause for a full beat. Let the heat pass.
- Don't repeat the loaded words. Reframe: “The question is…”
- Acknowledge the feeling if it's real: “I understand why that's frustrating.”
- Answer with facts: times, numbers, actions.
- Speak slightly slower and lower than normal. End on what's being done.
Try it today: Think of the hardest question you could be asked this week. Write a neutral reframe (“The real question is…”) and a fact-based answer. You'll be calmer in the room for having done it.
DAY 27 · UNDER PRESSUREThe hard conversation
Describe what a camera would see, say what it caused, then ask, don't assume.
SBI (Center for Creative Leadership) keeps feedback specific and observable, which reduces defensiveness because there's no character judgement to dispute. Stone, Patton & Heen's Difficult Conversations (1999) shows why separating impact (which you know) from intent (which you don't) keeps the conversation from turning into an argument about motives.
BEFORE“Hey, so, you're doing great overall, really, but, um, sometimes in meetings you can come across as a bit dismissive? Not a big deal, just something to think about. Anyway, great work on the report!”
AFTER“I want to talk about Tuesday's client call. You interrupted Priya three times while she was presenting, and the client started directing questions to you instead of her. I doubt that was your intent. How did it look from your side?”
- Get to the point within the first two sentences.
- Situation: “In Tuesday's…”
- Behaviour: what a camera would record. No adjectives about character.
- Impact: the concrete effect on people or work.
- Ask: “How did it look from your side?” Then listen.
Try it today: Is there feedback you've been avoiding giving? Write it as one SBI sentence today. If it's positive feedback, deliver it today; if it's hard, book the conversation.
DAY 28 · CONCISIONThe executive update
Lead with the decision you need; everything else supports it.
Minto's Situation–Complication–Question–Answer frame (The Pyramid Principle) moves the reader from shared context to the specific recommendation as fast as possible. Senior listeners have little time and many decisions, so an update framed as a decision with a recommendation is easier to act on than a list of activities.
BEFORE“So this week the team finished the API work, we had a few vendor calls, design is mostly done, QA started on Wednesday, we've had some issues with the vendor's delivery, and we're looking at options for the timeline.”
AFTER“We're two weeks late, and I need a decision today. The vendor missed their delivery, which blocks QA. Two options: wait for them and launch on the 28th, or launch on the 14th without the export feature. I recommend the 14th; only 5% of users use export.”
- Headline: status plus the decision you need, in one sentence.
- Context: one or two sentences. What changed.
- Options: two or three, with the trade-off.
- Recommendation: which one and why.
- Ask: “Can I get your go-ahead today?”
Try it today: Rewrite your next status update so the first line is the decision you need (or “No decision needed”). Put bad news in the first three lines, with your plan.
DAY 29 · PRESENCEThe two-minute talk
One throughline, one story, a memorised first and last line, and silence at the end.
Anderson's TED Talks: The Official TED Guide to Public Speaking (2016) treats the throughline as the backbone that makes a talk coherent. Memorising only the opening and close while rehearsing the middle as beats is a common coaching heuristic: it protects the highest-pressure moments without the brittleness of a full script.
BEFORE“Hi everyone, thanks for having me. Today I'd like to talk a little bit about feedback, and why I think it's important, and some of the things I've learned about it over the years.”
AFTER“Three years ago, my manager handed me a review with one line on it: “Talks too much in meetings.” [pause] It was the most useful sentence anyone has ever written about me. Today I want to convince you that the best feedback is the kind that's short enough to hurt.”
- Write your throughline in one sentence. Every beat must serve it.
- Open with a moment, a question or a surprising fact.
- Plan two or three beats; make one of them a concrete story.
- Close by returning to your opening, plus one action or thought.
- Memorise the first and last lines; rehearse the middle as beats.
Try it today: Use this talk. Offer it as a five-minute slot at your next team meeting, or record it as a short video for your team or your network.
DAY 30 · UNDER PRESSUREThe high-stakes moment
Don't try to calm down. Call it excitement, and walk in pre-loaded.
Brooks (Journal of Experimental Psychology: General, 2014) found that reappraising pre-performance anxiety as excitement, even by saying “I am excited” aloud, improved performance in tasks including public speaking compared with trying to calm down. Pre-rehearsed messages and stories reduce the working-memory load that pressure takes away.
BEFORE“[racing] Oh, great question, um, so, I guess my biggest failure, hmm, there are a few, I mean, I think, like, probably the time with the, the client project, which, it was complicated, so…”
AFTER“[pause, steady] My biggest failure was a client launch in 2022. I promised a date before checking with engineering, and we missed it by a month. I now never commit to a date until the team has estimated it, and in two years we haven't missed one.”
- Beforehand, say “I'm excited” out loud. Not “calm”.
- Pre-load two or three key messages, three STAR stories and your scariest question.
- In the moment: breathe, paraphrase, pick a shape.
- Answer first. Bridge if you need to. Stop.
- If you blank, pause, then restate your key message.
Try it today: Pick a real high-stakes moment in the next month (an interview, a pitch, a review). Pre-load your key messages, three stories and your scariest question this week, and say “I'm excited” before you walk in.