01 - Preface

Why build a new knowledge management system?

The Knowledge Worker's Dilemma

As the creator of the FLO.W system, my initial exploration began with a dilemma that virtually every serious productivity tool user encounters:

Option One: Pursuing the "best point solution" leads to information fragmentation.

We tend to seek out the "best" dedicated tool for each specific need. We use Flomo to capture fleeting ideas because it is fast enough; we use Feishu or Yuque to write structured project plans because they handle long-form content and collaboration well; we use Evernote or Readwise for web clipping and read-later because their collection capabilities are powerful enough.

The direct consequence of this approach is that our knowledge, thoughts, and plans end up scattered across isolated, non-communicating "information silos." When we need to consolidate all relevant materials for a project, we are forced to switch between multiple applications, searching, copying, and pasting. Every context switch drains our attention; every search risks missing critical information due to fuzzy memory. We have assembled an impressive arsenal of specialized weapons, only to find ourselves on a chaotic battlefield with fractured supply lines.
Option Two: Pursuing "unified information management" leads to internal chaos.

To solve the fragmentation problem, a natural idea is to put everything into a single powerful platform, such as Notion. But new problems quickly emerge. Without a clear, coherent top-level design and organizational methodology, a unified platform simply transforms external chaos into internal chaos.

Notes without structured categorization are no different in essence from notes scattered across different apps; they are equally hard to discover and reuse, nothing more than "digital dust." Projects and tasks without process-driven management, even when stored in the same database, amount to nothing more than an endlessly growing, anxiety-inducing list. We have simply thrown everything into a bigger, deeper drawer, only to discover that finding anything has become even harder.

These two options form the double bind that modern knowledge workers face.

The starting point of "FLO.W" was to break free from this bind, attempting to introduce an effective methodology within a unified platform (Notion) that lets users enjoy the convenience of centralized management while avoiding the trap of internal chaos, ultimately achieving the orderly flow of information and the creation of value.

Decision Paralysis Caused by Perfectionism

After identifying the twin problems of information fragmentation and internal chaos, many users encounter a third, more insidious dilemma: decision paralysis caused by information overload. A typical manifestation of this dilemma is users who, in pursuit of the "perfect system," expose all databases, charts, statistics modules, and progress trackers simultaneously on their homepage or core workspace view.

This "omniscient" design approach stems from seemingly sound logic: since I have invested so much effort building all these valuable data views and analytical tools, why not make them all visible so I can stay on top of everything at all times? However, this design overlooks a critical scientific fact: your attentional resources are extremely limited. When too many information modules compete for your attention simultaneously, the system is not empowering you; it is creating a new cognitive burden.

Specifically, this "module stacking" leads to three serious consequences:

1. Hidden Increase in Startup Cost

Every time users open their system, instead of immediately entering a flow state and beginning to work on specific tasks or projects, they unconsciously spend 5-10 minutes conducting a "system patrol": checking whether statistics across various databases have changed, browsing task distributions across different views, and admiring their carefully designed layouts and color schemes. Users become intoxicated by the illusion of "my system is so perfect," while invisibly consuming the precious time and energy that should have been devoted to actual output.

2. The Compounding Effect of Decision Fatigue

When all information is exposed simultaneously without filtering, users no longer face a clear "next action" but rather a "decision matrix" full of options: Should I handle urgent tasks first, or push forward on important projects? Should I review yesterday's notes, or plan tomorrow's schedule?

Every information module silently sends "look at me, look at me" signals, and this persistent, low-intensity demand for decisions rapidly depletes users' willpower resources, leading to "decision fatigue." The end result is often that users waste enormous amounts of time deliberating, yet never actually begin working.

3. Critical Information Gets Buried and Overlooked

When everything is emphasized, nothing is emphasized. In an information-dense interface, truly urgent and important matters are actually more likely to be buried under the noise of "secondary but visible" information. Users may be attracted by an aesthetically pleasing but non-critical statistics chart, while overlooking a core task with an approaching deadline or missing an important event that requires immediate response.

The design of "FLO.W" aims to systematically solve this dilemma.

By introducing Progressive Disclosure as a core design principle, the system abandons the "stack modules, fill the screen" approach. Instead, based on users' cognitive patterns and actual usage scenarios, it constructs a three-layer information filtering system. The core philosophy of this system is: present the right amount of information, in the right way, at the right time. The system intelligently distributes information across different tiers based on urgency, importance, and frequency of use, ensuring that users' attention always stays focused on what matters most right now, rather than being overwhelmed by a sea of information.

