Business as a System: Why Your People Problems Are Really Systems Problems 

Your operations manager is standing in your doorway. Again. She has a question about a customer issue that, technically, she has the authority to resolve. Your sales lead is waiting for you to approve a discount. Your project manager needs you to settle a disagreement between two people who have both worked at the company longer than some marriages last.Meanwhile, your inbox is collecting messages marked “quick question,” which is business language for this will somehow become your problem for the rest of the afternoon. 

By 5:30, you have made forty-seven decisions, attended six meetings, rewritten something someone else was supposed to own, and done approximately none of the work you planned to do. 

You have a team. 

You are still doing the cognitive labor of the entire company. 

Sound familiar? 

At some point, usually late at night or during the Sunday evening dread spiral, you start wondering whether you hired the wrong people. Maybe they are not proactive enough, not strong enough managers, don’t care as much as you do. Or maybe (this one tends to sting) you are simply bad at delegating. 

Here’s the truth: This probably isn’t a people problem. It’s a systems problem. 

That does not mean every employee is perfect. Some people are in the wrong role. Some managers should not be managers. Some behavior needs to be addressed directly rather than discussed for eighteen months in increasingly irritated leadership meetings. But when the same problems show up across multiple people, departments, and years, you are no longer looking at a collection of individual failures. You are looking at the business as a system. And the system is producing exactly what it has been designed – or quietly allowed – to produce. 

Your Business Is Already a System 

When I say, “business as a system,” I do not mean you need another software platform. You do not need a dashboard with seventeen tabs, a complicated diagram, or an expensive piece of technology your team will stop updating sometime around the third Tuesday. 

A business system is the full environment in which work happens. 

It includes: 

• How decisions get made and who has authority to make them 

• What happens when someone makes a mistake 

• Which behaviors get rewarded and the ones everyone complains about but continues to tolerate 

• Where information lives 

• How work moves between people 

• What gets measured and ignored 

• Whether priorities survive contact with Monday morning 

It also includes every unwritten rule your team has learned. 

The owner says, “I want people to take initiative.” The system says, “But check with me first.” 

Leadership says, “We trust our managers.” The system says, “Any decision over $500 needs three approvals and a minor act of Congress.” 

The company says, “We value accountability.” The system says, “Nothing will happen if you miss the deadline, but you may receive four reminders if you forget to update the spreadsheet.” 

People learn the real system quickly… and usually faster than leadership does. 

The System Always Wins 

Early in my career, I worked in organizations where leadership believed communication problems could be solved by sending more communication. 

More emails. More updates. More reports. 

At one point, I was asked to create a weekly company update about work that was already visible inside the product. Ninety minutes a week. Every week. 

The information existed. Anyone who needed it could access it. But instead of improving how information moved through the organization, the system assigned one person the job of copying it into another format. (Guess who? Yours truly.) 

It looked like a communication solution. It was really a workaround. That distinction matters. 

A workaround makes the immediate discomfort go away without addressing why the discomfort exists. This usually looks like: The business adds a meeting because people are not aligned. It adds an approval because someone made a bad decision. It adds a report because leaders do not trust the numbers. It adds a manager because the owner is overwhelmed. It adds a policy because one employee did something ridiculous. 

And eventually, the company is carrying years of operational scar tissue – extra steps, duplicate work, unnecessary approvals, and “temporary” processes that have somehow survived three office moves and a global pandemic. 

Then leadership looks at the team and asks why everyone moves so slowly. 

Uh… slowly through what? 

What Looks Like a People Problem 

Let’s look at a few common complaints. 

“My employees won’t take ownership.” 

Maybe. Or perhaps ownership has never been clearly defined. 

People are told to “own the result,” but they can’t approve the expense, change the timeline, challenge the priority, or say no to work that does not fit. That is not ownership. 

That is responsibility without authority—which is a lovely way to create anxious employees who ask permission before they breathe too aggressively. 

This is an area of personal frustration as I’ve lived it. I was responsible for explaining a product roadmap to customers, but I was not included in many of the conversations where that roadmap changed. I carried the responsibility. I did not have the authority. 

Some fake form of ownership had been handed down. Trust had not. Those decisions made ultimately made me leave that role. 

So before you accuse someone of avoiding ownership, ask: What can this person actually decide without me? 

Not theoretically and definitely not according to the job description you last updated when fax machines were still emotionally relevant. 

Actually. 

“My managers bring every problem to me.” 

That may not be a confidence problem; it may be learned behavior. 

What happens when a manager makes a decision you would not have made? Do you coach the thinking? Or do you step in, reverse the decision, fix the work, and remind everyone that this is why you have to be involved? 

You can’t complain that people depend on you while rewarding them for depending on you. That does not make you a bad person, and you’re probably just trying to protect the business.You built something valuable. You know where the landmines are. You can see consequences your team does not yet recognize. 

Of course stepping in feels responsible. 

But every time you provide the answer instead of building the person’s judgment, the system learns something: Wait for the owner. 

That is how you become the bottleneck while being surrounded by capable people. 

“No one communicates.” 

Usually, this means information is not moving where it needs to move, when it needs to move, in a form people can use. That is different from silence. Trust me, your company may communicate constantly. 

Slack messages. Emails. Meetings. Texts. Side conversations. Shared documents. Voice notes sent by someone driving down the highway, because apparently we have collectively decided that is normal. 

There is plenty of communication. There is no shared reality. 

One team updates the CRM. Another keeps a spreadsheet. The third team relies on whatever Gary remembers from the customer call. 

Then, leadership makes a decision in a meeting, but the people doing the work do not hear about it until the deadline changes. 

That is not a volume problem. It is a system design problem. 

