Removing friction across the user journey

I have a rule at BUUT that I repeat in almost every review: if a step in the journey does not either deliver value or earn the right to ask for something, it should not exist. Product-led growth gets talked about like a tactic, a free tier here, a viral loop there. I treat it as a single discipline: remove friction and add value at every stage of the journey, from the first time someone hears about you to the moment they tell a friend. Everything below is how I actually do that.

The journey is a sequence of questions

I map every product as a chain of stages: awareness, acquisition, onboarding, activation, retention, revenue, referral. Each stage has its own friction and, more usefully, its own question in the user's head. Awareness asks is this for me. Acquisition asks is this worth a click. Onboarding asks can I get started without pain. Activation asks did I actually get value. Retention asks is this still worth my time. Revenue asks is this worth paying for. Referral asks would I put my name on this.

Friction is anything that makes the answer harder to reach. A confusing headline, a form field too many, a permission wall with no context, a paywall before the aha. My job is to walk that chain stage by stage and ask three questions at every step: where do users hesitate, where do they lose trust, where do they need reassurance. That audit is unglamorous and it is where almost all the wins are. At BUUT it took our activation funnel from a vague hope to a defined sequence: KYC, child added, allowance set, first transaction. Once you name the steps, you can see exactly where people fall out.

Value-first onboarding: show, then ask

The most common onboarding mistake is gating the value behind work. A long form, a setup wizard, a tour of features nobody asked for, all before the user has felt a single thing worth feeling. You are asking for commitment before you have earned it.

Value-first onboarding inverts that. Deliver a real taste of the value before you ask the user for data, effort or money. Show, then ask. Let them feel the core promise as early as the product physically allows, and only then start requesting the things you need. At Coworksurf I cut time-to-value by 65% mostly by ripping out everything that stood between a new user and the thing they actually came for. Every screen you remove from before the aha moment is friction deleted from the most fragile part of the journey.

This matters even more in a regulated bank, where you are legally obliged to collect a lot up front. The instinct is to front-load all of it. The better move is to sequence it so the user always feels they are moving toward something, never just feeding a machine.

The commitment curve: small asks first

Trust compounds, and so should your asks. I think of it as a commitment curve: you start by requesting something tiny, and as the user gets value and confidence, you escalate. Email before phone number. A single preference before a full profile. One transaction before you ask them to move their financial life over.

Every premature big ask is friction, and worse, it snaps the thread. A user halfway up the curve who suddenly hits a demand that feels too large for the relationship simply leaves. The skill is sequencing the asks to match earned trust, never getting ahead of it. At BUUT, restructuring onboarding around this principle, asking less early and escalating as people progressed, lifted onboarding conversion by over 70% and cut support demand by roughly half. People do not need hand-holding when you stop asking them for more than the moment warrants.

Contextual consent: ask when it is obvious

Permissions and consent are where most products leak trust. The default pattern is an upfront wall: a stack of toggles, legal copy and permission prompts thrown at someone who has not yet seen why any of it matters. It converts badly and, frankly, it is a little dishonest, because you are asking for a yes before the user can possibly understand what they are agreeing to.

Contextual consent fixes this. Ask for each permission, each piece of data, each agreement at the exact moment it becomes relevant and the value is obvious. Ask for notification permission right when the user sets up something genuinely worth being notified about. Request the data point at the step where it visibly unlocks the next thing. Consent given in context converts far better, and it is more honest, because the user can actually see what they are saying yes to.

In a regulated environment this is not a nice-to-have, it is the whole game. We are legally required to ask for a great deal. Spreading those asks across the journey, each one anchored to a clear, immediate reason, is the difference between an onboarding that feels like a value exchange and one that feels like an interrogation.

Friction is the product

None of this is about clever growth hacks. It is craft. Map the journey, name the stages, and walk each one asking where people hesitate, where they lose trust, where they need a reason to continue. Deliver value before you ask for anything. Sequence your asks to match the trust you have actually earned. And request consent only when the reason for it is staring the user in the face. Do that consistently and growth stops being something you bolt on. It becomes what is left over once you have removed everything that was getting in the way.