Hella Creative / Thinking

Before You Decide What to Build, Decide What Needs to Change

·

A new website, app or AI tool is a starting point, not a brief. Five questions to answer first, and how to choose the change that actually matters.

Most projects start the same way. Someone in the business says they need a new website, an app or an AI tool. The request arrives with momentum, a rough budget and a quiet deadline, and the temptation is to treat it as the brief.

It is not the brief. It is a starting point.

The request tells you what someone has already decided to build. It rarely tells you what is actually broken. Until you know that, every hour and every dollar you spend is a guess dressed up as a plan.

A request is a symptom, not a diagnosis

A new website is a solution. An app is a solution. An AI tool is a solution. Each one assumes a problem, and that assumption is rarely examined.

When the assumption is wrong, the build succeeds technically and fails commercially. You ship on time. The thing works. Nothing in the business changes.

The useful work happens before anyone opens a design file. It starts with five questions.

Five questions to answer before you build anything

None of these require a large budget. They require a willingness to slow down for a few days and look honestly at what is going on.

What is happening in the business that prompted the request?

Start with the trigger. Sales slowed. A competitor moved. A team is drowning in manual work. A process breaks every month and someone has quietly stopped complaining about it. The request usually points at the symptom. The trigger points at the cause.

Who is struggling, and what are they trying to accomplish?

Name the people. Customers, staff, partners, whoever the work touches. Then describe what they are trying to do at the exact moment things go wrong. Not who they are in a demographic sense, but what they are attempting and where the attempt fails.

What evidence do we have about the problem?

Opinions are plentiful and cheap. Evidence is scarcer and far more useful. Look for support tickets, sales call recordings, analytics, drop-off points, error logs and staff interviews. If the strongest evidence you have is a feeling in the room, that is worth knowing too.

What would a meaningful improvement look like?

Not a feature list. An outcome. Fewer support requests. Shorter onboarding. More qualified inquiries. A process that stops depending on one person. If you cannot describe the improvement in plain business terms, you have not defined the problem well enough to solve it.

Which changes would make the greatest difference?

Rank the options by impact, effort and confidence. The goal is not the most ambitious idea. It is the change that moves the outcome the most for the least risk. Often that is smaller and less exciting than the request on the table.

A short example: more inquiries, wrong conclusion

A business comes wanting more inquiries. The obvious answer is more traffic, and the obvious build is a larger website with more pages and more content to attract it.

Then we look. Traffic is not the problem. Visitors arrive and cannot tell what the business sells, who it is for or what happens next. The offer is buried three clicks deep. The services read like a list of capabilities rather than a reason to choose this firm. Prospects leave without doing anything.

That finding changes the strategy. A bigger site would have amplified a message that was not working. The real work was a clearer offer, sharper service descriptions and a single next step a stranger could follow.

The website still mattered. It stopped being the lead item. The investment moved to the places that actually shaped the outcome.

Understand the business, understand the people, then choose

The order is the method. Understand the business. Understand the people. Then choose the intervention.

Sometimes that intervention is a website. Sometimes it is a clearer offer, a different service experience or a better internal process. Sometimes it is an AI tool that removes a step no one should be doing by hand. A website might be part of the answer. It is rarely the whole answer.

This is the difference between judgement and enthusiasm. Judgement means you investigate before you commit. It means you are willing to tell a client that the thing they asked for is not the thing they need, and to show the reasoning behind it. Hella works this way on purpose. Research and strategic direction come first, and the build comes after, sized to the change it is meant to create.

Something needs to change, but you are not sure where to begin

Bring the situation to a discovery session. We will explore what is happening, what matters and where to focus next. You will leave with a clearer read on the problem and a grounded view of what deserves your investment, whether that turns out to be a build at all.

The most valuable thing you can do before deciding what to build is decide what needs to change. Get that right and the rest gets simpler.