Resourcing by memory does not scale
At ten people, who has the skills and the bandwidth lives in one person's head. At thirty, it does not, and the firm rarely notices the moment it stopped working.
There is a question that gets asked constantly at a growing partner services firm: who has the right skills and the bandwidth for this project? At ten people, the answer lives comfortably in one person’s head. At thirty, it does not.
Resourcing by memory does not scale. It overbooks your best people, idles your newest ones, and leaves nobody able to plan.
How resourcing actually happens
Someone asks in Slack. Someone who has been around a while answers from memory. The project gets staffed based on who that person happened to think of. Fast, and at small scale, fine. The problem is what it depends on.
Where it breaks
- The person with the memory leaves, and the staffing knowledge leaves with them
- New hires cannot find who to ask, so they guess
- Senior consultants get overbooked, because they are the names everyone remembers
- Junior people sit idle, because nobody remembers to think of them
- The skills inventory, if it exists, is a spreadsheet HR updated once at a review
Every one of those is a margin or retention problem wearing a different hat.
Resourcing as a data question
The fix is not complicated. Make the inputs visible:
- A skills matrix with real proficiency levels, not a yes-or-no checkbox
- Capacity that is actually tracked, so bandwidth is a fact, not a guess
- Search that works: find a monday.com advanced consultant with healthcare experience should be a two-click answer
When the inputs are visible, staffing is a decision instead of a recall test.
Every misallocation is margin. The wrong person on the job, or the right person stretched across three jobs. And every overbooked senior consultant is a retention risk you created by accident. Resourcing is not an administrative afterthought at a services firm. It is the core operation, and it should run on data, not on whoever has been there longest.