the founder shape
Founders arrive at MARK with an unusual distribution. Map lands early and lands hard — if you’ve survived a runway crunch or killed a product line to save the company, you’ve trained Worth and Kill in a way most PMs never will. Existential stakes are the fastest teacher. Kill in particular is a founder competency: the person who built the thing is usually the last to kill it, except when they’re the first — and the ones who kill early tend to survive.
Resolve is the other strong side. Founders have defended hard calls to investors who know more about capital markets, to early employees who quit over a pivot, to co-founders who had a different vision. Hold isn’t abstract for you — you’ve lived it at high stakes, often alone. Power follows: telling the exec the call is wrong is structurally easier when you are the exec, though that same dynamic creates a different Hold failure (more on that below).
Acuity is the variable. Early founders who are close to their customer — doing the sales calls, working the support queue, reading every reply — often have sharp Signal. Then the company grows. The distance between founder and customer widens. Signal reading gets delegated. You start reading reports of reports. Reframe, the competency that asks whether you’re solving the right problem at all, is the one that atrophies fastest under scale pressure. Ken often follows behind Acuity — User in particular. You built the product for a version of your customer you understood in year one; the customer has moved, and your model hasn’t.
On the radar, a founder shape leans hard toward Map and Resolve. Acuity is the variable; Ken often follows behind.
the three competencies that decide the year
Worth — Map
Why this one: Every founder has a theory of what to build. The gap isn’t the theory — it’s the discipline to kill the alternatives. Worth at L4 isn’t about choosing the right thing; it’s about being explicit and auditable about what you chose not to build and why. Without that, the roadmap becomes a political document and the actual company strategy lives only in the founder’s head, which doesn’t scale.
L4 behavior: They can name the three things they killed this quarter — not the things that didn’t survive prioritization, but the things they actively decided not to build, with the reasoning that would still hold in six months.
Failure mode: The founder who treats the roadmap as a living negotiation. Everything is reprioritizable. Nothing is permanently off the table. The team can’t hold direction because they’ve learned the direction will move if a customer escalation or a board question arrives.
Bet — Acuity
Why this one: Founders make capital allocation calls — money, time, team focus — under more uncertainty than any other PM role. The question isn’t just “is this the right bet?” It’s “how much do we put behind it before we know if it’s right?” L4 Bet is reversibility-aware: the founder who bets big on one-way doors and small on two-way doors ships faster and recovers faster than the founder who applies the same conviction to everything.
L4 behavior: Before committing a resource call, they name the reversibility explicitly — “this one we can unwind in six weeks, this one we can’t” — and that distinction is visible in how much they’re putting behind each. The team can see the logic, not just the call.
Failure mode: Momentum bias. Founders who are fast, decisive, and right most of the time develop a pattern of treating all bets as equally high-conviction. One-way door decisions accumulate at the same pace as two-way ones. The first time it matters, there’s no recovery path.
Hold — Resolve
Why this one: The founder’s version of Hold is distinct from a PM’s version. You own the call — no one can force you to flip it. The pressure comes from a different direction: a co-founder who disagrees, a lead investor who pushes, a key hire who’s threatening to leave over a strategic disagreement. The failure mode isn’t folding to authority — it’s folding to social cost. The call that gets quietly revised after a board meeting. The pivot that gets framed as “we always knew we’d get here.”
L4 behavior: When a high-stakes pressure arrives, they name it out loud to the team: what the pressure is, why they’re holding, and what evidence would actually change their position. The call is held in public, not in private.
Failure mode: The founder’s specific L4 trap — holding a dead call past the evidence that should have ended it, because admitting the flip now would mean admitting the pressure that arrived six months ago was actually right. This is Hold inverted: using Resolve to avoid a Kill that’s overdue.
what to do this week
Write a one-page “no list” — the five things you decided not to build this quarter, with one sentence each explaining why that call holds even if a customer asks for it or a competitor ships it. Share it with your co-founders or your head of product by Friday. If you can’t fill five items, the list will show you the gap: either you haven’t been making explicit bets, or the calls you’re making aren’t surviving long enough to commit to paper.
read this next
MARK for self-assessment — because the founder fingerprint is unusually hard to read honestly without a structured prompt: you have strong priors, high stakes, and no direct manager to calibrate against; this essay gives you the discipline to read your own shape without confirmation bias.
avoid these traps
The founder exception. Believing your hold is always conviction when it might be sunk cost — you built the thing, you know it best, you’ve been right before. The competency lives in the ability to distinguish the two. When you can’t name the evidence that would change your position, that’s not Hold. That’s a Kill problem waiting to surface.
Delegated Signal. The year you stop reading primary sources — raw customer calls, support tickets, churn interviews — is the year your Signal starts drifting. Summaries are filtered; the filter reflects the beliefs of whoever’s summarizing. Founders who lose Signal lose it quietly, one layer of indirection at a time.
Bet uniformity. Applying the same conviction posture to every resource call, regardless of reversibility. The company survives the wrong bets it can unwind — it doesn’t always survive the ones it can’t. L4 Bet is visible in the differential: bold on two-way doors, careful on one-way ones.
citation
PL Standard v3.1 · MARK for founders