Connecting strategy, decisions, and execution during periods of growth and change.
The conditions vary by company and stage. The role is to manage the complexity the CEO deals with every day: organizing the work, keeping it visible, and making sure it moves.
Meeting structure, planning rhythm, and follow-through that help the leadership team stay aligned.
Board meetings, investor updates, leadership reviews, and internal decisions. The work is preparing the context, tradeoffs, materials, and follow-up so the decision process is clear.
Priorities made visible, ownership made clear, dependencies surfaced, and decisions carried into execution without adding unnecessary process.
Work that spans teams or sits outside a single function: partnerships, market work, operating model changes, special projects, and sensitive initiatives that need clear handling.
I've found myself working wherever the company needed someone to connect people, priorities, and execution. The titles changed because each company needed something different. The underlying work changed very little.
That work has taken me across product, engineering, partnerships, customer-facing teams, operations, and strategy. Sometimes it meant building an operating rhythm from the ground up. Sometimes it meant helping clarify market direction or connecting technical depth with executive decisions. Different companies asked for different things, but I kept finding myself doing the same kind of work.
I've found that the work rarely begins by solving a problem. It begins by understanding it. Every organization develops its own operating rhythm, ways of making decisions, and places where momentum slows. Paying attention to those patterns has become one of the most valuable parts of my work because it changes what needs to happen next.
Systems thinking. Execution bias. Cross-discipline range.
This works best when the CEO is looking for a senior operator, full-time or fractional, who can work alongside them with autonomy, absorb context quickly, move across functions, and carry important priorities without adding complexity.
If the work described here is relevant to what you're building, there are two ways to begin.