Imagine a company preparing to launch a major new product.
For the next six months, it urgently needs:
-
Product strategy
-
User research
-
Experience design
-
Cloud architecture
-
Mobile development
-
Data engineering
-
Cybersecurity
-
Quality assurance
-
Compliance expertise
-
Technical documentation
-
Customer onboarding
-
Launch marketing
The work is real.
The urgency is real.
Each capability matters.
But the demand is not uniform.
The security architect may be essential for several weeks and then needed only occasionally.
The data migration specialist may be critical during implementation and largely unnecessary after the transition.
The technical writer may be heavily involved toward the end.
The product designer may be central during discovery and then return during major iterations.
The customer onboarding team may become important only when the product is ready to reach users.
The company does not need twelve permanent departments.
It needs a changing combination of capabilities across the life of the outcome.
Yet the traditional response is predictable.
Open job descriptions.
Engage recruiters.
Interview candidates.
Negotiate compensation.
Wait through notice periods.
Onboard employees.
Create reporting lines.
Assign managers.
Purchase tools.
Add benefits.
Build a team.
By the time the team is ready, the market may have changed, the product assumptions may have shifted, and some of the original capabilities may no longer be the most important ones.
Then, once the work is complete, the organization still owns the capacity.
New projects must be invented to keep the team utilized.
Priorities begin adapting to the workforce instead of the workforce adapting to priorities.
This is one of the great contradictions of modern business:
Work is increasingly episodic, but teams are still designed as though demand were permanent.
The Permanent Team Was Built for a More Predictable World
The permanent team is not a bad invention.
It helped create some of the most productive organizations in history.
When work was stable and demand predictable, permanent teams made sense.
A factory expected to produce the same class of goods for many years.
A bank operated through relatively stable processes.
A technology platform evolved over long product cycles.
Skills remained useful for decades.
Communication across distance was difficult.
Institutional knowledge lived mainly inside employees.
Coordination required proximity.
Employment created continuity.
A company could forecast the capabilities it would need, hire people into stable roles, and organize them into lasting departments.
Permanent teams created:
-
Trust
-
Shared context
-
Cultural continuity
-
Operational discipline
-
Institutional memory
-
Long-term ownership
-
Reliable availability
-
Career development
-
Deep specialization
These advantages remain valuable.
The problem is not that permanent teams are obsolete.
The problem is that organizations use them as the default answer to almost every form of work.
Even when the work is temporary.
Even when the capability need is uncertain.
Even when demand is volatile.
Even when technology is changing faster than the hiring cycle.
Even when a specialist is needed for twenty days rather than twenty years.
The permanent team has become less of a strategic choice and more of an organizational reflex.
Work Rarely Arrives in Neat, Permanent Packages
Companies hire in roles because administrative systems require roles.
Payroll needs a title.
Compensation needs a level.
Managers need reporting lines.
Recruiters need job descriptions.
Finance needs headcount plans.
Human resources needs career frameworks.
But actual work does not care about any of these structures.
Work arrives as problems.
A customer cannot integrate the product.
A regulator introduces a new requirement.
A competitor launches a better experience.
A system begins failing under increased load.
A market opportunity opens in another country.
A company acquires another business.
A supply chain becomes unstable.
Leadership wants to introduce AI.
A product needs to be rebuilt.
Each problem requires a different combination of capabilities.
The shape of the work changes across time.
At the beginning of an initiative, the company may need research and strategic judgment.
Later, it may need architecture and implementation.
Then testing and validation.
Then training, rollout, and support.
The capabilities do not arrive together.
They do not remain equally important.
They do not necessarily belong to one function.
Yet organizations try to convert this changing demand into fixed boxes.
One box for a product manager.
Three boxes for engineers.
One box for a designer.
One box for a project manager.
The role becomes a rough container for a bundle of capabilities.
Sometimes the fit is reasonable.
Often it is not.
The organization either hires more capability than it needs or discovers that the role does not contain enough of what the outcome requires.
The Hiring Model Assumes Continuity That Often Does Not Exist
Hiring is one of the most consequential decisions an organization makes.
It creates a long-term economic and human relationship.
It should be used deliberately.
But in many companies, hiring is treated as a procurement mechanism for capability.
A need appears.
A requisition is opened.
A person is hired.
The assumption is that the need will continue.
Sometimes it does.
Sometimes the organization simply hopes it will.
This is particularly visible in growth periods.
A company wins several customers and hires aggressively.
It raises capital and builds teams ahead of demand.
It enters a new market and creates a regional structure.
It launches a transformation and hires specialists.
It expands a product roadmap and adds engineers.
Then conditions change.
Customer growth slows.
Funding becomes tighter.
The transformation ends.
The technology changes.
The market does not develop as expected.
The organization is left with a permanent cost structure built around a temporary forecast.
What follows is equally predictable.
Hiring freezes.
Budget cuts.
Reorganizations.
Role consolidation.
Layoffs.
The same company that described people as its greatest asset begins discussing them as excess capacity.
This is not only a financial failure.
It is a design failure.
The organization treated an uncertain demand signal as a permanent staffing requirement.
Employees eventually pay the price for management’s forecasting error.
Overhiring Is Often a Symptom of Execution Anxiety
Organizations do not always hire because the work requires permanent capacity.
They hire because permanent capacity feels safe.
A full-time employee is available.
A manager can assign work.
Knowledge remains inside the company.
The organization believes it has more control.
A dedicated team signals seriousness.
Executives can point to headcount as proof of investment.
Hiring also feels like progress.
A strategic priority becomes more tangible when a team is attached to it.
The company can announce:
“We have created an AI team.”
“We have established a transformation office.”
“We have built a customer implementation function.”
“We have doubled the engineering organization.”
But the presence of a team does not guarantee the arrival of an outcome.
A team may lack the exact capabilities required.
It may become overloaded with unrelated requests.
It may spend months defining its mandate.
It may wait for decisions from other functions.
It may protect itself by creating processes and intake systems.
It may become another permanent stakeholder through which future work must pass.
The company has increased capacity.
It has also increased organizational surface area.
More people now require coordination, leadership, communication, budgeting, career development, and future utilization.
Hiring reduces one form of anxiety while creating long-term commitments that may be difficult to reverse.
Underutilization Is Built Into the Model
No team has perfectly stable demand.
Some periods are intense.
Others are quiet.
Certain capabilities become temporarily critical.
Others become less relevant.
Permanent teams absorb this variability.
During peaks, employees are overloaded.
During quieter periods, organizations search for ways to keep them occupied.
This is where utilization begins to influence strategy.
A team has been hired.
A budget exists.
Managers must justify the capacity.
Projects are created, extended, or prioritized partly because people are available.
The company stops asking:
“What capabilities does this outcome require?”
It begins asking:
“What work can we give the people we already have?”
This appears responsible.
After all, unused capacity feels wasteful.
But it subtly reverses the relationship between work and organization.
The organization should exist to execute priorities.
Instead, priorities begin serving the organization’s existing structure.
This is one reason old initiatives refuse to die.
Teams, budgets, leadership identities, and career paths have formed around them.
Ending the initiative would not simply stop the work.
It would create an organizational problem.
Permanent capacity gives temporary work a survival instinct.
Peaks Create Overload; Valleys Create Politics
When demand exceeds permanent capacity, the organization experiences overload.
Backlogs grow.
Deadlines slip.
Employees work longer hours.
Managers compete for shared specialists.
Executives escalate priorities.
The company concludes it needs more people.
When demand falls below capacity, a different pattern emerges.
Teams defend their relevance.
Functions expand their mandates.
Managers seek ownership of adjacent work.
Internal initiatives multiply.
Reporting and governance become more elaborate.
People become concerned about reorganizations and job security.
The organization may appear busy while producing less meaningful value.
This is not a moral failure.
It is the natural behavior of a fixed structure facing variable demand.
A permanent team cannot disappear and reappear as work changes.
It must maintain continuity.
So it adapts its interpretation of what is necessary.
The result is an organization that alternates between exhaustion and underutilization.
During peaks, everyone is stretched.
During valleys, everyone must prove why the structure should remain.
Specialists Create a Particular Dilemma
Some capabilities are essential but not continuously required.
Examples include:
-
Cybersecurity architecture
-
Regulatory interpretation
-
Data migration
-
Performance engineering
-
Accessibility testing
-
Enterprise integration
-
Industrial simulation
-
AI governance
-
Forensic accounting
-
Change management
-
Technical due diligence
-
Cloud cost optimization
A company may desperately need one of these capabilities for a specific initiative.
But hiring a full-time specialist can be difficult to justify.
The role may be expensive.
The talent may be scarce.
The need may not remain constant.
The organization therefore makes one of several compromises.
It assigns the work to a generalist.
It delays the initiative.
It hires a consultant at a premium.
It adds the capability to a large outsourcing contract.
It hires permanently and hopes enough future work appears.
Each option solves part of the problem.
None fully solves the underlying mismatch between episodic need and permanent capacity.
The organization does not necessarily need another employee.
It needs reliable access to a capability.
That distinction is becoming fundamental.
Access Is Not the Same as Ownership
For most of business history, ownership was the most reliable way to obtain access.
If a company needed manufacturing capacity, it built a factory.
If it needed computing power, it purchased servers.
If it needed expertise, it hired employees.
Ownership created availability and control.
But many industries have since separated ownership from access.
Companies rent cloud infrastructure.
They subscribe to software.
They use logistics networks.
They access payment systems through APIs.
They use shared warehouses and manufacturing partners.
They acquire capability without owning every underlying asset.
The same transition is beginning in work.
Organizations are discovering that they do not need to permanently employ every capability they may require.
But accessing capability is more complicated than renting a server.
People need context.
They require trust.
They need access to systems.
They must understand the outcome.
They need to collaborate with other contributors.
Quality must be verified.
Knowledge must be retained.
Security must be governed.
Commercial incentives must align.
This is why a simple marketplace of freelancers does not solve the problem.
Discovery is only the first step.
The real challenge is turning temporary access into reliable execution.
Traditional Outsourcing Solved Scale, Not Adaptability
Outsourcing emerged partly because companies wanted access to capacity without directly hiring every person.
It allowed organizations to:
-
Reach lower-cost talent markets
-
Scale large teams
-
Transfer certain operational responsibilities
-
Access provider expertise
-
Reduce internal management burden
-
Establish delivery centers in new locations
For many types of work, outsourcing remains useful.
But traditional outsourcing often recreates permanence outside the company.
The provider hires a large workforce.
The customer commits to minimum volumes.
Teams become dedicated.
Contracts run for years.
Utilization remains central.
Changes require commercial negotiation.
Account management layers coordinate the relationship.
The company may not own the employees, but it still pays for relatively fixed capacity.
It has moved the organizational structure across a contractual boundary rather than fundamentally changing it.
Outsourcing can reduce certain costs.
It does not automatically make capability composable.
Staff Augmentation Solves Availability, Not the Outcome
Staff augmentation offers more flexibility.
A company can add individuals to an existing team for a period.
This is useful when the organization already knows:
-
What work must be done
-
How the work will be managed
-
Which capability is missing
-
Who will make decisions
-
How quality will be verified
But staff augmentation begins with people, not outcomes.
It asks:
“How many developers do you need?”
“What skills should they have?”
“How long should they stay?”
The customer remains responsible for turning those people into execution.
It must onboard them.
Provide context.
Manage the backlog.
Coordinate dependencies.
Resolve conflicts.
Verify delivery.
The additional capacity may help.
But the organization still carries the integration burden.
When execution fails, both sides can claim they performed their part.
The individual worked the agreed hours.
The customer managed the priorities.
Yet the outcome may remain incomplete.
Access to people is not the same as ownership of delivery.
Freelance Platforms Solved Discovery, Not Composition
Digital talent platforms created a major change.
They made global expertise searchable.
A company could find a developer, designer, marketer, analyst, or consultant from almost anywhere.
This expanded opportunity for both businesses and independent professionals.
But most platforms stop near the point where execution becomes difficult.
They help companies find profiles.
They facilitate contracts and payments.
They may provide ratings.
But the company still needs to determine:
-
Which combination of people is required
-
Whether their capabilities fit together
-
How they will collaborate
-
Who owns the complete result
-
How access will be controlled
-
How knowledge will be retained
-
How performance will be verified
-
What happens when someone becomes unavailable
-
How work should be recomposed when priorities change
A collection of profiles is not a delivery system.
The future requires more than talent discovery.
It requires capability composition.
AI Makes the Mismatch More Obvious
AI changes the economics of permanent teams in two ways.
First, it increases the productive capacity of individuals.
A capable person supported by AI may perform work that previously required several roles.
Developers can generate code faster.
Analysts can process more information.
Designers can create more options.
Marketers can produce more content.
Operations teams can automate routine processes.
This does not eliminate people.
But it changes how many people are required and which capabilities remain scarce.
Second, AI changes the demand for skills faster than traditional workforce systems can respond.
A capability that was valuable two years ago may now be partially automated.
A new capability—such as AI workflow design, model evaluation, or agent governance—may suddenly become essential.
Permanent teams were already struggling to match variable work.
AI increases the rate of change.
A company may spend six months recruiting for a role whose definition changes before the person joins.
It may build a large team based on yesterday’s productivity assumptions.
It may continue staffing tasks that could now be automated.
Or it may automate aggressively without preserving the human judgment required around the work.
The answer is not simply smaller teams.
It is more adaptable capability.
A Job Description Is a Forecast Disguised as a Document
Every job description contains assumptions about the future.
It assumes:
-
This work will continue to exist
-
The capability will remain relevant
-
The demand will justify a full-time role
-
The responsibilities can be bundled coherently
-
One person can cover the required range
-
The organizational location will remain appropriate
-
The company can predict what the employee will do months or years ahead
Sometimes these assumptions are correct.
Often they are only loosely examined.
The job description creates an appearance of certainty.
But the work may change soon after hiring.
The employee joins to perform one set of responsibilities and is gradually assigned another.
The role expands.
The priorities shift.
The technology changes.
The employee either adapts or becomes misaligned.
Organizations describe this as agility.
But the employee may experience it as instability inside a supposedly stable relationship.
A more honest operating model would acknowledge that some work is inherently episodic.
It would not force every capability need into the fiction of a permanent role.
Employment Should Not Carry the Entire Burden of Economic Security
There is a human reason organizations continue to prefer permanent teams.
Employment provides more than capacity.
It provides:
-
Income stability
-
Benefits
-
Social identity
-
Career progression
-
Community
-
Learning
-
Institutional belonging
-
Protection from market volatility
These are important.
The solution cannot be to replace secure employment with a global race to the bottom.
A future built entirely on temporary gigs would transfer business uncertainty onto individuals.
Companies would gain flexibility.
Workers would absorb volatility.
That is not a better system.
This is where many future-of-work arguments become dangerously shallow.
They celebrate flexibility without asking who carries the risk.
They celebrate independence without building economic security.
They celebrate global access without preventing exploitation.
They celebrate multiple income streams while ignoring the burden of continuously finding work.
If work becomes more episodic, the surrounding infrastructure must become more durable.
People need:
-
Portable reputation
-
Reliable payment
-
Access to recurring opportunities
-
Learning and capability development
-
Insurance and benefits independent of one employer
-
Clear rules
-
Dispute resolution
-
Economic visibility
-
Protection against arbitrary exclusion
-
The ability to build long-term value from repeated contributions
Permanent employment should not be the only mechanism through which people obtain security.
But removing employment without creating an alternative would be a step backward.
The Core Should Be Permanent
Not all work should become temporary.
Some capabilities belong at the center of the enterprise.
They carry:
-
Strategy
-
Culture
-
Institutional memory
-
Customer trust
-
Ethical responsibility
-
Long-term product judgment
-
Leadership
-
Risk ownership
-
Proprietary knowledge
-
Enduring operational accountability
A company that externalizes everything becomes hollow.
It may gain flexibility while losing identity and strategic control.
The goal is not to eliminate the permanent team.
It is to become more deliberate about what should be permanent.
A useful distinction is:
Core capability
Capabilities that define the company, protect its long-term advantage, or carry continuing accountability.
Variable capability
Capabilities that are important but fluctuate with projects, customers, markets, or workloads.
Specialist capability
Deep expertise required intermittently and difficult to justify as continuous headcount.
Commodity capability
Repeatable work that can be standardized, automated, or accessed through external systems.
Emerging capability
New skills where demand and methods remain uncertain.
The problem is not permanent employment.
It is using permanent employment for every category.
Teams Should Form Around Outcomes
The traditional team is usually formed around a function.
Engineering team.
Marketing team.
Finance team.
Security team.
Data team.
These functions develop valuable expertise.
But important outcomes cross them.
An alternative is to compose temporary execution units around a defined result.
For example:
“Launch the customer analytics product for the European market.”
The outcome may require:
-
Internal product ownership
-
A data architect
-
Privacy expertise
-
Front-end engineering
-
Data engineering
-
Security review
-
Customer research
-
Localization
-
Technical documentation
-
Implementation support
Some contributors may be permanent employees.
Some may be external specialists.
Some capabilities may be performed by AI agents.
Some may come from software platforms.
The execution unit exists for the outcome.
It changes as the work changes.
Once the outcome is complete, the unit can dissolve or be recomposed.
This does not mean people have no continuity.
The continuity moves from the temporary team to the broader network, platform, community, profession, or core organization.
The work unit becomes episodic.
The capability ecosystem remains durable.
The Team Is Not the Only Place Trust Can Live
One argument for permanent teams is that trust takes time.
This is true.
People who have worked together understand one another’s strengths, communication styles, and judgment.
They move faster.
But trust does not have to exist only inside one permanent employer.
It can also be built through:
-
Verified delivery histories
-
Repeated collaboration
-
Shared operating standards
-
Professional communities
-
Capability credentials
-
Transparent reputation
-
Governance systems
-
Common tools and workflows
-
Long-term network membership
Film production provides a useful analogy.
A production assembles around a specific outcome.
Directors, actors, cinematographers, editors, set designers, sound specialists, and many others come together.
The team is temporary.
The professions are durable.
Reputation travels.
Relationships recur.
Capabilities recombine across productions.
The model is not perfect, and many creative industries have serious labor challenges.
But it demonstrates that complex, high-quality outcomes do not always require one permanent organization to employ everyone involved.
Trust can live in an ecosystem.
The Cost of Permanence Is Larger Than Salary
When leaders think about headcount, they often focus on compensation.
But every permanent role carries additional costs:
-
Recruitment
-
Onboarding
-
Benefits
-
Management
-
Tools
-
Administration
-
Training
-
Career progression
-
Coordination
-
Facilities
-
Compliance
-
Future reorganization
-
Severance
-
Opportunity cost
More importantly, permanent teams create strategic inertia.
Once a capability is embedded in the organization, leaders become more likely to keep using it.
A company with a large custom-development team may continue building software that would be better purchased.
A company with a major data science function may frame every problem as a machine-learning opportunity.
A company with a large sales force may prioritize products that fit the existing sales model.
Capacity shapes strategy.
The organization does not merely hire to execute its choices.
Its existing workforce influences which choices appear possible.
This can be a strength when capabilities align with the future.
It becomes a burden when the future changes.
Layoffs Reveal the Design Flaw
The modern employment cycle often looks like this:
-
Growth appears.
-
Companies forecast continued demand.
-
Hiring accelerates.
-
Teams expand.
-
Layers of management emerge.
-
Demand changes.
-
Costs become unsustainable.
-
Hiring freezes begin.
-
Reorganizations follow.
-
Employees are laid off.
-
Remaining teams become overloaded.
-
Hiring eventually resumes.
This cycle is treated as an unavoidable feature of capitalism.
But part of it results from an operating model that converts every growth signal into permanent headcount.
Companies speak about agility while repeatedly expanding and contracting their human structures through painful mass events.
The financial market may accept this.
The affected employee experiences a sudden rupture in income, identity, relationships, and future plans.
Organizations also lose knowledge, trust, and morale.
Then, months later, some begin recruiting for similar capabilities again.
A more adaptive model would not eliminate economic cycles.
But it could reduce the violence of the response.
Companies could retain a smaller, stronger core and access variable capability without permanently absorbing every peak.
Workers could participate across multiple delivery environments rather than depending entirely on one employer.
Capacity could be recomposed instead of repeatedly hired and discarded.
“Flexible Workforce” Cannot Mean Disposable People
The language of flexibility is often one-sided.
Businesses want:
-
Flexible cost
-
Flexible capacity
-
Flexible contracts
-
Flexible access
-
Flexible locations
People also need flexibility.
They may want:
-
Multiple sources of income
-
Control over time
-
Geographic freedom
-
Exposure to varied work
-
The ability to reject unhealthy environments
-
A direct relationship between capability and reward
-
Time for family, education, health, or entrepreneurship
A better model must create mutual flexibility.
The company should not own a person’s entire productive identity.
The person should not be treated as an anonymous unit of capacity.
Capability should be discoverable.
Contribution should be visible.
Reputation should accumulate.
Relationships should endure beyond one project.
Economic participation should become more portable.
The future of episodic work depends on whether we build systems that respect the person behind the capability.
From Workforce Planning to Capability Planning
Most organizations plan through headcount.
How many engineers will we need?
How many salespeople?
How many managers?
How much will payroll grow?
This approach begins with roles.
Capability planning begins with expected outcomes.
What must the organization be able to do?
Which capabilities are essential throughout the year?
Which will fluctuate?
Which are rare?
Which can be automated?
Which should be accessed externally?
Which need to be developed internally?
Which capabilities can serve multiple outcomes?
Which are likely to become obsolete?
This creates a more dynamic view of organizational capacity.
Instead of a static org chart, leaders see a capability portfolio.
Some capabilities are owned.
Some are shared.
Some are rented.
Some are automated.
Some are assembled only when needed.
The company becomes less focused on the size of its workforce and more focused on the reliability of its execution capacity.
From the Org Chart to the Execution Graph
An org chart tells you:
-
Who reports to whom
-
Which departments exist
-
Where formal authority sits
It does not tell you:
-
Which outcome is being pursued
-
What capabilities are required
-
Where dependencies exist
-
Which human and machine contributors are involved
-
Where work is waiting
-
Who can block progress
-
How completion will be verified
For episodic work, the more useful representation is an execution graph.
The graph begins with an outcome.
It connects:
-
Capabilities
-
People
-
AI agents
-
Systems
-
Decisions
-
Dependencies
-
Controls
-
Evidence
-
Economics
The graph can change as the work changes.
It is not a permanent picture of the organization.
It is a living picture of execution.
This is how companies can preserve functional depth while forming temporary, cross-boundary delivery units.
The org chart may continue to describe the core.
The execution graph describes how outcomes actually happen.
A Virtual Delivery Center Is Built Around This Reality
The idea of a Virtual Delivery Center begins with a simple observation:
Organizations need capabilities that do not always justify permanent teams.
But they still require more structure than a freelancer marketplace or loose collection of contractors can provide.
They need:
-
Governance
-
Security
-
Access control
-
Capability composition
-
Delivery visibility
-
Financial control
-
Knowledge retention
-
Verification
-
Continuity
-
Reconfiguration
A VDC is a governed execution environment where an organization can assemble people, AI agents, software, and operating rules around an area of work.
The organization does not merely buy hours.
It creates access to execution capacity.
Some participants may remain involved for years.
Others may join for a specific outcome.
The composition can change without rebuilding the entire organizational structure.
The permanent core retains strategy, authority, and institutional responsibility.
The VDC provides adaptable capability around it.
This is not an argument for replacing every internal team.
It is an argument for ending the false choice between:
“Hire everyone permanently”
and
“Send the work to a traditional outsourcer.”
There is a broad space between those models.
That space is where the future organization will be built.
What Leaders Should Ask Before Opening Another Role
Before creating permanent headcount, ask:
Is the demand enduring?
Will this capability remain important for several years, or is it attached to one initiative, customer, technology, or growth assumption?
Is the capability core?
Does it carry strategy, institutional knowledge, ethical responsibility, or lasting competitive advantage?
Is the need full-time?
Does the work genuinely require continuous capacity, or does it arrive in peaks?
Can the role be defined accurately?
Are the responsibilities stable enough to justify a permanent job description?
Is the capability scarce or merely inaccessible?
Could the organization gain reliable access without owning it?
Can AI absorb part of the work?
Has the role been redesigned around current technology, or does it reflect old productivity assumptions?
What happens after the immediate outcome?
Will there be meaningful work, or will the organization need to manufacture utilization?
Who carries the risk if the forecast is wrong?
The company?
The employee?
A partner?
Is that risk allocation fair?
Could a temporary execution unit deliver the outcome better?
Would a composed team of internal people, specialists, agents, and partners move faster and reduce long-term rigidity?
Hiring may still be the correct decision.
But it should become a deliberate choice rather than the automatic translation of demand into headcount.
The Organization of the Future Will Have a Smaller Core and a Larger Reach
The future enterprise may employ fewer people than a traditional company of similar scale.
But it will not necessarily possess less capability.
Its core will hold:
-
Purpose
-
Strategy
-
Customer understanding
-
Product judgment
-
Governance
-
Institutional memory
-
Leadership
-
Key intellectual property
Around that core will be a wider execution network.
Specialists.
Partners.
AI agents.
Platforms.
Communities.
Temporary teams.
Persistent delivery environments.
The boundary of the company will become less defined by payroll and more defined by governance.
Its strength will not come only from what it owns.
It will come from what it can reliably access, compose, and direct.
This organization can respond to changing demand without repeatedly rebuilding itself.
It can add capability without adding an equivalent amount of bureaucracy.
It can pursue opportunities without treating every experiment as a permanent workforce commitment.
It can preserve its identity while changing its execution configuration.
This is not a loose organization.
It may require stronger governance than the traditional model.
Flexibility without control becomes chaos.
The advantage comes from combining adaptability with accountability.
The Question Is Not Whether Teams Matter
Teams matter enormously.
People need relationships.
Trust matters.
Shared context matters.
Belonging matters.
Continuity matters.
The argument is not that teams should disappear.
The question is:
Why must every team be permanent simply because the work matters?
Some teams should last for decades.
Some should exist for a product cycle.
Some should form around one customer.
Some should assemble for a crisis.
Some should appear for a transformation and dissolve when it is complete.
Some should combine humans and AI agents.
Some should cross company boundaries.
A mature organization should be capable of all these forms.
The permanent functional team is one model.
It should not be the only model.
We Need Permanence in the Infrastructure, Not Every Assignment
Perhaps the deeper answer is this:
People need continuity.
Companies need adaptability.
These needs do not have to conflict.
The continuity can live in the infrastructure around work:
-
Professional identity
-
Reputation
-
Benefits
-
Learning
-
Community
-
Governance
-
Payment
-
Opportunity access
-
Long-term relationships
-
Portable achievement records
The assignment can remain episodic.
A person can move between outcomes without starting from zero each time.
A company can access proven capability without conducting a six-month hiring process.
A team can form quickly because trust, standards, and verified histories already exist.
The execution unit becomes temporary.
The economic and professional ecosystem becomes permanent.
That is a healthier foundation than forcing every changing business need into a lifetime-style employment structure—or reducing every person to a disposable gig worker.
Work Has Changed. The Organization Must Catch Up.
Work is becoming more dynamic.
More specialized.
More cross-functional.
More global.
More automated.
More dependent on temporary combinations of expertise.
The traditional organization responds by stretching permanent teams, adding contractors, signing outsourcing contracts, and reorganizing departments.
These are attempts to make a fixed structure behave dynamically.
The better approach is to design dynamism into the model.
Keep permanent what should endure.
Compose what must change.
Automate what machines can perform reliably.
Preserve human judgment where it matters.
Build governance across the whole.
Measure verified outcomes.
Allow capabilities to move toward work rather than forcing all work through permanent structures.
The question is no longer simply:
“How many people should we hire?”
It is:
“What must remain permanently ours, and what must become reliably accessible?”
That question will reshape workforce planning, leadership, technology, and the boundaries of the enterprise.
Because the contradiction is becoming too costly to ignore.
Projects end.
Markets shift.
Customer demand fluctuates.
Strategies change.
Technologies become obsolete.
Capabilities rise and fall in importance.
Work is episodic.
It is time our organizations stopped pretending otherwise.