TR EN

Insights

Why we think in products, not projects

A project ends. A product keeps being useful, or it stops being a product. The difference changes how you build.

A project has a beginning, a budget and an end date. It is declared finished, handed over, and the team moves on. This is a perfectly good way to build a bridge. It is a risky way to build software.

Software does not finish. The business around it changes, the people using it change, the systems it talks to change. A tool that was exactly right at launch drifts out of true unless someone is responsible for keeping it right. That responsibility is what turns a project into a product.

Three things that change when you think in products

You design for the second year, not only the first demo

A project optimises for the day it is delivered. A product has to be pleasant to maintain, easy to extend and honest about its limits. That affects small choices: how data is structured, how settings are handled, what is automated and what is left visible.

You measure use, not delivery

"Done" is a statement about the team. "Used" is a statement about the world. Products are judged by whether people come back, whether tasks get easier, whether support questions go down. Those are slower signals and far more truthful ones.

You accept ownership

Someone has to answer when it breaks at an inconvenient hour. When ownership is clear, quality improves almost automatically, because the person fixing a problem is often the person who caused it, and learns from it.

A simple test

Ask of anything you are building: who will care about this in eighteen months, and what will they need from us? If the honest answer is that nobody will care, it is probably a project, and it is worth asking whether it should be built at all. If the answer is clear and specific, you are building a product, and you can start behaving like it today.

Let's build something meaningful.