We’re a week into July now and my decision to write some personal objectives for the quarter to go alongside my work objectives is proving to be an interesting experiment. I’ve begun to try and build some new habits to help me achieve not just my personal objectives but also my work ones.

The first of those habits has been to set aside the first 30 minutes of my work day to read and write. After I sit down at my desk with a coffee, I check in on Teams and my email to make sure there’s no fires, and then pick up my book. I open Obsidian to the literature note for that book, pick up my pencil and begin to read. As I go I underline anything that stands out, and then when I finish a section I write a note in my own words that covers those underlines. It’s fast becoming one of my favourite parts of my work day and I’m noticing an interesting side effect. When my time is up and I move on to some design work, I’m more productive and able to more easily focus on what I’m working on.

I’m pleased that I’m starting to build this habit and the influence it is having on my working day. My next small target is to keep some momentum now that I have finished reading the first book of this new habit. I have the next book lined up ready.

A year or so ago I moved my blog from Wordpress to Jekyll, going from a CMS powered website to a static site generator. The idea behind it was to make designing and building the site easier from my iPad, and in the hope it would give me a push to post more often.

It didn’t work.

So I find my self making another move and switching to Ghost to give that a try. It works with Ulysses which is my text editor of choice and an app I have installed on all my devices. Posting should be a lot easier now, but I’m unsure whether that will really make much of a difference. As I write this post, the question I keep finding myself returning to is why am I not blogging more?

Is it because I don’t want to? I don’t think so. I always have it nagging at the back of my mind that I want to write and post more. Is it that I don’t know what to write? That’s probably got something to do with it. Is it that I get hung up on it being my personal site and I want the design just right? That also likely is a cause. All of those are things that I can change, finding the way to change them is the key.

The first step I’ve made is to write myself some objectives. It’s that time of the year at work where we are moving to a new performance year. Part of the process involves me writing some objectives, this year I’m trying to use the OKR methodology to give myself some clear objectives and measures. I’ve decided to also write some personal OKRs for this quarter. We’ll see if they have an impact, but this post is the result of one of them, and we’ll see if I can keep going.

Over the last few months I’ve come across a number of personal blogs which have been inspiring me and fuelling my own desire to blog more. One of those is from Arun Venkatesan. His most recent post about his writing process is fascinating and worth a read. I like how each of his posts is seen as a creative exercise about something he is interested in. It’s more of a slow blogging process than the stream of links and sharing that’s became popular in the mid 00’s and has lasted until now.

Chris Hannah with an interesting post about writing at work. I go through phases at work where I will write a lot to help me clarify projects and make sure the problems we are trying to solve are clearly defined. Chris highlights a few other reasons he writes at work, with this one in particular standing out:

Gives the opportunity for more people to gain knowledge - Sometimes when you’re on a call or in a meeting, knowledge stays within small groups of people. But by having a written record, it allows more people (if shared appropriately) to also read it. For example, maybe a new employee wanting to know more about a piece of work/functionality, or someone on the same team that wishes to gain a better perspective of a bigger piece of work.

Sharing of knowledge is crucial in the workplace, especially in the world of hybrid and remote working. Conversations happen in private chats or small video calls and not always everyone who needs to be there is present. Some food for thought.

Chris Hannah with an interesting post about writing at work. I go through phases at work where I will write a lot to help me clarify projects and make sure the problems we are trying to solve are clearly defined. Chris highlights a few other reasons he writes at work, with this one in particular standing out:

Gives the opportunity for more people to gain knowledge - Sometimes when you’re on a call or in a meeting, knowledge stays within small groups of people. But by having a written record, it allows more people (if shared appropriately) to also read it. For example, maybe a new employee wanting to know more about a piece of work/functionality, or someone on the same team that wishes to gain a better perspective of a bigger piece of work.

Sharing of knowledge is crucial in the workplace, especially in the world of hybrid and remote working. Conversations happen in private chats or small video calls and not always everyone who needs to be there is present. Some food for thought.

This post was written when this blog was based on Jekyll before I moved back to WordPress. I have kept it as part of the history of this blog.

When I moved the blog to Jekyll last year I made several decisions about the posts I would bring across. One of those was to drop several of the post types that I’d added over the years leaving only a normal blog post as the type of content I could post. I hoped that by stripping out all the cruft I would be able to focus more on my own writing and build up more of a routine to posting. Inevitably that hasn’t panned out. There have been times where I’ve posted regularly, but just as I felt like I was getting into some kind of pattern things would happen and I wouldn’t post.

