I sat in a meeting once where a founder spent forty minutes explaining their product. Forty. Minutes. By the end, I still couldn't tell you what it did. He was smart. The idea wasn't bad. But he'd wrapped it in complexity so thick that the signal disappeared.
I asked him: "What if you removed 80% of what you just said and kept only the core?" He looked at me like I'd asked him to remove 80% of his child.
Adding complexity is easy. Removing it is hard. And we confuse easy with smart.
Complexity as Default
Complexity feels like depth. It feels like you've thought things through. More features feel like more value. More steps in the process feel like thoroughness. More detail in the explanation feels like expertise.
They don't. They're the opposite. Complexity is a sign that you haven't figured out the simple version yet.
Consider the difference between a junior engineer and a senior one. The junior adds features because that's how you show you're working. The senior removes features and asks why they're needed. The junior writes 500 lines of code. The senior writes 50 lines that do the same thing better.
The same principle applies to products, marketing, strategies, operations. Every layer of complexity you add is a layer between your customer and value. Every feature, every step, every requirement, every process—they're all friction.
Most founders add complexity automatically. Customer wants feature X? Add it. Customer struggles with step Y? Add a feature to make it easier (instead of removing step Y). Competitive pressure? Add more features. Need to justify your salary to investors? Add more complexity so they think you're working.
That's why most products have features nobody uses. That's why most onboarding flows have steps that matter to nobody. That's why most strategies fail—they're too complicated to execute.
Why We Default to Complexity
The real reason is ego and fear. Complexity is cover.
If your product is complex, you can't be judged for simplicity. You can't be wrong about a core belief because the core is hidden under layers. If your strategy is complex, no one can say it's obvious. A complex explanation feels authoritative in a way a simple one doesn't.
Simplicity requires you to be right. When you say "Our product does X and it's better because of Y," you've made a claim someone can test. When you say "Our product creates an integrated ecosystem of solutions across multiple verticals with a focus on synergistic value creation," no one can really evaluate it. You've hidden behind language.
Complexity is cowardice. It's a way to avoid being proven wrong.
But here's the problem: customers don't want complexity. They want simplicity. They want to understand what you do in ten seconds. They want to use your product without a manual. They want to execute your strategy without a PhD.
The market punishes complexity. The founders who win are the ones willing to be simple and therefore vulnerable.
Apple's Advantage
Apple's entire strategy is removing complexity. When everyone else had seventeen settings, Apple had one. When everyone else offered customization, Apple offered consistency. When everyone else wrote thick manuals, Apple assumed you could figure it out.
This isn't a limit. It's an advantage. By removing complexity, Apple forced itself to think about what actually matters. What's the core? If you can only have one setting, what is it? If you can't customize, how do you make it delightful?
This constraint made them better. Not just at design—at thinking. Because constraints force clarity.
Most founders avoid constraints. They want optionality. More options feel safer—there's something for everyone. But more options mean less clarity. And less clarity means nothing for anybody.
The Courage to Simplify
Simplification is harder than complication. Anyone can add a feature. Removing a feature requires you to say no. No to a customer request. No to an investor idea. No to a feature you spent months building.
When I worked at Facebook, the entire design philosophy was about subtraction. What's the absolute minimum you need to show? What can you remove? The original Facebook wasn't simpler because it was early. It was simpler because every single element had a reason to exist.
That doesn't scale automatically. Every new feature pushed for the same simplicity principle. "Does this add signal or noise? Does it bring people closer or push them apart? Is it essential or convenient?" Saying no to convenient is hard. It requires discipline and courage.
Simplification requires three things:
First, you have to understand the problem deeply. You can't simplify something you don't understand. So simplification forces deep understanding. You have to know what matters and what's decoration.
Second, you have to have conviction. Simplicity means making choices and living with them. You're saying our product does X and not Y. Some customers will leave because of that. You need the conviction to accept it.
Third, you have to be willing to be wrong quickly. When you're simple, you find out fast if you're wrong. With complexity, you can hide mistakes for years. Simplicity exposes them immediately. That's a feature, not a bug—but it requires courage.
The Practical Path
If you're building something or leading something, start here: If you can't explain it in two sentences, it's too complex.
Not because two sentences is always the right length. But because the exercise of fitting it into two sentences forces you to identify what actually matters. Everything else is decoration.
Then, remove one thing every week. One feature, one process, one step. Not because it's broken—because it's there. Ask: If we removed this, what would break? If the answer is "a report nobody reads" or "a process that's become habit," remove it.
The team will resist. They'll say it's important. It's not. It's important to them because they built it. Remove it anyway.
You'll notice something happens when you remove complexity: clarity emerges. The thing you were trying to build becomes clearer. Your competitive advantage becomes obvious. Your message becomes sharper.
That's because complexity was hiding what actually works. Once you remove it, the signal is finally visible.
The Real Strength
Simplicity looks weak to the person inside the organization. It looks like you're not doing enough. But to the customer outside, simplicity is strength. It says: "We know exactly what we're doing and we're confident enough to do nothing extra."
The founders I respect most are the ones willing to build something so simple that it seems impossible anyone would pay for it. Then they sell it for millions. Not because they're geniuses. Because they had the courage to cut complexity away and show what was underneath.
That's the move. Strip everything down to what matters. Hold the line. Win.