How do you decide when to use ‘head of’ titles?
For many a growing company, it can be a tempting shortcut. You’re not sure you want to call this person a director. Or you’re unsure if the role should actually be a VP. (But you don’t want to build out that leadership layer yet). So we use ‘head of’ as a placeholder.
There’s a little bit of nuance when it comes to internal versus external, which I’ll get to later. Backing out, the primary thing is making sure there is clarity of expectations. And ‘Head of’ is an obstacle to that.
Why ‘head of’ titles happen
We’re often inclined to give ‘Head of’ titles when we:
The eventual realities and conflicts
The impacts of a ‘head of’ title aren’t always immediately felt. Though when it comes time for performance reviews, calibrations, hiring decisions, etc., that’s where it manifests.
Companies are reticent to hire someone with a “VP of X,” title, only for the company to ‘outgrow’ that person, necessitating a seasoned and stage-aligned leader at that level. It entails either demoting the current “VP”, moving them out, or giving them a narrower leadership title.
In the long run, it also creates issues for:
When to actually use it
The narrow band of where ‘Head of’ applies is typically for ‘one of a kind’ roles that are in a highly-specialized function.
I apply four key criteria for ‘head of’ in order to consider using it: