Creating a Daily Standup Perspective With OmniFocus

2 minute read.

Like many of you in the software industry, every morning at 10am my team has a standup meeting. It’s meant to be a quick five minute meeting where everyone says what they accomplished yesterday, what they’re planning on doing today, and if anything is blocking them from moving forward. If done correctly, it’s a super-fast way to stay in the loop with everyone.

But sometimes it can be hard to remember all the details about what you did yesterday – especially on Mondays when you’re trying to remember past the weekend and back to last Friday. To help with this, I’ve traditionally kept a journal or work log of what I’m doing throughout my day. But with my recent job switch, I decided to start keeping all of that information in OmniFocus where I can slice and dice the data in ways that a plaintext journal won’t allow.

Because we use JIRA at work to track our tasks, rather than using OmniFocus the traditional way by entering my to-dos and then flagging what I need to get done to create a “Today” perspective, I get my marching orders directly from JIRA. So instead of entering my to-do’s into OmniFocus in advance of doing them, I add them as I complete them and immediately mark each as completed.

What this gives me is a dated and timestamped list of everything that I’ve accomplished. And with the “Standup” perspective that I’ve setup, I can simply flip to it in the mornings during our meeting and get an instant glance of what I accomplished yesterday and any tasks that happen to be waiting for me to complete.

To accomplish this, all of my work tasks are assigned to an OmniFocus project that corresponds to the real life project they belong to. For contexts, however, rather than giving them something like “Office” or “Laptop” or “Email”, they all get the same context simply titled “Work”. This allows me to group them together and sort by completion date in my custom perspective. Here’s what it looks like…

standup-perspective

As you can see, all the tasks I’ve completed are grouped by date – completed today, yesterday, this week, this month, etc. And then at the top is anything I’ve yet to do or might be currently working on.

This gives me a super easy way to provide my standup report each morning without having to remember everything myself.

Here’s a picture of the perspective settings I’m using to do this…

standup-perspective-details

I’m not using a project hierarchy, grouping by Completed, sorting by Project, showing Any Status, and All available items. I’ve also focused the sidebar selection to just my “Work” context.

By saving these settings as a custom perspective, it not only helps me out each morning, but also gives me a instant look at what I’ve accomplished or when something was completed if a boss or co-worker has a question.

A Stupid Idea?

2 minute read.

I have a stupid idea. Bear with me…

Apple’s new MacBook Pro is rumored to be updated later this year with the function keys replaced with a tappable OLED display. The idea being this display could change based on the app you’re using. But what if it wasn’t just the function keys. What if the whole keyboard was one big OLED touchable display?

When Steve Jobs stood on stage and announced the first iPhone in January 2007, before revealing the design, he showed a slide of “the usual suspects.” The standard smart phones at the time. He said the problem with theses phones (among other things) is the “bottom third.” He was referring to their fixed-in-plastic keyboards that are the same no matter what app you use. He said Apple “solved this problem thirty years ago with bitmap displays.”

Doesn’t that sound like an apt description of the standard laptop keyboard we’ve all grown accustomed to? What if it could change form whenever we switched apps?

Many people, myself included, are almost as fast at touch typing on a full-size, on screen, iPad keyboard as we are on a physical keyboard.

The travel of the keys on the new MacBook (One) has been drastically reduced to save space. Any further reduction and you’d practically be typing on a flat surface.

The new force touch trackpad in the MacBook (One) and recent MacBook Pros simulates the “click feel” by vibrating slightly.

What if the rumored MacBook Pro had a huge battery saving OLED screen for a keyboard that vibrated on key press? Would that be so bad?

Making Money Outside the Mac App Store

1 minute read.

One of the themes of this blog is how I make money selling my own Mac apps on my website rather than through the Mac App Store. I truly believe it’s the best way to go if you’re serious about earning a living. That said, not everyone has time to write their own backend sales platform like I did. For those who want to focus on development and make the actual sales process as painless as possible, I recommend using FastSpring. I’ve used them since 2009 and have never been disappointed. And getting up to speed with FastSpring couldn’t be easier than this great new book by Christian Tietze. It’s all about how to sell your apps outside the App Store. It covers everything from how to setup a storefront, to implementing serial numbers, and protecting your app against piracy. I’ve read the book, and it’s great.

If you do like the book and decide to buy, using this link will give me a small kickback. (But that hasn’t influenced my decision to post about it. The book really is good!)

image

Coding on My iPad Pro

2 minute read.

Last month, my 9-5 job was kind enough to gift me an iPad Pro and its new keyboard. I’ve had a few iPads in the past, but they’ve always ended up stashed away, unused, in a drawer somewhere. I simply never got hooked on their utility. I never found that killer app, which, for me, would be the ability to code anywhere. This Pro model, however, has changed all of that.

