ArticlesWebsite advice

The Myth of Removing Every Barrier: When Website Friction Helps

Paper-collage pathway with a filter, price tag, calendar and location checkpoint leading to a handshake, with an unsuitable route redirected

There is a familiar moment in website projects when someone points to a form field, a price, a booking rule or an eligibility question and says, “Can we remove that? It might put people off.”

Sometimes they are right. Websites can make simple tasks feel like applying for a small mortgage. An unclear menu, a compulsory account, a form that asks for information nobody uses, or a surprise fee at the final step creates effort without helping anyone.

But the opposite assumption is also risky: that the best website is the one that lets every visitor proceed with the least possible thought.

A website is not a waterslide. Its job is not to move the maximum number of people from the top to the bottom at any cost. Its job is to help suitable customers make a confident decision, and to help the business deliver what follows. Sometimes that requires a useful pause.

Not every drop-off is a failure

We tend to treat abandonment as proof that a pathway is broken. If fewer people complete a form after a budget question is added, the question must be bad. If bookings fall after prices are made visible, the price must be frightening people away.

Perhaps. It is also possible that some visitors learned the service was not suitable before spending their time and the business owner’s time on an enquiry that could not progress.

The number of completions matters, but it is not the whole result. A shorter form may produce more enquiries while creating more unsuitable work, slower replies and disappointed customers. A longer form may qualify well but discourage people who cannot reasonably answer detailed questions yet. Neither form is automatically better.

The right test is what happens after submission. Are the enquiries a reasonable fit? Can the business respond efficiently? Do suitable customers understand what will happen next? Are people being excluded for a business reason, or merely because the website is awkward?

This is the same distinction made in How Do You Know Whether Your Website Is Actually Working?: activity is not a business outcome. Form completions, clicks and bookings need to be connected to qualified enquiries, attended appointments or sales.

A useful barrier has a job

Purposeful friction changes the quality of a decision. It may ask a customer to confirm a service area, choose an approximate budget, read a cancellation condition, select a realistic date, upload a useful photo or acknowledge that a service has a minimum commitment.

Bad friction is different. It exists because two systems do not talk to each other, because a plugin default was never questioned, because the business wants data “just in case”, or because the customer must decode an internal process.

The customer should be able to see the bargain

An extra step is easier to accept when its purpose is obvious. “Tell us the suburb so we can confirm we service your area” is a fair exchange. “Address line 1, address line 2, suburb, state and postcode” before the visitor has even chosen a service feels like administration arriving early.

The customer gives a little effort or information. In return, the pathway becomes more relevant, accurate or dependable. If the business cannot explain that exchange in one sentence, the step may not have earned its place.

Price can create friction, but hidden price creates uncertainty

Prices are often removed from websites because they might deter someone. Of course they might. A price tells a customer whether an offer fits their budget. That is one of its jobs.

Not every service can publish a single figure. Complex work may need a range, a starting point, a minimum project size or a clear account of what affects the quote. The aim is not false precision. It is enough information for a reasonable person to decide whether the next step makes sense.

For consumer-facing prices, clarity also has legal significance. The ACCC’s price-display guidance says businesses must communicate clear and accurate prices before booking, ordering or purchase, and must display the minimum total cost including taxes and unavoidable or pre-selected fees.

A price signal may reduce the raw number of enquiries. It can also prevent the particularly joyless exchange where both parties invest time before discovering they were never discussing the same scale of work.

Every form field sends a small invoice

A form field charges the customer in attention, confidence and time. One field is cheap. Twelve unexplained fields are not.

The invoice is worth paying when the answer changes what happens next. A project postcode may determine serviceability. A preferred date may determine capacity. A photograph may replace several emails. A budget range may help a business recommend the right service rather than begin with an unsuitable proposal.

Fields that do not affect routing, fit, preparation or response should be challenged. The Office of the Australian Information Commissioner’s current APP 3 guidance says covered organisations should collect personal information only when it is reasonably necessary for their functions or activities. Even where a small business is not covered by the Privacy Act, data minimisation is a sensible design habit. If you do not need information, do not create the responsibility of storing it.

The technical details matter too. The W3C’s accessible forms guidance recommends asking only for information required for the transaction or process, using clear labels and instructions, and providing useful feedback when something goes wrong. A purposeful question presented badly is still bad friction.

Booking rules should protect both calendars

Online booking is often sold as the removal of friction: choose a time, press a button, done. Behind that simple action sit lead times, buffers, travel, preparation, deposits, cancellation rules, staff availability and the types of work that can sensibly be booked without a conversation.

