You launched Notion. Some people adopted it quickly. Others are acting like nothing happened.
That's normal. It's even predictable.
Resistance to change isn't a glitch in a Notion rollout. It's a constant. It shows up in every team, in every rollout, regardless of how good the tool is or how solid your approach is.
What changes from person to person is the deeper reason behind that resistance. And that's where most people get it wrong: they respond to the surface-level objection instead of the real concern underneath it.
A colleague who says "Notion is too complicated" isn't necessarily saying the tool is hard. They might be saying they're afraid of looking incompetent in front of colleagues while they're learning. Those are two very different problems, with two very different answers.
What resistance is really saying
Before going through the profiles, one foundational principle.
Resistance to Notion is almost always resistance to change, not to the tool. People resist for four deep-seated reasons:
- Fear of losing control ("my system works, why change it?")
- Fear of looking incompetent ("what if I can't learn this?")
- Perceived overload ("I already have too much to manage")
- Feeling imposed on ("nobody asked for my opinion")
Respond to the real reason, not the stated one. That's the golden rule of managing resistance.
The 4 resister profiles and how to win them over
Profile 1: the Territorial Manager
What they say:
"My team doesn't need this. We're doing fine as it is."
What they actually mean:
"I'm losing control over how my team works, and I don't know what that means for me."
This profile is the trickiest to handle because they have formal authority over the people you're trying to bring on board. As long as they're blocking, their team won't move.
Don't confront them head-on. You'll lose, even if you're right.
What works:
Show them a win from a comparable team. Not a promise. A concrete result, with numbers, from a team they respect.
Give them control within the structure. Their team can have its own Notion space, with its own conventions, its own templates. You set the overall framework, they decide how their team uses it inside it.
Get them to solve one of their own problems with Notion. Not a generic problem. Their problem. The one that eats their time or annoys them. If they see the value on something that affects them personally, their resistance drops significantly.
On the Official track, your executive sponsor can have a manager-to-manager conversation. That's often more effective than anything you can say yourself.
Profile 2: the Overwhelmed
What they say:
"I don't have time to learn a new tool on top of everything else."
What they actually mean:
"I'm already overloaded, and every new thing I'm asked to learn, however useful, just adds to a pile I can't manage already."
With this profile, pushing harder confirms exactly what they fear: one more unmanageable load. The more you insist on how important Notion is, the more you validate their fear.
What works:
Don't sell Notion as one more tool. Show them what they get to drop in exchange: a tool they stop using, a sync meeting that disappears, a manual report they'll never have to compile by hand again.
Give them one tiny task, not a full learning curve. A single database that replaces the spreadsheet they hated maintaining, not a rebuild of their entire workflow.
Don't train them in a group with everyone else. A 15-minute one-on-one session on their own task beats an hour of general training they sit through while thinking about their backlog.
Profile 3: the Loyalist to the Old Tool
What they say:
"We've always done it this way and it works, why change?"
What they actually mean:
"I'm good at the current tool. With Notion, I start from zero, and I don't want to be the least competent person on the team on a tool I didn't choose."
This profile often confuses attachment to the tool with attachment to their own expertise. The first is negotiable. The second goes straight to the fear of losing face.
What works:
Recognise their expertise instead of dismissing it. They know the old tool's limits better than anyone, use exactly that knowledge to help co-design the structure that replaces it.
Allow a period of overlap. Don't cut off the old tool on launch day, a hard cutover hardens resistance instead of defusing it.
Offer them private training rather than a group session, to avoid exposure in front of junior colleagues who have no such history to unlearn.
Profile 4: the Overlooked
What they say:
"Nobody asked my opinion, this is just being imposed on me."
What they actually mean:
Nothing about Notion itself. Their objection is about the process, not the content: they feel left out of a decision that affects them, and push back on principle, even if the tool is objectively better than the old one.
With this profile, improving the case for Notion changes nothing. The problem was never Notion.
What works:
Give them a real choice on something non-critical: how a database is named, the order of columns, the note-taking template. It doesn't matter that the core structure is already decided, what matters is that they had a say on something real.
Include them in a retro after the pilot, and ask for their opinion first.
Publicly credit one of their suggestions once it's implemented, even a minor one. That's often enough to defuse a resentment that was never really about the tool.
Is a resistant profile blocking your rollout?
A 1-hour session to analyse the situation and leave with a concrete strategy to clear the blocker.
Article 5 of 7 · See all articles in this guide →