Re-Decided Question
The same decision gets made again every few months because nobody can find why it was made the first time.
What it looks like
The Re-Decided Question is not a failure of attention. The team decided correctly the first time. The problem is that the reasoning was never stored anywhere the next person could find it. Without the why, the conclusion evaporates within weeks.
What it costs
The direct cost is meeting inflation: hours spent re-litigating questions that should have been one-sentence references to an existing record. The compounding cost is team frustration. People who have argued a point and won, only to argue it again six months later, stop bringing energy to the argument. Decisions made under the Re-Decided Question pattern are weaker because the people who made them no longer believe they will stick.
There is also an implementation cost: when the same question is answered differently on two occasions, both implementations move forward in parallel. Undoing one is rarely accounted for in any estimate.
The first step, without Saberra
At the end of your next meeting, have one person read back what was decided and who owns each thing. Then write it down, with the reasoning, in one shared location the whole team can search. One sentence per decision: what was decided, and why. That record alone will surface the next time the question comes up.
The deeper fix is a system that captures decisions automatically as they happen in meetings and email, attaches the source evidence, routes everything through review before it becomes trusted memory, and makes the full history searchable. That way, "why did we decide X?" returns the original discussion along with the answer.
The features that repair it
Decision lifecycle
Decisions as records with source evidence, status, and history, from candidate to confirmed. The why survives long past the meeting.
Meeting capture
Google Meet recordings, transcripts, and notes flow in automatically and become decisions, tasks, and risks. Agreement made in a call becomes a permanent, searchable record.
Ask Sera
Plain-language questions over the whole institutional memory, answered with sources. 'Why did we decide X?' arrives with the original discussion it came from.
Record history
Every record carries its provenance and change history. Who approved it and what it came from is always visible.
Browse the feature library:
Often appears alongside:
Make decisions that stick.
A Foundation session seeds your organization's decision history into Saberra and leaves you with a working memory system. The next time a question comes up, the answer arrives with its source.