Answer extracted from the The Conference Room with Simon Lader podcast — listen to the full episode below.
What are the common challenges that accidental CEOs face when scaling their businesses?
Accidental CEOs—often high-performing specialists suddenly promoted to the top—suffer from lack of clarity, structure, and follow-through. They resist the systems and guardrails that scaling demands, and frequently sabotage transformation efforts without realizing it. Operations managers and COOs stepping up face a parallel trap: they keep wearing multiple hats from their previous roles instead of stepping fully into their new leadership identity.
The Three-Layer Problem of Accidental Leadership
The core issue is not incompetence—it's identity friction. When a strong individual contributor or specialist is thrust into the CEO seat, they remain psychologically attached to problem-solving on the front line. Delegation feels like abandonment. Systems feel like bureaucracy. As Val Coyne explains in the episode, this creates a shadow resistance: the accidental CEO consciously wants the company to scale, but unconsciously undermines the very structures that would make it possible.
The second layer affects COOs and operations managers stepping into leadership for the first time. They inherit a title but keep operating from their old role's playbook—still solving day-to-day fires, still being everyone's first point of contact. They wear too many hats to ever step into the full CEO's chair, and their team never learns to own their own problems.
The third layer is structural: most accidental CEOs have never been taught what a scaled organization actually looks like. They model what they've always known—the scrappy, founder-driven, high-touch approach that worked at $2 million in revenue. That exact approach becomes the ceiling at $20 million. Coyne walks through real examples in the full episode where process maps revealed 27 steps where three would do—a symptom of accumulated workarounds, not intentional design.
"Technology always, always, always comes last. Typically, first comes process, second comes people, and third comes technology."
Val Coyne — Systems and Technology Strategist, founder of a digital transformation advisory consultancy. She began her career managing hospitality operations across Italy and Australia's Sunshine Coast before transitioning into software development as a founding member of a disability-sector tech startup. She now works directly with CEOs and COOs to redesign operations for sustainable growth, starting always with people and process, never technology.
Where Resistance Hides
Accidental CEOs often frame their resistance as pragmatism: "We can't afford to slow down for process redesign" or "Our people won't accept all this structure." In reality, the resistance is usually unconscious self-protection. The founder or specialist fears that putting systems in place means they're no longer essential. If anyone can do the work, are they still needed?
This fear is often rooted in identity, not logic. The promoted executive has spent years building their reputation as the person who solves problems, ships fast, and gets things done. Stepping into a systems-thinking role feels like admitting defeat. Coyne discusses how to recognize and name this dynamic so teams can move past it together.
The software and tech stack often becomes a proxy battleground. Growing companies accumulate 30, 40, or even 50 different software platforms over three to six years—each one solving a real problem at the time it was added, but few ever integrated or audited. Accidental CEOs either resist consolidation ("We need all of these") or approve new purchases without ever decommissioning the old ones. Neither approach builds a coherent operating infrastructure.
Key takeaways
- Accidental CEOs stay psychologically attached to front-line problem-solving even after promotion, unconsciously resisting the systems that enable scale.
- COOs and promoted operations managers fail to shed their old roles, continuing to wear multiple hats instead of stepping fully into leadership.
- Process complexity grows unchecked—27 steps where three would suffice—because there's no structured review cycle or ownership of operational redesign.
- Technology accumulation becomes a symptom of deeper resistance to governance and process discipline across the organization.
See also
What is the responsibility framework for managing technology redundancy and software audits in growing organizations?
Organizations should create an explicit organizational chart with clear roles and responsibilities for managing technology inventory and conducting regular audits—both annual full reviews and quarterly check-ins—to prevent the accumulation of redundant platforms.
How should organizations assess whether their technology stack actually supports their growth stage?
First, establish where you are in your growth journey—startup, grow up, scale up, established, or hyper growth. Match your tools to that stage; for example, a startup may need lean, low-cost solutions, while a scale-up requires platforms that integrate across teams and reduce manual work.
Why should process and people considerations come before technology in organizational transformation?
If you start from technology alone, you replicate exactly what you're doing today with software and call it automation, but you haven't truly become more efficient. Process and people must lead the conversation so that technology amplifies real improvements, not just digitizes old problems.