Get your first user.

The first screen told me what this was for. I didn’t have to hunt for a headline, which is the usual miss. The primary action sat where I expected it, and the empty state actually explained the job instead of showing me a blank rectangle.

Copy was plain. I knew what would happen if I clicked. Hierarchy held up once I was inside a real flow — labels matched the language I’d use, not the language of the feature. A couple of micro-interactions made it feel considered. Nothing flashy, just the sense that someone had sat with the defaults instead of shipping the first pass.

Settings lived behind a label I wouldn’t have used. I spent a minute looking for something that was one click away. I also bounced off the first error state — it told me something was wrong without telling me what to do next.

Onboarding asked me to name a workspace before I’d done anything worth naming. I didn’t have a reason to care yet, so I guessed, and then the rest of the product kept using a name that didn’t mean anything to me. Search results didn’t highlight why they matched. I assumed the thing I wanted wasn’t in there and went looking somewhere else.

Name the primary button after the action, not the feature. Lead with the empty state you want filled in, not a blank canvas. Put settings under a word a stranger would actually look for.

Don’t ask for a workspace name until I’ve created one piece of work. Make the first error tell me the fix, not just the failure. If search is a way in, show the match in the result — a title without context is a dead end. And cut one step from the first-run flow. I would have stayed longer if the product had let me do the job before it asked me to set it up.