I’ve always had two Macs. One to take places and another to get “real work” done. In the past that meant a spec’d out iMac and an 11″ MacBook Air. More recently, it’s been a work-issued 15″ MacBook Pro that stays plugged into my cinema display 99% of the time and a MacBook (One) when I travel. The new MacBook is certainly the most portable Mac I’ve ever owned, but it’s slow and lacks the screen space to do any UI intensive work.

Now that I have an iPad Pro, I’ve sold my MacBook and only touch my MacBook Pro when I have serious work to do. The iPad has replaced nearly everything I use my laptop for. That may not be so unbelievable. Lots of folks like Viticci have moved to an iOS only way of life. As I do more and more tasks on my phone, I’ve been tempted to try going iOS primarily, but I could never make that jump because I code for a living.

Until now.

I was screen sharing from my iPad to another machine on my local network, when it dawned on me how great it could be if this particular Mac were always available to me – even from outside my house. So, I splurged and ordered a datacenter-hosted Mac Mini from MacStadium. Ten minutes later I was connected to my new Mac in the cloud. And ten minutes after that, I had Xcode open and started testing the waters.

I’m using Screens.app to connect. And with a good internet connection there’s virtually no lag when screen sharing with my new Mac Mini. I’m able to run a native Mac resolution of 1920×1200 on my iPad in full screen. That gives me plenty of room to run Xcode and the iOS Simulator. With Apple’s new external keyboard, all of my usual Xcode and OS X keyboard shortcuts work just fine. And since coding is primarily a keyboard driven activity, my arm doesn’t get tired from reaching out and touching the screen like a designer’s might.

All in all I’m thrilled with my new setup. It gives me the simplicity and benefits of iOS, while still allowing me to do real work outside of the house or from the couch.

ipad-pro-xcode

Wrapping up 2015

3 minute read.

Last year, I wrote about my final sales numbers for 2014. Now that 2015 is wrapping up, it’s time to do the same.

I had very high expectations going into 2015. I released Hobo right at the start of the new year and planned a major update to VirtualHostX for the Fall. With both of those in place, plus a renewed focus on my mailing list and website analytics, I set the seemingly impossible goal of doubling my 2014 sales this year. That meant my revenue goal for 2015 was $123,000. Audacious. Lofty. But that’s what I was aiming for.

How’d I do?

I’m sad to report that instead of doubling, sales cratered. With about two weeks to go in 2015, my current revenue sits at $35,000. Don’t get me wrong. I know there are many people out there who would love to be making that kind of money on their app business. And I’m very fortunate to earn what I do. But, still, instead of doubling my revenue I almost lost 50% year over year.

Why?

I can point to a number of reasons why 2015 was such a down year. Some were business decisions. Others were personal. Most obviously (to me) is that Hobo never really took off. Sales have been OK, but my goal of having it match VirtualHostX dollar-for-dollar seem to have been premature. I had a couple large quantity sales to businesses, which gives me hope that I could begin marketing Hobo in that direction rather than at individual developers. I positioned the commercially licensed version of the app as a boon to web dev shops with the ability to share and remotely update .hobo files. But, looking back, I haven’t made that feature prominent enough on the website. I need to do a better job at educating potential buyers.

I also never got around to properly setting up my Hobo mailing list with Drip. One of the changes I made in 2015 for VirtualHostX was requring an email address to download the software. This lets me follow up with the user after they download the app. I don’t consider it spam. I send three emails – each a day apart – that walk the new user through the major features of the app. And then if they haven’t purchased after two weeks, I follow up with a simple email asking if there’s anything the app could have done better or if they’d like more time to evaluate it. This email course has worked extrodinarily well and provided me with a lot of great feedback. I’ve had a to-do to setup the same sort of course for Hobo for nine months but never got around to it. And that’s squarely my fault.

Another major reasons for the low sales volume is I never got around to building and releasing the major update to VirtualHostX I’ve been planning. During the week of a major upgrade release, I can count on an additional $10,000 – $15,000 in sales via upgrades. Not having a major release this year definitely caused a significant dip in sales.

And here’s where things get personal.

Why didn’t I have a new, major release ready in time for El Captian in the Fall?

Two reasons. One, we had a new baby girl. And, believe it or not, taking care of two kids is way more work than dealing with just one. But, the main reason is the planning for my major Fall release typically happens early in the Summer. But during June and July of 2015, I found myself at the bottom of a deep depression. One like I hadn’t experienced since 2009. It’s hard to properly describe what it’s like being depressed, because at its core, you feel nothing. And that nothingness saps away every ounce of motivation you have. My relationships with my family and friends struggled, my app business saw virtually no attention for three months, and my nine-to-five job suffered as well. Two of those areas were forgiving. The other, not so much. But, I bounced backed, got on some better meds, and feel great now. The seventh major release of VirtualHostX is going well and should be ready this Winter.

So what did I do well this year?

