I had a project catch-up with a client recently, a week after we'd run the first proper training session with one of their teams. The session had gone well. People were engaged, they asked good questions, and they left understanding how the new setup worked.

Then their project lead said something that has stuck with me since.

He said the training only counts if people can recall it instantly. Because the moment someone is busy, halfway through a task, with three other things demanding attention, and they can't remember whether this message belongs in a channel or a chat, they do not stop and go looking for the answer. They get frustrated, and they do it the old way. The old way requires no thinking at all.

He didn't ask for more training sessions. He asked for a cheat sheet. One page. When to @mention someone. Why you post in a channel rather than firing off a chat. Where files live. The handful of rules that decide whether the whole thing survives. And he wanted it pinned to the top of the team, where nobody has to go hunting for it.

Microsoft 365 training does not stick because people forget the new rules under pressure and revert to the old habit, which takes no effort to recall. The fix is a one-page cheat sheet covering the five or six decisions people make every day, such as when to @mention, when to post in a channel instead of a chat, and where files belong. Pin it to the top of the team so it is visible at the exact moment someone is deciding what to do. Training teaches the rule. The pinned cheat sheet is what makes the rule survive a busy Tuesday three weeks later.

Here is why this works, what belongs on the page, and how to keep people using it.

Most rollouts treat the training session as the finish line. Get everyone in a room, walk them through the new structure, answer the questions, tick it off the plan. Adoption sorted.

It isn't, and the reason has nothing to do with whether people liked the session. It's about what happens on an ordinary Tuesday, three weeks later.

Picture the person. They have a deadline this afternoon. Something has gone wrong that they need to sort in the next twenty minutes. They need to get a quick message to two colleagues. And somewhere in the back of their mind is a faint memory that there was a new rule about this, something about posting in the channel rather than starting a chat, and they cannot quite remember what it was or why.

They have a choice. Stop, go looking, work out the right way, do it properly. Or send the chat, because they have sent a thousand chats, and it takes zero seconds of thought.

Under pressure, people choose the cheap option over the correct one, every time. Call it laziness if you like, but it is what all of us do when we are busy and the right path has a cost attached.

Adoption is decided in those small moments, hundreds of times a week across a business, and none of them happen during your training session.

