Hire the Core. Virtualize the Rest.
Most companies still treat hiring as the default answer to an execution problem.
A product launch is slipping, so they open three engineering roles. Customer implementations are taking too long, so they hire more implementation managers. A new AI initiative appears, so someone asks for a data scientist, an AI engineer, and a product manager.
The assumption is simple. If the work matters, hire people around it.
For a long time, that was reasonable. People were the main source of capability, and employment was the most reliable way to keep that capability close.
The problem is that work has changed faster than the employment model.
Today, many important business problems do not need one skill, full-time, for years. They need several different capabilities, each for a different amount of time.
A customer implementation may need an integration engineer heavily for two weeks, a data specialist for three days, a security expert for a few hours, QA near the end, and a domain expert only when something unusual appears.
Hiring all of them permanently would be expensive. Hiring one generalist and hoping they can cover everything would be risky.
This is where the old model starts to bend.
The company does not necessarily have a people shortage.
It has a capability design problem.
Hiring is a permanent answer to a question that may be temporary
The first thing I would ask before approving a new role is not whether the work is important.
A lot of temporary work is extremely important.
A regulatory deadline can be urgent and business critical. A migration can determine whether a company succeeds or fails. A major customer implementation may be worth millions.
Importance does not make the work permanent.
This is where organizations often get trapped. A temporary surge creates a permanent role. Then the surge passes, the work changes, or the capability is no longer needed at the same level.
The employee is still there.
The company then has to find new work for the role, move the person elsewhere, or eventually make a painful decision.
We saw this pattern across many companies in the years after aggressive hiring. Forecasts changed, demand changed, technology changed, and organizations discovered that fixed headcount is much harder to unwind than it is to approve during a growth cycle.
That is not a criticism of hiring.
It is a reminder that employment is a long-term commitment and should be used that way.
If the capability is core, permanent, and needed full-time, hire.
If it is variable, episodic, or likely to change quickly, pause before turning it into payroll.
This is the same tension explored in Work Is Episodic. Why Are Teams Permanent?. Demand moves in waves, but the organization around it is often built as though the wave will last forever.
The core should stay close to the company
None of this means companies should stop hiring.
In fact, the more flexible the execution model becomes, the more important the permanent core becomes.
Every company has capabilities it should own deeply. These usually involve judgment, customer trust, institutional memory, strategy, product direction, architecture, risk, and leadership.
A software company should know its own product better than any external provider.
A financial company should keep real control over risk.
A healthcare company cannot outsource responsibility for patient outcomes.
A manufacturer should understand the systems and processes that make its operation distinctive.
These capabilities belong close to the company because they shape what the company is.
That is the core.
The mistake is assuming that every capability surrounding the core must also be hired permanently.
It does not.
A strong internal product leader may need access to five different specialist skills over the course of a year. That does not mean five permanent specialist roles are automatically the right answer.
A customer success leader may need temporary integration capacity every time a complex enterprise customer signs. That does not mean the company should carry the maximum implementation team all year.
The question is not whether the work matters.
The question is whether the capability needs to live inside the company all the time.
That distinction is subtle, but it changes workforce design completely.
Most modern work needs a changing mix of capability
This is one reason I like thinking in capabilities rather than roles.
Roles are convenient for HR systems and org charts. Real work is messier.
A person called a “Senior Implementation Engineer” may spend part of the week on integration, part on configuration, part on data mapping, and part chasing information from other teams.
Another customer may require a completely different mix.
The title stays the same.
The capability demand changes.
We explored this more directly in Roles Are Fiction. Capabilities Are Real.. The point was not that job titles are useless. The point was that work does not arrive neatly packaged according to them.
The more specialized the economy becomes, the more obvious this gets.
A company may need an excellent cloud security architect, but only for one critical week. It may need a pricing expert for a launch, a Dynamics specialist during an ERP transition, or a data engineer during migration.
The traditional answer is to hire ahead of need, borrow somebody internally, or bring in a contractor.
All three can work.
But there is another possibility.
Keep the permanent core small and strong, then build a flexible execution layer around it.
That is where the Virtual Delivery Center fits.
The VDC is the layer around the core
A VDC is useful when the company knows the area of work will remain important, but the capability mix inside that work will keep changing.
Think of Customer Implementation.
The company may always need to onboard customers. That is a persistent mandate.
But the exact capability needed for each implementation is not persistent.
One customer may need data migration. Another may need ERP integration. A third may have heavy security requirements. A fourth may require training and change management.
The company can keep the customer relationship, product knowledge, implementation ownership, and key decisions internally.
Around that core, the VDC can bring in whatever capability the current work requires.
That may include specialists, delivery pods, AI agents, software tools, or external partners.
When the work changes, the capability mix changes with it.
The function remains.
The payroll does not need to mirror every possible scenario.
This is what we mean when we say a VDC is not simply a remote team. It is a persistent execution environment around a mandate, with a variable capability layer inside it.
The idea becomes clearer when you look at How to Build a Virtual Delivery Center: A Practical Playbook. The VDC should grow around real work, not around an abstract desire to create a new organizational model.
This also changes the speed equation
Hiring is slow for a reason.
Good hiring should be careful.
You need to define the role, find candidates, interview them, assess fit, negotiate, wait through notice periods, onboard, and then give the person time to understand the company.
That can take months.
If the capability is going to matter for years, the investment can be worth it.
If the business needs a specialist for six weeks, the same process makes very little sense.
The work may be finished by the time the perfect hire becomes productive.
A VDC changes that because it does not begin with employment.
It begins with the outcome.
The company can define what needs to be delivered, understand the capability required, and activate a team around it much faster.
This does not mean recklessly throwing strangers into critical systems.
Governance still matters. Access still matters. Context still matters.
But those things can be designed around the work instead of waiting for a full employment cycle.
That is a very different kind of speed.
It is not “move fast and break things.”
It is “do not use a six-month organizational process to solve a six-week capability problem.”
The economics are different too
Permanent employment works well when the capability is used consistently.
The economics become much harder when the capability is used only part of the time.
Suppose you hire a specialist at a significant annual salary because you need them for a project this quarter.
What happens next quarter?
If the same level of work continues, great. The decision was probably right.
If it does not, the company is now paying for capability it is not fully using.
This is one of the reasons headcount can quietly become expensive. The salary is visible, but the unused capacity is less visible.
There is also management cost, benefits, onboarding, equipment, career development, and the responsibility to keep creating meaningful work.
None of those things are bad.
They are simply part of the commitment.
A VDC makes the cost structure more variable.
The company can activate capability when required and release it when the work changes.
That matters to finance, but it also matters to people.
A company that repeatedly hires into temporary demand and later lays people off is not only making an economic mistake. It is creating human damage around a forecasting problem.
A better capacity model can reduce some of that.
This is one reason the conversation around From Loyalty to Leverage: The New Compact Between Talent and Enterprise matters. The future of work should not be about making people disposable. It should be about creating relationships that are more honest about what is permanent and what is not.
The core can actually become stronger
There is a fear that using flexible capability weakens the internal team.
That can happen if the company does it badly.
If too much knowledge leaves the business, if external providers make all the important decisions, or if internal leaders stop understanding how the work happens, the company becomes hollow.
That is not the goal.
The better model is almost the opposite.
The internal core should become more valuable because it spends less time carrying every possible kind of execution work.
A product architect should not spend half the week solving routine implementation problems if those can be handled elsewhere.
A customer leader should not spend days trying to find a niche specialist inside the company.
A senior engineer should not become the default answer to every temporary capacity shortage.
The internal team should concentrate on the things that require internal context, judgment, trust, and long-term responsibility.
The flexible layer handles the variable execution around it.
This allows the permanent team to stay closer to the company’s real advantage.
When hiring is still the better answer
There are cases where I would hire without hesitation.
If a capability is central to the business, needed continuously, and expected to remain important for years, employment is often the right model.
If a person needs deep context that takes a long time to build, hiring makes sense.
If the role carries broad authority or institutional responsibility, hiring may be essential.
If you are developing future leaders, permanent relationships matter.
If the work will clearly fill a full-time role for the foreseeable future, trying to keep it external simply to avoid payroll may be short-sighted.
The point is not to replace hiring.
The point is to stop using hiring automatically.
The company should earn its way to a permanent role by showing that the capability itself is permanent.
A simple test before opening the requisition
Before approving the next role, ask a few questions.
Will this capability still be needed at roughly the same level two or three years from now? Does it need to remain inside the company for strategic, customer, regulatory, or knowledge reasons?
Will one person actually be busy with this work full-time, or are we bundling several occasional needs into a job title?
Could the company get a better result by combining a strong internal owner with specialists, AI agents, and temporary execution capacity around them?
And if the project ended six months from now, would we still be happy that we hired this role?
These questions will not always point toward a VDC.
Sometimes they will make the case for hiring even stronger.
That is useful too.
The purpose is to choose consciously.
The company after headcount will still have employees
There is a temptation in future-of-work discussions to turn everything into a dramatic prediction.
Employment is ending.
Everyone will become independent.
Companies will become tiny.
I do not believe it will be that simple.
The enterprise of the future will still employ people. Some companies will employ a great many.
What changes is that employment no longer needs to be the only way the enterprise accesses serious capability.
As we discussed in The Company After Headcount, the real capacity of an organization will increasingly include employees, specialists, AI agents, partners, software, and other forms of productive capability.
That changes what a company looks like.
A business with 300 employees may have access to more effective execution capacity than one with 3,000.
The difference may be how well it can assemble capability around an outcome.
Hire the core. Virtualize the rest.
There is a simple principle underneath all of this.
Keep the things that define the company close.
Hire the people whose knowledge, judgment, relationships, and leadership need to compound inside the business for years.
Treat those jobs seriously.
Invest in those people.
Then look at everything around them with fresh eyes.
Some work will be variable.
Some capabilities will be needed only occasionally.
Some tasks will move to AI.
Some specialist skills will change faster than the company can reasonably hire for them.
Some execution capacity will need to appear quickly and disappear just as quickly when the work is finished.
Do not force all of that into permanent employment simply because that is the structure companies know best.
Build a strong core.
Give that core access to a flexible execution layer.
Let the work determine the capability mix.
The result is not a company without employees.
It is a company that becomes much more deliberate about why it employs them.
That is a healthier future for the business.
And, if we get it right, probably a healthier future for the people too.