Career Goals and Progression Questions

Direct answer

The first twelve to eighteen months of moving from individual contributor into management are mostly about earning trust for a different kind of value: your team needs to see you multiplying their work rather than still trying to do the work yourself, and your own manager needs to see you build the operating rhythm, hiring, feedback, prioritization, that makes a team reliable without you personally in the room. Whatever the exact destination, a first-line manager role, a team lead role, or eventually a director-level path, the throughline is the same: build trust and credibility with the team you're now leading, not doing the work of.

Structured elaboration

Months 0-3, foundation. Skill: run the basic operating cadence (1:1s, priority-setting, unblocking). Activity: deliberately step back from doing the hands-on work yourself even when it's faster to just do it. Trust signal to watch for: the team starts bringing you problems before they're on fire, not after.

Months 3-9, establish credibility as a manager, not a former doer. Skill: give feedback that lands, specific and timely, and start shaping staffing and hiring decisions. Activity: run one real, visible decision, a prioritization call or a hard feedback conversation, and let the outcome speak for itself. Trust signal: a team member takes on stretch work because you pushed them to, and it goes well without your direct hand on it.

Months 9-18, scale and generalize. Skill: operate one level of abstraction up, setting direction across more than one initiative and representing the team upward and outward. Activity: depending on the destination, this might mean taking on a second team or deepening influence within the current one. Trust signal: the team performs well on a stretch even when you're out for a week, the real test of whether you've built a team rather than a dependency on yourself.

The phases repeat at larger scope whether the destination is first-line management, a team-lead role, or eventually a director-level path. The mechanism doesn't change, only the size of the team and the level of abstraction.

Worked example

"The hardest part of my own version of this transition wasn't learning the calendar mechanics of being a manager, it was the moment early on when I watched a mistake happen on a piece of hands-on work I used to own, and let the person make it and recover on their own instead of quietly fixing it overnight. I did that on purpose a few times in the first couple of months. By around month six, one of my reports took the lead on something genuinely hard without me in the loop until the decision was basically made, and it held up. That was the first time it felt like the team trusted my judgment as a manager, rather than just remembering me as a strong individual contributor who'd moved up."

Trade-offs & pitfalls

• The most common failure mode: continuing to do the hands-on work yourself under the manager title, because it's faster in the moment, which prevents the team from ever seeing you in the new role.
• Rushing credibility by asserting authority rather than earning it through visible, fair decisions.
• Under-investing in the coaching and feedback skill because it feels softer than the technical skill you're used to being judged on.
• Treating the twelve-to-eighteen-month plan as fixed regardless of destination. A first-line management plan and a longer director-track plan share the same mechanism but not the same scope, so naming which one you're aiming at matters.
• Neglecting to name a signal for whether this is actually working, so the transition just drifts rather than being checked against real evidence.

Direct answer

Treat the choice like a hypothesis worth testing cheaply before committing years to it: weigh the personal pull you already feel toward a specific part of your current workflow against external signal, where your organization or the market is actually investing, then run a small, time-boxed validation before fully committing.

Structured elaboration

• Factors to weigh: personal pull (the lightest-weight version of this question is simply which part of your current workflow you already find yourself wanting to deepen next), organizational trajectory (where your company or industry is actually investing), durability (is this likely to matter in several years or is it a narrow fad), and transferability (how much of the skill still carries over if the bet turns out wrong).
• State the hypothesis explicitly. Something like "depth in this direction will make me more valuable and more capable of X," rather than committing on a vague sense that it seems interesting.
• Validate cheaply before committing. A short, deliberately scoped trial project measured in weeks rather than years, informational conversations with people already deep in that direction, and a check against real market-demand signals, what's actually being hired for or invested in around you, rather than a single trend or headline.
• Set a deliberate decision checkpoint after the validation window: commit harder, pivot, or abandon. Don't let a time-boxed trial quietly become the multi-year commitment by default without a real re-decision.

Worked example

Rather than picking a multi-year direction cold, I started from what I was already gravitating toward inside my current work, the part of the job I'd stay late on even when nobody asked. I treated that pull as a hypothesis rather than a conclusion: I spent a few weeks on a small, deliberately scoped side project in that direction and talked to people already working in it about what the day-to-day looks like once the novelty wears off. I also checked it against real market-demand signals, what was actually being invested in around me, not just where I personally found it interesting, since a direction with no organizational pull is a much harder multi-year bet. Only after that validation window did I commit to it as a focus, with a deliberate check-in point rather than letting the trial quietly become the decision by default.

Trade-offs & pitfalls

• Committing years on personal interest alone, with no external demand signal, risks specializing into something the market or your organization doesn't actually value.
• Committing purely on market demand with no personal pull risks burnout in a direction you don't actually want to spend years in.
• Skipping validation and committing on a single conversation or a trend headline is the most common shortcut, and the most common regret.
• Letting a time-boxed trial silently become the multi-year commitment without a deliberate re-decision point.

Direct answer

Track a small mix of signals across a few categories: ownership and scope, what decisions and outcomes you're trusted with now versus a few months ago, skill evidence, things you can now do that you couldn't before, and external signal, feedback you actively solicit rather than wait for, reviewed on a set cadence so busyness doesn't get mistaken for progress.

Structured elaboration

Ownership and scope signal. Periodically write down, in a sentence or two, what you're currently trusted to decide or own without checking in first, and compare it to the same note from a few months earlier. If it reads the same, that's useful information regardless of how busy you've been.

Skill evidence signal. Keep a short, honest log of specific instances where you did something you genuinely couldn't have done a few months prior, a list of capability demonstrated, not a list of tasks completed.

