Why Babies’ Brains Can Teach Us Something About Project Management

It’s a poetic way of describing how the human brain develops.

At birth, the brain contains an extraordinary number of neurons — far more than it will eventually use.

At first glance, this seems like an advantage. More neurons should mean more capability.

Yet anyone who has watched a baby knows that abundance does not immediately translate into coordination. A baby’s hand may miss its mouth and land on its forehead instead.

Why?

Because the brain is designed to learn through selection.

During early childhood, neural connections are constantly reinforced or eliminated. Connections that are frequently used become faster and stronger. Those that are not used gradually disappear.

Neuroscientists call this process synaptic pruning. The brain does not become efficient by adding complexity. It becomes efficient by removing it.

Less noise. Stronger pathways.

When More Options Make Things Harder

Something similar happens in project management.

Many project tools promise flexibility through abundance:

• More features.

• More parameters.

• More configuration options.

At first glance, this feels powerful. But in practice, the opposite often happens. Each new parameter creates a decision. Each decision increases cognitive load.

Instead of helping teams move faster, the system quietly slows them down.

The tool becomes impressive. But harder to use.

A Personal Lesson

A few years ago, I discovered a project management tool built around Critical Chain principles.

On paper, it seemed perfect.

Highly configurable. Extremely flexible. Full of possibilities.

At first, I was excited.

But the more I explored the system, the clearer something became: There were simply too many choices. What started as enthusiasm slowly turned into hesitation.

The tool was powerful — but too complex to be practical in everyday work.

That experience taught me something simple: More options do not necessarily lead to better decisions.

Very often, the opposite is true.

Why Simpler Systems Work Better

Decision quality improves when a system reduces unnecessary choices.

This idea became central when designing KairoProject.

Instead of adding more features, the goal was to remove as many parameters as possible while preserving what truly matters.

Two principles guided that approach.

First: reduce cognitive load by limiting the number of inputs required to structure a project.

Second: reduce decision fatigue by automating repetitive elements whenever possible.

For example, recurring tasks can rely on predefined durations. This allows a project to be created quickly without estimating everything from scratch.

The goal is not to oversimplify reality.

Projects remain complex systems.

But the interface through which we interact with that complexity does not need to be.

Complexity Exists — But It Should Be Hidden

A good system does not remove complexity from the world.

It removes complexity from the decisions you have to make every day.

Just as the brain becomes more efficient by pruning unused connections, a project system becomes more usable when unnecessary choices disappear.

Sometimes the most powerful design decision is not what we add.

It is what we remove.

What to Take Away

When managing projects, complexity rarely comes from the work itself.

It often comes from the number of decisions we force ourselves to make.

A well-designed project system should therefore aim to:

• reduce unnecessary parameters

• minimize repetitive decisions

• make the important choices easier to see

Because clarity is not created by adding more options.

It is created by removing the ones that do not matter.

— Matthieu