"Total Focus; Total Enjoyment" by Tynan

I'm thrilled that Tynan is coming to you with two things -- first, he's offering a breakthrough session through GiveGetWin. It's geared around doing more of the kind of excellent work you want to do, becoming more internally focused with your emotions, having a more enjoyable life, building great habits, and producing a lot of value in the process. There's five spots, so check it out now.

Second, we have this wonderful tour-de-force interview: it starts by covering how Tynan made the shift from unfocused to focused, how to derive internal enjoyment from things, useful actionable exercises you can do right now, Tynan's method and mindset for producing creative work consistently, how to set up great habits and an excellent mental and physical work environment, and how to make blogging work and similar endeavors work for you. 

Total Focus; Total Enjoyment by Tynan, as told to Sebastian Marshall

When I turned 30 and I had a minor freak out… I thought, "I'll be 40 in not long, and then 50… there's things I want to do in my life, and they're not happening at this pace."

Before that, I had a general idea of things I wanted to do and have in my life, but I went about in an unstructured way. It was good in a lot of ways. It made be a broad process, but not much depth.

Micropriorities

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.