The problem is usually not friction. It is premature friction.

Day 25 on AffiSpark.

Yesterday I wrote that a lot of product friction is really sequencing friction.

Today I think the sharper version is this:

The problem is usually not friction.

It is premature friction.

I think founders often treat friction like it is always bad.

Pricing is friction.

Forms are friction.

Setup is friction.

Feedback prompts are friction.

Even asking the user to think for 10 extra seconds is friction.

But that does not automatically make it wrong.

A lot of friction becomes acceptable once it arrives after enough context, trust, or momentum.

That is the important part.

For AffiSpark, I did not remove pricing friction.

I kept the paid entry.

What changed was the timing.

The public preview puts context before payment, so the friction arrives later and feels more reasonable.

I did not remove the walkthrough ask.

I changed the handoff.

The in-browser form keeps the user inside the flow long enough to finish the next step before asking them to do extra work elsewhere.

I did not remove feedback friction either.

I made it timely.

The exit-intent prompt asks one small question while the hesitation is still fresh, instead of showing up after the user is already gone and expecting a thoughtful explanation.

That changed how I think about friction.

Bad friction is often not “too much.”

It is “too soon.”

That sounds small, but I think it is a useful distinction.

Because if the real issue is premature friction, then removing the ask entirely is not always the right move.

Sometimes the better move is:

move it later,

make it smaller,

or earn it first.

I think that is where a lot of early product clarity comes from.

Not:

how do I remove every obstacle?

But:

which obstacles have I earned, and which ones am I asking for too early?

That question feels much more honest.

The user might accept pricing after they can picture the workflow.

They might accept setup after they understand the payoff.

They might accept one quick feedback question after a visible hesitation point.

But before that, the exact same friction feels like a tax.

My current rule is simple:

before I remove friction, I want to ask whether it just needs to arrive later.

Curious how others think about this:

what friction in your product got accepted once it showed up later instead of sooner?