Action items agreed on a call have a half-life of about two days unless they land somewhere with a name and a date on them.
The deduplication is the hard part
Most things discussed on a client call are already tracked somewhere, often under different wording. Creating a fresh task for each one produces a doubled backlog within a month and, worse, two half-updated records of the same work.
So existing open work is read first and matched against what the call raised. Items that already exist get updated with what was said; only genuinely new commitments become new tasks.
Priority lanes, not a list
Eleven undifferentiated tasks get worked in the order they appear, which is the order they came up in conversation, which is meaningless. Grouping into priority lanes means the two that matter this week are visibly separate from the nine that do not.
A person confirms
The output is drafted for review rather than written directly. Transcripts mishear, and a task created from a misheard commitment is worse than no task, because it looks authoritative.
Runs well with
Skills compound. These are the ones we usually install alongside it.