What do YOU have in your Context list? Pls share it here

Definitely makes sense, thanks for your answer!

1 Like

Not a lot in mine, I keep it simple:


  • Wife
  • Accountant
  • Sister

I recently reworked my Context list inspired by an interesting blog post from Ben Brooks as well as Colter Reed’s great blog “Manage your Time. Manage Your Life”. It has been really working well for me so far so I wanted to share my setup in this thread as an additional option. This setup heavily leverages the idea that everything we do can be put into one of four quadrants on a grid, depending on whether or not it’s important and whether or not it’s urgent instead of using location and/or tool based contexts as most of my work can be done anywhere and all I need is a computer/iPad/iPhone and an internet connection. These context help me a lot with my weekly and daily planning and make sure I keep my attention where it needs to be: on the most important things, and not on the “latest and loudest”.

So here my current Contexts:

If I set the context of a task to “Urgent” this tasks requires my "immediate attention”. In other words something that is urgent simply means something that must be done immediately or the latest on the day it is due. I am working in customer success so typically these are tasks that are business critical for customers to get done and need to be take care of immediately or by a specific agreed on date. Usually these urgent tasks are not too many so the overall length of this list has not too bad so far.

Task with this context are the most important tasks to me. These are tasks that typically relate to my strategic projects and (delivery) improvement initiatives. The are the tasks that tend to easily fall off in the hectic of the day as they are not urgent (yet) but in the end are the ones that really make a difference and move strategic projects (work & personal) forward. This is the work that I care about doing and should be doing, the stuff that really matters. I am very rigorous and really only have tasks of strategic projects on there I am actively working on. If a strategic project drops in priority I copy it into a “On Hold/Someday” project that I have set to the “On Hold” status. I review these “On Hold/Someday” projects in this project list weekly so if I can actively work on a project in this list again I drag it back into my active project list. As I typically try to not have more than a few strategic projects I am working on at one point in time, this list usually doesn’t get very long.

Earliest Opportunity
This context is certainly very close to important. I use it for all tasks that are related to non-strategic projects. These tasks are typically tasks that are both important, but not at all urgent. In other words things I want to do at one point but not that will ever have a timeline associated with doing them as they have no strategic relevance to me. Just get them done at the earliest opportunity. This list has been getting quite long so I try to be very mindful which of these tasks are really active or can be deferred or belong in the “Someday/Maybe” context.

Anything where I have to communicate with someone (send an email, call, etc.). These are typically tasks that often end up with a “Waiting For” follow-up task. I put them into a separate Context as a lot of these tasks in there can be done if I have some unexpected (short) window of time I can use to work on them.

I want to talk to someone about something. I don’t add sub-context but rather search for the individual. So format I use when I create a new “Agendas” task is:

%Person%: What I want to talk to them about/need from them/etc.

This way I don’t end up with a huge list of different sub-contexts and the search feature in OmniFocus works great for this purpose. I did created a perspective for my boss that I can quickly open up when I have my one-on-one with him or need to chat with him. All I did was add his “%BossName%:” in the “Filtering text:” field of the perspective. This way the perspective shows all the Agenda items I want to talk to him about.

For example my Agenda would look like this:

My “Agenda - Boss” like this:

And the output of the “Agenda Boss” perspective would be this:

So I only get the agenda Items for my boss based on the filter criteria I added to the perspective.

Any articles, books, movies I want to read, review, or watch. Like I found something interesting on the internet I will create a read/review action item with the URL in the note that points me to the location on the internet where I found out about it.

When I am out and about what I need to pick up or get. I created a number of sub-contexts under the “Errands” context as I am heavily using the location services on my iPhone for some of the places I run errands at. Extremely helpful to me so I don’t forget something I am out and close to a place I could get the item on my list. I see the list as an OmniFocus notification on my iPhone/Apple Watch when I get close to the place I need something from. Very handy.

Waiting For
If I delegate a task, but still want to track it — or if I can’t start a task until I get something back (email response, etc.) — it gets this context. That way I can look at the Waiting For list to see who I need to bug and about what. It’s what keeps things from slipping through the cracks for me.

