• General Overview
  • The First Minute Defined
    • Work-topic start: the first minute begins when talk turns professional, not at the greeting
    • Audience gap: listeners lack your context and guess whenever you leave it unstated
    • Ambiguity cost: unclear communication burns about 17 hours a week in a 100-person business
    • Career stakes: poor communication is a top reason capable people miss promotions
    • Recoverable: strong daily impressions can overturn a bad first impression — at a ratio of eight to one
  • The Three-Statement Frame
    • Framing: the opening fifteen seconds decide whether a work conversation lands
    • Context: name the project, customer, system, or task; never assume shared context
    • Intent: tell the listener's brain whether to answer, act, decide, or just listen
    • Key message: the single most important line, up front — not a summary of details
    • Formula: topic plus intent plus point, in three sentences and under twenty words
    • So-what test: asking why the listener should care exposes the buried headline
  • The GPS Structured Summary
    • Goal: state separately what you want to achieve
    • Problem: name the obstacle; never merge it into the goal
    • Solution: say what you or they will do next, looking forward rather than back
    • Why it works: gives a frame of reference before detail, so listeners can connect the points
    • Unknown solution: state goal and problem, then offer one or two options and ask for help
    • Universal fit: goal, problem, solution summarizes any topic, role, or industry
  • Time Check and Validation Checkpoint
    • Time check: ask for the actual time needed, not "a minute" when it is five
    • Validation checkpoint: confirm the listener can engage, and give them a clear exit
    • Ability and availability: check knowledge, access, or authority — and whether now works
    • Placement choice: validate after framing for a quick exit, or after the summary for full context
    • Wrong person: frame around finding the right contact, not solving the problem
    • Risk: skipping either step wastes the listener's time and damages your credibility
  • One Topic, One Framing
    • Multi-topic risk: mixing contexts, intents, or problems in one framing confuses listeners
    • Separate framing rule: a different context or intent means a separate conversation
    • Summary framing: introduce every topic up front, then frame each one individually
    • Call-back: refer to the topic list between discussions so nothing is left undiscussed
    • Root-cause shortcut: when several problems share one cause, summarize that cause as the problem
  • Beyond Conversation
    • Email: the subject line carries context and intent; the body uses labeled Goal, Problem, Solution
    • Not every email: simple replies need only framing, but forwarding always requires a summary
    • Meetings: blank invitations are rude — state purpose and expected output up front
    • Recap the invitation: opening the meeting with the same framing aligns everyone and calms nerves
    • Status and escalations: lead with the summary, stay factual, and keep the focus on solutions
    • Interviews and messaging: the same framing shortens answers and instant messages alike
  • Making It Natural
    • Write it down: drafting the framing and summary before speaking beats memorizing
    • Two-minute payoff: brief preparation returns shorter, clearer, faster conversations
    • Practice over polish: repeated use makes the structure automatic in requests and updates
    • High-stakes exception: keep writing summaries for complex or high-stakes topics
