EfficientToDoList.com is an independent editorial site about task management: the software, the methods, and the very unglamorous habits that make the difference between a list you write and a list you finish.
It is written and edited by me, Neve Callaghan. I am 56, I have spent most of my working life running operations teams, and I have opinions about to-do lists that I have earned the hard way.
A note on this domain
Let me be straightforward about something, because the internet rewards honesty far too rarely.
I am not the person who built the original efficienttodolist.com. This domain has a long history — it was, for many years, the home of a Windows task management application published by another company. That project ended. The domain expired. I acquired it in 2026, as a new owner, with no relationship to the previous publisher, no access to their software, and no claim on anything they did here.
So why buy it at all? Because the name says exactly what I care about, and because a domain that spent seventeen years being linked to by people looking for a better way to organise their work deserves better than a parking page full of casino ads. People still arrive here from old software directories, old forum posts, old reviews. They arrive looking for help with their to-do list. I would rather give them something useful than a 404.
What follows on this site is entirely new: new writing, new testing, new editorial standards. Where an old page has been retired, I have tried to point it at a modern article that answers the same underlying question — how do I get my tasks under control on this machine, in this team, with this budget?
How I ended up doing this
I started work in 1992 as a scheduling clerk in a logistics depot outside Manchester. My job was a whiteboard, a clipboard and a phone. The whiteboard was the single source of truth for forty drivers, and if the whiteboard was wrong, forty people spent the day doing the wrong thing. That is where I learned the lesson that still underpins everything I write: a task system is only worth what people actually trust it with. A beautiful tool nobody updates is worse than a scruffy one everybody does.
From there I moved into process improvement, then into operations management. I spent eleven years as Head of Operations at a mid-sized software distributor, responsible for the workload of about 140 people across three time zones. In that role I migrated the company through four different task platforms. Two of those migrations were successes. Two were expensive, demoralising failures, and I was the one who had to stand up and explain why. I learned more from the failures.
Since 2016 I have worked as an independent operations consultant. My clients are mostly small and mid-sized firms — accountancy practices, agencies, a couple of manufacturers — and the brief is almost always the same: we bought a tool, nobody uses it, help. I run the audit, I run the training, and I stay long enough to see whether the new system survives contact with a busy Tuesday.
I am a certified Lean Six Sigma Black Belt, which sounds more impressive than it is. Mostly it means I am unreasonably interested in why things take longer than they should.
What this site is
Three things, and nothing else.
Software reviews written by someone who has migrated a real team
I install the software. I use it for a minimum of three weeks with real work — my own client projects, my own deadlines — before I write about it. I care about the things that only show up after week two: what happens when you have 400 open tasks, what happens when you are offline on a train, what happens when a colleague leaves and their tasks need reassigning, what the export looks like when you decide to leave.
I pay particular attention to Windows desktop tools, because that is where a large share of the working world still lives and because the productivity press systematically under-covers it in favour of whatever is fashionable on a Mac.
Methods, explained without the evangelism
Getting Things Done. Time blocking. The Eisenhower matrix. “First Things First” prioritisation. Kanban for people who do not work in software. These systems all work for somebody. None of them works for everybody, and the productivity industry’s habit of presenting each one as a conversion experience does real harm to people who try it, fail, and conclude that they are the problem.
I write method guides that tell you who a system suits, what it costs you in daily overhead, and the specific circumstances under which it falls apart.
Team and project workflow
Individual productivity is comparatively easy. The hard problem is a shared list — priorities that conflict, tasks with two owners, the status update that is a week stale. Most of my consulting income comes from that problem, so a good part of this site addresses it.
Editorial standards
- I test before I write. If I have not used a tool properly, I say so explicitly rather than paraphrasing a feature page.
- Free means free. When I recommend a free tool, I state precisely what the free tier does not do. Bait-and-switch pricing is my personal bugbear.
- Disclosure. Some links on this site are affiliate links, and some articles are contributed by outside authors. Sponsored or contributed content is labelled as such, at the top of the page, in plain English. No exceptions, no matter what is offered.
- Corrections stay visible. Software changes fast and I get things wrong. When I do, I correct the article and leave a dated note at the bottom saying what changed. I do not quietly rewrite history.
Working with me
I take on a small number of consulting engagements each year — tool selection, workflow audits, and the unfashionable but essential work of getting a team to actually adopt the thing you bought. I also accept a limited amount of contributed and sponsored editorial from companies working in this space, provided it is genuinely useful to the reader and clearly labelled.
If you want to discuss either, or if you simply want to argue with something I have written, the contact page is the place to do it. I read everything, and I answer most of it.
— Neve Callaghan, Editor