When Your Solutions Become Your Problems

The solutions that built your company are often the ones now holding it back. That's the trap of a growing business, and it catches strong operators hardest, because the instincts creating the problem are the same ones that earned the success. It's the point where linear cause-and-effect stops working and systems thinking becomes the capability that separates companies that scale from companies that stall.

Picture a founder whose consultancy grew from eight people to thirty-five in three years. Early on, her hands-on style was the edge: fast decisions, personal attention on every account, informal communication that kept everyone pointed the same way. By year three, each of those strengths had turned into a constraint. Fast decisions skipped people who had input she needed. Personal attention made her the bottleneck on everything that mattered. Informal communication left the team guessing at priorities. So she did the logical thing and hired managers, added process, built structure. The managers inherited unclear authority. Her new process slowed the responsive service clients came for. And the structure felt like bureaucracy to a team that prized the old informality. "Every time I solve one problem, I create two more," she told me.

That sequence isn't a failure of management; it's the signature of a company crossing from a simple system into a complex one, and still reaching for simple-system fixes.

The transition nobody names

Every company starts on simple logic: do A, get B. Work harder, win more customers. Hire good people, get better results. Tighten the process, gain efficiency. That linear thinking is correct while the business is small enough for one person to hold the whole of it in view.

Somewhere between twenty and a hundred employees, the wiring changes. The business becomes a system where everything touches everything else. A move in one area sends reactions through three others. A fix in sales creates a problem in delivery. Good intentions produce outcomes nobody chose. These are the growing pains of a Second Stage company, and they don't yield to more effort or tighter control, because effort and control are part of what's producing them.

The old approach fails for a structural reason: in a complex system, cause and effect come apart.

• Everything connects, so a change ripples in directions you never mapped
• The consequences you didn't intend routinely outweigh the benefit you did
• Root causes hide in the relationships between parts, not in the parts themselves
• Leverage sits in unexpected places, where a small change moves the whole
• Time delays separate a fix from its fallout by months, hiding the link between them

Five ways a good solution turns into a new problem

Each of these starts as sound management. Each becomes a problem for the same reason: it improves one part without accounting for the system around it.

Efficiency trap: you streamline and strip out slack to lower cost. The leaner system now has no buffer, so ordinary variation or a single supplier hiccup breaks it. Resilience and efficiency pull against each other, and some of the "waste" you removed was adaptability in disguise.

Specialization spiral: hiring specialists and building departments raises capability, and it also hardens the boundaries between the people who now have to coordinate. The handoffs start to fail. Marketing ships what operations can't support; sales promises what delivery can't keep. The interfaces between functions come to matter more than the functions.

Control paradox: adding approvals and oversight to protect quality invites people to route around the control, do the minimum it asks, or optimize for compliance over the result. The act of controlling changes the behavior you were trying to control, often defeating the point of the control.

Growth ceiling: leaning on the approach that built the early wins works until it doesn't, because what serves one scale blocks the next. Founder involvement that was decisive becomes the bottleneck. The informality that made the culture prevents the structure the company now needs. What got you here won't get you there.

Measurement distortion: installing metrics to focus effort teaches people to optimize for the number rather than the thing the number stood for. Sales hits revenue by taking unprofitable accounts; teams hit delivery targets by pushing quality problems downstream. How you measure shapes behavior more than what you say you want.

Notice the shared shape. In each one, a reinforcing loop forms where the fix quietly feeds the problem it was meant to solve. That loop, left unexamined, is how a company ends up working harder every year to stay in the same place.

The shift from linear to systems thinking

Systems thinking is the discipline of managing the relationships between the parts rather than the parts on their own. A few of the moves matter most at this stage.

• From parts to relationships. Stop optimizing departments in isolation and optimize the handoffs between them. Solve problems at the interfaces, where they live.
• From events to patterns. A problem that keeps recurring is rarely a run of bad luck. Find the structure generating it and change the structure, rather than fighting each instance as it appears.
• From control to conditions. Rather than directing behavior through authority, shape the structure and incentives so the right move is the easy one. Remove the barrier instead of adding the rule.
• From immediate to delayed. The effects that matter most tend to arrive late. Track leading indicators, give a change time to move the system, and respect that the best leverage usually carries the longest lag.

None of this turns every decision into a systems analysis. It means recognizing when a problem is systemic, and thinking differently on the ones that are.

