The Onboarding Trap: Naming Features Instead of Showing Value
Lauryn cautions against the most common onboarding trap — employees building what they think customers want. One pattern is naming features: a tooltip that announces "this is Automations" and explains what it is doesn't help a user who doesn't yet know if it's relevant to them. Instead, explain how the feature is relevant, or better, enable a one-touch turn-on that does some of the work for them.
- Teams build what they think customers want, not what customers actually want
- Naming a feature is an announcement of what the company built, not an aid to the user
- Explain how a feature is relevant, or enable one-touch turn-on that does the work
- Focus on contextual application and driving toward an outcome, not educating on a name
- Smart-defaulting — starting to do it for them — beats asking do-you-want-this
“we've named a feature but it's really sort of an announcement of something awesome that airtable built rather than an application that can help educate…”