How I Use the Products Section on Page Flows Every Morning Before I Open Figma

About eight months ago I started keeping a small ritual before any design session. Coffee, fifteen minutes of reading, and then a quick pass through the Page Flows products library before I touched a single frame. I did not expect it to change much. It turned into one of the more useful habits I have built around my work as a designer, and I want to explain exactly how I do it because the approach matters more than the time spent.

The products section on Page Flows lets you browse complete UX flows from real, shipped apps organized by product name. You can visit website and see companies like Revolut, Notion, Duolingo, Stripe, Airbnb, Dropbox, Slack, and dozens of others with their actual recorded flows available for review. What pulled me in initially was onboarding. What kept me coming back was everything else.

Why I Do It Before Opening Figma, Not After

The order matters. When I start inside Figma, my brain locks onto execution mode fast. I am thinking about components, constraints, spacing, and existing decisions in the file. There is very little room left to question whether the approach itself is right. Spending fifteen minutes in the products library before that happens keeps the more exploratory part of my thinking alive a little longer.

I am not looking for something to copy. I am looking for evidence of how a problem gets solved in a product that has been tested against real users and shipped to millions of people. That is a different kind of input than reading a design blog or browsing Dribbble, and it puts me in a better frame of mind for the work ahead.

What I Actually Look At

Onboarding Flows for Products Outside My Industry

My current project involves a B2B productivity tool. So most mornings I pull up an onboarding flow from a consumer app that has nothing to do with productivity. Duolingo is a frequent stop. Their onboarding gets users doing the actual thing, a short lesson, before asking for any commitment. Revolut walks users through identity verification with a horizontal progress stepper and short copy at each step explaining why the information is needed. Neither of those is directly applicable to what I am building, but both carry transferable thinking about sequencing and friction reduction.

Looking outside your own category forces you to notice structural decisions rather than surface ones. When I look at Duolingo’s flow, I am not thinking about green buttons and cartoon owls. I am thinking about where they placed the first meaningful action and how many steps precede any paywall.

Checkout and Upgrade Flows for Specific Moments

When I am working on a moment that involves money or a plan upgrade, I spend a few minutes on flows from products like Stripe, Shopify, or subscription-heavy apps that appear frequently in the library. The annotation layer that Page Flows adds to these recordings is where most of the value lives for me. Seeing exactly which elements a designer flagged as significant in a Stripe payment screen tells me something about what decisions the Stripe team thought were worth calling out.

Settings Screens When the Work Gets Boring

There is a phase in every project where I am building settings screens and account management flows, and it is easy to treat those as low-stakes filler work. I use the products library specifically to fight that tendency. Slack and Notion both have settings screens in the library, and looking at how much thought goes into their layout and information hierarchy reminds me that users spend real time in those screens too.

How I Keep the Session Short and Useful

Fifteen minutes is the ceiling I set for myself. If I go longer, I start collecting without synthesizing, which is its own kind of distraction. My actual method is to open one or two specific products based on what I am working on that day, watch through one complete flow, read the annotations, and write one sentence in my notes about what I observed. That sentence does not have to be profound. It is a forcing function to process what I saw rather than scroll past it.

Some mornings I open the library and sort by a flow type rather than a product name. The library lets you filter by category, so I might look at several different products’ onboarding flows in sequence. That comparison view is often more useful than looking at a single product in depth, because patterns across multiple products tend to be more reliable signals than anything you can read into a single design decision.

The Habit Sticks Because It Pays Off Quickly

The reason I kept doing this after the first few weeks was that it started showing up in my work in ways I could point to. I caught a sequencing problem in a signup flow because I had spent time the previous morning watching how Notion separated personal and team onboarding paths. I reconsidered a modal I was about to build because I had seen how a similar moment was handled with a bottom sheet in a fintech product on Page Flows.

What surprised me most is that this practice has made me more confident in my own decisions, not less. When I can point to how several well-resourced teams handled a similar problem, I feel steadier defending a direction in review. That was not something I expected from a fifteen-minute morning routine.