hide

Read Next

Day Twelve and Thirteen -- Metrics Are A Blessing And A Curse

Here was the plan for Day 12. If you remember, I was wrecked a few days earlier and looking to re-track --

Plan for tomorrow…

Over the next 3 days, need, *Sales *Philanthropy *Writing

Tomorrow… *Morning, a couple errands (power, etc) *Afternoon, take a quick crack at writing *Go to gym *Clean up *Meet Stepan, goals, etc. *Sleep early enough, tomorrow doesn't have to be crazy -- more important to just be on track

Here's what happened -

Micropriorities

On Tynan

I've talked a lot before about priorities in a macro sense-- that it's a good idea to have one large overriding first priority. In my case, that priority is SETT. So when another really exciting project comes across my desk, I can easily turn it down and just focus on SETT. On a daily basis, though, SETT isn't actually my top momentary priority at all times. If it was, I wouldn't ever eat or sleep, because working on SETT would be more important.

One of the keys to high efficiency (which translates directly to high productivity) is knowing what you're doing next. The biggest indicator on whether or not I'll have a productive day is whether or not I know exactly what I should be working on. When there's one big fix that needs to be created or one big feature that needs to be built, I have no problem putting in a 12-14 hour day. On the other hand, when I have ten low priority things I could work on, I tend to get much less done.

These deliberations happen outside of SETT, too. If I have a good block of SETT work to do, should I skip my daily blog post? What if a friend invites me to tea?

Without a clear hierarchy of priorities, it's easy to succumb to decision paralysis. I might start a paragraph of a blog post, but then when it's not coming together well, go answer some emails. To combat this, I decided to take the time and write out my micropriorities. Here they are with notes:

Rendering New Theme...