7–11 minutes

The UX checklist isn’t enough: 5 questions that shape better website experiences

There are plenty of UX checklists.

We have heuristics, research methods, accessibility guidelines, design patterns, journey maps, user flows and frameworks for just about every stage of a website project.

They’re useful. They give teams a shared language and help make sure important considerations don’t get missed.

But they don’t make the decisions for us.

The more website projects I work on, the more I find myself coming back to the questions underneath the process.

What are we actually trying to change?

What do we need to know before we make a decision?

How will someone make sense of what we’re showing them?

Will the experience still work once it becomes part of the day-to-day reality of the organization?

And is a new feature or interface actually what the situation calls for?

These questions are closely connected to the way we approach customer-driven strategy at Marketing Mile. Good digital experiences start with understanding the people we’re trying to reach, what they need to understand, and how they make decisions.

The website is where a lot of that thinking becomes visible.

1. Are we clear on what we’re trying to change?

A project brief gives us a starting point. It doesn’t necessarily give us the whole picture.

A client might come to us looking for a new website, a new navigation, a new feature or a redesign of a particular page. Those requests are important, but they are only one part of understanding what needs to happen.

Before getting into solutions, I want to understand:

  • What are we actually trying to change?
  • Who is affected by the current experience?
  • What is driving the need for change?
  • Is the stated issue the underlying issue, or something we can see because of it?
  • What would be different for the customer if we solved it?

This is where customer understanding becomes incredibly useful.

A website that feels difficult to use might have an information architecture issue. It might have a content issue. It might be that customers don’t understand the offering in the first place. Or the business may be asking people to make a decision before they have the information they need.

The right response depends on understanding what is actually happening.

This is one of the reasons I like the way Marketing Mile approaches customer research. The goal isn’t simply to collect information about customers. It is to understand what that information means for the decisions the business needs to make.

The same thinking applies to a website.

Before we decide what to build, we need to understand what we’re trying to change.

2. Do we know enough to make this decision?

It’s easy to treat research as another step in the process.

Conduct interviews.
Review analytics.
Look at competitors.
Test the prototype.

But the method is only useful if it helps us answer something that matters.

I prefer to start with the decision.

What are we trying to decide? What do we already know? Is there anything we are still uncertain about? And which of those unknowns could actually change the direction of the work?

That last question is important.

We can always learn more. There is almost always another report to review, another interview we could conduct or another piece of data we could collect.

The question is whether we need it to make the next decision.

This matters for websites because customers are often making important decisions before they ever speak with someone at the organization. 6sense’s 2024 B2B Buyer Experience Report, found that 81% of B2B buyers had already selected a preferred vendor before speaking with a salesperson.

That puts a lot of responsibility on the information people encounter while they are researching.

The website needs to help people understand what the organization does, whether it is relevant to them, what makes it credible and what they need to know before deciding what to do next.

That means research should help us understand those questions, not simply give us a collection of interesting findings.

Good UX isn’t about knowing everything. It’s about knowing what we need to know before we move forward.

3. Do we understand how people make sense of this?

This is where website structure becomes particularly interesting.

We spend a lot of time deciding how information should be organized. Navigation. Sitemaps. Page groupings. Content hierarchies. User journeys.

But the organization of the business isn’t necessarily the way a customer thinks about it.

Your team knows your services, departments, areas of expertise and internal terminology. A prospective customer may simply know that they have a problem and are trying to figure out what to do about it.

That distinction can have a huge impact on a website.

The way customers make decisions should influence how a website is structured. Understanding customer decision-making can help uncover the questions people are asking, the language they use and the information they need as they move toward a decision.

That gives us a much stronger foundation for deciding what belongs in the navigation, how pages should connect and what information needs to appear together.

It also changes the role of information architecture.

Instead of asking only, “Where should this page live?” we can ask:

  • What is someone trying to accomplish?
  • What information would they expect to find together?
  • What question is likely to come next?
  • What do they need to understand before they can move forward?
  • Are we organizing around their experience or ours?

This is becoming even more relevant as AI changes how people discover information.

