Alternatives
Most small teams do not need lighter project management. They need a better operating model.
The word "lightweight" in project management usually means "fewer fields in the ticket." That is not light enough. Paperwork replaces the ticket model entirely with visible work, personal plates, and deliberate decay.
Every year a new tool promises lightweight project management and ships a Kanban board with fewer columns. The ticket is still the center. The backlog still exists. The assignment model still assumes a manager distributing work to a team. It is the same system with a better coat of paint.
I've managed teams of four and teams of forty. The small teams never needed project management — they needed shared awareness and a way to see who was carrying what. The big teams needed PM. The tools do not distinguish between these two completely different problems. Paperwork is not lightweight project management. It is a different operating model for teams small enough that everyone can see the feed.
Lightweight PM vs Paperwork
A lighter ticket board is still a ticket board
Fewer fields, faster UI, simpler workflows — all genuine improvements. But the center of gravity is still a ticket assigned to a person on a board. That model creates backlog rot, assignment theater, and ceremony tax whether the board has ten columns or two.
Small teams need visibility, not workflow
A team of five does not need a ticketing system. They need to see what each person is working on, what is stuck, and what finished. Paperwork provides exactly that through a shared feed and personal focus views.
Feed-based coordination
Work lives in a shared feed instead of a board. Posts carry context, replies capture discussion, and the feed becomes the team's living record. No tickets to create. No boards to maintain. No backlog to groom.
Plates replace assignment
Instead of a manager assigning tickets, each person pulls work onto their plate. The plate is visible, limited, and time-based. Plate discipline — carrying only what you can finish — replaces sprint planning and capacity estimation.
Expiration replaces grooming
Work that nobody keeps alive expires. There is no quarterly backlog grooming session where the team collectively pretends to evaluate 150 stale tickets. If it matters, someone keeps it. If it does not, it disappears.
Who this is actually for
Teams of 3 to 20 people. Engineering teams, design teams, startup teams. People who tried Jira and hated it, tried Linear and liked it but still felt over-tooled, and are wondering if there is something simpler that still works. If you need Gantt charts and resource allocation, we are not the right tool. If you need to see what your team is doing without asking, we are.
Skip the lightweight PM tool. Try a different model.
Request access and set up your team in under a minute. No boards. No tickets. No backlog.