Career Goals and Progression Questions

Direct answer

Decide by diagnosing which constraint is actually binding right now: if it's a visibility or credibility gap, take the shippable path since it buys proof and goodwill; if it's a capability gap that will bottleneck everything after, invest the depth even though it won't show for a while. When genuinely unsure, default toward shipping, since visible momentum is what buys you the room to go deep later.

Structured elaboration

• Diagnose the binding constraint first. Ask directly: do people doubt I can do the harder thing (a visibility problem, solved by shipping), or can I genuinely not yet do it reliably (a capability problem, solved by depth)?
• Weigh the time horizon of the payoff. Depth work compounds, the skill gets reused across many future situations; shipping is mostly a point-in-time signal. The earlier you are in a role or level, the more depth tends to be worth relative to a single visible win.
• Look for a hybrid slice. Can part of the deep work be carved into something small enough to ship and visible enough to protect the time for the rest? This is often available and often missed.
• The same logic applies over a longer horizon. A lateral move offering real ownership but far less visibility is this same trade-off stretched over months instead of a single decision: the test is whether that ownership will eventually surface as something demonstrable, or whether it's ownership of something structurally invisible with no path to ever becoming visible.

Worked example

I was mid-way through work on a system that badly needed a deeper rewrite, work that wouldn't show results for a couple of months, right when a lower-effort, more visible feature request landed that would help my case going into a review cycle. I asked which was actually the binding constraint: I already had credibility for shipping, what I was missing was proof I could handle harder technical problems, so instead of choosing one or the other outright, I carved out the piece of the deep rewrite causing the most visible pain, framed it publicly as phase one of the larger effort, and used the resulting goodwill to protect time for the rest. The same question came up later at a larger scale, when I considered a lateral move into a role with far more ownership but almost no visibility; I only took it once I'd confirmed the ownership would eventually surface as something demonstrable, rather than staying invisible indefinitely.

Trade-offs & pitfalls

• Always choosing visibility produces a track record that looks credible but is shallow exactly when the next level starts expecting real depth.
• Always choosing depth risks being read as someone who goes quiet and doesn't ship, even when the eventual work is excellent.
• A hybrid slice isn't always available, and pretending there's always a clever middle path is itself a tell that you're avoiding an honest either/or call.
• For the lateral-move version specifically, the trap is accepting invisible ownership indefinitely on the promise it will "pay off eventually," with no concrete idea of how or when it becomes visible.

Direct answer

Name the specific skill gap precisely, not get better at X but the concrete capability you lack, build a month-by-month plan that pairs learning with a real, low-stakes application of the skill, and define upfront what evidence would prove to both you and your manager that the gap is actually closed, not just that time was spent on it.

Structured elaboration

Name the gap precisely. A vague gap, need more leadership, can't be closed on a timeline because you can't tell when it's done. A precise gap, I haven't yet led a project with more than one dependent team, can be. The gap itself varies by person and stage, it might be depth in a specific technology, a practice area such as MLOps, the operational practice of running machine learning systems in production, or cloud architecture, or a non-technical capability such as leadership, communication, or cross-team influence. Whatever it is, name it precisely rather than generically.

Choose the plan format that fits the gap and your organization's norms. A formal individual development plan (IDP) or personal development plan (PDP) tracked with your manager, a self-directed learning roadmap, or a mentorship-and-development plan built around a specific mentoring relationship. The format matters less than whether it has real milestones and a real check-in mechanism attached.

Build month-by-month milestones that pair input with application. A month or two of concentrated learning, a course, structured reading, shadowing someone strong in the area, followed immediately by applying it on a real, if small, piece of work, not learning followed by an indefinite wait for the right opportunity.

Define the closing evidence upfront, before you start. A completed project that required the skill, feedback from someone who observed you using it, or your own comfortable performance in a situation that used to make you anxious. Where you're earlier in your career or the gap is foundational, a lighter version of this plan can lean more on recommended resources, a specific book, course, or structured reading list, as the input side, since real-world application opportunities may need to be built up to.

Build in the feedback loop. A recurring, lightweight check-in with your manager or mentor, not just a single review at the end of the plan.

Worked example

"I identified a specific gap, I'd never led a piece of work that required negotiating priorities directly with another team, only within my own. I built a three-month plan. Month one, shadow a colleague who did this well in a couple of real meetings, and read a short set of material on negotiation and stakeholder alignment. Month two, take on one small piece of work myself that required exactly this, with my manager aware it was a deliberate stretch, and check in with my shadowed colleague afterward for candid feedback. Month three, take on a second instance of the same kind of work, this time without shadowing beforehand, to test whether the skill had actually transferred rather than only working with a safety net. I'd agreed with my manager beforehand what would count as evidence the gap was closed, specifically that I could handle one of these negotiations independently, with an outcome both teams considered fair, and that a peer who observed it would say so unprompted."

Trade-offs & pitfalls

• A plan that's all learning and no application doesn't close a skill gap on its own, it only prepares you for the real practice that does.
• Defining the gap too vaguely to know when it's closed leaves the plan running indefinitely with no clear finish line.
• Skipping the check-in loop means only finding out at the end whether the plan actually worked, rather than adjusting along the way.
• Be realistic about pacing. A genuinely new capability, especially one involving judgment rather than a mechanical skill, usually needs more than one real attempt before it's trustworthy.

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

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

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.