Overview
For people who have installed Notion but are at a loss for how to structure it, this designs the database structure and views of an all-in-one work management, goals, and retrospective dashboard. It prioritizes not flashy design but a minimal structure that you will open and use every day. If actual page creation is needed, connect via the Notion connector.
Trigger Keywords
Notion template, all-in-one work management, Notion dashboard, Notion goal management, Notion retrospective template, Notion structure, work database, Notion setup, Notion to-do
Workflow
Step 1: Decide the purpose
First, decide what this Notion will contain. Do not put everything on one page.
| Purpose | Core database |
|---|---|
| Work management | To-dos, projects, notes |
| Goal management | Goals, weekly actions, progress |
| Retrospectives and records | Retrospectives, work logs, lessons learned |
| All-in-one | Link the above together on one dashboard |
→ The clearer the purpose, the simpler the structure. Start with 1–2 DBs at first.
Step 2: Design database properties
Decide on the minimum properties (fields) to go into each DB.
- 할 일 DB: Title · Status (To-do/In progress/Done) · Priority · Due date · Project (relation)
- Goal DB: Goal · Period (quarter) · Key results · Progress rate
- Retrospective DB: Date · Cycle (weekly/monthly) · Keep/Problem/Try · Next action
- → The more properties there are, the less you use them. Keep only what is absolutely necessary for sorting and filtering
Step 3: Configure views
Create views that show the same data differently depending on the situation.
- Today view: Filter by due date = today or status = in progress
- This week view: Weekly filter and sort
- Board view: Kanban by status (To-do→In progress→Done)
- Calendar view: Based on due date
- → Enter once, view in multiple ways. Views are the core of using Notion
Step 4: Assemble the dashboard
Gather frequently used views and links on the home screen.
- Top: Today's to-dos, this week's goals (linked DB views)
- Middle: Projects in progress, recent retrospectives
- Bottom: Frequently used links and notes
- → Create a "home" you open every day to prevent things from getting scattered.
productivity-goal·productivity-retroConnect the deliverables here
Step 5: Operating rules and actual creation
- Input routine: Add today's tasks in the morning, one line of reflection in the evening →
productivity-habitintegration - Weekly cleanup: Archive completed items, prepare for next week
- Actual creation: Once the structure is finalized, pages and DBs can be created with the Notion connector (
mcp__claude_ai_Notion__*) - → But design comes first. Don't start by making an empty template; decide in the order of purpose → properties → views
Usage examples
Example 1: "I want to build an all-in-one work management dashboard in Notion" → Design task/project DBs → Today/This week/Board views → Home dashboard composition plan
Example 2: "I want to manage goals and reflections together in Notion" → Design goal DB + reflection DB properties → Link quarterly goals ↔ weekly reflections → Progress view
Example 3: "I installed Notion but don't know what to build first" → Narrow down to 1 purpose → Minimum 1 DB + 2 views → One home page you open every day
Deliverables
- Database structure by purpose
- DB property (field) design
- View composition by situation (today, weekly, board, calendar)
- Home dashboard layout
- Input and cleanup operating rules
Precautions
- If you make it fancy from the start, it won't be maintained — grow it from a minimal structure.
- The more properties and DBs there are, the greater the input burden. Keep only "what is absolutely necessary."
- Actual automatic page creation requires connecting the Notion connector. If not connected, structure design is provided up to that point.
Related skills
- moai-coworker:productivity-goal: Manage goals and key results with a Notion DB
- moai-coworker:productivity-retro: Structure the reflection format as a Notion reflection DB
- moai-coworker:productivity-habit: Visualize a habit tracker as a Notion view
- moai-coworker:collab-productivity-report: Use the work log DB for writing weekly reports
When not to use this skill
- Team collaboration workspace and permission design: For organization-level Notion, use
moai-coworker. - Creating tables with tools other than Notion (Excel, Google Sheets): Send document deliverables to the
moai-coworkerfamily. - Code and DB schema design: For software data models, the
moai-coworker/backend domain is appropriate.
Source
Based on a general design framework for all-in-one work management and dashboards in Notion + user vault notes. Wording and examples are independently composed based on South Korea as of 2026.