The Level Decision and Why It Matters
The decision between hiring a VP and a Director for a leadership role is one of the most consequential early-stage organisational design choices — and one of the most frequently made incorrectly. The error is almost always in the same direction: companies hire a Director when they need a VP, typically because the Director is cheaper, less intimidating, or feels more proportionate to the current team size. They discover 12–18 months later that the function has hit an execution ceiling that the Director's authority and capability cannot break through.
The cost of this error is not the Director's salary — it is the 12–18 months of suboptimal function performance, the replacement search cost when the Director leaves or is let go, and the organisational disruption of running the function at Director level when VP-level challenges require VP-level authority and approach.
Hire a Director When
The function is early-stage and primarily needs to execute a playbook, not design one
The team is 2–4 people and the primary challenge is task execution, not team architecture
The CEO or a more senior leader can provide the strategic direction for the function
The scope of authority required is within a function, not cross-functional
The primary development opportunity is enough for a strong Director who will grow
Hire a VP When
The function needs to design its own operating model, not execute a pre-designed one
The team will scale to 8–20+ people within 18 months and needs architecture, not management
The CEO cannot provide strategic direction for this function and needs a genuine thought partner
The function requires cross-functional authority and board-level communication
The function is a primary competitive driver where quality of leadership is directly revenue-impacting
The Cross-Functional Authority Test
The most reliable test for whether a role needs VP-level authority: does the person in this role need to be taken seriously in rooms where decisions are made about the company's direction, resources, and priorities? A Director of Engineering who needs to influence the product roadmap, advocate for engineering resources in the leadership team, and be heard by the CEO on technical strategy needs VP-level authority to do that job effectively. A Director without that authority will find themselves in the position of influencing upward constantly — which is exhausting, inefficient, and ultimately not sustainable.
The Team Size Heuristic
A rough heuristic that has significant exceptions but holds often enough to be useful: if the team being led will exceed 6–8 people within 18 months, hire a VP. If the team will remain at 4–6 people for the foreseeable future, a strong Director may be appropriate. The reason is not that larger teams require VP titles — it is that building and architecting a team of 10+ people requires the VP-level skills (hiring philosophy, org design, performance management culture, cross-functional relationship building) that are genuinely different from the Director-level skills of managing a small, already-assembled team.
The Upgrade Pressure Signal
The most reliable indicator that you hired at the wrong level: the person in the role consistently needs to escalate to you for decisions that should be in their authority. A Director who is constantly asking the CEO for permission to make decisions that should be theirs is in a role that needs VP authority — or is a Director who is not yet ready for VP authority. Either way, the solution is either an upgrade of the role or a change in the person.
"41 days. A $275K search. Two firms failed in 60+ days. That's not luck — that's a different system."
— Majhi Group case study. Read the full case study →