An underperforming team. A missed target. A feature that does not land.
The reflex is almost automatic: this is on me. And from there, the conversation shifts. We start justifying, defending, or over-explaining. Not because we are trying to avoid responsibility, but because we have tied the outcome to our own value.

That shift is subtle, but it changes everything.

The hidden cost of ego in performance discussions

When a performance issue becomes a reflection of self-worth, ego enters the conversation.

Instead of focusing on the problem, we focus on ourselves.
We think:

• I should have done better

• I should have worked more

• I should have anticipated this

It sounds responsible. In reality, it is limiting.

Because the problem is no longer external. It becomes internal.
And when that happens, the range of solutions shrinks dramatically.

You end up with simplistic answers to complex problems:

• work harder

• push more

• spend more time

This does not scale. It burns people out. And more importantly, it rarely fixes the actual issue.

Reframing performance as system feedback

There is a more effective way to look at it.

A performance gap is not a judgment. It is a signal.

It tells you that somewhere in the system, something is not working as expected.
Not you as a person. The system around the outcome.

That system can include:

• unclear priorities

• missing context

• poor incentives

• weak processes

• lack of ownership

• technical constraints

• misaligned expectations

When you adopt this perspective, the role shifts.

You are no longer the problem.
You are the person responsible for diagnosing and improving the system.

This is a completely different mindset.

Why this matters for growth

If your default reaction is “how could I have done better”, you will improve, but only incrementally.

You will become faster. Sharper. More experienced.
But you will remain the bottleneck.

Your impact will always be constrained by your personal capacity.

On the other hand, if you treat performance issues as system feedback, you unlock leverage:

• You identify root causes instead of symptoms

• You involve others instead of carrying everything yourself

• You design solutions that scale beyond you

• You improve the environment, not just your output

Over time, this compounds.
And this is where real career growth happens.

A practical shift in behavior

The difference shows up in very concrete ways.

Instead of asking:

• What should I have done better?

You ask:

• What is this situation telling me about the system?

• Where is the gap coming from?

• What assumption is wrong?

• What is missing for this to work properly?

• Who needs to be involved to fix this?

This creates distance from ego, without removing accountability.

You still own the outcome.
But you do not confuse ownership with self-blame.

The bottom line

Working harder is often the most intuitive response to a problem.
It is also the least scalable one.

The real leverage comes from stepping back and understanding why the system produced that outcome in the first place.

Performance problems are not personal failures.
They are signals.

What you do with that signal is what defines your impact.

A few years ago, the idea of the 10x developer was everywhere. Blog posts, conference talks, Twitter debates — the claim was simple: some developers are 10 times more productive than others. Or 100 times. Depending on who you asked.

The idea got a lot of pushback — and rightly so. It was often misused to glorify lone geniuse…

Read more

Ask ten people what it means, and you’ll get ten different answers — most of them a bit off.

Some think it means being average at everything and excellent at nothing. Others …

Read more

It’s inevitable. With scale comes complexity — more people, more teams, more interfaces. And somewhere in that web of new roles and responsibilities, things start slipping through the cracks.

Not…

Read more

It’s not just a clever metaphor — it’s a shift in mindset. And for CTOs, CPOs, and anyone leading product or tech at scale, it’s the only way to succeed.

Read more

We build abstractions “just in case.” We generalize early. We aim for reusability. But too often, that mindset leads us into the exact trap we were trying to avoid: accidental complexity.

Read more

And that changes everything. Let me explain.

Read more

On one side: tight alignment, with top-down direction, clear goals, and centralized decisions.

On the other: autonomy, where teams self-organize, explore, and move independently.

And so they feel forced to choose. Either control and coordination, or chaos and creativity.

But that’s th…

Read more