Enough structure to move
Small teams don't need sprints, story points, or swimlanes. They need a shared list that stays current. How Acme keeps task tracking light.
There is a familiar arc to adopting a heavyweight work tracker on a small team. Week one: enthusiasm and elaborate setup. Week four: half the board is stale. Week eight: the real plan lives in chat, and the tracker is where work goes to be archived.
The tool didn't fail because the team was undisciplined. It failed because it demanded more structure than the work actually had.
What a task needs
In Acme, a task is a title, a status, who created it, and when. That's the whole model. No required estimates, no custom fields to fill before you can save, no hierarchy to place it in. Capturing a task takes seconds, which is the only way a shared list stays current — the moment capture is expensive, people stop capturing.
Statuses are few and mean something, and they are always shown with a label, never as a bare color you have to decode.
Finding work should be a URL
The task list is filterable by status and searchable by text, and both live in the page address. That sounds like a small thing; it isn't. It means:
- You can bookmark "open tasks" and land there every morning.
- You can share exactly what you are looking at by copying the address bar.
- The back button works, because the view you were on is a real place.
On a phone, rows become cards, and the same filters apply. The list you see in a meeting is the list you saw at your desk.
Editing without fear
Changes give immediate feedback, and destructive actions are clearly marked and confirmed — deleting a task asks first; there's no undo-roulette. Because Acme is live, an edit made by a teammate shows up in your list without a refresh, so two people can work the same list in a standup without talking over each other's state.
None of this is novel, and that is the point. Acme's task tracking is deliberately boring, so that the interesting thing can be your work.