The response bank: one moment, many sentences

Most of this book gives you the ideal sentence for a moment. This chapter gives you the range, because fluency is not owning one good answer; it is owning five and choosing where to land. The textbook-taught engineer answers "How are you?" with "I am fine, thank you" forever, which is grammatical and slightly alien; real workplaces run on a spread of registers from enthusiastic to deliberately flat, and every band is professional in the right moment.

The five bands

For almost any social question there are five honest answer bands:

Two rules govern the whole table. Match energy roughly: a low-key answer to an enthusiastic asker is a mild door-close (fine if intended), while interrogating a low-key answerer ("just OK? what's wrong?") barges through a door they closed on purpose. And returning the question is the real politeness, whatever the band; "Not too bad. You?" is complete, while a bare "not too bad" plus silence ends the exchange with a thud.

"How's it going / how's your day / how are you?": the full spread

Ways to ask, roughly casual to warm: "You good?" (very casual, peers only) / "How's it going?" (the universal) / "How are you doing?" / "How's your day going?" / "How's your day treating you?" (playful) / "How are things?" / "How's life?" (broader, invites non-work) / "Everything OK?" (careful: this one signals you noticed something; do not use it as a plain greeting).

Low-key answers, the band non-native speakers most lack, with tone notes:

• "Not too bad." (the workhorse; means anywhere from fine to good)
• "Can't complain." (cheerfully flat; optionally "...well, I can, but nobody's paying me to")
• "Getting there." (mid-task flavor: the day is a slog being won)
• "Hanging in there." (wry; a shade more tired than "getting there")
• "Same old, same old." (routine, not unhappy)
• "Surviving!" (jokey-tired; fine among peers, skip with execs)
• "It's going." (deadpan; the shrug in word form)
• "Oh, you know. Monday." (weekday as complete explanation)

Weekend versions of the same spread, since "how was the weekend?" is the Monday ritual (Chapter 32):

• Enthusiastic: "Excellent; we finally did the coast hike."
• Warm-neutral: "Really nice, thanks; mostly family stuff. Yours?"
• Low-key: "Nah, stayed home, didn't do much. It was nice, actually." / "Quiet one, exactly what I needed." / "Didn't get up to much; recharged, mostly." / "Lazy one. No regrets."
• Honest-negative: "Honestly, mostly errands and a leaking sink. Ready for the work week, which tells you something."
• Deflecting: "Short. They always are. How was yours?"

Notice the trick inside the low-key band: the tiny tail ("it was nice, actually", "no regrets", "exactly what I needed") converts "didn't do much" from a shut-down into a contented answer. Without a tail or a return question, flat answers read as "don't talk to me", which is occasionally exactly what you mean; then they are working as designed.

Don't be confused: the understatement family. In British, Irish, Australian, and much Commonwealth English, negatives of negatives do heavy lifting: "not too bad" can mean genuinely good, "not the worst idea" is real approval, and "I'm not sure that's right" frequently means "that's wrong." Meanwhile "quite good" means very good in American English and merely somewhat good in British English. You do not need to adopt understatement, but you must decode it: when a British colleague says your design is "not bad at all", you just got a compliment, and when they say the plan has "a couple of issues", count the issues yourself.

Addressing someone whose name you don't know

The gap every non-native speaker feels: many languages have a standard stranger-address word, and workplace English mostly does not. The kit:

• Getting attention: "Excuse me..." is the universal opener, office or street. Softer workplace variants: "Hi, sorry to interrupt..." / "Sorry, quick question..." In someone's field of view, a small wave plus "hi" outranks any word; never tap, hover silently, or start talking to headphones (Chapter 32).
• What NOT to call people: "Sir" and "Ma'am" read as service or military register in most tech workplaces (and guess at gender); "Miss/Mrs" worse; "hey you" is rude; "buddy/chief/boss/ mate" are regional minefields (natural in some places, smarmy in others; if it is not native to your mouth, skip it). The professional solution is that you do not need any address word: "Excuse me, are you the right person to ask about badge access?" is complete.
• By role, when needed in a group: "the colleague from security", "whoever raised the latency point earlier, could you say more?", "sorry, I don't know everyone's names yet: the person who owns the deploy tooling?"
• Converting no-name to name, fast: "I'm Alex, by the way" (the reciprocal-trigger, Chapter 32) / "I didn't catch your name?" (fine even twenty minutes into a conversation) / and then use it once immediately: "Thanks, Noor" welds it into memory.

The meeting response bank

You are asked something in a live meeting: standup, planning, a demo, a tech talk, an exec review. Your possible truthful states are finite, and each has several good sentences. This is the bank.

You know the answer:

• "Three days, and the risk is the vendor quota." (answer first, one support: the default)
• "Short answer yes; nuance if you want it."
• "Two numbers: p50 is flat, p99 doubled. The story is the p99."

You know part of it:

• "Half-answer now, half by EOD: the write path does X, confirmed. The read path I'd be guessing; I'll check."
• "I can speak to the API side; Yuki owns the storage half."
• "Directionally yes, but don't quote the number until I verify."

You don't know:

• "I don't know offhand, and I'd rather not guess in a decision meeting. I'll post the answer in the thread by tomorrow."
• "Genuinely don't know; who's closest to the replication side?"
• "Unknown, and it's the right question; adding it to the open list."

You need a moment:

• "Give me ten seconds to think rather than improvising."
• "Let me think out loud, and stop me where I go wrong: ..."
• "Can you take the next question and come back to me? I want to do that one justice."

You didn't hear or follow:

• "Sorry, say the last part again?"
• "The exchange races the... what? I lost one word."
• "I lost the thread for a second; can you repeat the question?" (the honest zone-out recovery; infinitely better than a bluffed answer to a half-heard question)

The question is out of scope for this meeting:

• Standup: "Real question, wrong ceremony; grab me right after?"
• Demo: "That's roadmap territory; Priya, want it now or in the thread?"
• Tech talk: "Deserves a whiteboard, not a drive-by answer; find me after and I'll happily go deep."
• Exec review: "That's a one-way-door question and I don't want to answer it casually; can I owe you a written answer Thursday?"

The question challenges your work:

• "Fair challenge. Short version: X. Long version with data in the thread."
• "You might be right; the way to know is the replay, and I'll run it today."
• "Let me steelman that back before I answer, because if I've got your concern wrong my answer will miss: ..." (Chapter 26)

You're asked to take on more (planning, mid-sprint):

• Yes: "Yes, and it fits; the audit story is small."
• Conditional: "Yes if the demo prep moves to Ravi; I can't hold both."
• No: "Not without dropping something visible. What should move?" (Chapter 28)

Someone answers your question FOR you (the interceptor):

• Merge: "Exactly what Sam said, plus one detail: ..."
• Reclaim, gently: "Let me add the part only I know, since it was my incident: ..."
• Correct: "Sam's close; one correction that matters: it was the cap, not the timeout."

The pattern across all nine states: name your epistemic state honestly (know / part / don't / need time), then route (answer, defer, redirect, or verify). Meetings forgive every state except the bluff.

👉 One moment, many sentences works for questions; the next chapter applies the same method to a full technical fight. One suspicious diff (the search index says dot product, the design doc says Euclidean), one worried engineer, and every rung of the ladder for raising it, answering it, and standing corrected by the algebra. On to Chapter 40.