Decided, or Only Discussed? Turning a Meeting Into a Map With Owners and Dates

A week after a good meeting, try this. Open the notes and mark every sentence that was actually decided. Then mark every action that has a named owner and a date. For most meetings, the result is humbling. The notes are full of reasonable sentences — “we talked about the venue,” “piano might be an issue,” “Maya will look into it” — and almost none of them can be sorted into what was agreed, what was merely discussed, and who is doing what by when.

The rest of the trail is somewhere else. Part of it is in a chat thread. Part of it is in someone’s memory, which is a storage medium with excellent compression and very poor retrieval. The meeting happened. The record of it did not.

The Meeting-to-Action Map (for Freeplane) fixes the record, not the meeting. It is a Freeplane map already split into four branches — Context, Topics, Decisions, and Actions — with Owner, Due, and Status attributes waiting on every action node, plus a completed fictional example so you can see the shape before you fill your own.

Get it here: Meeting-to-Action Map (for Freeplane)

What goes wrong with ordinary meeting notes?

Four problems, all of them familiar.

The trail is scattered. Notes in one file, follow-ups in a chat thread, the real decision in someone’s head. Nobody is at fault; there was simply no single place built to hold it.

Topics, decisions, and actions share a paragraph. “Discussed parking; decided to request the hold; Owen to check on the piano” is three different kinds of statement crammed into one line. A week later, you cannot tell at a glance which part was settled.

Actions have no owner, no date, or no place to filter. “Look into the piano” is a hope, not an action. Without an owner and a date it cannot be followed up, and without a consistent place to record them, nobody can ask “what is still open?” without rereading everything.

A topic with no decision just evaporates. The meeting discussed the piano, did not decide anything, and moved on. Unless someone writes down “no decision yet” and creates an action to get one, that topic quietly disappears until it becomes a crisis on the day of the event.

Why separate what was said from what was decided?

Because the institutions that depend on meetings learned, sometimes painfully, that a record of talk is not a record of action.

When Henry Martyn Robert published Robert’s Rules of Order in 1876, his guidance on minutes made a distinction that still holds: minutes are primarily a record of what was done at a meeting, not of everything that was said. Motions, decisions, and assignments go in. The debate, however eloquent, mostly does not.

At the Constitutional Convention of 1787, two very different records were kept. The official journal recorded motions and votes. James Madison, sitting near the front, kept his own extensive notes of the debates. Historians are grateful for both, and the pairing illustrates the point neatly: the journal tells you what was decided; Madison tells you what was discussed. They are different records because they answer different questions.

Until December 1916, the British Cabinet kept no formal minutes. When Maurice Hankey became the first Cabinet Secretary under David Lloyd George, he began recording conclusions and the actions that flowed from them. Before that, ministers could and did leave the room with different understandings of what had been agreed.

A meeting-to-action map is the same discipline at a smaller scale. Topics go on one branch, decisions on another, actions on a third — each with an owner, a date, and a status.

What are the four branches?

The structure is simple enough to keep, which is exactly what makes it useful.

Context holds the date, the attendees, and the purpose in one sentence. The guide’s rule is sharp: if you cannot write the purpose, the map has the wrong meeting on it.

Topics holds one child node per topic that was actually discussed. Topic nodes stay topics. They are not allowed to masquerade as decisions or smuggle in actions.

Decisions holds the choice, in one sentence, under each decision node. If a topic produced no decision, you write “none” and add an action that will produce one. This is the rule that catches the evaporating topic.

Actions holds a single verb and object per node — “Send the hall-hold request,” not “handle the hall stuff.” Each action node carries three attributes, filled in the same sitting.

Why attributes on the action nodes?

Because they turn a list of tasks into something you can query.

Every action node in the template already carries Owner (a named person), Due (a date, written YYYY-MM-DD), and Status (open when created, updated when the work moves). Attributes are a standard Freeplane feature, and Freeplane’s own filter controls can show you, for example, only the open actions or only those due on a given date. The kit deliberately does not prescribe a click-by-click filter path, because menus vary by version and layout; it simply makes sure the data is there when you reach for the filter.

