Form follows function. At least, it should. One common request I get from clients is to create them “dashboards” in tools like @notionHQ. The request is usually the same: “I want to see all my most important information in one place.” And while that’s great, it misses one important aspect of how we work: Contexts. We get work done in contexts. We don’t get work done in static dashboards. Notion, at its core, is simply a collection of databases, database pages, and the contextual pages we access them in. Building a great database structure is one thing. But designing the context pages where work gets done is a completely different thing. In this short guide, I want to share a simple, repeatable process you can use to design your next context-based page for getting work done on NotionHQ.

Everything You Need to Know About Notion I’ve spent years designing and creating Notion workspaces for agencies of all kinds. I assembled everything I’ve learned into a complete guide called: The Complete Agency Workspace Guide for Notion: Everything You Need to Know to Organize, Systematize, and Scale Your Agency with Notion It’s packed with 11,000 words and over 2 hours of video. And it’s 100% free. Grab it here: learnchangedo.org/agency-wor…

People set up their Notion databases incorrectly all the time. I see it every time I do a workspace audit: • Wrong database views • Data commingling • Missing relations If you're creating a Notion workspace for your team, here's what you need to know about databases:

3. Don't Use Core Databases for Working Always make it easy to get work done. This begins with thinking about your users. Who are the people on your team, and what do they need to get work done? • A salesperson needs to leads, deals, and meeting notes • A project manager needs projects, tasks, and meeting notes • A contractor needs projects and tasks After you create your databases, tuck them into a "Databases" page. Use linked databases to create fully customized, user-tailored daily workspaces for each person on your team.