The Job Description: The Most Underestimated Document In The World

In every organization there is one document everybody produces, nobody values, and which contains — if you know how to read it — the whole of organizational intelligence in embryo.

An Ordinary Gesture

An HR director opens a Word file. They write a job title. They describe the missions. They list the required skills with levels. They specify the training prerequisites, the reporting lines, the particular constraints. They save it. They file it. They move on to the next one.

That gesture is performed millions of times a day around the world. In every language, in every sector, in organizations of every size. It is one of the most banal administrative acts there is.

And it is probably the most strategically under-exploited act in the whole history of management.

What A Job Description Actually Contains

Look at what the HR director has just written without registering its reach.

In describing the missions, they have defined what the organization concretely expects of this position. That is not administrative prose. It is an implicit contract between the organization and whoever will hold the role. The verbs used — “ensure”, “drive”, “supervise”, “design” — encode a level of responsibility. “Ensure production” and “drive continuous improvement on the line” do not describe the same position, even when both concern the same production line.

In listing the skills with levels, they have mapped what this position demands of human capital. Not in vague, generic terms, but with a usable granularity. “Lean Manufacturing, level 3 of 5” says something precise. It is a coordinate in a space of skills.

In specifying the hierarchical and functional relationships, they have described a fragment of the organizational network. This position reports to whom. It collaborates with which departments. It supervises how many people. It is a node in a graph.

In indicating the training and experience prerequisites, they have defined the conditions of access. It is a boundary in the space of possible career paths.

In a single document, the HR director has encoded — often without knowing it — strategy, structure, skills, relationships, flows of responsibility, and criteria for decision.

Then they saved the Word file and moved on to something else.

The Tragedy Of The Dead Document

In the vast majority of organizations, the job description is born and dies in the same gesture. It is created to satisfy an obligation — regulatory, contractual, or simply because “you have to have one”. It is filed in a folder. It is pulled out for a recruitment, an audit, or an annual appraisal. Between those moments, it does not exist.

It is a dead document.

Dead because it communicates with nothing. It does not know that thirty other job descriptions exist in the same organization. It does not know that five of them require the same critical skill. It does not know that the person holding this position was assessed six months ago and that their real skills differ significantly from the skills required.

Dead because it generates nothing. It does not produce a skills framework. It does not calculate a gap. It does not detect an inconsistency. It does not suggest a development path. It does not flag a risk.

Dead because it does not adapt. When the context changes — new regulation, new technology, a reorganization — nobody thinks to update the job descriptions. They become progressively decoupled from reality. Until they are so obsolete that everything has to be redone. An 18-month project. A substantial budget. The result: new dead documents, up to date for a few months.

That cycle has been repeating for decades. It is so entrenched that nobody questions it.

And the cost is considerable. A classical skills-mapping project — the kind that consists of manually reconstituting what the job descriptions already contain — costs between 500,000 and 2 million euros for a mid-sized organization, mobilizes teams for 12 to 18 months, and produces a deliverable that starts going obsolete on the day it is delivered.

The Question That Changes Everything

What if the job description were not an end but a beginning?

Not a document to be filed, but a starting point from which everything else is deduced. A nucleus from which organizational intelligence unfolds, mechanically, with no additional effort.

That question sounds naive. It is architectural. And the answer depends entirely on where that job description lives.

In a Word file it can generate nothing. The words are there, but they are inert. No system reads them, connects them, or computes with them.

In a classical HR module it can feed a few predefined processes. But each process lives in its own silo — the recruitment module does not talk to the training module which does not talk to the compensation module. The data exists in several copies, in several formats, with subtly different definitions.

But in an architecture where the job description is a structured document, each of whose elements carries within itself all the context needed to exploit it, something fundamentally different happens.

The Chain Reaction

Imagine an architecture where each skill listed in a job description is not simply a word in a paragraph, but a structured object carrying its identifier, its domain, its required level, and its relationship to the position that demands it.

A single document. A few dozen of those structured objects. Nothing spectacular on the face of it.

But the moment that document exists, it radiates.

The framework emerges without being built. Thirty job descriptions filled in, and suddenly you can answer a question organizations usually take months to address: what are our organization’s critical skills? The answer does not come from a mapping project. It comes from simply aggregating what already exists in the descriptions. “Lean Manufacturing” appears in twelve descriptions with required levels from 1 to 4 — that is a structuring skill. “Industrial cybersecurity” appears in only two — that is a scarce and potentially at-risk skill. The framework is not a project. It is a calculation.

Gaps reveal themselves mechanically. You assign a person to a position. You assess their real skills. The comparison is immediate: required level 4, current level 2, gap of 2. No need for a consultant spending three months interviewing everybody. The two-polygon radar — required and current — draws itself. The individual development plan follows. The annual appraisal conversation becomes factual instead of subjective.

Coherence is verified automatically. You create a new Operational Excellence Manager position supervising three Shift Supervisors. If the Shift Supervisors require level 3 in Lean, the manager should logically require at least level 4. If their contractual grade is lower than that of their subordinates, something is wrong. Those inconsistencies are invisible when descriptions are handled one at a time. They become obvious when the descriptions live in a common space.

Human risk becomes detectable. Cross critical skills with demographic data and an uncomfortable truth appears. The only industrial refrigeration expert at the Garoua plant is 58. When he leaves, that skill disappears with him. It is a human single point of failure. Invisible in an org chart. Invisible in Word files. Visible instantly when the descriptions are alive.

