If you own one product
Is it delivering what it was implemented for?
The dashboard looks healthy. Everyone logs in — they have to. But use is not the same as value.
Where to begin
Two ways in. The same instrument behind both.
If you own a portfolio
Can every product owner answer that question the same way?
You are accountable for benefits across products you do not run yourself.
The adoption health check
One product. One dataset. One report.
The instrument is an Employee Experience Survey — 360° PULS, built on the Adoption Diagnostic Assessment model that came out of our research. Ten themes across all three FARO dimensions, answered by the people who have to use it.
We run it. You get the report and the cleaned data.
The survey can run inside your own environment, so responses never leave the infrastructure your data governance already covers — or from ours, if you would rather not build anything. Either way we design the instrument, and the data is yours.
Phase
How long
We do
You do
Prepare
About 2 weeks
We do
Adapt and validate the instrument for your product — two hours with the product owner, then an hour to agree the final questionnaire — and design the heads-up, invitation and reminder sequence.
You do
Name a sponsor and a survey practitioner, confirm the target groups and segments, and — if you are hosting it — build the survey in your own environment from the questionnaire we design.
Survey
1–4 weeks
We do
Track the response rate as it comes in and advise on when a reminder will help and when it will not. Short monitoring calls, not a governance layer.
You do
Send it from a name people recognise, send the reminders, and export the data to us as it accumulates. This is the part that decides how long the whole thing takes.
Analyse
About 1 week
We do
Score, band and calculate the confidence interval; break the results down by role, region and experience; read every free-text answer.
You do
Tell us what else is going on — constraints, a roadmap, initiatives already running — so the reading is not made in a vacuum.
Hand over
1 hour, or a day
We do
Present the findings and hand over the cleaned data. A one-hour handover, or a full interpretation workshop that ends in agreed priorities and owners.
You do
Bring the people who can act on it.
What you receive
- An EFI score, 0–100, with a confidence interval and an acceptability band.
- Ten theme scores, and which of them are carrying the product and which are blocking it.
- Breakdowns by role, region and experience — so the problem has an address, not an average.
- Cross-dimensional patterns: what is driving what, rather than a list of symptoms.
- Your users’ own words, sorted into the pains behind the numbers.
- Lost Value Factor — how much of the value you were promised is not coming back.
- Recommendations tied to the findings, ready to prioritise.
- The cleaned dataset, so the baseline is yours to measure against later.
Where that leaves you
- You know how much value is leaking — and where.
- You have a score you can defend, and something to compare it against.
- You know which experience gaps are costing you — in users’ own words.
- You have priorities backed by evidence, not opinion.
- You can make a pivot-or-persevere call — and show your work.
The left column is what lands in your inbox. The right column is the reason to run it.
This is not the right thing if
- You want a sentiment snapshot. This is a diagnostic, and it is built to be acted on.
- Nobody is ready to act on what it finds. The value is in the decision that follows, not in the score.
Running more than one
Two or three products together answer a question none of them answers alone.
The instrument is the same on every product, which means the results can be read against each other. Some findings turn out to belong to the organisation rather than to any one product — and those are usually the ones worth fixing first, because solving one lifts several at once.
Two or three run in parallel, in the same weeks as one.
Not always this one
When something else is the better first move.
A 360° PULS reads all three FARO dimensions as your people experience them. Sometimes that is more than the question needs — and sometimes it is less.
WorkshopVital Signs Baseline
Choose this first if nobody can say what your telemetry is supposed to show. A number without an agreed meaning is not evidence, it is decoration — and a check will not settle what your own numbers were meant to mean.
SurveyEmployee Feedback Survey — FOCUSED PULS
Choose this if the question is smaller than the product: one feature, one device, a release you have just shipped. Ask it narrowly and you get a narrow answer — and if what comes back turns out to be larger than the feature, that is worth knowing early.
MethodAdoption Metric Trail (AMT)
Choose this if the honest answer to “what was this product supposed to deliver?” is that nobody ever wrote it down. A check still tells you how the product is experienced — but the moment you want that expressed as value, gained or leaking, someone has to have decided what the value was.
What each of them is, and what it produces, is set out in the toolbox on our approach page.
Or write to info@evonate.dk