What a fractional CPO actually does
Companies in Egypt ask for a fractional CPO when the product decisions have stopped being made. Here is what the role is for, and the part of it that usually gets dropped.
· The Fix · 5 min read
“Nobody here can decide what we build next, so we build everything.”
A founder in Cairo told me that last year, after asking me for a fractional CPO. I had asked him what he wanted that person to do on the first Monday, and that was the answer.
That is the real reason companies go looking for the term. Not the title. The decisions.
What the words mean, plainly
A CPO is a chief product officer. The person who decides what the company builds, in what order, and what it will not build at all.
Fractional means you get that person for part of the week, not all of it. Two days, one day, a fixed number of days a month. You pay for the days you use. You do not carry a senior salary you cannot fill with senior work yet.
Some people call it outsourced product leadership. Same thing. A company of 50 to 250 people has enough product decisions to need the judgement, and not enough to need the chair.
The three things you are actually buying
Someone senior says what you build next and what you drop. The argument ends. Work starts on Monday.
Your own people watch the decision get made, then make the next one with less help.
Why you chose this and refused that, written down where the next person can read it. This is the one that gets dropped.
The first one is easy to buy. Plenty of good people will come in and decide.
The second is harder, and a good engagement will at least try.
The third almost never happens, and it is the one that decides whether the money was worth spending.
Why the third one gets dropped
Because nobody misses it while the person is still in the building.
You ask why the pricing page works the way it does, and you get an answer, because the person who made that call is sitting there. The reasoning lives in their head and their head is in the room, so the company feels like it knows things it does not know.
Then the days end. The person leaves. Six months later somebody asks why the pricing page works the way it does, and the room goes quiet.
I ran product at Shezlong while it moved from debt to profit, and I have watched this happen from the inside more than once. The decisions were good. Six months later nobody could say why they were made.
The work is not the decision. The work is the decision plus the record of it.
What to ask for instead
If you are about to hire someone part-time to run product, ask for three things in writing before the first day.
A decision log. Every real call, one line each: what was decided, why, what was refused, and what would make you change your mind. Not a document nobody opens. One file, added to on the day the decision is made.
A named owner for each decision inside your company. Not the person you brought in. One of yours. They do not have to make the call. They have to be able to explain it after the part-time arrangement ends.
A handover date, set at the start. Write down the day the arrangement ends before it begins. An arrangement with no end date turns into a full-time salary paid in instalments, and everyone stops noticing.
What good looks like after ninety days
A new senior hire can read why the last four big calls were made, without booking time with anybody.
Your team argues about the next decision using the reasoning from the last one, instead of starting from nothing.
And you can stop the arrangement without losing anything, because what you were buying was never a person’s attention. It was the company’s ability to decide, and that stayed.
Most companies that ask us for product leadership have the same thing underneath: the decisions are being made, and nothing is keeping them. Sometimes you do need someone senior part-time. Often you have the judgement already and nowhere to put it.
If any of this reads like your company
The Memory Diagnostic takes two days, in person, and ends with the map of gaps, ranked by cost. Five short questions to start.
Read next