.png?width=500&height=113&name=FORWARD%20Brand%20Board%20(72).png)
Okthalia Adam advises founders and CEOs on the operating system that lets them lead without becoming the bottleneck – building the executive alignment, initiative infrastructure, and decision frameworks that scale as a team grows from 20 to 200 employees. She also coaches internal Chief of Staff hires on the scope, tools, and stakeholder management required to operate effectively in the role.
The founder bottleneck that no one names correctly
At 30–50 employees, most founder-CEOs become the critical path on decisions that should not require them. They know this is happening – they feel it in the accumulating Slack messages, the one-on-ones that run over, the strategic work that gets deferred to the weekend. What they rarely have is a clear diagnosis of the operating system failure producing it: a team that has grown past the informal communication architecture that worked at 15 people, with no replacement architecture built. The result is a CEO who is increasingly reactive and increasingly essential to routine operations, which is exactly the opposite of what the company needs as it prepares for the next stage.
What a well-designed operating system changes
A well-designed operating system for a 30–100 person company includes four elements: a weekly leadership team meeting with a format that surfaces decisions rather than updates; an initiative tracking system that tells every leader which projects they own, what done looks like, and when decisions need to be made; a decision framework that defines which decisions require CEO involvement and which can be made independently; and a quarterly goal-setting process that aligns the team before the quarter begins rather than after the first month has passed. These four elements, implemented together, typically return 12–20 hours per week of CEO time that was previously being consumed by coordination overhead that the operating system should be handling automatically.
When to hire a Chief of Staff vs. fix the operating system
Hiring a Chief of Staff into a broken operating system is the most common and most expensive mistake founders make with this role. The CoS becomes the CEO's personal coordination system rather than the company's operating infrastructure, which means they are solving the CEO's time problem but not the company's coordination problem. The right sequence is to design the operating system first – using advisory to identify the structural gaps – and then make the CoS hire into a defined role with clear scope. A CoS hired into a documented operating system is effective within 30 days. A CoS hired to figure out how the company should work takes 3–6 months to be effective and often leaves before reaching that point.
A STAR case from the Forward Share Ventures network
Situation: Series A founder-CEO at 35-person company running 14 direct 1:1s, no operating cadence, no initiative tracking, missing board prep deadlines, and team waiting on CEO approval for routine decisions. Company growing 80% YoY but CEO in reactive mode 90% of the time.
Result: 12-week engagement built operating cadence (weekly leadership team meeting, monthly all-hands rhythm, quarterly goal-setting process), initiative tracking system with clear owners and weekly status updates, and decision framework that reduced CEO approval bottlenecks by 60%. CEO reclaimed an estimated 12+ hours per week of strategic time.
Forward Share Ventures expert operators are selected from a verified STAR Portfolio™ of documented outcomes.
"The CEO who can't get off the critical path of their own company isn't bad at delegation – they've never been shown what a well-designed operating system looks like from the inside. The operating system is not a management philosophy. It is a specific set of meetings, processes, and decision rights that you design deliberately and then run consistently."
– Okthalia Adam, Chief of Staff Expert Operator, Forward Share Ventures
Frequently asked questions
What does a Chief of Staff advisory engagement look like?
A CoS advisory engagement typically runs 8–12 weeks and produces two things: an operating system design for the company at its current stage, and a scope definition for the CoS role if a hire is planned. The first four weeks are diagnostic: observing how the leadership team actually operates, identifying the specific coordination failures that are consuming CEO time, and mapping the decisions that should be delegated but aren't. The middle four weeks are design and implementation: building the operating cadence, initiative tracking system, and decision framework. The final weeks are stabilization: running the new operating system through two or three leadership cycles, calibrating based on what's working, and if applicable, preparing the CoS hiring brief and onboarding plan.
When should a CEO get CoS advisory vs. just hire a Chief of Staff?
Hire a CoS directly when the operating system is already working – the CEO has a functional leadership team operating cadence, clear initiative ownership, and a defined set of problems the CoS would own from day one. Use advisory first when the operating system is broken – when the CEO is the bottleneck, when meetings are chaotic, when no one is clear on what they own, or when initiative tracking doesn't exist. The advisory gets the operating system working before the CoS hire, so the CoS enters a defined role rather than a blank canvas. This makes the CoS hire 3–4x more likely to be effective within their first 60 days.
What does the first 30 days of a CoS advisory engagement focus on?
The first 30 days are diagnostic and design. Week one: observe the existing operating cadence – sit in on all recurring leadership meetings, read the last three board updates, review current initiative tracking if it exists. Week two: 1:1 diagnostic conversations with each member of the leadership team to understand where they feel blocked, where they feel unclear on priorities, and what they wish the CEO was more or less involved in. Week three: synthesis and initial operating system design – draft the weekly leadership team meeting format, initiative tracking structure, and decision matrix. Week four: pressure-test the design with the CEO and leadership team and begin running the first elements of the new operating cadence.
How do you know if your Chief of Staff is set up to succeed?
Three tests: First, the CoS has a written scope document that defines what they own, what they support, and what they are explicitly not responsible for – without this, the role expands to fill whatever vacuum exists and the CoS burns out within a year. Second, the CEO has delegated at least three specific initiatives to the CoS with clear success criteria – not "be my right hand" but "own Q3 board prep" or "own the quarterly business review process." Third, there is a standing weekly 1:1 between the CEO and CoS with a structured agenda that covers both strategic and operational items. CoS roles that fail typically lack all three of these structural elements.
What are the most common operating system failures at Series A?
Five operating system failures are nearly universal at Series A. First, the all-hands meeting that is actually a status update: 45 minutes of leaders reporting to the CEO with no cross-functional discussion or decision-making. Second, no initiative tracking: everyone has OKRs but no one knows who owns the 12 cross-functional projects that don't fit into a single team's OKR. Third, the CEO as the tie-breaker for decisions that should be made by functional leaders – which means every disagreement between two leaders requires a CEO intervention. Fourth, no quarterly alignment process – the leadership team learns what Q2 priorities are in the first week of April. Fifth, 1:1s that are therapy sessions rather than management: leaders bring problems to the CEO for processing rather than decisions for input.
Get an operator read on your situation
Twenty minutes with an expert operator who has been here before. No prep needed – bring the situation as it is. You will leave with a clear read on the gap and a concrete next step.
Get an operator read →No prep needed. 20 minutes. You'll leave with a clear read on the gap.
Find Your Expert in 48 Hours.
Founder-Vetted. Matched in 48 Hours. STAR-Verified.