The most honest way to measure adoption is to look at behaviour rather than at a survey. Three indicators are enough for most teams: the active usage rate — the share of users who actually log in and produce work in the tool; the number of exceptions outside the tool — work that bypasses the process and gets done the old way; and process cycle time, the change in how quickly a piece of work runs from start to finish.
Together the three show whether the tool has genuinely been embedded in the work, and they are more reliable than declared satisfaction. For the measurement to mean anything you need a baseline taken before the tool goes live and the same metric tracked at regular intervals. Low adoption usually has little to do with the quality of the tool and a great deal to do with weak integration into the process and insufficient training, so the metrics should be read alongside corrective training and a simplification of the workflow.
Shall we apply this matter to your situation?
Tell us your specific situation in a few sentences; we'll assess it with the right team.