A Project defines a clear outcome with a bounded scope. It answers: What does “done” look like for this body of work?
We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
⏰ When to Use It
Use a Project when:
- ✓ You have an outcome that requires multiple steps but is self-contained
- ✓ You want to avoid overwhelm by turning the outcome into actionable Next Actions
- ✓ You need a place to collect tasks, notes, and links for this specific outcome
📝 Relationship to Epics
- ✓ Epics categorize related Projects to pursue a larger outcome.
- ✓ An Epic can contain many Projects. A Project may exist without an Epic.
- ✓ Use an Epic when the initiative spans multiple distinct Projects or workstreams. Use a Project for a self-contained outcome.
⚙️ How It Works
- ✓ Define the outcome: What does “done” look like?
- ✓ Plan execution: Create Next Actions → that move the Project forward
- ✓ Optional categorization: Link the Project to an Epic → if it contributes to a larger initiative
- ✓ Organize context: Link relevant Knowledge →, Lists →, Events →, and references
- ✓ Review regularly: Keep it moving—archive when the outcome is reached or abandoned
📝 Archiving Behavior
Archiving cascades downward:
- ✓ Archiving a Project automatically archives all of its Next Actions.
- ✓ Archiving an Epic → archives all Projects under it and all Next Actions underneath those Projects.
💡 Tips
- ✨ Keep Projects focused: If it becomes too big or cross-cutting, elevate to an Epic that contains multiple Projects
- ✨ Make work visible: Use clear, small Next Actions →
- ✨ Avoid “forever” Projects: Ongoing areas belong in Lists → or Knowledge →