If those rules are not deliberate, software defaults become business policy. Every empty hour may appear available. A customer may be able to book a complex service tomorrow morning. A short appointment may split a day in a way that leaves the remaining time unusable.

A small amount of friction before booking can prevent much larger friction afterwards. Confirming the service type, location, price, duration and cancellation terms helps the customer understand the commitment. It also helps the business protect time it cannot sell twice.

A boundary should sound like service, not suspicion

The wording changes the experience. “We ask for two business days’ notice so we can offer the appointment to someone else” explains a practical rule. “NO CANCELLATIONS” sounds as if the website has already had an argument with the customer.

Useful boundaries are specific, proportionate and visible before commitment. They make saying yes straightforward and saying no considerate. They should not punish everyone for one unusual incident.

Put the pause before the expensive mistake

Friction is most valuable when it appears before a decision becomes costly to reverse. Show the service area before the full form. Explain the minimum project size before asking for a detailed brief. State likely timing before collecting payment. Put meaningful cancellation terms beside the booking choice, not in a link discovered afterwards.

This is where websites become more than brochures. As the article Your Website Should Be More Than a Brochure explains, a useful site can guide customer pathways and support the way the business actually operates.

Timing matters because the same question can feel reasonable or intrusive depending on when it appears. Asking for a delivery address during checkout is expected. Asking for it before showing a product is not. Requesting detailed project information after explaining scope and price can be useful. Demanding it on a generic contact form transfers the business’s discovery work to the customer.

The test for every extra step

Does this pause help the customer make a better decision or help the business deliver what follows, and can both sides understand why it is there?

A useful barrier prevents a larger mistake. A useless barrier merely moves work from the business to the customer.

Measure suitability, not just ease

A friction audit needs more than a conversion rate. Track the number of completed enquiries or bookings, but also review what happened next.

  • How many enquiries were suitable for the service?
  • How many needed basic clarification the website could have provided?
  • Where did good-fit customers hesitate or ask for help?
  • Which questions saved time later, and which answers were never used?
  • Which bookings were moved, cancelled or declined because an important condition appeared too late?
  • Did the pathway make it easy to confirm success and recover from an error?

A modest monthly sample is often more revealing than a large dashboard. Read several enquiries. Ask the person who responds to them which details are useful. Compare form completions with qualified conversations or attended bookings. Note recurring customer questions.

Attribution will remain imperfect. A person may read the price on Monday, ask a friend on Tuesday and call on Friday. The useful aim is not laboratory certainty. It is enough evidence to identify repeated confusion and make one deliberate change.

A practical test for purposeful friction

Review one important pathway from landing page to confirmation. For each extra step, field, condition or choice, ask:

  1. What decision does this improve? Name the customer or business decision. “We have always asked” is not a decision.
  2. Can the customer reasonably answer now? A new visitor may know their suburb and preferred date, but not your internal service category or the technical cause of their problem.
  3. Does the answer change anything? If nobody reads it, routes it or uses it to prepare, remove the question.
  4. Is the reason clear? Explain why you need information or agreement when the benefit is not obvious.
  5. Is the effort proportionate? The larger the commitment, risk or custom work, the more qualification may be justified. Buying a gift card should not require a project brief.
  6. What happens when the customer is not a fit? Give a clear, kind outcome: another service, a different contact method, a future date or an honest decline.

Remove, rewrite, reorder or split

Removing the step is only one option. A useful question may need plainer language. A price or condition may need to appear earlier. A long form may work better as two stages, with a short first enquiry followed by detailed information once fit is confirmed.

Sometimes the business process needs to change. If every enquiry requires several emails because the offer has no ordinary starting point, polishing the form will not solve the underlying ambiguity. The website-cost guide explains why clear scope and defined processes affect what a website project involves. Technology works best after the decision is reasonably clear.

The kindest pathway is not always the shortest

A short pathway can be inconsiderate if it lets a customer proceed without price, fit, timing or important conditions. A longer pathway can be inconsiderate if it asks the customer to perform unpaid administration for the business.

The useful middle is not “more friction” or “less friction”. It is friction with a named purpose, placed at the right moment and written in language that respects the customer.

Start with one form, booking page or service pathway. Remove a step that nobody can justify. Clarify one condition that customers discover too late. Add one question only if the answer will genuinely improve the next response.

Your website does not need to be frictionless. It needs to make the right things easy, the important things clear and the wrong-fit path graceful.

Are your website barriers doing useful work?

Review one form, booking path or pricing page with the customer and the business in mind.

Scroll to Top