There Was an Idea

In 1948, mathematician Norbert Wiener published a book that changed how we understand systems.

He called it Cybernetics.

The core idea: any system that reacts to the results of its own actions lives in a feedback loop. It receives information about what happened. And adjusts its behavior based on that information.

Two types of loops.

Reinforcing loop. The result amplifies the next cycle. The system accelerates.

Balancing loop. The result slows the next cycle. The system decelerates.

Wiener was writing about guided missiles and the nervous system. But loops work anywhere there's action and a reaction to it. In biology. In economics. In products.

"The thought and the action, the message and the correction, and then the message again — this is the rhythm of all goal-directed behavior." — Norbert Wiener, Cybernetics, 1948

A Reinforcing Loop Is Not Luck

Some products grow almost on their own. A user arrives, stays, comes back, brings someone else.

The founder looks at this and thinks: good product-market fit. Good timing. Got lucky.

Sometimes that's true. Usually it's not.

A reinforcing loop doesn't appear by accident. It gets built into the architecture of the product before the first user ever sees it.

The first screen decides whether someone stays for the next thirty seconds. Onboarding decides whether they reach the moment when the product becomes useful.

The first action inside the product decides whether they come back tomorrow.

These are the points where the loop either starts or breaks.

A founder who understands this designs the moment of return deliberately. A founder who doesn't just hopes the user comes back on their own.

Hope is not architecture.

A Balancing Loop Is What Happens When You Treat the Symptom

Metrics drop. Users leave after the first week. Conversions don't move.

The first instinct: add something. A new feature. Another page explaining how it works.

An onboarding flow with five steps instead of two.

The product gets more complex. A new user arrives and doesn't know where to start. Leaves faster than before.

Metrics drop harder. More gets added.

This is a balancing loop. It closed against you. Every action that was supposed to help is making the problem worse.

The issue isn't the features. The founder was treating the symptom without seeing the structure. Churn is not the cause, it's the signal.

Somewhere earlier the loop went the wrong way.

Adding doesn't fix the structure. It buries it deeper.

Where the Loop Gets Built

A designer enters the product before anyone else. Before the user. Before the investor. Before the first public demo.

And that's exactly when the loop gets built.

How the first screen looks is not an aesthetic question. It's a question about what action the user will take in the first thirty seconds and whether they'll want to take the next one.

How onboarding is structured is not a question of how many steps there are. It's a question of whether the person makes it to the moment when the product becomes something they need.

Before that moment they're not your user yet. They're just looking.

How navigation is organized is not a question of convenience.

It's a question of where the user goes when they don't know what to do next.

Design is not a visual layer on top of the product.

Design is the architecture of behavior. And the loop starts here.

The Loop Is Already Running

Every product is already running on some kind of loop.

Not because the founder designed one. But because users always react to what they see.

They stay or leave. Come back or don't. Recommend or say nothing.

That's the loop. It already exists. The only question is whether it's working for you.

A reinforcing loop isn't built after launch. It's built before. Into the architecture.

Into the logic of the first interaction. Into what the user does in the first few minutes and whether they want to do it again.

If that wasn't there from the start, adding features won't change the direction of the loop. It will only accelerate whatever is already happening.

The loop either works for you or against you.

There is no third option.