Hemory TeamOn this page
A new teammate suggests building a mobile app for event registration. Someone says, “We already ruled that out,” but the decision note only names the browser-based form. It does not explain whether the app was rejected on principle, excluded from this event, or postponed until later.
Record the unselected option, its status, the reason given, and the scope of the choice. Include a condition for reconsideration only if one was stated. This gives the next discussion a useful starting point instead of turning “we considered it” into a permanent veto.
Distinguish rejected, deferred, and unresolved options
An option can remain unselected for different reasons. The distinction affects whether someone should reopen the discussion, seek a missing decision, or wait for a stated condition.
| Status supported by the record | What the note should explain |
|---|---|
| Rejected for this scope | The option was not chosen for the specified work, with the stated reason |
| Deferred | Consideration or work was postponed; preserve any agreed timing or trigger |
| Discussed but not selected | The option appeared in the exchange, but its final disposition is not established |
| Replaced | A previously accepted approach was superseded by a supported later decision |
“We could revisit that” is not a commitment to build it. Likewise, an option omitted from the final summary was not necessarily rejected. Check the response and conclusion before assigning a status.
For the broader distinction between an idea and an agreement, see decisions, commitments, and ideas.
Keep the reason tied to the decision’s scope
Explain the constraint or trade-off that mattered at the time. “Too complicated” leaves future readers guessing. “Not selected for July’s one-day event because the team prioritized avoiding an app installation for attendees” identifies the work and the criterion.
Record that as the team’s stated reasoning. It is not evidence that an app would be unsuitable for every event or that attendees have independently validated the preference.
When the reason is missing, seek the relevant exchange or a later clarification. The guide to finding decision rationale covers that retrieval step. Do not supply a plausible reason merely to complete the note.
Use Hemory to recover the alternative’s actual status
A short decision note naturally emphasizes the chosen approach. Hemory retains captured discussions as transcripts and organized Memory, so the response to an alternative can remain available even if it was omitted from the summary.
For a known conversation, ask a follow-up question such as: “What happened to the app option in this discussion? Was it rejected for this event, deferred, or left open, and what reason was given?” Check the relevant passage when the distinction changes your note.
If the decision developed across discussions, a compatible AI agent connected to Hemory can help prepare a first draft from available context:
Prepare a note about the registration options we did not choose for July.
Use the available Hemory discussions and the current decision note I provide.
For each relevant option, establish its status, stated reason, and scope.
Include any agreed condition for reconsideration. Keep suggestions to
revisit separate from commitments to implement. Identify the supporting
exchange and flag any disposition the sources do not establish.Provide current external records separately when they are needed and outside the connection’s access. The benefit is recovering the exchange without manually reconstructing every objection before drafting.
Example: rejected for one event is different from deferred exploration
The following fictional discussion illustrates the method. It is not a customer case or actual Hemory output.
The event owner says: “Use browser registration for July’s one-day event so attendees don’t have to install an app. We are not building a native app for this event. Leave consideration of digital badges until after the event; we have not committed to implementing them.” The project coordinator confirms that browser registration is the plan for July.
A note based on that exchange could read:
| Option | Recorded status | Reason and scope | What remains open |
|---|---|---|---|
| Browser registration | Selected for July | The event owner prioritized avoiding an app installation for this one-day event | Later events are outside this decision’s scope |
| Native app | Rejected for July’s event | The chosen approach avoids requiring an app installation | No general decision about apps for future events was made here |
| Digital badges | Exploration deferred until after the event | The owner expressed interest in later exploration; no implementation commitment | No exploration owner, implementation date, or approval was established |
The summary can stay short:
July will use browser registration. A native app was ruled out for this event because avoiding an attendee installation was a priority. Digital badges remain a possible subject for exploration after the event, not approved delivery scope.
The note does not say that the app was technically impossible or that digital badges will be built in August. Neither claim follows from the supplied exchange.
Use a compact option note
Decision and affected scope:
Chosen approach:
Unselected option:
Status established by the record:
Reason stated at the time:
Reconsideration condition, if agreed:
Supporting source and discussion date:
Later clarification or revision, if any:If you recommend a new review trigger, label it as your recommendation. For example, “Consider the app again for a multi-day event” may be useful advice, but it should not appear as a condition agreed in the original discussion unless the record establishes it.
Keep this note beside the working decision. Include enough explanation for readers who cannot open your personal conversation record, with references for fuller background where accessible.
FAQ
Should I list every idea mentioned in a meeting?
Prioritize alternatives that explain the choice or are likely to be proposed again. A brief mention may not need a separate entry unless its status affects later work.
Can a rejected option become appropriate later?
Yes. The original reason may concern a particular scope, constraint, or period. Keep that history intact and record any new assessment as a later review rather than rewriting what was decided before.
What if nobody explicitly accepted or rejected the option?
Describe it as discussed with no disposition established in the available material. Ask for a decision if its status matters to the current work.
Use Hemory to preserve the reasoning while your attention stays on the options being discussed. Later, your decision note can explain the paths not taken as clearly as the one selected.