Succession is planned continuously. The plant director retires in three years. Who can replace him? Take the required skills of the target position, compare them with the assessed profiles of every internal candidate, rank by fit score. Samuel is at 91% but promoting him creates a hole elsewhere. Marie is at 84% but needs a spell on a plant. Thomas knows the site perfectly but has gaps in strategic leadership. Each option comes with its development plan, costed in duration and in money. What used to take weeks of work with an outside firm becomes an instant calculation.

The future becomes projectable. You inject context: the new HACCP 2026 standard, an SAP rollout planned for 2027, the automation of the packaging lines. The impact on each job description materializes. The Shift Supervisor will have to acquire “Automated line operation”. The Quality Manager will have to master “HACCP 2026 auditing”. The data-entry operator is at risk of obsolescence by 2027. New positions have to be created. For a leader, seeing the concrete impact of their strategic decisions on human capital in real time is priceless.

All of that, from a gesture the HR director already performs.

Why This Does Not Exist Everywhere

If the chain reaction is so powerful, why do existing systems not produce it?

Because those systems were built like office blocks — one floor per function, a lift between each floor, and fire doors everywhere.

The job description lives in one module. The appraisals in another. The skills in a third. Compensation in a fourth. Succession in a fifth. Each module was designed, sold, and invoiced separately. Each is excellent in its speciality.

But to reconstitute the overall view — the one that makes the chain reaction possible — those modules have to be made to communicate. And that communication costs millions. It mobilizes teams for months. And when it finally works, it is so fragile that updating one module can break the connection with the others.

It is the difference between having all the instruments of an orchestra and having an orchestra. The instruments are there. But the musicians are not in the same room. Each plays their part competently. Nobody hears the whole.

This is not a defect of those systems. It is a consequence of how they were conceived. Module by module. Need by need. Licence by licence. That approach solved real problems, one at a time. But it made structurally impossible the intelligence that arises when everything is connected.

The Strategic Stake Nobody Sees

Most leaders treat the job description as an HR subject. An administrative subject. A compliance subject. When they think strategy, they think five-year plans, financial dashboards, market projections. The job description is HR’s business. It is not on the executive committee agenda.

That is a fundamental error. And it rests on a misunderstanding of an almost embarrassing simplicity.

A job description, in its real function, is a projection of the strategy onto a role. Full stop.

Every position in an org chart exists because the organization needs somebody to accomplish part of its mission. The required skills, the expected levels, the responsibilities, the KPIs — none of it is arbitrary. It is the operational translation of a strategic objective into a set of necessary human capabilities. When a brewery requires “Lean Manufacturing level 4” for a Shift Supervisor, that is not a whim of the HR director. It is because the company’s industrial strategy rests on operational excellence, and that level of command is what it concretely takes for that strategy to materialize on the shop floor.

This is why the job description — the position, not the person — is the keystone of any coherent HR system. The person’s profile references their position. The skills assessment compares the person to the requirements of their position. The career plan projects the person towards a target position. The succession plan identifies who can hold a critical position. Not the payroll number. Not the directorate. The position. Because the position is the single junction point between what the organization wants to accomplish and what individuals have to be able to do.

And that is exactly where the system comes apart.

In 99% of companies, job descriptions are Word documents written once, never updated, disconnected from the strategy, copied and pasted from a generic template found on the internet. They are aligned with nothing at all. They describe a position as it was conceived three years ago, in a context that no longer exists, for objectives that have since changed.

And from there, the whole downstream HR system is skewed. Mechanically. Inevitably.

People are assessed on skills that no longer serve the current strategy. People are trained on gaps that are not the real gaps. Successions are planned towards positions whose definition is obsolete. Recruitment targets profiles that no longer match what the organization actually needs to accomplish. The entire HR edifice — assessment, training, mobility, compensation, succession — rests on a foundation that is no longer aligned. And nobody notices, because the foundation is a Word file nobody consults any more.

The paradox is cruel. The job description is the only document that connects strategy to people. It is the link between strategic intent and operational capability. And it is precisely that document which organizations treat as an administrative form to be filed and forgotten.

When a chief executive decides to automate the production lines, it is in the job descriptions that the decision should concretely materialize. Which positions change? Which skills become necessary? Which become obsolete? Which positions disappear? Which have to be created? Without living job descriptions, those questions stay unanswered until they become crises. The day the automation is deployed and nobody has the skills to run it. The day a critical expert leaves and nobody can replace them.

With living job descriptions — structured, connected, aligned with the strategy — those questions find answers in real time. The impact of every strategic decision on human capital becomes visible before implementation, not after.

And the beauty of it is that this is not sophisticated. It is simply correct. It is simply what the job description should always have been: not an administrative document, but the faithful and maintained projection of the organization’s strategy onto each of its roles.

Nobody does it. Not because it is difficult. But because nobody has seen that it is simple.

The Nucleus And The Reaction

A uranium atom is a banal object. It exists naturally, everywhere. For millennia nobody suspected what it contained. Then somebody understood that under the right conditions — the right architecture, the right environment — that banal atom could set off a chain reaction of considerable power.

The job description is the fissile nucleus of the organization. It contains, compacted into a few pages, the information needed to generate a skills framework, a map of gaps, a succession plan, a risk analysis, a strategic projection, a cross-site benchmark, a coherent compensation policy.

It is all there. In a document every HR director knows how to fill in. That every organization already owns.

The question is not how to create new data. It is how to give existing data the architecture that lets it react.