Why there is no assign button.

What that field does to a team

Work lands without a conversation. Load stays invisible until somebody breaks. And the person doing the assigning becomes a dispatcher — a job nobody wanted, least of all them.

You didn't hire people who need a queue. You hired people who can think. Your tooling should act like it.

What I did instead

Work reaches you as a suggestion. You accept it, and it becomes yours — your list, your order, your day. Or you decline it, and the software makes you write a sentence saying why.

That sentence is the whole design. A silent no tells the person nothing. A no with a reason is a conversation that already started.

These are rails, not gaps.

You can't assign work. You can't flag something urgent. You can't keep a backlog. None of that is a feature I haven't got round to — each one is a decision, and the decisions are the product.

That's what opinionated software buys you: the arguments are already settled, so your team stops relitigating how to use the tool and gets on with the work. Good rails mean you go faster without steering.

The cost is real. If you disagree with an opinion there's no setting to switch it off. If that sounds like a limitation, this isn't for you and I'd rather you found out here. If it sounds like a relief, you already get it.

The work keeps arriving. That part isn't going to change.

Email, Slack, forms, tickets, someone stopping by your desk. The volume isn't a personal failing and no amount of discipline makes it stop. What you can decide is where it lands and how long it's allowed to sit there.

There is a proper way to handle this, and most software isn't doing it. A backlog that grows forever isn't a system, it's a pile with a search box. Notifications you didn't ask for aren't a feature, they're someone else choosing when you get interrupted.

TeamList is the disciplined version. Work comes in by email, gets a date, and leaves until that date. Your list holds today and nothing else. Your summary arrives at the hour you picked. Nothing here is designed to pull you back in.

Where the idea comes from

Mark Hurst's Bit Literacy made the case years ago: the bits keep coming, so the skill is letting them through without letting them pile up. Todo list at zero. Inbox at zero. Not as a productivity stunt — as a way to stop carrying things you aren't going to do today.

That book is why this list only holds today, and why finishing it is the goal state rather than an empty screen the software apologises for.

What it costs you

Suggesting is slower than assigning. There will be Tuesdays when you want the button and it isn't there. When something is genuinely on fire you have to talk to a person rather than drag a card.

I think that trade is right. You should know it's a trade — anyone who tells you their product has no downside is selling something.

I build with small teams too.

I'm JD. I run Simple Focus and a portfolio of products. Small teams, lean, no appetite for software that needs administering.

I built TeamList for my own team before anyone else's. I know enough agency owners and product people to know what we actually want, and it isn't another platform — it's something capable and reasonable, that respects the people using it and earns its place in a week rather than a quarter.

You already know how you want to run your team. I built the rails I wanted for mine.

No implementation. No call.

Sign up, write your first todo, invite one person. That is the setup.

There is no onboarding sequence to sit through, no migration, no sandbox environment, and nobody from enterprise sales who needs to understand your workflow before quoting you a number. If it doesn't fit how you work, you'll know inside a day instead of after a quarter.