Introduction

In a world that celebrated “more features” and “bigger stacks” right up until the calendar politely reminded us it was 2020, the argument for simple thinking came roaring back. Simplicity isn’t a fad it’s an organizing principle. Whether you’re investing, designing a product, running a team, or just trying to plan dinner without spiraling into existential grocery aisle dread, the simple solution often wins. This piece slices through the noise of post-2020 complexity and shows, with practical examples and a dash of common sense, why less often beats more.

Why Simplicity Matters

Simplicity clarifies decisions, reduces hidden costs, and scales better over time. Business leaders and designers lean on principles like KISS (Keep It Simple, Stupid) and Occam’s Razor because they reduce cognitive load and operational drag. The KISS mindset is not about dumbed-down thinking it’s deliberate pruning, removing features and procedures that offer illusionary benefit while adding real maintenance burdens.

Decision-making: clarity beats cleverness

Complexity gives the illusion of sophistication. Faced with two options, people tend to assume the elaborate explanation is smarter a cognitive quirk known as complexity bias. That bias nudges teams toward complicated frameworks, exotic tools, and “strategies” that require consultants and slide decks to explain. In reality, simple systems focus your attention on the drivers that matter most and make it easier to learn from feedback.

Simple vs. Complex in Investing A 2020 Lens

Investing provides one of the clearest case studies: a humble, diversified index portfolio beats many elaborate strategies over long stretches. Ben Carlson’s analysis repeatedly highlights how straightforward three-fund Vanguard-style portfolios held up against large, actively managed endowments during the 2020 period drawing on the NACUBO/TIAA endowment data and showing that simplicity was not only competitive but often preferable. The takeaway: lower fees, broad diversification, and fewer trading impulses matter.

Why the simple portfolio wins

• Lower fees leave more return in your pocket.
• Passive diversification reduces manager risk and style drift.
• Fewer decisions mean fewer opportunities for behavioral mistakes.

Product and Design: Simplicity as Strategy

In product design, the battle between feature accumulation and user experience is eternal. Teams that prune thoughtfully produce products that delight users and cost less to maintain. Firms that obsess over elegant, simple flows often win retention; they trade marginal features for increased clarity and reliability. Forbes and other business outlets have pointed out that elegant simplicity saves money and improves outcomes especially in crises or when demand spikes unpredictably.

Design rules of thumb

– Prioritize core user journeys.
– Remove or delay “nice-to-have” features.
– Measure the operational cost of each addition (not just engineering time).

When Complexity Is Necessary

Simple is not always sufficient. Complex environments (global supply chains, large-scale scientific models, layered regulatory regimes) may legitimately require nuanced processes and multiple subsystems. The skill is not to fetishize complexity but to match the solution’s sophistication to the problem. Sometimes you need a multi-model forecast; sometimes you need a single rule-of-thumb. The trick is to recognize which category you’re in and avoid the one-size-fits-all trap.

Checklist to decide whether to add complexity

1. Does the increased complexity materially improve outcomes? (Not just marginally.)
2. Can you observe and measure the benefits?
3. Can your team reliably operate and maintain the added complexity?
4. Is the complexity robust under stress and change?

Common Patterns That Create Bad Complexity

Some sources of bad complexity are easy to spot: feature bloat, overlapping workflows, opaque specialist silos, and exotic customizations that only one person fully understands. These patterns increase operational risk and make organizations brittle the opposite of resilient. Recognizing complexity bias and the seductive narrative of “special sauce” helps leaders resist the urge to complicate for the illusion of competence.

Practical Steps to Simplify

Simplifying is an active discipline. Here are concrete moves you can make tomorrow:

• Audit features and processes. Remove or archive anything not used or that costs more than its benefit.
• Set constraints. Limits force creativity like strict budget caps or reduced sprint scope.
• Standardize templates and decisions. Templates reduce repeated ad-hoc choices that breed chaos.
• Automate the routine. Good automation reduces error without adding hidden maintenance costs.
• Build kill-switches. If a subsystem fails, can the rest of the machine operate safely?

Examples That Illustrate the Trade-off

Example 1 The 3-Fund Portfolio

A simple construction of U.S. total market, international total market, and total bond market funds provides broad exposure with minimal cost and decision friction. During the volatile 2020 calendar year and the fiscal window ending June 30, 2020, data showed that straightforward index allocations were robust relative to many complex active programs in endowments. That robustness came from diversification, low fees, and not trying to time markets.