“People resist change.” 

Sure, sometimes they do. 

People can become attached to a familiar process even when that process makes everyone miserable. Humans are fun that way. But before you label your team resistant, look at their experience. 

• How many initiatives have been announced and abandoned? 

• How many new priorities replaced last month’s new priorities? 

• How many consultants introduced a framework, renamed a few meetings, and disappeared before anyone had to live with the consequences? 

• How many employees gave honest feedback and watched leadership do absolutely nothing with it? 

People may not be resisting change. They may be protecting themselves from another unfinished leadership idea. 

That is not cynicism coming out of nowhere. The system taught them. 

The Five Places Systems Usually Break 

When we look at a business as a system, five areas tend to expose the real knots. 

Clarify how decisions get made. 

A job title is not decision clarity. Your team needs to know which decisions they own, which decisions require input, and which decisions genuinely need escalation. 

I’m not telling you everything needs a matrix, but I have seen a simple conversation fix a lot of the confusion. 

Answer: Who decides? Who contributes? What boundaries matter? When should the decision come back to leadership? 

Your managers can’t build judgment if every meaningful choice remains parked on your desk. 

Make work visible. 

At one point in my career, I was helping teams organize software work. Requests came from everywhere – hallway conversations, emails, phone calls, shoulder taps, and messages marked urgent by people with very different definitions of the word. The official backlog made the team look slow. The problem was not that the team was doing too little. 

Their backlog was incomplete. 

People were completing work that never appeared in the system because interruptions had become the actual operating model. Once we made the work visible, the conversation changed. We could stop debating whether people were busy and start asking whether the right work was moving.  
 
Visibility does not mean micromanagement. It means the team can see the same reality. 

Stop rewarding the behavior you claim to hate. 

Ok, ok. This one is uncomfortable. 

You can’t say you want strategic managers and then praise the person who personally rescues every project. You can’t say people should protect their capacity and then celebrate the employee who replies to email at midnight. You can’t say meetings should produce decisions while continuing to attend three-hour conversations that end with, “Let’s circle back.” 

Your culture is not what appears on the wall. It is what your system rewards… including the behavior you reward accidentally. 

Examine the handoffs. 

Most work does not fail while one person is doing it. It fails between people:  

Sales > Operations > Finance > Leadership > Management > Marketing > Sales > Customer 

And then what? Who knows? Who acts? What info even moved? Where was it recorded? What happens if the usual person is on vacation, sick, or finally enjoying the pool they pay to maintain? 

When handoffs live in people’s heads, your strongest employee becomes infrastructure. That may feel efficient right up until she leaves. 

Build learning into the weekly rhythm. 

Businesses often review results without reviewing how those results were created. 

Revenue is down. Projects are late. Customers are frustrated. 

Fine. 

But what happened inside the system? Where did work wait? What decision arrived too late? What assumption turned out to be wrong? What did someone notice but feel unable to say? 

A healthy system does not avoid mistakes. It makes mistakes visible early enough to learn from them. 

A System Is Not the Same as a Framework 

This is where business owners often reach for an operating framework. A quick Google search will reveal many. And after that, you’ll end up with a book, a consultant, a new cadence, and a wall of sticky notes (that ends up threatening to become permanent office décor). 

Frameworks can help. 

I have learned from several of them. I have taught them. I have implemented them badly, then adequately, then much better. 

Frameworks are wonderful teachers. 

They are terrible saviors. 

A framework gives you a way to see the business. It gives you language, structure, questions, and practices. What it can’t do is remove your responsibility to understand your company. 

You can’t graft a collaborative framework onto a fear-based culture and expect collaboration. You can’t install a quarterly planning process while changing priorities every Thursday. You can’t give managers scorecards while withholding the information they need to influence the numbers. 

The framework is not the operating system. The operating system is how people behave once the meeting ends. 

The Owner Is Part of the System 

You are not standing outside the business, observing it like a scientist in a clean white coat. You are in it. 

Your habits shape it. Your reactions teach it. Your exceptions rewrite it. 

Every time you bypass the process because doing it yourself is faster, you teach the company that the process is optional when pressure arrives. Every time you answer a question your manager could have worked through, you teach the manager to bring the next question back too. Every time you tolerate behavior from a high performer that you would never accept from anyone else, you teach the team that results buy immunity. 

This is not an invitation to blame yourself for everything. 

You are not broken. But you are participating in the system. 

That is good news. Participation means influence. You can change what the business teaches. 

Start With Diagnosis, Not Decoration 

Before you add a tool, hire another manager, or introduce a new meeting rhythm, look at the system you already have. 

Ask: 

• Where does work repeatedly stall? 

• Which decisions keep returning to the owner? 

• Where are people responsible without having authority? 

• Which process depends on one person’s memory? 

• What behavior do we complain about but continue to reward? 

• Which meeting exists because another part of the system is not working? 

• What changes when the owner leaves the room? 

You do not need to redesign the entire company in a weekend. Please do not try. Your family has suffered enough from the phrase “I’m just going to work for an hour.” 

Find one recurring pattern. Follow it through the business. Look at the roles, decisions, expectations, incentives, information, and behavior surrounding it. Then change the conditions, not just the person standing closest to the problem. 

This is the work of treating your business as a system. 

Not blaming your team. 

Not blaming yourself. 

Not stretching the rubber band farther and hoping it holds. 

Pause. 

Look at what the business has learned, then rebuild it with intention. 

The goal is not a company that can function only when you are watching it. The goal is a business where good people can use good judgment—and where you are finally allowed to have a life outside the system you built. 

Ready to see where your business is teaching people to wait, escalate, or work around the system? Start with the Business Readiness Assessment. 

-L