Work
You are hiring for jobs that don't exist.
Nobody in your leadership meeting will say this out loud, so I will. You are hiring for jobs that do not exist yet, and treating it like a vacancy to fill.
You have lived this. The perfect specification. The perfect candidate. Everyone exhaled. Six months later the role had already moved, and the person who fit it so well no longer did.
For decades, companies hired with precision. The exact experience. The right tenure. The industry background. The culture fit everyone could agree on. They treated the org chart like architecture. Permanent. Load-bearing. Specified down to the material. You added a column, you filled it, you moved on.
That worked when the building stood still.
The building doesn't stand anymore. The job you post today describes work that will be different by the person's first week and barely recognisable by the time they are good at it. You are not filling a role. You are betting on a capability that might matter. That makes it a strategic decision, even when it arrives as a job spec.
Most companies have not noticed. They run the same ritual. Write the spec, post it, interview for evidence that someone has already done the thing, make an offer, drop the new hire into a structure built on the belief that next year will look like this one.
It will not.
AI did not create this. It exposed it. The work inside a role now moves faster than the role. Some tasks vanish. Others become trivial overnight. New ones appear that were on nobody's competency matrix six months ago. You hire someone to do A. By spring you need them to do B. By the end of the year you need them to learn C and prototype D before the quarter closes.
Some call this agility. In practice it means you did not know what you needed, so you hired someone clever and hoped they would work it out.
Which raises the real question. What are you actually hiring for?
Most companies are still fighting the last war. They want the person who has done the exact thing before, at a logo they recognise, in a market they understand. That was clever when next year's work was last year's work. It stopped being clever.
So you engineer the worst of both worlds. You hire for stability inside a system that punishes it. You land the perfect candidate. The CV makes everyone comfortable. Eighteen months later they are a world-class expert in something you no longer need. Expensive. Stuck. Wondering why the ground moved under them.
It did not move. It was never solid. You sold them a photograph and called it a map.
Here is the shift the sharper companies have already made. They stopped hiring for the role and started hiring for adaptability.
They have not abandoned expertise. They have stopped over-paying for what someone already knows and started paying for how fast they get good at what they do not know yet. Call it adaptability. It is not being a generalist. A generalist knows a little about a lot and is remarkable at none of it. Adaptability is going deep fast, becoming useful, then doing it again somewhere else when the ground moves.
Adaptability is the thing you are hiring for. Learning velocity is how you find it. It does not show up on a career history, which is why the CV is becoming the least interesting document to read. You have to go looking.
So stop asking what they know. Ask how they learn.
Because adaptability is not a personality trait. Not the word someone typed on page two of their CV. It is a behaviour you can watch: the speed at which a person closes the gap between "I don't know this" and "I can do something useful with it." Which means "adaptable" on a CV is bullshit until you have watched it happen.
The most dangerous hire in a moving company is not the one who knows too little. It is the one who knows a single thing brilliantly and cannot recombine it. Expertise that cannot move is expensive nostalgia. The market does not care how good you were at the last thing. It cares whether you can be good at the next thing before the next thing becomes the last thing.
Creativity gets the same lazy worship. People talk about it like fairy dust, as if some were handed it at birth and the rest left theirs on the school bus. It is not mysterious. Creativity is recombination and judgment. Knowing which pieces snap together in a way nobody has tried, and knowing whether the result deserves to exist. The second half is the rare one. Judgment. Knowing what to build, when to stop, and which question is worth answering rather than a distraction in a strategy costume. Judgment gets more valuable exactly as execution gets cheaper, because you can automate the making of an answer, but you still need someone to decide it was the right question.
And this is where what looks like a hiring decision turns into an organisational one.
Stable work rewards experience. Moving work rewards learning velocity. And when nobody can name the capability you will need next year, you stop automatically hiring for it and start deciding whether to build it, rent it, or borrow it.
Headcount stops being the unit you plan around. Capability becomes the unit.
The old model was simple. Hire, seat, make permanent, pray the role outlives the person. When it did not, you paid in severance, friction, and a year of someone's life spent in a chair that should never have existed. The new model is less comfortable, because it admits the thing the old one worked hard to hide. You do not know what the company will need in two years. Neither does anyone else. A small permanent core building the long game, with a wider bench of capability you bring in when the work demands it, is not a cost trick. It is a hedge against a future nobody can see.
Which drops an inconvenient truth on the desk of whoever runs People.
If capability is the unit, and capability keeps moving, then the person who decides what the company needs, where to find it, and how fast to assemble it is not running a support function. They are running one of the most important functions in the company. They are managing its human riches: the intangible qualities that only real experience on the ground can validate.
And most Heads of People are still processing headcount requests and defending the culture deck while the CEO makes workforce bets in strategy meetings they were never invited to. The work went strategic and the function stayed administrative.
It is not the fault of the person in the seat. They are measured on whether they can fill today's roles, while being asked to build a workforce for a business whose future nobody can specify. They are stretched between a CEO who wants agility, a finance chief who wants to know why headcount is up, a hiring manager who wants someone who has done exactly this before, and a business that changed the role again on Tuesday. They are somehow supposed to make all four true at once.
They cannot, as long as People is run like a service desk. Because every one of those tensions is a people question. When the model shifts, a people question. When the product pivots, a people question. When the board asks what happens if the big bet fails, a very large people question. What capability do we have. What are we missing. What are we paying for that we no longer need. What do we build, what do we buy, what do we rent, and how fast can we switch before the whole thing seizes. That is not administration. That is strategy.
Here is something you can run this week.
In your next interview, put the CV face down on the table. Ask two things. What have you taught yourself in the last year that nobody asked you to learn. And what did you become useful at that you were never hired to do. Then stop talking and listen to the story, not the subject. Did they chase something hard because they were curious? Did they stay with it while they were bad at it? Did they get useful fast? Did they change their mind when the evidence changed? You will learn more from those two answers than from another forty-five minutes walking their career backwards. Count how many accomplished, expensive, perfect-on-paper people have nothing to say. That number is your real risk register.
Because the question is no longer whether they can do the job. The question is whether they can become the person the next version of the job will need. If you are still hiring as though the role were a fact, you are solving last year's puzzle with next year's payroll.