For consultants and managed service providers

Prove the implementation actually got adopted

Baseline the client's team, re-ask exactly the same questions on a schedule, and hand management a report where every number traces back to an answer or a file.

Start free with one engagement See how it works

No card. Your The Art of Service account signs you straight in.

25–40

questions, curated by you from a corpus of 1.88 million

4 min

for the client's team, on a phone, with no login

Monthly

the same frozen questions, so the comparison holds

Every figure

footnoted to the responses or the file it came from

Six months later, somebody asks whether it worked

The tool is installed, the project is closed, the sponsor has moved on, and the honest answer is that nobody measured the starting point. So the conversation becomes opinion against opinion, and the programme loses its funding to whoever argues better.

Adoption Evidence measures it instead. It asks the people doing the work a short, fixed set of questions, repeats exactly those questions on a cadence, and shows the movement per practice area. It is the difference between believing the rollout landed and being able to show it.

The part nobody else does

Almost nobody sets a baseline. The work starts because something is obviously broken, and measuring how broken feels like a delay to fixing it.

So upload what survived from before the change: the ticket export, the shared workbook, the process note somebody wrote. The system reads what is actually in those files, proposes a starting score for each question, and quotes the evidence.

“no column matching category among: Ticket ID, Opened, Summary, Assigned To, Status”
becomes 1 out of 5 on incident categorisation, with the file named.

You review every score and override anything you disagree with. It is labelled reconstructed everywhere it appears, because an evidenced estimate presented as a measurement would be worth less than nothing.

What you never have to worry about

It never emails your client

The report is a draft you edit and send yourself. The relationship is yours.

Individual answers stay private

You see the team average. An area with too few answers is suppressed rather than scored.

No fabricated numbers

A figure that cannot name its source cannot be put in a report. That rule is enforced in code, not by habit.