# Sample Email to a Manager for Career Growth: What to Actually Send Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/sample-email-to-manager-for-career-growth/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/sample-email-to-manager-for-career-growth.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving working with your manager at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer A short sample email to a manager for career growth, plus what to leave out, what the subject line should say, and how to ask without sounding entitled. ## Key facts - Title: Sample Email to a Manager for Career Growth: What to Actually Send - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Communication, Influence - Primary keyword: sample email to manager for career growth - Source page: https://headwayskills.com/knowledge/working-with-your-manager/sample-email-to-manager-for-career-growth/ ## What this page covers - A short sample email to a manager for career growth, plus what to leave out, what the subject line should say, and how to ask without sounding entitled. - Practical guidance for sample email to manager for career growth - How this topic connects to Working with Your Manager ## Detailed explanation You have written the email. You have rewritten it. It is still sitting there unsent, because every version either sounds like you are begging or like you are threatening to leave. A good sample email to a manager for career growth is short — around 200 words at most — and it does not make your case. It names the topic, asks for a dedicated half hour, and gives your manager time to prepare. The case gets made in the conversation, not in the inbox. That one distinction explains most of what follows, including why almost every template you will find online is longer than it needs to be. ## What does a good sample email to a manager for career growth look like? Here is a version you can adapt in about two minutes: > **Subject:** Time to talk about my development > > Hi [Name], > > I have been thinking about where I want to develop over the next year, and I would value your perspective before I get too far into my own conclusions. > > Could we find 30 minutes in the next couple of weeks? I would like development to be the only thing on the agenda, so it does not have to compete with our usual one-on-one. > > Happy to work around your calendar. > > Thanks, > [Your name] Notice what it leaves out. No list of accomplishments, no job title you are aiming for, no argument about why you have earned something. All of that belongs in the room, where your manager can respond and you can respond back. Templates that front-load the case are trying to win an argument by email, which is the wrong medium for one. ## How do I ask about career growth without sounding entitled? Change what you are asking for. Entitlement lives in the shape of the request rather than the wording: asking your manager to give you something reads as a claim, while asking for their perspective reads as an invitation. The second version is also the more accurate one. As McKinsey puts it in its guide to getting unstuck, neither your organization nor your manager is in charge of your next step — you are. What your manager holds is context you do not have: what is coming next quarter, where the budget sits, which work is about to need someone. You are asking for that context, not for a favor. One more thing to leave out: any hint that you are considering leaving. Even a mild one turns a development conversation into a retention conversation, and those go somewhere else entirely. ## What should the subject line say? Say what the meeting is about. The template collections that dominate this search, including status.net and Plandaction, converge on naming the topic in the subject line so your manager can prepare — and there is a second reason they tend not to mention. An unlabeled meeting request from a direct report reads as bad news. A subject line like "Quick chat?" leaves your manager opening their calendar wondering whether you are about to resign. Naming development in the subject tells them it is forward-looking and low-stakes before they have read a word of the body. ## How long should the email be? Under 200 words, which is the ceiling Routine recommends in its guide to this exact email, and shorter is fine. The reason is mechanical rather than stylistic. Career growth involves tradeoffs your manager cannot resolve alone — headcount, budget cycles, what the team needs next quarter. A long written case invites a short written deflection, because answering it properly would cost them half an hour they do not have at their desk. A short request invites a meeting, because agreeing to 30 minutes is easy. The 400-word template you found is not more persuasive — just easier to say no to. ## What if I do not know what I want yet? Send it anyway, and be honest that you are still working it out. Most advice tells you to arrive with your goals already defined. CareerBuilder suggests putting them into [SMART form](/knowledge/setting-goals/smart-goals-examples/) first, and RecruitMyMom recommends researching internal paths and talking to people in other departments beforehand. That is useful preparation, and if you have time for it, do it. But treating it as a prerequisite is how the email stays unsent for six months. What changes is the framing, not the decision to write. Instead of saying you want to move toward a specific role, you are asking your manager to help you see what is actually available and where they think you would do well. Managers generally find that easier to answer, not harder. It still helps to arrive with a rough sense of [your own strengths](/knowledge/self-awareness/how-to-identify-your-strengths/), even a provisional one, so the conversation has something to work from. If you are not sure how to put yours into words, [naming your strongest work skills](https://assessment.headwayskills.com/) is a reasonable place to start before you book the meeting. ## When should I send it — do I have to wait for my performance review? No, and waiting carries a cost: by the time the review comes around, next year's plans are often already set. Development conversations also work better when they are not sharing a table with [an evaluation of last year's work](/knowledge/working-with-your-manager/performance-review-preparation/). That said, an existing cycle is a low-friction way in if raising it cold feels like too much. A version of this question comes up repeatedly on career forums such as CareerVillage — asking whether there is a mid-year or annual review form you could fill out to discuss your progression. Routing the ask through a mechanism that already exists makes it feel procedural rather than personal, which is exactly what you want when you are nervous about it. ## Should I ask about a promotion or about development? They are different emails and they get different answers. There is a whole separate cluster of promotion-email templates online — Maestrolabs and others publish them — and those are built to request a decision: here is what I have delivered, here is the title I want. A career growth email requests a conversation instead. Blurring the two is the most common reason this email feels risky to send. If [the promotion](/knowledge/working-with-your-manager/how-to-ask-for-a-promotion/) is what you want, the growth conversation is usually the step before it: it is where you find out what the bar is, and whether anyone is holding a slot. Ask for the decision before you have had that conversation and you are guessing at what your manager is even able to say yes to. ## What if my manager says there is no room to grow right now? Treat it as information rather than a verdict. The Muse's guidance on career conversations is that aspirations which do not line up with what the team currently needs are not a refusal — they mean a longer runway, or a path that has to be built rather than stepped into. The useful follow-up questions are concrete ones. What would need to be true for this to become possible? Is that six months away or two years? A manager who cannot offer a role now can often offer a project, a stretch assignment, or an introduction elsewhere in the organization — and those are what make the next version of this conversation go differently. ## Should I follow up after the conversation? Yes, with a short message the same day or the next. Summarize what you understood and what either of you said you would do. Two or three lines, no formality. This is the one part of the process where writing genuinely beats talking. It gives you both a shared record, catches misunderstandings while they are still cheap to fix, and leaves a thread to pick up in three months instead of starting over. ## What actually makes this conversation go well Read back across those answers and one thing keeps recurring: hardly any of the difficulty sits in the wording. It sits in understanding what your manager is actually able to do, in choosing the right channel for the right part of the message, and in making an ask that someone has a reason to say yes to. Those are all things people get better at with practice. **Working with Your Manager** is doing most of the work here. It treats the relationship as a partnership rather than a hierarchy you petition — your manager has their own constraints and their own boss, and holding that in mind changes what you write. It is also the skill behind everything that comes after the email lands: aligning on what good looks like, agreeing goals that are challenging without being unrealistic, and shaping the content of your own job instead of waiting to be assigned it. **Communication** is why a 150-word email beats a 400-word one. The judgment underneath is about medium. Some things belong in writing; some belong in a conversation because they are complex, relational, or need negotiating, and career growth is squarely the second kind. Leading with your main point, keeping it brief, and writing a subject line that tells the reader what they are opening are the mechanics — but picking the channel correctly is what makes the mechanics count. **Influence** covers the part the templates never explain: why anyone should say yes. Preparing well means understanding what is in it for the other person and how decisions actually get made where you work, so that wanting to grow turns into something specific your manager has a reason to want too. It is also where the nerve comes from — being willing to ask at all, given that the worst available answer is no, and taking a smaller win when the full one is not on the table yet. None of the three is a fixed trait, and none of them is where the list ends: **the framework counts twelve**, and the free Job Skills Test walks through all of them. Once your manager does open a door, knowing **[which skills to build first](https://assessment.headwayskills.com/)** turns out to be more useful than another template. ## This is more familiar than it feels Some of this may already describe how you operate. You might notice that you think about what your manager is dealing with before you ask them for anything, or that you are the one who sends the summary after a meeting. These are behaviors rather than dispositions, and the version of you who raises this comfortably in two years is built out of the version who sends one slightly uncomfortable email now. They also carry further than this single conversation. The more responsibility you take on, the more of your work runs through other people's decisions — and the skills that get a development meeting booked are the same ones that later get a project approved. You have already done the part most people skip. You did not just want to grow; you sat down to work out how to say so. What is left is knowing which of these skills to put your weight behind first. ## Where your own skills stand The email is a small thing. What sits behind it — knowing how to work with the person you report to, and how to ask for something in a way that makes it easy to say yes — is worth knowing about yourself with a bit more precision. The Job Skills Test is a **free** self-assessment of your work skills. It takes about seven minutes, it covers all twelve of the skills this framework treats as learnable, and it shows you where you currently stand on each one, including the three above. There is nothing to prepare and no right answer to give. Whenever you are ready, it is a sensible thing to do just before you send the email — or just after. **Get my skills profile** *Free · 7 minutes · results shown instantly* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? A short sample email to a manager for career growth, plus what to leave out, what the subject line should say, and how to ask without sounding entitled. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Communication, Influence. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/working-with-your-manager.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/working-with-your-manager/sample-email-to-manager-for-career-growth/ Preferred summary: "A short sample email to a manager for career growth, plus what to leave out, what the subject line should say, and how to ask without sounding entitled." ## Change log - 2026-07-07: Content collection version published.