Notion databases that don't collapse under their own weight
Most Notion setups die from too many properties and too few decisions. Here's the pruning pass I run on every database before it goes into a template.
Every bloated Notion workspace I've inherited has the same problem: someone added a property for every question they might ask, and now nobody asks any of them because the view looks like a tax form.
My rule is one database, one job. A content calendar tracks content, not revenue. A client CRM tracks relationships, not deliverables. The moment a database answers two unrelated questions, split it or delete the extra properties.
Then I run the three-week test. If a property hasn't been filled in for three weeks of real use, it gets archived, not deleted. Archived properties can come back. Clutter rarely does.
The last pass is views. I cap each database at four: one for today, one for this week, one filtered by status, and one for review. If a template ships with twelve views, the creator hasn't decided what matters. That decision is the product.
None of this is clever. It's just discipline applied before the database becomes load-bearing. Do the pruning early and your system survives its first busy quarter.