Mem Tutorial: How to Use Your Inbox to Prioritize What's Important
Based on Maximize Your Output with Mem: Mem Tutorials 's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Mem’s inbox is best treated as a holding area for notes that still need processing, not as clutter to clear immediately.
Briefing
Mem’s inbox is positioned as the missing step between collecting information and turning it into usable knowledge: capture first, then process later—without getting pulled into constant context switching. The core idea is that notes only become valuable when someone takes time to reflect on them, and the inbox acts as a holding area for items that still need attention. Instead of treating the inbox like clutter to be cleared immediately, it’s framed as a prioritization engine that prevents important insights from getting lost in Mem’s non-linear timeline and link network.
A key concept is separating “capture” from “processing.” When someone saves notes—whether they come from books, highlighted quotes, podcast takeaways, meeting summaries, online courses, or even raw ideas from watching a video—the moment of capture is the worst time to decide what the note means or where it belongs. Trying to interpret and route a note in the same instant forces a context shift: the mind moves from the original input context to a new one, which can distract and waste time. The inbox solves this by letting people postpone interpretation until later in the day, when they can focus on processing with less mental friction.
The inbox also supports prioritization by destination rather than source. Instead of constantly asking, “Where did this come from?” users can later decide, “Where will this be used?”—for example, which article it supports, which project it feeds, or which blog post it can strengthen. This destination-based approach reduces the urge to constantly reorganize during capture and keeps the workflow for note-taking distinct from the workflow for execution.
Concrete examples in Mem illustrate how the inbox prevents forgetting. Notes added incrementally from Thiago Forte’s book “Building a Second Brain” are placed into the inbox, then later revisited to connect them to specific writing tasks—such as an article about why self-improvement reading alone isn’t enough. The inbox also holds “soon-to-be” literature notes and raw thoughts that aren’t ready for processing, ensuring they don’t vanish under new entries.
Project planning is another use case: a note titled “design and experience,” originally sparked by text messages and sitting in the inbox, is retained until it’s time to act—here, tied to a talk for a UPS store convention about designing customer experiences. Blog work benefits too: small nuggets and bi-directional links that would otherwise remain unnoticed in the broader network are surfaced through the inbox, including an outline for the video itself that was still being built while recording.
The practical takeaway is behavioral: clearing the inbox right away can lead to blank notes and missed opportunities. Keeping items in the inbox long enough to process them helps users prioritize what matters, remember what they captured, and generate knowledge instead of merely storing information.
Cornell Notes
Mem’s inbox is presented as a staging area for notes that haven’t been processed yet. The central workflow principle is to separate capture from processing: save ideas immediately, but decide what they mean and where they belong later to avoid context switching. The inbox helps prioritize by destination (which project or output a note will support) rather than by source (where it came from). Examples include keeping book takeaways in the inbox until they can be used in articles, holding “soon-to-be” literature notes, and retaining project ideas like “design and experience” until a talk is ready. Clearing the inbox too quickly can create empty notes and cause valuable insights to be missed.
Why is deciding what a note means at the moment of capture considered a bad time to do it?
How does the inbox improve prioritization compared with relying on Mem’s timeline and links?
What does “organize by destination instead of source” mean in practice?
What kinds of notes are good candidates for the inbox?
How do the examples show the cost of clearing the inbox too quickly?
Review Questions
- What specific problem does the inbox solve in the capture-to-processing workflow, and how does it reduce context switching?
- Give two examples of how a note in the inbox later becomes part of an output (article, blog post, or project).
- Why does “destination-based” organization matter more than “source-based” organization when processing notes?
Key Points
- 1
Mem’s inbox is best treated as a holding area for notes that still need processing, not as clutter to clear immediately.
- 2
Deciding what a note means right when it’s captured causes context switching and can waste attention.
- 3
Separating capture from processing lets people revisit notes later in the day with better focus.
- 4
Prioritization improves when notes are revisited from the inbox instead of hunted through a non-linear timeline of links.
- 5
Organizing by destination (which project/output a note supports) reduces constant reorganizing during capture.
- 6
Keeping notes in the inbox helps prevent forgetting ideas that would otherwise get buried as new entries arrive.
- 7
Clearing the inbox too fast can produce empty notes and cause valuable insights to be missed.