There is a moment, somewhere between the first serious doubt and the first serious application, when you have to decide whether your manager gets to know. Most career advice skips straight past it to the resignation letter. The conversation before that one is harder, because you are asking someone to help you grow out of the shape they hired you for.
First work out whether telling helps you or costs you
This is not a question about honesty. It is a question about incentives, yours and your manager's, and the two are rarely aligned.
Telling helps you when:
- There is a real internal path. The direction you want exists somewhere inside your employer, and at least one person has actually moved into it. Not "we support internal mobility" on a slide. A named human who did it.
- Your manager has a track record of backing moves. Watch what happened to the person who left his team for another one last spring. Did he help, or did he go quiet for six months? Behaviour predicts behaviour. Stated values predict nothing.
- You need something operational. Study leave, a four-day week, two weeks off around an exam, a smaller portfolio for a quarter. You cannot get any of that without explaining why you want it.
- The story will leak anyway. If you are taking a visible certification, or you have asked three people in another department for coffee, someone will mention it. Better that your manager hears your version first.
It costs you when you are on probation, on a fixed-term contract, or on a visa attached to your current role. It costs you when the team is under headcount pressure and someone upstairs is drawing up a list. It costs you when review or bonus season is within about eight weeks, because "not fully committed" is a cheap way to move you down a ranking and nobody ever writes it down. And it costs you when your manager is measured on retention or on your specific output, which means his interest is to keep you exactly where you are for as long as possible.
If you cannot name what you want your manager to do differently after the conversation, you are not informing him. You are confessing.
When you are unsure, the answer is not yet
Silence is reversible. Disclosure is not. So the default position, when the case is genuinely balanced, is to say nothing for now and run a quiet search in parallel to see what your options actually look like from the outside. Our guide to a discreet LinkedIn job search while employed covers how to do that without lighting up your network.
Give yourself a checkpoint. Three months, then re-read this section with what you have learned. A vague intention to "tell him eventually" turns into a leak you did not control.
Timing: after the plan, never during the doubt
Wait until you have something that qualifies as a plan. That means three things: a direction you can name in one sentence, some evidence you have already started, and a rough horizon. Without those, you are handing your manager a problem and asking him to solve it, and the solution he picks may not be one you like.
Then pick the slot carefully. Not inside a performance review, where anything you say gets filed as a rating input. Not on a Friday afternoon, when there is a weekend of silence for him to fill with his own interpretation. Not the week a bad quarter lands. Ask for thirty minutes on your own initiative, midweek, morning. Owning the calendar invite matters more than it sounds.
Frame it as a direction, not a complaint
Two sentences carry the same underlying truth and produce completely different outcomes.
"I am bored, this role is not really for me" makes you a problem to be managed. "Over the past year I have been pulled toward data work, I finished a certification in March, and I want to build toward that" gives your manager something he can attach himself to. Some of them like being able to say they developed someone.
Three things to keep out of the room. Do not compare yourself to a colleague who got the move you wanted. Do not criticise the team, even accurately. Do not attach money to it, because the moment salary enters, the conversation becomes a negotiation and your direction becomes a bargaining chip. If your change also has a funding question behind it, that belongs in your own planning, not in his office. Our piece on how to fund a career change is a better place for it.
Three openers for three situations
When an internal move is genuinely possible. "I want to be straight with you about where I am trying to go. I have been working toward the product side for about nine months, and I have done X and Y on my own time. I would rather build that here than somewhere else. Can we talk about what it would take?"
When there is no internal path. "I want you to hear this from me rather than from someone else. I am building toward something this organisation does not do. That means at some point it means leaving, though not in the next few months, and I want to hand over properly when it happens. I would like your advice on timing." This one is expensive. Use it only when the relationship is genuinely solid and you can afford the downside.
When you do not trust your manager. Narrow the ask until it is unremarkable. "I would like to get better at SQL because it would help me on the reporting work. Is there any budget for a course this quarter?" Every word is true. None of it is the whole plan. You are not obliged to hand over the whole plan.
Ask for one concrete thing
Vague conversations produce vague outcomes. Walk in with a single specific request:
- A secondment, two or three days a week for one quarter.
- A shadowing week with the team you are aiming at.
- A project on the side of your desk, ideally one nobody currently owns.
- A training budget, with the course name and the price already found.
- An introduction to a lead in another team, made by him, by a date.
If the internal route turns out to be real, you will eventually put it in writing as a formal application, and a cover letter for an internal transfer is its own exercise.
What happens after you have said it
Expect one of three reactions.
He takes it badly. Cooler tone, "I am surprised", and within a month you are off a planning invite. Do not argue about the reaction. Reassert your delivery in writing, keep your commitments visible, and move faster than you originally planned.
He becomes an advocate. Real, and better than most people expect. Convert it fast, because verbal support decays. Get a date, a name, and a mechanism in the same week, while the goodwill is fresh.
He says nothing. This is the most common and the most damaging. He nods, says he will think about it, and three weeks later your best project has quietly gone to someone else "for continuity". That is usually not malice. It is a manager doing risk planning with the information you gave him.
Whatever the reaction, send the same short email within a day: what you asked for, what he said, what happens next, and by when. Friendly, three lines, no ultimatum. It costs nothing and it means the conversation exists somewhere other than in his memory.
It cannot be unsaid
That is the honest part. There is no version where you mention this and your manager fully forgets it. He will factor it into next year's staffing whether or not he supports you.
So before you book anything, finish this sentence in writing: "In the next ninety days, I want my manager to ___." If you cannot complete it with something specific, you are not ready to have the conversation. Run the quiet route for another month and come back to the sentence.