Headcount is one of the most persistent words in organisational life.
We discuss increasing it, reducing it, freezing it, replacing it and moving it from one part of an organisation to another.
The word is useful.
An organisation needs to know how many people it employs, what that employment costs and whether it has sufficient capacity to carry out its responsibilities.
The problem begins when a measure becomes a way of seeing.
A headcount can tell us how many people are present.
It cannot tell us what they know.
It cannot reveal the experience they have accumulated, the judgement they exercise or the contribution they might make under different conditions.
It does not tell us whose ability has remained unseen.
Who may be ready to progress.
Who is carrying knowledge that the organisation has never formally recognised.
Or who has gradually stopped contributing—not because they have nothing more to offer, but because the conditions around them no longer make contribution possible.
People become visible in the workforce plan as numbers.
But organisations move forward through what becomes possible between them.
When the number becomes the person
There is nothing inherently wrong with counting people.
The danger lies in allowing the count to become the description.
When this happens, someone joining the organisation becomes additional capacity.
Someone leaving becomes a vacancy.
A period of growth becomes a recruitment requirement.
A period of difficulty becomes a reduction exercise.
A role is treated as a fixed container into which another person must be placed.
The organisation may search more widely, offer more money or engage another recruiter without first asking whether the role itself has changed.
What knowledge has been lost?
What relationships were held by the person leaving?
Are the skills now required different from those described in the existing job profile?
Could someone already inside the organisation grow into the work?
Does the organisation need another person—or does it need to connect and enable the capability it already possesses?
These questions do not eliminate the need to recruit.
They help ensure that recruitment addresses the real requirement.
The difference is between filling a position and understanding what the organisation needs to become capable of doing.
The headcount economy
The same distinction applies at the level of an economy.
Economic growth can be supported by adding more people to the workforce.
For a time, this may respond to labour shortages, increase output and allow organisations to continue operating.
But adding people is not the same as developing capability.
If an economy continually requires more workers without improving what people, organisations and technology can accomplish together, growth becomes increasingly dependent on expansion.
More people are needed to produce more output.
Pressure grows on housing, infrastructure, public services and communities.
Employers continue to experience shortages, even as employment reaches new heights.
The debate then becomes centred on where additional workers will come from.
That may be a necessary question.
But it should not be the only one.
We should also ask whether work is being designed in ways that allow people to develop.
Whether organisations are investing in the skills they say they cannot find.
Whether technology is improving human capability or compensating for structures that have not changed.
And whether people already participating in the economy can see a credible route towards more skilled, secure and meaningful work.
A headcount economy asks how many more people are required.
A capability economy also asks what more can become possible through the people already here.
Easy to enter. Hard to climb.
Recent work by the Malta Skills Observatory offers an indication of the issue.
In a ten-source snapshot of 5,030 retained job advertisements serving Malta and Gozo, 86% did not ask for a degree. Yet only 16% referred to training or progression.
These figures describe advertised requirements and opportunities. They do not provide a complete account of what every employer does after someone has been recruited.
But they raise an important question.
If many jobs are open to people at the point of entry, how visible is the pathway that allows them to move forward afterwards?
An economy may become relatively easy to enter while remaining difficult to climb.
People are recruited to meet immediate operational needs. They learn enough to perform the role. The organisation becomes dependent on their contribution.
But the next step is never clearly designed.
Training may be available without being connected to progression.
New technology may be introduced without helping people understand how their work is changing.
Experience accumulates without being translated into recognised capability.
A vacancy appears at the next level, and the organisation begins looking outside because it has not made visible what someone inside may already be capable of becoming.
This is not only a recruitment problem.
It is a failure to connect work, learning and progression.
People are not skills deficits
Discussions about skills frequently begin with what people lack.
A person is described as not yet ready, insufficiently qualified or missing the capabilities required for another role.
Sometimes the gap is real.
Certain work requires formal qualifications, licences, technical competence or experience that cannot responsibly be bypassed.
But people should not be understood only through the distance between where they are and a predefined requirement.
Every person begins from somewhere.
They carry knowledge from previous roles, informal responsibilities, education, family life, community participation and experiences that may not appear in their job title.
A person working in one sector may already hold many of the skills required in another.
Someone assumed to be far from a role may possess valuable adjacent capability but lack a clear route through which to complete the transition.
Another person may have the technical skills yet need confidence, exposure, support or an organisational environment in which they can exercise them.
Skilling should therefore begin with a different set of questions.
What can this person already do?
What do they understand?
Which capabilities can transfer?
What must genuinely be learned?
What barrier is preventing movement?
What pathway would make the next step credible?
And what meaningful opportunity will follow the learning?
This is the difference between treating people as collections of deficits and recognising them as holders of capability and potential.
The capability we fail to see
Organisations often know less about their people than they imagine.
They know job titles, reporting lines, salary bands and performance ratings.
They may know which courses someone has completed.
But they do not necessarily know who has experience beyond their current role.
Who has solved a similar problem elsewhere.
Who is trusted across departmental boundaries.
Who can explain complexity clearly.
Who exercises quiet judgement when formal processes do not provide an adequate answer.
Or who has the potential to contribute more but has stopped expecting to be asked.
Much of an organisation’s capability is relational.
It exists in the person colleagues approach when something does not make sense.
In the experienced worker who can see that a process is about to fail.
In the manager who creates enough trust for someone to disclose a concern early.
In the employee whose formal role appears modest but who holds together relationships on which the work depends.
These contributions are difficult to place on a headcount table.
That does not make them less real.
When such a person leaves, the organisation may replace the position and still discover that something important has gone missing.
The number has been restored.
The capability has not.
Technology and the workforce question
Artificial intelligence makes this distinction more urgent.
Organisations are beginning to ask which tasks can be automated, which roles will change and how many people may be required in the future.
These are legitimate questions.
But if they are approached only through headcount, the organisation may underestimate both the human capability it needs to preserve and the new capability it must develop.
The purpose of AI should not be limited to performing existing work with fewer people.
It can also help people work with evidence more effectively, recognise patterns, reduce administrative burden and devote more attention to judgement, creativity and relationship.
The better question is not simply:
How many people will we need?
It is: What will people need to become capable of doing—and how can technology help them do it responsibly?
That question changes the conversation.
It directs attention towards work design, skills, judgement, governance and participation.
It asks whether employees are being prepared for new systems or merely expected to adapt after the decision has already been made.
It asks who benefits from greater efficiency and whether the people whose roles are changing can see a place for themselves in what comes next.
Technology can strengthen human capability.
But only if capability is recognised as something to develop rather than a cost to remove.
Wellbeing is part of capability
People do not exercise their full capability simply because it exists.
They need conditions in which it can be used.
A person may possess experience and judgement but work within a culture where questioning a decision is unsafe.
Someone may complete training but remain in a role that offers no opportunity to apply it.
A team may have the skills required for change while carrying workloads that make reflection and learning impossible.
Another employee may appear disengaged when the underlying difficulty is exhaustion, exclusion or the repeated experience of being overlooked.
Wellbeing is therefore not separate from workforce capability.
It is one of the conditions through which capability becomes available.
This does not mean removing accountability or avoiding difficult expectations.
It means recognising that sustainable contribution depends on trust, clarity, health, belonging and the belief that effort can lead somewhere meaningful.
An organisation cannot say that people are its greatest asset while designing conditions that prevent those people from contributing fully.
The statement becomes meaningful only when it is visible in how work is organised, how decisions are taken and how people are enabled to develop.
What it means to ThinkPeople
To ThinkPeople is not merely to express concern for employees.
It is to adopt a discipline.
It means refusing to separate organisational strategy from the people expected to carry it.
It means looking for capability before assuming absence.
It means understanding the relationships through which work is actually achieved.
It means asking who may be missed by a decision that appears efficient.
It means treating skilling, progression and wellbeing as part of organisational readiness rather than as benefits added after the real strategy has been decided.
And it means recognising that transformation does not happen to people.
It happens through them.
This approach does not remove the need for workforce plans, financial discipline or difficult choices.
It makes those choices better informed.
A responsible leader may still conclude that a role must change, that new expertise is required or that an organisation cannot continue with its existing structure.
But the decision should follow a genuine attempt to understand what capability exists, what can be developed and what human consequences the chosen course will create.
Clarity before action.
Capability before replacement.
Pathways before exclusion.
Human judgement before automatic conclusion.
Beyond the count
The organisations best prepared for the future may not be those that become most efficient at replacing people.
They may be those that become most capable of recognising what their people can become.
They will understand their workforce not only by role and cost, but by capability, relationship, potential and readiness.
They will connect learning to real opportunities.
They will introduce technology in ways that strengthen human contribution.
They will make progression visible.
And when they must look outside for capability, they will do so with a clearer understanding of what they need and why it cannot yet be developed from within.
Headcount will remain necessary.
But it should be the beginning of workforce understanding, not its conclusion.
Because a number can tell us how many people are present.
It cannot tell us whether they are recognised.
Whether they can contribute.
Whether they can grow.
Or what may become possible when their capability is connected with purpose, opportunity and the right conditions.
Headcount tells us how many people an organisation has.
ThinkPeople asks what becomes possible through them.