Matching the Right Person to the Right Project (Without Spreadsheet Tetris)

The weekly staffing meeting at most services firms is the worst meeting on the calendar.

It runs an hour. It covers eight projects. It relies on institutional memory, a spreadsheet that's always 48 hours out of date, and a partner who has to remember who's good at what. Decisions get made with incomplete information. People get assigned to work that's wrong for them. The meeting ends with half the assignments “to be confirmed.”

This is our POV on why staffing matching is harder than it looks, what good staffing needs to actually work, and why the goal isn't perfect match but fast good-enough decisions.

Why the staffing meeting fails

Three data problems produce consistently bad staffing meetings:

1. Availability data is stale

The spreadsheet that shows who's free next week was last updated two days ago. Projects have changed. People have been pulled onto other things. The numbers in the spreadsheet don't reflect current reality.

2. Skill data is tribal

The partner running the meeting knows that Maria is great at financial modeling and Tom is the go-to for retail clients. This knowledge doesn't exist in any system. When the partner isn't in the meeting, half the institutional memory is gone.

3. Project requirements are fuzzy

“We need someone senior on this engagement” is not a staffing spec. Senior how? What skills? What client experience? What communication style? The vagueness produces either over-specification (only one person in the firm fits) or under-specification (anyone senior could do it), neither of which is useful.

Fix any two of these and staffing improves. Fix all three and the weekly meeting goes from an hour to fifteen minutes.

The three views staffing needs

Good staffing requires three live data views:

View 1: Who's available and when

Real-time utilization by person, with forward-looking commitments 4–8 weeks out. Not a snapshot from last Friday — current.

View 2: What each person is good at and interested in

Skill taxonomy plus preferences plus recent experience — see why skill-based staffing beats availability-based staffing for why this view changes outcomes. This is the view most firms lack. Tribal knowledge replaces it, which only works while the tribe is in the room.

View 3: What the project actually needs

Role requirements by phase, not a single “team composition” guess. Discovery needs different skills than Build. A project that lumps them together gets staffing mismatches downstream.

When all three views are current and aligned, staffing becomes a filter — not a negotiation.

Skill taxonomies only work if they're current

Most firms have tried skill taxonomies. Most have watched them decay.

The typical cycle: HR or operations builds a skill framework with 200 tags. Staff self-tag on hire. The taxonomy is never updated. Within 18 months, the tags don't match the work people are actually doing, and staffing decisions go back to tribal knowledge.

Skill taxonomies only produce value when they're continuously updated. Two practices keep them current:

1. Project-based skill attribution. Every project completion adds skill tags to the people who worked on it. The system learns what people are actually doing, not what they said they could do at hire.
2. Quarterly skill check-ins. Brief review with each person: what did you do this quarter that changes your skill picture? Update tags. Five minutes per person per quarter.

Firms that do this have skill data that stays useful. Firms that don't have a skill system that's rotted into unreliability.

Preference matters more than firms admit

People do better work on projects they want to do than on projects they've been assigned.

This is obvious, and it's systematically ignored in staffing. The staffing meeting optimizes for availability and skill match. It rarely considers whether the person wants the work, finds it interesting, or sees it as a development opportunity.

The cost of ignoring preference:

• Quality is lower on work the person doesn't care about.
• Turnover is higher among people who consistently get assigned to work they don't want.
• Firm-level skill development is erratic because people never work on what they want to grow into.

Adding preference to the staffing calculation doesn't mean everyone gets their first choice every time. It means preference is one factor among three or four, not ignored entirely.

Firms that get this right have higher retention, better delivery quality, and faster organic skill development than firms that don't.

The good-enough-fast rule

Perfect staffing is impossible. Every project has tradeoffs — availability vs. skill vs. preference vs. continuity vs. cost.

The firms that staff well don't obsess over perfect match. They make good-enough matches quickly and focus their energy on project execution instead of on staffing debate.

The rule: if the staffing meeting takes more than 20 minutes total for 8 projects, the firm is over-optimizing. Make the decisions, move on, and refine during the project if needed.

Over-optimization on staffing has its own cost: the decisions come out worse because fatigue sets in, and the firm burns hours on staffing meetings that could have gone to client work.

Three moves to make staffing work

1. Make the three views live: availability, skill/preference, project requirements — all in one place, current to the day.
2. Maintain the skill taxonomy continuously, through project attribution and quarterly check-ins.
3. Weight preference explicitly as one of the staffing criteria.

Firms that do these three things cut their staffing meeting time by 60–70%, improve project outcomes because people are on the right work, and see retention climb because people feel seen in the staffing process.

Good staffing isn't a harder meeting. It's a better system producing faster, better decisions.

Octayne's Resource Management brings availability, skills, preferences, and project requirements into one live view — so staffing decisions take minutes, not hours. Book a demo to see intelligent resource allocation on your firm's data.