Staffing
Also known as: Resourcing, Project assignment, Resource staffing
Process of assigning the right people to the right projects, balancing required skills, availability and utilization targets.
Staffing is one of the most strategic activities in a consulting firm: assigning the wrong person can compromise delivery quality, client satisfaction and project margin.
In a modern PSA, staffing combines a matching engine based on skills, calendar availability, seniority level and individual development goals. The staffing manager (or resource manager) seeks to maximize aggregate utilization without overbooking, avoiding burnout. A good practice is to run a weekly staffing review with a rolling 4-12 weeks horizon, integrated with the sales pipeline.
Most staffing tools model a person as a quantity of hours, which is why their plans look feasible and turn out not to be. Two senior developers are not interchangeable when one knows the client's legacy system and the other does not, and a plan that treats them as equal produces a first week nobody anticipated. Modelling who can genuinely replace whom, with how much ramp-up, is what makes the plan usable under pressure.
Staffing decisions are also development decisions, and firms that ignore that pay for it in attrition. Always assigning the safest available person to each engagement produces good short-term delivery and a team that stops growing. Recording each person's development goal alongside their skills makes the trade-off explicit, so stretching someone becomes a deliberate choice rather than an accident of availability.
A new 6-month project requires 1 lead architect, 2 senior developers and 1 PM: the PSA suggests three combinations of available consultants with >80% skill match.