How to track executive decisions in Tana

TL;DR

• Executive decisions fail differently than tasks: the decision gets made in the room, and six weeks later nobody can say exactly what was decided, why, or what happened next, so the same question gets debated again.
• Tracking a decision means capturing it as a distinct item the moment it is made, keeping the rationale attached, turning the follow-ups into owned work, and keeping decision, discussion, and follow-up connected for recall.
• Tana does that during the meeting: the Capture control turns the discussion into a typed Decision, extraction proposes the follow-ups assigned to the right person, and every change arrives as a proposal you approve.
• Afterwards you ask chat "what did we decide on pricing this quarter" or "why did we choose this vendor" and get an answer grounded in what was actually said, with the receipts attached.

Executive meetings produce two things: decisions and follow-ups, and both evaporate faster than anyone admits. The task half is covered in How to keep meeting action items from getting lost; this guide is about the harder half, the decisions. For the whole executive meeting cycle in Tana, prep to follow-through, see How to manage executive meetings in Tana. Tana tracks decisions with the same primitives it uses for any meeting, no separate executive mode, and that is the point: the mechanics below work for a weekly leadership sync and a board meeting alike.

Why decisions need different tracking than tasks

A task closes when the work is done. A decision never closes; it lives on as a constraint on future work, and its value depends on two things a task never needs: the rationale, so it does not get relitigated when the context resurfaces, and the connection to its consequences, so you can tell whether it worked. Meeting notes capture neither reliably. "Decided to move upmarket" in a summary doc records the outcome and loses the reasoning, the dissent, and the conditions for revisiting. That is why teams with good notes still reopen settled questions: the record says what, and the argument was about why.

How to track executive decisions, step by step

The method works in any tool. Under each step is how Tana does it for you.

Step 1: give decisions a shape, not a bullet point

A decision buried in prose is untrackable. Give it a defined shape: the decision itself, the rationale, who made it, and a status, so every decision can be listed, filtered, and revisited. In Tana you ask chat in plain language to create a Decision type with exactly those fields and a workflow for its states. Describe it once, and every captured decision carries the same structure.

Step 2: capture the decision in the meeting, as it happens

The worst time to identify decisions is afterwards, from memory or a transcript. In a Tana meeting the Capture control turns the last stretch of discussion into a typed item on the spot, a Decision included, without anyone stopping to dictate. This works whether the meeting runs in Tana or on Zoom, Teams, or Meet: the desktop app captures external calls in the background, with no bot joining, which matters in executive conversations where an extra participant changes the tone. If nobody captured it live, extraction after the call surfaces the decisions anyway, as proposals you review.

Step 3: keep the rationale attached to the decision

The rationale is what stops relitigation, and it is the first thing lost when someone writes up minutes afterwards. Because a Tana decision is captured from the conversation itself, it stays connected to the discussion that produced it: the options weighed, the objection raised, the condition for revisiting. When the decision resurfaces in six months, "why did we do it this way" has an attached answer, not one reconstructed from whoever remembers the meeting.

Step 4: turn the follow-ups into owned work you approve

Most executive decisions imply work: tell the team, update the plan, renegotiate the contract. When the call ends, Tana's extraction produces the action items assigned to the person the conversation pointed at, and files work into the trackers your team already runs on, including Linear, Jira, GitHub, Slack, and HubSpot, with more reachable through its MCP server. Nothing is written anywhere without review: every follow-up arrives as a proposal, so the leadership team keeps a human check on what leaves the room.

Step 5: update the record the decision affects

A decision about the Q3 strategy belongs in the Q3 strategy record, not in a meeting summary that competes with it. Pin the relevant doc or product track to the meeting, and Tana's extraction updates that record instead of creating a parallel one. Recurring executive meetings are where this compounds: extraction updates the existing outcomes and de-duplicates rather than spawning a new summary per call, so a quarter of leadership meetings leaves one current strategy record with its decision history, not thirteen overlapping write-ups.

Step 6: make the decisions recallable, with receipts

