pingpong

Work coordination

Write a decision log entry from agreed facts

A decision log is only useful if it records what happened, not a tidy version of it. Give the assistant the decision, the date, who made it, which options were on the table, and the conditions for revisiting it.

A text to start with

On [date], the team decided to [decision]. The options we considered were [option A] and [option B]. We chose [option A] because [reason]. The decision owner is [name]. We agreed to revisit if [condition]. Draft a decision log entry using only these facts. Do not add context or rationale I have not provided.

Example request. Change the details to fit your situation.

What to check before saving the entry

Compare the entry with your notes and confirm that nothing was added beyond your prompt. A log that smooths over disagreement or invents a cleaner rationale will mislead whoever reads it later. If an alternative that was actually considered is missing, add it to your prompt and regenerate, even if it was rejected quickly. The revisit trigger should be a condition someone can check, such as a metric or an event, rather than a date chosen without reason.

Storing and sharing the log

Save the entry wherever your team keeps decisions, and ask the decision owner to confirm it before it circulates. If the decision affects people outside the immediate team, send them a one-sentence summary with a link to the full entry.