I grew my mailing list considerably. That means when VirtualHostX 7.0 is ready to go, I should have a great audience to market it to. Further, earlier in the year I ran a bunch of A/B tests on my marketing website aimed at upping my conversion rate. I’m happy to report that I saw good growth in that regard – even with the change to requring email addresses to trial the app.

So that’s a summary of my year as far as business goes. I thought about listing all of the services I use and expenses I have running the business, but that hasn’t changed much since last year.

How’d you do?

Switching Email Providers

2 minute read.

Earlier this year I switched (after 11 years) away from Gmail to an email address at my own domain hosted by FastMail.

I didn’t make this decision lightly. I knew changing email addresses could uproot my very online identity. But I was tired of the new direction Gmail’s interface was heading, and I also worried about the horror stories you occasionally hear when Google accidentally closes or locks someone out of their account. Email is precious to me – especially the history it contains – and I didn’t want to chance losing it.

I’ve used FastMail with my freelance email address for years and always been extremely satisfied. So choosing them to replace Gmail was a no-brainer.

With that introduction out of the way, what I’d really like to talk about are the four steps I took to ensure a smooth transition to my new email address.

First, I used FastMail’s built-in IMAP importer tool to transfer over all eleven years worth of Gmail into my new account. The process took about six hours – they emailed me when it was complete.

Then, I setup a forwarding rule in Gmail to forward all mail to my new address and archive a copy in Gmail.

Next, I created a smart folder in 1Password that searched for my Gmail address as the login for any website. Over the next few weeks, I updated a few website from that list each day with my new email until they were all switched over.

Finally, I setup a rule in FastMail to file all email that was forwarded from Gmail to a specific folder. From there I can see all the remaining websites and mailing lists that have my old email address and update the ones I care about.

Changing email addresses isn’t easy. But it’s certainly doable with a little planning and some work after the fact.

Must, Will, Might

3 minute read.

Last month I came across a clever post about using just two GTD contexts by Matt Henderson (by way of SimplicityBliss). Like many of us, he’s experimented with lots of different ways of managing contexts. There’s the traditionalist approach where your contexts mimic the tools or location available to you: home, work, Mac, phone, etc. Then there’s Sven’s more modern approach based on energy level, which I’ve also advocated: brain dead, quick hits, full focus, etc. But Matt’s unique take is to simplify things even further into Will Do and Might Do.

It’s a fascinating idea because by getting rid of context groups such as work or personal (as I have mine setup) it implicitly acknowledges a modern-day truth we might not all be comfortable with. That being our work and personal tasks cross-pollenate and are often available simultaneously throughout the day. If you’re anything like me, you’re just a likely to pay the electric bill during a few minutes of downtime at work as you are to answer an email from your boss before bed. And with the majority of our work now available to us from nearly any device, the clean boundaries between traditional contexts break down. And as for those who used energy levels to define contexts, at least in my case, I would more often find myself scanning all of my available todos when looking for my next task, rather than taking the time to asses my current energy level and then switch to a perspective focusing on just that type.

When all those definitions fall away, what you’re essentially left with are tasks that you will do and tasks that you might do. Which is exactly where Matt’s Will Do and Might Do contexts come from.

I was so intrigued by this idea that I took the month of August to try the system for myself. However, I have made a few tweaks to the system he describes. I’m please to say that, a month later, this new system has worked well for me and I plan to continue with it. Here’s what I’m doing…

three-contexts

First of all, in addition to the Might Do and Will Do contexts, I’ve added Must Do. These three contexts impart a slight sense of priority and timeliness that I felt was missing. Tasks that fall into the Must Do context are items that simply must get done without delay. Typically, anything in this group is automatically added to my Today list. An example might be calling a repairman when the air conditioning breaks or paying my health insurance. Will Do contains tasks that I have committed to completing but that don’t have a firm deadline. Examples are “change air filters throughout house” or “install backup software on mom’s laptop”. None of these tasks are particularly urgent. They just simply need to get done at my convenience. Finally, I have my Might Do context, which is full of tasks that I would like to do some day but have not yet committed to. These are things like “schedule a cookout with Matthew when the weather is nice” or “investigate how to buy Google advertisements”.

In addition to those three contexts, I’ve left in place those that are location based errands. This means I still have contexts for the grocery store, pharmacy, and hardware store. I also have a context for any phone calls I need to make as I hate talking on the phone and would rather have all of those tasks together where I can just knock them out.

Finally, I still have waiting, on-hold contexts for tasks that I’ve delegated to other people.

This new context arrangement has really simplified how I think about my tasks. It’s made processing my inbox much faster, too. I’m no longer hemming and hawing about which particular energy level a todo falls under. I simply have to decide if it’s something I’m committed to or not. And, if I am, can I do it at my leisure or does it need to be done right away.

It’s always healthy to re-evaluate how your GTD system is setup, and I encourage you to give this three-context system a try. There’s nothing wrong with finding a more efficient way of working or a method that just makes better sense to you. Just don’t let toying with your todo app get in the way of actually getting stuff done.