who this is for
ICs and managers deciding their next move — not which title to chase, but which competencies the next role will actually develop.
the problem this solves
Most career planning is title planning. you compare your current title to a destination title, calculate the gap in seniority, and pick the company or team that closes it fastest. the problem: titles are not competencies. and the career moves that look biggest on paper often develop the least.
a Senior PM who jumps to Group PM at a larger company might spend the next two years running the same playbook with more people in the room. the title moved. the MARK fingerprint didn’t. three years later they’re applying for VP Product roles and wondering why interviewers keep probing the same spots.
this essay is about using MARK the other way around — starting with your fingerprint, sketching the fingerprint of where you want to end up, and then choosing the role that builds the delta.
how to use MARK for this, end-to-end
step 1 — get an honest read of your current fingerprint
before you can plot a move, you need a clear picture of where you actually stand. not where you think you stand, not where your last performance review said you stood.
take the Skill Scan as a starting point. then run a harder test: look at your last three significant product decisions. for each one, ask:
- did I read the conflicting evidence and land on a clear call — or did I defer to the loudest voice? (signal)
- did I hold my position when the exec pushed back — or did I fold? (hold / power)
- did I know when to kill the thing I’d been building — or did I keep going because of what I’d already invested? (kill)
- did I understand who I was really building for — or did I take the stakeholder’s framing at face value? (user)
your answers here are more diagnostic than any self-assessment. the MARK competencies you consistently fumble are the gaps. the ones where you led with confidence and evidence are the strengths. write down a rough level for each of the 12 — even a first-pass sketch is enough to work with.
step 2 — sketch the fingerprint of the role you want
pick the destination. be specific: not “VP Product someday” but the kind of VP Product role you actually want — the stage, the company type, the mission. different versions of the same title have radically different MARK requirements.
then ask: what does the fingerprint look like for someone who’s outstanding at this role? not average — outstanding. sketch it competency by competency.
three archetypes to use as anchors:
founder — the fingerprint is weighted heavily toward Resolve (hold, power, miss) and the top of Map (worth, kill). you need to decide what’s worth building when there’s no data, say no to your own ideas before they become expensive, hold the call when early investors push you to pivot, and own the miss cleanly when you were wrong. Acuity can come from cofounders or early team — a great cofounder with strong signal and bet can cover your gaps there. Ken matters, but it’s not the primary differentiator at the earliest stages; the market will tell you what you need to know about users more brutally than any interview.
VP product — the most balanced shape of the three, but with some non-obvious emphases. room and taste move to L4 — you’re reading organizational dynamics constantly (what does engineering actually think, what is the CEO not saying yet, where is this conversation really heading) and judging the quality of work you didn’t make (team roadmaps, spec quality, design quality, AI-generated output). hold matters a lot: you’ll be in rooms where the pressure to validate a bad call is enormous, and someone at your level folding sends a signal that cascades. worth and kill stay sharp — you’re killing your own team’s ideas regularly and they’re watching how you do it.
GM — heavy Map and Resolve, with Ken weighted on user and room. a GM is fundamentally deciding where to go (worth, kill, halt) and holding the course against quarterly pressure (hold, miss). they read the market constantly (user) and they read the org constantly (room). what they have, that a solo PM doesn’t, is a data team — so pure Acuity (signal, bet, reframe) can be delegated to some extent. the GM failure mode isn’t bad analysis; it’s inability to hold a direction when the numbers wobble.
step 3 — name the delta
lay the two fingerprints next to each other. the competencies where your current level is meaningfully below the target level — that’s the delta. those are the skills your next role needs to develop.
be honest about what counts as “meaningfully below.” if you’re at L2 hold and the target needs L4, that’s a gap that one job hop won’t close. if you’re at L3 power and the target needs L4, that’s a stretch — achievable in 12-18 months with the right environment.
write the delta down as a short list. it might look like:
power: L1 → L3 needed
hold: L2 → L3 needed
miss: L2 → L3 needed
worth: L3 → L4 nice to have
that list is your developmental brief for the next move.
step 4 — evaluate roles against the delta
now filter your options through one question: will this role force me to build the competencies on my list?
the answer depends on environment. two factors matter most:
surface area of judgment — does the role put you in situations where you have to exercise the specific competencies you’re building? a role at a 200-person company as Group PM might give you more people to manage but fewer moments where you’re exercising raw power (telling an exec they’re wrong with your job on the line). a role as the only PM at a 20-person startup might look like a step down in title but surfaces power and hold constantly — there’s no one else to absorb the pressure.
feedback loop speed — can you tell within weeks whether your call was right or wrong? startups compress the feedback loop. the company either ships the thing and it works, or it doesn’t. at larger companies you can stay comfortable in a competency gap for years because the feedback is too slow to catch you.
a job that doesn’t stretch any of the competencies on your delta list is not a developmental move — regardless of title, regardless of pay. it is a lateral move with a promotion sticker on it.
step 5 — make the call and track it
once you’re in the new role, track the delta explicitly. every quarter, revisit your fingerprint. the question isn’t “am I performing well” — it’s “am I moving on the specific competencies I came here to build?”
if you’re three months in and you haven’t had a single real test of hold or power, that’s a signal. either the role isn’t structured to surface those situations — or it is, and you’re avoiding them. both are diagnostic.
what to do in week 1
- run a rough self-assessment against the 12 competencies using your last three significant decisions as evidence
- sketch the target fingerprint for the two or three roles you’re most seriously considering
- for each role, list the MARK gaps it would and wouldn’t develop — explicitly, not generally
- identify one competency that your current role almost never surfaces — that’s the highest-signal gap
- if the highest-signal gap doesn’t appear in any of your current options, add at least one search thread that specifically targets the environment that would surface it
what to expect by week 4
if you’ve done the shape-gap exercise honestly, week 4 looks different from the usual job search. you’re filtering faster — you can disqualify a role in one conversation by asking “how often does the PM here have to push back directly against the CEO’s call?” and listening to what the answer reveals. you’re asking different interview questions — not “what does success look like” but “tell me about a call the last PM made that turned out to be wrong; what happened next.” you’re less confused by the title and comp variance across options, because you’re comparing roles on a different axis.
the goal isn’t the offer. it’s the fingerprint 18 months from now.
the five common pitfalls
1. optimizing for the fingerprint that looks impressive on paper. L4 across everything reads as the goal. it isn’t. a VP Product with L4 worth and L2 hold is going to fail the first time they’re in a room with a CEO who is wrong and determined. specialization beats balance for most career stages — know which competencies matter for your destination and build those, not all twelve.
2. assuming more years equals more MARK depth. the PM who spent 8 years at the same company in roughly the same environment will often have shallower hold, power, and miss than the PM who spent 4 years across two very different stages. years in title are not evidence of MARK level. be honest about which of your years actually tested the competency and which ones just ran the same playbook.
3. chasing the gap that’s comfortable to develop. signal and reframe are intellectually satisfying to build. power and miss are uncomfortable. the gap you most need to close and the gap you most want to close are usually different. watch which competencies never show up on your “areas for development” list — those are frequently the ones that are actually holding you back.
4. using the MARK delta to rationalize a move you’ve already decided on. the framework is most useful when it’s generating the question, not justifying the answer. if you catch yourself sketching the target fingerprint to match your favorite option, start over with a blank sheet.
5. treating the fingerprint as fixed. your MARK is a current state, not a forecast. the gap that looks alarming today — L1 power, say — is addressable in a good environment. don’t rule out a destination because your current fingerprint is far from it. the question is whether the next 18 months can close the meaningful gaps. usually, one or two good roles can.
a worked example
a Senior PM at a 500-person e-commerce company. strong Acuity — L4 signal, L3 reframe. she reads conflicting evidence well, spots the wrong question before the team goes down the rabbit hole, and sizes bets with real precision. the work shows it; her last two product launches were notably well-framed.
Resolve is a different story. L1 power — she’s never directly told a C-level they’re wrong; she finds ways to steer without confronting. L2 hold — she’s held positions in peer reviews but has folded in three of four exec reviews in the last year. miss is L2 as well; she’s diplomatic about failure, not clean.
a competitor offered her Group PM — same company size, larger team, more senior title, 20% more comp. the manager she’d report to is straightforward and reasonable. the environment would be predictable, the roadmap already set for the year.
she ran the shape-gap exercise. the target she actually wants is Director of Product at a growth-stage startup in three to four years — and that fingerprint needs L3 Resolve across the board. the competitor role wasn’t going to move any of that. nice people, same competency gym.
she declined. she took a role as the only PM at a 20-person seed-stage company building B2B workflow tooling — a step down in title, a meaningful step down in comp for the first year. within six months she’d told the CEO directly that their pricing strategy was wrong, held that position through two board meetings where the CEO wanted to capitulate to a large prospect, and taken a clean miss when a feature she’d championed flopped in beta.
eighteen months later: L3 across Resolve — verified through a Practice panel at PL. she took the Director of Product offer from a Series B company and had three questions in the final round specifically about holding positions under pressure. she answered them with evidence, not hypotheticals.
the title trap is exactly this: the competitor offer looked like progress. it had the right label and the right number. but it was re-running the same competency gym — and the gap that was holding her back would have stayed a gap.
citation
PL Standard v3.1 · using MARK for career planning