Tooltips feel helpful to the team that ships them and faintly condescending to the user who receives them. A tooltip that fires when you didn't ask carries an unspoken message — you should have figured this out — and interrupts the user's actual task to deliver guidance they may not need. Used well, tooltips are fine. Used as an activation strategy, they're a broadcast wearing a helpful costume.
The interruption problem. A tooltip decides, on the product's schedule, that now is the moment to teach you something. But the user is mid-task, with their own intent, and the tooltip cuts across it. The good case is they dismiss it; the common case is a low-grade friction that accumulates into the sense that the product is fussy.
The relevance problem. Tooltips fire on triggers, not on understanding. They can't tell whether you're confused or perfectly fine — so they interrupt the users who didn't need help and miss the specific confusion of the users who did. They're calibrated to the average user, which means they're wrong for most individual ones.
The conversational alternative. The difference between a tooltip and a conversation is who's in control. A tooltip interrupts on the product's terms; a conversation responds on the user's. A user who can ask a question the moment they actually have one gets help that's relevant by definition — because they asked for it — without being interrupted when they didn't need it. That's the inversion: from "let me tell you something" to "ask me anything."
Frequently asked questions
Are tooltips bad for onboarding?
Used sparingly they're fine; used as a primary activation strategy they interrupt users who don't need help and miss the specific confusion of those who do, because they broadcast on triggers rather than responding to understanding.
What works better than tooltips for activation?
A conversation the user controls — help available the moment they actually have a question, relevant by definition because they asked.