Move from optional to required

Before you require anything, the process should be documented, the quality loop running, and training tested on someone outside the pilot. Then give notice with a real date and hold to it.

Require the outcome, not the specific tool. Expect three kinds of holdouts and treat them differently: a skills gap (coach it), a real constraint (adjust or grant an exception), or a genuine objection (listen first, since they may have spotted something). Repeat your pledge at this moment, without being asked.