Example 2 Product feature pruning

An online product team removed low-usage “advanced” filters and consolidated three reporting screens into one. The immediate effects: fewer bugs, faster load times, and an unexpected uptick in new-user activation because people no longer needed a product manual to navigate the basics. The lesson: features intended to help power users can make the product harder for everyone else.

How to Keep Simplicity from Becoming Dumbed-Down

Simplicity should be elegant, not lazy. The goal is to remove the unnecessary while preserving robustness. Asking “what problem are we solving?” at every step prevents the slide into oversimplified solutions that fail when the environment changes. Good simplicity has: intent, measurable goals, and graceful failure modes.

Conclusion Common Sense, Revisited for 2020

The events around 2020 market turbulence, supply shocks, and rapid digital acceleration made one thing clear: simpler systems are easier to adapt, less expensive to maintain, and more transparent in crisis. Complexity can be essential, but it should be adopted deliberately, measured rigorously, and pruned mercilessly when it stops delivering value. If you want a short rule-of-thumb: start simple, watch results, and add complexity only when it demonstrably improves outcomes.

meta_title: Simple vs. Complex Practical Common Sense (under 60 chars)

meta_description: Why simple systems often beat complex ones lessons from 2020 for investing, product design, and decision-making. (under 155 chars)

sapo:
In the wake of 2020’s disruptions, simplicity proved its value across investing, product design, and leadership. This article explains why simple approacheslike the classic three-fund portfolio, lean product designs, and clear decision rulesoften outperform complicated alternatives. We cover cognitive biases that make complexity attractive, practical steps to simplify, and real-world examples that show how pruning features and decisions leads to better outcomes. If you want resilient systems, less costly operations, and clearer thinking, start with simple.

keywords: simplicity vs complexity, simple investing, complexity bias, KISS principle, 2020 lessons, Ben Carlson, three-fund portfolio

Personal and Professional Experiences on Simple vs. Complex (Field Notes)

I’ve seen the simple/complex trade-off up close in three arenas: a startup I advised, a mid-sized nonprofit’s finance team, and a family household during a chaotic holiday season. Each taught the same lesson in different uniforms.

At the startup, the product roadmap looked like a candy store: dozens of “must-have” features, each with a horde of sticky notes and optimistic timelines. The engineering team spent cycles building customization widgets that only a handful of beta customers used. When the founder asked us to cut scope, the pushback was intense “but it’s requested!” Fast-forward three months after pruning: deployment times halved, onboarding improved, and net retention ticked up. The removed features were never missed by new users and the codebase became easier to reason about. The collective sigh of relief when the build pipeline stopped failing every Tuesday was worth the initial political cost.

The nonprofit’s finance team had a policy matrix that multiplied like rabbits: multiple approval layers, special-case expense flows, and a half-dozen bespoke spreadsheets. During a fiscal crunch in 2020, leadership realized the approval chain itself was preventing fast decisions. We consolidated approvals, reduced redundant reports, and introduced a simple threshold rule (expenses under a modest amount auto-approved). That small change shortened the time to get funds to program staff and prevented missed grant deadlines. It also reduced the number of midnight spreadsheet edits a quality-of-life improvement for the finance team that didn’t show up on the balance sheet but mattered.

On the domestic front: holiday meal planning. The first year I tried to “up-level” everything three appetizers, two sides per person, a dessert flight I spent two days either at the store or in the kitchen. The result: stressed host, messy prep, and a menu that took away time from conversations. Next year I selected a few excellent items and doubled down on make-ahead prep. The food was better, the conversation was richer, and the cleanup was manageable. Simpler systems free cognitive bandwidth for what matters: relationships, strategy, and learning.

Across all these settings the pattern is identical. Complexity is often introduced with good intentions: to cover edge cases, to wow customers, or to be “thorough.” But complexity carries hidden taxes training time, greater failure surface, slower iteration. The antidote is discipline: clear criteria for adding features, routine audits to remove what’s unnecessary, and structured experimentation so complexity is only added when it proves its value. Real-world constraints are helpful: they force priorities. A project with a small budget and a short timeline becomes an excellent test for what’s essential.

The final, important point from experience: simplify in public, not in secrecy. When teams are part of the pruning process when they help decide what stays and what goes you get buy-in and better outcomes. People worry their important work will be discarded; co-design the simplification so the system retains legitimacy. That’s how you turn common sense into durable practice.