If you're a linear thinker, you can still lead this

The capability itself takes years to build, and plenty of excellent leaders are linear thinkers by temperament. Linear thinkers tend to be strong at execution and decisions. The task isn't to rewire who you are. It's to know when you need the systems view and to have a dependable way to get it.

That usually comes down to two things. Find the systems thinkers already around you: the people who ask "what else will this affect," who sit comfortably with ambiguity, who tend to name the unintended consequence before it lands. Then bring in outside perspective built for this: an advisor, a board member, or a peer who has navigated the same complexity and can see the loops you're standing inside of.

A handful of questions do a surprising amount of the work. Before you roll out a fix, ask what else it might touch. When a problem keeps returning, ask what pattern is producing it. For any solution, ask what it looks like in six months and in two years. The questions aren't there to slow you down; they surface the second-order effects while those effects are still cheap to design around.

The leaders who navigate this best stop treating complexity as the enemy. They stop expecting a growing business to behave like a small one, and they build the systems view, their own or borrowed, to match the reality their success created.

Frequently asked questions

What is systems thinking in business?

Systems thinking in business is the practice of understanding a company as a set of interconnected parts that influence each other, rather than a collection of separate problems to fix one at a time. It focuses on the relationships and feedback loops between functions, the unintended consequences of decisions, and the time delays between an action and its effects. Where linear thinking asks "what caused this problem," systems thinking asks "what pattern of interactions produced this situation." It becomes essential as a company grows past the point where one person can see and manage the whole directly.

Why do the solutions that built my company start causing problems?

Because the fixes that work in a simple system often make a complex one worse. When a company is small, cause and effect are tight and visible, so direct solutions work cleanly. As it grows, the parts become interconnected, and a fix in one area now creates second-order effects in others that can outweigh the original benefit. The solution was sound for the system you had. The trouble is that your success quietly changed the system into one that behaves by different rules.

When does a business cross from a simple system to a complex one?

Most companies cross over somewhere between twenty and a hundred employees, though the trigger is loss of visibility, not a precise headcount. The marker is the moment no single person can hold the whole business in view anymore. Decisions that used to have obvious consequences start producing surprises. Proven approaches stop delivering their usual results. This is the core of the Second Stage transition, and it's less a size than a shift in how the business has to be understood and led.

What are the growing pains of a Second Stage company?

The defining growing pain is that the operating model which drove early success starts working against continued growth. Founder involvement becomes a bottleneck. Informal communication that once kept everyone aligned now leaves people guessing. Efficiency measures remove the slack the company needs to absorb change. Each pain shares a root: a company managing a complex system with the habits of a simple one. The work of the Second Stage is building an operating approach matched to the complexity that growth created.

I'm a linear thinker. Can I still run a complex company?

Yes. Many effective leaders are linear thinkers, and that style brings strengths in execution and decisiveness. The requirement isn't to become a natural systems thinker overnight; it's to recognize when a situation calls for the systems view and to have reliable ways to bring it in. That means surrounding yourself with people who see connections and consequences you don't, asking a few disciplined questions before you act, and working with advisors who have navigated this complexity before. The goal is access to systems thinking, not a personality transplant.

How is this different from just hiring better managers or adding process?

Hiring managers and adding process are often the exact linear fixes that backfire, which is why this needs a different frame. More management and more process treat the symptom as a lack of structure, when the underlying issue is a set of interactions the new structure will also have to run through. Added without a systems view, they generate the control paradox and the specialization spiral described above. The difference is diagnostic: systems thinking asks what pattern is producing the problem before deciding what to add, so the fix works with the system instead of loading another layer on top of it.

How do you help leaders build systems thinking?

The work is part diagnosis and part building the outside view a busy operator can't reliably supply for themselves. That starts with mapping where a company's specific patterns of complexity are creating recurring problems, then working on the few leverage points where a change moves the whole rather than one corner of it. For leaders who are linear thinkers by nature, a large part of the value is sitting outside the system, naming the loops they're standing inside of, and asking the second-order questions before a decision hardens into a new problem.

Where to take this next

This kind of thinking gets sharper the moment you apply it to your own company's specific patterns of complexity, rather than the general idea of it. I work with owners and leadership teams of closely-held and family businesses on this: the strategy and leadership work of finding where complexity is creating recurring problems, and the few leverage points that move the whole. If that's where you are, that's the work I do.