Find explicit decisions
Give Nema the Slack thread, meeting notes, or other approved discussion that contains the choice. Identify the project and expected decision owner. Ask it to treat proposals, preferences, and reactions as discussion unless the record clearly shows a conclusion.
A row of approval emojis may have meaning in one team's process and none in another. Supply the convention before asking Nema to interpret it.
Record enough context
A useful decision entry names the choice, date, owner, scope, rationale, affected work, and source link. It can list alternatives when they explain why the team chose this path. It should not reproduce the whole debate.
Scope protects readers from overapplying the choice. A decision for one launch, customer, or quarter may not establish a general rule.
Keep unresolved proposals visible
When the thread contains strong opinions but no final answer, Nema should draft an open question rather than a decision. Conflicting statements should be shown to the owner for resolution.
If a later message changes the choice, create a new dated entry that supersedes the earlier one. Do not rewrite history. Readers need to know what was true at each point.
Confirm and store the record
Post the draft in Slack and ask the decision owner to confirm or correct it. The team then saves the approved record in its chosen location. Nema can link future status updates and handoffs back to it.
Any write to a durable knowledge system depends on configured access and the team's rules. The core workflow is the reviewed decision draft.
Start with a recent thread
Choose a decision participants remember clearly. Ask Nema to draft the entry, then have the owner compare it with their understanding. Notice which approval signals and scope details required explanation. Add those conventions to the team's reusable guidance.
Questions from operations teams
Can Nema decide whether consensus was reached?
It can apply the explicit signals your team defines. When the record is ambiguous, it should ask the accountable owner.
What if the rationale is sensitive?
Write a restricted record or a limited summary for the broader audience. Do not copy private material into an open channel.
How are changed decisions handled?
Add a new entry with its date, owner, and reason. Link it to the prior record and mark which decision is current.
Review older records when the project reaches a major milestone. Close questions that the team answered, retain the original dates, and avoid turning a temporary project choice into standing guidance without an explicit new decision.