Six small bugs that made a new user's first session feel broken.

We were about to hand a brand-new workspace to a group of people who had never used it. Before we sent the invitations, we sat down and went through the very first experience ourselves — not by reading the code, but by clicking through it the way a complete newcomer would, and writing down everything that felt off.

We found six things wrong. On their own, none of them was a crash. None of them would have shown up if we'd demonstrated the product, because in a demo you start from an account that's already set up and working. But stacked together, they made the first few minutes feel like the product was broken before the new person had even done anything.

What was actually wrong

1. Accepting the invitation dropped you straight onto the chat screen. The short to-do list that tells a newcomer what to do first lived on a different page — the home page — so the new person sailed right past it and never saw it.

2. The "Forgot password?" link sent you to one specific internal email address that meant nothing to an outsider. Helpful to exactly one person on earth, baffling to everyone else.

3. The home page showed three "coming soon" boxes. To us, those read as a preview of what's next. To a first-time visitor, they read as a half-finished product.

4. The blank starting screen said nothing at all. A fresh workspace has no messages in it yet, which is correct — but the empty screen gave no hint about what to do with that emptiness.

5. The welcome screen never actually explained what the product was. It assumed you already knew why you were there.

6. The little progress checklist ticked off a step too early — the instant you started to do something, before you'd actually finished it. So it congratulated you for a thing you hadn't done, which is worse than not keeping score at all.

The pattern under the list

Look at those six again. Not one of them is something you'd ever bump into from an account that's already up and running. We use the product every day, so we never arrive cold. We know what it is, so the missing explanation costs us nothing. We already have messages, so we never see the blank screen. Our own checklist was finished months ago.

Every one of these bugs lived in the gap between "the system works" and "a stranger can tell that it works." That gap is invisible to the people who built the thing. It is the only thing the newcomer can see.

The person who built it never lands on the screen that breaks for the newcomer. That is exactly why the person who built it should never be the one who signs off on the first run.

What we changed about how we check

The fix itself was undramatic — all six went out together and we confirmed them on the real, live product before calling it done. The method is the part worth keeping.

If you check your own onboarding while logged in as an administrator, it will pass. You'll tick every box, because every box was built for you and your account already meets it. The only check that catches these bugs is the one where you create a genuinely empty account, accept the invitation as if it were the first message you'd ever had from us, and refuse to lean on anything you already know.

We now treat that as a separate, required step before any new group of people gets access. Not a code review. A stranger's first ten minutes, done honestly by someone who isn't allowed to pretend they already understand it.

It's slow, it feels faintly ridiculous, and it's the cheapest bug-finding we do.

Under the hood

The product was a fresh agent workspace about to be opened to a group of first-time users. The six issues, in product terms:

1. Invite-accept routing. The invitation-accept flow redirected to /chat rather than the dashboard, which is where the activation checklist component is mounted. The checklist was never even rendered for the new user.
2. Hardcoded support address. The forgot-password link pointed at a single internal support email baked into the markup, rather than a generic support route.
3. Placeholder cards. Three "coming soon" cards were live on the dashboard — fine as internal roadmap stubs, wrong as the first thing an external user sees.
4. Empty state. The no-channels / no-messages state was technically correct for a new workspace but had no copy or call-to-action.
5. Welcome screen. No product explanation in the first-run welcome view.
6. Premature checklist completion. The activation step keyed on the user typing an @ character, marking the "mention someone" step complete before a mention target was actually resolved.

All six fixes shipped in a single change, deployed and then verified against the live site (not just locally) before sign-off. The takeaway is the audit method rather than any one fix: an onboarding audit run from an admin account passes by construction, because the admin account already satisfies every gate. The only audit that surfaces these is one performed from a genuinely empty, freshly-invited account by someone disciplined enough not to fall back on prior knowledge of the product.