By Jasmijn
Notion is not the point. But it can be the place.
I have spent years walking into companies at the moment when work has become just a little too heavy.
Usually not very dramatic from the outside. The company is growing, the team is busy, clients are being served, projects are moving. But underneath all of that, people can feel that the way they work is starting to get messy.
There are too many places where information might live. Too many meetings that end with “let’s pick this up separately”. Too many decisions that seem to happen somewhere between Slack, someone’s head and the founder’s latest voice note. And often, by the time I join the conversation, the company has already translated that feeling into a very practical request.
“We need a better tool.”
I understand that request. I have built a large part of my work around tools, systems and Notion. I love a good workspace. I love when information has a home, when a team can open one place and immediately understand what matters, what is moving and who owns what. So this is not an argument against tools.
But I have learned to be careful when a company says the problem is the tool.
Because sometimes the tool really is part of the problem. It may be too rigid, too scattered, too complicated, or simply not suited to the way the team works. But very often, the tool is only where the deeper problem becomes visible.
A project management tool will show you that ownership is unclear. A dashboard will show you that priorities keep shifting. A knowledge base will show you that nobody has decided what should be documented, where, and for whom. And the more flexible the tool is, the more it reflects what’s going on underneath. That’s why Notion can feel like a mirror.
Notion can hold the whole company, including the parts that have not been thought through yet. That is both the beauty and the risk of it.
You can build almost anything in Notion. But that also means you first have to know what you are building. Not just which database or which dashboard. You have to understand how the company actually needs to run. That is the part I find most interesting.
When I start working with a team, I am not only looking at the workspace. I am listening for the patterns underneath it. Where do decisions get stuck? Which questions keep coming back to the founder? Which meetings create clarity, and which ones create more work? Where does the team go when they need to know what matters this week? What is documented because it is useful, and what is documented because nobody trusts that people will remember?
Those questions tell you much more than the tool does.
I have seen beautiful systems fail because the operational choices underneath them were never made. The workspace looked clean. The dashboards were impressive. The databases were connected. Everyone was excited at launch. And then real work started again.
People went back to asking for updates in Slack because they did not trust the system. Tasks were created, but ownership was still vague, so nothing really happened. Meetings continued in the same rhythm, producing the same confusion. Decisions were written down somewhere, but not in a way people could actually find or use later. The founder still had to approve everything, because nobody had decided what the team was allowed to own without them.
In those cases, the tool was implemented, but the company had not changed how it runs. That is the distinction I care about. A tool can make work visible. A system makes work move.
For me, that is where Notion becomes powerful. Not when it is used as a prettier place to store everything, but when it becomes the place where the operating logic of the company lives. The place where priorities are connected to projects. Where projects are connected to ownership. Where meetings lead to decisions. Where decisions do not disappear. Where knowledge is not dependent on who happens to be in the room.
Notion is not the point. But it can be the place.
The place where a company stops depending on memory, assumptions and founder-brain, and starts working from a shared structure. The place where people can see not only what is happening, but how the company works.
At RunOps Studio, we build in Notion. But we do not start with Notion. We start with the company. How it thinks. How it decides. How work moves from idea to execution. How people share knowledge. How the founder can stop being the centre of everything without the company losing direction.
Only then do we build the structure. Clear priorities. Clear ownership. Clear decisions. A rhythm that keeps people aligned without endless meetings. A source of truth people actually use.
The tool matters. Of course it does. The wrong tool can slow a company down, and the right tool can create enormous leverage. But only when it is built around the way the company actually needs to run.
So before choosing the next platform, rebuilding the workspace or adding another dashboard, I would ask a different question first.
Not: which tool do we need?
But: how should this company work?
What are we trying to make clear? What should no longer depend on the founder? What needs a place? What needs a rhythm? What needs an owner?
That is where the real system begins.
And once that is clear, Notion can be a very good place to build it.
Want to talk more? Contact us
If you’re wondering how your company scores on those fundamentals, take our assessment and see where you stand.