Ideas or something I want to do one day.

So far this setup has been working well although my biggest concern is always that specific lists get too long and therefore overwhelming and it repels me to taking a look at them. Will get a better feel over the next few weeks how things work out with these new contexts and if the number of tasks in these contexts don’t get too long.


I came across that blog post as well and I am glad it worked for you. It is another attempt to combine the Four Quadrants approach with GTD using OmniFocus, theoratically taking the best parts of both systems. While I understand the logic behind defining urgency and importance as contexts, it just does not feel right to me.

Here is why I feel that way:

Urgency means there is a deadline for completing certain tasks or projects regardless of its importance. Tasks become urgent as their due dates approach. A task which is due 2 weeks from now is not really urgent at this stage but it will be in 2 weeks time. Assigning “Urgent” context to this task would create a false sense of urgency. I could, of course, use defer dates in conjunction with Urgent to get it out of my way until it became urgent. I could also add due dates as a reminder. But then such tasks would not be “available” before the defer date although there was nothing that prevented me from completing them before their deadlines. I would need to constantly review “remaining” tasks and change their attributes. I do not see any real benefit of setting up a system in such a way.

Furthermore, tasks can be Urgent and Important (or any combination of those) at the same time - this is how the Four Quadrant model works. However, you cannot assign those two contexts at the same time to a single task in OmniFocus. Flags could be useful at this stage for highlighting important tasks but this would create confusion.

Then there are further questions: what happens if I need to make an important phone call which is also urgent? Should I assign Important, Urgent or Communications? If I assign Important, it will not be listed under Communications. What happens if I need to run an errand (e.g. do grocery shopping for an important dinner tonight)? How would I manage not urgent/not important and urgent/important tasks?

I would have to split tasks between urgency/importance contexts and traditional location/tool/people contexts. Unfortunately my mind does not work that way: if there are quadrants, tasks must be in one of those quadrants.

The “Earliest Opportunity” context you mention above seems to represent Quadrant 2 (Important/Not Urgent). That’s another problem for me because there are no other contexts that represent other three quadrants. Also, there is already a context for important and another one for urgent. If a task was assigned Important but no due date or Urgent, would it not represent Quadrant 2 as well?

I would like to hear how you overcome such issues. The closest I could get with prioritization using contexts was to have Must Do, Should Do, Could Do and Waiting contexts. This worked fine for a while but then I realized I could not make proper use of location contexts (no geotagged tasks).

First, I might address the priority matrix concept. I also struggled with the meaning of Urgent and Important to set priorities. I eventually switched to a Must, Should, Could Do paradigm as you have. Even that eventually became a bit fuzzy. At the moment, I tend toward using an equivalent of Need To and Asked To. This adds a selection for what others expect of me (versus what I expect of myself). I need to (do something) when not doing has consequences that I am entirely unwilling to accept. I am asked to (do something) when something or someone outside of me requests of me (to do it).

In a traditional 1 - 4 list (with 1 highest), this becomes

  • N + A: 1
  • N: 2
  • A: 3
  • !N + !A: 4

Add Due or Not Due to this, cast your contexts based on what suits you best, and you have a rather potent set up IMO. Here are some rough examples

  • file taxes - N+A (+D) --> #1 with a due date
  • draft final report on meeting - N + A (+D) --> #1 with a due date
  • respond to an informal birthday party invitation - A --> #3 (perhaps with a due date)
  • exersize this morning - N --> #2 (perhaps with a flag as a repeat reminder)
  • invite Larry to dinner - !N + !A --> #4
  • outline ideas for Wastewater Runoff Report - A --> #3 (perhaps with a due date)
  • buy paint for bedroom walls - !N + !A --> #4 (until my spouse bumps this to #1 :-) )
  • collect documents for investment meeting - A (+D) --> #3 with a due date

Now with this as a background, I will note that I do not use contexts to set priorities in OF. I filter based on due dates, flags, and the ordering of my context list to set my priorities. That is a completely different story in a bunch of different threads.


1 Like

