A Design Review for the Mind

For almost two years, something has been bothering me.

Life is good. There is nothing dramatic to report. Yet something feels unresolved, and it keeps returning.

It is not a crisis.

It is a problem of method. I have been examining a thought as if the thought were the fault, and not examining the system that keeps producing the thought.

It is more like a room I keep entering and leaving, never quite sure why I went in. Every time I think I have understood it, another thought appears from a different corner.

Day after day.
Thought after thought.

I examine it.
Question it.
Turn it around.
Try to understand it.
Let it go.

It returns wearing another costume.

No awakening.
No grand insight.

Just the strange experience of being stuck inside an investigation that refuses to produce a conclusion.

Every thought eventually fails my own analysis.

Perhaps that is the problem.
Perhaps I have become too good at examining the thought and not good enough at questioning the system that keeps producing it.

Then, one morning, three unrelated things met on an iPad.

A discussion titled “Advancing Resilient Design Through Criticism.”
A Japanese proverb about getting off the wrong train.
And Śaṅkara’s opening word: mūḍhamate.

They did not give me an answer.
They gave the investigation a load test.

---

We like designs that agree with us

Think about how we normally design things.

We draw something.
We explain it.
People look at it.

“Looks good.”
“Beautiful.”
“Interesting.”
“Let’s build it.”

The idea survives.
Everyone is happy.
And the idea may still be completely wrong.

Nobody asks where it fails.
Nobody questions the dimensions.
Nobody tests the assumptions.
Nobody asks what happens when reality behaves differently from the model.
Nobody tries to break it.

We often mistake agreement for validation.

They are not the same thing.

Agreement tells us that people agreed.
Testing tells us whether the thing works.

A resilient design needs the second.

---

The value of friction

I have been designing a house.

Not merely rooms on a plan, but the relationships between them. Dimensions. Orientation. Circulation. Privacy. Structure. Light. Ventilation. Furniture. Future use.

The temptation is always to make the drawing look finished.

But every time we thought we had something right, another question appeared.

Does the geometry actually reconcile?
Can someone move through this space naturally?
Does the furniture fit without compromising circulation?
Does the bathroom belong there?
What happens to the structure if the design changes?
What happens ten years later?

And sometimes the answer was uncomfortable:

This doesn’t work.

Good.

That is exactly what we wanted to discover.

A contradiction found in a conversation is cheap.
A contradiction found after construction is expensive.

The drawing has failed.
The design has learned.

That is the difference.

This is why I like the familiar engineering idea of fail fast, with one modification:

Fail while failure is still cheap.

Fail in the sketch.
Fail in the simulation.
Fail in the conversation.
Fail in the design review.

Fail before concrete.
Fail before production.
Fail before the customer.
Fail before reality becomes your reviewer.

Because reality is a brutally expensive reviewer.

It doesn’t care how much time you spent defending the original idea.
It doesn’t care how beautiful the presentation was.
It doesn’t care how many people approved it.

Reality simply asks: does it work?

And if the answer is no, you pay.

This makes the critic strangely valuable.

The person who says wait, why, what if, show me, let’s try to break it can be irritating. They can slow the meeting down. They can puncture enthusiasm. They can become unpopular.

They may be the person saving the project.

A good critic isn’t trying to kill the design.
They are trying to kill the weakness inside the design.

The objective isn’t: destroy the idea.
It is: destroy what is fragile about the idea. Then rebuild. Stronger.

But what if nobody criticizes you?

What if everyone is polite, distracted, inexperienced, afraid, or simply waiting for someone else to speak?

Then the responsibility returns to the designer.

You have to become your own critic.

---

The internal design review

Self-criticism sounds unpleasant. It shouldn’t.

There is a difference between self-criticism and self-destruction.

Self-destruction says: everything is wrong with me.
Self-criticism asks: what have I missed?

Self-destruction searches for reasons to reject.
Self-criticism searches for reasons to improve.

Self-destruction attacks the designer.
Self-criticism tests the design.

The internal critic should not be a voice of punishment.
It should be a design-review mechanism.

Two questions are usually enough:

What am I protecting from examination?
What would I see if I were trying to disprove this instead of defending it?

And the more uncomfortable one underneath both:

What if the problem isn’t the answer?
What if the question itself needs a design review?

Fail fast becomes fail early, fail cheaply, learn deeply.
Which becomes: invite criticism before reality supplies it.
Which becomes: learn to criticize your own design before you become attached to defending it.

That is not pessimism.
It is a way of becoming difficult to surprise.

The goal is not to expect failure everywhere.
It is to discover the failure while it is still useful information.

---

The wrong train

Somewhere in the same trail of reading, a Japanese proverb appeared:

If you board the wrong train, get off at the next station. The longer you stay on it, the more expensive the journey becomes.

It was almost annoyingly simple.

But I was already thinking about design. About failure. About assumptions. About the cost of discovering mistakes late.

Suddenly the proverb wasn’t about trains.

It was about trajectory.

You don’t always need to know the entire route.
Sometimes you only need to recognize that the current direction deserves another look.

