Ten small tasks are finished, but the one demanding priority is still waiting. A summary that counts completions could call that a productive morning. Another morning spent on one difficult deliverable might look quiet by the same measure. Your AI review needs a way to tell those stories apart.
Retrospective coverage: Tina Huang published this tutorial on August 29, 2026. Newsroom is publishing this commissioned assessment on September 4, 2026, and no new release is implied.
Begin with one question, a few source notes and a review that can change the next action. Keep what happened separate from what the assistant infers. A score becomes useful when you can follow it back to the work and decide whether it describes progress you actually value.
In her August 29, 2026 tutorial, 10X Productivity in 10 Minutes , Tina Huang presents a personal workflow using Hermes and Obsidian. Obsidian holds the notes. The useful method to borrow is the feedback loop, with the source records still available when a summary needs correction.
The retained chapter sequence begins with “Daily Productivity Workflow,” then moves into the mechanics, a snag, a Granola segment and an attempt to improve the system. A snag is a useful part of the account. It gives the workflow a reason to be adjusted after it meets ordinary use.
The title’s 10X promise needs a baseline, outcome and observation period before it can become a result someone else expects. This tutorial is a personal example. The exercise here asks a narrower question: can a small record help you make one better-informed decision about your next block of work?
Give each note a question to answer
Choose a question your notes could answer. Perhaps the first priority keeps slipping past lunch, or interruptions keep breaking a planned work block. A specific concern gives each field a reason to exist and gives the next review a choice to make.
A daily entry might record the priority, start time, significant interruptions, an energy rating and whether the task reached its intended stopping point. That is a proposed small template, not a reconstruction of Huang’s private notes. Keep a field only when its answer can affect a decision.
This borrows from self-tracking while leaving the original observations available. If an assistant connects meetings or task switching with lost focus, inspect the relevant entries. They may support a useful pattern, reveal missing context or suggest the interpretation needs changing.
Make the practice small enough for an ordinary week. A short template completed consistently can tell you more than an elaborate system abandoned after a few days. Logging needs a cost too. Time spent maintaining the record is time the method is meant to help you use.
Leave room to disagree with the summary
The first disagreement is informative. An assistant may label a morning “low focus” because few tasks were completed. The note may show that one demanding task occupied the whole session. Keeping the original account lets you correct the label without rewriting the event.
Give the review three distinct records:
- The original observation, such as a task, time entry, meeting note or interruption.
- The interpretation produced by the AI system.
- The correction or action chosen by the user.
Those layers preserve where an explanation came from. A suggestion can stay tentative until you choose to try it. A correction can record what the assistant missed. Later summaries then have a clearer account to work with, rather than a growing pile of earlier interpretations treated as facts.
The same principle supports personal knowledge management . Notes retain more value when their source and context survive later summarization. An assistant can identify recurring language, assemble a weekly review or propose a connection, while the original entries remain available for inspection.
A correction is useful even when no automatic learning follows. Record the rule for the next review: a long deliverable should not be judged by the number of boxes checked. That makes the preference visible to you and to any later assistant using the notes.
Count the work you meant to finish
Task count can reward the work that is easiest to finish. Choose a measure that also represents the priority. A completed block of demanding work, a planned outcome reached or a deliverable accepted may answer a different question from the number of actions recorded.
Suppose a hypothetical baseline week has five planned priority blocks and three completed ones. After moving routine messages outside those blocks, another week has five planned and four completed. Completion rises from 60 percent to 80 percent, a 20 percentage-point change. Task difficulty and available time may also differ, so this comparison does not isolate AI as the cause.
Ask the assistant to name the entries behind its explanation, then inspect the work definitions and interruptions. Daily records can help adjust tomorrow. Weekly patterns can reveal recurring overload. A longer observation period gives you more chance to see whether a change survives beyond its initial appeal.
Keep the change that affects a useful decision and remove a field that never does. Our Instaply case study follows a related distinction between a generated suggestion and confirmed completion. A proposed action in a summary still needs its own outcome in the record.
Follow the note beyond its local folder
Obsidian stores notes locally as plain-text Markdown files by default. That gives you access to the vault, but a connected plugin, meeting assistant or remote model may send selected content elsewhere. Trace the actual route of the notes before deciding where sensitive entries belong.
A productivity log can contain confidential work, colleagues’ names or candid personal observations. Check what each connected service transmits, stores and retains, along with its training, deletion and export terms. Local storage in one application answers only one part of that comparison.
The question may need less detail than the full record contains. Interruption count and duration can reveal a pattern without copying the content of every message. Meeting timing may be enough without a transcript. A smaller input can protect private context and leave the review with fewer irrelevant details to interpret.
Read the recommendation beside the relationship
Huang’s retained public description promotes Granola, includes a Granola chapter and contains affiliate links. Keep that commercial context beside product recommendations. The tutorial’s personal workflow can still offer a useful idea, with its practical value tested against your own defined work.
Read the multiplier as a claim that needs its measurement conditions. Borrow the inspectable loop as a method to try. The small two-week example above gives a comparison you can calculate while leaving its causes open to investigation.
Our related analysis of managerial judgment and accountability adds an organisational dimension. There, the question is whether the person responsible can still explain a decision. Here, the same standard applies at an individual scale: can the user trace a recommendation back to the notes, identify the inference and explain why the next action follows?
The demanding task can now have a place in the review even if it occupied the entire morning. Its source note says what happened. The interpretation can be challenged. The next action remains yours to choose. That is enough structure to keep one useful priority from disappearing inside a fuller list.