Of course one thing that has never changed was that I still read articles. In fact this year I’ve focused more on RSS as a means of reading and as a result I’m reading far more than I used too. I’ve also adopted Good Links as my read later app of choice and am developing a reading work flow to help me process what I’m reading. Part of that process involves sharing what I read. So for the same reason I added the ability to share links on my blog many years ago I’ve added that ability to this one. It’s in a state I call earliest usable product like much of this blog is, but I intend to keep improving things continuously over the next few weeks.

Life is about tradeoffs. When we know what to say no to, and we know why, we can say yes with comfort and confidence to the things that matter. To the things that last.

In conversation with one of my favourite authors Austin Kleon, Ryan Holiday finished a post with this quote. They were discussing the choices between work, family, and scene, but I the sentence above can be applied to a lot of things.

Today, the third Monday of January, is commonly referred to as Blue Monday. It’s considered to be the most depressing day of the year. By this time people are feeling down because they have broken all their New Year’s resolutions and there’s still another week until pay day.

Day’s like this that receive a lot of coverage in the press can be both damaging and helpful to mental health awareness. They can harm mental health awareness by giving the impression that depression or other illnesses only happen on particular days, but they can be helpful by bringing conversations up with people. They can be helpful to highlight that every day can be a Blue Monday, it is not confined to a single Monday in January. Instead it can strike on any day, at any time. My Blue Monday’s have been on a Friday in December, a Monday in August, and a Tuesday in January. Each on years or months apart. What’s important to know is that they are all survivable.

If you are struggling with your own Blue Monday you’re not alone. People are there to help you, be they family, friends, or healthcare professionals. They all care about you. Don’t suffer in silence.

Part of my approach to the new year involved rediscovering one of my habits. I’ve been trying to write a blog post more often. I initially intended to use my Micro.blog and to post all my content there, but given the chance to reflect I realised I wanted my longer posts to live here. I’m not committing to a set number of posts per week, but I am committing to posting here more often.

All week I’ve been thinking about what to write about. Everytime I opened my iPad and sat down to write something I couldn’t think of anything to write. It started to become a problem. I wanted to write a post, but I didn’t know what to write. I wanted to write a post but I began to feel like I didn’t have anything to say. I wanted to write but I began to believe I didn’t have anything to say or write.

This is evening as I sat here recovering from my counselling session I was bumbling around on the internet. Something made me google a photographer whose blog I used to follow years ago. I even have one of his photos. To my delight I found his website and realised he was still blogging regularly. As I scrolled through his posts I came across one titled Stop hiding behind complexity. The first line struck me:

Whether we like to admit it or not, we sometimes enjoy making the simplest task more difficult because it's easier to blame the many loops it would have taken to finish it if we don't succeed.

I realised perhaps this is what I’m doing with my blog. I want to write a post but I think that I need to write something significant. Instead of sitting down to write something, be it about something I’ve read or done this week, I’m making the simple task complicated. The likelihood is that it’s easier to not post something and hide behind the thought that I have nothing to say than it is to open Obsidian and write until I’ve put something together worth posting. If I want to write for my blog more often, it should be as simple as writing a post and publishing it. No second guessing myself and no worrying about whether I have something to say. Just writing.

Over the years I’ve developed a few strategies to help get me in to the right frame of mind to work. One of the best ones is my time for work playlist, I put it on when I need to focus and it never fails to get me into the right state to focus on a project. I’ve worked out that the best albums for me to work to are film soundtracks. The nature of films means that they often build to a finale towards the end of the film, and the soundtracks have a big part to play in that. I find that as the urgency in the music builds my focus deepens and by the end of the soundtrack I’m immersed in my work.

Occasionally I’ll come across a new album that has a similar effect to the play list and I add it on the end. This week when I came across a new album I realised that it might be time to review the albums that I have in there. When I opened it up I had amassed over 6 hours worth of music. I realised it was time to review what albums I had saved, along with the fact that I rarely even got to the soundtracks at towards the end of the playlist.

Most of the time when I used this playlist it was to settle down to a block of work, generally in the afternoons when I have fewer meetings at work. That means a block of work a can last between 1 and 3 hours, so I really had no need for the amount of music that was in there. On a Wednesday afternoon work has implemented a no meetings policy, it means we have a consistent free block of time we can set aside for deep work, and my playlist gets used a lot on those afternoons.

When I assessed the albums that I had in there, I decided it was time to limit the length to about 3.5 hours of music. I picked my top 2 soundtracks and added in the new one to hit the magic length of time. I structured the playlist with the longest first moving to the shortest last. We travel through Dune, Tron Legacy, and The Dark Knight, which nicely breaks my work period into three chunks should I need to pause for a few minutes and move my legs. I’ve been using it this week and it’s working very well. If you’re interested here’s the Apple Music version for you.