📖 yourdailystory Browse all stories →
Systems & Scale Thinking
Published on Saturday, 08 August 2026 · ⏱ 11 min read

Jeffrey Immelt: Re

You know that feeling when you pull a loose thread on a sweater, and suddenly half the garment starts to unravel? That’s what it’s like to work with complex systems. To truly lead at scale, to guide teams through rapid growth, or to re-architect a legacy platform, you need to understand those unseen threads. You need Systems & Scale Thinking.

It's not about knowing every tiny detail of every component. That’s impossible. It's about seeing the interconnectedness of everything. It's about understanding the invisible forces that govern how things interact, feed into each other, and what happens at their edges. This insight lets you find the leverage points – the small nudges that create massive, positive change. It helps you anticipate the unintended consequences before they hit.

Here’s the thing nobody tells you about this skill. It's not intuitive. Your brain is wired for simple cause-and-effect. But in complex systems, the cause might be far removed from the effect, or the effect might loop back and become a new cause. It feels messy at first. And that feeling of not seeing the whole picture can make you feel incompetent. It's an emotional barrier, not an intellectual one. Don't let that stop you.

Let’s break this down.

Deconstruct: Identify the Loops and the Levers

The smallest, most useful piece of systems thinking is learning to identify feedback loops and leverage points.

A feedback loop is simple: when an output of a system feeds back as an input. Think of a thermostat. When the room gets cold (output), it tells the furnace to turn on (input), which then warms the room. That's a balancing feedback loop. But feedback can also be reinforcing: more users join your platform (output), making the platform more valuable (input), which attracts even more users. This is network effect.

A leverage point is a place in a system where a small shift can lead to large changes elsewhere. It's like finding the fulcrum for a heavy lever. Often, these aren't the obvious points. Pulling the visible lever might just break it. The real leverage is often in the system’s goals, its information flows, or its underlying paradigms.

For instance, consider a company with slow product development. A naive approach might be to hire more engineers (adding more parts). A systems thinker might ask: What's the feedback loop? Is it too many meetings (output) leading to less coding time (input)? Or is it vague requirements (output) leading to rework (input)? The leverage point might be in redefining the requirement gathering process, not adding more staff.

Remove Friction: Start Small, Map Backward

The emotional barrier to systems thinking is often overwhelm. Complex systems look like an impossible tangle. Trying to map an entire organization, or a global supply chain, or a large software platform all at once, is paralyzing.

To remove this friction, don't try to see everything at once. Pick one observable outcome or problem that's bothering you. Maybe it's customer churn, or a recurring bug, or slow deployment times. Now, trace its origin backward through just two or three layers of interaction. Ask, "What causes this?" And then, "What causes that?" Do this two or three times.

For example, if the problem is "slow deployment times": 1. What causes slow deployment times? "Manual testing takes too long." 2. What causes manual testing to take too long? "We don't have good automated tests." 3. What causes a lack of automated tests? "Developers aren't incentivized to write them, or they lack the tools."

You don't need to trace every thread. Just follow a few critical ones. This focused, iterative approach breaks the overwhelming task into manageable pieces.

You can even use AI as a coach here. Don't ask it to design your system. Instead, when you’ve identified a problem, ask your AI: "Given that X is a problem, what are three non-obvious components of a typical software system that might be contributing to it?" Or, "Help me phrase a question to uncover potential unintended consequences if we change Y in this context." This helps you widen your own lens, not replace your thinking.

Learn Enough to Self-Correct: Watch for Whack-A-Mole

How do you know you're doing systems thinking wrong? It’s simple: your solution to one problem creates two new, equally difficult problems somewhere else. This is the "whack-a-mole" effect. You optimize one part, only to see overall performance degrade, or a new bottleneck emerge.

When this happens, you haven't failed. You've simply missed a critical dependency or a crucial feedback loop. Your "system boundary" was too narrow.

The self-correction isn't to give up. It's to zoom out one step further. Expand your boundary. Realize that the component you optimized was more interconnected than you thought. You aren't incompetent; you just need to widen your lens and understand the next layer of interaction. Embrace the whack-a-mole as a signal, not a defeat.

Practice with Focus: Jeffrey Immelt and GE’s Digital Bet

