Frictionless SaaS, Chapter 23: Pattern Libraries and Proven Approaches

This is the next post in the final stretch of Frictionless SaaS: Designing Products Users Discover, Adopt, and Never Leave. The previous one was Chapter 22: AI, Automation, and the Future of Frictionless Design, where we looked at the AI-Era SaaS Framework and the Experience Moat.

Chapter 23 is different from most of the book. Up to this point, every chapter has been about frameworks — ways of thinking about a problem. This chapter is about patterns. Specific, implementable, copy-and-adapt designs that have been proven to work across dozens of successful SaaS products. If the frameworks tell you what to solve, the patterns show you what has actually worked when other teams have solved the same problem.

Why patterns, not just frameworks

Frameworks are powerful. But there is a moment in every implementation where your team stops asking "what are we trying to do?" and starts asking "okay, what does the screen actually look like?" That transition — from strategy to design to pixels — is where most activation work quietly goes sideways. You have a good framework. You brief the design team. They produce something that looks reasonable. It ships. It doesn't move the metric.

The reason is almost always the same: the team reinvented a wheel that a dozen other companies had already built and iterated on for years. They did not need creativity. They needed a pattern.

The Fast Activation Pattern Library

The first half of Chapter 23 introduces the Fast Activation Pattern Library — a collection of patterns specifically designed to get users to their first moment of value as quickly as possible. I won't walk through all six in detail here (the book does that with examples from specific companies for each one), but I will list them so you can see the shape of the library:

1. Blank Slate with Templates — never show a new user a blank canvas when you can show them a gallery of proven starting points.
2. Guided First Steps — a prescribed sequence that guides rather than restricts, nudging users toward first value instead of leaving them to wander.
3. Progress Indicator with Milestone Rewards — turning onboarding into visible, rewarding forward motion instead of an invisible maze.
4. Example Data with One-Click Cleanup — pre-populating the product so users can see what good looks like before they have to build it themselves.
5. Smart Suggestion Engine — gentle, dismissible, perfectly-timed next-step nudges that move users forward without pushing.
6. Celebration Moment — visibly acknowledging the first time something important works, because those moments matter more than most teams realize.

The chapter covers which companies pioneered each pattern and where they show up in products you already use. Slack, Notion, Zapier, Asana, Monday, Figma, and Shopify all make cameo appearances. None of the patterns are revolutionary individually. Together, they are the difference between an onboarding that converts and one that doesn't.

The Frictionless Onboarding Catalog

The second library in Chapter 23 focuses specifically on onboarding design — the Frictionless Onboarding Catalog. Where the activation library is about getting users to their first value, the onboarding catalog is about how the onboarding experience itself should be structured.

The six patterns in this catalog:

1. Role-Based Branching — the same onboarding for everyone is the same as a bad onboarding for everyone. Detect role or use case and branch accordingly.
2. Interleaved Tasks and Content — teach, apply, teach, apply. Never front-load learning and then hand users a blank product.
3. Completion Estimates — tell users how long it will take. Show progress. The simplest transparency in the book, and the one that moves completion rates the most.
4. Skip With Confidence — let users skip, but make sure they understand what they're skipping. The paradox is that the skip option increases engagement.
5. Adaptive Difficulty — adjust pace and depth based on what the product learns about the user. Like having a tutor instead of a tour guide.
6. Contextual Help Throughout — help does not end when onboarding ends. The product keeps teaching as long as the user keeps using it.

Each one gets worked examples in the book, including the specific moments where Slack, Stripe, and Duolingo get these patterns right in ways most products get them wrong. I'll note that the Skip With Confidence section is the one I get the most pushback on from teams — "but won't that hurt our completion rate?" — and it's also the one where the data is most surprising. I'll let the chapter make that case in full.

Additional high-performing patterns

The last section of Chapter 23 covers a handful of additional patterns that don't fit neatly into activation or onboarding but show up consistently in the products that users love. A few I'll mention here:

• The Undo Pattern, which looks like a feature but is really a trust-builder. Google Docs, Slack, and Figma have all built undo into the fabric of their products, and the reason is not convenience — it is that undo lowers the psychological cost of trying anything.
• The Search Everywhere Pattern, where a single global search bar finds features, settings, documents, and commands. This is what Slack's command palette, Figma's quick search, and Notion's search all do, and it's why power users can't go back to products without it.
• The Keyboard Shortcuts Pattern, which sounds small but compounds into a fundamentally different experience for your most engaged users.
• The Lazy Loading Pattern, which is how products feel fast even when they're doing heavy work behind the scenes.

How to use this chapter

I wrote Chapter 23 as a reference section more than a reading section. It is the chapter I expect teams to come back to when they are about to ship something and want to ask "has anyone solved this problem well before?" The full book covers each pattern with the specific mechanics, the measured impact, and the companies you can go look at to see the pattern in the wild — which is, frankly, the fastest way to learn any of these.

— Sho Shimoda