Start with the visitor’s goal
Website planning often begins with a list of pages: Home, About, Services, Contact. Those pages may all be necessary, but the list does not explain whether someone can accomplish what brought them to the site. A visitor might need to check whether a service is available in their area, compare two options, find an event location or ask a question. Each is a task with a useful outcome.
Write tasks from the visitor’s point of view, using specific verbs. “Find the price of a workshop” is easier to plan for than “learn about us.” Keep the organization’s goal separate: you may want more enquiries, while a visitor may first need to understand what the service includes. Supporting that earlier task can make the later action easier without forcing every page to act like a sales pitch.
Choose a manageable set of tasks
You do not need to map every possible visit at once. Start with five to ten tasks that matter to your audience and that the website can realistically support. Look at questions people already send by email, ask on calls or bring to appointments. If the site exists, note where its content answers those questions and where staff still have to fill in the gaps. Treat these observations as clues, not proof that every visitor behaves the same way.
Include tasks for people at different stages. A first-time visitor may need to understand what you offer; a returning visitor may simply need opening hours or a document. Consider people who arrive on a specific page from a search result rather than through the home page. If several audiences use the site, label the tasks by audience only where their needs genuinely differ.
Draw the path and identify what is missing
For each task, record a likely starting point, the information needed, the action to take and what a successful finish looks like. This can be a short line on paper or a simple table. For example: “Find out whether a workshop is suitable → read its description and requirements → check the schedule → request a place → receive confirmation.” The point is not to predict every click. It is to reveal the decisions a visitor must make.
Now walk through that path on the website. Can someone recognize the right link from its label? Does the page answer the question before asking them to fill out a form? Are essential details, such as eligibility or what happens next, available at the point where they are needed? Mark steps that depend on guesswork, repeated searching or contacting you for information that could be published. Those marks become a practical improvement list.
Make each step clear and usable
A task map can guide both content and navigation. Put important answers where visitors expect to find them, and use link text that names the destination or action. If a task requires several pages, give people a clear route forward and an easy way to go back. Related details should agree across pages; conflicting hours, prices or instructions can stop a task even when the navigation works.
Check the path under ordinary constraints, not just on a large screen with a mouse. Can a person read it on a phone, move through links and forms with a keyboard, understand headings out of context and tell which fields are required? An accessible route is part of task completion, not a separate finishing touch. If the last step happens offline, explain how to do it and what response, if any, the visitor should expect.
Use the map to plan small improvements
Choose one or two high-priority tasks for the next round of work. Fix missing information and misleading labels before adding new features. Ask someone unfamiliar with the site to attempt a task without guidance, then listen to what they expected at each step. You can also review relevant enquiries and site measurements, if available, to see where further checks might be useful. No single test or number tells the whole story.
Keep the map as a working document. When a service changes, a form is replaced or a common question appears, revisit the affected task and its pages. Give each task an owner who can check that its key details remain accurate. A short, maintained list of visitor goals is often more useful than a detailed plan that no one returns to: it gives a small team a shared way to decide what the website should help people do next.
