I have a pegboard in the garage.
It is not pretty. It is not color-coded for Instagram. It does not have custom LED lighting. It just holds the tools I actually use, in places I can reach without thinking, and it makes it obvious when something is missing.
That pegboard has taught me more about building Notion databases than any tutorial.
The garage rules that transferred directly
Everything has one home
On the pegboard, the 10mm socket does not live in three different drawers depending on my mood. It lives on the same hook every time.
In Notion, every important piece of information needs one primary database. Clients live in Clients. Projects live in Projects. Tasks live in Tasks. When the same client name exists in four different places with slightly different spellings, the system is already lying to you.
Empty hooks are information
When a tool is missing from the pegboard, I notice before I need it. The empty space is the alert.
In Notion, I want the same thing. Filtered views that show overdue follow-ups, projects with no next action, or clients with no contact in fourteen days. If the “problem” view is empty, I can relax. If it has items, I deal with them. No hunting required.
The most-used tools get the best real estate
My daily drivers hang at chest height. The specialty tools I use twice a year live higher or lower.
Same logic in Notion. The databases and views I touch every day sit at the top of my sidebar or as favorites. The archive databases and old project templates can live deeper in the workspace. If I have to click more than twice to reach today’s work, the structure is wrong.
Labels beat memory
I used to think I would remember where I put the torque wrench. I did not.
Now every hook has a simple label. In Notion, property names and view names need to be equally obvious. “Status” is better than “Current Stage of the Thing.” “Next Follow-Up” is better than “Date Field 3.” Future you is tired. Be kind to him.
How I apply this when I build a new database
Start with the hooks, not the wood
People open Notion and immediately start designing the perfect page layout. That is backwards.
First decide what the actual objects are. What needs its own hook? Usually it is:
People or companies (Clients)
Work containers (Projects)
Actionable items (Tasks)
Records of what was said or decided (Notes)
Get those databases right before you build any fancy dashboards.
Limit the properties to what you will actually update
My pegboard does not track the purchase date, weight, and preferred manufacturer of every screwdriver. That would be nonsense.
In Notion I ask one question for every new property: Will I update this when I am busy and slightly annoyed? If the answer is no, the property does not get added. Rollups and formulas are allowed only when they remove work, never when they create it.
Build the “missing tool” views first
Before I make a beautiful board view, I create the views that surface problems:
Overdue items
Items with no owner
Clients with no future follow-up date
Projects that have been “In Progress” too long
These views are the empty hooks. They tell me what needs attention without me having to remember to look.
The mistake I see in most Notion setups
People build databases that try to be both the pegboard and the entire workshop at the same time.
They create twenty properties, six linked databases, and a dashboard with nested filters that looks impressive and dies in eleven days. Then they say “Notion didn’t work for us.”
Notion did not fail. The system violated the pegboard rules. It became harder to put things away than to leave them on the bench.
A simple test before you add anything new
Stand in front of your current Notion workspace and ask:
Does every important thing have one clear home?
Can I see what is missing in under ten seconds?
Are the things I use daily the easiest to reach?
Would a tired version of me still update this?
If you get a no on any of them, fix that before you add another property or linked view.
The real point
My garage pegboard is not a productivity system. It is just a way to stop losing the same 10mm socket for the third time.
Notion databases should serve the same purpose. They exist so the work has a reliable place to live and so the missing pieces are obvious.
When the database makes the work clearer and the gaps visible, keep it.
When it starts needing its own maintenance schedule, take it down and simplify.
Meat. Heat. Bun.
Hang the tools you actually use. Leave the rest in the box.
No feedback yet — submit the first.