Career OS

Your record is built once, and it travels with you.

A product ships and the credit goes to the team. That is fair, and it is also where your part disappears. Career OS is where you set out what was specifically yours: the decision you made, the thing you held, the call that turned out right. Then somebody who was there confirms it.

Every piece of work, every reference and every stamp adds to one record, so you stop explaining your career from scratch. It is never edited, only enriched, so your growth stays visible, to you first.

Principal Product Manager

You turn tangled dependencies into platforms other teams build on. You are strongest where the work has been signed: Strategy, Discovery and Leadership.

Strategy

Dele Okafor

Discovery

Marta Villar

Delivery

checked on a call

Leadership

Tom Becker

AI Maturity

the work is on file

Growth

awaiting the work

Stamped when the work is checked. Signed when someone stands behind it.

Builder Fluency

Independent shipperread from the things you built

Your North Star

Chief Product Officer of an AI native scaleup, still close to the build.

A chapter of scaling what already works, grown through Leadership and AI Maturity.

Yours to write. Never scored.

The work behind the work

Two people, one job title, almost nothing in common.

One rebuilt how the company decided what to build. The other kept a roadmap tidy. A title cannot tell them apart, and for anyone reading quickly, the title and the logo are most of what there is.

So the part that took the years is the part that travels worst. The question you changed. The complexity you removed. The thing you argued should not be built. None of it fits in a line on a CV.

Cream is where that work gets its context. The problem, the decisions, what you contributed and what changed, alongside the perspective of people who saw it firsthand.

Where it starts

It begins with where you are heading.

Cream asks about your ambitions before anyone asks about your availability. Your record then grows around that direction, and when the direction changes, the old one stays in the record.

Your north star

Chief Product Officer of an AI native scaleup, still close to the build.

A chapter of scaling what already works, grown through Leadership and AI Maturity.

An example. Four questions, answered in the member's own words and changed whenever the answer changes. Never scored.

Your development plan

The one thing you choose to move next.

You pick the pillar you want to move next. It is rarely the weakest one.

It is the one that carries you closest to where you said you are heading.

Being built now, one piece at a time. See the roadmap

Being built now, and walked with our founding members first. See the roadmap

Cream reads your six pillars, the evidence behind each one, and where you said you are heading. Then you choose.

A player with a decent serve and a poor backhand might pour everything into the serve, because that is the shot the game they want to play is built on. Development works the same way. The gap that matters is the one standing between you and where you are going.

A plan your manager can open An example
  • You choose Leadership. Not the lowest reading you carry, but the one Chief Product Officer of an AI native scaleup actually requires.
  • Cream sets it out Where that pillar stands today, what evidence sits behind it, and what would move it. In language a manager can act on.
  • You share it A page you can send or print, prepared from the record on the day, so a manager reads what has actually been checked.
  • It comes back The project you are given, the work you go on to lead, the person who saw you do it. All of it returns to your record.

Most development plans are written once and never opened again. This one is worth opening again, because it is prepared from a record that changes as you do.

What the passport measures

Six pillars. One standard.

Cream reads a product career across six things that decide whether a product succeeds. Each one is stamped on its own evidence, and each one shows what it rests on.

Strategy

Signed by a reference

Discovery

Signed by a reference

Delivery

Checked on a call

Leadership

Signed by a reference

AI Maturity

Shown

Growth

Your word

An example, for the passport above. The tone says where a reading came from, never whether it is good.

Strategy

How you shape direction, make trade-offs, and decide what the product is really for.

Discovery

How you find real problems before the team spends time building the wrong thing.

Delivery

How you turn intent into shipped outcomes without losing the point of the thing.

Leadership

How you move people, decisions and momentum without relying on direct authority.

AI Maturity

How you apply AI as a core product capability, not a decorative feature.

Growth

How you learn from users, data and the market quickly enough to change what happens next.

Evidence over claims

