Guidance is not enough
Digital adoption was built to answer “Where do I click?” The questions people ask at work have moved on.
For most of the last decade, digital adoption meant one thing: the walkthrough. A small box appears on the screen, points at a button and says “click here”. Then the next box, and the next.
Walkthroughs work. They are still the clearest way to show someone an unfamiliar process inside an application. But if you sit with people as they work, you notice that “Where do I click?” is only one of the questions they ask, and rarely the hardest.
The three questions people actually ask
Watch a branch officer opening an account, a buyer raising a purchase order or a manager approving a leave request. Their questions fall into three kinds.
“How do I do this?” This is the walkthrough’s territory: the sequence of screens, fields and buttons.
“What is the rule?” Which documents does this customer type need? Which cost centre should this go to? Am I allowed to approve this amount? The screen rarely answers these. The answer sits in a policy, a circular or a procedure document, and often only in someone’s head.
“Can you just do this for me?” Checking the status of an invoice, copying the same data into a second system, chasing an approval. Nobody needs to learn these tasks. They need them done.
A walkthrough answers the first question well. It can’t answer the second or the third.
Why three separate tools fail
Most enterprises already try to answer all three. They have a training platform or walkthrough tool for the first, an intranet or knowledge base for the second, and an automation project somewhere in IT for the third.
The trouble is that these live apart. The knowledge base doesn’t know which screen you are on. The walkthrough can’t tell you the policy behind a field. The automation can’t explain what it did or why. Each one asks the employee to stop work, find the right tool and start again.
So people fall back on the fastest channel they know: asking a colleague. That works until the colleague is busy, on leave or has moved on.
Guide, Pulse, Act
The next generation of digital adoption is defined by three capabilities working as one.
Guide. Show people the next step, inside the application they are using, at the moment they need it. Walkthroughs, tooltips and in-context tips, shown to the right roles and kept current as systems change.
Pulse. Bring the company’s own approved knowledge to the moment it is needed. People ask in plain language and get an answer drawn from your policies and procedures, with the source, and only from content they are allowed to see.
Act. Turn a request into action across the systems a team already uses, within the permissions it already has. Routine, rules-bound work gets done, not explained.
What matters most is not the three capabilities on their own. It is that they share one context: who the person is, what they are allowed to do, which application they are in and what they are trying to finish. An answer can lead straight into a walkthrough. A walkthrough can hand off to an automation. A request typed in Microsoft Teams draws on the same knowledge as a question asked inside SAP.
Three questions to ask any vendor
If you are evaluating digital adoption today, ask these of any platform, including ours.
When a user asks a policy question in the middle of a task, where does the answer come from, and can they check it?
When a process spans two or three applications, does the guidance follow it, or stop at the edge of one?
When a task is purely routine, can the platform do it for the user, safely, within their existing permissions?
Guidance is where adoption starts. It can no longer be where it ends.
Next step: See guidance, answers and action working together on one of your own applications.
Rather talk it through?
Thirty minutes on your own screens, with your own questions. No slideware.