How to Create a Chief of Staff Role at Your Company
Takeaway: The most reliable way to create a chief of staff role where none exists is to solve the problem before you name it. Take on the coordination work a chief of staff would own, prove it relieves real pressure on your leader, then put a scoped, time-bound proposal in writing that makes hiring you the obvious next step.
Plenty of chiefs of staff created their own jobs. The role didn't exist, they saw a leader drowning in coordination and follow-through, they quietly started handling it, and eventually the title formalized what they were already doing. This isn't a lucky accident. It's a repeatable path, and given that McKinsey found almost two-thirds of new chiefs of staff are appointed internally, it's one of the most common ways into the role (McKinsey).
This guide walks through how to build the case, structure the proposal, and define the role so that your leader says yes, and so that the role you create is a real one rather than a relabeled coordinator job.
Start with the problem, not the title
The mistake most people make is leading with the title. They walk in and ask to be made chief of staff. That framing puts the leader on the defensive, because it sounds like a request for a promotion in search of a justification.
Flip it. Lead with a problem your principal already feels. A chief of staff earns their keep by relieving a specific, named pressure, and your proposal should start there. Dan Ciampa's Harvard Business Review case for the role describes the chief of staff as an air traffic controller for the leader and senior team, an integrator who connects work that would otherwise stay siloed, an honest broker, and a confidant (Harvard Business Review). Each of those is an answer to a pain a stretched leader recognizes: too many things competing for their attention, decisions that stall between departments, follow-through that quietly evaporates.
Before you propose anything, get precise about which of those pains your leader has right now. If you can't name the specific problem the role would solve, it's too early to pitch it. Our guide to when a company actually needs a chief of staff can help you diagnose whether the need is real.
Prove the need by doing pieces of the job first
The strongest proposals are backed by evidence, and the best evidence is that you have already started doing the work. Before you formalize anything, take on projects that alleviate your potential principal's workload, and once the working relationship is established and trusted, float the idea of the role (Prime Chief of Staff).
Concretely, that means volunteering to own the cross-functional project nobody is coordinating, running the leadership meeting so it produces decisions instead of updates, or building the pre-reads and briefs that let your leader walk into meetings prepared. Each of these is a slice of the chief of staff job, and each generates a result you can point to. Our guide to landing your first chief of staff role without the title covers how to engineer these openings deliberately.
This does two things. It proves the value of the role in advance, so the proposal describes something the leader has already benefited from. And it proves you're the right person to fill it, which matters because you're making two arguments at once: that the role should exist, and that you should hold it.
Write the proposal
When the relationship is warm and you have evidence, put the case in writing. A short, well-structured document lands far better than a verbal ask, because it lets the leader think it through on their own time and signals that you already operate like the role. The best next step after a first conversation is often to say you will draft a position description based on it, which gives you a concrete deliverable and puts your thinking on paper (Prime Chief of Staff).
A strong proposal covers six things.
1. The problem. Name the specific pressures on the leader and the organization that a chief of staff would relieve. Use concrete examples the leader will recognize, not abstractions.
2. The scope. Define what the role owns and, just as importantly, what it doesn't . This is where you prevent the role from becoming a catch-all. Be explicit that it's not an executive assistant role and not a decision-making role by title.
3. Where it sits. Show the reporting line (directly to the principal) and how it differs from existing roles. A chief of staff that reports three layers down isn't a chief of staff.
4. The mandate. Describe the authority the role borrows from the principal to coordinate across teams it doesn't manage. The role runs on the leader's backing, so name how that backing gets communicated to the leadership team.
5. The first 90 days. Lay out what you would do in the first month, at 60 days, and at 90 days, so the leader can see the role in motion. Ground this in a real plan, like our first 90 days operating plan.
6. How success is measured. Define what "working" looks like: meetings that end in decisions, priority projects that ship, the leader's time freed for the work only they can do. Vague roles fail; measurable ones survive.
Address the leader's concerns before they raise them
A good pitch anticipates resistance. Ask yourself what would make your principal hesitate, and speak to it directly in the proposal. Common concerns include cost, whether the role overlaps with an existing executive assistant or COO, whether it adds a layer rather than removing friction, and how the rest of the leadership team will react to a new person operating with the leader's authority.
You want the leader to get to yes, which means surfacing and addressing their apprehensions first rather than waiting for them to become objections (Prime Chief of Staff). On the overlap question specifically, be clear about how the role complements rather than duplicates. A chief of staff operates a level above the calendar and inbox that an executive assistant owns, and works through influence rather than the formal authority a COO holds. Our comparison of chief of staff vs EA vs COO lays out the distinctions you can borrow.
Define the role so it becomes a real one
Creating the role is only half the job. Scoping it well is what determines whether it succeeds. Two failure modes are worth guarding against from the start.
The first is the catch-all. If the role becomes the place every orphaned task lands, you will be busy and low-leverage, and the role will read as a glorified coordinator seat. Protect scope by tying the role to a small number of the leader's highest priorities, not to an open-ended willingness to do anything.
The second is the mandate gap. A chief of staff has almost no formal authority and works entirely through the principal's backing and earned trust. If the leadership team doesn't understand that you operate with the leader's mandate, you will hit walls constantly. Build the communication of that mandate into the plan, and make sure the principal is willing to reinforce it publicly.
It also helps to understand what kind of chief of staff you're proposing. The role scales differently depending on whether the leader mainly needs execution horsepower, strategic partnership, or organizational glue. Our guide to the three types of chief of staff can help you frame the version your leader actually needs, which makes the proposal sharper.
Negotiate the role and the title together, the pay separately
One practical note. When the role gets approved, resist the urge to let the title stand in for compensation. The scope and the pay are two different conversations, and a new title doesn't automatically carry a raise. Once the role is agreed, negotiate the compensation as its own explicit discussion. Our guides to the chief of staff salary landscape and to negotiating a chief of staff offer cover how to approach that.
Frequently asked questions
What should a chief of staff role proposal include?
Six elements: the specific problem the role solves, its scope and boundaries, where it reports, the mandate it borrows from the principal, a 30-60-90 day plan, and how success will be measured. Keep it short and concrete, and offer to draft the full position description as the next step (Prime Chief of Staff).
Can I create a chief of staff role for myself?
Yes, and it's one of the most common ways in. McKinsey found almost two-thirds of new chiefs of staff are appointed internally (McKinsey). The reliable approach is to solve the problem before naming it: do the coordination work, build the leader's trust, then propose formalizing what you already do.
How do I make sure the role is real and not just a title?
Scope it to a small set of the leader's highest priorities rather than to an open-ended pile of tasks, secure direct reporting to the principal, and make sure the leader will publicly reinforce your mandate with the leadership team. A chief of staff that reports three layers down, owns only logistics, or lacks the leader's visible backing is a coordinator with a fancier name.
When is the right time to pitch a chief of staff role?
When your leader is visibly stretched by competing priorities, stalled cross-functional decisions, or follow-through that keeps slipping, and after you have built enough trust by handling pieces of the work. If you can't yet name the specific pressure the role would relieve, it's too early. Our guide to when a company needs a chief of staff helps you judge the timing.
Should I ask for the chief of staff title before or after proving the value?
After. Leading with the title reads as a promotion request in search of a justification. Prove the value by owning slices of the role first, then propose formalizing it once the leader has already benefited. That sequence lets you argue two things at once: that the role should exist, and that you're the person to hold it (Prime Chief of Staff).
If you're building the case internally, our free chief of staff role proposal template gives you the scope, mandate, and 30-60-90 day structure to adapt for your leader. Join The Brief to grab it, along with our full guide to how to become a chief of staff.
