The Marshmallow Problem: Why Low Ego Teams Win

The Marshmallow Challenge is famous because it exposes something leaders often miss: the best team is not always the most credentialled or articulate. It is usually the team that tests early, adapts quickly, and does not waste energy protecting egos.

Why this matters

In business, most important work looks like a version of the marshmallow challenge. You are given incomplete information, some fragile materials, time pressure, and a goal that sounds simple until reality gets involved.

The organisations that perform best are not the ones that plan the most beautifully in the abstract. They are the ones that expose assumptions early, learn in public, and keep moving without turning every trial into a political contest.

The Unexpected Winners: Why Kindergarteners Beat MBAs

The rules of the challenge are simple: build the tallest free-standing tower possible using spaghetti, tape, string, and a marshmallow that must sit on top.

Again and again, kindergarteners outperform MBA students and many high-status professional groups. At first glance, that seems ridiculous. But the difference is not intelligence. It is behaviour.

Kindergarteners do three things well:

• They start building immediately rather than negotiating status
• They test early rather than waiting for a perfect final reveal
• They treat failure as feedback rather than embarrassment

What adults often call childishness is actually fast, low-ego, iterative learning.

Why Highly Educated Teams Often Struggle

MBA students and professional teams usually begin with planning, role negotiation, discussion, debate, and analysis. They try to create one elegant solution, then place the marshmallow on top near the end. It collapses.

That collapse happens because the real challenge is not theory. It is adaptation. The marshmallow is heavier than expected. The spaghetti bends more than expected. The design needs real-world testing.

Yet many adult teams fall into the same traps:

1. Ego wants to win the discussion.
   People protect their idea rather than testing the best available one.
2. Overconfidence delays learning.
   Teams rely on planning instead of rapid experimentation.
3. Fear of looking wrong kills good iterations.
   Nobody wants a rough first version if they think they are being judged.

This is exactly how strategy decks, innovation projects, and transformation programs fail in the real world.

The Strategic Lesson: Low Ego Is a Competitive Advantage

The teams that move fastest are usually the ones with the least ego friction. They do not confuse confidence with certainty. They do not treat feedback as a threat. They are willing to look unfinished long enough to discover what actually works.

In strategy execution, the biggest failures rarely come from lack of intelligence. They come from:

• Slow decision-making
• Overanalysis
• Political tension
• Leaders trying to be right rather than useful
• Fear of being wrong in public
• One big plan instead of many small learning loops

Low ego is not softness. It is operating maturity.

Why Playfulness Is a Strategic Weapon

Professional environments often treat play as unserious. But in the marshmallow challenge and in real organisations, playfulness is powerful because it reduces fear and increases curiosity.

A playful mindset tends to:

• Reduce internal competition
• Increase willingness to test rough ideas
• Create stronger psychological safety
• Accelerate learning under pressure
• Make shared problem-solving feel safer and faster

This is not about being silly. It is about creating an environment where experimentation feels normal, not dangerous.

Experience Still Matters — But Only When Ego Does Not Suffocate It

Experience absolutely matters. Engineers, for example, often perform well because they are used to prototyping and testing.

The key difference is simple: experience amplifies performance only when ego does not choke experimentation.

When experienced teams stay open, they become extremely powerful because they can:

• Recognise patterns faster
• Communicate more clearly
• Adapt without panicking
• Turn early failure into smarter iteration

But when experience hardens into status protection, it becomes a liability instead.

What This Means for Your Business and Team

The marshmallow challenge is not really about spaghetti. It is about how people behave under pressure when they do not fully control the outcome.

High-performing teams usually share three characteristics:

• Low ego
• High curiosity
• Fast iteration

Those same qualities matter in:

• Strategic planning
• Transformation programs
• Technology implementation
• Process redesign
• Innovation and prototyping
• Cross-functional collaboration

If your team keeps looping in analysis, meetings, or political tension, the marshmallow challenge is probably describing your operating culture more accurately than you think.

Leadership Implications: How to Build Low-Ego, High-Learning Teams

Leaders cannot force people to become smarter overnight. But they can design an environment where low ego and fast learning become normal.

Create a low-ego culture.

• Make it safe to be wrong early
• Reward truth and learning, not volume or title
• Reduce unnecessary status games in meetings and decisions

Push for fast, ugly prototypes.

• The first version should be rough enough to learn from quickly
• Do not wait for polish before testing assumptions

Replace “prove your idea” with “test our idea.”

• Shift from internal competition to shared experimentation
• Make small, low-risk tests a normal part of operating rhythm

Make experimentation habitual.

• Review what was tested, what was learned, and what changes next
• Build short feedback loops into real projects, not just workshops

The Final Insight: Every Project Has a Marshmallow

Every strategic initiative has a hidden risk — the unknown factor that can collapse the beautiful plan. You do not find that risk in the boardroom. You find it in testing.

The fastest learners win. The lowest-ego teams win. The best collaborators win.

When in doubt, build like a kindergartener: move early, test quickly, stay curious, and treat strategy as something you refine through action, not something you perfect in isolation.

From insight to action

Choose one current initiative and ask the team three questions this week: what assumption are we protecting, what would a rough prototype look like, and how can we test it before we spend another month discussing it? That conversation alone can change the speed and quality of execution.

Related reading: 7-Step Strategy Framework That Actually Works and The Marshmallow Problem Insight.