Weaponized Incompetence: The Meeting Notes Nobody Can Read
A team meeting with a rotating schedule on the wall, an arrow pointing to Jordan's name for note-taking duty this week
The team reading Jordan's meeting notes, which are a jumbled mess of fragments like 'thing about budget maybe?' and 'action item: someone do something' -- everyone looking baffled
A team member suggesting 'Alex should just do it since they are so good at it' while Alex looks trapped and Jordan nods enthusiastically in the background
Alex permanently stuck taking notes at every meeting for the rest of eternity, while Jordan produces a flawless client presentation on their laptop -- mysteriously competent when it counts
A colleague consistently takes such unusable meeting notes that the task permanently defaults to the most organized person on the team.
Explanation
It was supposed to be a rotating responsibility. Everyone takes a turn doing meeting notes. When Jordan's turn came, the team received a document that looked like a ransom note -- sentence fragments, no action items, three misspelled names, and an entire section that just said 'discussed stuff about the thing.' The team lead asked Jordan to redo them. Jordan produced a second version that was marginally better but still unusable. By the third meeting, someone suggested 'Maybe Alex should just do the notes since they are so good at it.' Alex, the most organized person on the team, is now the permanent note-taker. Jordan never takes notes again. This is weaponized incompetence in a team setting, and it follows a reliable script: perform the task badly enough that someone with higher standards absorbs it permanently, then coast on the redistribution. The key distinction from genuine incompetence is the selectivity. Jordan can produce detailed client proposals and flawless presentations -- but meeting notes? Suddenly they cannot form a complete sentence. The incompetence appears precisely when the task is unglamorous, tedious, or administrative. The fix is structural, not personal. Rotating responsibilities should come with clear templates, minimum standards, and accountability. When someone submits unusable work, the response should not be reassignment -- it should be revision with feedback. 'These notes do not meet our standard. Here is what is missing. Please resubmit by end of day.' This removes the payoff for performing badly. Weaponized incompetence only works in environments that would rather work around the problem than confront it.
Key Takeaway
When someone is selectively bad at only the tasks they do not want to do, it is not incompetence -- it is a strategy.
A team lead introducing a standard meeting notes template with required sections: decisions, action items, owners, and deadlines
Jordan submitting notes that miss the standard, and the team lead returning them with specific feedback: 'Action items are missing. Please resubmit.'
Jordan resubmitting usable notes after the second attempt, the rotation holding because accountability held
The team rotating note duty fairly, everyone contributing, Alex freed from the permanent role they never volunteered for