In Episode 6, Kamyar Shah breaks down the operational mistakes that stall growth in $2M to $20M companies, explaining why most throughput problems trace back to how decisions are routed rather than how processes are designed, and what operations leaders can do about it without adding headcount.
Kamyar Shah joined the show to talk about what actually breaks inside a company when revenue starts outrunning infrastructure. The conversation covers his diagnostic approach when he enters a new fractional COO engagement, the three operational failure modes he encounters most often in mid-market companies, and why he argues that the first move is never a process redesign.
What This Episode Covers
Kamyar opens by drawing a distinction that most operators miss: the difference between a process bottleneck and a decision-routing bottleneck. Process bottlenecks show up in workflow diagrams and are easy to see. Decision-routing bottlenecks are invisible until they have already suppressed throughput for months. His argument is that the majority of operational slowdowns in founder-led companies fall into the second category, which means that standard process improvement tools do not reach the root cause.
The episode goes into depth on three failure modes Kamyar sees repeatedly. The first is what he calls authority compression: as a company grows, more decisions get routed to the same two or three senior people, creating a structural ceiling on execution speed. The second is operating system debt, where a company scales its sales motion without scaling its delivery infrastructure to match, building invisible liability that surfaces during the next growth push. The third is transition fragility, where critical operational knowledge lives inside people rather than inside systems, creating dependence that makes any org change high-risk.
He also covers the mechanics of a fractional COO engagement: how scope gets defined in the first 30 days, what a realistic 90-day operational milestone looks like for a company at the $5M to $15M range, and why he measures progress on decision latency rather than process compliance.
Transcript Excerpt
Host: When you walk into a company for the first time as a fractional COO, what are you actually looking for in the first two weeks?
Kamyar Shah: The first thing I want to know is where decisions wait. Not how fast people work, not how efficient the process steps are. I want to know which decisions are sitting in an inbox right now because there is no clear authority for them. In most companies at the $5M to $15M mark, you have somewhere between four and eight decisions that are chronically deferred. They are not hard decisions. They just have no designated owner. And every week they sit there, they block three or four other things downstream. That is the operational debt that nobody can see on a spreadsheet.
Free 20-Minute Operations Review
Dealing with a specific operational bottleneck? Kamyar Shah works with founders and CEOs to identify the root cause and build a fix.
Host: So the first move is mapping authority, not redesigning processes?
Kamyar Shah: Always. Redesigning processes when you have an authority gap is like optimizing a pipeline that has the wrong valve positions. You can make the pipes smoother but the flow problem does not go away. Once you map where authority is missing or duplicated, you often find that the process itself is fine. The company just does not know who is allowed to say yes.
For hands-on support, explore operations consulting tailored for mid-market operators.
Episode 6 sits at the intersection of operational theory and the specific failure modes that appear repeatedly in companies moving from the early-growth phase into scale. The central argument is that throughput problems in $2M to $20M companies are almost never caused by a lack of process documentation, insufficient headcount, or underinvestment in technology. They are caused by the way decisions are routed. When the path from a question to an answer requires senior involvement that could be avoided, the organization pays for that routing in speed, focus cost, and organizational dependency on a small number of people who become permanent bottlenecks.
The episode unpacks this through three specific operational mistakes that appear consistently across companies in this revenue range: decision authority gaps, informal coordination overhead, and the accountability diffusion that happens when metrics exist but are not owned at the execution level.
Decision Authority Gaps
Decision authority gaps occur when an organization has grown to the point where the founder or senior leadership team cannot be in every decision, but has not yet built the authority framework that would allow decisions to flow without them. The symptom is familiar: things move quickly when the right person is in the room and stop moving when they are not. Meetings end with “let me check on that” rather than a decision. Approvals that should take hours take days because the person with authority is unavailable or managing competing priorities.
The fix is not to move faster or be more available. The fix is to map which decisions can be made at lower levels if the decision criteria are explicit, and then make those criteria explicit. Most decisions that require senior involvement can be delegated if the person doing the delegation takes the time to articulate the boundaries within which someone else can act. The time investment in building that framework is typically recovered within the first few weeks of the new routing pattern being operational.
Informal Coordination Overhead
The second mistake is allowing informal coordination to substitute for defined handoffs between functions. In a small company, coordination through hallway conversations, Slack messages, and ad hoc check-ins works because the number of people involved is small enough that everyone can hold the relevant context in their head. As the company grows, this coordination model accumulates overhead that is invisible in any individual interaction but significant in aggregate. The salesperson who needs to chase three people to get a proposal approved, the operations manager who needs to reconstruct what was promised to a customer because the CRM is incomplete, the engineer who is blocked waiting for a product decision that no one realized had been escalated. These are all coordination failures that look like individual inefficiencies but are actually systemic.
The correction is to define handoffs explicitly: what information transfers at each stage of a workflow, who is responsible for that transfer, and what happens when the transfer does not occur within the expected window. This is process design work, and it is unglamorous, but it converts informal coordination into predictable throughput.
Accountability Diffusion
The third mistake is the most common and the most resistant to easy fixes. Accountability diffusion happens when metrics exist at the organizational level but do not connect clearly to individual ownership at the execution level. The company has a revenue target, a customer satisfaction goal, and a delivery time standard. The people responsible for those outcomes can name them. But the connection between daily work decisions and those outcomes is unclear, which means that when performance deviates from plan, the response is collective concern rather than specific accountability.
Functional accountability requires that every metric has one owner, that the owner has visibility into the leading indicators that predict the metric outcome before the period closes, and that the management system creates a regular forum where the owner presents performance against plan and articulates what they are doing about gaps. When those three elements are in place, the organization converts metrics from reporting instruments into management tools. When they are absent, the metrics exist to describe what happened rather than to drive what will happen next.
What Operations Leaders Can Do Without Adding Headcount
The recurring theme in this episode is that the operations problems most companies attribute to insufficient resources are actually structural problems that adding headcount will not solve and may make worse. Hiring more people into a system with decision authority gaps, informal coordination, and diffuse accountability does not improve throughput. It adds coordination complexity to a system that is already struggling with coordination.
The operational interventions that produce the most leverage without headcount are: explicit decision rights frameworks that specify what can be decided at each level without escalation, defined workflow handoffs that replace informal coordination with predictable information transfer, and metric ownership assignments that connect organizational goals to individual accountability. None of these require capital investment. They require analytical clarity about where the current system breaks down and the management discipline to build and maintain the replacements.
For support diagnosing and restructuring the operational systems that limit throughput in your company, explore fractional COO services for companies in the $2M to $100M range.