And if you never filter at all, you still have a complete record, because the owner, the date, and the status are sitting right on the node where anyone can read them.

The guide’s rule for action nodes is worth adopting wholesale: an action without an owner is not yet an action. An action may wait without a due date only if you have deliberately left Due empty and written why in the node text. Status stays open until the work actually moves. Fill all three before you close the map.

What is in the kit?

The zip contains a 3-page guide, two Freeplane maps, and a README.

  • **Meeting-to-action-template.mm** — the blank template, with Context, Topics, Decisions, and Actions, and Owner, Due, and Status attributes on the action nodes. Even the placeholder text teaches: “Action 1 — a single verb and object.”
  • **EXAMPLE-Northshore-hall-walkthrough-FICTIONAL.mm** — a filled, labelled fictional example.
  • The guide — the four branches, attributes on action nodes, the first-hour path, and the fictional example walked through as a narrative.

The maps are Freeplane XML (map version="freeplane 1.13.0"), written for Freeplane 1.13.x, and were checked as well-formed XML when the kit was built. The stable line they target is Freeplane 1.13.5. Official Freeplane documentation describes creating a new map from a template with File → New map from template…, and you can also simply open the files and save a copy under a new name.

What does the fictional example look like?

The example is a hall walkthrough for Northshore Studio, a made-up studio. On a fictional date in November 2026, Maya Chen (studio lead) and Owen Park (hall contact) — both fictional — walk a community hall. Purpose: leave with a hold decision and named next actions.

Three topics were discussed: whether the hall is available for a Saturday 4 p.m. start with an hour of setup, whether a piano will already be in the room, and parking and walking access for an audience.

Two decisions were recorded. The first: request a hold on the hall for the Saturday 4 p.m. start. The second is the one worth studying: piano access — none yet, needs a follow-up. The map does not pretend a decision was made. It records the absence of one and turns it into work.

Two actions follow, each with its attributes filled. Maya Chen sends the hall-hold request, due 2026-11-21, status open. Owen Park asks whether a piano will already be in the room, due 2026-11-18, status open.

Read the example once and you will see the whole method: three kinds of statement, kept apart, with every action owned and dated.

What does the first hour look like?

Install or open Freeplane 1.13.x. Open the fictional example first, so you have seen a completed map — including the decision that is still open, and the two actions with their attributes.

Then start from the template — File → Save as, or open Meeting-to-action-template.mm directly — and save it under the name and date of your real meeting. Fill Context first: date, attendees, purpose. Then Topics, as they were actually discussed. Then Decisions, in the same sitting, writing “none” and adding an action wherever a topic produced no decision. Write Actions last, and fill Owner, Due, and Status on every action node before you leave the map.

The best time to do this is right after the meeting, while the difference between “decided” and “discussed” is still obvious to everyone.

How does it sit next to the Decision Map Template Pack?

The Decision Map Template Pack is for a choice: the question, the criteria, the options, and the because. The Meeting-to-Action Map is for a meeting: what was discussed, what was decided, and who will do what by when. When a meeting produces a substantial choice, take that choice to a decision map and leave a short pointer on the meeting map. They are companions, and neither replaces the other.

Freeplane is a trademark of its trademark owner, and the software is released under the GNU GPL. This is an independent set of original maps and a guide for people who use Freeplane. It is not an official Freeplane product, and it does not include the Freeplane application.

A record that answers “who is doing what by when?”

You are not paying for a blank map. You are paying for a structure that already separates topics from decisions from actions, attributes already waiting on every action node so the record can be filtered later, a rule that turns undecided topics into owned actions, and a filled example you can learn the whole method from in a few minutes. The next time someone asks what was agreed, the answer will be on one map.

Get the Meeting-to-Action Map (for Freeplane): Meeting-to-Action Map (for Freeplane)

It will be listed on our Tools for Freeplane page alongside the rest of the tools in that line. You can browse every Organa Obscura tool on the Products page.

Leave a Reply