Every PM has internalized the same lesson: remove friction, increase conversion. Fewer clicks, faster onboarding, smoother flows. It's product management orthodoxy.
But in 2026, a growing number of product leaders are questioning this default. The argument is simple: if AI can replicate any frictionless experience overnight, then frictionless IS the commodity. The moat lives in the friction.
Quick Answer (TL;DR)
Friction maxxing is the deliberate addition of strategic friction that increases user investment, skill development, and switching costs. In a world where AI commoditizes features instantly, the products that retain users are the ones where users have built something they can't walk away from. The key distinction: friction must create value, not block it.
What Is Friction Maxxing?
The term picked up momentum after Mind the Product featured it this week, but the idea has been brewing since AI-generated products started shipping at scale in late 2025.
Here's the core thesis: in the AI era, any feature you ship today can be cloned tomorrow. AI coding assistants build MVPs in hours. Design tools generate interfaces on demand. The traditional USP (unique selling proposition) has a half-life measured in weeks.
So what's left? Switching cost.
Friction maxxing is the practice of deliberately designing product experiences that require meaningful user investment. Not pointless hurdles. Not dark patterns. Strategic friction that makes users more capable, more embedded, and more reluctant to start over somewhere else.
Think of it this way: a product with zero friction is a product with zero switching cost. Users who invested nothing will leave the moment something 1% better appears. And with AI generating new products daily, that moment comes fast.
Why Frictionless Products Are Losing
The "remove all friction" playbook worked when building software was hard. If your competitor needed 18 months to copy your smooth onboarding, you had runway. That's no longer true.
AI commoditizes features overnight. An agentic AI system can analyze your competitor's product, generate equivalent functionality, and ship it before your next sprint planning. Feature parity is the default now, not the exception.
Zero-friction onboarding means zero switching cost. If a user can get value from your product in 30 seconds with no setup, they can get value from your competitor in 30 seconds too. You've optimized yourself into replaceability.
Users who invest nothing leave easily. This is the churn rate problem that frictionless products refuse to acknowledge. Low-investment users churn at 3 to 5x the rate of users who completed meaningful setup. The data is consistent across B2B SaaS.
The Notion example tells the story. Notion is objectively harder to learn than Apple Notes or Google Keep. The onboarding is longer. The learning curve is steeper. And Notion's retention crushes simpler alternatives. Why? Because users who build databases, create custom templates, and connect integrations have invested dozens of hours. That investment IS the moat.
Three Types of Strategic Friction
Not all friction is created equal. The friction maxxing framework identifies three types worth adding.
1. Investment Friction
Make users build something valuable inside your product. Custom workflows, personalized dashboards, curated template libraries, configured automations. Every hour a user spends customizing your tool is an hour they'd need to repeat elsewhere.
Example: A PM using a RICE scoring model who has configured custom weights, imported historical data, and built scoring templates for their specific team context. Switching to another prioritization tool means rebuilding all of that from scratch.
2. Learning Friction
Require skill development that pays compounding returns. Products with genuine learning curves create users who identify as practitioners of that tool. Figma designers, Excel power users, Vim enthusiasts. The skill itself becomes a sunk cost.
Example: Figma's auto-layout system takes hours to master. But once you've internalized it, you're 10x faster than someone using a simpler tool. Walking away from Figma means walking away from that investment in yourself.
3. Network Friction
Create collaborative dependencies that make individual switching decisions insufficient. When your team's processes, communication patterns, and shared knowledge live inside a product, no single person can decide to leave.
Example: A product team with 200 Slack channels, custom workflows, and integrations connected to their entire tool stack. Even if a better messaging app appears, migrating the network is a project that nobody wants to own.
When Friction Maxxing Works (and When It Doesn't)
This isn't a universal strategy. It's a specific play for specific product categories.
Where friction maxxing works:
- B2B tools where users build workflows and store institutional knowledge
- Productivity software where customization drives efficiency gains
- Platforms with data gravity where more data means more value (analytics, CRMs, project management)
- Collaboration tools where network effects compound over time
- Products pursuing a product-led growth strategy with expansion revenue
Where friction maxxing fails:
- Consumer apps competing on convenience. Nobody wants friction in their food delivery app.
- Checkout and payment flows. Every additional step costs revenue. This is not the place.
- Signup and authentication. Friction here just kills acquisition.
- Emergency or time-critical tools. When speed is the value prop, friction is the enemy.
The dividing line is clear: friction must create value, not just block it. If the friction makes the user more capable or more invested, it's strategic. If it just makes them wait or work harder for the same outcome, it's bad design.
How to Apply This to Your Product
Here's a practical playbook for PMs considering friction maxxing.
Step 1: Map your product's friction points. Use a Jobs to Be Done framework to identify every moment where users invest effort. Categorize each as value-creating friction or value-blocking friction.
Step 2: Identify which friction points increase switching cost. Look for moments where users create something unique: configurations, templates, custom fields, saved views, integrations. These are your defensible friction points.
Step 3: Test adding "productive friction" to onboarding. Instead of the fastest possible time-to-value, design onboarding that helps users build something personalized. A custom dashboard. A configured workflow. A template tailored to their team size.
Step 4: Measure retention by onboarding depth, not just speed. Track cohorts by how much setup users completed, not how fast they finished. You'll likely find that users who spent 20 minutes in onboarding retain 2 to 3x better than those who skipped through in 2 minutes.
Step 5: Plan friction investments on your roadmap. Use your product roadmap to schedule features that deepen user investment. Template builders, customization options, data import tools, and integration ecosystems all increase switching cost over time.
Real Examples of Friction Maxxing in 2026
These products prove that strategic friction drives retention.
Notion added complexity at every turn. Databases, relations, formulas, API integrations, team wikis. Each layer of complexity is a layer of user investment. Their churn rate for teams using 3+ features is under 2% monthly, compared to 8% for single-feature users.
Figma bet on a steep learning curve with massive payoff. Design systems, component libraries, auto-layout, variables, and dev mode require real skill investment. Designers who master Figma don't switch because their speed advantage is too large to abandon.
Salesforce turned customization complexity into an entire ecosystem. Custom objects, Apex triggers, Flow automations, and AppExchange integrations create a web of dependencies that make migration a multi-year, multi-million dollar project.
Linear took a different angle: opinionated workflows. Instead of letting teams configure everything, Linear enforces specific patterns for issue tracking, cycles, and project management. Teams that adopt Linear's workflow build muscle memory and process habits around it. The friction isn't in complexity; it's in the process commitment.
The Bottom Line
The PM playbook for the last decade was simple: remove friction everywhere. That advice is now incomplete.
In 2026, the question isn't "how do we make this easier?" It's "how do we make this more valuable to invest in?" Products that answer the second question build moats. Products that only answer the first build commodities.
Friction maxxing isn't about making products harder to use. It's about making products harder to leave.
Sources
- Mind the Product: The Case for Strategic Friction - March 2026 feature on friction maxxing
- Lenny's Newsletter: Why Frictionless Products Lose - Analysis of retention vs. onboarding speed
- Notion Annual Report 2025 - Retention data by feature adoption depth