Work Planner: Organize Tasks Without Heavy PM Tools

Blog image

A work planner stops working the moment everything on it looks equally urgent. Not because the tasks are wrong, but because a flat list strips out the one thing that decides what you actually do next: what state each task is in. "Email the vendor," "wait for legal to respond," "decide on the headcount split," "review Sam's draft" — a normal to-do list flattens those into four identical checkboxes, and then you spend the morning re-sorting them in your head instead of doing them. This piece lays out a different build: a work planner organized around work states, kept separate from meetings, with a daily rhythm for remote work and a clear line for when you actually need heavier software.

That sorting tax is real, and it compounds. The American Psychological Association's summary of task-switching research found that people lose time every time they switch between tasks, and lose more when the tasks are unfamiliar or complex. A flat planner forces a switch every time you read it — you re-evaluate each item from scratch. The fix isn't a better app. It's a better axis.

I rebuilt my own planner three times over two cycles before this stuck — Maren, after the third rebuild, finally survived a full quarter. The version that held wasn't prettier. It just sorted by state.

Blog image

Work Planning Fails When Everything Looks Equally Urgent

The standard advice is to prioritize by urgency and importance. That's the Eisenhower principle — Dwight Eisenhower's line, which Todoist's writeup traces to a 1954 speech, was that what's urgent is seldom important and what's important is seldom urgent. It's a genuinely useful sorting frame, and I'm not arguing against it.

But it answers a different question than the one that stalls most workdays. Urgency tells you which task matters. It doesn't tell you whether you can act on it right now. Half my stalled tasks weren't low-priority — they were high-priority things I physically couldn't move because I was waiting on someone else. Sorting those by urgency just put a red flag on something I couldn't touch. The more useful first cut isn't "how urgent" — it's "what state is this in."

Build a Planner Around Work States

Here's the core move: sort work tasks into four states based on what they're waiting on, not how important they are. Importance is a second pass inside each state. The four states cover almost everything that lands on a knowledge worker's plate.

Blog image

Doing

Tasks that are fully in your court, right now, with nothing blocking them. You have everything you need; the only variable is your attention. This is the only state you should pull from when you sit down to do focused work. If a task isn't in Doing, it doesn't belong in your next ninety minutes — and most planners fail because they bury three actionable tasks under twelve that aren't.

Keep this list short on purpose. A Doing list with twenty items isn't a plan, it's the same flat pile with a new label. Three to five is the honest number for a focused block.

Waiting

Tasks that are blocked on someone or something else — a reply, an approval, a delivery, a decision that isn't yours. These are not your tasks right now, and the mistake is leaving them mixed in where they nag at you. Move them out of sight but not out of mind. The only action a Waiting item needs from you is a follow-up if it goes stale, which is a different motion than doing the task itself.

This is the state that quietly breaks most planners. A blocked task left in the main list reads as "you're behind," when really you're just waiting. Separating it removes a whole layer of false guilt.

Discussing

Tasks that need a conversation before they can move — an alignment you haven't had, a question that needs a real back-and-forth, a decision that requires another person in the room. These aren't blocked the way Waiting items are; they need you to initiate something, but that something is a conversation, not solo work. Batching these is useful: a single check-in can often clear three Discussing items at once.

Reviewing

Tasks where the work is done by someone else and your job is to look, judge, and respond — a draft to read, a proposal to approve, a PR to check. This is low-warmup work; you can do it in the gaps where you don't have the runway for a deep Doing task. Knowing something is in Reviewing rather than Doing tells you it fits a fifteen-minute window between meetings, which is exactly the kind of slot a flat list wastes.

The payoff of the four states: when you open the planner, you're not re-deciding everything. You go to Doing when you have focus, Reviewing when you have scraps of time, Discussing when you're about to talk to people anyway, and you leave Waiting alone until it's stale. The state tells you the motion.

Plan Meetings and Follow-Ups Separately From Tasks

Meetings are not tasks, and jamming them into the same list is a quiet reason planners collapse. A meeting is a fixed point in time you show up to; a task is something you pull when you have capacity. They obey different logic, and mixing them makes both worse — your task list looks falsely full, and your meetings lose their prep.

Keep meetings on the calendar where they belong, and give each recurring or important one a tiny attached note: what you need going in, what you owe coming out. The "coming out" part is where follow-ups live, and follow-ups are the single most-dropped category of work I know. A meeting ends, three action items get verbally agreed, and they evaporate because they never made it onto a list. The fix is a deliberate motion: the last two minutes of any meeting, the follow-ups become Doing or Waiting items in your planner. Not "later" — right then.

