To plan your workday, decide before the day starts which tasks you will do, in what order, and in which time slots. The four systems here - Getting Things Done, Time Blocking, RPM and Personal Kanban - range from a full trusted system to a single visual board. This page explains what workday planning involves, how to choose a planning method that matches how you work, and where daily and weekly planning meet.
Planning your workday means doing three things before the day starts: writing down everything you have taken on, deciding what today is actually for, and giving the chosen work real hours. All three are verbs, and that matters: a plan is something you do rather than something you own. Skip the writing and you plan around whatever you happen to remember. Skip the deciding and you have an inventory. Skip the hours and you have intentions with nothing holding space open for them.
The writing-down step gets skipped most, because it feels like admin rather than work. At work the commitments arrive through more channels than memory can track: mail, chat, a decision made out loud in a meeting, a promise on a call that never reached a list. Anything held only in your head keeps announcing itself to prove it has not been forgotten, which is the premise David Allen built Getting Things Done on. One place to put all of it is the whole fix; which place matters far less than using it consistently.
Deciding is where planning meets prioritizing, and the two questions differ. Prioritizing asks which of these deserves the day; planning asks when each survivor happens and in what order. A list captured but never ranked gets worked from the top, which hands the day to whatever was written down first. When the ranking is the part that keeps stalling rather than the placing, the prioritization methods take that question head on.
Giving the work hours turns a plan into something you can test before the day disproves it. A list is silent about duration: it reads the same whether it holds an afternoon of work or a week of it. A calendar is not silent, and the disagreement surfaces the moment you try to fit one into the other. Time Blocking exists to force that disagreement early, while there is still room to drop something on purpose, instead of at half past five, when the only move left is pushing the rest into tomorrow.
None of this produces a document you keep. A plan is a set of decisions with a short shelf life: the one written on Monday describes a week that has already moved by Wednesday, because a meeting shifted or the thing you thought was a morning turned out to be most of a day. Re-deciding is not evidence that the planning failed. Re-deciding is the planning, and every method below is built to be re-run, not rewritten.
Planning has a boundary worth naming. It cannot add hours, and it will not rescue a week carrying more work than it has room for; what it does is make that shortfall visible on Monday instead of Friday, while saying so is still useful to the people waiting. If your plans fail by the same margin every week, the volume is wrong rather than the method, which is a conversation about what you have agreed to. When the difficulty is holding attention after the plan exists, the focus methods are the nearer shelf, and the hub sorts all seventeen by what they fix.
The four planning methods differ less in what they believe than in what they cost. Each keeps the plan on a different surface - a set of lists, a calendar, a written outcome plan, a board - and each charges its own upkeep for it. So the deciding question is not which is best, but which surface you would still be maintaining a month from now.
Getting Things Done is the choice when the trouble is volume. David Allen's system is the only one of the four that treats collecting as a step of its own: capture everything, clarify what each item requires, sort the results into lists, then work from the lists rather than from memory. It is also the most machinery this site asks for anywhere, rated advanced and resting on a weekly review its method page puts at one to two hours. GTD suits Architects, who want the whole system visible before trusting any part of it; it returns little to someone with one project and a quiet inbox.
Time Blocking is the choice when the trouble is the day rather than the list. Each task becomes a block on the calendar with a start, a duration and an end, which fits work that is already calendar-shaped: meetings you did not call, handovers with fixed windows, work that must happen while a particular colleague is at their desk. The gain is that your own work stops being the only item with no defended slot. The prices are arithmetic and slack: its method page puts daily planning at fifteen to thirty minutes and treats buffers as structure, since blocks packed back to back collapse the first time one runs long. It suits Architects, and anyone whose calendar is largely written by others.
Rapid Planning Method is the choice when the trouble is direction. Tony Robbins's system runs the usual order backwards: name the Result you want in a form that can be checked true or false, name the Purpose that makes it worth the week, then write only the actions that serve it. It is built for people who get through their tasks reliably and still find the thing that matters sitting where it was on Monday - the Visionary's week. The cost is ceremony: its method page puts the weekly session at thirty to sixty minutes, so spend it on the handful of outcomes that decide the quarter and leave routine work on a plain list.
Personal Kanban is the choice when too much is already open. Three columns - To Do, Doing, Done - and a hard cap on how many cards may sit in Doing at once. A board answers two questions a list cannot: how much is open at once, and which of it has stopped moving. The cap does the real work: nothing new may start until something leaves the middle column. It is the lightest of the four, rated beginner, upkeep a five-minute board review a day, and it suits visual thinkers and the Improviser, who would rather nudge a board than rebuild a schedule.
The costs above are the real dividing line, running from a five-minute board review to a weekly review of one to two hours; that spread matters more than any feature comparison. Read what is left against the four working-style profiles on the front page, one of which will sound like your ordinary week, and against the comparison table naming the methods each style should try first. Weigh that upkeep against your worst week rather than your best: a planning system earns its place on the weeks already going badly.
Each of the four also has one step that carries the rest, and it is reliably the one that feels most skippable: the weekly review for Getting Things Done, without which the lists go stale and stop being trusted; the buffer for Time Blocking, without which one task running long takes the afternoon with it; results rather than activities for RPM, since an outcome can be checked on Friday and an activity cannot; the cap on Doing for Personal Kanban, which stops being a cap the first time it is treated as a suggestion. Protect that step first.
Most planning systems run two passes at different rhythms, and they do different jobs. The weekly pass sets the frame: what the week owes, which large pieces need room, where the days are already spoken for. The daily pass fills that frame in: what today holds, in what order, against the hours genuinely free. Run only one and the missing half soon makes itself known.
The weekly pass is the only one with a view wide enough to see shape. Laid out whole, a week shows which days have already gone to meetings, where each deadline lands, and whether the work you keep meaning to start has anywhere to live. It is also where a repeating collision becomes visible - the report that always falls on the same afternoon as the review meeting - and a collision spotted on Monday can be moved, while the same one met on Thursday can only be absorbed. When a week laid out this way comes back mostly booked, no ordering of what remains will recover the missing hours; the question that comes first is how much of the week meetings are allowed to take. Both weekly-cadence methods here work at this level: RPM sets the week's results, the GTD review keeps the lists worth reading.
The daily pass is short and should stay short. Its job is to reconcile the frame with the day that actually turned up: the meeting added overnight, the task that ran to twice its estimate, the request that arrived after you left. Time Blocking reconciles by assigning hours; a Kanban board does it by pulling the next card once something leaves Doing. Either way it is minutes rather than a sitting, and it holds up best attached to a fixed moment you already keep, so planning does not depend on remembering to plan.
Dropping either pass fails in its own way. Run only the daily one and you get a well-ordered series of days that never adds up: the work with no deadline attached is postponed by a run of individually reasonable decisions. Run only the weekly one and the plan meets its first real Tuesday with no mechanism for repair, so it gets abandoned rather than adjusted. That second failure is where most people conclude planning does not work for them, when what went missing was the smaller pass.
So keep both, keep both small, and put the weekly one at the close of the week rather than the start of the next, while you still remember why things moved. Write what the week owes in a form you can check on Friday: a draft sent, a decision made, a release out. Areas to work on cannot be checked, and what cannot be checked will not warn you while there is still a week left. And if the plan survives only by dropping the same category of work each time, carry that into the next weekly pass as an item of its own.
A comprehensive methodology for managing commitments and tasks. GTD is built on the principle that your mind is for having ideas, not holding them. By getting everything out of your head, you reduce stress and increase clarity.
Instead of a separate to-do list, time blocking assigns every task a specific time slot on your calendar. This forces you to confront the reality of how much time you have and ensures your priorities get protected time.
An outcome-focused planning system that connects your daily actions to a deeper sense of purpose. Instead of a list of 'to-dos,' you create a plan for 'outcomes,' which provides clarity and motivation.
A visual workflow management method that helps you see your work, identify bottlenecks, and focus on finishing tasks. By limiting how many items are in 'Doing' at once, you reduce context switching and increase completion rates.
Plan your day at work before it starts: write down what you have taken on, decide the few things the day is really for, and give those a place in the hours you actually have free. The order matters. Deciding without writing down means planning around whatever you happened to remember, and deciding without placing leaves a list that has never met the length of an afternoon. Keep the pass short and attach it to a fixed moment, ideally the end of the previous day, so the plan is waiting rather than invented while the day is already running.
Schedule your day by giving each chosen task a start time and an end on the calendar, placing the work that must be protected first and letting flexible work fill in around it. Estimate before you place, because the collision between a list and a day only appears once durations are attached. Then leave buffers, since a schedule with no slack fails the first time something runs long. Time Blocking is built around this, and its guidance is to treat blocks as appointments and to schedule only the mornings when the rest of the day is unpredictable.
A list works when every line names a physical next action, when it is short enough to fit the day, and when finishing something is the condition for starting the next thing. Vague entries are what stall a list: an entry reading taxes gives you nothing to begin, while one naming the call you owe the accountant does. Getting Things Done makes that translation a step of its own. Cap what is open at any moment, the way a Kanban board caps its Doing column, and price the list in hours against the calendar before you believe it.
The best day planning method is the one whose upkeep you will still be paying in a month, which depends on how much your week changes and how much structure you want. This site covers four. Getting Things Done carries many open commitments and charges a weekly review. Time Blocking suits days shaped by other people's calendars. The Rapid Planning Method starts from the outcome, not the task. Personal Kanban is the lightest, a board with a cap on what may be in progress. Match one to the week you actually have, and let a heavy week be the test.