The Cannonical Roam Demo - complete version

TL;DR

Roam’s slash commands can insert 24-hour “current time” timestamps, enabling manual time tracking that links back to specific work sessions.

Briefing Cornell Notes

Briefing

A workflow built around Roam turns note-taking into a system for time tracking, task management, and email drafting—without forcing users into rigid folders. In a live demo, Roam is presented as “an Excel of note-taking,” where indented lists gradually unlock deeper capabilities like linked references, tables, and automated views. The practical payoff is that tasks and notes can be filtered by context (time, projects, or domains like email) so people can keep an “inbox zero” style workflow while still retaining a searchable knowledge base.

The demo starts with attention management: user interviews and work sessions are logged with timestamps inserted via a slash command that generates a 24-hour “current time” entry. By adding time ranges and then linking back to the relevant interview notes, the user can quickly estimate how long each conversation or research session took. While the current setup is described as manual, the roadmap includes richer time-tracking features such as aggregating “time” entries, filtering them, and generating charts.

Task management follows a GTD-style inbox approach. A “make to do” action converts a bullet into a checkbox task while also creating a linked “to do” page. That page can be filtered to hide scheduled items (pushing them into “scheduled” or “someday” lists) so the inbox only shows unscheduled work. Scheduling is handled through slash commands and a date picker, and tasks automatically appear on the correct daily pages once scheduled. The demo emphasizes that tasks can be removed from the inbox view simply by applying or adjusting filters, supporting both “do it now” triage and later review.

Roam’s task system also connects directly to email work. When the user drafts strategically important emails—such as investor or client communications—they often write the content inside Roam, then paste it into an email client (Superhuman is mentioned). Roam supports copying either plain text or “block references,” which paste with a footnote-style trail showing where the content was used before. This lets the user reuse stable facts (like routing numbers or account numbers) without hunting through documents, aiming for “autocomplete away” retrieval.

For larger planning, the demo highlights dependency graphing and reverse dependency thinking: starting from the next action or “next step” and working backward to identify prerequisites and time constraints. Daily habits and project plans can be represented as linked structures, with starred shortcuts for quick access. Another planning mode uses recursive knowledge graphs for curriculum-like structures, where completing one module unlocks paths to subsequent modules, and progress can be tracked per learner.

Finally, the demo positions Roam as a flexible alternative to Evernote/OneNote-style organization. Because Roam is a web app, it’s less likely to be blocked by firewall policies, and it supports overlapping taxonomies—like viewing only the tasks relevant to “email” when in that context—something the demo claims is harder in file-based tools like Excel or OneNote. Pricing is mentioned as $14 per month, and the system is framed as growing with the user from simple outlining to advanced querying and calculations.

Cornell Notes

Roam is demonstrated as a unified system where indented notes become tasks, time logs, and email-ready drafts through linking and filtering. The workflow uses slash commands to insert 24-hour timestamps for attention management, then aggregates time by linking ranges back to specific user interviews. Tasks are created from bullets (“make to do”), appear on linked to-do pages, and are filtered so the inbox stays focused on unscheduled work while scheduled items move to date-based views. For writing important emails, content is drafted in Roam and pasted into Superhuman, with “block references” preserving provenance and reuse. For big projects, dependency graphs are built by starting at the next action and working backward to identify prerequisites and time constraints.

How does Roam support attention management and time tracking in the demo?

The user logs time during work sessions by using a slash command to insert “current time” as a 24-hour timestamp. Later, they can add time ranges (e.g., from one point to another) and link those ranges back to the specific user interview notes. This creates a quick way to estimate how much time was spent per interview, with future plans mentioned for more automated aggregation, filtering, and charting (e.g., using a “time” query to pull and summarize tracked entries).

What does the GTD-style inbox workflow look like, and how does filtering keep it manageable?

