Built to Be Launched

The site isn't embarrassing. At some point, someone put real thought into it. But as we scroll, the quiet signs accumulate. A news section that stopped moving over a year ago. A team page with someone who no longer works there. An event listed as "upcoming" that happened before the pandemic.

Nothing is broken. But something is wrong.

The conversation turns, as it always does, to how the new site would be managed going forward. The answer comes back tentatively. There's one person who handles updates. She's stretched across three other responsibilities. She's never really been trained on the CMS and usually contacts the previous agency when something needs changing.

In that moment, I'm not looking at a neglected website anymore. I'm looking at a website that was never built to be maintained. It was built to be launched.

The static digital brochure

The static digital brochure is what a website becomes when the conditions for keeping it alive were never created. The design is finished, but the system isn't.

It's not a criticism of the people involved. The client wanted a great website and got one. The agency delivered what was scoped. But somewhere between handover and today, the site quietly stopped being a living thing.

The problem isn't neglect. The question that was never asked, at the right moment and with the right seriousness, is: who will keep this alive, and do they have what they need to do it?

That question isn't just operational. It turns out to be the most important design question of all.

Trust has a timeline

A potential donor lands on the homepage for the first time. The design is considered, the message is clear, the photography is warm and specific. Trust begins. First impression earned.

They come back three weeks later after receiving an email. They want to check something: a programme, a date, a name. They find the page. It's current. It reflects what they were told. They feel oriented. Return visit earned.

Six months later, they're deciding whether to make a significant contribution. They go back to the site. The latest news is from last month. There's a new case study they hadn't seen. The team page reflects the person they spoke to on the phone. The organisation feels tended to, like someone is home.

That's where trust lives: not in the first impression, but in the accumulated evidence that this organisation tends to things. That it is what it says it is, consistently, over time.

The design earns the first impression. The content earns the return visit. The maintenance earns the trust.

Design still matters

Let's be clear about something. Design matters. A site that looks dated or inconsistent signals something before a single word is read. For a nonprofit or educational institution, where credibility is currency, that signal is expensive.

Visual coherence tells a visitor that someone is paying attention. The design earns the right to be read. Without it, nothing else gets the chance.

But design is a moment. Trust is not a moment.

Assembly as intention

The way a website is assembled already contains a prediction about whether it will be maintained.

A CMS that only a developer can navigate is a brochure waiting to happen. A training session that lasts an hour and never repeats is a system that will drift. These aren't failures of will. They're failures of design: designing without accounting for the people who will live in the system long after launch.

This is where agencies and developers carry real responsibility. The decisions made during a build, what platform, how the editor experience is structured, what the handover actually includes, are trust decisions. They determine whether the client has a fighting chance of keeping the site alive.

An editor with a CMS that respects their capacity and makes sense on first encounter will use it. Build a site only an expert can maintain, and you've quietly decided the site will drift.

The question worth asking

Whether you're deciding what your website should do, deciding what to build it in, or deciding what to deliver to a client, the question underneath all of it is the same:

Is this being built to be maintained, or just to be launched?

The design earns the first impression. The content earns the return visit. The maintenance earns the trust.

All three matter. Only one of them lasts.