Many job descriptions are based on the past
When a position becomes available, the response is often predictable. The old job description is pulled up, updated here and there, and published again. That may seem efficient, but it relies on an important assumption: that today’s needs are the same as yesterday’s. This is often where things go wrong. Organizations are constantly changing. Teams take on different responsibilities, technology changes how work is done, and projects create new demands for employees. Yet job descriptions often remain largely unchanged for years. As a result, a vacancy may focus mainly on who needs to be replaced, while paying far less attention to the problem that actually needs to be solved. The difference may seem small, but in practice it is significant.
Every vacancy hides a different challenge
A manager might ask for an experienced project manager. The immediate response is often to search for exactly that profile. But a deeper conversation may reveal that the role is mainly about stakeholder management. Or driving change within a team. Or creating structure in a complex project. In that case, the job title matters less than the underlying need. The same applies to years of experience. Organizations often ask for ten years of experience, while five years of relevant experience combined with the right skills may be just as valuable. Sometimes organizations are looking for a specialist, while a generalist with the right ability to learn may be a better fit for the organization’s future direction. That is why the most successful vacancies are often not the ones written fastest. They are the ones where time is taken to explore the question behind the question.

