Users do not hate effort. They hate unclear effort.

Day 33 on AffiSpark.

I think founders often blame the wrong thing when a step feels heavy.

We blame effort.

Too many steps.

Too much setup.

Too much friction.

Too much to ask.

But I think the sharper version is this:

Users do not hate effort.

They hate unclear effort.

A lot of work becomes acceptable once the user can clearly picture two things:

what they are being asked to do

and what they get on the other side of it

That distinction has been useful for me lately.

Because the exact same work can feel very different depending on how legible it is.

For AffiSpark, I did not remove the paid plan.

I did not remove setup.

I did not remove the walkthrough ask.

What changed was that I kept trying to make the work more legible before asking for it.

The public preview makes the paid ask easier to accept because the user can inspect the workflow first.

The work is still there.

It just no longer feels blind.

The in-browser walkthrough flow makes the next step easier to accept because the user can see that clicking the CTA actually leads somewhere finishable.

The ask is still there.

It just no longer feels vague or open-ended.

Promo-code attribution fits the same pattern in a different way.

Affiliate tracking feels much more believable when it survives messy real buying behavior, not just the cleanest possible path.

The system feels safer to invest time in because the payoff looks more real.

That changed how I think about friction.

Sometimes the step is not too much.

Sometimes the step is just too hard to picture.

And when that happens, founders often reach for the wrong fix.

We remove the ask.

We weaken the ask.

We hide the ask.

But sometimes the better move is simpler:

make the work easier to understand before asking for it

Show the path.

Show the payoff.

Show what happens next.

Show what "done" looks like.

I think users can handle more effort than founders assume, as long as the effort feels grounded.

What usually breaks the flow is not just work.

It is uncertainty wrapped around the work.

That is what makes the exact same step feel heavier than it really is.

My current rule is simple:

before I call a step too much effort, I want to ask whether the effort is just too unclear.

Curious how others think about this:

what part of your product got easier the moment users could clearly picture the work and the payoff before starting?