Threadably

Turn a long discussion thread into a decision newcomers can trust

A five-field note that preserves the difference between a proposal and an agreement.

By Ashley Kays Rabbitt · November 18, 2026

A team discussion begins with a request to move a launch. Someone proposes Thursday. Another person asks whether customer support will be ready. The last message is a thumbs-up. An AI summary says, “Launch moved to Thursday.” It reads well and quietly settles a question the team left open.

Build the decision note from five fields: proposed change, named decision-maker, evidence of approval, effective date, and unresolved dependencies. A blank field is a legitimate result. If the team never named an approver, write “approval unclear” and preserve a link to the relevant part of the discussion.

Turn a thread into a decision
ProposalThursday was suggested
DependencySupport readiness is open
DecisionNamed owner confirms the date

Reconstruct the decision from two viewpoints

For a fictional thread, have one colleague write a summary and another challenge every sentence using only the original messages. “Thursday was proposed” survives inspection. “Customer support agreed” requires a message from the relevant person. If the thumbs-up might mean either “saw this” or “approved,” ask the owner for a single clarifying reply.

Granola’s account of transcript retrieval offers a parallel lesson: summaries can omit the detailed words a downstream decision depends on. Make it easy to recover those words in a thread, too. Granola • Why agents missed transcript evidence

Once an owner confirms the date, add the confirmation to the record with its time. Leave the earlier proposal and concern intact. A teammate joining next week can now see what changed, who decided it and what remains open, without treating the entire discussion as a binding decision.