What you'll understand by the end of this lesson
- What feedforward is and how it differs from feedback
- Why uncertainty before an action causes hesitation and drop-off
- How button labels, tooltips, and checkout previews use feedforward
- How to audit your CTAs and forms for missing feedforward
The principle in plain English
Feedback tells you what happened after you did something. A confirmation email after signup, an error message after submitting a wrong password, a green tick after a successful payment — all feedback.
Feedforward tells you what will happen before you act. It answers the question every hesitant visitor is silently asking: "If I click this, what happens next?"
When that question is unanswered, hesitation fills the gap. Visitors pause. Some abandon. Not because they don't want the outcome — but because uncertainty about the path there feels risky.
A simple example
Imagine two doors. One has a sign that says "Push." The other has no sign.
You know how to open a door. But you've probably still paused at a handleless door before, unsure whether to push or pull. That moment of uncertainty — brief as it is — is friction. The sign on the first door eliminates it entirely.
That's feedforward. It's information that removes uncertainty before you need to act.
Where feedforward appears on websites
Button labels that describe the outcome
The most common place feedforward fails is on CTA buttons. Generic labels create uncertainty. Specific labels resolve it.
"Submit" — tells the user nothing. What happens after they submit? Will there be a confirmation? Will they be charged? Will someone call them?
"Get my free report" — tells the user exactly what to expect. They will receive a report. It is free. No surprises.
"Book a 20-minute call" — tells the user the commitment they're making. No ambiguity about what they're signing up for.
The label is feedforward. It answers the uncertainty before the click.
A fast rule for improving button copy: replace the verb with the outcome. "Submit" → "Send my enquiry." "Sign up" → "Create my free account." "Learn more" → "See how it works." The outcome framing answers the unspoken question and removes hesitation.
Tooltips on form fields
Forms create uncertainty at every field. Visitors ask: why do you need this? What will you do with it? Is this required?
A tooltip — even a one-line explanation next to a field — provides feedforward that resolves the hesitation before it turns into abandonment.
"Phone number (optional — we only use this if we need to reach you about your order)" is a feedforward statement. It pre-answers the objection before the visitor even forms it.
Checkout previews
A checkout process that shows a summary screen before the payment step is a feedforward mechanism. It says: here is exactly what you're about to confirm. No surprises.
Removing this preview — jumping straight from "enter card details" to "your order is placed" — leaves a gap where the visitor has to trust that nothing unexpected will happen. Some visitors won't take that risk.
Progress indicators
A progress bar at the top of a multi-step form is feedforward. It tells the user how many steps remain before they know. Without it, every "next" click is a small act of faith — the visitor doesn't know if they're halfway through or one step from the end.
Why this matters for conversion
Hesitation is the direct precursor to abandonment. Visitors don't usually leave because they don't want what you're offering. They leave because they encountered a moment of uncertainty and the effort of resolving it felt higher than the value of continuing.
Feedforward pre-empts that hesitation. It answers questions before they're asked. It turns uncertain actions into confident ones.
Feedforward only works if it's accurate. A button that says "Start your free trial" and then charges the user creates a worse experience than a button that said nothing — because the user now has a broken expectation on top of the original uncertainty. Feedforward must be truthful or it actively damages trust.
The CRO audit
Go through your main conversion path and ask at each action point:
1. Does every CTA button describe the outcome, not just the action?
Look at every button. Does its label tell the visitor what they'll get, not just what they'll do? If it says "Submit," "Go," or "Next," it has no feedforward.
2. Are sensitive or unusual form fields explained?
Any field where a visitor might wonder "why do you need this?" — phone number, company size, job title — should have a one-line explanation. If it's optional, say so.
3. Does your checkout preview exactly what will be confirmed?
Before the final payment step, does the user see a clear summary? Is the price, the product, the delivery terms, and the commitment all visible before they're asked to confirm?
4. Do multi-step forms show progress?
If your form has more than two steps, visitors need to know how far through they are. A progress indicator is feedforward for the journey, not just the next action.
A SaaS pricing page has a button labelled 'Get started.' What is the feedforward problem, and what would improve it?
Feedforward removes uncertainty before users act. But what about the design decisions themselves — when you have multiple solutions and need to choose, what's the principle that guides you toward the simplest one that works?