External signal, actively solicited. The input side of tracking is asking for feedback on a regular cadence rather than waiting for a formal review to surface it. Pick one or two people whose judgment you trust, a manager, a peer, a cross-functional partner, ask a specific rather than generic question, do it on a set interval so the answers accumulate into a trend, and use that same conversation to show your manager concrete evidence of the movement you've tracked, not just to ask how you're doing.

Keep yourself honest. At each check, ask whether the evidence you've gathered would convince someone who doesn't already like you, not just whether you feel you've been busy. Busyness isn't itself a metric, the ownership, skill, and feedback signals above are proxies for actual movement.

Worked example

"Every few months I set aside a short amount of time to update three things: a one-line note on what I currently own without checking in, a short log entry on anything I did recently that I genuinely couldn't have done before, and a specific question I asked one trusted colleague or my manager about what was still holding me back. One quarter my log of things I did looked long and I felt productive, but my ownership note hadn't changed at all from the previous check, and when I asked my manager the specific question, the answer named a gap I hadn't noticed because I'd been focused on volume rather than scope. That mismatch, feeling busy while the ownership and feedback signals were flat, was the useful signal, and it redirected my effort the following quarter toward the specific gap rather than more of the same work."

Trade-offs & pitfalls

• Treating task completion as the metric rewards busyness and tells you nothing about whether your scope or trust is actually growing.
• Waiting for a formal review cycle to get feedback means the signal arrives too infrequently and too late to redirect effort.
• Asking for feedback with a generic question, how am I doing, tends to produce generic, unhelpful answers. A specific question produces something you can act on.
• Tracking too many metrics becomes its own busywork. A small, consistent set reviewed honestly beats an elaborate dashboard reviewed rarely.

Direct answer

The move is to separate diagnosis from reaction: before assuming the gap is unfair (inconsistent criteria, an indifferent manager) or purely a personal failing, do an honest, evidence-based audit of your own case first, then act on what you actually find rather than on the story you started with. That self-diagnosis is what keeps the response grounded instead of either resigned or entitled.

Structured elaboration

1. Name the trigger honestly, whatever it actually is: no advancement across two review cycles, criteria that seem to shift depending on who's managing you, or just a general sense of plateauing. Treat it as a starting observation, not a verdict.
2. Diagnose before reacting. Audit your own evidence (scope actually carried, outcomes attributable to you, feedback received) against whatever the organization's stated or informal bar is. Separately, note if the bar itself looks inconsistent or unclear across managers, that's useful information, not an excuse to skip the audit.
3. Have the direct conversation. Bring your honest self-assessment to your manager and ask explicitly what's missing, rather than silently accumulating resentment or silently giving up on the goal.
4. Decide on a bounded response. Set a real timeframe to see change, and know your own answer for what you'd do if nothing changes, without turning that into an ultimatum in the room.

Worked example

"At one point I'd gone through two review cycles without the scope change I was expecting, and it would have been easy to decide either that the process was broken or that I just wasn't good enough. Instead I sat down and mapped what I could actually point to: had I taken on next-level work, could I show outcomes that were mine, had anyone besides me confirmed it. Some of it held up, some didn't, there was a specific kind of cross-team decision I'd been avoiding making solo. I brought that honest picture to my manager instead of a complaint, asked directly what was missing from their side, and used what came back to set a concrete plan with a real check-in date rather than just waiting quietly for the next cycle."

Trade-offs & pitfalls

• Skipping the self-diagnosis and going straight to a conversation framed as a grievance is the entitled failure mode interviewers are listening for.
• Quietly disengaging or lowering your own ambition instead of raising the issue is the opposite failure mode, and just as costly.
• Blaming inconsistent criteria across managers without also checking your own evidence dodges the harder, more useful half of the question.
• Setting no real timeframe for reassessment lets "wait and see" drift indefinitely. A grounded answer names when you'd revisit the decision.

Direct answer

Start from a specific, named skill gap rather than "wanting a mentor" generally, then find someone with direct experience closing that exact gap and structure the relationship around a concrete cadence and deliverable, not just occasional check-ins.

Structured elaboration

• Start with the gap, not the relationship. Name the specific capability you're missing, not "I want a mentor," but "I need someone who's actually navigated this exact problem."
• Identify the right person by evidence they've solved that specific problem, not just seniority or title.
• Structure it deliberately: a defined cadence that's regular but time-boxed, a specific artifact or goal to work toward together rather than open-ended conversation, and a natural end point or reassessment.
• The reverse angle applies here too. The same intentionality applies when you're the one acting as mentor to someone else, tying it back to your own trajectory: teaching a specific skill to someone else is often the fastest way to convert your own implicit knowledge into something you can articulate and lean on for your next level. Seeking and giving mentorship around a specific gap draw on the same underlying skill.
• Close the loop. Define what "done" looks like so the relationship doesn't drift into indefinite informal chats with no forward motion.

Worked example

There was a specific area I knew I was weak in, and I didn't look for "a mentor" broadly, I looked for one specific person on a different team who'd actually solved that exact problem before. I asked for a defined arrangement: a recurring session for a set number of weeks, working through a real piece of my own work rather than abstract advice, ending with a specific deliverable I could point to. That structure meant neither of us had to guess whether it was working. Later, when I mentored someone else through a similar gap, I used the same shape in reverse, a defined cadence, a real deliverable, an endpoint, and explaining the reasoning behind my own decisions to someone else sharpened it for myself in a way informal conversations never had.

Trade-offs & pitfalls

• Open-ended "let's grab coffee sometime" mentorship rarely closes a specific gap, it produces goodwill but not measurable progress.
• Picking a mentor for their title rather than evidence they've solved your specific problem wastes both people's time.
• No defined endpoint means the relationship either fades awkwardly or persists past its useful life.
• Treating mentoring others as separate from your own growth misses that teaching a gap you've closed is often how you close the next one.