Deployment is decided in a hurry: in management and business consulting firms

The proposal is countersigned on Thursday evening. The client wants a kick-off on Monday. By Friday noon a partner scrolls a spreadsheet for anyone without a client, and the first name that fits goes. That is how many consulting firms staff: quickly, with whoever is free, with little thought for skill or growth.

• A junior with no survey experience lands on a customer research workstream and learns by erring in front of the client.
• The strongest modeller is pulled into three engagements because everyone knows she delivers.
• A consultant benched for six weeks is overlooked because nobody knows she wants supply chain work.
• A senior joins two weeks late and spends days catching up with a team that has already shaped the answer.
• Someone asks why he was moved off a client, and nobody can say.

The direct cost is rework and slow deliverables. The indirect cost is larger. Consultants staffed by accident stop asking for growth. Those who always get the hard jobs tire. Clients notice a team that changes midway, and the engagement lead spends partner time on introductions when the problem needs her.

Sales and delivery keep different calendars. The partner who wins the work signs the scope and moves on, while the delivery partner hears late. Availability lives in several heads and a few private sheets. Nobody owns the question of who is due a stretch role this quarter.

1. 1

   Keep one availability sheet

   List each consultant with grade, practice, three strongest skills, current engagement, roll-off date and what she wants to learn. One person, usually the operations manager, refreshes it every Monday.

2. 2

   Hold a staffing call weekly

   Practice heads and the delivery partner review signed work, likely wins and people rolling off. They name teams for the next three weeks.

3. 3

   Ask for the pipeline early

   Business development shares proposals at verbal agreement with a likely start date, so staffing begins before the contract.

4. 4

   Match on fit and growth

   For each role name one person who fits today and one who would stretch. Make every fourth assignment a stretch, with a lead who has time to coach.

5. 5

   Record the reason

   Note why each person was chosen. After the engagement, ask consultant and lead whether the match worked.

Name | Grade | Practice | Three strongest skills
Current engagement and lead | Roll-off date | Days booked next month
Leave dates and travel limits | Growth goal this quarter
Proposal hours last week | Bench days this quarter
Notes: client conflicts, language, site limits, stretch candidate (yes or no)

Keep it on one screen. If it needs scrolling in every direction, nobody will update it.

• Which signed engagements start within three weeks and still lack a lead?
• Who rolls off this month, and who has asked for a sector or method?
• Is anyone booked above the usual load for more than two weeks?
• Which proposals rest on one named person?
• Who has sat on the bench longer than two weeks, and doing what?

Ask in the same order each week. After a month, partners arrive with the facts and the call shortens. After each kick-off, the engagement lead can send two lines to the staffing owner: was the team right? Over a year those notes show which pairings work.

• Days from signature to a named team.
• Engagements per consultant in the past quarter, by grade.
• Bench weeks per consultant and the work done in them.
• Share of assignments chosen for growth.
• Team changes after kick-off.

Not every match can be perfect. A kick-off in week one may need whoever is free. The test is whether the choice was made on purpose. If a junior goes onto a survey workstream without experience, name a reviewer, add a checkpoint at day five and tell her why. A stretch with support is development. A stretch in silence is a risk.

Watch the pairings too. A hypothesis-driven partner and a detail-first analyst can sharpen each other, or can grind for weeks. Ask both after the first fortnight how the working style fits. Small adjustments early, such as a daily fifteen minute huddle or a shared outline of the storyline, prevent a painful mid-project swap.

Finally, protect the bench from stigma. Time between projects is when proposals get written, diligence notes get filed and juniors read the last three readouts. If the bench is described as failure, people hide it and the sheet lies.

This is one of five patterns on the hub for management and business consulting firms. For skills, see how management consulting firms build a competency matrix. For cover, read how consulting firms can cover absence. Headcount against pipeline belongs to our workforce planning service.