Most project tools are very good at giving work somewhere to go. Backlog, board, sprint, roadmap, archive, custom status, custom status for the custom status. Then a small team spends half a meeting explaining what “ready” means this week.
Tracker starts with a narrower idea. Work should be small enough to explain, bounded enough to finish and explicit enough that another person can tell whether it is done. A Story has a purpose, acceptance criteria and an out-of-scope edge. That sounds obvious until you read a ticket that says “improve the flow” and discover that everybody brought a different flow.
The planning shape stays deliberately plain: Backlog, Board and Icebox, with Cycles and Releases where they help. The point is not to recreate every view somebody has ever requested from a project tool. The point is to keep the active work legible when five people are building, reviewing and operating the same thing.
Acceptance criteria do a lot of quiet work here. They turn “I think this is finished” into something another person can check. Out-of-scope notes stop a small Story from growing a second head halfway through the cycle. Human acceptance keeps the final “yes” with the person who owns the outcome, not with the automation that happened to move a card.
That makes Tracker more opinionated than a blank Jira clone. It is not trying to win a configuration contest. A small team does not need a museum of workflow states. It needs fewer conversations where the real work is hidden inside a label, a chat thread and somebody’s memory.
The useful test is not whether Tracker can represent every process. It is whether a team can open a Story after two weeks and still answer four plain questions: why are we doing this, what counts as done, what are we not doing, and who accepts the result?
That is the product I want to market. Not “project management, but with more AI”. Just a delivery tool that leaves enough structure and evidence behind that the team does not need to perform archaeology every Friday.
Tracker is still being built. That is visible in the edges, the decisions and the occasional thing that has not yet earned a button. I prefer that to a polished system that quietly makes every workflow somebody else’s problem.