• Deep Dive
  • Introduction
    • Why first minute matters
      • Work communication: over 80% of daily interactions with teams, peers, managers
      • Audience gap: listeners lack your context; they guess when unclear
      • Cost of ambiguity: 17 hours/week clarifying in a 100-person business
      • First-minute goal: set context, intent, and message for success
    • Core principles
      • Prepare the audience: frame the message before delivering it
      • Get to the point: respect busy listeners; brevity prevents rambling
      • Focus on solutions: effective conversations move from problems to actions
      • One topic at a time: avoid mixing multiple issues in one conversation
    • Framing in 15 seconds
      • Context: orient listeners to the topic and situation
      • Intent: state clearly what you want to achieve
      • Key message: headline that captures the whole point
      • Framing: foundation for a successful conversation
    • Structured summary
      • Goal: define the outcome you are aiming for
      • Problem: name the obstacle between goal and reality
      • Solution: lead the conversation toward desired action
      • Universal application: works for any topic, role, or industry
  • Chapter 1 - What is the first minute
    • Defining the first minute
      • Work-topic start: the first minute begins when you switch from personal to professional topics.
      • Not the greeting: excludes salutations and time spent on personal engagement.
      • Everyday work talk: focuses on normal business topics, not interviews, dates, or relationship-building.
    • Why the first minute matters
      • Professional respect: being liked is not enough; organized delivery earns professional credibility.
      • Career impact: poor communication is a top reason people miss promotions, especially for leaders.
      • Daily weight: over half of work time is spent communicating, leaving lasting impressions.
    • Repairing a bad impression
      • Reversible: consistent strong performance can overturn poor first impressions.
      • Eight-to-one ratio: it takes eight good impressions to cancel one bad one.
      • Fast turnaround: daily conversations can rebuild reputation in under two weeks; emails and meetings speed this up.
      • Future chances: new teams and companies offer fresh opportunities for first impressions.
    • How the book helps
      • Build the skill: coming chapters teach how to create a great first minute for any work topic.
      • Make it natural: repeated practice makes clear communication automatic in requests, updates, and daily exchanges.
  • Chapter 2 - Framing
    • Framing Conversations in Fifteen Seconds (Chapter 2 - Framing · I)
      • Why Framing Matters
        • Framing: the first fifteen seconds decide whether a work conversation lands.
        • School gap: years of schooling never teach how to start work conversations.
        • Steve's ten-minute reveal: an LT-10 testing deadline issue surfaced only after rambling.
        • Common failures: missing context, unclear purpose, slow point, mixed topics.
      • The Three-Statement Frame
        • Context: name the topic you want to talk about.
        • Intent: state what you want the audience to do with the information.
        • Key message: deliver the headline — the most important part up front.
        • Order matters: frame in three sentences or less, delivered in under fifteen seconds.
        • Audience benefit: listeners stop guessing and process the message immediately.
      • Context Orients the Listener
        • Context: a simple statement naming a project, customer, system, or task.
        • Always needed: never assume the other person shares your mental context.
        • Even close collaborators: they may be thinking about anything else.
        • Cost of omission: the audience gets distracted trying to decode the topic.
        • Quick examples: "I'm working on project ABC…", "We're closing the sale on Jefferson…"
      • Intent Directs the Brain
        • Intent: tells the brain whether to answer, act, decide, or just listen.
        • Delayed intent: the audience forms assumptions and may need to reprocess.
        • Working memory: only about twenty seconds; unclear intent causes information loss.
        • Emma's rollercoaster: Daniel's mixed good-and-bad news without purpose caused false alarms.
        • Practical tip: if intent isn't clear in a minute, ask the speaker to clarify it.
    • Intent, Key Messages, and Framing (Chapter 2 - Framing · II)
      • Showing Intent in One Line
        • Five intent categories: needing help, requesting action, wanting a decision, heads-up, providing requested information.
        • State intent in one line: audience immediately knows what to do with the message and can decide whether to engage.
        • Wanting to chat: add a sixth category for stories, venting, gossip; use “Would you like to hear?” to set expectations.
        • Daniel and Emma: missing intent made Emma worry; “It’s not urgent” would have let her defer safely.
      • Combining Context and Intent
        • Context plus intent: both together make the topic and purpose clear before details.
        • Daniel’s opening: “Can I talk about TechCorp? Not urgent, but funny” lets Emma choose to listen or defer.
        • Concise framing: examples run 9–15 words; enough to prepare the audience’s frame of mind.
        • Universal habit: starting every interaction this way would make expectations clear every time.
      • Delivering the Key Message
        • Key message defined: the single most important line your audience needs to know; not a summary of all details.
        • Mechanic lesson: give bottom line first—cost and time—then offer details; audience focuses better afterward.
        • Diagnose and prepare: “Why are you telling me this?” and “So what?” reveal missing key messages and shape framing.
        • BLUF: Bottom Line Up Front puts conclusion and recommendation at the start for rapid decisions.
      • Creating Good Key Messages
        • Find it with “So what?”: answer identifies the most impactful part; consequences often outweigh the event itself.
        • Example: new client: the $50M closing was buried last; lead with “We are closing Davison Group today.”
        • Example: system down: 57-word story condenses to “Sales system is down, one week to fix” and becomes clear.
        • Conversation rollercoaster: without a key message, audience rides every twist until the point finally arrives.
    • Framing Single and Multiple Topics (Chapter 2 - Framing · III)
      • Assembling the Framing Statement
        • Framing statement: combine context, intent, and key message into one or two lines.
        • Formula: name the topic + describe intent + get to the point.
        • Concise by design: examples stay under twenty words and under fifteen seconds.
        • So-what test: every key message must answer why the listener should care.
      • Framing Pays Back in Minutes
        • Steve's LT-10 example: context "testing the LT-10," intent "we have a problem," key message "finishing a month late."
        • Framing saves time: shorter discussion, less confusion, audience knows expected action.
        • Practice builds confidence: start even if awkward; audience will appreciate clarity.
        • Two-minute investment: preparation cost is repaid immediately in clearer, faster conversations.
      • Separate Topics Need Separate Framings
        • Multi-topic risk: combining topics increases confusion and derails conversations.
        • One context = one topic: separate contexts mean separate conversations and separate framings.
        • One intent = one purpose: an FYI plus a request cannot share a single framing.
        • Ambush: framed for one intent, then key message asks a different action; causes "wait, what?"
        • Key-message check: same context and intent can stay one framing; different intents need separate framings.
      • Summary Framing for Multi-Topic Conversations
        • Summary framing: introduce all topics up front, then address each separately with its own framing.
        • Timothy's example: three topics framed as "advice plus two decisions" in one context.
        • Simple context: when framing multiple topics, context is simply "I have several things to discuss."
        • Combined intent and key message: summarize each topic's intent and key message without twenty-word limit.
        • Audience choice: summary framing lets the listener pick which topic to address first.
      • Same Context, Multiple Topics
        • Andrea's case: same "new region roll-out" context, one FYI and one decision request.
        • Conversation framing: state number and type of topics at the start to keep them separate.
        • Call-back: between topics, refer back to the summary framing to orient the audience.
        • Safety net: declaring multiple topics prevents walking away with topics undiscussed.
  • Chapter 3 - Structured summaries
    • Structured Summaries via GPS (Chapter 3 - Structured summaries · I)
      • Why structured summaries matter
        • Clear summary first: gives audience a frame of reference before details arrive.
        • Diving into detail too quickly: confuses listeners who can't connect points to the main topic.
        • Tangents and rambling: frustrate and obscure the original point.
        • Dwelling on the past: meetings can spend 80% of time on problem history instead of next steps.
        • Training gap: courses say be concise but rarely show how to build a summary.
      • Work conversations center on problems
        • Work is problem-solving: companies meet goals by avoiding or preventing problems.
        • Three conversation types: find a solution, recommend a solution, or report a solved problem.
        • Focus on solving: structure messages around clarifying the problem and moving toward action.
        • Don't hide problems: hiding a work problem is never acceptable.
      • The GPS structured summary
        • GPS method: three-part summary — goal, problem, solution — fits any topic.
        • Goal: what you want to achieve; stated separately.
        • Problem: the obstacle preventing the goal; don't merge into goal.
        • Solution: what I/we/you will do to reach the goal.
        • Navigation metaphor: GPS shows destination, obstacles, and route, like the summary.
        • All three parts needed: goal and problem are commonly conflated; keep distinct.
      • When solution is unknown
        • Unknown solution: state goal, problem, then ask for help finding a solution.
        • Propose options: offering one or two ideas makes it a request for advice, not extra work.
        • High performers ask: they seek help with candidate solutions rather than dumping the problem.
        • Avoid asking others to solve: few like extra work; most enjoy giving expert insight.
      • GPS in practice
        • Sam's refund request: a GPS summary would get authorization and shipment help in under 30 seconds.
        • IT firewall example: plain-language GPS made a technical compliance issue clear to any role.
        • NASA BBQ: non-engineer Nick summarized ISS funding as goal, problem, solution in thirty seconds.
        • Avoid jargon: summaries work when they don't require technical expertise.
        • Brief by design: the summary is an introduction, not the whole conversation.
        • Frame before structure: combining framing with GPS always strengthens the message.
    • Clear Summaries for Any Topic (Chapter 3 - Structured summaries · II)
      • Why Summaries Get Overcomplicated
        • Audience assumption: we summarize as we would like, not as the listener needs
        • Detail bias: we believe others need all the facts before they can understand
        • Variable confusion: causes and dependencies crowd out the real problem
        • Problem stacking: summarizing several problems at once dilutes the message
      • The GPS Method Covers Any Topic
        • Universal structure: goal, problem, and solution summarize even the most complex work
        • Minimal start: share the least information needed to make your point, then add detail
        • Leaders expect summaries: high-level clarity comes before supporting detail
        • Root cause rule: if multiple problems share one cause, summarize that cause as the problem
      • Structuring Conversations with Multiple Problems
        • One problem at a time: each problem needs its own framing and structured summary
        • Sequential topics: move from topic to topic with fresh framing and summary in the same meeting
        • Common cause exception: the shared root cause becomes the single problem to solve
        • Example: go-live delay from late deliveries, backlog, and testing becomes one response plan
      • Solutions Are Forward-Looking
        • Solution states intent: tell the audience what happens next and how they are involved
        • Avoid history: chronological explanations force listeners to dwell on mistakes
        • Positive updates: report fixes already made, not the problem’s full backstory
        • When stuck: if you don’t know next steps, make the solution “Can you help me fix this?”
      • Making the Summary Stick
        • Write it down: notes keep the opening clear; content matters more than polished delivery
        • Prepare over memorize: one minute of preparation boosts confidence
        • Practice builds fluency: repeated use makes structured summaries second nature
        • Self-check: single goal? one problem? actionable, forward-looking solution?
  • Chapter 4 - Time check and validation checkpoint
    • The Two-Step Opening
      • Time check: Ask for enough time before launching into your message.
      • Validation checkpoint: After framing or summary, confirm the audience can engage now.
      • Miss either step: Risk damaging your reputation or wasting the listener's time.
      • Prepare in seconds: Think through intent, message, and likely duration before speaking.
    • Time Check Details
      • Ask for actual time: Don't say a minute if the conversation will take five or ten.
      • Underpromising backfires: A missed self-imposed deadline damages credibility as a worker and communicator.
      • "Do you have a minute?": People take the request at face value; conversations stretch far past the minute.
      • Get to the point quickly: Framing plus structured summary preserves time for actual discussion.
    • Validation Checkpoint
      • Validate ability and availability: The listener needs enough info to judge whether they can help.
      • Give a clear exit: Ask "Are you the right person?" / "Do you have time now?" / "Any questions?"
      • Avoid trapping: Without this step, audiences must interrupt or endure a longwinded intro.
      • Possible outcomes: Ready now, not ready, wrong person, or need clarification; all except ready are handled with grace.
    • Ability and Availability
      • Ability: Confirm the person has knowledge, access, or authority before explaining the problem.
      • Availability: Unscheduled conversations require an explicit check; assume neither time nor desire.
      • Your urgency isn't theirs: People may not share your excitement or pressure; ask, don't assume.
    • Placement Choices
      • Validate after framing: Quick exit if wrong person, but little context for judging urgency.
      • Validate after summary: Full context, but longer wait before the checkpoint.
      • Either placement works: Validating gives the other person a choice against competing demands.
    • Finding the Right Person
      • Focus on locating help: Frame around finding the right contact, not solving the issue.
      • Example framing: "Locked out of sales system" – intent: "Can you help?" – key message: "Know how to reset password?"
      • Repeat the concise framing: If one person can't help, use their suggestions to move to the next contact.
      • Keep it short: Like asking directions; skip backstory and save everyone time.
  • Chapter 5 - Applying the techniques
    • Framing email and meeting invitations (Chapter 5 - Applying the techniques · I)
      • Emails use the same conversation techniques
        • Beyond conversations: framing and structured summaries work for email, invites, escalations, presentations, interviews.
        • Email remains primary: 39% use it to ask questions, 57% for status updates.
        • Transactional focus: work email needs directness, not pleasantries.
        • Same method: clear framing plus structured summary yields shorter, clearer messages.
      • Framing and structured summary in an email
        • Subject line: carry context and intent.
        • First line: restate intent and state the key message.
        • Body: labeled Goal, Problem, Solution bullets with blank lines.
        • Call-to-action label: "Solution/Request" highlights a clear request.
      • Every email doesn't need full GPS
        • Simple replies: one-line answers, group discussion, feedback need only framing.
        • Email chains as conversation: subsequent replies flow naturally without formal structure.
        • Complex topics: first email should include a structured summary; follow-ups can skip it.
        • Break when confused: in long muddled chains, insert a structured summary to refocus.
        • Forwarding always requires summary: don't make new recipients dig; treat it as a new conversation.
      • Longer emails need visual structure
        • Dense text kills readership: no urgency, no focus, hard to scan.
        • Headings, bullets, white space: make messages easy to consume.
        • Expand under headings: add more bullets under Goal, Problem, or Solution as needed.
      • Meeting invitations are conversations too
        • Blank invites are rude: equivalent to telling someone to show up without context.
        • Clarity drives productivity: unclear purpose causes unproductive meetings; only 1 in 10 always know purpose.
        • Adapt framing: subject gets context and intent; key message becomes purpose and output.
      • Meeting invitation format
        • Meeting purpose: one line why the meeting is held.
        • Meeting output: one line stating expected outcome, decision, or list.
        • Additional info: include structured summary or key message to orient invitees.
    • Framing Invitations and Status Updates (Chapter 5 - Applying the techniques · II)
      • Meeting Invitations as Framed Messages
        • Invitation structure: use context, intent, purpose, and outcome headings to frame the invite.
        • Key message may suffice: two or three bullet points can define purpose and why invitees are needed.
        • Bold the headings: keep bolded labels in the invite to guide readers through the message.
        • Skip time check and validation: recipients can return later; their accept/decline response is validation.
        • Purpose before salutation: start with meeting purpose, not “Dear John”; mobile screens favour purpose first.
      • Agendas and Multi-Topic Meetings
        • Single purpose means no agenda: invitation with purpose and output is sufficient; formal agenda adds work.
        • Multiple topics benefit from agenda: shows order and speakers, especially when each topic has a different owner.
        • Frame each agenda item: introduce every topic as a new conversation with its own structured summary.
        • Connect topics to common theme: invitation framing should relate to the shared thread across topics.
      • Start by Recapping the Invitation
        • Recap the invite at meeting start: use the same content as the invitation as your script.
        • Don’t assume invites are read: attendees may have skimmed or forgotten details from days ago.
        • Align everyone: hearing the same goal, problem, and solution removes assumptions.
        • Invite early questions: clarify or validate the framing before discussion begins.
        • Eases nerves and focus: prepared notes calm the leader and get attendees solving problems.
      • Avoid Forwarding Blank Invitations
        • Blank forwards create confusion: recipients must ask the organizer or attend to discover the point.
        • Clear invites reduce follow-up emails: fewer people ask what the meeting is about.
        • Remote work inflates attendance: easy adds fill calendars; clear framing keeps invites relevant.
      • Use a Validation Checkpoint in the Meeting
        • Offer an opt-out after framing: say “If this isn’t something you need, please feel free to leave.”
        • Confirm the right people: checkpoint lets attendees ask clarifying questions about purpose and role.
        • Make attendance an accountable choice: participants stay because they can add or get value.
        • Name required attendees: keep key participants; everyone else gets the choice to leave.
        • Not for every team: new or inexperienced teams may need more direction before empowerment.
        • Boosts engagement: people who choose to stay are more invested in the discussion.
      • Status Updates with Solution Focus
        • Frame each update: state context, intent, and key message; follow structured summary steps.
        • Match depth to audience knowledge: familiar audiences need shorter problem statements; unfamiliar need more.
        • Focus on solutions, not problems: say whether it’s fixed, who’s doing what, and what’s next.
        • Summarize future plans briefly: give key points, then let the audience ask for details.
        • One minute may be enough: lead with the summary; detail only follows if requested.
    • Structure for Every Conversation (Chapter 5 - Applying the techniques · III)
      • Status Updates and Unplanned Questions
        • Bare-bones update: use framing, structured summary, and validation checkpoint — nothing else.
        • Unexpected questions: repeat the question, then give key message and GPS summary.
        • Avoid defensiveness: structured summary keeps answers factual and solution-focused, not emotional.
        • Don’t know the answer: apologize, admit the gap, and propose a follow-up.
      • Escalating Issues
        • Escalation clarity: framing and structured summaries get to the point faster.
        • Fact-based framing: reduces emotion and excuses, helping the receiver assess.
        • Solution focus: turns escalation into a plan, not a complaint.
        • Verbal escalations: write the summary ahead and never skip the solution.
        • Email escalations: follow the same clear, organized structure as in-person.
        • No solution yet: use structured summary to define the problem and ask for help.
      • Positive Messages and Presentations
        • Good news brevity: rambling praise wastes celebration time.
        • Same structure: give context, make intent clear, and get to the point.
        • Work presentations: open with context, intent, and key message to align the room.
        • Not for entertainment: TED-style or entertaining talks fall outside this advice.
      • Instant-Messaging Platforms
        • Conversation style: IM is back-and-forth, not one complete message.
        • Still structured: include time check, framing, structured summary, and validation checkpoint.
        • Informal ≠ unclear: apps require the same concise clarity as in-person communication.
      • Framing Interview Answers
        • First-minute stakes: interviews reward logical, clear, concise communication.
        • Framing examples: generic context, clear intent, and key message naming the challenge.
        • Structured summary: goal, problem, solution — describe any situation in under a minute.
        • Interview preparation: write out examples; adjust framing per likely question; use past tense.
        • Validation checkpoint: stop and ask if the interviewer wants more detail.
  • Conclusion
    • The Critical First Minute
      • First minute: defines engagement, understanding, and next steps
      • Unclear start: risks confusion, wasted time, unmet expectations
      • Preparation: ready the audience to receive your message before diving in
    • Framing and Expectations
      • Time expectation: tell listeners if this is a 30-second or a 30-minute discussion
      • Framing: focus attention with context and topic
      • Intent: state what you want the audience to do with the information
      • Key message: reach the point quickly
    • Structured Summary
      • Goal: open by stating what you aim to achieve
      • Problem: name the specific barrier to that goal
      • Solution: offer a fix or request help finding one
      • Future focus: keep the summary moving forward, not dwelling on the past
    • Engaging the Audience
      • Two-way check: confirm the audience has ability and availability to engage
      • Defer option: allow postponement or redirection to someone more helpful
    • Building the Skill
      • Write first: draft framing and summary before speaking
      • Payoff: two minutes of prep returns shorter, more effective conversations
      • Internalize: context, intent, key message, goal, problem, solution become natural
      • Exceptional prep: still write summaries for complex or high-stakes topics
  • Resources
    • Reference apparatus: the section is a bibliography only — source citations, URLs, and further-reading titles, with no distillable ideas.
  • Acknowledgements
    • The Work Behind the Book
      • Fifteen years: distilled from communication lessons learned from mentors and colleagues
      • A beginning too: the book launches a new path helping others become great communicators
    • Those Who Made Time and Belief
      • Danielle: gave the two decisive gifts — time to write and belief in its usefulness
      • Against the odds: written through house moves, job and continent changes, a toddler, and a pandemic
      • Rob Alban: supplied the push to start, insisting there was something useful to share
    • Shaping the Manuscript
      • Friesen Press editors: took raw words and moulded them into something readable
      • Editing as revelation: the first round exposed how much help the text truly needed
      • Beta readers: a small group whose input kept the content complete and organized
    • Foundations and Field Testing
      • Carlos de Pommes: taught the first principles of clear communication nearly two decades ago
      • Lasting foundation: those early lessons underpin every idea in the book
      • Workplace labs: telecom and tech employers gave hundreds of hours of real situations to test ideas
