Chief Product Officer: The Role That Decides What Gets Built
A Gulf group hires a chief product officer when a branch-led business goes digital. The role works only if the chief executive says who has the last word.
Subscribe to our newsletter
A standing brief on the executive search and leadership market across the Gulf.
A Gulf group usually hires a chief product officer for one reason. A business that was built to sell through branches, shops or a sales team has decided to sell through a screen as well, and someone has to decide what that screen does. The role works only when the chief executive has settled, before the person arrives, who has the last word on the customer's journey. In JOH Partners' experience that decision is often missing, and its absence explains most of the disappointments. This piece sets out how the chief product officer differs from four neighbouring roles, why Gulf groups tend to create it, and what a board should agree before it opens a search.
A chief product officer is hired to decide, not to design
The title sounds creative. The job is mostly about saying no. A group that has launched an app, a portal or a digital service has a long list of things it could add: a new feature for the sales team, a different journey for a particular customer segment, an integration a partner has asked for. Every one of those has a senior colleague behind it. The chief product officer is the person who ranks them, funds a few and turns the rest down.
That means the role carries an authority question that the technical roles do not. A chief technology officer can succeed by delivering what was asked, on time, to a standard. A chief product officer cannot succeed that way, because nobody has told them what to ask for. They have to decide, and then stand behind the decision when a branch head or a chief commercial officer objects.
Four neighbours who each think they own the customer
The role sits among four others, and boards that blur them end up with arguments that look like personality clashes but are really missing boundaries.
The chief technology officer builds and runs the platform. The chief digital officer takes an existing business and moves it online, which is a change mandate with a conversion target. The chief marketing officer brings customers in and decides how the offer is described. The chief commercial officer owns the revenue number and the relationships that deliver it.
The chief product officer decides what the product is. That sentence sounds obvious until a quarter-end arrives and the commercial head wants a discount feature built in a week, the marketing head wants a sign-up flow shortened, and the technology head says both will delay a security fix. Someone has to decide. If nobody has been given that authority, the loudest voice wins, or the chief executive is pulled in to settle every dispute, which defeats the point of having hired the role.
A product leader who never disagrees with the chief executive is not doing the job. The one worth hiring says no, and is right often enough that the chief executive keeps asking.
Why the role turns up in Gulf groups, and what it replaces
The roles around it are older than it is. In most Gulf groups, a bank, a retailer, a telecoms business or a logistics operator already has people whose job it is to sell, to deliver and to serve. The product role arrives when the group decides that some part of the customer relationship will be run through software, and that the software needs an owner who thinks like a customer rather than like a department.
What it usually replaces is a committee. Before the appointment, product decisions are taken by whoever runs the relevant business line, with the technology team as a service provider. That works while the digital part is small. It stops working when the digital part carries a meaningful share of revenue, because the business lines then compete for the same engineering time and nobody is accountable for the whole.
Allan Abbas, a fintech founder and former Amazon operations leader, talks in his conversation on the gap between corporate discipline and startup chaos about moving between the two worlds. It is a useful listen for any board that is hiring a product leader from a technology company into a group with a longer history. The person arrives used to deciding quickly. The group is used to deciding together.
JOH's research on the revenue mandate beneath the Gulf chief executive is the companion read on the commercial side of that tension, and its research on the innovation mandate covers the neighbouring question of growth through what the group does not yet sell.
The decision a chief executive should make before the search
Three things should be settled before the first candidate is met, and the chief executive should be the one to settle them.
The first is the final word. Decide which questions the chief product officer decides alone, which they decide after consulting, and which stay with the chief executive. Write the list down and share it with the commercial, marketing and technology heads before the appointment is announced.
The second is the power to remove. A product that can only grow is a product nobody owns. The appointee needs authority to switch things off, including things a senior colleague asked for. Without that, the role is a backlog manager with a senior title.
The third is the measure. Be specific about how the person will be judged in the first year. A number tied to customer behaviour, such as how many customers complete a journey or how often they come back, is a better measure than delivery against a roadmap, because a roadmap can be met perfectly and still produce the wrong thing.
JOH's work building group-level functional leadership at a Saudi industrial holding shows how much easier these arrangements are to set up when a group is building several senior functions at once under a single, clear agenda from the chief executive. The same discipline applies to this appointment on a smaller scale.
What a failing mandate looks like
What follows is a composite. It combines patterns from several mandates and describes no single client.
A diversified retail and services group appoints a chief product officer from a well-known technology company to run its customer app. In the first six months the new appointee redesigns the sign-up journey and the app's ratings rise. In the second six months the group's largest business line asks for a loyalty feature that fits its own sales campaign but cuts across the journey the product lead has just simplified. The chief executive, wanting peace, asks for a compromise. The feature ships in a reduced form. The next request arrives within a month, and the pattern repeats.
By the end of the second year the app has a dozen features, each with a sponsor, and no clear idea of who it is for. The chief product officer leaves. The group concludes that it hired the wrong person. In JOH's experience the more accurate diagnosis is that it hired a decision-maker and never gave them a decision.
If a group wants a product leader, the chief executive has to accept being told no by one. Without that, it has hired a project manager with a bigger title.
Pricing the role
Pay for the role does not behave like pay for other senior technology appointments. At growth-stage companies, a large part of the value can sit in equity, and a cash figure alone understates the package. At a Gulf group with no equity plan to offer, the opposite problem appears: an offer pitched on cash alone can look generous and still miss what the candidate is actually comparing it with. JOH's benchmark of chief product officer packages across three markets, which shows cash and equity separately is the reference JOH points boards to when they are working out which problem they have.
Boards weighing the appointment should also ask how they will know, a year in, whether it is working. Platforms such as Board Pulse let a chair or a people committee follow how senior appointments are performing against the brief they were given, rather than discovering the answer at the annual review. The question is worth putting at the start: what would we expect to see after twelve months if this person has been given real authority, and what would we see if they have not?
The same logic applies to the sector. The technology and digital sector page sets out how JOH approaches senior product and technology appointments for groups that are building a digital business next to an older one.
Key takeaways
JOH Partners is an executive search and senior executive recruitment firm advising boards, family groups and sovereign-adjacent platforms on chief product officer and wider technology and digital appointments across the GCC, the UK and Singapore. A chief executive deciding whether the group needs this role, and what authority it would carry, can engage a partner for a confidential conversation, or request a Board Pulse demo to see how senior appointments can be followed against their brief.
Questions about this topic.
What is the difference between a chief product officer and a chief technology officer?
A chief technology officer decides how things are built and keeps them running. A chief product officer decides what gets built, for which customer, and what gets switched off. In a Gulf group the two are often hired within a year of each other and the line between them is rarely written down. Boards that write it down before either appointment is made have far fewer disputes about priorities later.
How is a chief product officer different from a chief digital officer?
A chief digital officer is usually given an existing business and asked to move it online, which makes the mandate about conversion and change. A chief product officer is asked to decide what the product is, and to keep deciding it as customers and competitors move. Some groups need only one of the two. Groups with several customer-facing businesses often need both, with a clear rule about who decides when they disagree.
Why do chief product officers often struggle in Gulf groups?
In JOH's experience the usual cause is not the person but the arrangement. The appointee is given responsibility for the customer journey without the authority to overrule the commercial or branch heads whose targets that journey affects. A product leader who cannot say no to a senior colleague is running a backlog, not a product.
How should a board test whether a chief product officer is working?
Ask what has been switched off in the last twelve months. Products and features that are only ever added are a sign that nobody has the authority to remove them. A second test is how many senior colleagues the chief product officer has overruled, and whether the chief executive backed them each time.
Does pay for a chief product officer differ much from other C-suite roles?
It can, because at growth-stage companies a large part of the value sits in equity rather than cash. JOH benchmarks the role across several markets with cash and equity shown separately, since a cash figure alone understates the package where equity applies and overstates it where the group has no equity plan to offer.
Oliver Helvin
Founder and Managing Director
Oliver Helvin is the Founder and Managing Director of JOH Partners. He writes on the GCC executive market, leadership transitions in family-controlled businesses, and the discipline of senior search.
LinkedIn ↗Read next.
Tell us about the role.
We’ll tell you who’s right.
Confidential conversations with the partner leading the practice you need. We respond within one business day.