Being the first person in a role that did not exist before

Nobody has done this here before

A new role is created because somebody argued for it, wrote a case, and got a budget released. That process leaves a trail, and the trail matters more than the job description, because the description was written afterwards by whoever had to advertise the post and it is usually a composite of everything the team wished for.

The practical difference from an established role is the absence of comparison. There is no former holder to be measured against, no accumulated set of expectations, and no colleague who can tell you what a good month looks like. That sounds like freedom and it is, partly. It also means that if your idea of the job and your manager’s idea of the job differ, nothing in the environment will reveal that for a long time.

Find the problem the role was funded to solve

Somewhere behind the vacancy is a specific irritation that became expensive enough to hire against. Work out what it was. The question that gets you there is not what the role is responsible for but what was going wrong before the role existed, and it is best asked of two or three different people, because the answers will not match and the disagreement is the useful part.

Sometimes the answers converge on one clear problem, which makes the first year straightforward. Sometimes they reveal that three people each expected the post to solve a different thing, in which case you have discovered your actual first task, which is getting those three people to agree on a priority order. That is uncomfortable to do in your first months. It is much worse to discover in your first review.

Success needs defining before it can be assessed

In an established role, success is defined by precedent, and you can meet it without ever articulating it. In a new one, precedent does not exist, so a review conversation will be improvised from whatever your manager happens to remember. That improvisation tends to favour whatever was most visible, which is rarely the most valuable thing you did.

The remedy is to propose the measure yourself, early, in writing and modestly. Two or three things that would indicate the role is working, agreed with your manager in the first couple of months, will shape every subsequent conversation about your performance. If they will not engage with that at all, you have learned something important about how much thought went into creating the post.

Scope expands to fill a vacuum

A role without defined edges attracts everything that has no other home. Tasks that nobody wanted, requests that fit no existing team, and the residue of old reorganisations will all drift towards the new person, and each individual arrival is small enough that refusing looks unreasonable.

Say yes to some of it deliberately, because in the first months this is how you learn where the work actually lives and who is under pressure. But keep a written record of what has accreted, and revisit it at a fixed point — the end of a quarter is a natural one — with a straightforward summary of what the role has become. Making the drift visible is usually enough to stop the parts of it that nobody actually intended.

You will have to explain yourself repeatedly

Colleagues understand established roles by pattern recognition. Yours will not fit a pattern, so people will not know when to involve you, and the most common failure of a new post is not that it is done badly but that it is routed around by people who never learned it existed.

That is fixed by unglamorous repetition. Say what you do in a sentence, use the same sentence consistently, and go and find the two or three teams whose work most obviously touches yours rather than waiting to be introduced. It feels like self-promotion and it is really just signposting, which somebody has to do and which nobody else has any reason to.

Sometimes the role should not have been created

It is worth admitting that a proportion of new posts are a response to a structural problem that a hire cannot fix — a process that does not work, a team that is short of capacity, or a disagreement between two departments that has been converted into a job advert. In those cases the person appointed is set up to fail politely, and no amount of clarity from them changes the underlying arithmetic.

The signals are reasonably legible within six months. Nobody can name what the role should achieve, the sponsor who argued for it has moved on, or the work you are given is precisely the work two teams were already fighting over. None of that is a comment on you. It is a comment on the decision, and treating it as personal will keep you there longer than the situation warrants.