The entry point for almost everyone. Low-demand, no personal disclosure required, and it gets speech happening before anyone has to be good at it.

1. Pick a category: favorite color, favorite move, animal you would be, period in history you would visit, cuisine, car, vacation spot, sandwich.
2. Everyone answers in one sentence. First round is the answer only.
3. Second round: the same answer, plus one sentence of why.
4. Third round: someone else asks you a follow-up question about your answer.

The jump from round one to round three is the actual skill: holding a short exchange rather than delivering an answer.

Twenty questions and its relatives. Trains question quality, turn-taking, and tolerating not knowing yet.

1. One person thinks of an object, person, or place.
2. Others ask yes-or-no questions only. Cap it at twenty.
3. Afterward, review which questions narrowed things down and which wasted a turn.
4. Play again with a rule: no question may repeat information you already have.

Broad questions early, narrow questions late. Most people reverse it.

Communication with the words taken away. Useful for anyone who over-relies on verbal precision, and a relief for anyone who finds talking effortful.

1. Draw a prompt from a hat and represent it — drawing only, or gesture only.
2. Others guess aloud.
3. Switch to a version where the drawer may say one word, then two, then a full sentence.
4. Discuss which version was easiest and why.

How much information travels without speech at all. That is the channel you are also using in every conversation.

Words only, no gestures. One of the most revealing activities in the set — it exposes vagueness instantly.

1. One person has a simple picture the other cannot see. A house, a face, a pattern of shapes.
2. Using words only, guide the other person to draw it. No pointing, no showing.
3. Compare the drawing to the original.
4. Swap roles. Then run it again with a rule that the drawer may ask questions.

Round two with questions allowed is almost always better. That is the case for checking rather than assuming.

For many people this is the single hardest sentence to say at work. It is a script, and scripts can be learned.

1. Write the ask in one sentence. What you need, from whom, by when.
2. Say it aloud and record it.
3. Play it back. Count the qualifiers — sorry, just, if you have time, no rush, maybe.
4. Record it again with every qualifier removed. Compare the two.
5. Practice three versions: to a peer, to a supervisor, to someone you do not know well.

Removing qualifiers usually feels rude and almost never sounds rude on playback. That gap is the whole lesson.

Offering badly reads as pity or as taking over. Offering well leaves the other person in charge.

1. Practice the difference between “let me do that for you” and “would it help if I took the X part?”
2. Role-play offering to three people: someone struggling openly, someone hiding it, someone who has refused before.
3. Try an offer that names something specific rather than “let me know if you need anything.”
4. Practice accepting a refusal without pressing.

Specific offers get accepted. Open-ended ones almost never do.

Saying what you are trying to do, before you do it. Prevents an enormous amount of misreading.

1. Write a one-sentence version of what you want from a coming conversation.
2. Practice opening with it: “What I am hoping to get out of this is…”
3. Try the same sentence in three registers — casual, neutral, formal.
4. Practice a version that names what you are not asking for.

Naming your intention out loud usually shortens the conversation and lowers the temperature.

The counterpart skill, and the one that most changes how people respond to you.

1. Practice the open version: “What are you hoping happens here?”
2. Practice it before a disagreement rather than during one.
3. Try it with someone whose position you already think you know. Notice whether you were right.
4. Practice reflecting the answer back before responding to it.

The urge to answer before they finish. Sit through it.

Asking in a way that gets you something usable instead of “you are doing fine.”

1. Practice narrow questions: “What is one thing I could have done differently in that meeting?”
2. Compare it to the broad version: “How am I doing?” Notice what each one gets you.
3. Role-play receiving an answer you did not want. Practice saying only “thank you, let me think about that.”
4. Practice a follow-up that asks for a specific example.

The reflex to defend. Every second spent defending teaches the person not to tell you next time.

Specific, behavioral, and separated from character. Hard to do well and highly learnable.

1. Practice the structure: what you observed, what effect it had, what you are asking for.
2. Strip out every character word — lazy, careless, difficult. Replace with the observable behavior.
3. Record it. Play it back and ask whether you would want to receive it.
4. Practice giving positive feedback with the same specificity. Most people are vague when it is good news.

Whether your version names a behavior or names a person. That is the whole difference.

Saying no, declining, and stating what you will and will not do.

1. Write the limit in one sentence with no explanation attached.
2. Say it aloud and record it. Then record it again with an explanation added.
3. Compare. Notice which one sounds firmer and which one invites negotiation.
4. Practice three: a small limit, a medium one, and one that matters.