Some more interesting discussions in this thread, as always, and while I’ve always shied away from the quadrant approach (at least in recent years – I used it more back in the nineties when Franklin Covey was all the rage), I tried messing with contexts to set priority years ago, and it just didn’t work for me, at all. Too narrow since things can only have one context. Tags could solve this, even pseudo-tags, but I find that things change often enough that this is also more trouble than it’s worth (for me, at least). That said, I think my workflow (somewhat described above in this thread and elsewhere) inherently takes some of this into account – as much as I need, anyway – without my even fully realizing it until I sit down and think about it.

For example, I’m very focused on using due dates only for “hard landscape” tasks, but I’m also not against giving myself a hard landscape for certain things that I feel have a need. Ergo, anything with a due date becomes “Urgent” automatically. This is clearly the “Must Do” or N+A and N stuff. While the “hard landscape” approach to due dates suggests that tasks need to have consequences, there is such a thing as personal consequences in terms of meeting one’s own goals and objectives.

For instance, I have an exercise regimen that I want to stick to on a daily basis. I used to just make that a flagged task, but I found it was too easy to ignore that if I was otherwise busy. Now it has a due time of 8AM that pushes me to do it before I start my workday, rather than just feel that it can drift off the bottom. It’s a mindset, but putting that due time on there automatically puts it into the Important+Urgent category. It suddenly becomes a “Must Do” for me.

The thing I like about OmniFocus, however, is its fluidity, and this was where quadrant systems always felt too intransigent. I mean, yes, you can move things around between quadrants, but that always felt more like admitting defeat rather than reprioritizing stuff based on an actual schedule of timelines.

Life is fluid, priorities changes, both external and internal, and the ability to review and adjust things is critical to a good workflow, IMHO (the same lessons I’ve been learning about budgeting over the years too, but that’s another story :) ).

For example, as much as my morning routine is in the “Must Do” category, if something more important came up, that could easily be pushed off. I might adjust the due date to later in the day, or I might decide that it really does need to be skipped today and simply move it to tomorrow. Adjusting the due time on it feels like a more conscious decision (to me) to plan my time than simply moving it around between contexts, or otherwise figuring out how to deal with it in a more nebulous way.

Or, to put it in a job context, I’m working on a report that’s due today at 4:00. That’s clearly a “Must Do” N+A type of task. Then the client sends me an email and says that a security breach has come up and needs to be investigated right away. Do I keep working on the report? Of course not, I reprioritize. The report is still N+A, but just not for today any more.

So to line it up with the past couple of posts, my take on the categories would be more like this:

Must Do: Flagged, Due Date
Should Do: Flagged
Could Do: Available, Unflagged

In all cases, defer dates are assigned as appropriate for things that are further out. For example, my taxes are already in OmniFocus for next spring with due dates all set up, but obviously I’m not in a position to even LOOK at them until at least March, so the first action in that project is flagged and deferred until March 1st.

The beauty of flags and due dates in the OmniFocus approach as well is that longer-term tasks can flow from Could, to Should, to Must very easily, and even somewhat automatically. Take taxes, for instance… My first action might be “Collect T4 slips” (our equivalent of a U.S. W2), with the following parameters:

Due: March 15th
Defer: February 1st
Context: Desk

On February 1st, that task becomes a “could do.” It’s now available in my Desk context if I’m looking for stuff to do. I can do it, but I don’t really need to yet. If I do nothing at all about it until March 14th, then suddenly it will go from Could to Must, but usually I’ve seen it and addressed it long before it gets to that point.

The key to this aspect of making things work is the Review process. As I’ve said elsewhere, that really is the secret sauce that makes the system work. I go through a detailed review every Monday morning, looking at all of my relevant remaining tasks to determine what needs to be done. Again, life and priorities change, and while I may think I have all the time in the world to do my taxes in March, I may be buried in the middle of five projects by the time March rolls around and tearing my hair out. Dates will get shifted around during the review process to account for this.

