Linh NguyenSomething looks odd. A step nobody understands. A date that seems arbitrary. A supplier chosen over a cheaper one. The invite goes out to six people for forty minutes, titled something like “align on scope.” Most of the meeting is archaeology. Who decided this? Why? Was that before or after the client changed their mind? Four people now remember an answer. It is written down in nobody's notes, so the same meeting happens again in five weeks with a different four people.
The bad version is quieter. The one person who genuinely knew left in March, and the answer is simply gone. You re-decide it, more expensively, with less information than you had the first time.
This is for people who run work that outlives the people doing it: long deliveries, handovers, ordinary staff turnover. It is not a fit if your work is short enough that nobody ever needs to ask why.
In plain English: Goalpen is a living goal tree where the reason sits on the task itself — a note, a file, a pinned decision — so the next person does not have to reconstruct March.
Why the wiki does not save you
There usually is a wiki, and it is usually thin. Not because people are lazy. Writing something down means leaving the work, choosing a page, and guessing what a future stranger will search for. That is two decisions and a context switch at the exact moment you are busiest — so it does not happen while the reasoning is fresh, which is the only time it is cheap.
If that meeting is already on your calendar, keep reading. The next part is the habit — not a tour of menus.
Keep the reason on the piece of work
A goal or task in Goalpen can carry a Note — a short rich-text piece for the reasoning: why this approach, what we rejected, what we promised the client. It can carry Documents: the brief, the signed scope, the spec, with a new version when one supersedes another. It can carry a longer write-up when something deserves more than a note. And it can carry a channel, with the decisive message pinned.
The task card summarises what is attached, with counts for notes, blogs and documents. That is the part that changes behaviour. Nobody has to already know a note exists in order to find it. The same card can show a clock for time already spent on that branch. You start and stop the timer on the task; it is not an automatic record of everything you did. Open Time on the goal and the hours add up by person and by branch.
And because the note lives on the node, writing it stops being a context switch. You are already looking at the task at the moment you know why.
Notes are edited in place and keep no history. Only documents carry the archived version chain, so if a note's reasoning changes, the old reasoning is gone. Files you attach count against your workspace storage allowance, which is at its smallest on the Free plan.
Take the decision your team has now explained more than twice
Open the task it belongs to. Add a Note with three lines: what we decided, what we turned down, and what would make us revisit it. Next time the question comes round, answer it by opening the task.
If the three lines are messy, Ask AI on the Team and Business plans can tidy them without changing the meaning. The habit itself does not need AI. A Free workspace sees a demo of that helper, plus an upgrade prompt.
Prefer to talk it through first? Use Contact us. Want the numbers before anything else? Skim Pricing. No hard sell either way.
*Current page check: “three lines on the task, not a wiki page” (13 August 2026).*