By Deep Work Club · Last updated: October 2026 · Reading time: 12 minutes
A chief of staff (CoS) is the right hand of a CEO or founding team: a generalist role without a functional area of its own, which keeps strategy, priorities and the leadership team aligned and takes on everything that matters but has no owner yet. That is why the chief of staff role and responsibilities look so different from one company to the next. This article explains what a chief of staff in a startup actually does, which types exist, how the role differs from founders associate, COO and executive assistant, and where its typical tensions lie. It draws on research, a McKinsey analysis and our work with founders, leaders and chiefs of staff in Berlin startups.
Key takeaways
A chief of staff works directly for the CEO or founding team, usually without a functional area or a team of their own. The role keeps strategy, priorities and the leadership team together and takes on topics without an owner.
The role is temporary by design: in a McKinsey analysis of around 250 chiefs of staff, median tenure was 2.3 years. Two thirds were promoted afterwards.
Two themes come up again and again in our work with chiefs of staff and founders associates: feeling alone in the role and the question of the next step.
The typical tension is responsibility without ownership: you care as if it were your own company, but without your own area and only with borrowed authority.
Organisational psychology calls the underlying problem role ambiguity. A meta-analysis links unclear roles to weaker performance, while conflicting expectations barely are.
What is a chief of staff?
A chief of staff is a leadership role without a line of its own: the person works directly for the CEO, the founding team or another executive, prepares decisions, drives the most important initiatives and closes gaps nobody owns yet. They are responsible not for one area but for how all areas work together.
The title comes from the military and politics. In the White House, Sherman Adams, who started in 1953 under President Eisenhower, is recorded as the first chief of staff. According to McKinsey, the corporate role emerged in the second half of the 20th century, inspired by these precedents.
In startups, the role is often less clearly defined. Early on, a chief of staff takes on much of what nobody else does. As more specialists join the departments, more of that moves elsewhere. The role fills gaps and changes with every gap that gets closed.
What does a chief of staff do? Responsibilities at a glance
A chief of staff usually covers six areas: keeping strategy and planning on track, running the leadership team's rhythm, preparing board and investor meetings, driving projects without an owner, building structures for growth, and acting as the CEO's sparring partner and filter. Which of these dominates depends on company stage and founding team.
Area | What it includes | Typical in a startup |
|---|---|---|
Strategy and planning | Annual and quarterly planning, setting and tracking OKRs and KPIs | OKR process, KPI dashboard |
Leadership team rhythm | Agendas, preparation and follow-up of leadership meetings and offsites | Weekly, offsite, decision log |
Board and investors | Board meetings, investor updates, fundraising materials | Board deck, data room |
Projects without an owner | Taking on topics until someone owns them | Building hiring, introducing a CRM, interim lead |
Structures for growth | Creating processes, roles and decision paths | Rebuilding processes that grew organically |
Sparring and filter | Preparing decisions, protecting priorities, delivering uncomfortable messages | What reaches the CEO and what doesn't? |
According to McKinsey, chiefs of staff earlier in their careers tend to focus on KPIs, board meetings and projects, while experienced ones more often act as their principal's proxy in discussions and decisions.
In startups, the focus is often on building: the team is stretched thin, and beyond hiring, someone has to build the structures new people can grow into. That often lands with the chief of staff.
What types of chiefs of staff are there?
In our work with chiefs of staff, we keep meeting four types: the generalist after the first year, the young founders associate, the jump candidate and the CoS before the leadership step. They differ less in title than in the question on their mind.
Type | Typical situation | The question behind it |
|---|---|---|
Generalist after the first year | The foundations are in place, specialists take over topics, the role narrows, or you are responsible for everything and own nothing | How do others do it, and what comes next? |
Young founders associate | Early to mid 20s, directly with the founder, many projects without prior experience | Am I good enough for what they trust me with? |
Jump candidate | CoS at a fund or associate who wants to found a company or become an operator | What does the next step actually look like? |
CoS before the leadership step | More often in larger companies, shortly before a role with a team | How do I lead people instead of projects? |
A common type is the generalist after the first year: little distress, clear questions, above all how other chiefs of staff shape their role.
For young founders associates, the themes are more internal: a quiet worry about not living up to the founders' trust. More on this in the article on impostor syndrome as a leader.
One difference from McKinsey's sample of around 300 organisations worldwide: there, chiefs of staff had just over twelve years of work experience on average, and nearly two thirds were appointed internally. In the Berlin startups we work with, chiefs of staff are often much younger, frequently ex-consultants, and only a short time into the role.
Chief of staff vs founders associate vs COO vs executive assistant: what's the difference?
The chief of staff is responsible for how the areas work together, not for an area of their own. The COO runs operations with their own team and budget. The founders associate is usually an entry-level role for projects directly with the founder. The executive assistant manages the CEO's calendar, communication and logistics.
Role | Focus | Own area or team | Authority | Typical entry |
|---|---|---|---|---|
Chief of staff | Executing strategy, leadership team, topics without an owner | Usually no | Borrowed from the CEO | Consulting, strategy, operations |
Founders associate | Projects and analyses for the founder | No | Low, project-based | University, first years of work |
COO | Operations, processes, results | Yes, with line responsibility | Own, formal | Experienced operators or managers |
Executive assistant | Calendar, communication, organisation for the CEO | No | Administrative | Assistant roles, office management |
In practice the lines blur: some CoS roles are effectively a stepping stone to COO, and some companies call their founders associate chief of staff. In Harvard Business Review, Dan Ciampa argues that CEOs need more support than an executive assistant can provide. Still, many chiefs of staff first have to explain what they actually do, and that they are not the person who runs the CEO's calendar.
What makes the role so demanding? Three typical tensions
The role carries three tensions: responsibility without ownership, being alone in a position few people understand, and prioritising between several strong founders. In our work with chiefs of staff and founders associates, these themes come up again and again, alongside three more:
Topic | How it shows up |
|---|---|
Alone in the role | No sparring at eye level, neither in the team nor with the founders |
Unclear next career step | The question of where the role leads often comes up after about a year |
Impostor feelings and comparison | Lots of responsibility early in a career, few benchmarks |
Prioritising | Requests come from all sides, often from several founders at once |
Responsibility without ownership | Involved in everything, but without decision rights of your own |
Building structures for growth | Creating processes and roles while the team grows faster than the organisation |
1. Responsibility without ownership: involved in everything, in charge of nothing
Many chiefs of staff describe it like this:
"I feel responsible for the whole company, but I get to decide almost none of it."
The flip side: if you work on every objective, in the end you're not truly accountable for any of them. And anything without a clear owner lands with the chief of staff first.
Research calls the feeling that something is "mine" without legally owning it psychological ownership (Pierce, Kostova and Dirks, 2001). It makes chiefs of staff good at their job and, at the same time, makes it hard to draw boundaries, because every problem of the company feels like your own, even when the decision lies elsewhere.
Then there's the question of when to simply execute and when to mirror something back to the CEO. How to phrase disagreement so it lands is covered in the article on Radical Candor.
2. Alone in a role nobody understands
Chiefs of staff sit between the team and the founders: take load off above, bring calm below. Offloading your own stress onto the team feels wrong, and the founders are the very people you're meant to relieve.
A sentence we hear again and again in our work with chiefs of staff:
"Only other chiefs of staff really understand what this role is like."
Friends and mentors rarely understand the role, and CoS events often stay superficial, because everyone shows up polished and hardly anyone talks openly about what's hard. Leaders further up know the pattern too, see The higher you go, the quieter it gets.
3. Prioritising between founders
With several strong founders, everything that sits between them lands with the CoS. And whoever delivers well gets even more. The dilemma: you don't want to pit the founders against each other, but you don't want to be seen as someone who resists work either. Some chiefs of staff develop their own protective strategies, such as deliberately downplaying their role so that fewer requests reach them.
Why does the role so often feel unclear?
The role feels unclear because it is. Organisational psychology calls this role ambiguity: a lack of clarity about what belongs to your role, what is expected and how success is measured. It is more closely linked to weaker performance than conflicting demands are, and it is the core problem for many chiefs of staff.
Robert Kahn and colleagues described role conflict and role ambiguity as sources of stress in organisations in 1964. In 1970, John Rizzo, Robert House and Sidney Lirtzman developed the questionnaires that became the research standard and showed the two are different things: with conflict, expectations contradict each other; with ambiguity, they are missing.
A meta-analysis by Tubre and Collins (2000) found a negative relationship between role ambiguity and job performance (r = −.21), but hardly any between role conflict and performance (r = −.07). Applied with caution: three founders with different wishes are less of a problem than a mandate nobody ever wrote down.
How long do people stay chief of staff, and what comes next?
The role is usually a stage, not a destination. In McKinsey's analysis of around 250 chiefs of staff, median tenure was 2.3 years. Two thirds were promoted afterwards, on average by more than one level, 18 percent moved laterally, and only one in ten went straight into another chief of staff role.
Four in five stayed in the same industry, typically at the same company. The data is not specific to startups. In our work with chiefs of staff in startups, the question often comes up after about a year, and many deliberately don't want to stay in the role too long.
Behind it lies a paradox: the better a chief of staff does the job, the smaller the role becomes. If you scale the organisation well, you make yourself partly redundant. Which paths come next and how to tell it's time is covered in What comes after chief of staff?.
Three things for this week
Write down your mandate. Half a page: What belongs to your role and what doesn't? How does your CEO measure your success? When do you execute, and when do you push back? Discuss it in your next 1:1. Wherever your answers differ, you've found the most important conversation of the quarter.
Make an owner list. Write down everything that sits with you only because nobody else owns it. Give each topic a future owner and a date. Whatever shouldn't get another owner is truly yours.
Find a peer outside the company. One or two chiefs of staff in a similar situation you talk to regularly and confidentially, not just at events. That is what the Leadership Circle is for, also as a group just for chiefs of staff. How this kind of peer learning works is explained in Peer learning for leaders.
FAQ
What does a chief of staff do in a startup? They work directly for the CEO or founding team: track strategy and OKRs, run the leadership team's rhythm, prepare board meetings and take on projects without an owner, such as hiring, processes or new structures.
What is the difference between a chief of staff and a founders associate? A founders associate is usually an entry-level role handling projects and analyses for the founder. A chief of staff co-steers the leadership team and acts with the CEO's borrowed authority. In young startups, the two roles often blur.
Is a chief of staff part of the C-suite? Not in the classic sense. A chief of staff usually has no area or budget of their own. Their influence comes from proximity to the CEO, not formal power. Whether they sit on the leadership team is up to the company.
How long do people typically stay chief of staff? In a McKinsey analysis of around 250 chiefs of staff, median tenure was 2.3 years, and two thirds were promoted afterwards. In startups, the question of the next step often comes up after about a year.
What background do chiefs of staff have? According to McKinsey, about half come from strategy or operations, with just over twelve years of work experience on average. In Berlin startups, chiefs of staff are often much younger and frequently ex-consultants.
Where can chiefs of staff find exchange with peers? Through informal circles, events and investor networks, which many find superficial or too infrequent. More depth comes from a fixed, confidential group with the same people over months, such as a facilitated peer group just for chiefs of staff.
In summary
A chief of staff holds together what grows faster than the structures in a startup: strategy, leadership team, board and the topics without an owner. The role is broad, influential and temporary by design. Its typical tensions are responsibility without ownership, being alone and prioritising between founders, and behind all three sits role ambiguity. Writing down your mandate, handing topics to owners and finding peers outside the company doesn't make the role smaller. It makes it clearer.
Don't want to figure this out alone? In the Leadership Circle, up to ten leaders from Berlin startups and scale-ups meet regularly, facilitated by Lea Mersch, also as a group just for chiefs of staff. Book a free intro call
Sources
Goodman, A., Rochford, C., Ramsay Gray, O., & Johnson, P. (2024). Chief of staff: Anatomy of the role in eight charts. McKinsey & Company, 29 August 2024. https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/chief-of-staff-anatomy-of-the-role-in-eight-charts
Ciampa, D. (2020). The Case for a Chief of Staff. Harvard Business Review, May–June 2020. https://hbr.org/2020/05/the-case-for-a-chief-of-staff
The White House (1999). Meet Chief of Staff, John Podesta. Archived website of the Clinton administration. https://clintonwhitehouse5.archives.gov/WH/kids/inside/html/fall99/html/podesta.html
Kahn, R. L., Wolfe, D. M., Quinn, R. P., & Snoek, J. D., in collaboration with Rosenthal, R. A. (1964). Organizational Stress: Studies in Role Conflict and Ambiguity. New York: Wiley.
Rizzo, J. R., House, R. J., & Lirtzman, S. I. (1970). Role conflict and ambiguity in complex organizations. Administrative Science Quarterly, 15(2), 150–163. doi:10.2307/2391486
Tubre, T. C., & Collins, J. M. (2000). Jackson and Schuler (1985) revisited: A meta-analysis of the relationships between role ambiguity, role conflict, and job performance. Journal of Management, 26(1), 155–169. doi:10.1177/014920630002600104
Pierce, J. L., Kostova, T., & Dirks, K. T. (2001). Toward a theory of psychological ownership in organizations. Academy of Management Review, 26(2), 298–310. doi:10.2307/259124