Rethinking How Cloudflare for Teams Onboards New Users

When Cloudflare for Teams launched in January 2020, the promise was straightforward: deliver a Zero Trust security solution that combines the power of the biggest service providers with the ease of use that smaller organizations need. The product pairs two pillars — Access, which secures inbound connections by verifying identity at the door of your applications, and Gateway, a Secure Web Gateway that protects users as they browse the Internet.

But building the tool is one thing. Making it genuinely simple to use is another, and Cloudflare admits that early on the Teams Dashboard fell short of that goal.

From Feature Shop to Intentional Design

The rapid pace of shipping features throughout 2020 came with consequences. The teams behind the dashboard fell into what they call a "Feature Shop" dilemma: too much focus on what they were building, not enough on why. The result was a fragmented user interface where individual features worked fine in isolation, but didn't connect into a seamless, unified experience.

A concrete example came early with onboarding. Cloudflare for Teams was meant to be a single pane of glass for security policies, yet users had to onboard to Access and Gateway separately. There wasn't even an onboarding path for Access. The initial reaction was to simply build one — but that approach created a fork in the road rather than a unified entry point.

The design team framed the problem as a party invitation: you give guests the address, they arrive, and discover the building is a duplex. Which door do they knock on? The confusion isn't their fault, it's the fault of the architecture.

Asking Why Before What

The shift in approach was to lead with design. Rather than handing the design team a mockup and asking them to prototype it — a practice they call "solution pollution" — product and design now start by gathering contextual data and validating the problem space with the people it affects.

The classic illustration: if you say you need a fast car, you're likely to get a car. But if you say you need to get from point A to point B as quickly as possible, you might end up with something entirely different — a bike, a scooter, or a novel alternative.

Applied to onboarding, this reframing produced a different answer than the original "just build an Access flow" instinct. Instead of two divergent pathways, the team created one unified Cloudflare for Teams onboarding flow.

A Three-Step Onboarding and a Quick Start Guide

The redesigned flow rests on two principles: preparing users for success and emphasizing time-to-value. Research showed that early users felt overwhelmed by required configuration and reached their "Aha!" moment later than they should. The fix was to truncate the initial process to three steps:

  • Welcome to Teams
  • Create a Team Name
  • Pick a Plan

After that, users land in an "inboarding" flow, a Quick Start guide. By providing a variety of "Starter Packs" that automate much of the manual setup, the guide lets users get value out of Cloudflare for Teams almost immediately.

What Comes Next

Cloudflare plans to keep extending the Quick Start guide with more robust starter packs and opportunities for continuous learning. Longer term, they're looking at adding intelligent recommendations based on the user's environment.

The same principles behind the Quick Start guide will be applied elsewhere in the UI this quarter, including Empty States and Overview pages. The underlying goal is to encourage healthy debate early in the development process, forcing the team to map risks to controls and build every feature with intentionality.