Tasks are created from bullets using a “make to do” action, which turns the bullet into a checkbox and also generates a linked to-do page. That to-do page applies filters to hide tasks that are already scheduled or placed on a “someday” list, keeping the inbox focused on unscheduled items. Scheduling uses slash commands and a date picker; once scheduled, tasks appear on the corresponding daily pages and are removed from the inbox view automatically via the filter logic. The demo also shows shifting filter settings to “remove” scheduled tasks from the inbox when aiming for inbox zero.

How does Roam connect tasks and context—especially for email—without forcing a single folder structure?

Tasks can be tagged or linked so they can be filtered by context. When the user is in an email-writing context, they can view only the to-dos related to email, rather than scanning an all-tasks list. The demo illustrates this by using email-related tags/links and showing prerequisite tasks (e.g., converting investment docs to PDF) that must be completed before sending a specific email. This overlapping taxonomy is presented as a key advantage over file-based organization.

Why draft important emails inside Roam, and what is the role of block references?

For strategically important emails (investors/clients), the user drafts language inside Roam to ensure accuracy and reuse of stable information like routing numbers and account numbers. When pasting into Superhuman, Roam can paste plain text or “block references.” Using block references adds a footnote-like trail that indicates where the content was used previously, helping the user track and reuse information without re-searching documents.

How does dependency graphing work for large projects in this workflow?

The approach is described as reverse dependency graphing: start from the next action (or next step) and work backward to identify prerequisites. The demo connects this to time constraints and deep-work scheduling, where tasks can be assigned to specific “storm” and “out of storm” time windows (Cal Newport is referenced). It also shows how daily habits and project steps can be represented as linked structures, with shortcuts (like a starred daily habits view) for quick access.

What planning example demonstrates Roam’s recursive knowledge graph capability?

A curriculum design example shows modules unlocking subsequent learning paths. After completing “1.1,” the learner can move to “1.1.a,” and the structure can be recursive—where components of “1.1.a” become their own linked subsets. The demo also notes that progress can be tracked per student and that tables can be generated to summarize learning paths, though the explanation moves quickly.

Review Questions

How does the demo’s timestamp insertion method enable later time aggregation by interview or session?
What mechanisms keep the inbox focused on unscheduled tasks, and how do scheduled tasks reappear on the correct daily pages?
In what ways do block references improve reuse and traceability when drafting emails in Roam?

Key Points

1
Roam’s slash commands can insert 24-hour “current time” timestamps, enabling manual time tracking that links back to specific work sessions.
2
Tasks created from bullets (“make to do”) automatically generate linked to-do pages, and filters keep the inbox focused on unscheduled items.
3
Scheduling uses slash commands and a date picker so tasks appear on the correct daily pages while disappearing from the unscheduled inbox view.
4
Email drafting can be done inside Roam and pasted into Superhuman, with “block references” preserving provenance and reuse trails.
5
Context-based filtering lets users view only the tasks relevant to a domain (like email) instead of scanning a single master list.
6
Large projects can be mapped with reverse dependency graphing by starting from the next action and working backward to prerequisites and time constraints.
7
Roam is positioned as a flexible alternative to Evernote/OneNote-style organization because it supports overlapping taxonomies and is a web app less likely to be blocked by firewalls.

Highlights

Roam is used as both a time tracker and a knowledge base: timestamps are inserted during sessions, then time ranges link back to the exact interview notes.

The inbox workflow relies on linked to-do pages plus filters that hide scheduled items, keeping unscheduled work front and center.

For investor/client emails, drafting in Roam supports reuse of stable facts and optional “block references” that show where content was previously used.

Dependency graphing is framed as reverse planning: start from the next action and work backward to prerequisites and scheduling constraints.

Roam’s overlapping context filters (like “email-only” tasks) are presented as a key advantage over file-based tools.

Topics

Roam Workflow
Attention Management
GTD Tasks
Email Drafting
Dependency Graphs

The Cannonical Roam Demo - complete version - December 20, 2019