Someone asked me about a decision I made four months ago. Which vendor we chose for a project. The answer was real. I knew we had decided something. I just could not find where that decision lived.
I opened Outlook and searched for the vendor name. Nothing came up because the email thread was about something else. I checked the shared folder for project documents. The decision was in a Word file, buried in a paragraph that was mostly about timelines. I pulled up the Teams meeting transcription. The conversation was there, but the transcription was 40 pages long and I had to read through it to find the part where we actually landed on something.
It took 20 minutes to find a decision I made in two minutes.
The gap between storing and retrieving
Most people assume the problem is forgetting. You made a decision, you wrote it down somewhere, and now you cannot find it. The problem is your tools are built for storing information, not retrieving it.
You can have every decision documented across your email, your documents, and your meeting notes. You can be the most organized person on your team. That still does not help when someone asks, “What did we decide about this?”
The information exists. It is just scattered across three different tools, each with its own search, each with its own way of organizing things. You know the answer is somewhere. Finding it is the work.
The time cost nobody tracks
Think about the last time you searched for a past decision. You probably did not count the minutes. But those minutes add up.
A single search through email, documents, and chat can take 15 to 20 minutes. Do that three times a week and you are losing an hour every week. Over a year, that is 50 hours spent looking for things you already decided.
The cost is even higher when the search happens in a meeting. You are on a call. Someone asks about a past decision. You say you will get back to them. You spend 20 minutes searching after the call. Then you get back to them. Then you spend another 10 minutes explaining the context because your note only had the decision, not the reasoning behind it.
The decision itself took two minutes. Retrieving it took 30.
Why your existing tools struggle with this
Email search works when you remember the sender or the subject line. It does not work when you are searching for a concept. “What did we decide about the vendor?” is not a subject line. It is a question your email client cannot answer. The same fragmentation that scatters your work context across email, chat, and your task list makes searching for past decisions nearly impossible.
Document search finds files that contain your keywords. It does not tell you which paragraph in a 10-page document holds the decision you need. You find the file and then you read through it.
Meeting transcriptions capture everything that was said. They also capture everything that was not a decision. The decision you need is one sentence in a 40-page transcript. You have to read the whole thing to find it.
Notes apps and knowledge bases solve this problem by asking you to write the decision down in a dedicated place. The problem is they require you to decide what is a decision worth saving, where to file it, and how to tag it. That decision-making step is exactly what you do not have time for when you are in the middle of a meeting.
Calendar tools remind you about upcoming events. They do not help you recall what happened in a meeting three months ago.
None of these tools are broken. They are just not designed for the question, “What did I decide about this months ago?”
What actually works
Keep a decisions log. It is a simple document where every decision lives in one place, searchable by topic.
The trick is not writing decisions by hand. You already have meeting transcriptions and AI summaries. Use them.
Here is the workflow I use.
Paste the meeting transcription or summary into an AI tool. ChatGPT, Claude, Copilot — any AI that can read text. Add this prompt:
“Extract all decisions from this meeting. For each decision, give me: the topic, what we decided, and the reason. Format as a simple list.”
Copy the output into your decisions log. The AI will give you structured decisions from the raw meeting text. You do not have to read through 40 pages of transcription yourself.
Add the date and meeting name at the top of each batch. “July 10 — Project X review.” This lets you search by date or project later.
This takes about 30 seconds per meeting. Paste, prompt, copy. The AI does the heavy lifting of finding decisions buried in discussion.
When someone asks “what did we decide about the vendor?” you search the document for “vendor” and find the answer in seconds. You do not open a transcription. You do not read through a summary hoping it mentions the decision.
The downside is the 30 seconds. If you skip it, the decisions stay buried in transcriptions. The AI extraction only works if you actually run it and save the output somewhere searchable.
Review the log once a month. Close out decisions that are no longer relevant. Archive old projects. A 50-line log is easy to search. A 500-line log is not.
The insight
Storing information and being able to retrieve it are two different problems. Most tools solve the first one and leave you to figure out the second.
The fix is faster capture, automatic structure, and a single place where you can ask questions instead of running searches across multiple tools.
Your decisions are worth more than the time you spend looking for them.