Why fixing the surface never fixes the problem

We've all done this. Changed the room, not what was actually wrong. New notebook, when the real issue was we'd stopped opening the old one. New gym plan, when the real issue was we hated mornings. New relationship, same pattern from the last one, just wearing a different name.

Design thinking has a word for this. Cosmetic solution—you fix what's visible and leave the actual cause standing exactly where it was.

A college notices attendance dropping and redesigns the lecture hall. New chairs, better lighting, fresh paint. Attendance doesn't move. The room was never the problem. The lectures just weren't worth showing up for.

A food app gets complaints about slow delivery. The team redesigns the interface—new colours, smoother animation, a cleaner layout. People are still annoyed. The app looks great. The food still takes forty minutes. We're good at changing what people can see. We're a lot worse at looking at what's actually underneath it.

That's not laziness, it's just easier. A new coat of paint is something you can point out by Friday. Root cause work doesn't show results that fast, so we default to the version that looks like progress.

There's an old story that goes something like this. A rat is terrified of a cat, so it prays to become a cat. Then the cat is scared of a dog, so it becomes a dog. The dog is scared of people, so it becomes a human. And the human, it turns out, is scared of everything—the rat, the cat, the dog, other people, the dark, its own future, et al. Four bodies. Same fear, wearing a new outfit each time.

That's the whole point of a cosmetic fix. You can change the form as many times as you want. If nobody deals with what's actually running underneath, it just follows you into the next version.

Five whys

Toyota's founder, Sakichi Toyoda, built a method around exactly this problem: ask why five times before you stop.

A student keeps missing deadlines. Why? He starts too late. Why? He waits until he feels ready. Why? He's waiting to feel confident. Why? He's scared the work won't be good enough. Why? His worth feels tied to whether the work is perfect.

Nobody solves that with a better planner. The complaint was about time. The actual issue is about fear and self-worth. Most of us stop at why two or three, because why four and five usually point somewhere we'd rather not look.

The part that's actually hard

Design thinking calls this deep empathy, and it's the step everyone skips, because it doesn't produce anything you can screenshot. A new logo is visible by tomorrow. Understanding what someone is actually dealing with takes longer, and for a while it looks like nothing's happening, right up until it changes everything.

In the Gita, Lord Krishna doesn't tell Arjuna to change his armour or his position on the battlefield. He goes straight at the confusion underneath: who Arjuna thinks he is, what this moment actually means to him. Once that shifts, the decision in front of him becomes possible in a way it wasn't before.

We do this constantly without noticing. New city, same loneliness. New relationship, same fight, different name. New career, same self-doubt in a different office. We keep updating the interface and wondering why nothing feels different.

The question worth sitting with isn't what needs to change on the outside. It's what's actually going on underneath this. That second question is slower, less satisfying, and it's the only one that actually holds.

The rat had whatever it had inside it the whole time. It never needed a new body. It needed a new answer to one question: What am I still running from?

Change the conviction. The form sorts itself out.

Keep unfolding.