INSIGHTS / CREATIVE WEB PILOT

How to plan a website before design begins

A practical perspective from CreativeWebPilot on planning and improving digital experiences.

Digital decisions become easier when the starting point is clear. This article explores practical considerations that can be applied during planning, redesign or ongoing improvement.

Start with the business question

Before discussing layouts, fonts or platform choices, define what the website needs to accomplish. A useful starting point is not simply that a business needs a new website, but a more specific description of the change the business wants to create. Perhaps prospective clients do not understand the service quickly enough. Perhaps enquiries are coming from the wrong audience. Perhaps the existing site has grown over several years and no longer presents the business in a coherent way.

Writing the problem in plain language gives the project a reference point. Design decisions can later be tested against that problem instead of being evaluated only by personal preference. A clear problem statement also makes it easier to decide what information deserves priority and which features are genuinely necessary.

Understand the audience and their questions

A website serves people at different stages of familiarity. Some visitors already know the business and need practical information. Others are comparing alternatives or trying to understand whether a service is relevant to their situation. Planning should identify the questions a visitor is likely to have and decide where those questions are answered.

This exercise often reveals that the best structure is not simply a list of internal departments or services. It is a sequence of information that helps an outside visitor understand context, value and the next action. The more accurately the likely questions are understood, the easier it becomes to create useful page hierarchy.

Define the primary actions

Every page does not need to push the same conversion. A visitor reading an in-depth article may reasonably continue to another article, while a visitor on a service page may be ready to request a conversation. Planning primary and secondary actions helps prevent the website from becoming a collection of competing buttons.

The important question is what the visitor should be able to do after understanding the information on that page. When this is clear, calls to action can feel like a natural continuation of the page rather than an interruption.

Build the information architecture

Once priorities and visitor needs are clearer, pages can be grouped into a simple architecture. Main navigation should represent the most important areas of the website, while supporting information can remain accessible without competing for attention.

A sitemap is not merely a technical requirement. It is a way to test whether the website has a logical story. If two pages repeat the same role, they may need to be combined. If an important decision is difficult to support without a new page, that gap becomes visible before design begins.

Plan content before polishing visuals

Placeholder text can hide structural problems. Real or near-final content reveals whether a section actually communicates something useful. Even when final copy is not available, planning headings, key messages and approximate content length creates a stronger design foundation.

The goal is not to finish every sentence before design. It is to give the design process enough meaningful material to test hierarchy, emphasis and page rhythm. Visual decisions become more reliable when they respond to actual communication needs.

Conclusion

Planning does not slow a website project down. In many cases it prevents expensive changes later by making important questions visible early. A strong plan can still leave room for creative exploration and improvement.

By defining the business question, audience needs, page roles and next actions before visual work begins, the project starts with a stronger foundation and a clearer path toward implementation.