So in the example above, when February 1st hit, I’d see my “Collect T4s” task and make a decision on what to do about it. If it’s still in the “Could” category, I leave it alone. If I know that February and March are going to be crazy, I move it to the “Should” category, giving it a flag and maybe adjusting the defer date (to reflect the day that I actually plan to deal with it). As I move closer to the deadline, I’m going to keep seeing it in the weekly reviews, and will likely flag it at some point regardless to give myself more lead time, moving it into a Should/Must sort of split. My main working context shows only flagged items, but sorts by due date, so anything with any due date whatsoever ends up at the top. These are inherently and always higher priority than anything without a due date (the pure “Should” stuff).

A word on Reviews as well… OmniFocus’ Review system is second to none, and a key to that process is setting Review cycles and “Next Review” dates. As I’ve said, my taxes project is already in OmniFocus, lurking there to come up for Review in February. Since it’s only October right now, however, it doesn’t come up in my weekly reviews. There’s no point to keep looking at it every week as it’s not relevant right now. Similarly, I have projects I review regularly, but they don’t change often enough to warrant a weekly review, so they’re set to be reviewed every 2, 4, or 8 weeks. They don’t disappear off my list in the long term, but I don’t need to keep looking at the same lists of tasks every week and going “Yup, still the same. Nothing different to do here.” This is especially true for those single-action lists and projects that already include routine and recurring flagged tasks.

One thing that I haven’t really addressed in my system, mind you, is “Important” vs “Urgent.” The “Should Do” kind of covers that, but not directly. The fact is that what’s important but not urgent for me is usually really obvious, and I prioritize those again by flags (“Should Do”), or by sorting – most of my “Important” projects and single-action-lists are higher in my project hierarchy, so their flagged tasks sort above the lesser important ones. Again, this is something I’ve inherently done without giving it much thought to a “Four Quadrants” approach, and it works quite well for me.


After reading this thread and related posts, I’ve come to a simplified system that I’d like to share.

Like many here, I’ve tried and ultimately failed at most of the various context systems - traditional, energy, time, etc. While a part of me loves the more granular systems, I’ve found that they work better on paper than in practice. Between the way my world and my brain work, these context systems are just not compatible with me.

The simplified list that hwend88 noted and linked above was closest to working for me, but I still needed to boil it down further. So here is my system. I basically have two contexts:


I expand that to account for things for which I need other people - either delegated to them, waiting for a response, or waiting to be with them. In other words, things I cannot do solely by myself.

Important - Pending
Minutiae - Pending

(Side note - I find “pending” creates less anxiety for me than “waiting for”, and also serves the more general definition I have set).

I (try to) review daily using a Plan perspective - which basically shows anything available. I flag anything I want to do today.

I use due dates for things that either have hard external due dates or some unacceptable consequence if I don’t get it done by a certain date.

I have four main perspectives:

Important not Due
Important and Due
Minutiae and Due
Minutiae not Due

As you can see, these are the Four Quadrants. Whether it’s because it’s the first productivity system I learned (as a kid, from my Dad, via Covey) or because it just works with my brain and my world, I have always found the most success and ease with the four quadrants. I don’t always think it’s perfect, but it’s the best I’ve found, for me, so far.

One thing I really like is that tasks due soon will automatically populate the due perspectives as the dates approach (I use 2 days for due soon). Until then, they stay in “not due”. I use Forecast to see my week ahead as well.

I also use pseudo-tags lightly (#tag in notes) for some specific (and more traditional) contexts - for example: #errands and #person (for a few very important people). I then have corresponding perspectives to search for the #tag.

Similar to jdh, I order my project list for priority, so more important tasks float to the top. I don’t necessarily work my way top-down - I’m pretty good with prioritizing on the fly during the day as needed - but it does help when I’m scanning my list. And does give me a psychological push to have the projects I prefer to be working on near the top.

Lastly, I have my projects in folders, generally grouped by my areas of responsibility. This helps sometimes when I’m looking to see all the things to do, for example, for work or around the home or for our household finances.

I am intrigued by both DrJJWMac’s and jdh’s systems - thank you for sharing! I may yet try them one of these days. But my system is working for now, and I’ve too often spent too much time fiddling with Omnifocus rather than getting things done. ;-)

