Blog

Stop teaching users your software

Toba

Most software asks people to learn it before it helps them. We built tours, tooltips and help articles so users would remember where the settings live. Then we measured whether they did, and called it feature adoption.

People don’t want to learn your menus. They want the invoice sent, the teammate invited, the report exported. The menu was only ever the price of getting there.

AI changes who pays that price. A user can now say what they want in their own words and let the product find the way. So the useful question for a product team is whether people got it done.

Skavelo is built on that idea. It learns a web app by using it, the way a new hire would. When someone asks how, it shows them on their own screen. When they’d rather not do it themselves, it fills in the form and stops before the last click, so the user still decides what gets sent.

Recorded on a demo app: Skavelo fills in an invoice and stops on Send invoice, so the click stays with the user.

Say someone in a project tool types “invite ade@example.com as a viewer”. Skavelo offers to show them the way or to do it. If they pick Do it for me, it opens the team page, enters the email, chooses Viewer and stops on Invite. The click is theirs.

Trust comes in steps. People hand over a task once they’ve watched it done right, so Skavelo shows first, fills in when asked, and always leaves the final click to them.

The number worth watching is tasks people finished. Our Monday summary counts them, and how many of those Skavelo filled in for the user.

Your users already know what they want to do. Your product should know how.

See what Skavelo would tell your users, on your own product, before you add any code.

Start free