Forced System Growth

It’s been a busy few weeks between work and a sick kiddo at home. Sorry for missing the last two posts.

The changes I’ve recently experienced at work has inspired some thinking on this post’s topic. While I typically have a good mind for keeping track of projects (with some liberal use of a notebook), the updates to my job and the sheer scope of accrediting an engineering degree has proven to be more than my current organizational and productivity systems are capable of managing. Tasks were rapidly multiplying and open-loops weren’t being migrated for tracking; there was no translation between meeting notes and what was getting scheduled into my calendar.

I functionally hit a crossroad. One path was to keep trying to do the same thing and fall further behind, and the other was to force a systems growth to accommodate my new workload. What got me here won’t get me there, if you will. Put another way, my outputs were optimized to how I managed my workload, so if I wanted to change or improve my output, I would have to change the system. Changes in work forced the system to grow.

On one level, I want to deny this – why do I have to constantly adapt the system to new work? Can’t I find one universally applicable approach to managing my workload? Sadly, no. This is the pipedream sold by productivity wizards who claim their one system will take care of everything. The reality is that those systems are often tweaked to meet the unique cognitive needs of the person. If you want to use those prescribed systems (GTD, Building a Second Brain, etc), you will need to adapt it to how your mind processes information. And it makes sense that as you grow in your career, you will need to grow the systems that you use to keep on top of things.

Most of my systems have developed “organically.” I would implement new features on an ad hoc basis in response to specific needs. This is one of the first times that I’ve had to make large changes by first thinking through what I needed and how I wanted things to play out. As weird as it is, it reminds me of Stephen Covey and seems to combine two of his principles – begin with the end in mind, and sharpen your axe. By knowing where you want to go, and by spending a lot of front-loaded work setting things up, you have a better chance of dealing with bumps as you go.

Stay Awesome,

Ryan

Getting the Need for GTD

I seemed to have hit an inflection point in my job recently that I’ve been struggling to overcome. While my work has had multiple buckets of concern, I’ve been able to managing things fairly well using my memory and jotting notes and to-do’s in my notebook. However with moving into a position that requires managing complex, long-term, and poorly-defined processes, I’ve been increasingly finding it difficult to keep everything straight in my mind. My tasks aren’t are clearly defined, and I’m required to be more independent in how I manage both my own personal workflow and the various areas under my responsibility.

Simply maintaining a to-do list doesn’t seem to cut it anymore. There is too much to keep track of, too many legacy pieces of information that has accumulated over time, and the pace at which things are added or change is steadily increasing in velocity. Add to this the need to keep on top of things in our personal life at home, volunteer work, and activities that I find gratifying, and I’m feeling slightly paralyzed in knowing what I should fix my attention to.

In an effort to get a handle on things, I’ve picked up David Allen’s Getting Things Done. It’s the first time in a while where it feels like the text is speaking to me. I went into the book a little leery of going after yet another gimmick or shiny new toy. GTD is a seminal system in the productivity space, and so it sometimes carries with it some baggage from some of the more problematic areas of the space. Yet, I’ve found it helpful so far in thinking through my problems. At its core, my problem is in two areas: the meaningful transformation of input, and in execution.

I suppose GTD will eventually help me with the latter (I don’t know – I haven’t finished the book yet as of writing), but it’s been incredibly insightful in tackling the former. I tend to take notes and capture to-do items all over the place. However, what I’ve been lacking is examining each of these pieces of input and doing something with it; processing them into their buckets. The list has grown so large and unwieldy that I am having trouble finding stuff when I need it. I have tried popping items into information systems like Notion, Trello, or using tags to help me find it later, but most of these systems have lacked the context to help make the inputs useful later. Instead, they sit in whatever capture system was used to grab them at the time – physical notebook, email inboxes, Trello, tags in OneNote, calendars, or tasks in Teams.

I’ve found GTD helpful in suggesting organizational structures and parse out what will be meaningful later and what can be archived out of mind. I’m still working through developing a system, but so far embracing ideas from GTD has helped keep things more readily at the top of my mind, which has translated into less general anxiety as I go through the work day.

Stay Awesome,

Ryan

Falling Through My Systems

This late post is a nice springboard into something I’ve been thinking about throughout the pandemic. Pre-pandemic, when I was still commuting to work, I had a fair number of systems to help me get stuff done. My commute to work helped me film daily vlogs, listen to books, and think about big ideas for blog posts and Stay Awesome vlogs. When we started working from home, those outputs began fading. Now, I feel behind on my blog posts, I *maybe* film a personal vlog once every two weeks, and Stay Awesome has been put on an indefinite hiatus until Jim and I get some extra headspace bandwidth to devote attention to it.

I was also known for my notebook. I carried a Field Notes notebook everywhere with me, and was constantly scribbling notes into it. Then, around 4 months into working from home, I found myself abandoning the monthly notebook and appropriating a disused larger notebook to jot down tasks, lists, and random thoughts. The Field Notes book was small, portable, convenient, and had many systems to track things I found important, such as exercise, health, habits, etc. Now, my notebook is largely devoted to task management, because when every day feels the same, you can quickly find yourself several weeks down the line having nothing to show for your time.

In a sense, I’ve fallen through my systems. The various “systems” I implemented succumbed to inertia when I both lost the cues that triggered them and lost the will to keep putting effort in the system to power the flywheel, and friction has ground them to a halt.

James Clear has a pithy phrase, that “you do not rise to the level of your goals. You fall to the level of your systems.” This is a riff on an older Greek observation from Archilochus: “We don’t rise to the level of our expectations, we fall to the level of our training.”

