Tag: Systems

Workplace Weakness

I’ve been thinking about personal weaknesses I have in the workplace – besides missing my regular posts for this blog…

Focus and persistence are two things I think I am weakest at. On a macro level, I have poor focus to stay on task. The consequence of poor focus means I either flit from project to project, or I self-sooth to avoid the pain of friction (typically by going on YouTube).

Poor day-to-day focus leads to poor persistence, which means I don’t carry things to completion. I stick in the ideas or early implementation phase. I chase the next shiny distraction. This would be somewhat remediated through better habits and intentional prioritization of my tasks and time. It would also be partially addressed through better task management, where everything is organized and resurfaced at the times I need them.

Solutions:

Focus
– short work sprints (pomodoros)
-discrete tasks (break projects into small, well-defined, finite steps)
-block out the world (headphones and white noise)
-block out distractions (website blockers)

Persistence
-organized task management system
-calendar blocking
-show up each day with focus habits (see above)
-project and tasks planning
-recognize that progress is made in small steps

Stay Awesome,

Ryan

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

Slipped Time

Sorry for the lack of posts these last two weeks. I have lots of reasons (the holiday Monday, work has been keeping me busy, feeling tired from childcare, and our family being sick the last week), but those are poor excuses for not carving out some dedicated time to put thoughts to screen. I have been doing a decent job of holding myself accountible with work, but knowingly allowing two weeks to go by unplanned without posts shows that my systems still have some issues with keeping me on top of everything.

I appreciate the grace you have offered in my absence.

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

WFH: Struggles in Focus

In March, I will have been working from home (WFH) for a full year. You’d think that with my experience being employed pre-pandemic, I’d know how to manage my time and motivate myself. But, I have to be honest that working from home has had its challenges. Every time I think I’ve got it figured out, I somehow end up reverting back to a less productive mode of work.

You’d also think that after working from home for a year that I’d have a handle on the situation, yet there, too, I’m finding it difficult. I could attribute it to having a child and the challenges that come with that level of life adjustment, but I feel that would be a disingenuous excuse for my poor integrity.

I know I’m not alone; many people are feeling this. In the beginning, the articles were about learning to draw boundaries in work/life balance. Then came the articles urging us to dress for the office, trying to capture the liminality inherent in a structured schedule. Then came the posts lamenting the late nights with alcohol and doom-scrolling. We all are feeling the anxiety of trying to remain in the present while our focus is pulled towards thoughts about a dimly lit uncertain future.

The best I can do is continue to experiment and see what sticks for me. At the moment I’m trying to be more intentional with my work calendar. I set up to three priorities for the week, block off time in my calendar to work, and spend the first moments at the beginning and the last moments at the end of the day to plan, reflect, plan, and review.

One thing I’m enjoying with this approach is that I’m having an ongoing dialogue with myself in my work calendar. At a high level, I’m leaving a paper-trail of my thoughts, and with that trail I can autopsy where I’m successful and why I fail. But in the day-to-day moments, voices from the past come to help my present understand itself, then I leave little notes for the future to pick things up after rest.

I’ll keep practicing this approach and write some comments in the future, if it sticks.

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