1 Like

Thank you for the compliment.

The use of pending rather than waiting for is interesting. I am curious enough to perhaps give that change a spin in my own implementations of OF. I use it in my Kanban boards rather than waiting for, so it makes great sense.


I had read the same article(s) and considered it an absurd idea until your explanation in how you’ve put it into practice. I’ve drastically trimmed my contexts done into similar roles (urgent/important/achievements/details) and have my minutia and little things under @details accordingly.

It’s the details that give me the most problem sometimes but I think having those little actionable pieces easily surfable is helping.

Great answer, @jdh! Can you share your Contexts and how you use them? Thanks!

I am new to OmniFocus and I am trying to determine the best contexts for my law practice and the workflows in my practice. This is an organic list open to your suggestions and helpful criticism.

No Context

  • Must Do
  • Should Do
  • Could Do
  • Call
  • Email
  • Letter
  • This Week
  • Next Week
  • This Month (Dec. 2015)
  • January 2016
  • December 2016
  • 2017
  • Emails
  • Letters
  • Pleadings
  • Discovery
  • Court Orders
    Planning & Preparation
  • Litigation
  • Business Entities
  • Real Estate
  • Other
    Rituals & Routines
  • Daily
  • Weekly
  • Monthly
    Delegated Tasks
  • Paralegal
  • Client
    Waiting On
  • Client
  • Opposing Counsel
  • Vendor
  • Judge
    Follow Up
  • Daily
  • Weekly
  • Monthly

IANAL, but…

Most of what you have here don’t really seem like contexts to me. The deadlines should be represented with due dates, and you can look at them with the forecast view. Many of the other items are Projects or tasks within projects.

Useful contexts tend to be built around locations or necessary resources, so “County Courthouse”, “Office”, “Phone” are good as well as having a context for each active client to review when you meet with that client as well as anybody else who you have regular meetings with.

You don’t want all your “waiting on client” to be in the same context, instead you want a separate context for each person you might wait on, so you can select a view for that person and see what you need to do with them. Ditto for Opposing Counsels.

You would then define a project for each case and assign appropriate contexts to tasks within that case for the client, opposing counsel, judge, etc. If you are are using the same vendor for multiple cases, looking at that vendor’s context would then show you all the tasks that require that vendor.

Thank you for the comments, @deepeddy. I am going to revisit my approach. Does it make more sense to have @People as a context and then a subcontext for each person (i.e., attorney, client, or other person regardless of their status) then to have @Attorneys, @Clients, and @Others with sub-subcontexts with each individual then labeled a sub-subcontext?

That seems to be up to what works for you. Don’t be afraid to revisit your schema down the road and decide if it works for you or not.

In fact, I’d put a repeating task in place to revisit the schema every few months.

Personally, I created a mind-map of both my contexts contexts and my projects which I revisit every few months.

The “Who, What, Where, When” context scheme turned up in about my 3rd or 4th iteration.

Also, I wasn’t able to really make OmniFocus work for me until I had both my work and personal life using it.


@bradleybclark. I suspect you are mixing contexts and organisation.

For example, How do you anticipate using the Follow-Up contexts?

You may not need the Follow-Up contexts. If you put a task in your Daily list for 'sweep Delegated Tasks - Anyone need chasing?’ With the repeat set as ‘defer another’ one day then you will get the regular prompt to chase overdue stuff. Waiting on could be treated similarly - 'Check waiting On - does anyone need chasing?’

Each task can only have one context, if you are not careful you will be spending a lot of time moving tasks between contexts. If a task is ‘Waiting on: Judge’ it can’t also be in ‘Follow up Weekly’ (though a different task like ‘Check with Court that Judge xyz has received the papers for ABC’ could go there. The downside that you now have two tasks to track rather than one)

