Hire Chief of Staff — leverage for the chief executive

No — different jobs entirely. An EA manages the CEO's time; a chief of staff multiplies the CEO's impact: preparing decisions, driving cross-functional initiatives, and exercising judgment on the CEO's behalf. The EA protects hours; the chief of staff creates leverage.

Judgment, drive, and communication ability matter more than any specific CV: often ex-consulting, ex-operations, or rising internal talent. Domain expertise helps but the core skill is turning the CEO's intent into organisational action — that is rarer than any credential.

Borrowed authority, explicitly granted: the organisation must understand that the chief of staff speaks with the CEO's mandate on defined matters. Without that clarity the role collapses into scheduling; with it, things move.

When the CEO's calendar is full but the important work is not getting done — decisions delayed, initiatives drifting, follow-through failing. If you recognise that description, the time is now; waiting only compounds the cost.

Frequently — it is one of the role's best features. Eighteen to twenty-four months of working across the whole business, with the CEO's trust, prepares someone exceptionally well for operational leadership. Many companies plan this path deliberately.

I work on a fixed monthly retainer scoped to the days per week you need. A diagnostic-and-design engagement is short and project-priced, while fractional or interim cover is an ongoing retainer. I avoid hourly billing because a chief of staff's value is in outcomes, not logged hours. We agree the mandate and the scorecard up front, so you pay against defined leverage rather than an open-ended seat. I give you a firm number after the first scoping call.

The diagnostic takes about two weeks: shadowing your calendar, inbox and a few live initiatives. The operating cadence is live within the first month, a decision log, a weekly business review and tracked commitments. Measurable change in decision latency and meeting load usually shows by the end of the first quarter. I resist promising instant transformation; the first fortnight is mostly listening, because installing the wrong system fast is worse than installing the right one deliberately.

If you need the function to exist now, or you are not yet sure what the role should own, start fractional. You get a working operating system and a proven mandate before committing to a permanent salary. A full-time hire makes sense once the leverage gap is clearly defined and large enough to fill a calendar. Many of my clients hire a fractional chief of staff first precisely so the eventual permanent hire inherits something that already works.

Both, depending on what you need. Most often I design the role, the scorecard and the interview loop, then either run the search end-to-end or partner with your recruiter and sit on the panel. The design work matters more than the sourcing. When people hire a chief of staff and it fails, it is almost always because the role was never properly defined, not because the shortlist was thin.

Yes. I am based in Dubai and work with founders across the UAE, US, UK, Canada, Pakistan and Malaysia, and the Gulf timezone is genuinely useful: I can clear a European morning and still overlap with North American afternoons. The role runs remotely through the shared decision log and weekly review, with occasional on-site weeks when a transformation or offsite warrants it. Timezone has never been the constraint; a clear mandate is.

Against the scorecard we agreed before the search, not against how busy they look. I track decision latency, the share of committed actions completed on time, your recurring meeting hours, and whether initiatives with no natural department owner are actually moving. If those numbers are not shifting within a quarter, the mandate is usually the problem, and we fix the setup rather than blame the person.