Who said what in the async thread two weeks ago

The thread is almost certainly still in Slack, but you'll find it faster by searching for a weird specific word someone used (a typo, a vendor name) than by scrolling. If the decision lived in a Loom, jump to where comments cluster. The real fix is writing one sentence the day it happened.

It's Tuesday morning, your coffee is still hot, and your manager pings you in DM: "hey, what did we land on for the Q2 onboarding copy?" You remember the thread. You remember Priya pushed back on the second variant, Marcus posted a Loom, and somewhere in there a decision happened. You open Slack, type "onboarding copy," and get 47 results across six channels. You try "Priya copy" and now it's 112. The Loom is bookmarked in Chrome under a folder you renamed three times. You have ten minutes before standup. This is the part nobody warned you about when you took the remote job: the context is saved, it's just unreachable.

Why search bars fail you on async threads

Slack search is built for keywords, not for arguments. An async thread is rarely about one phrase. It's a small braided thing: someone proposes, two people object, a Loom gets dropped in, an emoji vote happens, and then the channel quietly moves on. None of that lives under a single searchable word. You typed "onboarding copy" but the actual decision was phrased "go with variant B and drop the testimonial line," which used none of your search terms.

This is the same trap that turns a Chrome bookmarks bar into a graveyard and a browser bookmark folder into a graveyard you avoid opening. You saved the URL. You did not save the reason. Two weeks later you are searching for the reason, and the URL is useless.

A practical heuristic: in a long thread, the actual decision usually sits near the last reaction emoji, not at the bottom. Reactions are a better seek bar than timestamps.

The Loom you half-watched at 1.75x

Loom is great for letting Marcus on the West Coast explain a Figma file at 9 PM his time so you can watch it at 8 AM Eastern. It is not great for being a record. You watched it at 1.75x while making toast. You remember the screen with the orange button. You do not remember the minute mark, the conclusion, or whether Marcus said "ship it" or "we should probably test this first."

Loom's library lets you filter by date and by space, and the comments are timestamped, which is the trick most people miss. If three teammates dropped comments at 4:12, 4:14, and 4:31, the decision is almost always inside that window. You don't need to rewatch 11 minutes, you need to jump to 4:12. But you have to know to do that, and at 9:50 on a Tuesday before standup, you don't have the patience.

This is why a one-line written summary, posted into the thread or into a Notion page the same day, beats every clever search trick. The summary you didn't write is the search you can't run.

What a US-remote workday actually looks like

You're in Raleigh, your designer is in Portland, your PM is in Brooklyn, and the contractor on the 1099 is in Austin. Standup is async on Mondays and live on Thursdays. The team uses Slack for chat, Loom for walkthroughs, Notion for specs, Linear for tickets, and Figma for whatever Marcus is gesturing at this week. On any given Tuesday you are touching five tabs and a desktop app. Your Chrome window has 31 tabs open. You bookmarked the important one. You named it "copy v2 FINAL" and now you have four of those.

Notion is supposed to be the source of truth, and on the days people write things down it is. But the decision often happens in the Slack thread first, and the Notion page gets updated "later," where later means Friday at 5:45 PM or never. By the time your manager DMs you Tuesday morning, the canonical record is still split across three tools, and you are the one expected to reconstitute it before standup at 10.

The small habit that actually works: when a thread resolves, paste the Slack permalink and one sentence ("we shipped variant B, dropped the testimonial line, May 14") into a single inbox you trust. Could be a Notion page called Decisions, could be an AI-context-memory tool you ask in your own words, could be a Google Doc. The key is one inbox, not seven. Most remote workers I've watched do this end up with the Notion page winning, until the Notion page becomes its own bookmark graveyard, and then they switch.

The retrieval problem nobody puts in the job description

Storage was solved a decade ago. Slack stores everything, Loom stores everything, Notion stores everything, Google Drive stores everything. The 1 TB iCloud plan you pay for stores your screenshots. None of that helps when the question is "what did Priya say about the second variant on or around May 13."

A recall-first approach treats the question as the primary interface. You ask, in normal English, "what did we decide about Q2 onboarding copy two weeks ago," and something matches the meaning of that question against what you actually saved. This is the same shift behind searching notes by meaning instead of keyword and behind remembering a conversation from last week. The bottleneck has moved from save to recall, and most tools have not caught up.

This is where dEssence fits, as one option among several. You save the Slack permalink, the Loom URL, the Notion page, and the Figma link into the Chrome extension, Telegram bot, or the web app at dessence.ai, then ask two weeks later in plain English. No folders, no tags, no organizing. It is not the only way to do this; a disciplined Notion page works, a well-tagged Obsidian vault works, ChatGPT Memory and Claude Projects do a version of this. The right tool is the one you'll actually use on a Tuesday morning before standup.

Honest about dEssence

Notion and Obsidian and Claude Projects are all real options for this scene, and they all have strengths dEssence does not. Notion is a full workspace your whole team can edit. Obsidian gives you a local-first vault you fully own. Claude Projects keeps context inside the chat where you're already working.

dEssence is in beta, which means a few real tradeoffs you should know. There is no native iOS or Android app yet, so on your phone you're using the web app or the Telegram bot. The free tier caps how much you can archive, which matters if you're trying to dump three years of saved threads at once. There is no team workspace yet, so this is a personal recall tool, not a shared one. The paid tier isn't finalized, so pricing later is a known unknown.

Frequently Asked Questions

Q: How do I find a specific Slack message from two weeks ago when I don't remember the exact words? Search for a weird specific token first: a typo, a vendor name, a Loom URL fragment, a number. If that fails, filter the channel by sender and the date range, then scan for the last reaction emoji on the thread. The decision usually sits close to that reaction, not at the bottom of the thread.

Q: Is it worth writing a one-sentence summary every time an async thread resolves? Yes, and the cost is roughly 20 seconds per thread. Paste the permalink, write one sentence with the date and the verb that matters ("shipped," "killed," "deferred to Q3"), drop it in one inbox. The return is that you can answer your manager's Tuesday-morning DM in under a minute instead of 15.

Q: What's the difference between saving context and being able to recall it later? Saving is one click into a bookmark, a Slack save, a Notion page, a screenshot. Recall is finding it later when you can only remember fragments: who was in the thread, roughly when, what the argument was about. Most tools optimize for save. Recall is the harder, less-solved half.

Q: Should I use Loom timestamps or Slack permalinks as the canonical reference? Whichever holds the actual decision. If the call was made on the Loom, link to the Loom with the timestamp in the URL (Loom supports this). If the call was made in the thread, link to the Slack permalink. Linking to both with a one-line summary is better than picking, because future-you doesn't remember which tool held the decision.

Q: How do I keep this habit from becoming yet another folder system I abandon? One inbox, not seven. The moment you have a Decisions Notion page, a Slack saved-items list, a Things 3 project, and a starred Gmail label all running at once, you've recreated the bookmark graveyard. Pick one place. Make it the place you actually open on a Tuesday morning.

If you want to try the recall-first approach without committing to a workflow change, dEssence is free during beta with no card, and you can save the Slack permalink, the Loom URL, and the Notion page into the same inbox and ask in your own words later. The honest caveats: it's beta, there's no native mobile app yet, no team workspace, and the free tier caps archive size, so it's a personal tool for now, not a team source of truth.