Three Problems That Block Value Creation

If the "tool selection" and "decision paralysis" issues described above are hidden psychological traps, then in day-to-day work we also face more visible process blockages. These three problems drain our energy through idle spinning, and through the FLO.W system, we will tackle them one by one.

Problem One: Chaotic and Disorganized Workflows
- Symptoms: Tasks are complex and run on multiple parallel tracks, causing important items to be frequently overlooked; projects progress slowly, often relying on intuition and fragmented communication rather than clear paths and milestones; large amounts of repetitive work consume time and energy, yet without standardized processes (SOPs), experience cannot be accumulated and efficiency cannot improve. The result is massive internal energy drain, with output disproportionate to effort.
- Root Cause: The lack of an "action management framework" that effectively connects and breaks down macro goals, mid-term projects, and daily tasks.
Problem Two: Scattered and Forgotten Knowledge Notes
- Symptoms: Ideas are jotted down on the spot, knowledge points are scattered across various apps and documents, making it difficult to form a coherent system; notes lack effective connections, making it impossible to reach all related context through a single thread; when knowledge is needed to solve problems or create something, it cannot be recalled or utilized at critical moments, and past learning and thinking fail to compound.
- Root Cause: The lack of an effective mechanism to transform information from "recording" to "connecting," and ultimately distill it into a "personal knowledge system."
Problem Three: Creative Output Hits a Bottleneck
- Symptoms: You have great ideas, but it is difficult to systematically develop them into complete works or proposals; the creative process lacks structure, leading to inconsistent output and uneven quality; in the AI era, facing massive amounts of information and powerful AI tools actually creates more anxiety, making it hard to efficiently coordinate various tools and convert AI capabilities into personal creative advantages.
- Root Cause: The lack of a smooth "value creation pipeline" that integrates "idea incubation," "material accumulation," "process management," and "review and iteration."

Three Frustrations of Notion Users

When we turn to Notion to solve the difficulties described above, we often find ourselves caught in yet another layer of predicament. Not only are the old problems not fully resolved, but Notion's extreme freedom and flexibility actually give rise to three unique new pain points, often called "luxury problems."

Pain Point One: Building a System That Lacks Coherence
- Symptoms: Users are attracted by Notion's powerful databases, views, relations, and other features, but due to a lack of top-level design, they end up building a database here and a page there. Databases operate in isolation; pages are merely a simple relocation of documents. Powerful features like relations and rollups are shelved due to the complexity of understanding and configuring them.
- Result: Notion ultimately becomes a fancier, better-looking "advanced bookmarks folder" or "digital diary," failing to become a true "operating system" capable of driving personal work and life.
Pain Point Two: Information Connections That Exist in Name Only
- Symptoms: Users learn to use bidirectional relations, building extensive links between notes. But they quickly discover that when a core note is linked by hundreds of other pages, the link network becomes impossible to interpret. On the linked pages, you can only see a long "mention list" without being able to distinguish the nature or context of these links. You can navigate from A to B, but on page B, you cannot find a specific direction to move to the next step.
- Result: The overuse of links creates new "information noise." What appears to be a dense knowledge network is actually a tangled, signpost-less fishing net; important knowledge remains dormant in the database, unable to be precisely retrieved when it matters.
Pain Point Three: Copying Everywhere, Fitting Nowhere
- Symptoms: The Notion community is filled with beautifully crafted templates and "best practices" shared by power users. Users eagerly collect and duplicate these templates, trying a minimalist Dashboard today and imitating a data-flow kanban board tomorrow. But without understanding the design logic and intended use cases behind these templates, the result of blindly copying is that their own workflow becomes hostage to the template.
- Result: Users' Notion workspaces become a patchwork monster of various styles, like an actor constantly changing costumes without ever finding a role that is truly their own. They are perpetually "working for the tool," constantly adapting to someone else's system, yet never building a personal system that truly fits their own thinking and working habits.

The birth of FLO.W was precisely to systematically solve all of the above predicaments. It brings a clear, complete, and internally consistent design philosophy and underlying logic, aiming to help knowledge workers, especially those in the Chinese-speaking world, truly build their own personal operating system on the powerful and flexible Notion platform, one that continuously evolves and ultimately serves the creation of value.