The test of decision tracking is recall under pressure: preparing for a board meeting, onboarding a new executive, or settling "did we actually agree to that". Because the decisions, discussions, and follow-ups stay connected, you can ask Tana's chat "what did we decide this week" or "why did we deprioritize the enterprise tier" and get an answer grounded in what was actually recorded, with receipts pointing back to the source. That is the difference between an answer you can put in front of the board and one you have to double-check first.

What this looks like in Tana

A concrete scene: the monthly leadership meeting, run on Meet, captured by Tana with no bot on the call. Mid-discussion, the team lands on raising the enterprise price. Someone hits Capture, and that stretch of conversation becomes a Decision with the rationale filled from what was said. The Q3 pricing doc was pinned to the meeting, so extraction updates that doc rather than writing a new summary, and proposes the follow-ups: the CFO owns the revised model, a task lands in the revenue team's tracker, the announcement draft goes to Slack. You skim the proposals and approve. Before the next board meeting, a scheduled agent leaves a prep doc built from the connected context, so the decision, its rationale, and what happened since arrive together. When a board member asks why the price moved, the answer comes from the record, not from memory. Same primitives as any Tana meeting, applied where stakes are highest.

Where a general notetaker fits

A notetaker or a general chatbot handles the floor of this problem well. If what you need is a record of what was said, a transcript and an AI summary deliver it, and most notetakers will list the decisions they detect. Where they stop is connection. Each meeting becomes its own summary doc: the decision sits apart from the record it affects, the rationale is compressed to a line, the follow-ups are a list someone still turns into owned work themselves, and recall means searching last quarter's summaries and hoping the phrasing matches. For executive meeting management the connection is the product: a decision is only tracked if the why, the consequences, and the current state travel with it. That is the layer Tana adds, decisions as typed items connected to their discussion and follow-ups, updated in the records they affect, and recallable through chat with receipts.

Frequently asked questions

How do you track decisions made in executive meetings?

Capture each decision as a structured item at the moment it is made, keep the rationale attached, assign the follow-ups to named owners, and connect the decision to the record it affects. Tana does this during the meeting itself: the Capture control turns the discussion into a typed Decision, extraction proposes follow-ups assigned to the person the conversation pointed at, and everything arrives as a proposal you approve before it is written anywhere.

How do you record the rationale behind a decision, not just the decision?

Capture the decision from the conversation rather than writing it up afterwards, because the rationale lives in the discussion and dies in the minutes. In Tana a captured Decision stays connected to the conversation that produced it, and you can define a Decision type with an explicit rationale field, so "why did we decide this" has an answer attached to the decision itself.

How do you find out what was decided in past meetings?

If decisions live in scattered summary docs, you search and hope. If they are tracked as connected items, you ask. In Tana you ask chat "what did we decide about the vendor contract" or "what did the board decide on hiring" and get an answer grounded in what was actually recorded, with receipts pointing to the source, reliable enough to prepare a board update from.

How is decision tracking different from action item tracking?

An action item closes when the work is done; a decision never closes, it constrains future work, so it needs its rationale and consequences kept attached, not a done state. The two are linked in practice, since most decisions produce action items. Tana captures both from the same meeting, decisions as typed items and follow-ups as assigned tasks filed where the work happens, connected to each other. For the action item half, see How to keep meeting action items from getting lost.

Can AI track decisions and follow-ups from board meetings automatically?

Yes, with the same mechanics as any other meeting, which is what you want: board meetings do not need a special mode, they need the standard chain to be trustworthy. Tana captures the meeting without a bot joining, extracts the decisions and follow-ups, assigns them, and files the work, and every change is a proposal a person approves before it lands. That review step is what makes automation acceptable in a boardroom context.

How do you prepare for a board meeting using past decisions?

Preparation is mostly recall: what was decided last time, why, and what happened since. In Tana a scheduled agent can brief you before the meeting with a prep doc drawn from the connected context, and you can ask chat directly for the decisions on any topic with receipts, so you walk in with the decision history rather than reconstructing it the night before. The broader meeting workflow is covered in How to manage executive meetings in Tana.