Why did I start using Notion? Because "doing well" and "being seen" are two different things.
To be honest, I started doing project management,It was forced out of necessity.。
The pressure from above made me realize for the first time that..."Doing a good job" and "making sure your work is seen as good" are two entirely different things. I completed the task within the deadline and didn't slack off, yet some people still think I "didn't do anything" simply because I didn't leave any records.
To avoid misunderstandings and ensure my efforts were recognized, I began documenting every task, progress update, and outcome. But handwritten notes were scattered and difficult to consolidate and track. I realized the problem wasn't the method itself, but the lack of a tool to systematically organize everything.
After thorough research and evaluation, I've decided to use Notion. It addresses the pain point of "no records" in my work, and more importantly, it elevates me from merely "keeping records" to "systematically documenting."
🔬 My Notion Experiment: Piecing Together Scattered Post-its to Create a Work Map
I plan to start with the pain points at work: project progress, meeting minutes, notes, and miscellaneous tasks are all scattered across different places. I use Notion as my own...UI/UX LabI have reorganized these records.
My core concept is simple:"Piece together scattered sticky notes into a well-organized work map."
Although I had handwritten notes before, my records were still quite disorganized:

Handwritten work progress lacks a comprehensive overview.

Hand-drawn Gantt chart is messy

Scattered information takes time to locate

A large number of scattered tasks
My needs extend beyond mere "notetaking" to encompass "integration." I require a platform capable of simultaneously managing projects, learning, inspiration, and output. Thus, I redesigned a project management information architecture that works seamlessly for me while remaining accessible to colleagues—centralizing all work progress and related information within a single Notion database.

Use Notion to track project progress

Use Notion to track personal tasks
Now, when you open the page, you can see the status, progress, and last update date for each task. Whether it's a team project or a personal task, everything is clear at a glance.
Notion is no longer just a notebook; it has become my daily "work dashboard." This has led me to realize that UI/UX design principles are equally applicable to "human-tool interactions."
How I Designed My Personal Work System in Notion
To clarify the chaotic information, I've broken down all content into three levels and established connections between them, allowing them to interlink like a neural network.
- Project Layer: Manage overall progress, timelines, and task assignments. All ongoing projects are listed here for easy direction confirmation.
- Task LayerTrack the progress and deadlines for each task. Every step has someone assigned to it, ensuring nothing gets stuck in the middle.
- Resource LayerMeeting minutes, SOPs, manuals, inspiration, and reference materials are all stored here. It automatically links to projects and tasks, serving as the logistical backbone of the entire framework.
Organizing things this way allows me to clearly see the contents of each project and quickly find the details I need. The workflow has become much smoother, making my work easier.
Project Layer

Gantt chart tracking
Task Layer

Personal Work Board Categories
Resource Layer

Work Manual and Meeting Minutes
💡 From Tool to Design: Three Features I Think Are the Best
- Centralization and Serialization: Information Architecture The first step in UX design is establishing an information architecture. I consolidate all projects, documents, and meeting notes into a single database and set up relationships so each project automatically links to its SOPs, assets, and team members. With just one page open, you can see all the information.
- Visual Information: Reducing Cognitive Load In UI design,Reduce cognitive loadThis is a core principle. I use kanban boards, progress bars, and charts to make information visible. What used to take half a day to sift through on a list can now be grasped at a glance.
- Real-time Feedback and Loop Output: Consistency Unified layout and fixed columns; automatically mark ”Done” when finished. Any note can be quickly converted into a blog, learning record or SOP, without the need to organize, and quickly convert information.
🧠 Challenges Encountered and Solutions
At first, I was eager to use every feature, jotting things down while randomly experimenting with databases and relations—and soon found myself lost. I realized I'd committed a cardinal sin for UX designers:Without first asking about the "purpose," they began discussing the "function."
I asked myself: "Why do I need this information?" "Who does this page make things easier for?"
When the user is myself, Notion becomes a "UI/UX project designed for myself." Through it, I test information architecture and interaction methods, and this feedback also serves as the basis for reorganizing my workflow.
🎯 Advice for beginners: Start with the problem, don't get tied down by the tools.
If you're also thinking about getting started with Notion, my advice is:
- Start with "the problem you want to solve," not "what the tool can do."
- Start by using someone else's template to familiarize yourself with the logic, then gradually develop your own version.
- Notion's greatest advantage is its ability to be redesigned at any time, so don't be afraid to scrap it and start over.
From chaos to integration, it's not about finding the perfect tool, but starting to design your own system. Let Notion be your testing ground, not another information black hole.
Further Reading
Frequently Asked Questions (FAQ)
A: If you create too many pages too quickly, you won't know how to use them later. First, you need to clarify what problems you want to solve, set up the workflow to complete the work, and then decide what data needs to be saved. Take project tracking as an example, you only need three pages in the beginning: project, task, and resource, and the other functions can be grown slowly.
A: First of all, define "the problem I want to solve". Instead of opening a page directly, we first draw a flow: Project → Task → Resource. After determining the information structure, then move this structure into Notion and link it up with the database association (Relation). Only in this way can the system be logical and less likely to get messy.
A: Both. In team projects, it is mainly used for tracking progress so that colleagues can see the status of the project in real time. Individuals use it to organize meeting minutes, course notes, inspiration and life events. Currently, there are two areas: the Personal Dashboard (for managing tasks, inspiration and personal notes) and the Project Dashboard (for tracking progress, documents and meeting information).
A: Because it's not about "how to operate Notion", it's about "how to make Notion work for me". the essence of UI/UX is to understand the user's needs and behavioral logic, and when I observe myself as a user, I can really design a system that works well and doesn't crash.
A: Of course. Just like designing an interface, a system is never "finished", it only "conforms more and more to your own habits". When I have time, I will re-inventory my needs, delete unneeded pages, and add needed functions.
A: The biggest change is the sense of mastery. I used to be pushed by tasks, but now I can control the rhythm. Through Notion, projects, tasks, and data can be integrated in one place, and the linkage of timeline, kanban, and database makes each process clear at a glance, and coworkers can also see the progress clearly. Most importantly, the framework can be reviewed, adjusted, and continuously improved.




