| Responsibility | Manager scope | Director scope |
|---|---|---|
| Priorities | Turn agreed business priorities into an execution plan. | Resolve competing priorities with functional leaders and set the operating agenda. |
| Systems work | Own process improvements, configuration, and ongoing delivery. | Set ownership and architecture direction; hands-on expectations depend on the team. |
| People | Coordinate contributors and potentially manage a small team. | Plan team capabilities, responsibilities, and development. |
| Decisions | Make decisions within a defined area of ownership. | Establish cross-functional decisions, investment choices, and escalation paths. |
Start with the problem you are hiring to solve
Write down what is not working today. A reporting backlog, inconsistent routing, and a difficult CRM rollout may point to a need for stronger execution. Repeated disagreement about lifecycle ownership or which initiatives deserve resources may point to a leadership gap.
A more senior title will not fix an absence of decision authority. If a new director is expected to align departments, specify which decisions they can make and which executive will support them when priorities conflict.
- What needs to change in the next 90 days?
- Which decisions are already made, and which remain unresolved?
- Who will agree on priorities and remove obstacles?
- Who will handle day-to-day administration while larger changes happen?
When a RevOps manager is the better fit
A manager can fit a team with a clear operating direction that needs someone to run processes and improve execution. The person might own lead lifecycle rules, organize a reporting backlog, and coordinate a CRM change with marketing and sales.
Assess whether the candidate can distinguish a request from the underlying problem, prioritize work, test changes, and support adoption. Ask for an example that continued to work after launch, including the documentation and handoffs they maintained.
When the scope calls for a director
A director may be appropriate when your team needs a shared operating plan, clearer ownership across functions, and decisions about where to invest people and systems effort. That responsibility requires access to leadership and the authority to make tradeoffs.
Ask candidates how they resolved conflicting priorities. Explore what they recommended, who disagreed, what evidence changed the discussion, and how the resulting decision was implemented. Team size alone does not tell you whether someone has done this work.
Make the hands-on expectations explicit
A first operations leader may still configure systems and build reports. Be explicit about how much time that work will take and what support is available. A role that combines strategy, administration, integrations, analytics, and team building needs a realistic sequence of priorities.
Choose two or three initial outcomes and name the responsibilities that will stay with other people. Use the interview to assess the work you need now, then discuss the direction in which the role could develop.
Use questions that reveal the level of ownership
Ask each candidate to separate their own decisions from the work of the wider team. Record the evidence and what still needs verification.
- Tell us about a lifecycle change you owned. Who agreed on the definitions?
- How did you decide which operations requests to defer?
- Describe a time leadership disagreed with your recommendation. What happened next?
- Which part of the work did you perform yourself, and which did you delegate?