Get AI summaries of any video or article — Sign up free
A NEW approach to TASK MANAGEMENT | Interstitial journaling in Tana thumbnail

A NEW approach to TASK MANAGEMENT | Interstitial journaling in Tana

Tomi Nuottamo·
5 min read

Based on Tomi Nuottamo's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Create super tags for #task and #meeting notes so tasks and meeting content can be queried and surfaced consistently.

Briefing

Interstitial journaling in Tana is presented as a way to turn an overwhelming, static task list into a living “flow of the day”—with timestamps, lightweight check-ins, and notes that get captured exactly when they happen. The payoff is practical: a clear plan for what to do and when, plus a running record of decisions, meetings, and task outcomes that reduces stress from a never-ending backlog.

The setup starts by creating a daily template driven by two “super tags”: one for tasks and one for meeting notes. Using Tana’s command prompt, the creator converts tags into super tags (e.g., #task and #meeting notes), then configures a “day” tag that generates the daily note template. Inside that daily template, a query pulls in all nodes tagged as tasks that are not yet done, so unfinished work automatically appears at the top of the day. A second field—called a “Time log”—is added as the place to write timestamped journal entries and notes.

The daily workflow begins with a morning check-in. A timestamp is inserted via the command prompt (e.g., typing “time” to capture the current moment), followed by a quick, free-form reflection such as how the day is starting (“feeling rested,” “great night’s sleep”). The method deliberately keeps these reflections out of the structured daily template so the thinking stays flexible; the template is for capturing the day’s tasks and key notes, while the journal entries can be placed wherever they fit.

Tasks are then scheduled as part of the day’s narrative. The creator breaks the plan into segments like “morning” and “afternoon,” adding time markers (for example, “8 am working out” and “9:30 focus time”). During focus blocks, tasks can be written as nodes, including longer work items like “write a few paragraphs,” and tasks can be structured with checkboxes by configuring the #task super tag to require a completion toggle. As the day progresses, meetings and outcomes are captured in-line: a timestamped entry can be tagged as #meeting notes, and meeting details can be opened alongside the day’s flow.

A key feature is that tasks created throughout the day automatically roll up into the query node that lists unfinished tasks. That means the daily page becomes both a timeline of what happened and a control panel for what still needs doing.

At the end of the day, the shutdown routine—borrowed from Cal Newport—is used to close the loop. A new #shutdown hashtag is created, timestamped, and filled with reflections on what went well, what could improve, and how to prepare for the next day. Because each shutdown is tagged, weekly review becomes possible by aggregating all shutdown entries. Finally, planning tomorrow is done by creating tasks for the next day and copying relevant nodes, so tomorrow’s list is grounded in what actually emerged today.

Overall, interstitial journaling reframes task management as continuous capture and scheduling within a day’s thought flow—prioritizing progress over perfection and offering a simple starting point that can be made more complex over time.

Cornell Notes

Interstitial journaling in Tana replaces a static task list with a day-by-day “flow” of timestamps, notes, and tasks. The setup uses super tags for #task and #meeting notes, plus a configured day template that automatically queries unfinished tasks into a single daily view. A “Time log” field stores timestamped check-ins, meeting notes, and in-the-moment updates, while tasks are scheduled into morning/afternoon blocks to keep planning flexible. At day’s end, a #shutdown routine (inspired by Cal Newport) captures reflections and sets up weekly review. The result is less stress from backlog lists and better continuity between planning, execution, and reflection.

How does the Tana setup ensure unfinished tasks show up automatically each day?

It creates a daily template under a configured “day” tag that includes a query node. That query pulls in nodes tagged with #task that are “not yet done,” so any task created during the day (tagged as #task and marked incomplete) automatically appears in the daily page’s unfinished-task list.

Why keep check-ins and reflections out of the structured template?

The workflow keeps the morning check-in and other free-form thoughts in the “Time log” rather than forcing them into the template. The stated reason is to preserve a freer thinking flow—without restricting how mornings unfold—while still capturing timestamps for later reflection.

What does “interstitial journaling” mean operationally in this method?

It means inserting tasks and notes throughout the day as they occur, using the day’s narrative timeline. Timestamped entries can capture breaks, meeting outcomes, and task follow-ups, and those notes can be linked or opened in-line. Tasks created in this flow are then collected back into the daily unfinished-task query.

How are meeting notes handled so they stay connected to the day’s plan?

Meeting moments get timestamped and tagged with #meeting notes. Notes can be written under that meeting tag, and the method supports quick access via side panels or inline opening (e.g., shift-clicking the link). This keeps meeting context attached to the same daily timeline where tasks are being scheduled.

What is the shutdown routine used for, and how does it support weekly review?

At the end of the day, a #shutdown hashtag is created with a timestamp and filled with reflections: what went well, what needs improvement, and how to prepare for the next day. Because each shutdown entry is tagged, all shutdowns from a week can later be aggregated into a review, enabling pattern spotting across days.

How does the method turn today’s work into tomorrow’s plan?

After completing #shutdown reflections, the creator plans tomorrow by creating tasks for the next day (e.g., “walk dog”) and copying relevant nodes as needed. This produces a task list for tomorrow that’s grounded in what was captured and learned today.

Review Questions

  1. What components (tags, template fields, and queries) are required so unfinished #task items appear automatically on the daily page?
  2. How does the method balance structured planning (morning/afternoon blocks) with free-form journaling (Time log) to reduce stress?
  3. Describe how #shutdown entries enable both end-of-day reflection and later weekly review.

Key Points

  1. 1

    Create super tags for #task and #meeting notes so tasks and meeting content can be queried and surfaced consistently.

  2. 2

    Configure a day template that includes a query for #task items that are not yet done, so the unfinished list updates automatically.

  3. 3

    Add a “Time log” field to capture timestamped check-ins, break notes, and meeting outcomes in the order they happen.

  4. 4

    Schedule tasks into morning/afternoon blocks with time markers, using the #task super tag to enable completion checkboxes.

  5. 5

    Use timestamped #meeting notes to keep meeting context connected to the day’s timeline and task roll-up.

  6. 6

    Close each day with a timestamped #shutdown reflection (what went well, what to improve, how to prepare), enabling weekly aggregation later.

  7. 7

    Plan the next day by creating tasks (and copying relevant nodes) based on what emerged during today’s flow.

Highlights

The daily template uses a query to automatically collect unfinished #task nodes into one place, eliminating the need to manually maintain a backlog.
Interstitial journaling treats the day like a timeline: timestamps and notes are inserted as events happen, while tasks created in that flow roll back into the unfinished list.
A #shutdown hashtag turns end-of-day reflection into a structured dataset that can be reviewed weekly.
The method intentionally keeps check-ins free-form to protect thinking flexibility, even while tasks remain structured and trackable.

Mentioned