Hiring a Head of Product? Stop shopping for a miracle

A Head of Product hiring brief often starts with a reasonable frustration: the company is building things, but leadership cannot explain why these things deserve the investment. Then the brief expands. The new person must repair delivery, discover the market, motivate the team, understand AI, win customers and somehow keep every stakeholder happy.

These needs may be real. They do not automatically form one coherent job. Before evaluating candidates, agree which problem the role must own, which problems require partners and which conditions you are prepared to change. A polished executive hire can spend months absorbing ambiguity that the hiring team could have discussed before the first interview.

Name the business situation before choosing the title

Consider three hypothetical companies. One is still searching for a customer problem people will pay to solve. Another has repeat customers but an overloaded development team. A third has several product teams making decisions that pull in different directions. Each may advertise for a Head of Product. Each needs a different balance of hands-on discovery, delivery coordination and organisational leadership.

Write a plain paragraph describing your situation. Include customers, commercial constraints, team size, current decision-making and the most expensive uncertainty. Ask the CEO, engineering lead and hiring manager to write it independently. Differences in their answers are useful evidence, even if collecting them briefly makes the room less comfortable.

A title cannot settle those differences. Agree them before candidates have to guess which version of the job will appear after they sign.

Define the mandate the person can actually exercise

List the decisions the Head of Product will own. Can they reorder work? Stop an initiative? Access customer evidence? Challenge a sales commitment before it becomes a promise? Hire or coach the people needed to deliver? Which decisions remain with the founder or executive team?

Then list the constraints. There may be fixed contractual commitments, a restricted budget or a founder who intends to remain the product visionary. None of this is inherently disqualifying. It becomes difficult when the advertisement promises autonomy and the interview quietly describes an elaborate approval route.

A useful sentence is: “The person can decide X within these limits, while Y remains an executive decision.” Candidates who ask about this are investigating whether they can do the work. They are not necessarily demanding a throne with ergonomic armrests.

Look for evidence of developing people

A strong individual product manager may be excellent at their own work and still need support to lead others. In The VP Product Role, Silicon Valley Product Group identifies team development as a central responsibility, including recruiting, training and coaching. Treat leadership as a skill to investigate directly.

Ask for an example of helping someone make a better decision over time. What did the candidate notice? What feedback did they give? How did they adapt when the first attempt failed? What could the colleague eventually do without them? Respect confidential details and allow anonymised examples.

Also ask about a disagreement with engineering or sales. Good answers usually contain the other person's legitimate concern, the evidence available and the tradeoff agreed. “I convinced everyone” tells you less than an explanation of what the candidate changed in their own recommendation.

Test judgement through a bounded conversation

Use a short hypothetical case with incomplete information. For example, a software company has falling activation, a promised reporting feature and a request to introduce an AI assistant. Ask what the candidate would investigate first, what they would delay and which assumptions could change their choice.

Provide the same case and evaluation criteria to candidates. Keep the exercise proportionate and avoid collecting unpaid solutions to a live company project. You are looking for reasoning, questions and collaboration. The person with the prettiest slides may simply have found the better template.

During the conversation, reveal one new constraint. Perhaps the reporting feature is contractually committed, or the activation measure includes customers who have not finished onboarding. Watch whether the candidate updates their view. Calm adaptation provides more useful evidence than defending a first answer at all costs.

Distinguish learning speed from instant certainty

Your company contains history a new person does not know. A candidate who immediately claims to know the answer may be simplifying away that history. Ask how they learn a business, which people they involve and how they separate observed problems from attractive explanations.

Domain experience can shorten some learning. It can also bring assumptions from a different market. Decide where it is essential and where transferable judgement matters more. A regulated product, a consumer app and an internal workflow may require different specialist partners even when the product leadership principles overlap.

If AI is central to the role, ask how the candidate would choose a workflow, evaluate quality, involve users and assign human responsibility. Naming the newest tools is easy. Explaining when a tool should not be introduced is often more informative.

Make the first 90 days an agreement

A hypothetical first month could focus on learning: customer conversations, decision mapping, delivery observation and agreement on the most important problem. The next month might test a specific change, such as clearer onboarding priorities or a smaller release scope. The third could establish how the team reviews results and adjusts investment.

These are planning examples, not guaranteed milestones for every company. Specify what information and access leadership will provide. Agree which existing commitments remain in place during diagnosis. A new leader cannot establish a credible baseline if the underlying priorities change after every executive conversation.

• What will we understand better after the first month?
• Which decision or workflow will improve first?
• What evidence will tell us the change helped?
• Who will partner with the new leader?
• What support will the executive team provide?
• Which expectations should wait until more is known?

Choose the right shape of support

A full-time leader makes sense when product direction and team development need sustained ownership. A focused consulting engagement can suit a bounded diagnosis or stalled initiative. Fractional support may fit a recurring leadership need below a full-time workload, provided availability and authority match the work.

Discuss these options against the actual problem. Using an external adviser without an internal decision owner can create reports that nobody is authorised to use. Hiring permanently before clarifying the mandate can embed the same uncertainty at a higher monthly cost.

For the organisational issues behind the vacancy, read how founder approval becomes a bottleneck and how to turn an overloaded roadmap into choices. My AI product leadership page explains my approach to product strategy, practical AI adoption and delivery. If that matches your situation, bring the business problem, the decision mandate and the team context to our first conversation.

Questions people ask

When should a company hire a Head of Product?

Consider the hire when product direction, investment choices and team development need sustained ownership beyond what the founder or existing managers can provide. First clarify the business problem and decision mandate. An overloaded backlog alone does not establish the need. A focused diagnosis, delivery improvement or experienced individual contributor may fit the situation better than a permanent leadership appointment.

What should I ask a Head of Product candidate?

Ask how they learned a business, changed priorities using evidence, developed other people and handled a disagreement with engineering or sales. Use a bounded hypothetical case to discuss assumptions and tradeoffs. Look for clear reasoning and willingness to update their view. Avoid relying only on presentation polish, tool names or broad claims about achieving alignment.

What should a new Head of Product achieve in 90 days?

Agree a plan suited to the company rather than a universal checklist. Useful early goals include understanding customer problems, mapping decision rights, identifying a costly bottleneck and testing one focused improvement. Establish the evidence for reviewing that improvement and the support leadership will provide. Commercial outcomes depend on the product, market, available resources and existing commitments.