• Core Conclusion and Practical Takeaways
  • The Central Conclusion
    • First minute decides: engagement, understanding, and next steps are set before any detail lands
    • Ambiguity is expensive: a 100-person business loses roughly 17 hours weekly to clarification
    • Listeners lack your context: when you don't frame the message, the audience guesses
    • Communication is a skill: organized delivery, not likability, earns professional credibility
    • Eight-to-one ratio: one bad impression takes eight good ones to cancel out
  • Frame in Fifteen Seconds
    • Framing statement: combine context, intent, and key message in under fifteen seconds
    • Context: name the topic so listeners stop decoding and start listening
    • Intent: signal whether to answer, act, decide, or simply listen
    • Key message: lead with the bottom line; answer "so what?" before details
    • One topic, one framing: different contexts or intents need separate openings
  • Summarize with GPS
    • GPS summary: goal, problem, solution structures any topic, role, or industry
    • Keep goal and problem distinct: conflating the two is the most common summary error
    • Solution is forward-looking: state what happens next, not the history of mistakes
    • Unknown solution: state goal and problem, then ask for help finding a fix
    • Share minimally first: give only what's needed to make the point, then add detail on request
  • Check Time and Validate
    • Time check: ask for the real duration, never call a ten-minute talk "a minute"
    • Validation checkpoint: confirm the listener has ability and availability before explaining
    • Give a clear exit: "Are you the right person?" lets listeners redirect you early
    • Your urgency isn't theirs: ask about competing demands instead of assuming shared pressure
  • Daily Practices
    • Write before speaking: one or two minutes of drafting repays itself in faster conversations
    • Emails: subject carries context and intent; body uses labeled Goal, Problem, Solution
    • Meeting invitations: state purpose and expected output; blank invites waste everyone's time
    • Recap the invite: open meetings by restating the framing so everyone shares the goal
    • Reuse everywhere: requests, updates, escalations, interviews, and messaging all follow the same structure