In your next one-on-one, paraphrase the main point once in your own words. Doing it just once matters because it pushes you to capture the essence of what your colleague actually said instead of mentally rehearsing your reply and waiting for your turn to talk.
Your Practice Loop
Pick one low-stakes conversation today, such as a standup update or a short call, and commit to paraphrasing once before you respond. Reps matter more than difficulty here, so a small meeting is enough for your first attempt.
While the person speaks, note their main point in three or four keywords on paper or in your notes app. This keeps your attention on their message instead of on what you plan to say next.
When they finish, reflect the essence back in your own words, not verbatim, without adding praise or judgment. Keep it to one or two sentences so the moment stays natural.
Then ask one or two open-ended clarifying questions, such as What would that look like in practice? rather than yes or no questions. Aim for two questions per session in the first week.
Finish by checking your paraphrase directly: ask Did I get that right? Listen to the answer, since their confirmation or correction is the real feedback for this drill.
If their reply shows you missed the point, restate it once more with the corrected detail. One correction per conversation is fine at first, and catching the miss is progress, not failure.
A Full Demonstration in a One-on-One
Imagine a colleague says, I'm worried the launch date is unrealistic because QA still has twelve open bugs, and the team is already stretched thin. You paraphrase: So you're concerned we can't hit the launch because QA load and team capacity are both tight? No judgment added, just the essence in different words.
She replies, Exactly, though the bug count is the bigger issue than capacity. You caught the main concern, and her correction sharpens one detail, which is the drill working as intended. Your follow-up question: What would you cut from the release to shrink QA time?
Here is a weaker version to contrast. So you think the launch will fail? pushes a conclusion she never made and invites defensiveness. Notice the difference: capture her stated point, not your prediction of where it leads.
One more pattern to avoid. Repeating her words almost verbatim, like You're worried the launch is unrealistic because of twelve bugs, sounds like an echo rather than understanding. Swap in your own phrasing so she can hear how you interpreted it.
Run this once in a real one-on-one today. The demonstration above gives you the shape: her words, your paraphrase, her confirmation, one open question. One honest attempt with a real colleague teaches more than rehearsing the perfect sentence alone.
Observable Self-check and Next Adjustment
After the speaker finishes, use one observable check: note down whether they confirmed or corrected your paraphrase. Their reply, not your feeling about it, tells you the drill worked. Did I get that right? is enough, and a correction counts as data, not failure.
Track one tally per conversation for a week: confirmed, corrected, or no reply. A simple notes-app line like confirmed, launch QA point keeps it honest. Aim for two confirmations by the end of the week before changing anything.
Then make one adjustment: shrink the paraphrase. If you needed several sentences, cut the next one to a single sentence capturing only the main point. Shorter reflections are easier for the speaker to confirm or correct, so the feedback loop sharpens with each attempt.