> Want the full method for deciding what lives where in your Microsoft 365 setup, including how to make the rules stick? The Microsoft 365 Chaos Cure lays the whole thing out, step by step: [get the Chaos Cure here](https://www.meetimeservices.com/chaos-cure).

Here is the shift that changes how you plan a rollout. Recall is the thing you are training for.

Everyone in that session understood. Understanding is easy, and there was plenty of it in the room. Recall is the scarce resource, and it decays fast. A week later most of the detail is gone. A month later people remember roughly that things changed and very little about how.

If you accept that, the job becomes obvious. Reduce what people have to remember, and put what's left within reach at the moment they need it.

That is the whole logic of the cheat sheet. It takes the rules out of people's heads and puts them somewhere they are looking anyway. It turns a memory problem into a glance.

And there's a second benefit that matters just as much. When the rule is written down and visible, it stops being a matter of opinion. Nobody has to argue about whether this should be a chat or a post. The page says. That takes the social awkwardness out of correcting each other, which is one of the quiet reasons new ways of working collapse: people notice a colleague doing it the old way, decide it isn't worth the friction of saying so, and let it slide.

Keep it to one side of A4. The temptation to be thorough is the thing that kills it, because a five-page guide is a document nobody reads, and a one-page guide is a thing people glance at.

Cover the decisions people make every single day. In most small businesses that means:

If you need a specific person to act, name them. If you need the whole team to see it, mention the team. If it is information nobody has to do anything with, mention nobody. This single rule fixes most of the "I didn't see it" problem, because it tells people what a notification actually means.

The default that changes everything. If the conversation relates to the team's work, it belongs in the channel where the team can see it. A private chat is for the things that are only ever relevant to those two people. Write the rule in one line and give one example of each.

Not attached to messages. Not on someone's desktop. In the files area of the channel the work belongs to. One line, no exceptions.

The rule that keeps a channel readable. New topic, new post. Response to an existing topic, reply underneath it.

Give people the one place to ask, and name the people who will answer. A rollout without an obvious "I don't know what to do" route sends everyone back to email, quietly.

That's it. Five rules, one page. If you find yourself writing a sixth and seventh, ask honestly whether they affect what someone does every day. If they don't, cut them.

A cheat sheet saved in a folder is a cheat sheet nobody opens. The whole value is proximity: it needs to be in the place people are standing when they make the decision.

Pin it to the top of the team, in the general area everyone sees. If your business has an intranet, put it there too, and link to it. The test is simple. If someone has to remember that the cheat sheet exists in order to find it, you have replaced one memory problem with another.

You should also point at it, repeatedly, in the first few weeks. When someone does something the old way, reply with a link to the page and nothing else. No telling-off, no lecture. Do that ten times and the page becomes the reference everyone reaches for. Do it never, and the page becomes wallpaper.

Think of the cheat sheet as the visible surface of a bigger agreement your business makes about where things belong: which conversations live in channels, which live in chat, where files go, what a mention means. That set of shared rules, so nobody has to guess where something belongs, is what I call a What Goes Where Agreement.

Most businesses have that agreement in their heads, in various incompatible versions. Writing it down as one page is what turns it from an intention into something people can follow. If you want to see how the rest of the thinking fits together, the [full guide to organising Microsoft Teams for a small business](https://www.meetimeservices.com/blog/how-to-organise-microsoft-teams-small-business) walks through structure, channels, and where each kind of work belongs.

Here is the awkward part. Almost every rollout skips the cheat sheet, and the reason is that it feels too simple to matter.

You have spent weeks designing a structure. You have run sessions, wrangled diaries, handled objections. Against all of that, a single side of A4 with five bullet points looks like an afterthought. It doesn't feel like the thing that decides the outcome.

But look at what the alternatives cost. More training sessions cost days of everyone's time and decay just as fast. Policing people costs goodwill. Waiting for habits to form on their own costs you the rollout, because the old habit is already formed and is winning by default.

The page costs an hour. It is the highest-return hour in the whole project, and it is the one people leave out.

Why doesn't Microsoft 365 training stick?

Because training creates understanding, and daily behaviour runs on recall. People understand the new way perfectly well in the session, then forget the detail within a couple of weeks. When they are busy and cannot recall the rule, they revert to the old habit, which takes no thought at all. The fix is to reduce what people have to remember and put the remaining rules somewhere visible at the moment of the decision.

What should a Microsoft Teams cheat sheet include?

Keep it to one page and cover only the decisions people make daily: when to @mention a person or a team, when to post in a channel rather than start a private chat, where files should live, how to reply in a thread rather than starting a new one, and where to go when you're stuck. Anything that does not affect daily behaviour should be left off.

Where should I put the cheat sheet so people actually use it?

Pin it to the top of the team so it sits where people already are, and add it to your intranet if you have one. If someone has to remember the cheat sheet exists in order to find it, it will not get used. In the first few weeks, respond to old-way behaviour by linking to the page rather than by correcting people, so the page becomes the shared reference.

How long should a new ways of working guide be?

One side of A4. Long guides feel more thorough and get read less, which makes them worse than useless because they create the illusion that the job is done. If you are on your seventh rule, ask whether it affects what someone does every day. If it doesn't, cut it.

Is a cheat sheet enough on its own to make a Microsoft 365 rollout stick?

No, it works alongside good structure and clear training, and it needs someone to keep pointing at it for the first few weeks. What it does is close the gap between the training day and ordinary working life, which is where most rollouts quietly fall apart.

If you're rolling out a new way of working in Microsoft 365 and you can already feel people drifting back to the old habits, there are two ways I can help depending on how hands-on you want to be.

If you'd like to sort it yourself, the Microsoft 365 Chaos Cure lays out the whole method, including the structure, the rules, and how to make them stick. [Get the Chaos Cure here](https://www.meetimeservices.com/chaos-cure).

If you'd rather have a second pair of eyes on your specific rollout, and the wider question of how your teams work together, it might be worth a conversation to see if we'd be a good fit. [Book a discovery call](https://www.meetimeservices.com/how-we-can-help) and we'll look at where your adoption is leaking and what would fix it.

---

Gavin Jones is the Founder and Director of MeeTime Ltd., where he helps small and medium businesses get far more out of the Microsoft 365 tools they already pay for. He has run dozens of Microsoft 365 assessments and implementations for SME teams, and writes and records regularly on making work simpler.