Work shouldn't need a project manager.
Somewhere along the way, task software turned every to-do into a project plan. Pounce keeps the to-dos simple, and the projects too.
Most of it isn't a project.
None of that needs a Gantt chart. It needs three answers: what needs doing, who's got it, and what's waiting. That's what Pounce gives you.
- It's the quote you promised to chase.Today
- The thing Marcus said he'd sort out on Monday.Upcoming
- The customer who's been waiting two days for a reply.Inbox
- The paper order that still hasn't turned up.Waiting
- The five-minute job that's somehow three weeks old.Anytime
Project management got carried away.
It started with a list. Then each task needed fields, seventeen of them. The fields needed boards. The boards needed columns. The columns needed custom statuses, and somebody had to run a meeting to agree what "In review" means.
Then came dependencies. Then automations to move things between statuses. Then dashboards to check the automations were working.
Now half the team spends its day updating the tool, and the Kellett quote still hasn't been chased.
That's project-management theatre. Pounce doesn't do theatre.
Do less. Know more.
- Write something down.
- Give it to someone.
- Put a date on it.
- Wait for somebody.
- Get it done.
That's the whole job. Pounce is built around those five things, and deliberately nothing else.
Sit. Wait. Pounce.
Waiting on someone is part of the job. Pounce treats it like one.
Most task software has a status for this. It's usually called Blocked, and it's where useful information goes to die. Blocked by what? Since when? Who's meant to chase it? The card doesn't say, so nobody chases.
In Pounce, Waiting on is a status with a note. Set it, write down what you're waiting for, pick a date to chase it, and get on with something else.
The note sits right there in the list, so the whole team can see what's holding it up.
Things Pounce will never ask you to do
- Drag a card across a board.
- Agree on a list of custom statuses.
- Debug an automation.
- Build a dashboard nobody opens.
- Buy a seat for a supplier you email twice a year.
- Read twelve notifications about one task.
If your work genuinely needs those things, plenty of tools do them. Most work doesn't.