📖 How to use this template

One flat list of everything a small product team currently owes, sorted by priority rather than filed into phases. No sections, no nesting, no ceremony. The sample is a web team's open work: page updates, API changes, a few fixes.

1. Duplicate this project into your own organization (dropdown next to the project name, then Duplicate)
2. Delete the sample items and add your own. Keep them at the top level. The flatness is the point, and a list you have to expand is a list nobody reads.
3. Set a priority on every item: Urgent, High, Medium or Low. This is the only ordering the project has, so an untriaged item is invisible work.
4. Assign each item to a person, not a team, then switch to Board view grouped by assignee to see who is carrying what
5. Tag by the kind of work: new_feature, design, specs, documentation, routine, check. Swap these for whatever categories your team actually argues about.

Three statuses carry an item end to end: To-do, In progress, Completed. Deliberately short. A longer pipeline is worth having when work waits on other people, and this template assumes it mostly doesn't.

Dates are optional here and most items don't have one. Use a due date when something is genuinely time-boxed, and a start date when it is waiting on a date to begin. Leaving both empty is a legitimate answer, which is why priority does the sorting instead.

Two habits keep it usable. Triage new items the day they arrive, because a flat list with no priority is just a pile. And close finished items rather than leaving them at Completed forever, since the value of one list is that its length means something.