Four layers of evidence. Each one makes the picture sharper.

The same capability, seen more clearly at each layer. Each one is harder to earn than the last, and your record always shows which layer a reading sits on.

You state it

Your own account of what you can do, in your own words. It is where every record starts and it is never where one ends.

You show it

The work itself. Something you built, shipped or turned around, with the decisions you made inside it.

We probe it

A real conversation about the detail only the person who did it would know. Judgment shows up here in a way a document can't carry.

Someone signs it

A named reference who watched you do it puts their name to it. That is the stamp, and it is the only thing that can't be self declared.

first

You state it

Self assessed
then

You show it

Work shown
then

We probe it

Checked on a call
finally

Someone signs it

Signed by a reference

The two readings

Two readings, and the distance between them.

Every pillar carries what you believe of yourself, and what the evidence supports so far.

The distance between them is the honest part. It is also the clearest guide you will get to what is worth strengthening next.

Both readings run out of five, and each one shows how it was earned, from your own account through to a named reference who was there. You can see where every reading came from.

Every record starts empty and fills as evidence is added.

Your six pillars An example, out of five
Strategy
Self assessed
Shown

Confirmed

signed by Dele Okafor

Discovery
Self assessed
Shown

Confirmed

signed by Marta Villar

Delivery
Self assessed
Shown

Shown

checked on a call

Leadership
Self assessed
Shown

Confirmed

signed by Tom Becker

AI Maturity
Self assessed
Shown

Shown

the work is on file

Growth
Self assessed
Shown

Your word

awaiting the work

Self assessed Shown signedConfirmed by reference

Evidence gaps

Strong, and not yet visible.

Sometimes the capability is real and the proof has not caught up. Cream keeps the two apart, so you can always tell which one you are looking at.

Strong but invisible

Emerging and developing

Genuinely early

Strong but invisible

You have the capability. The evidence is thin or missing. This is the most common situation for senior product leaders who move fast and rarely document what they have done.

Emerging and developing

You have some evidence here but it isn't yet strong enough to stand on its own. One more clear example, or a reference who can confirm the pattern, changes how this reads.

Genuinely early

This is an area you haven't yet worked in deeply. Knowing it clearly means you can make an intentional choice about whether to develop it, delegate it, or build a team around it.

The aim isn't to make you look complete. The aim is to make your growth visible, specific and credible, to yourself and to the people who matter.

The second axis

Titles say where you sat. Journeys say what you have lived through.

Transformations are the journeys an organization lives through, and the problems you solved on the way.

Your record carries the change you have already made, not only the title you happened to hold.

Pillars read how far you operate. Journeys read what you have been through. Cream reads both.

An example. The ticks are journeys this member has lived.

✓Founder led to product organization

Single product to platform

✓SaaS to AI native

Services to product

✓Startup to scale up

Consumer to enterprise

Growth at all costs to efficiency

Entry into a regulated market

References that add

A reference does more than confirm.

Every reference is a real conversation with someone who was there.

Every call adds something you could not have written about yourself.

A reference is built to leave your record stronger than it found it.

It checks what you said, and it finds what you never thought to say.

An example, written to show the shape of a good reference.

They didn't just ship it. They held the line on scope while everyone senior wanted one more thing, and the launch held because of it.

Marta VillarVP Product, who worked beside them for two years

Confirms Delivery Deepens Leadership New insight recorded

What happens next

How the picture builds.

Five steps, and none of them starts over. Each one adds to what the last one built.

  1. 1

    Share what you have built

  2. 2

    Complete your Cream call

  3. 3

    Add references

  4. 4

    Choose what you are working on

  5. 5

    Career OS compounds

  1. 1

    Share what you have built

    Your request and your build evidence are the starting point. Cream reads what you have shipped, decided and shaped.

  2. 2

    Complete your Cream call

    A structured conversation that probes your judgment, your patterns and your ambition, in ways that build evidence alone can't reach.

  3. 3

    Add references

    One or two people who have worked alongside you answer a short set of focused questions. Their perspective confirms, deepens or revises the picture.

  4. 4

    Choose what you are working on

    You pick the pillar you want to move, which is rarely the weakest one. It is the one that carries you toward where you said you are heading.

  5. 5

    Career OS compounds

    Every piece of work you add, and every person who confirms it, strengthens the picture. The more you build, the more visible your growth becomes.

