Latest / Scaling Up with Fexingo: How Small Businesses Become Mid-Market Companies / How Mid-Market Firms Build Decision Rights
Transcript
- Lucas: We talk a lot about mid-market firms hitting a wall at fifty million in revenue, but I want to zoom in on the specific mechanical failure that causes it. It is rarely a lack of capital or a bad product. Usually, it is a collapse in decision velocity. The company grows faster than its ability to authorize actions. Luna: Right. You have more people, but every single email now requires three levels of sign-off. What used to take an hour takes three days. Lucas: Exactly. And the founder tries to solve this by working harder, approving everything personally until they burn out. We see this pattern repeatedly in our research. The organization becomes paralyzed by ambiguity. Everyone knows what they are supposed to do, but no one knows who is allowed to make the final call when things get complicated. Luna: So the problem is actually clarity, not capability? The talent is there, but the permission structure is broken. Lucas: Precisely. Today we are looking at a specific tool called a decision-rights matrix. It is a simple grid that assigns ownership for every major category of business activity. We looked at a mid-market industrial manufacturer that implemented this last year and cut their average approval cycle from four days to eighteen hours. Luna: That is massive. How did they even start mapping that out without creating endless bureaucracy? Lucas: They started by listing the top twenty-five recurring decisions. Things like hiring a regional manager, changing a vendor contract over five hundred thousand dollars, or launching a new product line. Then they categorized each decision into one of four types. Approve, Recommend, Input, or Notify. That is it. Just four letters. Luna: I like that simplicity. But how do you prevent the Recommend step from becoming a bottleneck where everyone is just passing the buck? Lucas: Good question. The key is defining the difference between advice and authority. In the matrix, the person with the 'Approve' role has final say. They can ignore the recommendations if they want. The 'Recommend' role means you must gather data and propose a path, but you do not own the outcome. If you blur those lines, you get paralysis. Luna: So the Approver owns the risk. That makes sense. Who usually ends up as the Approver in these mid-market firms? Lucas: Ideally, it is the person closest to the customer or the operational reality. For example, in that manufacturing case, the VP of Sales got full Approve rights on marketing spend under two hundred thousand dollars. The CEO only needed to be Notified. Before the matrix, the CEO had to sign off on every small campaign. Now he never sees them unless they fail. Luna: That shifts the dynamic completely. The sales leader feels trusted, and the CEO gets bandwidth back. It feels like a culture play disguised as a spreadsheet. Lucas: It is definitely a culture play. Because you cannot force people to use the matrix if they don't trust the system. We saw another company try to implement this purely as a compliance exercise. They made the matrix public, but then the executives kept bypassing it via hallway conversations. The document existed, but the actual decision-making stayed hidden. Luna: Ugh, that sounds familiar. The shadow org chart always wins if the official one isn't respected. How do you enforce it without micromanaging? Lucas: You tie it to performance reviews. One of the firms we studied made it clear that ignoring the matrix was a leadership failure. If a director tried to approve something they weren't supposed to, it was flagged in the quarterly review. Not as a punishment, but as a process error. It signaled that following the protocol was part of the job. Luna: So accountability flows both ways. You hold people accountable for respecting the boundaries, not just for hitting targets. Lucas: Correct. And this creates psychological safety. When people know exactly where their lane ends, they stop worrying about stepping on toes. They can make bold moves within their domain because they know the rules. The anxiety of ambiguity disappears. Luna: That must be freeing for middle managers. They are often stuck in the middle, trying to please everyone. Clear boundaries would let them actually lead. Lucas: Absolutely. Middle management is the first casualty of scaling. They become message passers instead of decision makers. By giving them explicit Approve rights, you turn them into owners again. That is how you retain good talent. People leave when they feel powerless. Luna: But what about the edge cases? The weird, one-off situations that don't fit neatly into the matrix. Do they create a separate exception process? Lucas: No. That is a trap. If you create an exception process, you invite exceptions everywhere. The rule is simple. If a decision falls outside the matrix, it defaults to the CEO or the executive team. It is rare, but it forces leaders to address the gap in the system rather than hiding behind ad-hoc approvals. Luna: So the default escalation is visible. It highlights where the matrix needs updating. It turns friction into data. Lucas: Yes. Every time a decision goes to the top, it is a signal that the matrix is too rigid or unclear. You review those incidents monthly and adjust the grid. It becomes a living document, not a static policy. That keeps the organization agile. Luna: I imagine some founders struggle with letting go of that control. Even with a matrix in place, they might still want to jump in. Lucas: They do. And that is why the board or the external advisors often help drive this. An outsider can point out when the founder is violating their own rules. We had a case where the founder kept overriding his VP of Operations. The VP just stopped bringing problems to him. He started solving things quietly, which created bigger risks later. The matrix gave the VP cover to say, 'This is my call.' Luna: That is powerful. It gives junior leaders the armor they need to push back against senior bias. It changes the power dynamic without a confrontation. Lucas: Exactly. It institutionalizes trust. Instead of relying on personal relationships, you rely on the system. If the CEO leaves tomorrow, the new leader can look at the matrix and understand how decisions flow. It reduces key-person dependency. Luna: Which is huge for valuation. Investors love predictability. A clean decision framework looks much better than a chaotic founder-led shop. Lucas: It does. And it scales. You can add layers to the matrix as the company grows. You don't throw it away. You just refine the categories. The core logic remains stable while the details evolve. Luna: So the lesson is not just about efficiency, but about building a resilient organization that can survive leadership transitions. Lucas: Right. Clarity is the foundation of scale. Without it, you are just adding headcount to a broken engine. With it, you build a machine that runs itself. Luna: If you enjoy these deep dives into how businesses actually work, consider supporting the show directly. A small group of listeners already chips in monthly through buy me a coffee dot com slash fexingo. That support literally funds the research and editing that keeps this ad-free. Lucas: It helps us keep the lights on and brings in fresh perspectives. If that resonates with you, check out the link. Otherwise, back to the topic. Luna: One last thing on the matrix. How do you communicate this to the wider team so it doesn't feel like top-down control? Lucas: You frame it as empowerment. The launch meeting should focus on what people CAN do, not what they can't. Show them the new freedoms they are gaining. When people feel trusted, they adopt the system quickly. Luna: Empowerment through structure. That is a compelling way to sell internal change. Lucas: It works. Because freedom without boundaries is just chaos. Boundaries without freedom is prison. The matrix sits right in the middle. Luna: A balanced approach to scaling. I wonder if other industries face similar bottlenecks with different names. Lucas: Probably. But the mechanics of authority are universal. Whether you are in tech or manufacturing, someone always needs to sign off. The question is whether that signature adds value or just delays progress. Luna: And if it doesn't add value, maybe it shouldn't exist at all. Removing friction seems to be the real goal here. Lucas: Exactly. So next time you feel stuck in a meeting waiting for approval, ask yourself who actually owns that decision. The answer might surprise you. Luna: Or it might reveal that the owner is missing entirely. Either way, it is worth investigating before the next quarter closes.