Why don’t our email announcements actually prepare users for Microsoft’s SharePoint UI changes?

Table of Contents

The Direct Answer

Because email is the wrong channel for interface change: it arrives before the change, out of context, and competes with a full inbox. Users skim it, forget it, and meet the change inside SharePoint days later. Guidance has to appear in the app, at the moment of the change.

Deeper Explanation

Email announcements fail at change readiness because they break almost every rule of how people actually absorb procedural information. The announcement lands in an inbox that already receives dozens of other messages, is read once (if at all) with no task to anchor it, and describes a screen the user isn’t looking at yet. Procedural knowledge — the specific sequence of clicks to complete a task — is exactly the kind of information that doesn’t transfer well when it’s read in the abstract, detached from the interface it refers to. By the time the SharePoint UI change actually rolls out, the mental link between “that email I skimmed” and “this button that moved” is gone. This isn’t a discipline problem to be solved with a punchier subject line; it is a mismatch between when information is delivered and when it is needed. Memory decays steeply, with research on the forgetting curve showing memory of new information decays steeply within the first days without reinforcement, and a one-shot email delivered before a change is, by definition, no reinforcement at all. Change-management research points to the same root cause from the human side: Prosci finds the top reason people resist a change is simply lack of awareness of why it’s happening. A single broadcast, disconnected from the moment of impact, rarely builds the kind of awareness that survives to the point where the user meets the new interface and has to act.

The fix is to match the communication channel to the moment of impact rather than to the calendar. Microsoft actually gives IT a strong head start here: the Microsoft 365 Message center surfaces upcoming SharePoint changes to admins, flagging major user-impacting updates at least 30 days in advance. The gap isn’t warning time — it’s the last mile of getting that awareness to the user at the second they encounter the new interface, not 30 days earlier in their inbox. In-app messaging closes that last mile: instead of an email, you place a banner, popup, or walkthrough on the SharePoint page itself so the explanation appears exactly where and when the change does. Because it fires in context, the message carries meaning the same words would lose in an inbox, and it can persist on the page for as long as the change is still unfamiliar rather than scrolling out of view after a day. VisualSP was built for this, letting teams publish important announcements directly inside the web platform rather than hoping an email gets read. Delivered through VisualSP’s Microsoft 365 and SharePoint guidance layer, that message can also link straight into a walkthrough, turning a passive notice into active help at the point of confusion. For IT leaders who own the change-communication process, VisualSP’s IT leader solution reframes the job from “send a better email” to “deliver the message where the work happens” — which is the only place a change notice can actually change behavior.

The Research

Strategy and Actionable Steps

  • Shift the channel from inbox to interface. Move change communication out of email and into the SharePoint page, where the message appears at the moment the user meets the change. VisualSP’s in-app announcement capability is designed for exactly this shift, so the notice reaches users in context instead of in a crowded inbox. Email can still carry the strategic “why,” but the operational “what changed and what to do” belongs on the page.
  • Use Microsoft’s advance notice to stage, not to broadcast. Treat the 30-day Message center lead time as prep time to build the in-app banner and walkthrough, so guidance is armed the day the change ships rather than sent early and forgotten. The lead time is an asset only if you spend it building the in-context help, not drafting another email that will decay before rollout.
  • Pair every announcement with an action. Don’t just describe the change — link the in-app notice directly to a walkthrough that shows the user the new path. That converts awareness into immediate ability, which is what actually keeps people moving. A notice that ends in “here’s how” outperforms one that ends in “thanks for your patience.”
  • Target the message to who’s affected. Show the notice only on the pages and to the roles impacted by the change, so it reads as relevant help rather than another org-wide blast to tune out. Relevance is what earns attention that a mass email loses, and it protects the credibility of your next notice so people keep reading them.
  • Reinforce after rollout, not just before. Keep a lightweight tip available on the changed screen for a few weeks so late-returning or occasional users still get oriented. This directly counters the steep decay a single announcement can’t overcome, and it catches the part-time or returning users an email-once approach always misses.
  • Track whether the message worked. Measure views and interactions with the in-app notice to confirm the audience actually saw it at the point of use — something an email open rate can never tell you about the moment that matters. Use that signal to decide when a change is absorbed and the notice can be retired.
  • Keep one source of truth per change. When the same change is explained in an email, an intranet post, and a hallway conversation, the versions drift and users act on stale instructions. Authoring the guidance once in the app and pointing everything else at it keeps every user on the current, correct steps. It also means a later correction is a single edit, not a chase across channels.
  • Close the loop with the help desk. Share the list of upcoming changes and the in-app guidance you’ve staged with your support team so they recognize the pattern when a ticket does arrive. Tickets that slip through become the signal for which guidance to strengthen next. Over time the ticket queue itself becomes a map of where your change communication is still thin.

FAQ

Are email announcements ever useful for change management?

Yes, for broad awareness and strategic context ahead of a change — email is fine for “here’s what’s coming and why.” It fails as the mechanism that carries a user through the change itself, because that requires guidance at the moment of use, which email can’t provide. Think of it as setting the stage, not delivering the help; the two channels do different jobs and shouldn’t be asked to substitute for each other.

How does IT find out about SharePoint UI changes in advance?

Through the Microsoft 365 Message center, which posts upcoming changes and flags major user-impacting updates at least 30 days ahead. Filtering it to SharePoint gives admins a reliable pipeline of what’s changing and when, well before users see it. That lead time is exactly what makes staging in-app guidance possible instead of reacting after the tickets arrive.

What’s the difference between an email blast and in-app messaging?

An email blast is delivered to the inbox, before and away from the task, and read once. In-app messaging appears inside the application on the relevant page, at the moment of the change, and can trigger a walkthrough. So one hopes the user recalls a prior email, while the other reaches them in context exactly when they need it — and can prove they saw it through engagement data rather than an ambiguous open rate.

Why do users ignore change emails specifically?

Because they compete with a crowded inbox, lack an immediate task to make them relevant, and describe something the user isn’t doing yet. With no reinforcement and no context, the content decays quickly and the announcement is effectively invisible by the time the change lands. It’s not carelessness — it’s how attention and memory work under information overload, and no subject line fully overcomes it.

Can in-app messages become noise too?

They can if over-used, which is why targeting matters. Showing a notice only on affected pages, to affected roles, and retiring it once the change is absorbed keeps in-app messaging relevant and trusted. Used with discipline, it stays a signal rather than becoming a new form of ignorable blast, and the engagement data tells you when to pull each one so the channel never wears out.

Should we announce a change in multiple channels at once?

Spreading the same explanation across email, intranet, and chat usually backfires, because the copies drift and users act on whichever stale version they find first. Keep one authoritative source — the in-app guidance on the affected page — and let any other channel merely point to it. That keeps the operational instructions consistent and correctable with a single edit, instead of scattered across places that age at different rates.

Should the message appear before the change or when it lands?

Both, but weighted toward the moment it lands. A brief heads-up beforehand sets context, but the message that actually changes behavior is the one on the page when the user meets the new interface. In-app delivery lets you keep a tip live on the changed screen for as long as it’s still unfamiliar, which is what carries users through — something a single pre-change email can’t do.

See how teams solve this

Get a Demo

Table of Contents