Explanations invite debate. A limit stated plainly usually ends the conversation.

Different from setting one. This is what you do when the limit is tested — and it usually is.

1. Role-play stating a limit, then having it pushed back on. Twice.
2. Practice repeating the same sentence without adding new justification.
3. Practice staying warm while repeating — tone steady, volume steady, no escalation.
4. Practice the exit line: “I understand, and my answer is the same.”

Adding new reasons each time. It signals the limit is negotiable.

Checking that what you said is what landed. The least glamorous skill here and possibly the most useful.

1. Practice the summary: “So what I am hearing is… have I got that right?”
2. Practice asking for it in reverse: “Can you tell me what you are taking away from this?”
3. Deliberately mis-summarize once and notice how quickly it gets corrected. That is the point of asking.
4. Practice ending an exchange by naming what happens next and who is doing it.

How often the summary does not match. In most conversations nobody ever checks.

A ratio, not a feeling. Count what you actually say over a day and most people find they are correcting far more than they are affirming — usually without any idea that is the balance.

The target is simple: at least two genuine affirmations for every redirection. Not to be soft. Because a person who only ever hears from you when something is wrong learns to brace when you approach, and a braced person does not take in correction.

1. Count first, before changing anything. One day, two columns: what you praised, what you redirected. Most people are surprised, and the surprise is the useful part.
2. Check that the praise is real. Vague praise does not count toward the ratio and does not build anything — “good job” is not an affirmation, it is a noise.
3. Practice specific praise: the behavior, its effect, and why it mattered. Rehearse three out loud.
4. Practice praising something ordinary. Most people only affirm the exceptional, which means most work goes unremarked.
5. Practice praising in front of others, and redirecting privately. The reverse is common and does real damage.
6. Recount after two weeks. Ratios shift slowly and it is worth seeing that they shift.

Praise used as setup. If every affirmation is immediately followed by a correction, people learn to hear praise as a warning and it stops working entirely. Some praise must arrive with nothing attached.

Before the request, the correction, or the directive — name something true about the other person’s growth, gifts, or contribution. Then make the ask.

This is not a softening technique and it is not flattery. It establishes what you have actually noticed, so the request arrives to someone who knows they are seen rather than someone bracing for criticism. The anchor must be true, specific, and about them.

1. Write the ask plainly first. You need to know exactly what you are requesting before you build anything around it.
2. Find the anchor. Something you have genuinely observed — a strength, a contribution, or growth you have watched happen. Not a compliment; an observation.
3. Make it specific enough that only this person could receive it. “You are great” anchors nothing. “You caught the error in that report before it reached the client” anchors firmly.
4. Say the anchor, then a beat of silence, then the ask. Record it. The silence matters — it stops the anchor reading as a preamble.
5. Practice the version where the anchor connects to the ask: “You are the most careful person on this team, which is why I want to ask you about…”
6. Practice it with someone difficult. This is where it does the most work, and where it is hardest to find a true anchor.

Two things collapse this. The word “but” — it deletes everything before it, and people hear only what follows. Use a full stop instead. And the manufactured anchor — if you had to invent something nice, do not say it. A false anchor is worse than none, because it teaches the person your praise is a delivery vehicle.

It changes what the listener is doing while you speak. Someone anticipating criticism spends the conversation preparing a defense and takes in very little. Someone who has just been genuinely seen has capacity left to actually hear the request.

Most people handle this one of two ways: avoid it until it becomes a crisis, or brace for it and go in cold. Both come from the same belief — that honesty and warmth cannot occupy the same conversation.

They can, and the combination is what makes the message survivable. Softening the content is not compassion. Delivering it coldly is not honesty. The work is holding both.

1. Write the hard sentence first — the actual thing, in plain words, before any cushioning. You need to know what you are really saying.
2. Say it aloud and record it. Play it back and ask two separate questions: is it clear, and is it kind? Score each one to five.
3. Record it again fixing only the lower score. Do not soften a clear message; do not sharpen a kind one.
4. Practice the opening. Name what the conversation is about before you begin it — no ambush, no long preamble.
5. Practice the pause. After the hard sentence, stop. Let it land. Most people fill that silence and undo the message.
6. Practice staying. Role-play the other person becoming upset, defensive, or tearful, and stay in the room without retreating or hardening.
7. Practice the close: what happens next, and what your support looks like.

