A lot of product friction is really sequencing friction.
Day 24 on AffiSpark.
A lot of the recent AffiSpark changes looked unrelated on the surface.
Public preview.
In-browser walkthrough flow.
Exit-intent feedback.
Promo-code attribution.
Today I think they were all solving the same problem.
A lot of product friction is really sequencing friction.
Many flows do not fail because a piece is missing.
They fail because the right piece shows up at the wrong moment.
Payment before context.
Handoff before completion.
Feedback after the user has already mentally left.
Same pieces.
Wrong order.
That is why sequencing matters more than I used to think.
The order communicates what the product understands about the user’s state.
Context before payment says:
you can evaluate this safely.
Payment before context says:
commit before you understand.
Completion before handoff says:
finish the job while momentum is still here.
Handoff before completion says:
you do the extra work.
Feedback at hesitation says:
I want to learn from this exact moment.
Feedback after abandonment says:
I probably already lost the useful part.
AffiSpark got better not just because I added things, but because I changed when the product asked for things.
The public preview put context before payment.
The walkthrough form kept the next step in-browser before handing anything off.
The exit-intent prompt asked for feedback while the hesitation was still fresh.
Even promo-code support came from the same idea in a different form:
attribution has to survive when the buying journey gets messy, not just when the first click is clean.
I think founders often react to friction by adding more product.
Sometimes the better move is smaller than that.
The parts might already exist.
They might just be appearing too early or too late.
That is a much cheaper problem to solve.
And often a more important one.
My current rule is simple:
before I build something new, I want to ask whether the current pieces are just showing up in the wrong order.
Curious how others think about this:
what part of your product got easier the moment you changed the order instead of the feature?
The "premature friction" framing is genuinely useful because it changes the intervention. If friction is bad, you remove it. If friction is just early, you move it. Those lead to very different product decisions.
The pricing example you gave is something I've noticed a lot. The exact same price that feels like a wall before someone understands the workflow feels totally reasonable after they've seen it in action. Nothing changed except when the ask showed up.
"Have I earned this ask?" does a lot of work. It shifts from "will users accept this" (which depends on the ask) to "have they built up enough context to accept this" (which is much more controllable).
One mental model that's helped me: treat trust like a limited resource. Every premature ask depletes it. Every value moment replenishes it. Friction only clears when the trust balance is positive at the moment of the ask.
That's a strong way to frame it.
“If friction is bad, remove it. If friction is early, move it” is exactly the distinction I was trying to get at. And I like the trust-balance model too, because it explains why the same ask can feel unreasonable in one spot and completely fine a few steps later.
“Have I earned this ask?” is probably the better product question.
This resonates. The version I keep running into is onboarding for non-technical users — small operators who aren't evaluating your product on feature depth, but on whether they can trust it enough to invest their time in setup. Flipping the sequence from "connect your accounts → see value" to "see value with sample data → then connect" changes the entire dynamic. It's the same move you're describing: context before commitment. To answer your question — the thing that got dramatically easier when we reordered was the initial data sync step. Same feature, different position, completely different conversion rate.
Exactly. “See value with sample data, then connect” is a strong example because it does not remove the setup work, it just stops asking for commitment before belief.
And that's usually the real shift. Same feature, better sequence, much less perceived friction.