Everything but the deciding.
47 specialists that carry a product decision from the first signal to the honest look back six weeks later. The research, the spec, the review pack, the launch brief — drafted to your standard, every claim carrying a source, waiting on your call. You still decide. You stop typing.
- specialists
- 47 specialists
- lifecycle stages
- 14 lifecycle stages
- end-to-end paths
- 7 end-to-end pathsevery claim cited
Two competitors moved on price since June. Our middle tier has not, and three lost deals said so out loud.
Nine losses this quarter name it. It is currently ranked eleventh on the backlog.
Reordering the next quarter is a decision, not a finding. It is waiting, written up, for you.
Filed as cited evidence against 6 ideas already on the backlog.
An idea is a sheet of possibility.
Pixie Dust Industries gives teams the structure to shape it into something useful. A sheet of paper holds every shape it could become. A sequence of deliberate folds gives it structure, and then a purpose.
Product work goes the same way. An idea gets clearer through questions, decisions, trying things, and refining what came back. The Product OS is that sequence, written down and running. It does not end in perfection. It ends in something people can use, and the next fold.
Nobody took this job to format documents.
And yet the week fills with the tax. The blank page. The fourth rewrite. The research you are certain exists somewhere. The decision relitigated in a meeting because nobody wrote down why it was made. The launch that shipped and was never looked at again.
The part of the job that needed a person — the judgement — gets whatever is left on Friday afternoon.
- Writing the thing up so somebody else can read itEvery time
- Finding the research that already answered thisTwice a month
- Chasing the same five people for the same five viewsEvery decision
- Tidying a backlog nobody can rank without youEvery fortnight
- Going back to check whether the launch did what it promisedAlmost never
The half of the job that is not judgement
Most of a day back. The boring half.
These are the five artefacts a product manager produces over and over. On the left is what each one costs by hand. On the right is what it costs when a specialist drafts it and you edit.
The last row is the one that matters. It was not slow before. It was not happening.
By-hand figures are our own team’s, measured on real work. Yours will differ. Drafting is not deciding: every one of these still comes to you.
Specialists, not a chat window.
Each one owns a part of the lifecycle, knows what it is allowed to touch, and hands its work to the next. Between them they are 47 skills you never have to learn the names of.
A goal, the tools it may reach for, and the standard it works to. It joins the crew and everyone else can call it.
Reads the market, the won and lost deals, and what your own customers are saying, before anybody in the building has formed an opinion about it.
“Two competitors moved on price since June. Our middle tier has not.”
One harness. Every tool you already pay for.
No new place to work. The crew reaches into the tools your team is already in, reads what it needs, and puts the finished thing back where people will find it.
- Ask the backlog
One question, every idea, every piece of evidence hanging off it.
Ideas citing the missing report9Ranked above it10Evidence attached31 - Run the research
An open question becomes a finished briefing, with a source on every claim.
Sources read48Perspectives taken5Claims without a citation0 - Convene the review
Four standing seats argue with the decision before your team has to.
OperatorObjectsDesignAgreesBehaviouralReframes - Attach the evidence
Findings land on the backlog as citations you can open, not as opinions.
From lost deals6From support3From the open web4 - Publish where they read
The finished artefact lands in the tool the team already lives in, in the house format.
SpecPublishedEpicsGroomedLaunch packDrafted - Measure the promise
Six weeks on, the spec is held to the numbers it set itself.
Promised+12%Actual+3%Filed for next timeYes
Illustrative figures · read-only unless a person approves the write
14 stages. 7 paths through them.
Left to right is the lifecycle, signal to shipped to learned. Pick a path and watch where it goes, including where it comes back — the returns are why this is a system and not a pipeline.
What the market, our lost deals and our own customers are telling us, gathered before anyone forms an opinion about it. Everything here ends up as cited evidence on the backlog rather than as a view.
It learns your product. Not the other way around.
Every business speaks its own language, and a template does not. Everything the crew finds lands in the Brain: your definitions, your customers, your history, the reasoning behind calls that were already made.
Which means the work compounds. The next quarter starts where the last one finished, instead of at the beginning, with the same three arguments.
- Born from your own material. It reads what you already wrote down.
- Fluent in your business, not in a template's idea of one.
- Never stops learning. Change course and it follows you.
Who they are, what a shift actually looks like, and what they will never tolerate
What counts as activated here, and why it is not what the last company meant
Who moved, when, and what it cost the deals you lost that quarter
What was decided, by whom, and the objection that was overruled
What a good spec looks like in this house, taken from the ones that worked
Every launch, what it promised, and what it actually did
Illustrative · the Brain holds whatever your team feeds it
You lead. They do the digging.
There is nothing to configure and nothing to keep up to date. The crew changes when the work changes, and it is in your next session.
- 01Say it in your own words
No command to remember and no menu to learn. Describe the task the way you would to a colleague, and the front door names the specialist that fits, or the short chain of them.
- 02Watch the work, not a spinner
You see which specialist is running, what it read, and what it found. Every claim it brings back carries the source it came from, so you can check rather than trust.
- 03You approve. It lands.
Nothing reaches your tracker, your documentation or your team unreviewed. You edit, you approve, and the finished thing goes where the team already reads.
That is three specialists and a review gate. You did not have to know that, and nothing moves until you say so.
Five of the 47.
Underneath the crew are named skills, each doing one job properly. You never have to call one by name, but you can.
- PM CompassFront Door
Describe the task in your own words. It names the one skill that fits and starts it.
- Storm ResearchDiscovery
One topic in, a multi-perspective briefing out, every claim carrying a source you can open.
- Write PRDDefinition
A groomed idea becomes a PRD in the house format, grounded in the persona library, published where the team already reads.
- Steering PackSteering
A slice of the backlog becomes a review pack: one-liners, what is missing, council verdicts, and the order to discuss them in.
- Metrics ReviewMeasure
Six weeks later, the same PRD is measured against the numbers it promised, and told plainly when it missed.
- See the catalogueAnd 42 more
Intake, grooming, the council that argues with you, tracker hygiene, the whole launch suite. The full catalogue is behind the door.
What keeps it honest.
None of this replaces a product manager. It removes the tax on being one: the blank page, the fourth rewrite, the research you know exists somewhere, the decision relitigated because nobody wrote it down.
What is left is the part that needed a human all along.
- A person signs off anything that counts.
Those are the yellow gates on the map, and they do not move. Nothing reaches your tracker or your documentation unreviewed.
- Every claim carries a citation.
Research that cannot be traced to a source does not ship as research. You can open the link and check it.
- Findings compound.
What the team learns lands in the Brain, so the next quarter starts ahead of the last one instead of at the beginning.
- It cannot drift.
This site, the map and the catalogue are generated from the skills themselves. If it says we do it, we do it.
The questions people ask first.
Nearly always the same eight, and nearly always in this order. Anything else, ask a person — you will get an answer rather than a ticket number.
01Does it write things and put them live without me?
No. Every stage that commits to something sits behind a review gate — the yellow ones on the map above. The crew drafts, cites and proposes; a person approves before anything reaches a tracker, a document or a customer.
02What do I actually get out of one of these?
A finished artefact in your house format, with the reasoning and the sources attached: a briefing, a spec, a review pack, a set of groomed epics, a launch pack, or a scorecard against what you promised. Not a chat transcript.
03Do I need to learn commands?
No. Describe the task in your own words and the front door names the specialist that fits and starts it. The named commands exist for people who like them.
04Is this just a prompt library?
No. A prompt gives you words back. These reach into your real tools, read your real backlog and your real deal history, attach evidence you can open, and put the finished work back where your team reads it.
05What happens to the research when someone leaves?
It stays. Everything the crew finds is filed in the Brain rather than in a thread, which is the difference between a team that compounds and one that starts over every time somebody moves on.
06How long until it is useful?
The first session. The crew works from what you already have written down, so the first briefing or spec comes back the same day rather than after an onboarding project.
07How do I know it is not making things up?
Because a claim without a source does not ship as research. Every finding carries the link it came from, and you are meant to open them. Where it does not know, it says so rather than filling the gap.
08Who can get in?
Access is granted per person today while this is still being run in anger by one team. Sign in below and we will sort it out.
Learn it once.
Product work is a small set of moves repeated forever. Written down, the standard stops depending on who is having a good week.
Access is granted per person while this is still young. No card, nothing to configure.