Build the website around customer questions – not the organisational chart
A practical method for making your company website easier to understand, navigate and take action on – by organising content around customers’ decisions.
Category: Web Design and UX
Many corporate websites reflect how the business is organised. Each department gets its own menu item, internal terminology becomes page titles, and content is allocated according to who owns it. The result may be orderly internally, but challenging for the customer.
Customers rarely visit to explore your organisational chart. They want to know whether you can solve a specific problem, whether the solution is right for them, why they should trust you, and what they should do next. A good website structure follows this line of thought.
The work is therefore not just about moving menu items around. Structure, navigation, typography, visual identity, accessibility and conversion must all support the same user journey. Here is a practical method for making that happen.
Start with the questions customers are actually trying to answer
Before discussing design, you should identify the questions the website needs to answer. Start with real conversations from sales, customer service and project management. What questions do potential customers ask before requesting a meeting or a proposal?
For many business purchases, the questions follow roughly this order:
- Do you offer what I need?
- Do you understand my situation or industry?
- How do you work?
- What do I get, and what terms apply?
- Do you have relevant experience?
- What is the next step?
The order will vary. An accounting customer may be concerned with system support and switching from a previous provider. A contractor may prioritise capacity, geographical coverage and proven experience. The point is to identify the decision-making questions that matter to your customers.
Write each question on a separate note. Then link existing pages to the questions. Pages that do not answer a clear customer question should be assessed critically. They may be necessary, but they do not necessarily need to appear in the main menu.
Turn the questions into a clear information structure
Once the questions are known, you can group content around the customer’s tasks. This often results in a different structure from the internal departmental organisation.
For example, a company that provides consulting, software and training does not necessarily need to present these through the names of three internal teams. Customers may benefit more from entry points that describe their needs: streamline workflows, gain better management information or train employees.
A useful structure usually has three levels:
- Orientation: What does the business offer, and who is it relevant to?
- Evaluation: How does the delivery work, what distinguishes it from the alternatives, and what experience does the company have?
- Action: How does the customer get in touch, place an order, search or move forward?
Do not force everything into the main menu. Legal information, press content, job openings and detailed resources can be important without being among the first choices a potential customer needs.
Write navigation for people who do not know your internal terminology
Menu items should be short, concrete and understandable without explanation. An internal term may feel precise to employees, but unclear to the customer.
Test each navigation term with three questions:
- Can a new visitor predict what they will find behind the term?
- Is the term clearly distinct from the other menu items?
- Do customers use this term when describing their needs?
Be particularly cautious with broad terms such as solutions, expertise and services. They can work, but only if the content behind them is clearly defined. If products, consulting and customer support are all placed under solutions, the customer has to guess.
The same clarity should be present in local navigation elements. On a service page, relevant next choices might include approach, pricing and terms, customer stories or contact. These entry points help the user move forward without having to return to the main menu.
Use typography to show the order of the answers
A good structure is of little use if all elements appear equally important. Typography should make the content hierarchy visible before the text is read.
Each page should have one clear main heading that describes its content. Subheadings should break the decision down into understandable parts, not merely decorate the page. A heading such as How we manage the transition provides more information than Our process.
Body text should have sufficient size, line spacing and contrast. Long lines make it harder to find the next line, while very short lines create unnecessary interruptions. Choose a comfortable text width and test it on both small and large screens.
Limit the number of typographic treatments. If the page uses many font sizes, colours, capitals and emphases, it becomes difficult to understand what is actually important. A simple system with clear levels is easier to maintain and more predictable for the reader.
Let the visual identity support the task
Visual identity online is about more than the logo, colours and typeface. It is also expressed through spacing, imagery, icons, buttons, cards and the way content is prioritised.
The company’s distinctive character should be visible, but it should not compete with the user’s task. Large decorative elements, animations and unusual page layouts can add character, but they should not obscure what the business offers or how the customer should proceed.
Define a few practical rules for the identity:
- What color is used for primary actions?
- What do clickable elements look like?
- What type of images present the business credibly?
- How much space should separate different content sections?
- How can the logo, brand colors and typography be used without compromising readability?
Consistent use is more important than having many variations. When buttons, links and content cards behave consistently across the website, customers do not have to learn the interface again on every page.
Build accessibility into the structure
Accessibility should not be treated as a check that comes after the design is complete. Many of the most important decisions are made while the structure and visual direction are being determined.
A logical heading hierarchy makes the page easier to navigate with assistive technologies and easier to scan visually. Clear link text tells users where a link leads. Good contrast makes text and controls readable. Visible keyboard focus shows users where they are without a mouse.
Also make sure that information is not conveyed through color alone. An error message in a form should have both a visual indicator and specific text explaining what needs to be corrected. Required fields must be clearly marked, and instructions should appear next to the field where they are needed.
Accessible solutions are often easier to use for customers who are using their phone in bright light, have a temporary impairment or are simply trying to complete a task quickly.
Connect each page to a natural next step
Conversion does not mean that every page should push the same contact action. The next step must match how far the customer has progressed in their consideration.
On an overarching service page, the next step might be to choose a relevant service or industry. On a detailed solution page, it might be to read a customer story, see how the delivery is carried out or schedule an introductory conversation. On the contact page, the task is to make the enquiry itself feel safe and easy.
A good call to action describes what will happen. Request an assessment or Schedule an introductory conversation is clearer than Send or Click here. Consider adding brief information about what the customer should prepare, who will respond and what the conversation will clarify.
Avoid multiple visually similar primary actions in the same section. If booking, downloading, subscribing to a newsletter and contacting you compete for attention, the priority becomes unclear. Choose one primary action and present secondary options more subtly.
Test the structure with tasks, not opinions
You do not need to wait for a finished website to find out whether the structure works. Create a simple overview of pages and menu items, and give several people specific tasks.
For example, ask them to find out whether the business can provide a particular service, how a collaboration begins or whom they should contact. Do not help them along the way. Observe which words they look for, where they hesitate and whether they go back several times.
Then test a simple page prototype. Can participants quickly explain what the page is about? Do they see the most important action? Do they understand the difference between the options? Can they complete the form using a keyboard?
Feedback should be linked to the task. The fact that someone likes a color says little about whether the website works. If they cannot find the right service, misunderstand a heading or overlook the contact button, that points to something that can be improved.
A structure that can be managed over time
The website will change as the business gains new services, markets and employees. The structure should therefore be based on clear principles, rather than being a one-off result.
Before a new page is created, the content owner should be able to answer which customer question the page solves, where it belongs and what next step it should lead to. If this is unclear, it is often better to improve an existing page than to add yet another menu item.
When the website follows the customer's questions, design choices become easier to justify. The navigation reflects the tasks, the typography shows the hierarchy, the identity creates recognition, accessibility removes barriers and conversion points help the customer move forward. The website then functions as a cohesive tool, not as a collection of pages owned by separate departments.
