Best Practices

Lithora is flexible, but these conventions help teams move faster.

1. One Task, One Owner

While Lithora allows multiple assignees, we recommend designating a single "Primary Owner" (the first avatar). This ensures accountability. If a task needs multiple people, consider breaking it into subtasks.

2. Use "Cycles" for Engineering

For software teams, we recommend using the Cycle View (Sprint). Set a clear goal for 2 weeks, and only pull in tasks that contribute to that goal. Move unrelated bugs to the Backlog.

3. Document Decisions, Not Just Outcomes

Use the Docs tab in a project to write "RFCs" (Request for Comments). Link the resulting Tasks to this spec. This provides context 6 months later when you wonder why a feature was built a certain way.

4. Keep It Clean

Archive completed projects. Don't let your sidebar become a graveyard. Use the "Archive" feature to hide old work while preserving the data for search.