Stuck in a family email thread with no decision? Try this.

Today's Tip: Make sense of a long email thread in under a minute

The most useful AI trick isn't writing new emails. It's making sense of the old ones.

Let me explain…

Wesley Owens got looped into a group email chain last Thursday. His 50th high school reunion is coming up in May. Forty-three replies later, he still couldn't tell you where the venue decision had landed.

Wesley is 68. Semi-retired shop teacher out of Louisville, Kentucky. He still substitutes a couple of times a month, and volunteers with the local Habitat for Humanity carpentry crew on weekends.

Careful reader. Good note-taker.

He tried. Scrolled the whole thread top to bottom. Two people were pushing the Elks Lodge for the reunion. One had a cousin who could get them the country club at half price.

Somebody's spouse had food allergies. Another branch of the chain was about parking… and another about whether spouses were invited to the Friday dinner or only Saturday.

He gave up around reply thirty. Closed the app. Made coffee.

That night his wife said, "Just paste it into that Google thing your grandson showed you."

Here's what happened next…

Wesley went to gemini.google.com on his laptop. Signed in with his regular Gmail account. Opened Gmail in another tab, selected the entire chain — every reply, from the very first message down — copied it, and pasted it into Gemini with a specific prompt.

Fifty-five seconds later, Gemini came back with a plain-English summary. Who wanted what. What had actually been agreed to. What was still open. And what Wesley personally owed a response to.

Plus a draft reply he could actually send.

He read it. Changed one word. Hit send.

Here's the exact prompt that did it.

Wesley's summary came back like this: "This thread concerns picking a venue for the May 2027 reunion. Two attendees favor the Elks Lodge for cost reasons. One favors the country club because of a family discount. No decision has yet been made."

Clear. Finally.

The state-of-play piece told him something he had missed entirely. Someone had proposed a Doodle poll on August 30 to settle the venue question. Wesley had scrolled right past it.

Nobody had voted yet. That was the next step everyone was quietly waiting on… not another round of debate.

Now, I know what you're thinking… this sounds like something my grandson does, not me.

I understand. But here's what changes it.

You are not learning a new app. You are not managing anything. You are copying and pasting one time. That's the whole skill. If you can select text and press paste, you can do this.

Wesley sent that reply. Six people voted on the Doodle poll within two hours. The venue got picked by the weekend. He never had to scroll through the thread again.

Try it the next time you get looped into something. It really is one paste away.

★ Quick Wins

Skill Builder: The Summary-First Prompt

Here is a small habit that will change how good AI is at helping you. Before you ask AI to do anything with a long piece of text — an email thread, an article, a policy letter, a contract — ask it to summarize what it read first. Every single time.

Why? Because AI is fast… and fast is a little dangerous. It will happily draft a reply, argue a case, or write a summary based on what it thinks your input says.

Sometimes that matches what you meant. Sometimes it doesn't… and you'll never know unless you check.

The Summary-First Prompt gives you that check. You ask AI to tell you back what it saw before it does anything else. If the summary is wrong, you catch the mistake before it becomes your problem. If the summary is right, everything that comes after rests on a good foundation.

This works in Claude, Gemini, and Grok. It works for a two-page document or a fifty-page report. It costs you nothing — ten seconds of your time, ten seconds of the AI's time. And it prevents most of the sloppy mistakes AI makes on complex inputs.

Wesley did not know this rule the first time he tried the Thread Untangler prompt. He got lucky that Gemini's summary came back accurate. The next time he uses it, he'll ask for a summary first — and only accept the draft reply once the summary matches what he actually meant.

Small habit. Big difference.