#Custom Workflow

Based on the theme note's "Input → Processing → Output" framework, through a unique theme tag system!

You can turn off PARA mode, or start from the IPO Example Vault / GTD Example Vault and adapt it.

#IPO Knowledge Management Vault

Based on the IPO Example Vault, create a simplified knowledge management system.

#What is the IPO Model

In knowledge management, IPO typically refers to the process of Input, Processing, and Output. This model describes the entire journey of knowledge from acquisition and processing to application.

In the IPO model:

1. Input: This marks the starting point of knowledge management, involving the collection and acquisition of information. Input can include data, documents, research, personal experiences, external information, etc. The quality of input is crucial to the entire knowledge management process.

2. Processing: At this stage, the input information is analyzed and refined to make it useful and applicable. Processing activities may include analysis, synthesis, evaluation, interpretation, storage, and sharing of knowledge. The goal of this phase is to transform raw data and information into valuable knowledge.

3. Output: This is the final stage of knowledge management, where processed knowledge is applied to real-world problems to create value. Output can include decisions, solutions, new products, improved processes, training materials, etc.

Can be simply understood as a simplified version of the CODE/PARA practice, it greatly reduces the entry threshold for beginners. Users only need to focus on input, output, and themes, and easily record, organize, and use notes.

#Core Structure

1. Input System:

   • Store all collected information, materials, and inspirations in the '1. Input' directory
   • Use theme tags to associate related content, such as #ReadingNotes/BookTitle, #LearningMaterials/CourseName

2. Processing Flow:

   • Create theme notes in the '2. Themes' directory to deeply process input content
   • Build knowledge association networks through theme tags
   • Use "Canvas View" or "Advanced Lists" to organize knowledge structures

3. Output System:

   • Store final results in the '3. Output' directory
   • Output can be articles, reports, project deliverables, speeches, etc.
   • Quickly find related input and processing content through reverse indexing via theme tags

#Advantages

• Simple and Easy: No need to understand complex PARA systems, just focus on three core stages
• Flexible and Customizable: Adjust the content and usage of the three directories according to personal needs
• Theme-Focused: Organize knowledge around themes, which aligns better with how our brains think
• Easy to Get Started: Particularly suitable for knowledge management beginners to quickly build their own note system

#GTD Action Management Vault

Based on the GTD Example Vault, you can build an execution-first system focused on moving work forward.

#What is the GTD Model

GTD (Getting Things Done) externalizes commitments into a trusted system and keeps the next action visible. It does not require every note to be sorted into PARA on day one. It first makes sure tasks can be captured, clarified, executed, and reviewed.

#Core Structure

1. Inbox:

   • 1. Inbox stores unclarified ideas, tasks, and material
   • These items usually start with #gtd/inbox

2. Action System:

   • 2. Actions/Next Actions aggregates #gtd/next
   • 2. Actions/Waiting For aggregates #gtd/waiting
   • 2. Actions/Someday Maybe keeps possibilities that are not active now

3. Project System:

   • 3. Projects stores outcomes that need more than one action
   • Every active project should keep at least one #gtd/next or #gtd/waiting item

4. Reference, Reviews, and Archive:

   • 4. Reference stores useful material that is not directly actionable
   • 5. Reviews holds weekly reviews, monthly reviews, and system cleanup
   • 6. Archive stores completed or paused material

#Tag Design

The GTD vault uses two kinds of tags:

• #gtd/next, #gtd/waiting, #gtd/someday, and #gtd/inbox describe task state
• #ctx/deep-work, #ctx/computer, #ctx/call, #ctx/errand, #ctx/home, and #ctx/mobile describe execution context

This lets you choose work by state and context first, then return to the project note for full background.

#Media Creator's Vault

#Core Structure

1. Content Workshop:

   • Topic management uses the demand pool theme tag, such as theme #PhoneReview/iPhone16

   • Use "Canvas View" to build content script frameworks

2. Production Pipeline:

   • Each video production is broken down into storyboard script → shooting list → editing project sub-themes, such as

     • #PhoneReview/iPhone16/StoryboardScript

     • #PhoneReview/iPhone16/ShootingList

     • #PhoneReview/iPhone16/EditingProject

3. Content Output:

   • Finally, store the finished products in the output directory

#Academic Vault

#Core Structure

1. Input System:

   • Literature abstracts use Literature ID#article theme tags for automatic association

   • Experimental data is dynamically indexed through templates using Dataset ID#dataset

2. Processing Flow:

   • Each research direction serves as an independent theme (e.g., #QuantumComputing-OpticalQuantumRoute)

   • Use the "Advanced Lists" feature to perform topological sorting of literature citation relationships

3. Output System:

   • Paper drafts automatically aggregate reference materials (through reverse indexing via theme tags)

   • Track submission progress and review cycles through the "Home View"

#Sales Vault

#Core Structure

1. Customer Management System:

   • Set #Customer-CompanyA theme tag for each customer

   • Automatically generate "Customer Profile Timeline" to display communication records

2. Business Process Tracking:

   • Opportunity follow-up uses Stage:RequirementConfirmation[75%] progress tags

   • "Big Calendar View" plans customer visit schedules

3. Data Analysis Module:

   • Sales funnel is broken down by region/product line through "Filter View"

   • Performance weekly reports automatically extract KPI data from theme notes