A weekly status review on projects with one’s boss tends to be part of having a job, and I was recently asked about how I use OmniFocus and Agenda for this process. It was a great question, because it made me think about my workflow so that I am optimizing for both:
- Simplicity – having the right amount of detail and ease of execution
- The audience – making sure my workflow makes it easy for my boss to consume the content I’m offering up
We’re well in to January, but it’s still resolution season, right?
Every year, around this time, I resolve to lose the weight I’ve gained since my twins were born, and every year I… don’t. This year, things are different.
Need to do some last minute holiday shopping? I know I do. Thankfully, I have a workflow for how I approach gift giving, powered by OmniFocus.
I wrote earlier about how I use OmniFocus for organizing my holiday experience, but in response to a reader question, I thought I’d expand on my gift management workflow.
In a previous post, I wrote about my iOS Shortcut that connects Agenda to OmniFocus. With thanks to everyone for their questions, I wanted to follow up with some additional details around how I use the Shortcut and what my workflow is like.
It’s that magical time of year where I have to shovel my driveway four times in one weekend, but it’s so worthwhile, because I’m cozied up by the fire now while the outside is blanketed in beautiful snow that reflects the lights my neighbours have hung with care.
Also, there’s a bajillion things to do. How does one cope?
I thought that, for both my sanity and for the purposes of sharing, I’d break down my holiday construct in OmniFocus.
I’m a meetings guy. Largely not by choice, but a lot of my work day is meetings.
One of the biggest traps of meetings is that, unless they are very well facilitated (spoiler alert: many aren’t), it gets really easy for agreements or commitments to be made but then later lost or never acted on.
After all, saying stuff is easy.
I’ve found just the right solution to this that works for me, though, and so I wanted to write about it.
One of the marquee features of OmniFocus 3 is the move from Contexts to Tags. I adore this capability, but I think it introduces a lot of questions:
How do I use this?
Do I worry about how many Tags I have?
In what ways should I apply those Tags to actions?
Now everyone’s answer to this will be different (which is wonderful, and demonstrates the flexibility of the software here), but I wanted to share my own experience.
I’m going to write a bit more about the Forecast and Forecast Tag in OmniFocus 3, because I think it’s just a plain great thing.
In the physical world, things have names for a few purposes:
- Common language
- Identity or brand
- Relative reference
And sure, you can change something’s name without changing what it is, but you do end up changing how that thing is perceived.