Project Management

This document will guide you on how to create, configure, and manage projects in the FLO.W Template to achieve efficient project management.

How to Add a Project

Task vs Project: How to Choose Correctly

When using the FLO.W Template, many users wonder: when should I create a project, and when do I just need to record a task? Understanding the difference between the two is key to efficient management.

Concept Understanding

Tasks are like each specific action in cooking - washing vegetables, cutting meat, stir-frying, eating, washing dishes. Each action is very specific, you don't need to break it down further, just execute directly.

Projects are like "hosting a dinner party", requiring menu determination, guest invitations, ingredient shopping, cooking, table setting, party game preparation, etc. It has a clear endpoint, but requires a combination of a series of tasks to achieve.

Three Judgment Criteria

1. Do You Need to "See Progress"

This is the most important judgment basis. If you often ask yourself "When will this be done? How much more is needed?", then you need more than just individual task completion prompts, but overall progress visualization.

Suitable for creating projects:

• Preparing Double 11 event materials (need to care about overall progress of copy, posters, channel docking)
• Product feature iteration (need to track design, development, testing stage progress)

Suitable for recording as tasks:

• Sending an email to contact a KOL (complete upon execution, no progress bar needed)
• Updating a document (single action, no breakdown needed)

2. Are You "Making a Checklist"

When you think of something, if you start thinking "I need to do A first, then B, and also C", then it's a project. If you just think "go do this thing", without the impulse to automatically break it down, then it can be a task.

3. Do You Need to Review After Completion

If after completing something, you feel it's necessary to summarize experience, refine methodology, or analyze problems, then it deserves to be a project. Projects have clear boundaries and complete process records, making them the most suitable granularity for review.

Typical review scenarios:

• Planning marketing campaigns (analyzing what worked and what didn't)
• Completing product iterations (summarizing development process and improvement points)
• Organizing team training (evaluating training effectiveness and methods)

Practical Suggestions

When Unsure, Prioritize Creating Project

When you can't determine, suggest creating a project first. The project page can serve as a "chaos buffer", you can first put related tasks, ideas, and materials into it, without worrying about whether it's perfect.

If you later find the matter is simple, you can:

• Directly delete the project page (notes and tasks within won't be affected)
• Mark the project as completed and archive, retaining the attempt record

Allow Adjustments and Trial & Error

This system allows you to flexibly adjust:

• Tasks can be upgraded to projects
• Projects can be simplified to tasks
• No information will be lost due to adjustments

Develop Judgment Intuition

After using for a while, your intuition will become more and more accurate. At first you may need occasional adjustments, but gradually you'll be able to accurately judge whether to use tasks or projects at the moment of recording, because your brain has internalized this judgment logic.