who this is for
ICs and managers who want their 1:1s to do actual development work — not status recap — and anyone who needs to communicate their judgment growth to a boss or a boss’s boss without sounding like they’re self-promoting.
the problem this solves
1:1s drift. It happens to almost everyone, and it happens fast — within a few months of starting a new role, most 1:1 calendars have quietly become project syncs. You cover blockers, you relay updates, you talk about what’s shipping. The manager leaves knowing what you’re working on. They do not know how you’re thinking.
That’s the gap. And it’s not a commitment problem on either side. It’s a language problem. Without shared vocabulary for the judgment work — the decisions you made, the calls you held, the moments where you folded when you shouldn’t have or pushed back when it was hard — there’s nothing to anchor a development conversation to. You can say “I want to grow my strategic thinking” but neither of you knows what that means on a Tuesday.
MARK gives you the map. Not as a performance script — as a shared reference point that turns vague manager-speak (“you need to build executive presence”) into something you can actually work on, evidence in hand.
how to use MARK for this, end-to-end
step 1 — take the skill scan and read your fingerprint honestly
Before you bring MARK into a 1:1, you need your own read. The Skill Scan is the entry point. It’s five minutes; it produces a fingerprint across the 12 competencies. Read it as a starting hypothesis, not a verdict.
What you’re looking for: two or three competencies where you’re below where you expected, and one where you’re stronger than you thought. The gaps are your development lever. The surprise strength is worth naming explicitly in conversation — managers often don’t see it until you surface it.
step 2 — pick one competency to focus on per 4–6 week cycle
Not twelve. Not four. One.
The mistake most people make when they discover a framework is trying to develop everything at once. MARK has twelve competencies; if you’re trying to move on six of them simultaneously, you’re moving on none of them. Pick the one that’s most load-bearing right now — the one where your current level is actively costing you, or where leveling up would visibly change what you’re able to do.
Good heuristics for picking:
- Where did I last get friction? (A Resolve competency — Hold, Power, Miss — is often behind “I’m not seen as strategic enough”)
- What’s the gap between my fingerprint and the role I’m targeting? (Map competencies — Worth, Kill, Halt — often flag for PMs who want to move into director roles)
- What did my last Brief result tell me? (If you’ve submitted a Brief, the result fingerprint is evidence, not just a scan answer)
step 3 — bring evidence to the conversation
Once you’ve picked a focus competency, don’t walk into the 1:1 empty-handed. Bring a call — a specific decision you made in the last 3–4 weeks where that competency was live.
The format is simple:
- The situation — what decision were you in?
- What you did — the specific call you made
- Your read on your own level — “I think I was L2 here — I held the position initially but softened it when the VP pushed back in the review”
- What you’d do differently — or what you think the L3 version looks like
That’s it. You’re not asking for a grade. You’re creating a shared anchor that your manager can respond to with their own read. Nine times out of ten, the conversation that follows is 10x more useful than anything a status update produces.
step 4 — ask your manager to read you against the anchors
If your manager knows MARK, this is easy. If they don’t (see step 6 below), you can still do this. Share the /framework link. Point them at the specific competency you’re working on. Ask: “Does your read of that situation match mine? Where would you put me on that level arc?”
A good manager will tell you where their read diverges from yours. That divergence is the actual development data. If they put you at L2 and you thought you were L3, the conversation now is: what did they see that you didn’t? What would L3 actually have looked like in that moment?
step 5 — agree on a development move before you leave
Every MARK-focused 1:1 should end with one concrete action:
- A Brief to submit (tests the competency with real evidence you can cite)
- A scenario to watch for (“next time we’re in a planning review, I’m going to practice Hold — stay at my read even when the GM challenges it”)
- A Manual chapter to read
- A coaching question to journal on
One thing. Not a list. If you leave with a list, you’ve diffused the focus.
step 6 — managing up without lecturing
This is where most people get stuck. Your manager doesn’t know MARK. You want to surface your development without making it weird.
Don’t lead with the framework. Lead with the behavior.
“I’ve been thinking about the times I’ve backed off a call when I shouldn’t have — I want to get better at holding a position under pressure” lands exactly as well as “I’m developing Hold, which is the conviction competency in Resolve.” Better, actually, because it doesn’t require your manager to learn anything first.
Then, if they’re curious — and most managers are, when you’ve articulated a development focus this clearly — you share the link. “There’s a framework I’m using to structure my own development. Here’s where this fits.” Light. Not a pitch. Not a lecture. An invitation.
If they read it and engage, great. You now have shared vocabulary. If they don’t, keep using the behaviors — “staying at my read,” “owning the miss cleanly,” “naming the wrong question before solving it” — and the development work still happens. The label is a shortcut, not the work itself.
step 7 — skip-level conversations
Skip-levels are a different genre from regular 1:1s. You have less context between you and less time to build it. You need to communicate where you are in your development with enough precision that someone who hasn’t seen your day-to-day work can form a view.
MARK gives you a way to do that without sounding like a complaint and without generic self-promotion.
“I’m actively developing Power — the ability to push back on exec calls that I think are wrong. Here’s a situation from last quarter where I held the position, and here’s one where I didn’t and the cost was real” gives your boss’s boss something to assess. It shows self-awareness, shows you’re doing actual development work, and doesn’t position you as someone griping about your manager’s decision-making.
Compare to: “I feel like my manager doesn’t give me room to push back on exec decisions.” Same situation, zero development posture, guaranteed to read as a complaint.
Power is a Resolve competency — it’s about conviction in asymmetric situations, not just courage. Framing your development through the competency keeps the conversation on your growth, not on organizational politics.
step 8 — performance review season
If your review form is generic — “strategic thinking 1-5,” “communication 1-5,” “executes with impact” — MARK is a translation layer.
Before you write your self-review, map the form’s dimensions to MARK competencies:
- “strategic thinking” → probably Worth + Kill + Reframe
- “drives alignment” → probably Room + Power
- “executes with impact” → probably Bet + Hold + Miss
- “communication” → probably Room + User
Now write your self-review through the competencies: cite a specific call, name your honest level read, describe what growth looks like. Even if your reviewer doesn’t know MARK, the evidence specificity will stand out. “L2 on Hold — I submitted the roadmap recommendation despite initial pushback from the growth team, but softened it during the final stakeholder review before I should have. Next cycle: hold to the recommendation through one more round of challenge before revising” is a far sharper self-assessment than “could grow in strategic courage.”
what to do in week 1
- Take the Skill Scan. Get your current fingerprint. Don’t overthink it — it’s a starting point.
- Pick one competency. The one that’s most load-bearing in your current role. Not the most interesting one, the most important one.
- Identify your evidence. A call from the last 3 weeks where that competency was live. Write two sentences on your level read of that moment.
- Put a 30-minute MARK development block on next week’s 1:1 agenda. Tell your manager in advance: “I want to use 20-30 minutes of our next 1:1 to share something I’m working on development-wise. I’ll bring a specific example.”
- Share
/framework— either before the meeting (“here’s what I’ll be referencing”) or during if your manager asks what the framework is.
what to expect by week 4
After four weeks and two or three MARK-focused 1:1s, you should be able to see a few things:
Your manager has a clearer model of your judgment shape. Not just what you’re working on, but how you think. They can start to calibrate you in real-time — “she’ll hold the position in the room” or “he’s still developing Power — I should watch this next planning cycle.”
You’re naming your calls in real-time. Instead of leaving a meeting thinking “that went okay I guess,” you’re leaving with a read: “that was a L3 Hold — I stayed at my recommendation through two rounds of challenge.” That self-awareness compounds.
The conversation in 1:1s has shifted. Even if your manager doesn’t use MARK language back at you, you’ll notice that the quality of the development conversation has moved up. When you bring evidence, they respond with evidence. When you name a gap, they can help you close it.
the five common pitfalls
1. weaponizing MARK against your manager. Don’t. Never say “you’re L1 on Power” to your manager — even if you believe it, even if it’s accurate, the rubric is not a weapon. Use it to develop yourself, not to diagnose others. The moment MARK becomes a tool for judgment-scoring people around you, it stops being useful and starts being damaging.
2. replacing conversation with rubric-speak. “My Signal was L2 in that meeting” is not a development conversation — it’s a report. MARK gives you vocabulary, not a script. The work is still done in human conversation with specific evidence and real reactions from someone who knows your context. The label is the shortcut into the conversation, not a substitute for it.
3. making MARK the entire 1:1 agenda. It’s a tool for development threads within a relationship, not the relationship itself. Most 1:1s should still cover the things 1:1s cover: what’s live, what’s hard, what support is needed. A 20-minute MARK development block every 4-6 weeks is right for most situations. If every 1:1 becomes a MARK debrief, you’ve over-rotated.
4. picking the competency you’re best at. This one is subtle. When you pick which competency to work on, the temptation is to pick one where you’re already strong — it’s easier to gather evidence that flatters you. Pick the one that’s costing you, even if the evidence will be a mix of what you did right and what you didn’t.
5. using MARK language before your manager has a baseline. If you walk into a 1:1 and start talking about Hold and Resolve without 30 seconds of context, you’ll lose them immediately. One sentence of context upfront (“I’ve been using a framework called MARK to structure my own development — here’s the quick version”) goes a long way.
a worked example
A senior PM — let’s call her Priya — had been at her company for eighteen months. Her 1:1s with her VP of Product were well-intentioned: 30 minutes every two weeks, covered what was shipping, what was blocked, what decisions were pending. Good relationship. No real development work happening.
Priya took the Skill Scan. Her fingerprint showed she was stronger on Map (Worth, Kill, Halt) — she was good at deciding what to build — but weaker on Resolve, particularly Hold and Power. She’d been sensing this. In design reviews, she’d present a recommendation, get pushback, and soften the recommendation faster than the evidence required.
She decided to focus on Hold for the next 6 weeks. The anchor at L3 is roughly: holds a position when challenged, separates challenge-from-stakeholder from challenge-from-evidence, revises when genuinely wrong but doesn’t bend from social pressure.
She brought evidence to her next three 1:1s. Not highlights — honest reads. One was a planning meeting where she’d held her roadmap recommendation through two rounds of push from the growth team and it ended up shipping as she’d proposed. One was a quarterly review where she’d softened the P0 definition after one challenge from the CFO, faster than the evidence required, and the project scope drifted. Both were relevant evidence. The honest mix was what made the conversation useful.
Her VP started responding differently. By the third 1:1, he was giving her pre-read on where he’d seen her hold and where he’d seen her fold, with specific examples she hadn’t even brought. “That call in the roadmap review last week — you held it well. The one in the pricing sync — you backed off earlier than you needed to.”
Six months later, during her performance review, her VP said something she’d never heard a manager say to her before: “I have a clearer picture of your judgment shape than I’ve had of any direct report. I know how you think, not just what you shipped.” She was promoted to Principal PM two months after that.
The mechanism wasn’t MARK. It was the quality of the conversations MARK enabled. She had a language for the work she was doing on herself. Her manager had a frame to respond within. The relationship held the evidence; the framework surfaced it.
citation
PL Standard v3.1 · using MARK for 1:1s and managing up