Organisational memory
The decision nobody wrote down
Every firm has a record of what it did and no record of what it decided. This is about that gap: why a notes field does not close it, and what closing it actually means.
5 min read
Three months later, someone asks a simple question
"Why did we drop this client's price by 12%?" The person asking is the new account lead. The person who knows left six months ago. What exists: an invoice with the final number, and a WhatsApp thread nobody opens any more.
That is not a memory failure. It is a recording failure. The decision was made, it was probably right, and it had nowhere to be written.
Notice which half the systems kept. Work done is recorded, because work has a status and a status goes in a table. A decision has no status. It happens once, and afterwards only its consequences are visible.
Four places a decision goes to die
And all four look like reasonable places
The WhatsApp group
The fastest place to say it and the worst place to find it. Not searchable, not attached to the client, and whoever joins later was never in it.
Minutes nobody reads
Written, sent, filed. The problem is not that they do not exist; it is that they are not attached to that client's record, and six months on nobody knows which set of minutes it was in.
The CRM notes field
One free-text column. A decision, a chat and a phone number all have the same shape, so you cannot ask "what did we decide this quarter" — a question a column of prose cannot answer.
The task the decision produced
This is the subtlest one. The task gets recorded and the decision does not — so six months later you know what you did and not why. A task is a decision's effect, not the decision.
Why "just add a field" is not the answer
The natural response is: fine, add a note type called "decision". But the problem is not the label. A decision needs everything a task needs and more — the person accountable for it, the date it was taken, and the discussion that arrived at it.
That discussion is the important part. A decision with no reasoning cannot be reviewed six months later: you do not know what was considered and what was not, so you cannot tell whether changed circumstances should change the answer.
So what is needed is not a field but a shape: something that has a kind, an accountable person, a date, and that keeps the conversation it came out of attached to it.
Our answer
The seven things real work produces share one shape
In PulseUp, task, comment, decision, blocker, idea, potential and risk are one shape: one card, one table, one thread. A kind decides only what a record may say — not where it goes.
And they are written on that client's or engagement's own page rather than in a separate section. Which means three months later, the place you go looking is the place it was written.
A reply can carry its own kind too: you answer a blocker with a decision. So a discussion that arrives at a decision produces it without leaving the discussion — and the reasoning stays next to the outcome.
- Every record with an accountable person and a date
- On the contact's, company's or engagement's page — where you would look for it
- In the Work stream and the agenda, on its own date
- And if the engagement is team-private, so is its record
- Sara MohammadiTuesday, 14:02Voice note
Site visit. Mr Rezaei said next year's budget is settled by the end of Mordad and they won't decide anything before then.
Task created: Follow up on budget — Sara Mohammadi
said on the drive back — filed before the office
- Amir KazemiMonday, 09:30
The 1403 statements arrived. Scanned, and the quality is poor.
A small test worth running
Nothing has to migrate. Pick one engagement for one week and write every decision about it in that one place — not the group, not the minutes.
At the end of the week, ask one question: if it changed hands today, would the next person understand from this page why the work went the way it did? If the answer is yes, that is the difference this piece is about.
Common questions
How is this different from meeting minutes?
Minutes say what happened in one meeting; a record says what has been decided about this client — from any meeting and any conversation. The first captures an event, the second builds a history.What if the team does not adopt it?
That is a real risk, and the answer is that writing a decision must not be harder than writing a message. There is one writing box per page and it defaults to a comment; making it a decision is one icon away.Can we use this instead of project management?
No, and deliberately. Tasks stay in their own table and the board is the same board. Records are for the things that have no status: a decision does not get ticked.
Try it on your own data
The free plan has no time limit. Bring the hardest document you have.