TattvaDocs
Workflows

Track a decision

Get a decision into Tattva, review it, watch its assumptions, and record how it turned out.

Tattva records decisions from your documents and analyses rather than from a form. This workflow takes one decision from a written note to a measured outcome. For what a decision holds, see Decisions.

Write the decision down

Decisions come from documents, so start with one. Meeting notes, a strategy memo or an RCA write-up works. For each decision, write:

  • what you decided, in one sentence;
  • why, and what you rejected;
  • what you expect to happen, and by when;
  • the assumptions that would prove it wrong, and the metrics that would show it.
Decision: Move 30% of Q3 paid social spend to search.
Why: Search CAC has been 20% lower for three months.
Rejected: Cutting spend overall; testing a new channel first.
Expected: Blended CAC below 650 within 60 days.
Assumption: Search CAC stays below 600 at the higher spend.
Invalidates if: Search CAC goes above 600 for two weeks.
Watch: blended CAC, search CAC.

Save it as a .md or .txt file.

Upload it

Sources → Upload → Upload more, and pick the file. When it is Ready, Tattva has pulled out the decisions it found. Open debates that are not commitments yet become Discussions instead.

Review it in the ontology

Open Ontology → Make → Data and choose the Decisions sub-tab. Expand the decision and check:

  • Rationale and Expected outcome;
  • Alternatives considered;
  • Assumptions, each with its "Invalidates if:" condition;
  • Evidence: the passage it came from.

If it is not really a commitment, click Convert to discussion →. If it should not be tracked at all, Remove as decision. If a discussion on the Discussions sub-tab has become a real call, click Convert to decision →.

Watch the metrics with a tracker

Create a tracker for the metric that tells you whether the decision is working. Ask the question in Reasoning ("How is blended CAC moving week over week?") and click Save as tracker, then add a rule. If the decision serves a goal, link the tracker to that goal with the right role. See Trackers and Goals.

Trackers with RCA or forecast questions also record their findings as proposed decisions, with the top cause, the recommended actions and the assumptions to watch.

Read the decision page

Open the decisions list: type /decisions after your Tattva address. While the project has no reports, Browse decisions → on the Reports page also opens it. Click the decision.

Decisions list

The decision page has three tabs:

  • Summarised: the top cause, the Implementation Sequence of actions, and the Key Assumptions.
  • Deep dive: the Evidence and the Hypotheses to Watch.
  • Trail: the inputs at decision time, including the ontology version and how fresh the data was.

Decision page

Capture the outcome

When the horizon arrives, or whenever you want a reading, go back to Ontology → Make → Data → Decisions, expand the decision and click Capture outcome. Tattva measures the watched metrics against their targets and records a verdict: on track, at risk, off track, invalidated or confirmed. Each capture is added to the decision's outcomes and to the Outcome Ledger on the decisions list.

Why this pays off

  • You can defend the call later. The decision, its evidence and its assumptions are in one place, as they were at the time.
  • You learn which calls work. The Outcome Ledger compares what you expected with what happened.
  • Your team sees its own habits. Decision Signs reads the decision history.

Tips

  • Write assumptions you can measure. "Search CAC stays below 600" can be checked; "search keeps working" cannot.
  • Name the metrics to watch. Capture outcome can only measure what the decision says to watch.
  • Record decisions when you make them. A decision written down months later tends to remember the reasoning more kindly than it was.
Track a decision — Tattva Docs