Feedforward in ecommerce
Next principle →A button that names the next step makes shoppers less afraid to press.
A button that says only Continue leaves shoppers guessing whether it will charge the card or show shipping first. Say what happens next and they can press with less worry.
Feedforward, sometimes called an action preview, tells a shopper what will happen before they click, so they can decide with the result in mind.
Look for buttons that cost money or can't be undone, and write what each one does. Arrival dates on delivery options and “Card not charged yet” on a checkout button are both feedforward. Make sure the words are true, because a broken promise can cost more trust than a vague label.
Feedforward example: a checkout button that says card not charged yet
Checkout is the last stop before paying $1,000 for an oak table. The only button says Continue, so the shopper can't tell whether it will charge the card or show shipping first. On these made-up numbers, 72 of 100 shoppers buy, which comes to $72,000. The owner keeps the page and rewrites the button to read Continue to shipping, with a second line saying Card not charged yet. With the new wording, 78 of 100 buy, for a total of $78,000. When a lot of money is at stake, say what the next click does.
How feedforward works with other principles: 4 store examples
Feedforward sits close to a few ideas that also guide a click. Two get mixed up with it, one pulls against it and one makes it stronger. Every store below is made up to show the idea.
Feedforward vs signifiers
Often confused with: A signifier shows that something can be pressed, and feedforward says what pressing it will do, so a button can have one without the other.
Illustrative store example: A razor store shows a solid, button-shaped Subscribe, so shoppers know they can press it. Only the line under it, First box ships Monday and you can cancel anytime, tells them what will happen when they do.
Signifiers: how a button shows where to press →Feedforward vs feedback loop
Often confused with: Feedforward comes before the click and feedback comes after it, so one makes a promise and the other shows that the promise was kept.
Illustrative store example: A gift card store's button reads Email card to Sam on Friday, so the buyer knows the plan. After the tap, a line saying Scheduled for Friday shows it worked, and if that line never appears the buyer will wonder whether Sam gets anything.
Feedback loop: why every tap needs a visible answer →Feedforward vs curiosity gap
Clashes with: A curiosity gap holds back the answer to make people click, while feedforward gives the answer up front, so the two pull in opposite directions on the same button.
Illustrative store example: A tea subscription store puts See what's inside on a button, and shoppers can't tell if it opens a photo page or starts an order. Keep the teaser in the headline and make the button say See this month's 6 teas.
Curiosity gap: when a teaser earns the click →Feedforward and provide exit points
Works with: Feedforward says what a button will do and an exit point says how to undo it, and shoppers can hesitate less when they know both.
Illustrative store example: A luggage store's button reads Reserve for pickup, card not charged, so shoppers know what comes next. A short line beneath it promises a Cancel link on the next screen, which makes that first click feel smaller.
Provide exit points: how a clear way out builds trust →Put it into practice
What is the difference between feedforward and feedback?
Timing. Feedforward comes before the action and says what will happen: “Clicking takes you to shipping.” Feedback comes after and says what did happen: “Added to Bag.” A store needs both, and checkout shows why: the button should say what it will do, and the next screen should confirm it happened.
How do I write a feedforward label?
Finish the sentence “When I press this, ...” and use the answer. Continue becomes Continue to shipping. Submit becomes Place order for $1,000. Sign up becomes Get the weekly email. Start with a verb, then say what happens, and add a short second line only for a real worry such as being charged.
Where else can I use feedforward besides buttons?
Anywhere a shopper is about to commit. Put the arrival date on each delivery option instead of a name like Standard Courier. Show a swatch's color on the product photo when someone hovers over it or taps it. Show the total with shipping before the pay step. On a subscription, say when the first charge comes and how often.
Can a button say too much?
Yes. A button with two lines of small print is harder to scan, and shoppers may stop reading it. Keep the label to the next step and one key reassurance. It also backfires when the words aren't true: if “Card not charged yet” is followed by a charge, you've lost that shopper's trust.
How do I know a clearer button helped?
Split your visitors so that half see each button, which is called an A/B test, and count how many finish checkout. A wording change may only move things a little, so let it run until you have plenty of orders. You can also show a few people each button and ask what they think it will do. If they guess right, the label is working.