In 2001, Jeffrey Immelt took the reins of General Electric from the legendary Jack Welch. Welch had built GE into a sprawling, efficient industrial and financial powerhouse. But Immelt saw a future where machines, no matter how powerful, were just physical shells. The real value, he believed, would come from the data they generated and the software that interpreted it. He envisioned GE becoming a "digital industrial" company.

This was a grand vision of Systems & Scale Thinking. GE wasn't just building jet engines, power turbines, and MRI machines anymore. Immelt wanted these machines to be intelligent. He saw their millions of sensors generating petabytes of data, data that could predict failures, optimize performance, and even inform new designs. He launched Predix, a software platform designed to connect all these industrial assets, analyze their data, and create new services.

The challenge wasn't just technical. It was profoundly systemic.

Imagine Immelt in a strategy meeting, trying to explain the invisible threads. He wasn't just asking his aviation division to build a better engine. He was asking them to understand how data from that engine, analyzed by software, could inform how airlines scheduled maintenance, optimized flight paths, and even structured their financing models based on predicted uptime. He was connecting vast, disparate systems: physical engineering, software development, data science, customer operations, and financial services.

He faced immense friction. How do you integrate agile software developers into century-old industrial divisions? How do you build a common platform, Predix, that can speak the language of both a wind turbine and a hospital's MRI scanner? How do you overcome the inertia of a company where each division had its own deeply entrenched processes, cultures, and even its own data silos?

Immelt believed the leverage point wasn't just in the new code, but in shifting GE’s entire operating paradigm. He wanted GE to move from selling products to selling outcomes – selling "uptime" for a jet engine rather than just the engine itself. This required a fundamental re-architecture of how GE built, sold, and serviced its products. It meant understanding new feedback loops: better data -> better predictions -> less downtime -> happier customers -> more data.

The struggle was immense. GE’s sheer scale and complexity meant every change rippled through a vast, intricate ecosystem of people, processes, and technology. The embedded systems, the existing incentives, the deeply ingrained ways of thinking acted as powerful balancing feedback loops, resisting change. Engineers who had spent careers perfecting physical tolerances now had to think about software updates and cybersecurity. Business leaders had to grapple with new subscription models.

Immelt spent billions on this transformation. He knew the emotional barrier was real: people felt they were being asked to abandon what made them successful. But he pushed, because he saw the future demanded a fundamental re-evaluation of GE as a system, not just a collection of successful businesses.

Ultimately, the transformation proved too difficult to fully complete under his tenure within GE’s existing structure. The sheer scale of systemic change, combined with external financial pressures, led to Immelt’s departure and GE’s eventual breakup into separate companies.

But his vision and his attempt to re-engineer such a colossal machine highlight the core challenge and power of Systems & Scale Thinking. He saw the unseen threads, understood the profound leverage points that could be pulled, and faced the immense friction of trying to fundamentally alter the feedback loops of an industrial giant. His story shows that even when the outcome isn't a clean, unmitigated success, the thinking required to attempt such a transformation is precisely what leaders on a growth path must cultivate. You learn to see the world not as separate pieces, but as a living, breathing, interconnected organism.

The Skill

Systems & Scale Thinking is the ability to perceive and analyze the invisible network of dependencies, feedback loops, and leverage points that govern complex organizations and technologies. It's seeing the whole forest, not just the trees, and understanding how changes to one part ripple through the entire ecosystem, often in non-obvious ways. It’s about understanding dynamic complexity – where cause and effect are not close in time or space. This skill lets you identify the most effective points for intervention, anticipate unintended consequences, and build more resilient, adaptable systems.

Do This Today

During your team's stand-up or project meeting tomorrow morning, identify one proposed change or solution. Before it's approved, ask one specific question about a potential unintended consequence or a ripple effect on another system. For example, "How might optimizing X impact Y downstream, or Z's workload?" The goal is to articulate an impact on a component outside the immediate scope of the proposed change.

Sources

This is a dramatized editorial narrative created for personal inspiration, drawn from publicly available sources listed above. It is not affiliated with or endorsed by the person, company, or their estate.

Read on yourdailystory.com →

One true story a day to get a little better. Start today's →