Criticism serves the same purpose.

It doesn’t always tell you the correct destination.
It tells you: check the direction.

---

Then Śaṅkara appeared

On the same iPad, the morning Bhaja Govindam playlist began.

Bhaja Govindam, bhaja Govindam,
Govindam bhaja mūḍhamate.

One word stopped me.

Mūḍhamate.

Mūḍha points toward bewilderment, delusion, confused understanding.
Mati is mind, understanding, discernment.

So this is not simply: hey, stupid.

It is an interruption.
A challenge to misdirected understanding.

You can possess enormous amounts of information and still fail to see what matters.
You can know the rules and miss the game.
You can have the blueprint and miss the building.
You can have the data and miss the truth.
You can be highly intelligent and still have a blind spot.

That is the mūḍha-mati problem.

Śaṅkara’s opening did not feel particularly ancient.
It felt uncomfortably current.

---

The distracted mind can look productive

The distractions change. The mechanism doesn’t change very much.

We have become extraordinarily efficient at manufacturing distraction. The phone in your pocket doesn’t merely contain distractions. Distraction has learned your preferences. It knows what makes you angry, anxious, comparative, restless, and willing to return.

The distracted mind doesn’t necessarily look foolish.
It can look extraordinarily productive.

That may be the most dangerous version.

Because you can spend years doing things without examining the direction in which all that doing is taking you.

Mūḍhamate is not: you don’t know enough.
It is: are you examining the mind that is deciding where to look?

---

The designer is inside the building

When we design a system, we can usually step outside it. We can test it, measure it, break it, observe it.

When we design our own lives, we are simultaneously the architect, the user, the investor, the salesperson, and the reviewer.

That is terrible governance.

We are reviewing our own architecture.
Of course we miss things.
We are inside the building.

Being inside the building doesn’t make self-review impossible.
It simply makes it harder.

We can notice which questions make us defensive.
We can compare stated values with actual behaviour.
We can look for the gap between what we believe and what repeatedly happens.

The two-year itch I started with belongs here.

Not: what is the correct thought?
But: what if the method of examination is the thing that keeps reproducing the same room?

---

The sajjanan

Another Sanskrit word enters here.

Sajjanan.

A good, virtuous, noble, or worthy person.

In human relationships, the more interesting meaning is this:

The sajjanan is not necessarily the person who makes you feel good.
They may be the person who makes you see better.

A flatterer protects your feelings.
A controller protects their authority.
A sajjanan protects your welfare.

Sometimes protecting your welfare means telling you something you don’t want to hear.

Not: do what I say.
But: this is what I see. Now you decide.

That is criticism without control.
Care without possession.
Truth without coercion.

The sajjanan doesn’t think for you.
They help you think more clearly.

They don’t take away your judgment.
They strengthen it.

They don’t need you to agree with them.
They need you to look.

There is a temptation to romanticize this figure. To imagine that somewhere out there is a wise person who will finally tell us what we need to know.

That would be another form of dependency.

The sajjanan can point.
They cannot see on your behalf.

A friend can identify the blind spot. You still have to examine it.
A teacher can challenge your understanding. You still have to understand.
A critic can break your design. You still have to rebuild it.

External criticism is valuable.
Internal criticism is essential.

The first gives you another perspective.
The second gives you independence.

---

The design review for the mind

A resilient design doesn’t assume it is correct.
It assumes it can be tested.

A resilient mind doesn’t assume it is enlightened.
It assumes it can be deluded.

That isn’t weakness.
It is intellectual humility with engineering discipline.

The useful question is not: what would prove me right?
It is: what would prove me wrong?

And the harder one:

What if I am protecting the very assumption I need to examine?

Those questions create room for correction.
And correction is cheapest before consequences become irreversible.

Don’t wait for the crack to widen. Look for the hairline fracture.
Don’t wait for the system to collapse. Test the load.
Don’t wait for someone to point. Look.

---

Mūḍhamate

That is what I hear differently in Śaṅkara’s opening now.

Mūḍhamate is not merely an insult.
It is an interruption.
A tap on the shoulder.
A design review for the mind.

Stop.
Look again.
You may be missing something.

The person who gives us that interruption is not our enemy.
They may be the person most invested in our ability to continue the journey. Not for them. For us.

But the deeper instruction is more demanding:

Do not wait for the interruption.
Interrupt yourself.

Stop before someone has to stop you.
Question the assumption before the consequence exposes it.
Look for the weakness before the world finds it.
Ask the question before the crisis asks it for you.

The mūḍhamate is not only the person who needs correction.
It is the person who has forgotten to examine their own understanding.

The sajjanan is not merely the person who corrects them.
The sajjanan is the person who helps them recover the ability to see.

That morning, three unrelated things met on an iPad.

They did not solve the problem I have been carrying for two years.
They did not give me an awakening.

They gave me a better question.

What if the thing that needs redesigning is not the world around me, and not even the thought I keep returning to, but the way I am examining both?

That is the review I had been postponing.