# OmniFocus SOP
> [!overview]
> updated:: [[2023-05-28]]
## Best Practices
- Be specific and intentional about project naming. *Status meeting* is less actionable than *Prepare for 2021-08-02 Status Meeting*.
- Weekly reviews are an important part of [[Getting Things Done (GTD)|Getting Things Done]], as well as keeping OmniFocus current.
## Naming conventions
I have a couple of standards I use that help me with creating and using perspectives.
## Top level projects as areas of focus
I maintain the same [[OmniFocus SOP#Johnny Decimal numbering|Johnny Decimal]] structure as I do across the rest of my system (including [[Obsidian SOP|Obsidian]], [[Fantastical]], and [[DEVONthink]].) This allows me to either focus or exclude areas of my life in searches and perspectives (i.e. I don't want to see my 35 Work items while in a 10 Personal head space…)
### Johnny Decimal numbering
All of my top level Project as well as perspectives make use of [[Johnny Decimal]]. This means that I can use the quick switcher to pull up relevant projects or perspectives quickly. It also maintains the same muscle memory across applications.
### Waiting or waiting for
From [[Getting Things Done (GTD)]], I classify some tasks in some version of "waiting" (i.e. there's a future action I need to take… but is reliant on someone or something). I used to be a lot more granular with this, separating out "Waiting" and "waiting for" but it became needless friction.
Tasks designated as waiting are started with **WF //** so that I can quickly search or use it as a common perspective variable.
### Follow up
Similar to [[OmniFocus SOP#Waiting or waiting for|my waiting designator,]] I use a "follow up" context from [[Getting Things Done (GTD)]]. I use two versions of this, **FU //** and **INR FU //** as both allow "FU //" to be a common search or perspective term.
**FU //** means that the ball is clearly in my court. My next action is to follow up.
**WF // INR FU //** stands for "if no response, follow up" and means that I'm waiting for something, whether it be delegated or just something in someone else's court in general. It's equally searchable in my "waiting" or "follow up" workflows.
## Tags
Inspired by the fantastic website, [Learn OmniFocus.](https://learnomnifocus.com/)
- Quality of life — *My new favourite tag…*
- 🗓️ Date & Time
- Today — *Has to happen today.*
- Morning
- Afternoon
- Evening — *Typically a personal or volunteer task project*
- Weekend — *Typically a personal of volunteer task project*
- ⚒️ Tools & Services — *A thing you need to get something done*
- Calendar
- Car — *Technically a location and a tool…*
- Computer
- Conceptboard — *Tool used specifically for work*
- Discord
- Email — *Address neutral; just indicates email action required*
- LinkedIn
- Message
- Microsoft Teams — *Sigh…*
- Obsidian
- OmniFocus
- Online
- Phone
- Printer — *So rare, and yet so necessary*…
- Slack
- 📍 Places — *A place you need to be to get something done*
- Home — *Location aware*
- Arriving — *Location aware, notification*
- Leaving — *Location aware, notification*
- School — *Location aware*
- Arriving — *Location aware, notification*
- Leaving — *Location aware, notification*
- Office — *Location aware*
- Arriving — *Location aware, notification*
- Leaving — *Location aware, notification*
- San Francisco
- Plane — *For things I could do on a plane that doesn't need internet*
- 👩👩👧👧 People — *A person you need to connect with to get something done*
- Category
- Person Name
- Routine
- Errand
- Reset
- Daily Reset
- Weekly Reset
- Maintenance
### Removed
- I've removed the "waiting" tag. It has been replaced with [[OmniFocus SOP#Waiting or waiting for|WF //]] in the task name and strategic use of perspectives.
- I've removed the "delagated" tag as it was causing too much friction. It has been replaced with the [[OmniFocus SOP#Follow up|WF // INR FU //]] convention in the task name.
## References
[Learn OmniFocus - Tags](https://learnomnifocus.com/tags/)