How to Find an Old Slack Thread

Start with the narrowest detail you remember

Do not begin with a broad phrase such as “onboarding copy.” Common project language can produce pages of results.

List the fragments you still remember:

• Who participated
• The likely channel
• The approximate week
• A customer, vendor, or product name
• A number or deadline
• A link to Loom, Notion, Linear, or Figma
• An unusual phrase or typo

Start with the rarest fragment. A vendor name or misspelled word usually removes more noise than the main topic.

If the search fails, change one variable at a time. Keep the sender and change the date range; keep the channel and replace the topic with a tool or person. This helps reveal which memory is wrong without making the search broad again.

Searching “onboarding copy” might produce 47 results across six channels, while another broad combination can make the set larger rather than smaller. The thread is rarely indexed by the sentence now in your head.

Filter before you scroll

Narrow results by channel, sender, and approximate date. You may not remember the exact Tuesday, but you may remember whether the discussion happened before a launch, after a customer call, or during a project phase.

Open likely messages in their original context and inspect their replies. Scrolling an entire channel should be the last resort.

Search for links when words fail

Async decisions often cross tools: a question begins in Slack, details move into Loom, a specification changes in Notion, and work is assigned in Linear.

Search for the tool name or a fragment of its link. Also check related Notion pages, tickets, or meeting notes for a Slack permalink.

A plain bookmark often becomes a bookmark graveyard: the URL survives while its role in the decision disappears.

Inspect reactions near the decision

The final decision is not always the last reply. A thread may end with acknowledgements, side questions, or scheduling details.

Look for a proposal or confirmation that received several reactions, then read several replies before and after it. The decision may be approving a variant, delaying a release, or assigning an owner. Attention alone does not prove that a suggestion became the final choice.

Once you find the answer, copy the message permalink.

Follow the discussion into Loom

If the thread points to a Loom recording, inspect timestamped comments. A cluster around 4:12, 4:14, and 4:31 can define the section worth watching instead of replaying the whole recording—especially if the original viewing happened at 1.75× while you were distracted.

Watch enough context to distinguish “we could ship this” from “we will ship this.” Then return to Slack for replies posted after the recording.

Meeting records fail similarly when a transcript exists but the decision continues elsewhere. The best meeting notes app for follow-up context keeps the decision connected to what happened next.

Check the likely source of truth

Inspect the Notion specification, Linear ticket, or Figma comments if Slack does not settle the question. Do not assume an official document is current; compare its update time with the discussion.

Your goal is the latest decision and the context supporting it, not merely a matching sentence. This resembles searching notes by meaning: you reconstruct the event from people, dates, links, and actions.

Save one sentence when the thread resolves

The easiest thread to find is the one summarized when it ended.

Write one sentence with the decision, date, and important names. Add the Slack permalink and any essential Loom or Notion link. For example:

Onboarding copy: chose variant B, removed the testimonial line, decision in Priya’s Slack thread.

A good decision note answers:

1. What was decided?
2. Who was involved?
3. When did it happen?
4. Where is the original discussion?

Include the informal words you expect to remember—such as “the orange button”—alongside the official name. Keep these summaries in one trusted destination, whether that is a Notion decisions page, private document, AI context memory, or dEssence.

dEssence can hold a saved Slack permalink beside related Loom and Notion links so you can ask about those saved items later. Splitting summaries across Slack saves, browser bookmarks, and several note apps recreates the problem.

The same rule applies to useful Twitter threads and to remembering a conversation from last week: keep the reason and takeaway with the link.