You launched Notion. Some people adopted it quickly. Others are carrying on as if nothing happened.
That is normal. It is even predictable.
Resistance to change is not an anomaly in a Notion deployment. It is a constant. It appears in every team, at every deployment, regardless of how good the tool is or how solid your approach.
What varies from one person to another is the underlying reason for that resistance. And that is where most people get it wrong: they respond to the surface objection instead of the real concern.
A colleague who says "Notion is too complicated" is not necessarily saying they find the tool difficult. They may be saying they are afraid of looking incompetent in front of colleagues during the learning phase. Those are two very different problems, with two very different solutions.
What resistance is really saying
Before introducing the profiles, one fundamental principle.
Resistance to Notion is almost always resistance to change, not to the tool. People resist for four deep reasons:
- Fear of losing control ("my system works, why change?")
- Fear of appearing incompetent ("what if I can't learn this?")
- Perceived overload ("I already have too much to manage")
- Feeling that the change was imposed ("no one asked my opinion")
Address the real reason, not the stated one. That is the golden rule of managing resistance.
Profile 1: the Territorial Manager
What they say:
"My team doesn't need this. We work perfectly well as is."
What they really mean:
"I am losing control over how my team works, and I don't know what this means for me."
This profile is the trickiest to handle because they have formal authority over the people you are trying to bring on board. As long as they block, their team will not move.
Do not confront them directly. You will lose, even if you are right.
What works:
Show them a win in 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 and templates. You set the global framework; they decide how their team uses it internally.
Help them solve one of their own problems with Notion. Not a generic problem. Their specific problem: the one that costs them time or annoys them. If they see value on something that affects them personally, their resistance drops significantly.
On the Official Path, your executive sponsor can have a manager-to-manager conversation. That is often more effective than anything you can say yourself.
Profile 2: the Comfortable One
What they say:
"I have my system, it works, I don't see why I'd change."
What they really mean:
"I've invested time in my current setup and I don't want to start from scratch."
This profile is not hostile. They are simply satisfied with the status quo. And unlike the Territorial Manager, they are not actively blocking others. They are simply abstaining.
Forcing them creates resistance where there was not really any.
What works:
Do not ask them to abandon their system. Ask them to try Notion for just one thing over two weeks. The most painful thing in their current daily routine. Not a generic use case. Their specific case.
Respect their autonomy. "You can keep using Excel for your calculations. I am just asking you to try Notion for meeting notes." Reducing the scope of the ask reduces the perceived resistance.
Let time and peers do the work. When they see colleagues finding information in 10 seconds while they have been searching through emails for 5 minutes, the conversation changes.
Profile 3: the Overloaded One
What they say:
"I don't have time to learn a new tool right now."
What they really mean:
"I am afraid this will cost me more time than it saves."
This profile is often sincere. They really are busy. And their concern is legitimate: learning a new tool requires an upfront investment.
Arguing about long-term value is pointless with them. They know it could be useful. They just have no time for "could be".
What works:
Reduce the perceived investment to a minimum. "Let me show you one thing in 10 minutes, now, if you have the time." Not a training session. Not a discovery session. Ten minutes on their most urgent problem.
Do the work for them the first time. Build their first Notion space during a session together. They arrive with their problem, they leave with a working system. The investment is minimal, the result is immediate.
Show them what not changing is costing them. Not aggressively. Just an observation: "You told me you spend 45 minutes a week searching for meeting notes. With Notion, that's 30 seconds." Making the cost of the status quo visible is often more effective than promoting the benefits of change.
Profile 4: the Vocal Critic
What they say:
"Notion is too complicated, we already have too many tools, Excel is fine, and anyway it won't work."
What they really mean:
"Nobody asked my opinion, and I want everyone to know I disagree."
This profile is the most visible. They speak up in meetings, in Slack channels, over coffee. They can seem like your worst enemy.
They can also become your best ally.
Vocal critics often have legitimate concerns expressed in an awkward way. And when you genuinely listen to them and make them feel heard, they frequently switch sides with as much enthusiasm as they resisted.
What works:
Meet them privately, not in public. Debates about Notion in group meetings go nowhere. A one-on-one conversation in a relaxed context is ten times more productive.
Listen before responding. "What really bothers you about this deployment?" Let them talk. Take notes. Show that you are taking their concerns seriously.
Incorporate their feedback where possible. If their criticism is constructive, act on it and tell them you did. "You were right that the project structure was too complex. I simplified it. Is that better?"
Give them a role. Vocal critics who become champions are often the best champions. They know the objections from the inside, and they know how to address them.
What you must not do
Whatever the profile, three mistakes come up repeatedly.
Forcing. Even on the Official Path where you have authority, forcing adoption produces surface-level compliance, not real adoption. People use Notion because they have to, not because they find value in it. That does not last.
Debating in public. Discussions about the merits of Notion in group meetings reinforce resistance. They give a platform to sceptics and make others uncomfortable. Handle resistance individually, not collectively.
Giving up too early. Some people take time. Much more than you would like. As long as they are not actively blocking others, let time and peers do their work.
One last thing
You do not need to convince everyone.
80% adoption is a success. There will always be a few people who prefer their old habits, and that is acceptable as long as it does not harm how the team functions collectively.
Focus your energy on the people who can move. Leave the holdouts alone, and let time do its work.
How to measure whether Notion adoption has actually worked
Because managing resistance and measuring adoption are two sides of the same problem.
