Day 36 on AffiSpark.
I think a lot of heavy product flows have the same root problem.
Each step creates more uncertainty than it resolves.
The user clicks something and now they have more questions than before.
Did it work?
What happens next?
Do I need to leave the browser?
Am I paying before I understand it?
Will this actually track the way I expect?
That is when a flow starts feeling heavier than it really is.
Because effort alone is not what exhausts users.
Accumulating uncertainty does.
That has been a useful lens for AffiSpark.
The public preview helped because it closed a question:
what am I paying for?
The in-browser walkthrough flow helped because it closed another:
what actually happens after I click this?
Surfaced billing errors helped because they closed:
did the payment fail, or did the flow just disappear?
Promo-code attribution helped because it closed:
will this still work once the buying journey stops being perfectly tidy?
Same product.
Same category.
Different feeling.
I think that feeling comes from whether each step reduces doubt or creates more of it.
A good step usually does one simple thing:
it narrows the next question.
A bad step often does the opposite.
It asks for action, but leaves the user with three new uncertainties to carry into the next screen.
That is when even simple flows start feeling expensive.
I think founders often focus on how much a step is asking for.
That matters.
But another useful question is:
what uncertainty is this step supposed to resolve before the next one appears?
If the answer is “not much,” the step may be doing less work than it needs to.
And if the answer is “it creates more uncertainty than it removes,” the flow will feel heavier than it should even if the number of steps is small.
My current rule is simple:
before I optimize a step, I want to know what question it is supposed to close.
Curious how others think about this:
what part of your product got easier once each step started answering the previous question instead of creating a new one?