Skip to main content

Projects for Long-Term Habits

Add a “Projects” layer parallel to Areas. Some habits contribute to long-term outcomes (e.g., finishing a book or completing a course). Tracking progress toward a Project gives users a sense of advancement and increases motivation, especially for habits tied to measurable achievements.

2 comments

Comments2

  • Ahmad

    •

    Dec 9, 2025

    Just to clarify before anyone mentions Areas: this idea is not about adding another category.

    Areas are great for high-level classification, but Projects follow a different logic based on several well-known productivity frameworks such as:

    • the PARA Model (where Projects are outcome-driven and separate from Areas),

    • outcome-oriented habit systems,

    • and project-based behavioral design models.

    In these frameworks, an Area is a stable domain of life, while a Project is a time-bound unit with a clear outcome — like finishing a book, completing a course, or reaching a specific milestone.

    Projects exist to track progress toward a long-term result, not just to group habits.

    Both structures can coexist without overlap:

    Areas organize where the habit belongs, while Projects show what long-term outcome the habit is building toward.

    • Minh Thư

      Team•

      Dec 17, 2025

      Hi @Ahmad ! Thank you so much for sharing your idea!

      Thanks for the detailed explanation regarding the PARA model and behavioral design.

      I’m still trying to visualize the practical benefit of this feature. Using your example of 'Finishing a Book' — currently, I would just create a habit called 'Read a Book' and track that streak.

      In your proposed structure, how would a 'Project' function differently? Is it about having a separate progress bar (e.g., % of book completed) linked to the habit, or is it just a way to tag the habit? I'd love to understand the workflow difference.