Product Manager
Execution is cheap now. A product engineer with AI can build what used to take a team, so the bottleneck is no longer how much gets built. It is judgment: knowing what is worth building, for whom, and why now. That is the scarce thing, and it does not scale by adding headcount.
So product management at Systeric is a small, senior function. A handful of PMs carry the judgment for many projects, rather than one PM per team shipping features. The ladder reflects that: it is one path that gets deeper and broader, not a management chain. You apprentice, you own a surface, then a project, then direction across projects. There is no management chain at all, no Group PM, Director, or VP layer. Near the top, the most senior PMs embed as a client’s fractional CTO, owning a company’s product and technical direction rather than a chain of reports.
At a Glance
One path, from apprentice to the apex. It does not fork into parallel IC and management tracks: a PM grows by carrying more judgment over more of the product, until the most senior embed as a client’s fractional CTO. It rejoins engineering and design at the top, in the CTO, the one best at building product.
APM → PM → Senior PM → Principal → Fractional CTO → CTO| Level | Owns | What “good” looks like |
|---|---|---|
| APM | A slice, apprenticed | Learns how PMs decide by working under one; owns a slice of a project with guidance. |
| PM | A product surface | Owns one surface end to end: the problem, the call on what to build, shipped and measured. |
| Senior PM | A project | Owns a whole project from vague strategy: finds the problems worth solving and sets its direction. |
| Principal | Direction across projects | The judgment the org leans on: sets product direction across several projects. |
| Fractional CTO | A company’s direction | The rare product mind, embedded as a client’s fractional CTO: owns a company’s product and technical direction, the way Systeric shows up inside it. |
| CTO | The whole product | Best at building product: the synthesis of product, engineering, and design judgment. |
The spine down the middle column is the whole story: a slice → a surface → a project → direction across projects → a company as its fractional CTO → the whole product.
Your Shape: The Seven Attributes
The ladder tells you your altitude. This tells you your shape: where you are strong, where you are thin, and what to do about it.
It is attribute-focused, not level-focused. You are not “a PM”. You are a profile: maybe strong at product sense, thin at data, middling at strategy. Place yourself honestly on each attribute and the line comes out jagged. That jaggedness is the point: it shows exactly where to push next.
It is a mirror, not a scorecard. Nobody is graded or ranked here. Each attribute is a direction to grow, not a number to defend.
- Product sense: taste and judgment for what is worth building, and the conviction to cut the rest.
- User insight: getting past what users ask for to the real problem they have.
- Strategy & prioritization: choosing what to do and what not to, and in what order, and why now.
- Delivery: driving the work to shipped and measured, now mostly by directing engineers and AI rather than doing it yourself.
- Data & impact: choosing the metric that actually matters, then proving it moved.
- Communication: being understood the first time; aligning people without authority.
- Influence: raising the few PMs and bending the org toward the right product, with leverage rather than headcount.
Gauging Someone
You gauge a PM by their shape: where they sit on each of the seven attributes, drawn as a radar. Here is every level’s shape. Place your report against the rung they are growing toward, and the gap is the work.
How to read the shapes. This is one path, not a fork. Each rung’s shape contains the one below it: you keep everything and add, nothing recedes. The early rungs are spiky, strong on a few spokes and thin on the rest; the senior rungs fill out as judgment broadens from a surface to a project to the whole product. The depth spokes (product sense, user insight, strategy, data) lead the way up, with delivery, communication, and influence coming in as scope grows.
- PM: owns one product surface end to end, the problem, the call, shipped and measured.
- Senior PM: owns a whole project from vague strategy; finds the problems worth solving.
- Principal: the judgment the org leans on, direction across several projects.
- Fractional CTO: the rare product mind, embedded as a client’s fractional CTO, owning a company’s product and technical direction.
- CTO: the synthesis, best at building product.
The climb, in detail
The radar is the summary. Here is the same thing in words for the climb, apprentice to Principal, attribute by attribute. The point of each row is what genuinely changes by level, not a baseline every PM is expected to do. Every PM talks to users and defines a metric; what moves up the ladder is the judgment behind it.
| Attribute | APM | PM | Senior PM | Principal |
|---|---|---|---|---|
| Product sense | Has opinions on small calls; learning to tell a real bet from a loud one | Makes the build-or-cut call on their surface and is usually right | Spots the high-leverage bet others miss; cuts work that looks good but does not matter | Sets what “worth building” means across projects; the taste others calibrate to |
| User insight | Talks to users from a script; reports what they said | Talks to users regularly; gets past what they say to what they do | Finds the unmet need behind the request, before users can name it | Builds the org’s instinct for the user; makes evidence beat opinion |
| Strategy & prioritization | Sequences their own slice; follows the agreed priorities | Prioritizes their surface by impact and effort; says no with a reason | Shapes a project’s direction from vague strategy; sequences by risk | Decides which bets the org makes at all |
| Delivery | Writes a clear story and coordinates a small build to ship, with guidance | Drives a surface to shipped and measured; keeps the plan honest, no surprises | Drives a whole project to land; de-risks the hard part early | Sets the delivery standard the PMs work to |
| Data & impact | Defines an obvious metric when prompted; reads the result after | Defines the metric before build and confirms it moved, every time | Picks the metric that actually matters, not the easy one; knows which number would change the call | Sets what counts as impact across projects; cuts the metrics that mislead |
| Communication | Updates say done, next, blocked; writes a spec others can follow | Surfaces changes early; the doc aligns the team the first time | Aligns stakeholders and execs in writing; influences without authority | Sets how the org writes and decides about product |
| Influence | Focused on their own growth; helps a peer when asked | The go-to for newer PMs on how things work here | Raises the PMs around them; transfers judgment, not answers | Multiplies the whole function; the few PMs get better because of them |
Hiring For It
Hiring is two gates, in order. First the non-negotiables: critical thinking, honesty, ownership, low ego, high agency. Fail one and it is a no-hire at any level, no matter the rest. Those, and the loop built to force them out, live in Hiring. Then the read: where does the candidate sit on each attribute? Since PM is a small, senior function, the bar is high and the search is slow on purpose.
| Attribute | What to look for in the room |
|---|---|
| Product sense | Give them a product and ask what they would cut: do they reason from impact, or just list features? |
| User insight | Ask about a product they know well: do they talk about real user behavior, or their own preference? |
| Strategy & prioritization | Hand them five things and a deadline: do they sequence by impact and defend a “not now”, or try to do all of it? |
| Delivery | Walk through a past launch: did they drive it to shipped and measured, or hand off and hope? |
| Data & impact | Push past “we set a metric”: which one, why that one, and what would have changed your mind? |
| Communication | Make them explain a hard tradeoff: do you follow without having to ask “why”? |
| Influence | Ask how they changed a strong team’s direction without authority, with evidence. |
You hire at the level the evidence supports, attribute by attribute, not the title on the CV. A spiky candidate is normal: hire the spikes you need and coach the rest, but never past a failed non-negotiable.
Growing Your Reports
This is the part that compounds. A direct report’s profile is your coaching agenda, and the move is almost always the same two:
- Double down on the spike. The attribute they are already strongest at is usually where their value compounds fastest. Feed it.
- Clear the one blocker. Find the single thinnest spoke holding them below their next rung and put real reps there. A rounded-but-flat profile helps no one; do not sand the spikes down to raise the floor everywhere at once.
The mechanism per attribute is the same: have them apply the next level’s behavior one step earlier than feels comfortable, then close the gap with review.
| Attribute | The rep that levels it up |
|---|---|
| Product sense | Have them make a real build-or-cut call and defend it; review the bets that did not pay off |
| User insight | Put them in front of users weekly; have them bring the problem before it is framed |
| Strategy & prioritization | Hand them a project’s direction; make them say no to something real and own it |
| Delivery | Give them a launch to drive end to end, release notes and metric included |
| Data & impact | Make them pick the metric before build and defend why that one; read the result honestly after |
| Communication | Hand them the doc the team has to align on; rewrite it together until no one asks “why” |
| Influence | Give them a cross-team call to win on the merits, with you out of the room |
Where growth goes exponential. Early on, you grow a report’s own spokes. Higher up, the move flips: their leverage becomes the judgment they set for everyone else, the bar, the strategy, the few PMs they make better. In a small function that is the whole game, one Principal who lifts the standard moves more than any single PM’s output.
Keep it live: the profile is the spine of the 1:1, revisited each cycle. For how the work itself moves stage by stage, see How Systeric Works. For how to run the growth conversation, see Leading People.
Related: Roles, Product Engineer, Product Designer, Hiring