You are convinced that Notion can change the way your team works.
Problem: nobody else is yet.
No allocated budget. No official mandate. A leadership team that hasn't said yes, but hasn't said no either. And colleagues who get along perfectly well with their Excel spreadsheets, email threads and sticky notes.
Welcome to the Guerrilla Path.
It is not the fastest path. It is the path suited to your situation. And when it is executed well, it produces something the Official Path never generates on its own: adoption that comes from people themselves, not from a mandate imposed from above.
The logic of the Guerrilla Path
Before diving into the phases, you need to understand the philosophy underpinning this entire path.
You cannot force adoption. You have neither the authority nor the budget for that. What you can do is make Notion so useful for a few people that everyone else wants in.
The engine of the Guerrilla Path is FOMO.
Not constraint. Not mandatory training. The fact that your colleagues see people saving time, finding information in 10 seconds, and finally escaping the email flood. And they think: I want that too.
Your job, at every phase, is to create those visible moments.
Phase 0: prepare the ground (3 to 4 hours)
Before showing Notion to anyone, you need three things.
A concrete problem to solve
Not "improve team collaboration". A specific, painful problem that you or your team experiences daily. Meeting notes that disappear. Project tracking that lives in five different places. An onboarding process that depends entirely on one person's memory.
Choose a problem you can solve with Notion in under a week. Not the most important problem. The most demonstrable one.
Internal allies
Identify two or three people in your professional circle who fit this profile: frustrated with current tools, open to trying new things, and with enough informal influence that their adoption is visible.
Do not look for tech enthusiasts. Look for people everyone respects who suffer from the problem you want to solve.
Your own usage
Before convincing anyone else, use Notion yourself for two weeks. For your meeting notes, task list, project tracking.
Two reasons. First, you will understand the real friction points before imposing them on others. Second, when someone asks "what is that thing you are using?", you will have something concrete to show.
Do not talk about Notion. Show it.
Phase 1: the discreet pilot (30 days)
You have your problem, your allies, and your own usage. Time to launch a pilot.
The rules of discreet mode:
- No announcement to the whole team
- No asking leadership for permission
- Volunteers only
- One problem, one solution
Approach your allies individually, never as a group. The script is simple: "I have been using something to organise [specific problem] and it genuinely helps. Do you want to try it together for a month? Nothing official, just a test."
The key to the pilot is building with them, not for them. Run a one-to-two hour working session where you build the system together. They contribute ideas, you guide the construction. By the end of the session, the system belongs to them as much as it does to you.
A co-built system is ten times more likely to be used than one delivered ready-made.
What you document during the pilot:
- Before-and-after screenshots
- Simple metrics: time saved, information found faster, meetings better prepared
- Verbatim quotes from your allies: what they said about the problem before, what they say now
At the end of 30 days, you have either a solid success story or valuable lessons. Either way, you move forward.
Phase 2: pitching leadership (3 to 4 hours of preparation)
Your pilot worked. You have proof. Time to step out of discreet mode.
An absolute rule before pitching: never present without real data. You have one chance to convince. Just one. Do not waste it on theoretical promises.
What your pitch must contain:
- The initial problem, expressed in business terms (time lost, missing information, coordination errors)
- What you built and with whom
- Measurable results from the pilot
- Testimonials from your allies
- What you are asking for: official authorisation, allocated time, and possibly budget for the paid plan once you have proven value at a larger scale
What your pitch must not contain:
- A demonstration of Notion's features
- Unsupported promises
- A request to deploy immediately to the whole team
Leadership does not care whether Notion is a beautiful tool. They care whether it solves a real problem, whether people genuinely use it, and whether it is worth the time and energy it demands.
Answer those three questions with concrete proof. Everything else is secondary.
Phase 3: pilot at a broader scale (4 to 6 weeks)
Leadership said yes, or at least "show us more". You now have conditional authority.
Do not make the mistake of deploying immediately to the entire team. You have one success story. You need a portfolio of success stories.
Launch two or three additional pilots with different teams, on different problems. The goal is to prove three things to leadership:
- That it works for different types of teams, not just yours
- That it solves different types of problems, not just one isolated case
- That non-technical people can adopt it, not just early adopters
Choose your pilot teams strategically. Take a team that is highly visible to leadership. Take a team known for being critical and hard to convince. If you win them over, everyone else will follow.
Phase 4: scale without forcing (3 to 6 months)
You have several successful pilots. Leadership is convinced. The temptation is to deploy fast and wide.
Resist that temptation.
The Guerrilla Path worked until now because you let people choose. Do not change strategy now. Keep making successes visible. Keep letting teams ask to join rather than forcing them in.
What you build at this phase:
- An internal help centre: FAQ, getting started guides, ready-to-use templates
- A champion network: one or two people per department who answer their colleagues' questions
- Light governance: naming conventions, locked database structures to prevent chaos, one simple rule (archive rather than delete)
The system must be able to run without you. That is the sign that adoption is real and lasting.
You have succeeded when:
- 70% or more of the team uses Notion regularly
- New joiners are onboarded into Notion from day one
- You spend fewer than 3 hours per week maintaining the system
- People defend Notion themselves when someone questions it
What kills the Guerrilla Path
A few common mistakes I observe, so you can avoid repeating them.
Announcing too early. Talking about the deployment before you have proof creates expectations and resistance you are not yet in a position to manage.
Wanting to build everything alone. A system you built for the team without them will always be less adopted than one built with them.
Giving up after two weeks. Habits take at least 30 days to form. A pilot judged after one week tells you nothing.
Moving to the Official Path without being invited. If leadership has not yet given you an official mandate, do not behave as if they had. It creates distrust.
What if you are already stuck?
The Guerrilla Path has its own resistance patterns. The manager who sees your initiative as a threat. The colleague who keeps using Excel regardless. Adoption that stalls at 30% and stops progressing.
These situations have specific solutions.
The 4 types of Notion resisters and how to bring them on board
And if you want to know where you really stand in your deployment, and what you are missing to move to the next step:
