Get AI summaries of any video or article — Sign up free
Tana Tour with Andrea Grimsdatter Stallvik: Simple Student Workflows thumbnail

Tana Tour with Andrea Grimsdatter Stallvik: Simple Student Workflows

Robert Haisfield·
5 min read

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

TL;DR

Tana works best for this workflow when notes are captured quickly during class or lab work and only lightly tagged for later retrieval.

Briefing

A biotechnology master’s student credits Tana with replacing a messy sprawl of notes across Google Docs, OneNote, and paper—turning scattered lectures, textbook reading, tasks, and meeting records into a single, searchable system. The biggest payoff isn’t fancy organization; it’s speed. Notes get captured during class or lab work, then tagged just enough to retrieve the right things later, including “questions I need to ask” and “read more” items.

Before Tana, the student relied heavily on Google Docs for intensive group-lab work. Each morning’s brainstorming produced new documents, and the result was a pile of “Untitled” files with no reliable way to extract the useful figures and decisions afterward. That frustration pushed an afternoon of learning Tana’s structure and tags—after which the system immediately felt more usable than juggling many separate documents. The same problem showed up in other formats too: handwritten notes in math were hard to find later, and Word/Docs files for different sessions created fragmentation without a clean way to bring everything together.

In Tana, the student organizes around a “today” node for active work, then builds class-specific decks and collections under it. During lectures, notes land in the relevant lecture node, while questions get tagged as they arise. A live search then pulls all tagged questions from within a specific lecture subtree, producing a condensed checklist for breaks or end-of-class follow-ups. The student also uses tags like “read more” to capture curiosity that doesn’t fit the moment—sometimes tied to overlapping topics across courses.

Task tracking follows the same efficiency-first philosophy. Instead of maintaining separate task apps, tasks are written directly during lectures as they come up, with a lightweight requirement to assign each task to a project. For study and thesis work, tags also act as retrieval hooks: papers get tagged so their abstracts and notes stay structured, and reading plans or chapter notes get grouped for exam revision.

Beyond academics, Tana supports extracurricular workflows, especially recurring meetings. A “meeting” tag organizes rigidly structured weekly sessions, with notes under agenda/outcome points and practical details like who to email, when, and what response was needed. After meetings, the student exports meeting information into HTML to paste into emails—turning Tana’s notes into actionable communication.

The student deliberately avoids over-structuring. They don’t want to spend lecture time filling out many fields, and they question whether linking people and references is worth the effort versus the payoff. Inline references are used more in writing and research than in everyday note capture, and unlinked mentions are acknowledged as an untapped feature. Overall, the system’s value comes from low friction—capturing thoughts quickly—paired with just enough tagging to make later retrieval effortless. The advice to new users is to start simple: use a small set of tags that support searches, then expand only if it genuinely saves time.

Cornell Notes

A biotechnology master’s student uses Tana as a single workspace for lectures, textbook reading, tasks, and meeting notes. The core method is fast capture plus lightweight tagging so information can be retrieved later—especially via live searches that aggregate tagged items like “question” notes under a specific lecture. Instead of spending time on heavy templates or exhaustive metadata, the student keeps structure minimal during class and relies on tags to create efficient pathways for review, exam prep, and thesis reading. The approach extends to extracurricular work, where recurring meetings are organized with tags and exported into emails. The system matters because it prevents the fragmentation that happened with many separate Google Docs, Word files, or handwritten notes.

What problem pushed the student to switch from Google Docs and OneNote to Tana?

During an intensive student project, each morning’s lab brainstorming generated new Google Docs that quickly multiplied into many “Untitled” files. Useful figures and decisions were hard to extract later, creating a retrieval problem. That experience motivated an afternoon to learn Tana’s structure and tagging, after which notes became easier to consolidate and search compared with scattered documents.

How does the student turn lecture notes into something actionable during breaks?

Notes from a class go into a specific lecture node under the student’s “today” area. When a question appears mid-lecture, it’s written down and tagged as a “question.” A live search then finds nodes tagged as “question” within that lecture subtree, producing a condensed list of follow-ups to ask during breaks or at the end of class.

What does “read more” tagging do in the student’s workflow?

When something comes up that the student wants to investigate later—often because it connects to a project or another course—they tag it as something to read more on. Later, during revision for exams, live searches surface these items so the student can revisit unresolved threads without hunting through unrelated notes.

How is task tracking handled without separate task software?

Tasks are captured directly during lectures on the “today” node as they arise. Each task is assigned to a project, and live searches are set up across the tree to surface tasks by context. The student emphasizes speed and “no information disappearing,” contrasting it with earlier workflows that required more work to keep tasks and notes aligned.

How does Tana support extracurricular meeting workflows?

A “meeting” tag organizes weekly sessions with a rigid agenda/outcome structure. Notes include who to contact, what to send, and timing details. After meetings, the student exports the relevant information into HTML and pastes it into emails, using Tana as the source of truth for follow-up communication.

Where does the student draw the line on organization—especially around references and linking people?

The student avoids heavy linking of people and inline references in everyday notes, arguing that it can drift into “organization for organization’s sake.” They see potential benefits (like answering questions tied to who attended), but they prioritize quick capture and retrieval over exhaustive relationship mapping. Inline references are used more when writing research drafts and tracking paper-related notes.

Review Questions

  1. What specific tagging strategy lets the student generate a “questions to ask” list for a lecture without manually sorting notes afterward?
  2. How does the student’s approach to tasks differ from using separate task apps, and what efficiency goal drives that choice?
  3. Why does the student avoid linking every person or building complex templates during note-taking, and what trade-off are they trying to manage?

Key Points

  1. 1

    Tana works best for this workflow when notes are captured quickly during class or lab work and only lightly tagged for later retrieval.

  2. 2

    Live searches are used to aggregate tagged items (like lecture “question” notes) within a specific subtree, turning raw notes into a short checklist.

  3. 3

    A “today” node acts as the active landing zone for lecture notes, reading notes, and tasks, reducing the need to manage many separate documents.

  4. 4

    Task capture is integrated into note-taking: tasks are written when they appear and assigned to a project, with searches used to surface them later.

  5. 5

    Extracurricular meetings are organized with tags and structured notes, then exported into email-ready formats (HTML) for follow-up.

  6. 6

    The student intentionally limits metadata and reference-linking during capture to avoid slowing down attention in lectures.

  7. 7

    Advice for new users: start with a small set of tags that support searches, then add complexity only when it clearly saves time.

Highlights

The student’s “question” tag plus a live search creates an automatic end-of-lecture list of follow-ups, without manual sorting.
Switching from many Google Docs to a single tagged structure solved the “Untitled document” problem and made retrieval practical.
Meeting notes aren’t just archived; they’re exported into HTML and pasted into emails to execute follow-up work.
The student’s guiding principle is low friction: capture first, structure later only as needed.
They avoid exhaustive linking of people and references because it risks turning organization into busywork.

Topics

Mentioned