1 of 9

Where you work best

The room where you do your best work.

The same person thrives in one room and stalls in another. Seven questions ask about the place that gets the best from you: how decisions get made, how much scrutiny you want, the manager you did your best work for.

Cream then reads it back to you in plain words, so you can tell us if we got you right. It is your own account, and it stays that way. It is never scored, and it never narrows what you are shown.

Live for members since September 2026. See the roadmap

Where you work bestAn example
  • How decisions get madeI decide it myself, inside a remit I have been given
  • Freedom and scrutinyA quick word with someone I trust, then go
  • The person you report toSet the direction and left the how to me
  • Support, when everything is newA clear brief and a regular conversation while it is new
  • How the work actually happensClosely with one or two others, most days
  • How far ahead you can seeA quarter. Enough to plan, not so long it goes stale.
  • What the work asks of your timeLong hours around a launch, and not otherwise

What you bring

You make the call inside a clear remit and carry it, and you do your best thinking with one or two people close by.

Where you do your best work

A team that trusts you with the how, stays close while the ground is new, and plans a quarter ahead rather than a year.

Written by AI from your answers. An invented example.

Builder fluency

How far you can take an idea on your own.

The distance between an idea and something a person can use has collapsed. More product people now shape the problem, build enough of it to be real, and stay with it until it is in someone's hands.

It is one of the hardest things to show on a CV, because everyone describes it with the same words. Here it takes a shape, across six dimensions, from the problem you chose to what happened after it went out.

You file a Build Record of one thing you built: the problem, how you worked, how it got out, and who saw it. No code required. A prototype, an automation, a brief that shipped: all of it counts, shown beside your six pillars and never as one of them.

Live for members since September 2026. See the roadmap

Builder fluency, read across six dimensions An invented example, drawn as a shape across six dimensions: strongest in product judgment and shipping ownership, with the least reach in technical shaping. Problemselection Productjudgment Technicalshaping Buildleverage Iterationvelocity Shippingownership
An invented example, read from the things this member built. It reads as an independent shipper.
  1. Level 1ShaperTurns an ambiguous problem into something a team could actually build.
  2. Level 2PrototyperMakes something functional enough for a real person to try.
  3. Level 3Collaborative builderContributes materially to the technical calls, the iteration and the launch.
  4. Level 4Independent shipperTakes a bounded problem from discovery to production with few handoffs.
  5. Level 5System builderShips repeatedly, and builds the things that let other people ship too.

Level 5 is not the target. The level worth having depends on the role, the company and the product, and a record that says which one you are is more useful than one that implies everyone should be climbing. Empty is not low: a record with nothing filed here says nobody has asked yet.

Where you already are

The case you could never quite make.

Ask for more scope and you are asking people to remember whose work it was. They remember the team's.

A record settles it. What you decided, what you held, and someone who was in the room confirming it. Useful the day you want more where you are, and ready whenever you decide to shape what comes next.

  1. 1

    The review you are about to have

    What you did, and who saw you do it. Not a memory anyone has to be talked into.

  2. 2

    The manager who is about to change

    Your record does not reset because the person who knew your work has moved on.

  3. 3

    The conversation you have not decided to have yet

    Built once, ready on the day you want it rather than the week you need it.

Start with one piece of work.

Choose the one that says something about how you think. Add the problem, the decisions you made and what changed, then invite someone who was there to add their perspective.

Everything after that joins the same record. It is never edited, only added to, and it stays yours.