Tools & Thoughts for Leaders

Simplifying complexity

TTL 22

Chaos is layered, not random.

👋 Good Morfternight! Paolo Belcastro here, welcoming you to the twenty-second issue of TTL: Tools & Thoughts for Leaders, your weekly dose of leadership insights.

Today, I want to explore a concept that transcends disciplines and industries: breaking down complexity into its simplest components.

Complexity often feels overwhelming, but at its core, it’s usually a collection of simpler components working together—sometimes in misalignment.

By isolating and understanding these basic building blocks, we can make sense of the chaos, uncover patterns, and unlock innovative solutions.

Lessons from sinusoids

To see this concept in action, let’s look at a visual representation of how simple elements can give rise to highly complex reactions.

Take a look at this graph, which represents a function with pseudo-random and significant variations.

Pretty unpredictable, uh?

If we break it down, we notice that it’s actually the result of combining three simpler functions, each with less randomness and fewer variations.

Breaking it down further, these functions can themselves be reduced to six basic sinusoidal components—each with a highly regular pattern and constrained amplitude (oscillating between -1 and +1 by definition).

Oftentimes, what appears random is merely the result of layered simplicity: randomness isn’t random at all.

These three sine waves—each simple and predictable, when overlapped with slight phase shifts, produce a waveform that appears chaotic at first glance.

This concept serves as a powerful metaphor for leadership.

What feels like overwhelming complexity—whether in team dynamics, customer behavior, or product performance—is often the result of simpler elements working out of sync. For example, a team repeatedly missing deadlines might not be due to one glaring issue but a combination of factors: communication gaps, conflicting incentives, or resource constraints.

By isolating these variables and addressing them one by one, the seemingly “random” failures become understandable—and solvable.

Tackling complexity through first principles

Just as breaking down chaotic patterns reveals simpler components, we can apply the same approach to solving real-world problems. One of the most effective ways to tackle complexity is by using a first principles approach: breaking a problem down to its fundamental truths.

This method doesn’t just simplify the issue—it challenges assumptions, bypasses traditional thinking, and unlocks innovative, efficient solutions.

Take rockets, for example.

For decades, space missions came with astronomical price tags. Engineers focused on small, incremental improvements—reducing material costs or optimizing fuel efficiency—while ignoring the more in-depth issue: rockets were single-use. Each launch required building an entirely new rocket, only for it to be discarded after one flight.

Now, imagine if airplanes worked the same way—if every trip from Paris to New York required a brand-new plane that was scrapped upon landing. Air travel wouldn’t just be unsustainable; it would be unthinkable.

The breakthrough in space exploration came from rethinking the system entirely: instead of tweaking costs at the margins, rockets needed to be reusable.

This type of thinking demands stepping back, questioning every assumption, and digging into the root of the problem.

Simplify. Strip away what’s unnecessary. Then rebuild with clarity and purpose.

The “5 whys” technique

To accomplish this, one of the most effective tools is the “5 Whys” technique, developed by Toyota—a simple yet structured method for uncovering the root cause of any issue.

The idea is straightforward: ask “why” repeatedly—typically five times—to dig deeper into a problem and identify its true origin.

By the fifth “why,” you should have identified the root cause.

Here’s an example:

Symptom: Sales are declining.

  • Why #1: Marketing campaigns aren’t driving traffic.
  • Why #2: The campaigns aren’t targeting the right audience.
  • Why #3: We haven’t updated our customer personas.
  • Why #4: We lack up-to-date data on customer preferences.
  • Why #5: Our analytics tools are outdated.

The root problem here isn’t the marketing team’s creativity, but the outdated analytics tools.

This method not only resolves immediate difficulties but strengthens the overall system by addressing foundational weaknesses.

I find that “The 5 Whys” technique is just as valuable in personal conversations and career development as it is in problem-solving. By asking “why” repeatedly, it helps uncover the deeper motivations behind our ambitions and goals. You might discover that what you truly want is different from what you initially thought, or realize there are alternative paths to achieve it.

