All articles

    How to Have a Career Growth Conversation With Your Manager

    By Izzy H. · Published June 15, 2026

    The conversation that changed my trajectory wasn't a review. It was thirty minutes I almost didn't ask for, because asking felt like overstepping — like I hadn't earned a talk about the future yet. The review that quarter had been all numbers; the part about where I was actually headed got two rushed minutes at the end, if that. So I booked a separate slot and said plainly that it was about direction, not performance. Nothing was on the line, and that was exactly why it worked. Here is how to run that conversation on purpose, including the part nobody prepares for.

    Why this conversation can't wait for review season

    A performance review answers a backward-looking question: how did the last cycle go. A growth conversation answers a forward one: what should the next cycle build. Folding the second into the first guarantees it loses, because ratings and compensation suck the oxygen out of the room. The moment money is on the table, both of you start negotiating, and nobody develops anyone mid-negotiation.

    The fix is to hold the growth conversation on its own, off-cycle, with no rating attached. The companies that moved to continuous check-ins did it for exactly this reason — the annual snapshot was the wrong container for development. You can make the same move unilaterally: book thirty minutes that is explicitly about trajectory, not performance, and say so when you book it.

    The conversation managers are actually equipped to have

    Managers are the largest single factor in how engaged people are at work, and development conversations are where a lot of that influence lands. But there is a catch most advice skips: a manager can only give a good answer to a good question. 'Where do I stand?' invites a shrug or a platitude. 'I want to move from owning features to owning a domain — what would you need to see?' invites a real answer, because it gives them something concrete to react to.

    So the burden of a good growth conversation is mostly on the person asking for it. Come with the direction half-formed and the evidence in hand, and you convert your manager from a judge into a collaborator — which is the role most of them would rather play anyway.

    What to bring

    Three things, none of which take long if you have been keeping a record. A direction: where you want to grow, stated as a shift in scope or capability rather than a title. Evidence: two or three dated examples of the work that points that way already. And one specific ask: the assignment, exposure, or feedback that would move you toward it. The ask is what separates a growth conversation from a venting session.

    If you have been scoring your own growth across the six signals — scope, skills, autonomy, network, judgment, options — you already have the raw material. The conversation is largely reading two of those lines aloud and asking your manager to react.

    Bloomly turns a quarter of captured work into the prep for this exact conversation — the recent wins, the skills that moved, the themes worth raising — so you walk in with evidence instead of a vague sense that you've grown.

    A script that works

    The opener

    Name the frame so it does not get mistaken for a review or a raise request. 'I wanted to use this time on where I'm headed, not how last quarter went — is that alright?' This one sentence does a lot: it lowers the stakes, signals you have thought about it, and gives your manager permission to be candid rather than evaluative.

    The direction and the evidence

    State the shift, then back it with work. 'I want to grow from running individual features to owning a domain. I think it's already started — I led the export rewrite end to end and I've been the one unblocking the portal team. I want your read on whether that's the right direction and what the gap is.' Specific goals outperform vague ones for the same reason here as everywhere: they give the other person a target to aim at.

    The ask and the close

    Propose the work rather than requesting a verdict. 'Could I own the next cross-team migration as a stretch? And would you point out where my judgment isn't there yet, in the moment, so I can close it?' Then close by writing down what you agreed: the assignment, the feedback loop, the date you will revisit it. A growth conversation with no recorded commitment is a nice chat that evaporates.

    Questions that move it forward

    • What does the next level actually look like in practice on this team — not the rubric, the real version?
    • Where do you see my judgment as not-yet-there, and what would change your mind?
    • What's a piece of work coming up that would stretch me toward the direction I described?
    • Whose career here looks like the one I'm describing, and what did they do that I'm not?
    • If we have this conversation again in a quarter, what would tell us it went well?

    What to do after

    The conversation is worthless if it lives only in your manager's memory and yours — both decay, and neither is on record when the next review needs receipts. Write down what was said within the hour: the direction you aligned on, the assignment they offered, the gap they named, the date you set. That note becomes the agenda for the next conversation and the spine of the eventual case.

    Then feed it into the plan. A growth conversation that does not change your development plan was entertainment. Translate the assignment and the gap into a row you will actually work, and track the evidence as you go so the next quarter's conversation opens with proof instead of recollection.

    When the answer is no (or 'not yet')

    Sometimes the direction is not available — no headcount, no domain to own, a manager who cannot sponsor it. The mistake is to treat that as a closed door. Ask the diagnostic question instead: 'Is it a gap in me, a timing problem, or a structural one?' The three answers point three different ways. A gap is a development plan. Timing is a date to revisit. Structural means the growth you want may not exist here — useful, if unwelcome, information.

    And keep the record either way. The research on advocating for yourself is blunt: people who never make the case pay for it across a career, often six figures or more. The case is not a single dramatic ask — it is a series of these conversations, each one building on the last, each one on record. A 'not yet' you tracked is worth more than a 'yes' you forgot.

    Bloomly is the career journal app for this exact workflow.

    Track wins, generate Period Recaps, get a performance review draft on demand.

    The second growth conversation is always easier than the first, because it opens with what you both said last time instead of a cold start. Book one this month, off review season. Bring two pieces of evidence and one real ask. Write down what you agree to before you leave the room. Then have it again next quarter — that quiet compounding, one conversation building on the last, is what actually moves a career.

    Bloomly is the career journal app for this exact workflow.

    Track wins, generate Period Recaps, get a performance review draft on demand.

    Frequently asked questions

    How do I start a career growth conversation with my manager?

    Book thirty minutes off-cycle and frame it explicitly: 'I want to use this time on where I'm headed, not how last quarter went.' That one sentence lowers the stakes and gives your manager permission to be candid rather than evaluative. Then bring a direction, two or three pieces of evidence, and one specific ask.

    What should I talk about in a career development conversation?

    A direction stated as a shift in scope or capability (not a title), evidence that the shift has already started, and one concrete ask — an assignment, exposure, or feedback loop that moves you toward it. Avoid 'where do I stand?'; it invites a platitude. Specific questions get specific answers.

    Should I talk about growth in my performance review?

    Hold it separately. A review is backward-looking and has ratings and pay attached, which crowds out development and turns the room into a negotiation. Schedule the growth conversation off-cycle with nothing on the line — that's the container development actually fits in.

    What if my manager says I'm not ready for the next level?

    Ask whether it's a gap in you, a timing issue, or a structural one — the three answers point three different ways. A gap becomes a development plan, timing becomes a date to revisit, and structural tells you the growth you want may not exist here. Record the answer either way; a tracked 'not yet' beats a forgotten 'yes.'

    How often should I have growth conversations with my manager?

    Quarterly is a good default — frequent enough that commitments don't drift, rare enough to show real movement between them. Each one should open with the evidence accumulated since the last, which is why keeping a running record between conversations matters more than the conversation itself.

    Sources

    Claims in this article are backed by the following published sources.

    1. Gallup (2024). State of the Global Workplace Report. Gallup. Read

      Multi-year employee engagement data — basis for claims about how rare effective recognition and feedback are inside organizations.

    2. Cappelli, P. & Tavis, A. (2016). The Performance Management Revolution. Harvard Business Review. Read

      Industry-defining piece on the shift from annual reviews to continuous feedback at Adobe, Deloitte, Microsoft, GE, and others.

    3. Babcock, L. & Laschever, S. (2003). Women Don't Ask: Negotiation and the Gender Divide. Princeton University Press. Read

      Estimates that workers who fail to negotiate compensation can lose hundreds of thousands to over $1M across a career — the source for the $1M loss-aversion anchor on the homepage.

    4. Locke, E. A. & Latham, G. P. (2002). Building a Practically Useful Theory of Goal Setting and Task Motivation: A 35-Year Odyssey. American Psychologist, 57(9). Read

      35 years of goal-setting research showing specific, difficult goals produce higher performance than vague 'do your best' goals — the basis for claims that vague development goals fail and evidence-checkable goals work.