Someone on your leadership team has read a book.  This is not inherently bad news. 

The book is highlighted. There are sticky notes involved. Someone has used the phrase “right people, right seats” three times this week, and your next leadership meeting now includes an agenda item called “generic framework discussion.” 

I’m sure you’re intrigued, but you are also tired. 

Your business has outgrown informal conversations, decisions made in hallways, and a planning process that mostly consists of you remembering what everyone promised last month. 

A business operating system sounds like exactly what you need. One structure. One language. One rhythm. Maybe even one meeting that does not end with someone saying, “I thought we decided that already.” 

A framework is often the first system a small business owner encounters when they start looking for operational structure. It is visible, understandable, and supported by books, tools, implementers, and a large community. For many companies, it is useful. For some, it is an excellent fit. For others, it becomes another framework the company performs rather than an operating system the team actually uses. 

The real question is not whether frameworks work. 

The question is whether your business needs a generic framework – or a custom operating system designed around the way your company creates value. 

Those are not the same thing. 

What Is a Business Operating System? 

A business operating system is the repeatable way your company turns direction into coordinated action. 

It connects: 

The important word is connects. 

Most businesses already have versions of all these things. They have goals, meetings, job descriptions, reports, and processes (even when those processes live entirely inside one employee’s head beside a collection of passwords no one else knows). 

The problem is that the parts do not work together. 

Strategy says one thing. The sales incentive rewards another. The meeting agenda focuses on something else. The owner overrides all three when an important customer calls. 

That is still an operating system, just not a particularly coherent one. 

What Generic Frameworks Give You 

Many of the generic frameworks offer a defined model for running the business. They usually include a structure with key components like: vision, data, process, people, etc.  

In practice, these frameworks typically bring a specific set of tools alongside them.   

There is real value in this. Most of the decent generic frameworks give teams language. And shared language is not trivial. 

A company that has spent years talking around problems may benefit enormously from a common way to name priorities, surface issues, assign ownership, and review progress. It gives leaders a rhythm and r educes the temptation to reinvent the meeting every Monday. 

It asks companies to document processes, confront people issues, choose priorities, and use data rather than vibes – which, in some leadership teams, is a genuinely radical development. 

A few of the frameworks outline clear boundaries. They are not designed to be everything. That clarity is part of its appeal. 

The Best Argument for Generic Frameworks 

Frameworks work particularly well when the business needs structure more than customization. 

Your company may have grown through relationships, instinct, and heroic effort. Sure, all of that got you here. It will not get you comfortably to the next stage. 

No one can name the top priorities. Every meeting becomes a status update. Problems are discussed repeatedly but rarely resolved. Roles have grown around people rather than being designed around the work. Processes vary depending on who is doing them. The owner remains the final stop for nearly every important decision. 

A defined framework can interrupt that chaos. 

You do not have to design every tool. You do not have to invent a planning cadence. You do not have to create a vocabulary from scratch. You start with a model that has already been tested by other companies. 

That can be a significant relief. Especially for an owner who has spent the last decade inventing everything else. 

Where a Generic Framework Can Become the Wrong Fit 

Here’s the kicker: The same standardization that makes generic frameworks approachable can also become the constraint. 

Your business may not need every prescribed tool. It may need a different decision model, planning horizon, meeting rhythm, way to organize work, or relationship between strategy and execution.  

A manufacturer, professional services firm, restaurant group, medical technology company, and creative agency may all need operational discipline. They do not necessarily need identical operating mechanics. 

When I was younger, I believed there had to be a right  way to organize a company. I was so cute back then. 

After working across startups, acquisitions, global organizations, product teams, leadership teams, and more frameworks than any reasonable person should discuss at dinner, I believe something less tidy: 

Every organizational model solves certain problems while creating new ones. 

The goal is not to find the perfect framework. The goal is to understand which tradeoffs fit your business. 

The Framework Fit Problem 

A framework becomes dangerous when leaders stop treating it as a tool and start treating it as truth. 

The conversation changes from: “What problem are we trying to solve?” to: “Are we doing [insert generic framework here] correctly?” 

Those are very different questions. 

I saw this repeatedly in Agile transformations. 

Teams would spend enormous amounts of energy debating roles, meetings, terminology, and framework compliance while the work still bounced between too many people. Decisions still took too long. Priorities still changed constantly. Customers still could not tell when their requests would be completed. 

The business had more process, but it had not necessarily built more capability. 

Adding structure to the wrong problem does not solve the problem. 

It makes the problem more organized. 

What a Custom Operating System Does Differently 

A custom business operating system starts with diagnosis rather than implementation. 

Instead of beginning with a predefined set of tools, it asks: 

• How does this company create value? 
• Where does work actually get stuck? 
• Which decisions require the owner? 
• Which decisions only appear to require the owner? 
• Where do handoffs fail? 
• What information do teams need? 
• What is the company trying to protect as it grows? 
• Which parts of the current culture are strengths? 
• Which habits worked at eight people but are breaking at forty? 
• What level of structure can the organization realistically sustain? 

Then the operating practices are built around those answers. 

Useful ideas do not become unusable simply because another framework includes them. 

But a custom system may also include: 

• Decision boundaries for managers 
• Team-level work visualization 
• Cross-functional planning 
• Customer journey handoffs 
• A role architecture that distinguishes leadership from subject-matter expertise 
• Different operating rhythms for different functions 
• Explicit escalation rules 
• Feedback loops tied to how work actually moves 
• A gradual capability-building plan rather than a single rollout 

