The Iceberg

An iceberg is 90% underwater.

You only see the top. The rest exists, affects everything, but stays out of sight from the surface.

Products work the same way.

Low conversions are the tip. User churn is the tip. "Nobody understands what we do" is the tip.

These are not problems. They are signals that something is wrong deeper down.

How Founders Respond to Signals

Conversions drop, so they change the button. Users leave, so they add a feature. Nobody gets the product, so they write more text on the homepage.

This is a natural reaction. Fix what you can see.

But the button is not why conversions are low. The feature is not why users churn. The text is not why nobody understands.

This is treating the problem at the level of the symptom. The symptom fades. The problem stays. Then it comes back somewhere else.

Where the Real Problem Lives

Almost always deeper than it looks.

Low conversions are usually a positioning problem. The product doesn't clearly say who it's for and why. The user arrives and can't tell if this is for them. They leave.

Churn is usually an onboarding or value problem. The person never reached the moment when the product became useful. They didn't leave because it was bad.

They left because they never understood why to stay.

Product confusion is usually a language problem. The product is described in the language of the person who built it, not the person who's seeing it for the first time.

The founder knows what they built. The user is seeing it fresh.

Different symptoms. One type of cause: a gap between what the product says and what the user hears.

How to Find the Real Problem

Don't guess. Look below the symptom.

Conversions are low — don't change the button. Ask: does the user understand what's being offered in the first five seconds? If not, the problem is communication, not design.

Churn is high — don't add features. Ask: where exactly does the user drop off? What were they supposed to understand at that moment and didn't?

Nobody gets the product — don't write more. Ask: whose language is the site written in? The language of the person who built it or the person who will arrive?

The question is always the same: where exactly does the connection between the product and the user break?

Why This Matters for Design

Design is often treated as the final layer. Product first, design after.

But design is the first thing the user sees. They don't know what's behind it. They see the surface and draw conclusions about what's inside.

That's why design is not decoration. It's translation. From the language of what exists to the language of what the user can actually take in.

And when something isn't working on the surface, the cause is almost always deeper. In the logic. In the positioning. In how the product thinks about itself.

Changing the surface without changing the logic is polishing the iceberg from above.

Everything underneath stays exactly as it was.