
We crossed two hundred Project OS onboardings this quarter. Somewhere around the fortieth, we realized we had been thinking about them wrong: an onboarding is not a support cost. It is a two-hour usability session with a motivated participant.
So we started treating them like research. Every onboarding gets a structured note: where the client hesitated, what they asked, what they tried before asking. Two hundred sessions later, the patterns are impossible to ignore.
The first ten minutes decide everything
Clients who imported real project data in the first ten minutes activated at nearly triple the rate of clients who started with a demo workspace. Nobody falls in love with sample data.
That single finding reordered a quarter of roadmap: import tooling went from backlog item to the most invested-in surface of the product.
Feature requests tell you what clients can articulate. Onboardings show you what they cannot.
Questions are roadmap
We tag every question asked during onboarding. When the same question crosses twenty occurrences, it stops being a training issue and becomes a design defect — the interface failed to answer it.
Twelve of the last twenty Project OS releases traced directly back to an onboarding note. The roadmap did not get shorter. It got truer.



