Most organizations approach a website project as a series of decisions that can be revisited if something does not work out. Choose a platform, build the structure, publish the content, and if anything feels wrong, adjust it later.
This assumption is the source of most expensive website problems.
Website decisions do not work like that. They work more like a branching structure, where each choice made early determines what is possible at every stage that follows, and reversing a decision made at the foundation requires undoing significant work that was built on top of it.
When an organization chooses a platform, that choice determines what content structures are possible, what integrations are available, what security posture the site can maintain, and what the maintenance burden will look like for years. A platform chosen because it was familiar or inexpensive rarely announces its limitations at the time of the decision. It announces them when the organization has grown and the platform cannot accommodate what the work now requires.
When an organization builds a navigation structure around its internal departments rather than its visitors’ goals, that choice shapes every content decision that follows. Fixing it later means restructuring content that was organized around the wrong logic – not editing a few pages, but reconsidering the entire information architecture.
When an organization defers content strategy until after the platform and structure are chosen, the content adapts to what has already been built rather than the platform and structure being chosen to support what the content needs to accomplish. The result is a site where the thinking is visible in layers – each decision made reactively to the one before it rather than from a shared understanding of what the site needs to do.
The organizations whose websites consistently support their mission over time are not the ones with the largest budgets. They are the ones that made the foundational decisions: platform, structure, audience, purpose – before any execution began.
That early clarity does not eliminate the complexity of building a good website. It determines whether the complexity compounds or resolves.
The question worth asking before any website project begins is not “what do we want the site to look like?”
It is “what do we need the site to accomplish, for which visitors, in which situations, and what decisions do we need to make first to make that possible?”
That question, answered clearly, determines everything that follows. Skipping it does not save time. It defers the cost of not having answered it.
For museum directors, nonprofit executives, and organizational leaders accountable to boards and funders, the practical implication is straightforward. The most expensive website decisions are not the ones made at launch. They are the ones made without sufficient clarity about what the site needs to accomplish – and discovered, at considerable cost, when the site no longer fits where the organization has gone.
The organizations that treat a website project as a strategic decision rather than a production project consistently get more durable results, spend less over time, and face fewer situations where a site that was recently built already needs to be reconsidered.
You have enough clarity when you can answer three questions specifically: who are the two or three visitors whose confidence matters most to your organization, what does each of them need to accomplish on the site, and what does the site need to communicate that your organization cannot currently say clearly. If those answers are vague, the project will produce a site that looks current but functions generically.
Platform selection made on familiarity or cost rather than fit. A platform that works well for a small organization with simple content needs creates real constraints for an institution managing multiple programs, complex stakeholder relationships, and serious funder accountability. The cost of migrating away from the wrong platform later is significantly higher than choosing correctly at the outset – in staff time, development hours, and the disruption of rebuilding on a new foundation.
Sometimes, and it depends on whether the problems are structural or surface. Content that no longer reflects the organization, language that has drifted from current positioning, and imagery that feels dated are all fixable through ongoing maintenance. A platform that cannot support the organization’s complexity, a navigation structure built around internal assumptions rather than visitor goals, and a content architecture that reflects a different strategic period are structural problems – and they require a more deliberate intervention than incremental updates can resolve.
Frances Naty Go is the founder of Goldlilys Media, where she helps mission-driven organizations turn their websites into clear, durable systems that support meaningful work over time. She works with museums, nonprofits, health and wellness brands, higher education, life sciences, travel organizations, and expert-led businesses.
With a background in Computer Science from UC San Diego, Frances brings a thoughtful, strategic approach to building digital experiences that educate, orient, and build trust, without unnecessary complexity.
Questions first? Start a conversation