This is also where a memory-keeping tool earns its place over a static list. The follow-up from last week's sync only matters if something remembers it surfaced. A planner that forgets context between weeks makes you the memory, and you are not a reliable database at 5 p.m. on a Thursday — which is the gap personal AI tools are built to fill, holding recurring context so you don't have to re-supply it every week.

A Work-From-Home Planning Rhythm

Blog image

Remote work removes the ambient structure an office gives you for free — no commute to bookend the day, no visible cue that everyone's wrapping up. The productivity isn't the problem; Stanford research led by Nicholas Bloom, reported by Stanford, found hybrid work had no negative effect on output when it was managed deliberately. The catch is that word — deliberately. A lot of work from home apps overcorrect by adding more structure than anyone can sustain. You don't need a fourteen-widget dashboard. You need three moments.

Morning: a five-minute pull. Look at Doing, pick the two or three things that have to move today, and ignore the rest of the states until they're relevant. Don't re-plan the whole week; just load today.

Midday: a state check, not a guilt check. Did anything in Waiting come unblocked and need to move to Doing? Did a meeting just create follow-ups? This is maintenance, not a full re-sort — two minutes, tops.

End of day: a close-out. Move finished items off Doing, push any unfinished ones honestly forward, and glance at tomorrow's calendar so the morning pull is fast. The point of the end-of-day pass isn't completeness — it's letting yourself stop. Remote work blurs the line where the workday ends, and a deliberate close-out is how you redraw it.

The rhythm matters more than the tool. I've run this in a notebook and in an app, and the notebook version worked fine for a while — it fell apart only when the volume got high enough that I needed something to remember Waiting items for me.

When to Graduate to a Task Management Dashboard

Here's the honest boundary, because most people reach for heavy software far too early. A full task management dashboard — the kind with assignees, dependencies, custom fields, and reporting — is built for teams coordinating shared work. If you're planning your own tasks, that machinery is overhead you'll spend more time feeding than benefiting from.

You've genuinely outgrown a personal planner when: multiple people need to see and update the same tasks; work has formal dependencies where one person's output blocks another's start; or someone above you needs reporting on status across a whole project. Those are coordination problems, and a dashboard solves coordination. None of them are solved by a solo work planner, and none of them appear just because you're busy.

Busy is not the signal. Shared accountability is. If the only person who needs to see your tasks is you, a state-based planner will almost always beat a dashboard — less setup, less maintenance, faster to actually use. (If you do decide you need the heavier option, that's a separate decision worth comparing properly against your actual workflow rather than picking the most-marketed one.) The tools worth considering at that point are the dedicated team apps, not a souped-up personal list.

FAQ

Blog image

What is a work planner?

A work planner is a personal system for organizing the tasks, meetings, and follow-ups of your job so you know what to do next without re-deciding every time you look at it. It's distinct from a team project tool: a planner is for one person's work, optimized for fast daily use rather than shared coordination. The version in this piece sorts by work state — Doing, Waiting, Discussing, Reviewing — instead of by a flat priority list.

How do I organize tasks at work?

Start by sorting every task into one state based on what it's waiting on: can you act now (Doing), are you blocked on someone (Waiting), does it need a conversation (Discussing), or are you judging someone else's work (Reviewing)? Then prioritize within each state. When you sit down to work, pull only from the state that matches the time and energy you have. This beats a single ranked list because it tells you not just what matters, but what you can actually move right now.

Do I need a task management dashboard?

Probably not, if the work is only yours. Dashboards earn their complexity when multiple people share tasks, when work has formal dependencies, or when someone needs status reporting across a project. If none of those apply, a dashboard is mostly setup and maintenance you'll abandon. The trigger to graduate is shared accountability, not how busy you feel — busy alone is solved by better sorting, not heavier software.

How should remote workers plan their day?

Build three deliberate moments to replace the structure an office provides: a five-minute morning pull (pick today's two or three Doing items), a midday state check (move anything newly unblocked, capture meeting follow-ups), and an end-of-day close-out (clear finished items, glance at tomorrow). The close-out matters most for remote work — it's how you mark where the workday ends when nothing else does. Keep the system light; the rhythm does the work, not the app.

If your current planner leaves you re-sorting the same list every morning, try the state cut for one real week before changing anything else — just label each task Doing, Waiting, Discussing, or Reviewing and pull only from Doing when you sit down to focus. By Friday you'll know whether the problem was your priorities or just the shape of the list. That's the test I'd start with.

Previous posts: