SELICOR CONSULTING

When you should hire a Head of Data, and when you shouldn’t

The title is easy. The mandate is the hard part.

Head of Data is one of the most requested roles in the market, and one of the most frequently misunderstood. Some organisations need a leader to build a data function from scratch. Others need a leader to stabilise foundations and governance. Others need a leader to unlock value from an existing team that is busy but not moving the business.

If you hire the wrong version of this role, you will see the same pattern. Slow progress, frustration, and a growing sense that data is expensive but unclear. This is rarely a people problem. It is almost always a clarity problem.

Signs you are ready to hire a Head of Data

• There is a clear business problem to solve, not just a desire to “do more with data”.
• Leadership agrees on priorities, even if the delivery path is not yet perfect.
• Data has multiple stakeholders and you need a single owner for alignment and decisions.
• You have demand coming from the business that cannot be met with ad hoc reporting.
• There is a budget and runway to build capability over time, not a quick fix expectation.

Signs you should not hire one yet

This is the part most people skip. If any of these are true, the role is likely to become a scapegoat.

• No one can define success in 12 months. If the outcome is vague, delivery will be judged emotionally.
• There is no executive sponsor. A Head of Data without cover will spend their time negotiating for basics.
• You are hiring the title to solve a political problem. It will not hold.
• The organisation is not ready to make decisions. Data work will stall in committees.
• You expect one leader to fix engineering, analytics, governance, and AI without a plan or team.

The three common versions of Head of Data

Most briefs accidentally combine three roles. Clarifying which version you need is the quickest way to improve hiring outcomes.

• 1) The foundation builder
  Focus: data platform basics, data quality, governance, and first delivery wins.
  Best when: you are early stage or rebuilding after years of drift.
• 2) The operating model leader
  Focus: aligning stakeholders, defining product and delivery shape, prioritisation, and measurable value.
  Best when: you have talent in place but outcomes are inconsistent.
• 3) The scale and optimisation leader
  Focus: reliability, performance, cost control, and scaling a mature data estate.
  Best when: you already have a platform and need industrial strength operations.

A good hire can flex across areas. A bad brief forces them to do everything, at once, with limited authority.

What to clarify before you write the job spec

If you do nothing else, answer these questions internally. They remove ambiguity, speed up hiring, and make strong candidates lean in.

1. Who owns data at board level, and what decisions can the Head of Data make without escalation.
2. Where the role sits, and what “good collaboration” looks like with technology, product, and commercial teams.
3. The first 90 days, including what must be delivered and what is explicitly out of scope.
4. Your governance stance, including privacy, security, access, and what is non negotiable.
5. Your measurement approach, so you track outcomes, not activity.

What good looks like in 12 months

A strong Head of Data hire usually creates visible progress in four areas. Not all at once, but with a clear sequence.

• Clarity: a shared definition of priorities, ownership, and decision routes.
• Foundations: the basics are stabilised, and people trust the data more than they did.
• Delivery: a predictable cadence of work that ties to business outcomes.
• Momentum: a hiring and capability plan that matches reality, not ambition.

A simple hiring approach that works

• Step 1: pressure test mandate, reporting line, and success metrics.
• Step 2: decide which version of the role you need most.
• Step 3: write a spec that reflects your reality and your constraints.
• Step 4: interview for decision making, stakeholder influence, and delivery pattern.
• Step 5: be honest about what support exists today, and what will be built.

FAQ

• When should we hire a Head of Data?
  Hire when you have clear business outcomes to deliver, leadership alignment on priorities, and a need for a single owner to align stakeholders, governance, and delivery.
• What are signs we are not ready to hire a Head of Data?
  If success is vague, there is no executive sponsor, decisions take weeks, or you expect one person to fix platform, analytics, governance and AI at once, the role will likely struggle.
• Who should a Head of Data report to?
  It depends on the mandate. If the role is platform heavy, reporting into technology can work. If the role is outcome and prioritisation heavy, reporting into a business leader can work. The key is clear authority and decision rights.
• What should a Head of Data deliver in the first 90 days?
  Clarity on priorities, ownership and decision routes, an initial operating model, and a realistic plan for foundations and delivery. Early wins matter, but only if they support a sustainable cadence.
• How do we avoid hiring the wrong Head of Data?
  Define the version of the role you need, set measurable success criteria, be honest about foundations and constraints, and interview for decision making, stakeholder influence, and delivery patterns.

If you want to go deeper

I also have a dedicated guide on Head of Data recruitment, including how to shape the search and how to avoid common market pitfalls. If you are unsure whether you need a Head of Data now, we can sanity check it quickly before you go to market.

Back to Insights Talk through a role