People rarely resist a tool; they resist a vague plan. Your communications should read like a senior clinician explaining a new technique: what problem it solves, what it will feel like on day one, and how you will keep patients safe while you learn. Avoid vendor jargon. Use everyday language: “We’re introducing Motics to reduce the time you spend writing and to make letters clearer for the people who rely on them.”

Explain two key concepts up front. First, time‑to‑note: the minutes from finishing a consultation to having a note you are happy to send. Lower is better because it preserves context and reduces after‑hours work. Second, push success: the proportion of notes that move to your EHR without error. High push success means fewer double‑entries and fewer messages to admin staff. Tell people you will measure both and share the trend, not just a single number.

Bring the change into existing channels rather than inventing new ones. One week before go‑live, a concise email from the clinical lead sets the tone. Place a two‑page quick start in the shared drive and on desks where notes are written. On the morning of go‑live, open clinic with a three‑minute reminder of the only three things that matter that day: check your microphone and device, use the default template, and follow the push pre‑flight if you plan to send the note to the EHR.

In week one, make progress visible with real numbers. “Average time‑to‑note fell from nine minutes to six.” Share one practical tip from champions—perhaps adding a one‑sentence Specific Instruction to referral letters. This shifts the conversation from opinion to evidence. If something goes wrong, say so plainly and state what you’re doing about it; bad news delivered clearly builds more trust than silence.

Close the loop by keeping a short change log: date, issue, experiment, decision. Link to it in every update. When clinicians can see a clean trail from feedback to action, they understand that Motics is being introduced with them, not to them, and confidence grows.