Regardless, the question I have is whether I truly had a system if it was a fair-weather operation that wasn’t robust enough to adapt to these kinds of radical changes. When I lost the external liminal cues that came from commuting to work, or from even leaving the house on a regular basis, the things I called systems disappeared as well. Is it charitable to call these things “systems”? In virtue ethics, you aren’t said to possess a virtue if you only exercise it some of the time – you aren’t considered courageous if you don’t act courageously in a moment that requires it. Does this apply to systems as well?

Part of me says yes, but that’s not very helpful. Perhaps I should reframe my thinking and consider the quality and attributes of the system. Borrowing from Taleb, some systems are fragile, some are robust, and I suppose some are antifragile. I understand antifragile systems in the context of biology (e.g. stressing muscles can allow them to get stronger over time), though as of writing I can’t think of any productivity system that get stronger under pressure.

Regardless, it’s clear that much of my productivity was built upon what can now be labelled as fragile systems. They worked under certain conditions, but outside of that narrower band they are less able to withstand fluctuations or variance. In my reflections over the last few months, I’ve been seeing the value in understanding the causes of system failures so that I can create new processes to help me in work and life. For now, the first step is to acknowledge that I’ve fallen through my systems, and having acknowledged this, I can stop spinning my wheels and start seeking traction.

Stay Awesome,

Ryan

Reflection – A Systems Review of Results

I’ve been mulling over a quote I wrote down in my notebook back in March, especially as it relates to my productive output at both work and for my personal projects:

“Every system is perfectly designed to get the results it gets.”
~Paul Batalden

At the end of the day, I’ll look back at my lists of tasks and feel frustrated that another day has slipped by thanks to my monkey brain’s inability to focus. Of course, this is placing the blame on the wrong focus because it’s ignoring two important facts: it assumes I’m not in control of my behaviours when I blame it on my “monkey brain,” and it assumes that I’m setting myself up for success merely by sitting at my computer. Both of these are patently untrue. I have control over my environment and (to borrow a phrase from Jocko Willink) I should be taking extreme ownership over my work situation.

If I find myself frustrated with my lack of output, I have to look at the system that my productivity is set against. If I spend my day getting lost down YouTube video and blog holes, then it’s because my system is optimized for it.

If I’m allowing myself to give in to temptation or distraction, it’s because it’s easier to fall back on things that are psychologically comforting and there is too much friction to get started on the real work.

Motivation is a flywheel – I have to overcome inertia to get the wheel turning, and it takes time before inertia helps the wheel turn freely. If the system is optimized to prevent me turning the flywheel, then it’s important to look at the system for fixes, rather than bemoaning the outcomes.

It’s not a quick fix. It will take time, effort, and a direction to push towards that will start the flywheel. I shouldn’t be so hard on myself. If the flywheel grounds to a halt, then it’s my job to stop, reset, appraise, and re-engage.

Stay Awesome,

Ryan

Productivity From Home

Note – not my workspace.
Photo by Anna Auza on Unsplash

It’s taken me six weeks, but I think I’ve finally found a good system for working from home. Like many people who are fortunate to work from home during the pandemic, I’ve been struggling with keeping my normal routines while working from my computer at home. I won’t pretend that I had a perfectly productive system when I used to commute to the office everyday, but where I had the illusion of being productive simply by being at work and conversing with my colleagues, at home I am totally cut off from those signifiers of “work.” In the last few weeks, I’ve had spurts of productive time, but those were relatively few in number.

Late last week, however, I found a good combination that allowed me to really focus on moving my tasks along. I’ll share some of the tools that have been working for me.

First, using headphones to play noise while I work helps me make the mental shift in context from “home” to “work”. I have two sets of headphones at home, and both work well – a wired set of Sony headphones with noise canceling function, as well as a set of Philips Bluetooth headphones that also cancel noise actively.

I don’t just listen to music, however. I find most music to be distracting to my workflow – even lyric-less songs. My mind tends to pick up on the melody, and I’ll focus on that instead of the task at hand. I have two sources of noise I currently use – a pomodoro Chrome extension that plays fuzzy white noise (and conveniently tracks my pomodoro sessions), as well as a pomodoro video on YouTube that includes a visual timer and ticking clock. The white noise blocks out ambient noises that otherwise gets through my headphone’s noise canceling feature, and the ticking noise helps me focus.

Speaking of pomodoros, I use the pomodoro method to break down the tasks into manageable chunks. It also has the benefit of bypassing my motivation drive. Rather than committing to working an 8-hour work day, I commit to the next 25-minute block of work.

I have a lot of projects and tasks to keep track of, so I use two systems to prioritize and track my work. For long term, multi-step tasks, I have set up a dedicated board on Trello to manage where each project is in the pipeline. I have created buckets that I can move tasks through, from the general pool of tasks, to the planning phase, into an active phase, and if the project is put on hold, I can take notes on what I need to do to push things along while the task is in limbo.

For day to day task planning, I went simple and set up a text file that I number tasks as I think of them for the day, then I keep track of what I accomplish each day in a growing list. I usually would do this in my notebook, but I liked being able to cleanly re-order tasks. On paper, you can only order tasks in the initial stack you wrote them in, but if something changes during the day (e.g. a meeting gets scheduled on short notice), it’s harder to move things around.

Aside from the Microsoft Office tools provided by my employer (Outlook, Teams, Sharepoint, and OneNote), that covers my current workflow. Depending on how long the stay-home order is in place, I might update how this system evolves. It’ll also be interesting to see what of this system I port back with me to the office (I have a feeling I might bring the headphones to help me focus).

If you have any systems or tools you like, I’m curious to hear about it in the comment section.

Stay Safe and Awesome,

Ryan