🤖ReplacedByAI
✨ Powered by GPT-4o

Told Your Role Is Being Merged with Another? What to Do First

Being moved to a role that doesn’t exist yet, being told your role is at risk, telling a manager the job isn’t the job, being asked to sign new terms — every one of those has exactly onejob in it, and it’s yours. This is the only conversation here where half the job belongs to somebody else: a person sitting in the same organisation, in the same conversation from the other side, whose employment isn’t yours to describe. Three things follow. Nothing here rules on what happens to them — not leaving, not displaced, not kept, and never which of you ends up with it — and nothing here lets them into your message, which is the mirror error and the commoner one, because naming them feels like honesty: “I understand the other role is going too” turns a question about your own job into a statement about somebody else’s, inside a document you don’t control, and gets answered as a comment on the restructure. A merged role is described by addition and worked by subtraction: you’ve been handed two sets of duties added together and nobody has said what comes out. So this won’t tell you it’s two jobs for one salary or that you’re being set up to fail — and it won’t reassure you that it’ll settle down or that duplicated work falls away either. What’s answerable is what the combined role owns and what’s being stopped, because a merger with nothing named as coming out is an addition described as a merger. And the half you don’t hold is the whole question: you can describe your own work in detail, and for the other one you have a title. You get what to write down first, the five questions to ask in writing, who can actually answer them, the message at no more than 118 words that argues for nothing, the five things to leave out, the three replies that come back, and four questions this page won’t answer — each with the person, function or document that holds it.

Sample merged role plan

Generated for: Operations Coordinator, told at Thursday's team meeting that my role and the Client Services Manager role are becoming one from January, both sets of duties on a slide, nothing said about what stops, the other role is held by a colleague I work with every day, I've been covering half of it since March and said I could probably manage it

Write this down before you ask anything — What your role owns today is half of the only comparison there is, and it is the half nobody else has in front of them. For the other half you have a title, and a title is the narrowest possible description of a job. Every step below costs nothing and commits you to nothing. Write your own role out task by task. Write down the exact words you were told, by whom, and when. Note what of the other half has already started arriving, as fact and not as a grievance. Note the date it is said to take effect. Say nothing yet, to anybody, about whether you could manage it.

The real one is written against what your own role actually owns, what you were actually told, and whatever you can say about the other half — and it never invents the other role, never tells you whether it is two jobs for one person, never says a word about whoever holds the other half, and never rules on whether you can be required to take it. The opening of yours is free — no card, no account. One credit finishes it. See what a credit costs.

First one is free — no card needed.

Credits

— credits available

This is the single input that most changes the advice, and it’s the one almost nobody can fill in properly — which is the point. You can describe your own work in detail; for the other half you have a title, and a title is the narrowest possible description of a job. Put down whatever you’ve actually been told, even if it’s one word. Nothing here infers the work from the name of the role, and nothing treats overlap you assume as overlap that exists. If you leave it blank that comes back as the first thing to go and retrieve, never as a role this page invented. An invented other half isn’t a weak sentence: it’s a description of somebody else’s job, written by a stranger, handed to the people designing the merger, and read as your own account of what you’re taking on.

Who writes a job description, and who can tell you what a combined role would own, is completely different at a 40-person firm and somewhere with a people team, a grading framework and a written restructure policy, so a sentence about the place is worth giving — but it comes back as context for the routing, never as a description of how that employer runs reorganisations, what it usually does, or how likely it is to change anything. No real name is needed and none goes into the draft.

These aren’t the same conversation, and which one you’re in decides who can usefully answer you. A colleague holds the other roleis where the commonest and most expensive error lives, so it’s handled hardest: the only job this page will work on is yours, and they belong in no message, no question and no note. The other role is vacant is the easiest half to describe and the hardest to price, because nobody is defending it and the work has already been landing somewhere. I’ve been sent both job descriptions looks like the whole answer and isn’t: a job description lists what a role owns and none has ever listed what it costs to own it. I’ve already said I can manage itis the one people arrive on most worried: it won’t tell you what that did, and it won’t coach a retraction or an apology either; it adds the questions instead. Nothing here tells you this is serious — and nothing tells you it isn’t.

This decides which section gets written. Get it described in writingis the cheapest thing on the page and the only move that keeps every option open: a structure isn’t a job, and a numbered list gets answered line by line while a paragraph gets answered with reassurance. What comes OUT of the jobis the right question and the one nobody answers unprompted — but it’s asked about the design of the role, never about your capacity, and this section will not let you volunteer what you’d drop, because a concession offered before anybody asked is answered as an agreement that everything else is manageable. The half I don’t holdis retrieval: the other role’s written description, the cycle it runs on, what falls due when, what’s currently late or unowned — and not one question about the person who holds it. Buy time turns on something readers get wrong: an ask for time is granted when it carries a reason about understanding the role and a date you name, and read as a position when it carries a reason about whether you want it.

Give both halves, because they do different work: what you’ve been told— when, by whom, in what form, what words were used, what date it takes effect — and what has happened since: whether any of the other half has already started arriving, whether anything is in writing, what you said back. Without that second half the plan can only ask about the announcement. No name is needed and none goes into the draft: not whoever announced it, not your manager, not whoever decided it, not HR, and above all not whoever holds the other role — the only job this page works on is yours, because a colleague named in your message is somebody else’s employment inside a document you don’t control. Nothing here rules on whether the combined role is doable, whether it’s two jobs for one salary, whether you’re being set up to fail — or, in the other direction, that it’ll settle down and the duplicated work will fall away. Nothing here rules on whether you can be required to take it, whether you can decline, or what saying you could manage it already committed you to. Those go to whoever is designing it, to your employer’s own written policy, to a representative where one exists, and to somebody qualified where you live. We never invent or infer the other half from its title, so anything you don’t supply comes back as a bracketed placeholder telling you who to ask. And nothing here writes a case for keeping your job as it is, a pitch for being the one who gets the combined role, an application, a grievance or a legal threat — nor raises pay, which is the first place readers reach when two jobs become one and the fastest way to lose the description.

Powered by GPT-4o • Takes ~15 seconds