Lessen the Burden of Action and Information: Cut Steps, Fields and Load
Learn how to remove steps, fields and mental load from a task, and how to find the friction that makes people quit.
In short
Lessening the burden of action and information means removing steps, fields and mental load from a task, so fewer people quit part way through.
12 min readFree
What You Will Learn
Every screen asks something of the person using it. It asks them to read, type, click or decide. This lesson is about lowering that ask. When an action takes less effort, or the information is easier to take in, more people finish what they started. You will learn how to cut steps and inputs, how to reduce the information a person must handle, and how to find the friction that makes people quit so you know where to start.
Key words
- Burden
- The effort, steps and thinking a person must spend to finish a task.
- Friction
- Anything on a screen that slows a person down or makes them stop. Extra fields, extra clicks and confusing text all count.
- Input
- Any piece of information a person must type, pick or upload.
- Cognitive load
- How much a person has to hold in their head at one time while they work. Also called mental load.
- Drop-off (abandonment)
- The point where a person quits a task before finishing it.
- Completion rate
- The share of people who start a task and finish it.
- Time-to-complete
- How long a person takes to finish a task, from the first step to the last.
- Progressive disclosure
- Showing the items people need most first, and keeping the rest one step away until someone asks for them.
- Autofill
- A browser or website filling a field with information it already has, so the person does not type it.
What Are the Two Kinds of Burden?
Burden comes in two forms. The action burden is the work of doing something, such as filling in a form, pressing buttons or moving between pages. The information burden is the work of understanding something, such as reading a long paragraph, scanning a crowded page or guessing what a label means. Both slow people down, and both make them more likely to leave.
Action burden
Each field, click, page change or password request gives a person one more reason to stop. A form with many required boxes asks far more of them than a form with a few.
Information burden
Long text and crowded screens force extra reading before a person can decide. Content that can be scanned in seconds lets them act sooner.
Friction
Friction is the sum of small annoyances in a task. One box rarely ruins a form, but many small costs stack up until the person gives up.
The goal is not to strip out everything. Removing a step the business truly needs, or hiding a detail a person must read before paying, creates new problems. The goal is to remove the parts that do not help the person finish the task.
Cut the Steps and Inputs
Start with the action itself. Count how many steps it takes and how many things a person must type or pick. Then ask which of those things are needed right now, and which could wait or disappear.
Remove Fields You Do Not Need
Many forms ask for information out of habit. CXL, a conversion research site, argues that each extra question makes a form harder to finish, so the fix is to cut what is not truly needed. A practical test is to ask whether the transaction can still be completed without a given field. If it can, that field can be moved later or removed.
Tip
Ask of every field: what breaks if this box is empty? If the honest answer is nothing, delete it or move it to a later moment.
Combine Fields and Screens
Two boxes that describe one idea can often become one. Fewer boxes mean fewer taps and less attention spent on the form. Splitting a long process into several small screens is a separate choice. It can help when each screen asks one clear question, but it can also add page loads and waiting. Test the choice instead of assuming it works.
Prefill and Reuse What You Already Know
If a person has already told you something, do not ask again. A postal code or email given earlier in a buying process can be carried forward to the next step. Returning customers can have their saved details filled in for them. Address autofill adds one more saving: the person types a few letters, picks the right address from a suggestion list, and the other address boxes fill themselves.
Tip
Use standard, plain labels such as 'Postal code' or 'Email'. Browsers and autofill tools recognise common labels more easily than unusual ones.
Reduce the Information Load
Information load is how much a person must read, compare and remember before they act. You can lower it by breaking content into small parts, showing only what matters at this moment, using plain words, and arranging the page so the most important thing is seen first.
Chunk Content Into Small Groups
Chunking means grouping related items into small sets. Splitting a form into steps can help, as long as tightly related fields stay together on the same step. A progress indicator also helps, because it tells people how far they have come and how much is left.
Use Progressive Disclosure
Progressive disclosure shows the few most important options first and reveals the rest when a person asks. Writers describe it as a way to make complex tools easier to learn and less error-prone. The first layer holds what most people need most of the time, and advanced items sit one step away behind a link, panel or secondary screen.
Show the essentials first
Put what most people use every time in the first view. Never hide something that people need on every visit.
Keep the levels shallow
Summaries of Nielsen Norman Group research say designs with more than two layers of hidden content tend to lose people. Keep the path to a hidden item short.
Label the hidden part clearly
A hidden option only helps if people can tell it exists. A label such as 'Show more details' tells them what they will get.
Hiding is not always the right move. A Nielsen Norman Group writer noted in 2014 that scrolling down a page is often easier than deciding which heading to open. When people need to compare items, show them together.
Plain Language and Clear Hierarchy
Plain words lower the load. 'Full name' is easier to read than an official-sounding phrase that a person must decode. Clear hierarchy means the most important item looks the most important. Fullstory, a product analytics company, advises using clear labels that match how customers think, and grouping shipping and payment details in a logical way. Show the price and the next button where people look first, and use visible labels rather than placeholder text that disappears once someone starts typing.
Tip
Read each label out loud. If you have to pause and guess what it wants, rewrite it in everyday words.
Worked Example: A Checkout Step by Step
Here is one real flow that uses these ideas. Shopify, an online store platform, describes a guest checkout that lets a shopper buy without creating an account. This lesson compares that approach with an imagined slow checkout that forces account creation and asks for about 15 fields before payment. The steps below follow Shopify's own descriptions.
- 1
Skip the account wall
A guest gives only what the order needs: contact details, a shipping address and payment.
- 2
Type the address once, or not at all
The shopper types a few characters of the street address and picks a match. The other address boxes fill in. Shopify has announced that its address autocomplete will soon be enabled automatically on stores.
- 3
Merge and hide
Name boxes become one, and a rarely used second address line can sit behind a link. Both changes remove visible work without removing anything the order needs.
- 4
Reuse saved details
A signed-in customer, or someone using a wallet such as Shop Pay, has shipping and payment details filled in from earlier orders.
- 5
Offer one-tap payment
Accelerated checkout buttons, such as Shop Pay, fill the saved shipping and payment details on their own. There are no forms to type.
- 6
Ask for the account last
After the purchase, the shopper can be invited to create an account. The business already has the name, email and address, so the sign-up takes little effort.
The result is what matters for this lesson. Shopify's own checkout guidance includes a store, Stellar Eats, that switched to a one-page checkout and saw conversions rise by 3.5%. That is a single case, so treat it as a sign of what to test, not a promise. The lesson is that each removed box or tap happens at the exact moment a person decides to buy.
Shopify is used here because its guides and examples were available to read in full. The same logic applies to any form where someone is about to act.
How Do You Find the Friction Before You Change It?
Do not guess where the problem is. Map the path a person takes, then look for the points where they stop, hesitate or go back. A user flow is the set of screens and actions a person moves through to finish one task.
Map the Flow Step by Step
- 1
Write the goal
Name the single action you want, such as placing an order or finishing a signup.
- 2
List each screen
Write every page or screen between the start and the finish, in the order a person sees them.
- 3
Count the work on each screen
Note the fields, buttons and decisions on each one. Those are your possible sources of burden.
- 4
Mark the exits
Note every place where a person could leave the flow, including places where they must wait or search for something.
Spot Drop-Off and Hesitation
Analytics tools can show how many people reach each step and how many leave there. Fullstory suggests splitting a checkout into smaller transitions, such as cart to shipping, shipping to payment and payment to confirmation, rather than reading it as one big funnel. This shows the exact step where people quit.
How Do You Measure With Completion Rate and Time?
Completion rate
Out of everyone who starts, how many finish? This is the main test of whether a change worked.
Time-to-complete
How long the task takes from start to finish. Shorter is usually better, but a fast finish full of errors is not a win.
Error rate
How often people hit a warning message, or go back to fix something they entered.
Record today's numbers before you change anything, then compare the same measures afterwards. Without a before-and-after record, you cannot tell whether the change helped.
Tip
Measure first, change second. Write down the current completion rate and time-to-complete, so the team can prove that a later change made things better.
Common Mistakes to Avoid
Removing a field the business needs
If a removed box was truly needed, the order may fail or staff must chase the answer later. Ask why each field exists before you delete it.
Clearing the form after an error
Keep what the person typed, and point straight to the field that needs fixing.
Hiding costs until the end
Surprise costs at the last step create doubt and drop-off.
Giving a side field too much weight
A prominent coupon-code box can send people off to search for a code, and some never come back. Keep it modest.
Autofill can also backfire. A merchant forum thread describes shoppers who felt that automatic payment choices limited their options. Let people change saved details easily.
Check Your Thinking
Try these two short scenarios. Each one needs the ideas from this lesson.
Quick check
A small bakery's online order form has 14 fields. Its analytics show that most people who start the form leave on the delivery address page. Which change would you test first?
Quick check
A signup form asks for name, phone, company, job title, address and a password confirmation. 60% of people who start it abandon it. Which change should you make first, and why would it raise completion?
Key Takeaways
Lessening the burden means cutting the steps, typing and mental effort a person needs to act or understand. Remove fields you do not need, combine what can be combined, and reuse details you already have. Shrink the information load by chunking content, showing essentials first, and writing in plain words. Then find the friction with a clear user flow, drop-off data and session recordings, and judge each change by completion rate and time-to-complete.
Tip
Pick one step to cut this week, record its numbers, and keep the change only if completion improves.
Sources
- Shopify: Checkout Optimization Complete Guide (2026)
- Shopify: Guest Checkout, Benefits, Best Practices, and How-To
- Shopify: Autofill, Google Autocomplete at Checkout
- Bogos: Shopify Guest Checkout, Setup, Fixes, and Best Practices
- Shopify Community: Disable ShopPay default checkout (forum thread)
- Baymard Institute: Ecommerce Checkout UX Guide
- CXL: Form Design Principles, 13 Empirically Backed Best Practices
- Forefront Industries: Cut Checkout Friction to 12 Form Fields
- LogRocket: Designing a seamless checkout flow
- Fullstory: Checkout Friction: The Hidden Leaks in Your Conversion Flow
- Zuko: 14 Experts share their checkout optimization tips
- Wikipedia: Progressive disclosure
- UX Pickle: Progressive Disclosure, Definition and Examples
- Phoenix Studio: What Is Progressive Disclosure and How Does It Simplify a Page?
- Raw Studio: Validate Progressive Disclosure in Two Sprints for Designers
- Lollypop: Progressive Disclosure UX, Guide and Examples
- Bytebridge (Medium): Progressive Disclosure, executive summary
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.