Progress Indicators
Establishing structural trust during multi-step flows. Why arbitrary percentages destroy credibility.
An archival pattern library and engineering deep-dive into the mechanics of software onboarding, empty states, and setup UI. Built for product engineers who despise generic templates.
The industry standard of slapping a Joyride.js tooltip over every navigation item is a failure of structural design. When you force a user to click "Next" seven times before they can input data, you are not educating them; you are creating cognitive friction.
True onboarding happens in the empty states. It happens in the carefully constrained sequence of initial configurations. It happens when you deliberately introduce friction to increase long-term retention.
Establishing structural trust during multi-step flows. Why arbitrary percentages destroy credibility.
Designing the void to force user action. Transforming blank canvases into primary conversion levers.
Architecting complex setup without cognitive overload. The mathematical limit of user patience.
When to defer password creation. The hidden cost of aggressive SSO gating.
Requesting hardware access (camera, location) without triggering immediate denial.
Why floating UI is a structural crutch, and how to design self-evident interfaces instead.
Structural UI refers to the embedded architectural constraints of an application, as opposed to cosmetic overlays. A tooltip is cosmetic. A setup wizard that blocks navigation until a database is connected is structural.
We believe that activation cannot be solved by marketing. It must be solved by engineering.
Quantitative models for onboarding mechanics. Stop guessing; measure the friction.
Every field you ask for before the user receives their first unit of value reduces day-30 retention by roughly 2.5%.
Friction is not inherently evil. It is only evil when it is arbitrary. When friction is justified (e.g., connecting a secure API key), users tolerate it.
The application you designed exists only for power users. New users interact exclusively with your empty states. Design them first.
| Metric (B2B SaaS) | Median | Top Quartile |
|---|---|---|
| Signup to Day-1 Activation | 14.2% | 31.5% |
| Email Verification Dropoff | 22.0% | 8.4% |
| Avg Time to 'Hello World' | 14m 30s | < 3m |
Forcing users to swipe through abstract illustrations detailing the "value proposition" they already agreed to by downloading the app.
Requesting push notification privileges before the user has received a single unit of value from the platform.
Dumping a user into a complex, multi-panel dashboard with no data, no clear next action, and a tiny "Create New" button hidden in the header.
"We spent six months redesigning our product tour to be more friendly. Activation went down 4%. We then deleted the tour and added sample data to the dashboard. Activation went up 18%."— Lead Product Engineer, Series C SaaS
Optimized for immediate dopamine. Low intent, high volume. Requires zero-friction SSO, immediate visual feedback, and gamification to retain attention spans measured in seconds.
Optimized for structural trust and data ingestion. High intent, lower volume. Can tolerate (and sometimes benefits from) intentional friction during complex configuration steps.
Aggressive use of modal overlays and forced 12-step tours.
Bypassing blank slates by forcing users to start from pre-configured community templates.
Integrating education directly into empty states and utilizing intentional friction for high-intent actions.
Adjust the slider to see the compounding negative impact of forced product tours on day-1 retention.
We need read access to analyze your commit history and generate the developer velocity dashboard.
// Good onboarding is like a well-designed REST API. // It shouldn't require a 40-page PDF manual (tooltips). // It should return clear 400 errors (validation) and provide sensible defaults. POST /api/v1/workspaces Body: { "name": "Engineering", // Required (Wizard Step 1) "region": "us-east" // Defaulted (Hidden from UI) } Response: 201 Created
Why making it harder to sign up can dramatically increase long-term retention. A study in forced investment.
How the pursuit of zero-friction onboarding creates confused, uninvested users who abandon the product on day two.
Deconstructing the most critical and frequently neglected view in enterprise software design.
The engineering of activation is a mathematical discipline. Use the tools, implement the patterns, and watch your day-1 retention compound.
Open the Toolset