Single-threaded team
A single-threaded team has one clear owner and real focus on one important goal, rather than a group of people borrowing time from their other jobs. The point is not headcount. It is that the goal is somebody’s actual job rather than everybody’s additional one.
The arithmetic nobody does
Nine people at twenty per cent is not the same as two people full time, even though the spreadsheet says it is. Context switching, scheduling and the fact that the day job always wins in a conflict mean the effective capacity is far below the notional one.
And when the goal slips, the honest diagnosis is rarely that it was too hard. It is that nobody was ever really on it.
What single-threaded actually requires
One owner whose success is the goal’s success, not a coordinator. A small team whose primary allocation is this work. And explicit permission for those people to say no to their previous responsibilities, which is the part that gets skipped.
Without the third one you have relabelled the same part-time arrangement, and it will behave exactly as it did before.
The trade you are making
Fewer goals, properly resourced, beats more goals worked in parallel by people who are already busy. That is the trade, and it is uncomfortable because it means saying no to things that are genuinely worth doing.
The alternative is not doing more. It is doing more slowly, and finding out at the end of the quarter.
What is a single-threaded team? +
A team with one clear owner and genuine, primary focus on one important goal, rather than several people contributing a fraction of their time alongside their normal jobs.
Why do part-time OKR teams fail? +
Because the day job always wins the conflict, and context switching eats the notional capacity. Nine people at twenty per cent reliably delivers less than two people who are actually on it.