Recommended Free Tools
A website redesign should begin with the task visitors are struggling to complete, not with a fashionable layout, animation, or color palette. A trend can inspire a design idea, but it does not prove that visitors need it. First identify where people encounter friction; then test changes against their ability to reach the outcome they came for.
Why should a redesign start with user problems?
A visual refresh can make a site feel newer without making it easier to use. If visitors cannot find a product, understand a service, complete a form, or get an answer, changing the site’s appearance alone may leave the underlying obstacle untouched.
As an Amazon Associate I earn from qualifying purchases.
The UK Government’s Government Design Principles put the sequence plainly: “Service design starts with identifying user needs.” The principle applies beyond government services: identify the people, tasks, and context first, then choose a design response. A complaint that a site “looks dated” is worth investigating, but it is a hypothesis—not yet evidence of what users need.
What should you research before redesigning?
Audit the evidence you already have
Review analytics, on-site search logs, previous research, and relevant support or service information. Look for signs of where visitors leave a process, search repeatedly, make errors, or ask for help. Treat these signals as clues: analytics can show where behavior changes, but usually cannot explain why.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
List what is known, what remains uncertain, and which user task each question concerns. Stakeholder suggestions can help identify hypotheses, but they should not stand in for visitor evidence. Government Digital Service guidance advises: “Treat any opinions or suggestions that do not come from users as assumptions that have to be proven by doing research.” See Learning about users and their needs.
Talk to and observe people doing real tasks
Interview and observe actual or likely users as they attempt tasks the site exists to support. Ask what they are trying to accomplish, what they expect to happen, and where they get stuck. Watching someone use a site can reveal mismatches between a team’s assumptions and the language, choices, or information visitors actually need.
Include people who have difficulty with the current service, not only those who are easiest to recruit or already comfortable online. Consider relevant steps outside the website too: a task may involve a phone call, a document, or another service channel. User research is not a box to check after the design is chosen; without it, a team may not know which problem to solve or whether its service works for users, as the Government Digital Service explains in User research for government services: an introduction.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
Include access needs in the work
Recruit people with different needs and abilities, including disabled participants and people who use assistive technology when relevant to the audience and service. Accessibility is not a final visual polish step: barriers in content, controls, interaction, or structure can prevent people from completing the same tasks as everyone else. The UK government’s Guidance and tools for digital accessibility provides resources for this work. Adapt recruitment, legal obligations, and accessibility practices to the site’s sector and geography.
How do you turn findings into a useful redesign brief?
Write needs as outcomes, not as a preselected feature or aesthetic. For example, “I need to know when my request has been received so I can plan what to do next” describes a need. “Add an email notification” prescribes one possible solution before the team has tested whether it fits.
A compact prompt is: “I need to [do something] so that [achieve an outcome].” Use language people recognize, and connect each need to the evidence behind it. The GOV.UK needs guidance uses the distinction between needing a reminder and deciding in advance that the reminder must arrive by email or letter. That leaves room to test the right channel or another approach.
Do not treat every request as a specification. A user’s words are evidence to interpret alongside observation and other findings; the proposed response still needs to be tested. A concise brief should say who is affected, what they are trying to do, what obstacle is established, and what outcome would count as improvement.
How should you test redesign ideas?
- Choose a task and outcome. Define what a visitor should be able to do and what evidence would show they reached the intended result.
- Develop alternatives. A change might adjust wording, navigation, page structure, or interaction—or it might not require a broad visual redesign. Keep the solution open until evidence points to it.
- Test with actual or potential users. Observe whether people can complete the task, where they hesitate or make errors, and whether they need assistance. Include people with relevant access needs.
- Use realistic devices. Test on the devices people actually use for the service rather than assuming a desktop or mobile-only experience.
- Refine and test again. Keep, change, or remove elements according to what the sessions show. Check usability and accessibility during development, not only after launch.
Government guidance recommends making services simple to use and testing design decisions with users; see 4. Make the service simple to use. The practical principle is broader than a single usability session: keep learning as the design develops and after it is live.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How do you compare a visual refresh with a problem-led change?
Compare options by what visitors can do, not by which mockup wins a preference vote. A visually appealing option may still fail the task; a less dramatic change may remove the obstacle. Use the same task and user groups when comparing alternatives where possible.
Rank #4
| What to assess | Question to ask |
|---|---|
| Task outcome | Can visitors reach the intended result? |
| Friction | Where do they hesitate, make errors, abandon the task, or need help? |
| Different users and access needs | Does the change work for people with different abilities and circumstances? |
| Devices | Does the experience work on devices visitors actually use? |
| Ongoing evidence | Do later research and live service data indicate the problem has improved? |
Preference can be useful context, but asking which version people like best does not establish that either version helps them succeed. There is no universal numeric benchmark in the cited guidance for a successful redesign; teams need measures suited to their service and baseline evidence.
What should happen after launch?
Launching a redesign is not the end of the learning cycle. Continue observing how the live service performs, review relevant analytics and support signals, and run research when new questions arise. Use what you learn to refine the experience rather than assuming that a one-time redesign solved every problem.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThe cadence depends on the team and service. Government Digital Service guidance for government teams recommends user researchers work with a team at least three days a week and research sessions at least every two weeks; it also recommends team members observe at least two hours of user research every six weeks. These are operational recommendations in government guidance, not universal requirements or outcome benchmarks for every website.
When is a visual trend useful?
A trend can be a source of ideas once the team understands the user problem. It may suggest a way to communicate information or structure an interaction, but adoption should depend on whether testing shows that it helps the intended audience complete the task. The evidence does not establish that visual trends are inherently harmful; it establishes that trend adoption alone is weak evidence of a user need.
Official UK government guidance is especially detailed about public services. Its research principles are useful to website teams more broadly, but recruitment, legal duties, success measures, and operating constraints should be adapted to the site’s audience and location.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