The two failure modes are opposite and equally common. Cushioning — wrapping the message so thoroughly that the person leaves without knowing anything was wrong. And armoring — going in braced, delivering it flat, and leaving quickly. Listen to your recording for which one is yours.

Withholding honest feedback to spare someone’s feelings is not a kindness. It denies them information they need and would probably want. The warmest available action is usually to tell them the truth and stay with them while they take it in.

Collaboration is not the same as everyone being nice, and it is not the same as everyone agreeing. It is a set of concrete habits that make it rational for people to share what they know rather than hold onto it.

1. Ask what actually gets rewarded where you are. Individual heroics, or work that made someone else’s job easier? People collaborate when collaboration is what gets noticed.
2. Practice crediting out loud. Rehearse naming whose idea it was, in a room where it counts. Specific, by name, unprompted.
3. Practice inviting before deciding. “Here is where I am leaning — what am I missing?” Compare it to announcing a decision and asking for thoughts afterward.
4. Practice asking the quietest person first. Notice how much this alone changes what a group produces.
5. Practice disagreeing with the idea while backing the person. Rehearse the sentence that does both at once.
6. Practice handing something over. Delegating without hovering is a communication skill, not a management one.
7. Choose one habit and run it for a month. Opening meetings by asking rather than telling is usually the highest-yield place to start.

Collaboration theater — asking for input after the decision is made. People detect this immediately and it costs more trust than not asking at all. If it is already decided, say so and say why.

This one changes more than any other item here, and it is a stance rather than a technique.

Most communication is delivery-oriented. I said it. It was in the email. I explained it twice. Under that stance, once the words leave you, responsibility transfers to the listener.

Commitment-oriented communication starts somewhere else: I am committed to this person actually receiving the message and getting what they need. Which means the job is not finished when I have spoken. It is finished when they have it.

1. Name the difference. Take a recent frustrating exchange and ask: was I trying to be understood, or trying to have said it?
2. Practice stating commitment out loud at the start. “I want to make sure this actually works for you, so tell me if I am not being clear.”
3. Practice checking rather than assuming. Ask what they took from it — not whether they understood, which almost always gets a yes.
4. Practice the second attempt. Role-play saying the same thing a completely different way, without any sign of impatience.
5. Practice taking the miss. Rehearse “that was on me, let me try again” instead of “as I said before.”
6. Practice asking what would help. “Would it be easier written down? Would an example help? Shall we do it together the first time?”

The phrases that give the stance away: as I already mentioned, like I said, I sent that last week. Each one moves the failure onto the listener. Notice them in your recordings and in your email.

This is the stance that makes every other activity work. Someone committed to being understood will naturally slow down, check, rephrase, and try again — without being taught any of those separately. And for anyone on the receiving end who processes language differently, the difference between a delivery-oriented speaker and a committed one is the difference between struggling and being included.

Every other activity here works on how you communicate. This one is about the room you are in — and it applies whether you lead a team, sit on a committee, or are simply the person everyone notices.

Kindness and excellence are usually treated as a trade-off: be warm or be demanding. They are not opposites. The environments people describe as the best they ever worked in almost always had both, held at the same time.

1. Name the culture you are actually in. Describe a recent ordinary moment — not a crisis — and what it revealed. How does this group treat a mistake? A question? A quiet person?
2. Separate the two axes. Score your setting twice, one to five: how kind is it, and how excellent is it? Most people find they are high on one and low on the other, and the gap is the work.
3. Identify what you personally set. You establish culture in three places: what you praise out loud, what you let pass, and how you respond when something goes wrong. Pick the one you have most control over.
4. Practice specific praise. Vague praise builds nothing. Rehearse naming one behavior, its effect, and why it mattered — out loud, in front of others, using the person’s name.
5. Practice holding a high standard warmly. Role-play saying “this is not there yet, and I think you can get it there” without softening it into nothing or hardening it into a rebuke.
6. Practice repairing publicly. Rehearse acknowledging your own error in front of the group. This single act does more for psychological safety than any policy.
7. Choose one small change and run it for a month. Opening a meeting by naming something that went well. Asking the quietest person first. Thanking someone specifically rather than generally.

The belief that kindness lowers the bar. In practice the opposite holds — people take feedback, admit errors, and ask for help far more readily where they are treated well, and all three are prerequisites for excellent work. A group that is only demanding does not get excellence; it gets concealment.

Kindness that avoids the hard conversation. Withholding honest feedback to spare someone’s feelings is not kindness — it denies them the information they need. The warmest thing you can do is tell someone the truth and stay with them while they take it in.