Almost every B2B team that comes to us with a "Notion problem" doesn't have a Notion problem. They have a systems design problem. Notion just amplifies what was already there: if the processes were clear, it organizes them; if they lived in one person's head, it distributes them badly.
Over the last 18 months we've implemented workspaces at more than 40 companies. These are the five patterns we see break every single time a team grows from 5 to 20 people.
1. A database is not a graveyard
The most common mistake: using a database as an information dump. "Let's drop every meeting / client / document in here" → a month later it weighs half a megabyte, nobody filters, and everyone creates another one "for themselves".
A database has to drive decisions. Every record answers a business question: who does what? what stage is this deal in? what deliverables have we agreed on?
If you can't summarize its purpose in one sentence, it's not a database. It's a graveyard.
2. Relations are cheap, duplicates are expensive
The difference between a workspace that scales and one that drowns: the relations between databases.
- A project with no client linked is orphan information
- An invoice with no project is a number without context
- A meeting with no deliverable is wasted time
Every time you duplicate information between two databases ("let me copy the client name in here"), you're adding debt. Use Relations and Rollups, they're the closest thing Notion has to SQL, and they're free.
"If I have to copy a piece of data between two places, it means a relation is missing.", golden rule of the workspace.
3. Every property has to drive decisions
Workspaces that don't scale pile up properties "just in case": 25 columns in a task database, 18 different statuses.
A property without a clear use case creates friction for the whole team every time someone creates a record. Multiply that by 50 records/day × 6 people and the real cost is hours per week.
For every property, ask: what decision changes if someone fills it in? If the answer is "none", delete it.
4. The personal view rules, not the central dashboard
Managers design workspaces from their control panel: pretty dashboards, aggregations, charts. The team that has to use those systems doesn't open the central dashboard, they open today's task.
Design Andrea's view and Carlos's view first. Make them clean, filtered to their own work, with a big button to create what comes next. The executive dashboard falls out of that for free, the other way around doesn't work.
5. If someone can't find where something goes, it's badly named
The real test of a system: if a new hire on their third day can't figure out where to log a discovery call, the system is wrong. Not that person.
Naming beats documentation. A good name removes the need to explain.
In short
Notion doesn't fail. What fails is designing workspaces as file cabinets instead of living systems. If you're right now at that point where you can feel that "Notion is getting chaotic", that's exactly the moment to overhaul it, before you hire 5 more people and multiply the entropy.
Want an honest second read on your workspace? Let's talk for 30 minutes.
