We were going to hire the wrong person. Not a bad person. The wrong seat.

The conversation had been running for a while in the way these conversations run: a manager was underwater, said so repeatedly, and asked for help in a specific shape. Everyone agreed. The role had a name, and the name had been said out loud enough times that it had started to feel like a decision that had already been made.

Before we posted it, I pulled twenty-eight weeks of hours out of the payroll system and put them in a spreadsheet by function, by week.

The gap was real. It was just not where anyone had been pointing. The function that was screaming was overloaded about four weeks a year, badly, in a way that was memorable and awful. A different function was running eleven percent over its own capacity almost every single week, quietly, absorbed by two people who never brought it up because it never got bad enough on any single day to be worth a conversation.

The recommendation that came out of it was a processing role, two seasonal tour staff, and one flex position that floated between the two. It did not match the request. It matched the data, and it cost less than what had been asked for.

The loudest gap is rarely the widest gap

Escalation is not a measure of need. It is a measure of how a specific person responds to pressure, and the range of human responses to pressure is enormous.

Some managers escalate at seventy percent load because they are conscientious and want lead time. Some absorb one hundred and twenty percent for a year and then quit in an email on a Tuesday, and everyone says they never saw it coming. If you staff by who is loudest, you are running an organization that rewards volume, and you will lose your quiet people first — which is a problem, because the quiet ones tend to be the ones absorbing the overflow.

Complaints tell you where the pain is felt. They do not tell you where the pain is created. Those are frequently two different departments, and the one creating it is almost never the one complaining.

The Coverage Curve

Twelve weeks minimum, twenty-plus is better. Payroll hours, by function, by week, plotted against whatever your demand signal is — bookings, orders, tickets, tours, volume of whatever the thing is you actually do.

You are looking for three things, and none of them are averages.

- The chronic overage. A function running consistently over its stated capacity with no single dramatic week. This is your real hire, and it is almost never the one being requested, because chronic pain does not generate escalations. It generates resignations. - The break week. The single worst week in the window. Look at what actually happened, and specifically at who covered. That person is your flight risk and they have not told you yet. - The hollow. The stretch where a function is genuinely underused. This is not an argument for cutting anyone. It is where your flex role can live, and it is the reason a flex role is cheaper than two specialists.

Then the question that decides it: is this a coverage problem or a capability problem? Coverage means more hours of something you already do. Capability means nobody there can do the thing at all. They feel identical from the inside and they have completely different answers, and hiring a specialist to solve a coverage problem gives you an expensive person doing basic work who leaves in eight months.

Hire the flex role first

Specialists are a bet on a forecast. Flex roles are a bet that your forecast is wrong.

Your forecast is wrong. It is wrong in a direction you cannot currently name, which is precisely what makes it a forecast. A person who can move between two functions gives you information about where the real demand sits, and after two quarters you will know exactly which specialist to hire, with evidence, in a budget conversation you will win in four minutes.

There is a second effect nobody counts. A flex role is the cheapest promotion pipeline you will ever build, because the person in it ends up being the only human in the building who understands how two departments actually hand off to each other.

The failure mode

You hire to relieve a feeling, and the feeling belongs to a manager rather than to the operation.

The warning sign shows up about ninety days later. The new person is fully ramped, and the same manager is still tired. That is the tell that the constraint was never headcount. It was an undecided Ocean Stride Advisory | Framer production copy 7 question, or a process with no owner, or two people doing the same job and neither one being told to stop.

Headcount is the most expensive way to avoid a hard conversation, and it works just well enough for one quarter to be worth trying again.

One thing to try this week: Pull twelve weeks of hours by function. Find the worst week. Find out who covered it. Then go ask that person one question about what they think should be different, and let them talk longer than is comfortable. — Michael J Washington, Ocean Stride Advisory