The point is not to be unique for the sake of being unique. No one needs an artisanal, small-batch meeting cadence. 

The point is fit. 

Generic or Custom: Five Questions to Ask 

How much ambiguity can your team tolerate? 

Generic frameworks give you a clearer starting point. That can help a leadership team that is overwhelmed by too many options or has never operated with a consistent rhythm. 

A custom system requires more discovery and more participation. You have to examine how the company works rather than adopting a ready-made answer. 

For some organizations, that process is valuable. For others, it becomes another excuse to delay making obvious decisions. 

Be honest about which company you are. 

Is your problem a lack of structure, or a mismatch in the structure you have? 

Generic frameworks can be powerful when the business has no consistent planning, accountability, or issue-resolution practices. 

But some businesses already have plenty of structure… or too much of it. Duplicated reports, layers of approval, meetings that exist to prepare for other meetings, processes designed around old constraints. The list goes on.  

In that case, installing another complete system may increase the weight. You may need to remove, reconnect, or redesign – not pile on. 

How different are your functions? 

A five-person professional services firm may be able to use one operating cadence across the company. A 150-person company with sales, field operations, finance, project management, and customer support may need more variation. 

Alignment does not require uniformity. 

Every team does not need the same meeting. Every function does not need the same measures. Every decision does not need to travel through the same path. 

The question is whether the parts remain connected. 

Does your team need compliance or capability? 

A framework can create initial discipline, but the long-term goal should not be for people to follow a process they do not understand. It should be for them to use judgment inside a clear system. Your managers need to know why the planning rhythm exists, understand what the measures reveal, and be able to adjust the system when conditions change without blowing everything up. Otherwise, the company becomes dependent on whoever knows the framework best. 

That is not operating capability. That is outsourced certainty. 

What happens when the framework does not fit? 

This may be the most important question:  
Can your team adapt the tool or will every deviation be treated as failure? 

A framework should help you see the business more clearly. 

When following it makes the business harder to see, the framework has stopped serving you. 

The Case Against False Choices 

This is not actually a clean generic-versus-custom fight. 

A strong custom operating system may borrow elements from any of the frameworks. 

It may use information from Lean, Agile, Scaling Up, EOS, LeSS, systems thinking, organizational design, facilitation, project management, and the strange but useful process your operations manager developed because no existing tool solved the problem. 

The question is not whether an idea originated inside a branded framework. The question is whether it helps your people make better decisions and coordinate work. 

Similarly, choosing a generic framework does not mean your company should surrender all judgment. Implementation still requires context. What matters: 

• Your culture 
• Your leadership behavior 
• Your ownership 

You can’t install accountability while rescuing everyone from consequences. 

You can’t install a scorecard while arguing with every number you dislike. 

You can’t install long-term priorities every time a new request feels. 

The operating system is not what appears on the template. It is what leadership reinforces under pressure. 

When Generic Is Probably the Better Starting Point 

Generics may be a fit when: 

• The company lacks a consistent leadership rhythm. 
• The leadership team wants a proven, structured approach. 
• The business model is relatively straightforward. 
• Leaders are willing to follow the system long enough to learn from it. 
• The company needs shared language quickly. 
• The team is prepared to document processes and confront unresolved issues. 
• Customization would become an excuse for avoiding discipline. 

That last one matters. 

Some owners say they need a custom approach when what they mean is, “I would like to preserve my ability to ignore anything inconvenient.” 

That is not customization. That is avoidance with better branding. 

When a Custom Operating System Is Probably the Better Fit 

A custom system may fit when: 

• The business has multiple functions with meaningfully different workflows. 
• Existing processes are already mature but poorly connected. 
• The company operates in a complex or rapidly changing environment. 
• Leadership wants to build internal operating capability, not framework dependence. 
• The organization has tried prescribed systems that created ceremony without solving the underlying problem. 
• Decision rights and cross-functional handoffs are bigger issues than meeting structure. 
• The owner is willing to participate in diagnosis and change personal habits. 
• The company needs to preserve important cultural strengths while adding discipline. 

A custom approach is not easier and does require more honesty. You’ll lose the opportunity to blame the framework when the work is built around your business. 

The Question Beneath the Question 

Owners often ask, “Which operating system should we use?” 

The deeper question is: What does our business need to become capable of doing without me? 

Seeing the same reality? 

Making decisions closer to the work? 

Protecting priorities? 

Resolving issues? 

Learning from mistakes? 

Coordinating across functions? 

Developing managers who can think rather than wait? 

Start there. Then evaluate the framework. Not the other way around. 

Generic frameworks can be strong tools. A custom operating system can be a strong tool. 

Neither will save a leadership team from having hard conversations, making tradeoffs, clarifying authority, and changing the behavior that taught everyone to wait for the owner. 

Frameworks are useful. They are not magic. 

Choose the path forward that helps your people see, decide, and adjust, then make sure it builds a company that can breathe without you holding the entire thing together. You did not build a team just to become the permanent human help desk. 

You are allowed to lead. You are also allowed to leave the room. 

Not sure which model fits? Use the Generic-or-Custom Fit Scorecard to evaluate your complexity, leadership readiness, operating needs, and appetite for customization before committing to either path. 

-L