However, it’s important to strike a balance—there’s a reason it’s called the 5 Whys, not the 18 Whys. Digging too far can lead to overly broad or philosophical answers, leading us nowhere.

The art of testing

When facing complexity, resist the urge to address everything at once.

One of the most common pitfalls in problem-solving, especially in product development, is trying to address multiple variables simultaneously, which leads to ambiguous results.

For instance, if you’re redesigning a landing page to improve conversions, changing the color scheme, call-to-action placement, and headline all at once will make it impossible to determine which adjustment influenced the outcome.

Instead, focus on isolating one and only one variable at a time—this is the foundation of effective A/B testing.

This principle extends beyond product development. In team processes, avoid overhauling multiple elements at once when things aren’t working. Make a single change, observe its impact, and iterate. Incremental adjustments provide clarity and ensure sustainable improvements.

Misaligned goals

The concept of simplification applies to personal relationships too, whether within a single team or across multiple teams.

In teams and organizations, dynamics often feel more complicated than they really are.

What looks like chaos is frequently the result of misaligned goals rather than a lack of skill or effort.

Individuals and groups, each driven by their incentives, can unintentionally work against each other, creating friction and inefficiencies.

The good news? Realignment, not overhaul, is typically the key to resolving these conflicts.

Take the classic case of a sales team versus a customer support team. Sales might be focused on increasing the number of new subscribers, while support prioritizes reducing churn. Sales wants volume, often achieved through aggressive promotions, while support wants satisfied, long-term customers. These priorities seem to clash, but the conflict dissolves if you redefine their shared objective. Aligning both teams around a metric like “revenue per subscriber” balances growth and retention, fostering collaboration and ensuring everyone works toward the same goal.

Another common source of tension is the age-old battle between speed and quality. Development teams are regularly pushed to release new features quickly, while quality assurance teams aim to deliver reliable, bug-free products. These goals can feel like polar opposites, but they don’t have to be. The solution is clear role definition: let one team drive rapid development and innovation, while the other ensures long-term quality and stability. Dividing responsibilities this way reduces conflict and ensures both priorities are addressed effectively.

When goals are aligned, what once felt like unmanageable complexity transforms into coordinated effort.

Teams work better together, conflicts are minimized, and the organization moves forward.

Practical applications across contexts

In leadership

When leading teams, complexity often manifests as conflicting priorities or unclear processes. Use the principles of simplification and alignment to uncover hidden barriers.

In product development

Complex systems create complex reactions. A single overlooked variable can derail a launch or compromise customer satisfaction. Simplifying your processes—through rigorous testing, prioritization, and feedback loops—keeps your team focused on what matters.

In personal growth

Simplification isn’t just for systems; it’s essential for self-reflection. Ask yourself: Why are you pursuing this career path? Why does this challenge frustrate you? By peeling back the layers and discarding superficial answers, you can uncover the deeper motivations and truths that guide your personal and professional growth.

Remember, simplification is essential—but we live in a world of intricate, interconnected systems.

Simplifying is how we operate: we categorize, divide, and process information to make sense of the surrounding chaos.

Not to overlook the complexity that shapes our world.

The purpose of simplifying is to make complexity understandable, not to eliminate it.


That’s it for today.

If someone forwarded this to you, you can subscribe to get your copy next week. If you enjoyed reading this, please share it.

Here on TTL, we dig into practical leadership tips and effective strategies, with a particular focus on tech leadership and managing distributed teams (that’s what I do every day, add me on LinkedIn).

Whether you’re steering a tech startup or leading a remote team, these insights are designed to help you navigate the complexities of modern leadership.


I also publish on paolo.blog and monochrome.blog

Cheers,

Response

  1. […] week, in our discussion on the “tension between development and QA teams”, I noted how development thrives on speed and innovation, while QA focuses on stability and […]

Leave a Reply

Your email address will not be published. Required fields are marked *

You may also enjoy…