You probably won’t need three contexts for waiting on - by setting the appropriate defer dates tasks will be ‘invisible’ until needed. If it is a weekly follow up then set the defer date as Monday or 7days (depending on when you want it to ‘re-appear’

I suspect that the Deadlines will have little benefit - if they are dead dead dead deadlines then use a due date on the project or appropriate task. If you are trying to get visibility of ‘what’s looming’ then having Folders at the project level might be the easiest way to do this.

For your ‘Today’ Context, you might find a perspective (PRO Version of OmniFocus) a better solution. Flag each item that you want to do Today. Then use the ‘Estimated Duration’ field for priority 1 = Must, 2 = Should, 3 = Could.

When creating the perspective

  • Presentation = ‘Sort Actions by: Estimated Duration’
  • Filtering = ‘Flagged’

That said, you might be better served (particularly if you have the standard version) by just flagging the ‘Musts’ and once those are completed, going through the actions flagging ‘Shoulds’ and, once those are done, picking another item as a reward (the coulds).

Some users, aggressively defer out anything that doesn’t have a chance of being done today so anything visible is a ‘Could’ - I have too many possible tasks for that approach.

A Learning Journey

OmniFocus is a huge learning journey, don’t be surprised if you have lots of false turns early in the journey.
The Fewer contexts that you can ‘get away with’ the easier it to decide which context to put a task in. Carefully wording the task helps. As does using the Filter function ( OmniFocus call it the search box) as this enables you to filter the view using keywords.

My own contexts are:

  • Comms. All email, letters, calls go here. The first word of the task tells me what to do - 'e.g. write to architect and tell him where to shove his latest bill’; ‘Call Fred - agree meeting date and location’
  • Do. My catch all, if it doesn’t fit anywhere else it goes in here. Usually I find the right context during the daily/weekly review.
  • Tickler. This is for reminders that I haven’t set a project up for yet (the Project is also Tickler), e.g. ‘Insurance is due for renewal on (dd/mm)’ or key dates - 'Is xxxxxxx domain available now, did yyyy renew it?’ - I have a daily task reminding me to check the ticklers - if there is something there then I either deal with it (<2 mins), kick it into touch for a day or two (defer it again) or set up a project to handle it properly). I find Omnifocus better than using a computer diary (the traditional approach for tickler type items). I do have a physical tickler file as well for tickets etc.
  • Waiting. Stuff that the next action depends on someone else. Typical tasks are ‘Fred - has XYZ application been submitted yet?’ - starting with the individual’s name makes it easy to find, if there are lots of tasks for Fred I can use the filter (search) box to narrow the view down just those things that are with him.
  • Admin. This is where my daily/weekly/monthly tasks and rituals sit. They are dealt with when I am in ‘Admin Mode’.
  • Places. These are location/client specific, I have one for each client, one for home, one for my monthly CEO Group meeting etc/ My location/client contexts start with an @ - that makes it really easy to filter them when entering tasks.
  • People. Several sub-contexts under here. Each of the kids, wife, CEO’s of the client businesses etc. This context gets purged quite regularly. More recently (esp. for Client CEOs and their key Staff) I have been starting tasks with their name and using the appropriate places context. I have perspectives set up for the client company which pull together the appropriate ‘Place’ and the appropriate ‘People’ into a single view. Perspectives are your friend and it is well worth playing with them as a way to consolidate several contexts into a single view.
  • Errands, with the subcontexts for appropriate stores etc. Like many others errands isn’t used for General Shopping - that goes on the iOS ‘reminders list’ because all of us can add/tick off items - the errands is for low urgency items, mostly diy/hardware - there are GEO fenced locations to ‘remind’ me of appropriate tasks when I arrive, this has saved me from many ‘second trips’
  • Mac. For stuff that I need a computer/internet to do.
  • Planning. Like ‘Admin’ this is a ‘mode’ that I block out time to do. This can include working out the major steps in a project or putting tasks in the right place. Typical tasks in this context would be 'Plan - Redecorate Study’ or occasionally tasks that make up a key part of a project that suddenly occur to me that I don’t want to forget and for which there isn’t a full project yet .e.g. ‘Use accountability pairs in CGP Programme’. When I am in planning mode I will either create the project, or put the task in the right place.
  • Reading. - stuff that needs to be read, This is a bit of an orphan context for me. If it is work then it will drop into the ‘Do’ Context ‘Read Board Papers for XXX’ if it is a ‘yeah, whenever’ thing then it should go into the ‘Someday/Maybe’ context
  • Someday/Maybe - nuff said…

Typical Daily Workflow

My typical day will start in Admin mode, running through the morning ritual (which involves looking at the waiting list, checking diary etc.) then flagging the top 3 to 5 items for the day. At this point I will block out time in my diary for the flagged tasks around any meetings that I have - making sure that there is plenty of ‘faffing’ time for the interruptions etc. From here I work in my ‘Today’ context which shows tasks that are ‘Due or Flagged’ (For me due is in the next 5 days, but items with a due date are as rare as rocking horse dung in my database so if they are visible in the perspective it is very important)

If I am in any meetings/Clients I switch to the appropriate perspective to make sure I cover all of my questions/follow ups. I don’t capture actions directly into OmniFocus in meetings (it’s rude and distracting for the other person) but use an A5 case bound day-book. Late PM is back to Admin, transferring actions (theirs and mine) from the day book, cleaning down the inboxs etc.

Good Luck - As mentioned earlier the learning curve is huge, I regularly fall off the wagon and have to climb back on, each time gets a bit easier.

The best bits of advice I got were -

  1. Due dates should be rare, defer dates should be used as often as possible (and changed as often as needed).
  2. If in doubt about whether you will do something then stick it into ‘someday/maybe’ - you are going to put more things into OmniFocus than there are hours in the day to do them so kick as much into touch as you can at the start.
  3. Do your weekly review - remembering to set the review frequency of the project appropriately (not every project needs to be reviewed every week) If your weekly review takes too long, you need to diarise some planning time.

Edit: removed orphan brackets, included reference to Tickler project


Excellent advice. Thank you.

Here’s a typical workflow that I’m trying to figure out how to build into OmniFocus 2 Pro (I’d love suggestions on how to implement this workflow):

  • I receive a Notice of Hearing (“NOH”) from opposing counsel (the NOH sets the day and time for a court hearing. As a result of the NOH, several things have to happen within a particular time.
  • Calendar the hearing date and time.
  • Calendar my deadline to respond.
  • Analyze the motion that is the basis for the hearing.
  • Draft my response.
  • E-file my response.
  • Appear at the hearing.

There are other steps depending on the type of motion (e.g., I have to get an affidavit from a witness or my client to include with the response when I file it). I will be delegating that task to the witness or my client and then waiting on that affidavit.

-{boss’s EA}
weekly exec meeting

I have read thru this whole thread, as I’ve been in a bit of a Contexts re-vamp. Neither tools nor energy levels as contexts has worked. So I came across @DrJJWMac post here (DrJJMac’s contexts) and boom…his way of constructing his conexts has totally jived with the way my brain works. After reading thru this thread from this link, in particular his problem solving parent context with sub-contexts of:

is really working for me, both for projects and my single actions lists. I was already using emojis elsewhere, so this really is an enhancement for me.

So now I have these (duplicated under Working and Non-Working parents, which allows me to quickly filter), Locations (all sub-contexts have actual GPS locations to use on iOS), and a On Hold Waiting context, with sub-contexts for the most regular people (wife, parents, work colleagues), and lastly a “Follow-up” parent context with the same sub-contexts as waiting for. I check Waiting every morning, if the due date is shown, and in fact I need to follow-up, I simply switch to the Follow-Up context or the associated child context for follow-up with a regular, specific individual.

Thank you @DrJJWMac, I think I finally have found a context methodology that will works! Here are mine.

Duplicating them in Working and Not Working parents helps me quickly filter out my areas of focus. I could have made specific Perspectives where I select on the those folders, but I felt for context Perspective where the sidebar shows the context, a quick click on Working and Not Working suites me better in my single “Today” perspective.


I greet as you click to get the context name ??? I like it a lot.

Glad you find my set useful. In the meantime, it looks like this …

The 🔕dropped context follows on a discussion thread here. I use an AppleScript and a toolbar icon to drop or undrop selections of tasks.