Weekly Reviews in Roam Research

TL;DR

Treat the weekly review as a fast capture-and-plan system, not an all-day introspection exercise.

Briefing Cornell Notes

Briefing

Weekly reviews in Roam Research work best when they’re treated as a fast capture-and-plan ritual—not a multi-hour life audit. The core goal is to (1) record what actually happened during the week, (2) identify what should carry forward, and (3) choose priorities for the next seven days so the flood of new inputs doesn’t blur focus.

A common mistake is turning the weekly review into an exhaustive introspection session. Instead, the workflow described here starts with a practical premise from David Allen’s Getting Things Done: the week review sharpens attention by processing completed work and deciding what matters next. In Roam, that translates into a short, repeatable structure built around clarity for the upcoming week. The process can include inbox and calendar checks, but the Roam-specific emphasis is a three-part check-in: list wins, run a plus/minus review of what went well and what didn’t, then decide the “next” actions.

The first section—Wins—begins with gratitude and milestones, not just metrics. Wins can be business milestones (like crossing 600 YouTube subscribers), but they can also be intangible outcomes such as valuable comments, meaningful replies to a newsletter, or simply a good day. The point is to slow down long enough to notice progress before planning the next week.

Next comes the plus/minus review, using a simple structure: “plus” for what went well and “minus” for struggles or missed plans. The “plus” side is built from daily notes—going back through specific dates to pull out concrete accomplishments, such as publishing videos, completing planned tasks, or recording content. The “minus” side goes beyond listing failures by diagnosing why they happened and, crucially, generating solutions or workarounds. If external factors derailed plans (like construction noise), the review should capture what to test next time (sound check, timing changes such as recording earlier). If time management broke down (birthday commitments, underestimating explainer-video effort), the review should adjust assumptions and add realistic buffers.

The “next” section turns insights into an actionable plan. It starts by checking the calendar for already-scheduled commitments, then deciding whether to keep, defer, or eliminate next-week tasks based on limited time and energy patterns (protecting “golden time” in the morning, for example). Tasks that don’t require a specific time block get scheduled via Roam’s date-based reminders and “to-do” entries in daily notes. Larger projects are broken down into next actions—rewriting vague goals into verbs, then decomposing them into steps (e.g., “create presentation,” then define sections, text, design, templates, images, and user-experience considerations). Buffer time is recommended to counter optimistic scheduling, and for manual tasks there’s even a tactic of “beating the clock” to stay efficient.

Finally, journaling closes the loop. It’s framed as free-flow reflection rather than rigid prompts, with examples like “How was my energy this week?” and “What great content did I consume?” This is where patterns and creative connections surface—such as noticing sleep issues tied to specific days, or deriving content ideas from what resonated. The workflow can be skipped when time is tight, but journaling is described as the most insightful part.

To make weekly reviews sustainable, the process can be saved as a Roam template with sections for wins, review (plus/minus), and journaling. The result is a repeatable 30–45 minute system that keeps priorities clear and turns weekly outcomes into next-week execution.

Cornell Notes

A Roam Research weekly review is designed to be quick and actionable: capture wins, run a plus/minus audit, then schedule the “next” actions. The method rejects hour-long life reviews in favor of processing completed work and choosing priorities for the coming week. Wins can include gratitude and milestones (not just numbers), while the minus section requires diagnosing why plans failed and recording workable fixes or adjustments. Next actions are planned by checking the calendar for time constraints and using Roam date-based reminders/to-dos for tasks that don’t need exact time blocks. Free-flow journaling—especially prompts like energy and “great content consumed”—is positioned as the most insightful part because it surfaces patterns and creative ideas.

Why start a weekly review with “wins,” and what counts as a win?

Wins are meant to counter the tendency to forget progress when weeks move fast. The approach emphasizes listing what went well—milestones, gratitude, and meaningful moments—rather than only tracking performance metrics. Examples include crossing a YouTube subscriber milestone (like 600 subs) and also non-metric feedback such as valuable comments or replies to a newsletter that confirm the content resonated with someone.

How does the plus/minus review work in Roam, and what makes the “minus” section useful?

The review uses a simple structure: “plus” for what went well and “minus” for struggles or missed plans. The plus side is built from daily notes by revisiting specific dates and pulling out concrete accomplishments (e.g., published videos). The minus side is more than a list of failures: it asks why the plan didn’t happen and then records solutions or workarounds—like testing sound if construction noise interfered, or adjusting assumptions and adding buffer time when tasks took longer than expected.

How are next-week tasks chosen without overloading the calendar?

Next-week planning starts by checking what’s already scheduled in the calendar, then deciding whether planned tasks still make sense. If commitments conflict, tasks can be deferred, eliminated, or reframed (for example, turning a meeting into an email or phone call). The method also accounts for energy patterns—protecting morning “golden time” for meetings and scheduling accordingly—so the plan matches realistic capacity.

What’s the difference between scheduling on the calendar versus using Roam’s date-based reminders?

The calendar is reserved for items that need specific time frames, especially focus blocks for creative work like writing, recording, or preparing workshops. Roam’s date picker and daily notes handle tasks that only need to happen by a day or within a week, such as “update all the descriptions on videos.” Those tasks are added as to-dos tied to a date, so they appear when reviewing that day.

How should big projects be converted into “next actions”?

Large goals are broken down into the first actionable step and then decomposed into a project-style to-do list. The method stresses rewriting vague intentions into verbs (e.g., “create presentation for the course” instead of “slides”). Then it nests steps like determining sections, writing text, designing with templates, finding images aligned with branding, and planning user-experience elements. Parts that belong later can be tagged with future dates so they resurface during upcoming weekly reviews.

What role does journaling play, and why is it positioned as the most insightful part?

Journaling is free-flow reflection that helps uncover patterns and creative connections. It can use prompts like “How was my energy this week?” and “What great content did I consume?” The method suggests that while wins and plus/minus can feel robotic, journaling lets the inner self connect dots—such as noticing sleep problems on certain days or generating content ideas from what resonated. It’s recommended not to skip journaling when possible, though it may be shortened when time is tight.

Review Questions

What specific information should be captured in the “minus” section to make next week’s plan smarter (not just more accurate)?
How would you decide whether a task belongs on the calendar versus as a Roam date-based to-do?
If a project estimate repeatedly runs long, what adjustment does this weekly review process recommend making to your planning assumptions?

Key Points

1
Treat the weekly review as a fast capture-and-plan system, not an all-day introspection exercise.
2
Use a three-part Roam structure: Wins (gratitude and milestones), Plus/Minus (what went well, what struggled, and why), and Next (priorities and scheduled actions).
3
In the minus section, record the cause of failure and at least one workaround or fix so the same problem doesn’t repeat.
4
Plan next week by checking the calendar first, then using Roam date-based to-dos for tasks that don’t need exact time blocks.
5
Convert vague project goals into verb-based next actions and break them into nested steps (text, design, templates, assets, and user experience).
6
Add buffer time to counter optimistic scheduling, especially for manual or multi-step tasks.
7
Save the weekly review as a Roam template so the process stays consistent and takes roughly 30–45 minutes.

Highlights

The weekly review’s purpose is focus: capture what happened, diagnose what didn’t, and choose what matters next—without turning it into a life audit.

The minus section isn’t just “what failed”; it requires a reason and a workaround (e.g., construction noise leads to sound testing and earlier recording).

Roam’s date picker plus to-dos handle day-level commitments, while the calendar handles time-specific focus blocks.

Buffer time is built in to prevent optimistic estimates from collapsing during execution.

Journaling is framed as the most insightful part because it surfaces patterns and content ideas.

Topics

Mentioned

David Allen