Roadmaps & Readiness · Anil Kabir Kumar ·
Beyond Tactics
When founders discuss growth, the conversation typically focuses on tactics: marketing channels, product features, market expansion. These discussions are important, but they often miss a more fundamental question: Is your operating model designed to support growth?
The operating model—how your organisation is structured, how work flows, how decisions are made—is the hidden layer that determines whether growth creates value or chaos.
At Cralgo, we work with founders on roadmap ownership and execution governance. In this work, we've observed that operating model issues often underlie what appear to be strategy or execution problems.
What Is an Operating Model?
An operating model describes how an organisation delivers value. It encompasses:
Structure: How teams are organised, what roles exist, how authority is distributed Process: How work flows through the organisation, what handoffs occur, what decision gates exist Technology: What systems support operations, how they integrate, what data flows between them People: What capabilities exist, how they're developed, how performance is measured Governance: How decisions are made, how accountability is maintained, how progress is monitored
These elements interact as a system. Changing one affects the others.
Why Operating Models Matter for Growth
Growth stresses operating models in predictable ways:
Coordination Complexity
As organisations grow, coordination becomes exponentially more difficult. What worked when everyone sat in the same room fails when teams span functions, locations, and time zones.
Decision Bottlenecks
Founders who made every significant decision early on become bottlenecks as decision volume increases. Without deliberate distribution of decision authority, organisations stall.
Process Fragmentation
Informal processes that worked at small scale fragment under growth pressure. Different teams develop different approaches, creating inconsistency and friction.
Capability Gaps
Skills that enabled early success may not match growth requirements. Technical founders may need commercial leadership. Generalists may need specialists.
Technology Limitations
Systems chosen for small-scale operations often don't scale. Integration challenges multiply as the technology ecosystem expands.
Designing for Scale
Operating model design for growth requires intentional attention to several dimensions:
Structural Decisions
Functional vs. business unit organisation: Functional structures (marketing, operations, finance) create specialisation but complicate cross-functional coordination. Business unit structures create accountability but may duplicate capabilities.
Centralisation vs. distribution: Central functions create consistency and efficiency. Distributed functions create responsiveness and accountability. The right balance depends on your business and growth trajectory.
Role clarity: As organisations grow, role boundaries must become clearer. Ambiguity that creates flexibility at small scale creates confusion at larger scale.
Process Design
Core processes: Identify the handful of processes most critical to value delivery. Design these deliberately rather than allowing them to evolve haphazardly.
Decision processes: Clarify how decisions are made, who has authority, and what escalation paths exist. Decision clarity is particularly important for governance.
Handoff management: Where work passes between teams or functions, design clear handoffs with defined responsibilities and quality standards.
Technology Architecture
Scalability assessment: Evaluate whether current systems can support growth trajectories. Identify scalability limits before they become constraints.
Integration strategy: As the technology landscape expands, integration becomes critical. Develop clear integration strategies rather than point-to-point connections.
Data architecture: Ensure data can flow where it's needed for decisions. Data silos that work at small scale become serious obstacles at larger scale.
Capability Development
Identify growth-critical capabilities: What capabilities will you need that you don't currently have? Begin developing these before they become urgent.
Build vs. hire: Some capabilities can be developed internally; others require bringing in new people. Make these decisions strategically.
Leadership development: Growth requires leadership at multiple levels. Invest in developing leadership capabilities beyond the founding team.
Common Operating Model Failures
Several patterns commonly derail growth:
Founder over-involvement: Founders who don't evolve their roles create decision bottlenecks that constrain growth.
Premature complexity: Adding structure and process before they're needed creates overhead without benefit. Timing matters.
Copy-paste models: Adopting operating models from larger organisations without adaptation to your context rarely works.
Neglected culture: Operating model changes affect culture. Failing to attend to cultural implications creates resistance and dysfunction.
Siloed design: Designing operating model elements in isolation, rather than as an integrated system, creates misalignment.
The Evolution Path
Operating models must evolve as organisations grow. The model appropriate at £1M revenue differs from what's needed at £10M, which differs from £100M.
This evolution isn't a single redesign—it's continuous adaptation. Build the capability to assess, design, and implement operating model changes as an ongoing function.
Signals That Change Is Needed
Watch for signals that current operating models are constraining growth:
- Decision backlogs increasing - Coordination problems becoming chronic - Quality inconsistencies emerging - Key people becoming overwhelmed - Customer experience deteriorating
When these signals appear, operating model assessment should follow.
The Cralgo Approach
At Cralgo, operating model considerations are woven into our technology leadership engagements. We help founders assess current operating models, design for growth, and implement changes with appropriate governance.
This work connects to broader roadmap ownership—operating model evolution should align with strategic direction, not proceed in isolation.
If your organisation is experiencing growth friction that might trace to operating model limitations, consider starting a conversation.
Frequently asked questions
What is an operating model?
An operating model describes how an organisation delivers value. It encompasses structure (how teams are organised), process (how work flows), technology (what systems support operations), people (what capabilities exist), and governance (how decisions are made).
Why do operating models matter for growth?
Growth stresses operating models by increasing coordination complexity, decision volume, and capability requirements. Operating models designed for small scale often fail under growth pressure, creating bottlenecks and dysfunction.
When should I redesign my operating model?
Watch for signals: decision backlogs, coordination problems, quality inconsistencies, overwhelmed key people, or customer experience deterioration. These often indicate operating model constraints that warrant assessment.
What are common operating model mistakes during growth?
Common failures include founder over-involvement creating bottlenecks, premature complexity adding overhead without benefit, copying models from larger organisations without adaptation, and designing elements in isolation rather than as an integrated system.
How does Cralgo approach operating model work?
Operating model considerations are woven into Cralgo's work on technology leadership and transformation. We help founders assess current models, design for growth, and implement changes with appropriate governance—connected to broader roadmap ownership.