Someone may arrive at a specific page from an AI-generated answer rather than starting on the homepage and following the navigation. That changes the path, but it doesn’t remove the need for good structure.

The relationships between information still matter. Context still matters. Clear language still matters. So does knowing what someone is likely to need next.

Webflow’s 2026 State of the Website research, based on a survey of 1,000 marketing and technology leaders across the U.S., Canada and the UK, found that 52% of marketing leaders plan to prioritize optimization for AI-driven search and summaries in 2026.

As the way people find information continues to change, the underlying job remains familiar: help people understand what they are seeing and decide what to do with it.

AI can change the path to information. It doesn’t change the need for the information to make sense.

4. Will this work in the real world?

A website can look great in a prototype and still be difficult to manage once it’s launched.

The content changes. People change roles. Services evolve. Processes change. New information needs to be added. Someone who wasn’t part of the original project eventually becomes responsible for maintaining the site.

Those realities are part of the experience too.

So I want to understand:

  • Who will maintain this?
  • What happens when the content changes?
  • What happens when the process behind the experience changes?
  • Can the organization support what we’re designing?
  • What will this look like six months after launch?

This is one of the reasons collaboration matters so much in website projects.

UX, content, marketing, technology and business teams each see a different part of the experience. Bringing those perspectives together earlier gives us a better chance of designing something that can actually work within the organization.

And that matters beyond the initial launch.

A website isn’t a finished product that gets put away. It becomes part of how the organization communicates, sells, supports customers and operates.

It has to work in the real world, not just in the prototype.

5. Does this problem need a UX solution?

This is one of my favourite questions because it opens up the solution space.

Sometimes the answer is a new interface or feature.

Or maybe it’s clearer content.

Perhaps it’s a change to a process.

It could even be that the information already exists and simply needs to be easier to find.

And sometimes the best improvement is to remove something rather than add something.

This is yet another area where customer understanding provides so much value.

If we understand what people are trying to accomplish and where they are getting stuck, we can start looking at the whole experience rather than assuming the answer has to be a website change.

That might mean changing the content before changing the design.

It might mean fixing an internal process that is creating friction for customers.

It might mean changing how a service is explained.

Or it might mean building something new.

The point is to understand the situation well enough to make that choice deliberately.

This connects with a broader idea we return to often at Marketing Mile: customer insight should help the business decide what to do next.

That applies to websites just as much as it applies to marketing strategy.

The right solution starts with understanding what needs to change.

Good website experiences start with better questions

UX frameworks and checklists are useful. They give us structure and help us think through the experience systematically.

But the most important decisions usually happen before we get to the checklist.

They happen when we ask:

  1. What are we trying to change?
  2. What do we need to know?
  3. How will customers make sense of this?
  4. Will it work in the real world?
  5. What kind of solution does the situation actually call for?

Those questions bring customer understanding into the website process.

And that is where the connection between strategy and experience becomes really important.

A customer-driven strategy can tell us who we are trying to reach, what matters to them and how they make decisions. The website then has to bring that understanding to life through its content, structure, interactions and pathways.

Strategy only becomes meaningful when customers can actually experience it. The gap between strategy and customer experience often shows up in the places where people interact with an organization, including its website, content and other digital touchpoints.

So before jumping into the sitemap, wireframes or visual design, it is worth taking a step back and asking better questions.

Because good website experiences aren’t created by following a formula.

They come from understanding the people, the business and the decisions that the experience needs to support.

Let’s work together

If you’re thinking about a new website, revisiting an existing one, or trying to figure out why your current experience isn’t supporting customers the way you want it to, Marketing Mile can help you connect the strategy to the experience.

We can start with customer research, look at how people are making decisions, review your existing website, or work through the structure and content needed to support the journey.

About the Author: Emily

Emily Sumarah is an Experience Architect & Solutions Strategist who supports Marketing Mile clients in ensuring that customer-driven strategy is reflected in their digital experiences. She helps organizations create websites that align with user needs, support decision-making, and consistently bring strategic priorities to life.