Unowned Meeting Items
Turn recurring unowned items into assignments
Read the meeting notes below and find the items that come up repeatedly but never get a clear owner. Output a table: 1) the item, in one sentence describing what must be delivered; 2) how many times it was raised, with the actual quotes; 3) why nobody picked it up — no authority, no capacity, unclear ownership, or general worry; 4) the specific role it should go to, not “the relevant colleagues”; 5) the latest date it starts causing damage if still unowned. At the end, name the one item that needs a decision in the room. [Paste notes]
How to use
Repeated does not mean important — often everyone assumes someone else owns it. Write down the cost of not doing it first; then an owner is a real conversation.
Good for
- The project Weekly has been running for six weeks; every time someone says tracking needs finishing, but no owner ever appears in the notes, and the issue rolls toward launch.
- In a cross-team meeting, several teams mention that access requests are too slow, each assumes it is someone else's problem, and it evaporates when the room empties.
Not for
- The item already has a named owner and is merely late — calling it unowned repeats the blame; chase the schedule instead.
- Someone mentioned it once in passing and there was no agreement — upgrading it to an action item invents work nobody signed up for.
Example
Input
Sync notes (week 3): A: Tracking still isn't done — we won't be able to see conversion after launch. B: Isn't that the data team? C: We only do reporting; product has to file the request. A: We said that last time. D: Let's just get the launch out. B: So who files it? (No answer.)
What you get
First row: “Finish the tracking needed for launch and file the request”, noting it has come up three weeks running, with A's and C's words quoted. For why nobody took it, write “ownership unclear: product thinks data files it, data is waiting on product”, and assign it to the product lead rather than “the relevant colleagues”. End with the cost of leaving it: no channel-level conversion after launch, a decision needed by next Wednesday, and “who files the tracking request” as the one thing the meeting must settle.
Common mistakes
- Treating every mentioned item as unowned — real orphan items are raised repeatedly, someone asks who owns them, and nobody answers; not all chatter.
- Assigning it to “product, data, and engineering together” — three owners means no owner; it has to land on one role.
Try tweaking it like this
- Add “one sentence someone can ask in the room for each item”, such as “Who can put a name to this by Friday?”, which breaks the logjam on the spot.
- Switch to “only items raised two or more times”, which suits long project retrospectives and filters one-off noise.