Chief of Staff Expert Operator – Kenya Reynolds

An executive assistant manages the CEO's calendar, logistics, and communications – high-leverage support that frees CEO time from administrative work. A Chief of Staff manages the operating model of the company – how decisions get made, how cross-functional work gets coordinated, and how strategic initiatives get tracked and executed. Day-to-day, a CoS runs the operating cadence (weekly leadership team meeting, initiative reviews, cross-functional syncs), owns the decision rights framework, manages the strategic initiative portfolio, and flags the issues that require CEO attention before they become crises. Kenya does not manage the CEO's calendar. She manages the system that lets the CEO use their calendar effectively.

A fractional CoS is most effective for the infrastructure build phase – designing and implementing the operating system, decision frameworks, and coordination protocols. This typically takes three to six months and is best done by someone with experience building these systems across multiple companies rather than a first-time CoS who is figuring it out in real time. A full-time CoS is most effective once the operating system is in place and requires a dedicated owner to run it continuously. Kenya often works with the founding team to identify whether a full-time CoS is the right next hire or whether a well-designed operating system can run with existing team capacity. The answer depends on the company's coordination complexity and strategic initiative load.

A Chief of Staff is the right hire when the primary constraint on company execution speed is cross-functional coordination and CEO bandwidth – not functional capacity in any specific domain. If sales is underperforming, the right hire is a VP Sales. If engineering velocity is declining, the right hire is a VP Engineering. If the CEO is a bottleneck in decisions that do not belong to any single function, and if cross-functional initiatives are stalling because nobody owns the coordination layer, a CoS is the right hire. The signal is whether the CEO's bottleneck is in thinking (strategy, judgment) or in logistics (meetings, coordination, initiative tracking). A CoS removes the logistics bottleneck, freeing the CEO for the thinking work.

A 90-day CoS engagement with Kenya produces: a documented operating cadence (meeting structure, frequency, and agenda format for all recurring leadership meetings), a decision rights framework (which decisions are made at what level, with what input and what documentation), a strategic initiative tracking system (a single source of truth for all company-level initiatives with owner, milestone, and status), a cross-functional communication protocol (how information moves between teams without requiring CEO involvement), and a CEO time audit with recommendations for meeting load reduction. These are not templates or frameworks – they are implemented systems that have been running for 60–90 days and have been adapted to the company's actual operating patterns before handoff.

Three diagnostic signals are most reliable. First, project stall pattern: if projects consistently stall waiting for CEO input rather than because of functional execution gaps, the CEO is the bottleneck. Second, meeting load: if the CEO is in more than 20 meetings per week at a company of 20–50 people, a significant portion of those meetings are happening because the operating system requires their presence rather than because their presence adds unique value. Third, escalation pattern: if team leads are regularly bringing decisions to the CEO that should be resolved at the team lead level, the decision rights framework is missing. All three can be diagnosed in a two-week operating audit without committing to a full engagement.