Most companies do not hire a person.
They hire a hope.
The hope that someone will come and take away the workload.
The hope that a new person will fix the team''s weak spots.
The hope that this time a candidate will arrive who can do everything: sales, analytics, communication, processes, systems, account management, AI tools, documentation, initiative — and also "fits well into the team".
But the most important question is very often left unasked before hiring:
What work do we actually want this person to get done?
Not according to the job title.
Not according to an old job ad.
Not according to what the previous person used to do.
But for real: which concrete tasks need to be given to someone, why exactly these ones, and should they even belong inside one person''s role at all?
This is the core of role clarity.
And that is why role clarity is a much bigger topic than just a job description.
Why is role clarity more important today than ever before?
Because work itself is changing faster than job titles.
Many roles in companies have been assembled according to logic that emerged 20, 30, or even 50 years ago. Sales manager, HR manager, project manager, assistant, marketing manager, account manager, production manager — all of these titles sound familiar.
But the work inside those roles has changed.
And it is still changing.
AI is already taking over part of the tasks. Some completely. Some partially. In some work, the human stays as the decision-maker and AI becomes the assistant. In some work, only the part that requires context, judgement, empathy, accountability, and decision-making remains for the human.
The question is no longer only who we hire.
The question is:
- Which tasks remain for the human?
- Which tasks can AI do?
- In which tasks does the human become the supervisor of AI?
- In which tasks do we need a human because a machine cannot be accountable?
- And are we even hiring for the right role — or are we hiring an old-world job title to solve a new-world problem?
If this conversation does not happen before hiring, a very expensive confusion is born.
Role clarity for the employee: am I doing the right work, or just plugging holes?
For the employee, role clarity means a sense of safety.
They understand what is expected of them.
They understand what they are evaluated on.
They understand where their responsibility ends and someone else''s begins.
They understand where they are supposed to be strong and where they are not.
When a role is blurry, the person starts guessing all the time.
- Is this my job?
- Should I be doing this?
- Why am I doing this?
- Why isn''t someone else doing this?
- Why am I being measured on something I''m not actually strong at?
- Why do I constantly have to compensate for someone else''s gaps?
A blurry role creates invisible stress. And often the problem is not that the person is a bad employee. The problem is that the person has been given a combination of tasks that does not match their nature, values, energy, skills, or work style.
A person can be very good — just in the wrong role.
Or in the right team — but under the wrong tasks.
Or in the right company — but measured wrongly.
Role clarity for the candidate: am I applying for a real job, or for a beautiful job ad?
For the candidate, role clarity is a question of honesty.
Job ads often describe an ideal person. Not the actual work.
They look for a person who is strategic and detail-oriented. Independent and highly collaborative. A fast mover and a thorough analyst. A great communicator and a deep specialist. A leader and a doer. Creative and systematic. Ambitious and loyal. A salesperson and an administrator. A visionary and an Excel person.
But a real person does not have all strengths at once.
If the candidate does not understand which tasks are actually critical, they cannot honestly evaluate whether the role fits them.
And the employer cannot honestly evaluate whether the candidate fits the role.
That is how we arrive at a situation where everything seems to match on paper, but at the start of the actual work it turns out the fit was only on paper.
Role clarity for the team lead: am I looking for a person, or am I solving a systemic problem?
The team lead usually sees the pain first.
Someone is overloaded.
Some work doesn''t get done.
Someone can''t cope.
A task keeps landing on the wrong person''s desk.
A team member is doing work they don''t want to do or can''t do well.
Another person could do the same work much better, but no one has ever asked them.
Then the simple conclusion appears: "We need a new person."
But before hiring a new person, you should ask:
- Do we actually need a new person, or are the roles distributed wrongly?
- Which tasks are today''s people doing that they shouldn''t be doing?
- Which tasks are left undone because no one has the natural strength for them?
- Which work in the team is in the wrong hands?
- Should the new person fill a gap or create a completely new capability?
- Are we hiring a person to do the work — or to pay the price of today''s confusion?
Role clarity is not just an HR topic. It is a management topic.
The team lead has to be able to describe what outcome they need. HR can help shape that into a role and a hiring process. But the actual content of the work has to come from inside the team.
Role clarity for HR: bad input produces bad hiring
HR can only hire as well as the input given to them.
If the team lead hands HR an old job description, a vague wish, or a copy of some previous job ad, then precise hiring cannot emerge from it.
HR cannot guess which tasks are actually critical.
HR cannot know which work in the team isn''t functioning today.
HR cannot see which responsibilities are wrongly distributed.
HR cannot magically find a person to fit a role that has not been genuinely thought through.
Hiring often fails not because HR did a bad job, but because the role was not made clear before hiring.
And that is the most interesting place.
We often talk about role clarity once the person has already been hired.
Once the confusion is already here.
Once the expectations don''t match.
Once the candidate doesn''t live up to the hopes.
Once the team is disappointed.
Once the new person is stressed.
But role clarity should be the starting point of hiring, not aftercare.
Role clarity for team members: a new person does not arrive into a vacuum
When a new person joins the team, their work is not the only thing that changes.
The whole team''s distribution of work changes.
Someone gives something up.
Someone gets more.
Someone''s influence shrinks.
Someone''s responsibility grows.
Some people feel relief.
Some people feel threatened.
Some start supporting the new person''s energy.
Some start pulling them down — consciously or unconsciously.
That is why a new role cannot be defined by the manager alone in a back office.
The conversation has to happen inside the team:
- Which work goes to the new person?
- Which work stays with the existing people?
- Which work should be eliminated or automated altogether?
- Which work could AI partly take over?
- Who is being relieved of work that was actually draining them?
- Who is being given work that actually energises them?
- What conflicts may arise around work style, values, or responsibility?
A new person does not automatically solve a team problem. Sometimes they simply make it visible.
Why do companies stay stuck in old roles?
Because old roles are comfortable.
They can be copied.
They can be quickly turned into a job ad.
They are easy to compare against market salary levels.
They are understood by managers, HR, and candidates.
But comfortable does not mean accurate.
An old role description may have emerged in a time when today''s tools, today''s business model, today''s team, today''s market, and today''s AI impact did not exist.
That is why at the start of every new hire, you should ask:
- Do we actually need this position?
- Or do we need a certain collection of tasks?
- Do those tasks belong to one person?
- Should some of them be done by AI?
- Should some of them be split between existing people?
- Are we looking for a person to fit the role, or shaping the role around the person and the work?
That last question is often the most uncomfortable. But also the most useful.
Why does CV-based hiring not show role fit well enough?
A CV speaks about what a person allegedly did before.
But a CV does not show well enough:
- whether the person wants to do this work;
- whether they can do this work for the long run;
- whether this work gives them energy or drains it;
- whether their values match the team;
- whether their work style matches the manager;
- whether they can operate in this culture;
- whether they fit this specific combination of tasks;
- whether they fit the team''s dynamics;
- whether they need a different kind of management than the team lead offers.
In hiring, skills are often looked at because they are easy to describe. But the biggest problems do not always come from skills.
They come from misfit.
A person may know how to do the work but not fit this environment.
A person may be a very good cultural fit but need support to learn a skill.
A person may look weaker on the CV but be a much better choice in terms of tasks, values, and team dynamics.
Here a question appears:
Why do we prefer a skill written on a CV whose proof can be thin, while leaving the person''s actual fit with the work, the manager, the team, and the culture unevaluated?
This does not mean skills don''t matter. They do.
But skills are only one layer.
Role fit is much broader.
What should actually be talked through before hiring?
Before looking for a new person, the team should run one very practical exercise.
Not starting from the job title, but from the work.
- First: what work needs to get done?
- Second: which of these are business-critical?
- Third: which work do today''s people do well?
- Fourth: which work drains today''s people?
- Fifth: which work is today in the wrong hands?
- Sixth: which work can be automated or reduced with AI?
- Seventh: which work will still require a human in the future?
- Eighth: what kind of person would fit the remaining role best?
Only after that should a job ad emerge.
Not the other way around.
What does Sparkly do in all of this?
Sparkly was built so that the fit between people, tasks, and teams does not stay at the level of gut feeling.
Sparkly helps look at role clarity through multiple layers at once: tasks, person, team, management, values, energy, fit, risks, and future changes.
1. Building a role starts from tasks, not from the job title
Sparkly helps describe which concrete tasks belong inside the role.
That means that before hiring, the question is not only "who do we need?" but:
- what needs to get done?
- which tasks belong to this role?
- which tasks are critical?
- which tasks could be in someone else''s hands?
- which tasks may change in the future because of AI?
This makes the input to hiring much more precise.
2. In hiring, the person is evaluated against the actual work of the role
Sparkly does not look at the candidate only through the CV or a previous job title.
A candidate can be compared against the concrete tasks, role expectations, values, work style, management needs, and team fit.
This helps see whether the person fits exactly this role — not just a similarly-named position at some other company.
3. Candidates can be compared meaningfully
When there are several candidates, Sparkly helps compare them not only by a list of skills, but also by how they fit:
- the tasks of the role,
- the dynamics of the team,
- the manager''s style,
- the culture of the organisation,
- values,
- work energy,
- potential risk areas.
This gives the manager and HR a much better picture than simply "whose CV looks stronger".
4. The team lead sees what is actually happening in the team
Sparkly helps the team lead see how people influence each other.
- Who amplifies whom?
- Who slows whom down?
- Where does energy emerge?
- Where does friction emerge?
- Which tasks fit whom better?
- Which responsibilities are wrongly distributed?
- Where might overload, conflict, or a drop in motivation appear?
This is not labelling people. This is making management visible.
5. Team members see their own tasks in their own portal
In Sparkly, the employee themselves has an overview of their own tasks.
This helps the person understand what is expected of them, which work is on their responsibility, and how their role fits into the whole.
Role clarity should not be a document sitting in a folder somewhere.
It should be a living tool that the person and the manager can actually use.
6. The impact of AI on roles is built in
Sparkly also helps look at how AI may change the role.
- Which tasks may disappear entirely over time?
- Which become partly automatable?
- In which can AI be an assistant?
- In which does the human remain the decision-maker?
- In which is the human still irreplaceable because context, accountability, empathy, and value-based judgement are needed?
This is critical, because the role of the future cannot be built only on the job description of the past.
Closing thought: role clarity is not an HR document. It is a business decision.
Role clarity determines whether a person can succeed.
It determines whether the candidate honestly understands what they are walking into.
It determines whether the team lead is managing real work or managing confusion.
It determines whether HR is hiring against a precise input or trying to guess.
It determines whether team members can amplify each other or start quietly draining each other.
The most expensive hiring mistake may not be hiring the wrong person.
The most expensive mistake may be that the right role was never made clear in the first place.
And maybe every new hire should start not from the question:
"Who do we need?"
But from the question:
"What work actually needs a human — and what kind of human can actually succeed in this work?"