Category: Goals

Identifying Areas of Growth

I had my latest performance appraisal last week. I found I had a much easier time identifying areas of growth this time over last year after having gone through an accreditation visit for one of our programs. In the past, I would look at my current skillset, look at the friction points I was experiencing, and project forward a better future based on picking up some new skills or experience. This process is fine, but I realize the flaw is that the path you choose to develop in is not based on experience. It’s a guess about what might be helpful.

Contrast this to going through the accreditation process. To prepare for the performance appraisal, I reviewed the last year’s worth of information (my calendar, my one-on-one meeting notes, and notes I’ve taken about my job) and saw patterns of missed opportunities and under-performance. In these areas, I can reflect and see how if I had more skills or experience in these particular areas, I would have had a better time navigating the issues we faced.

Based on this backwards reflection (rather than guessing or projecting forward), I could more clearly articulate what I’m weak in and where I would gain the highest value in focusing on.

I think this marks for me the formal transition from the “start of career” phase to a more mature “middle career phase.” I have enough work experience and self-knowledge to draw meaningfully from, and that allows me to make smarter choices moving forward.

Stay Awesome,

Ryan

Long Absences

You never intend to step away for very long. A week goes by, then another. Without realizing it, a month has passed.

It can sometimes be hard to keep up a weekly blog. I don’t know how the daily folks do it – Seth Godin says it’s just consistency, but does that mean it’s easier to show up everyday than once per week? Maybe… It’s harder to push off to tomorrow when the deadline is always midnight. I’m not impressed by the folks whose job is to churn out multiple pieces of content per day. Creative burnout aside, there is a difference between being paid for the content and doing it without pay.

Excuses are easy, especially when they are real. Yes, I didn’t set time aside to write, but I also had a major deliverable due at work. I even set up auto-responders on my emails to manage people’s expectations while I was in focus mode. These are reasons, but they do not excuse the absence when you know what you are getting yourself in to.

And when you return to the notion of an update, you feel the need to write something profound to offset the time away, but the ideas feel crusted and not worth sharing. Instead, you hide away, and figure you’ll get back to it next week, meanwhile the feeling of panic and dread increases at the thought of delivering that perfect post.

But next week comes and goes.

There is no magic solution beyond showing yourself compassion, resetting the clock or counter, and shipping the next thing by trying again.

Stay Awesome,

Ryan

Advice from Col. Chris Hadfield’s Keynote

At my college, there is a yearly multi-day event for employees to deliver PD workshops to each others to teach skills and share experiences. The college invites thought-leaders to delivery keynote addresses to kick-off and close-out the event.

This year, the closing address was delivered by Canadian astronaut Col. Chris Hadfield. After his inspiring talk, he fielded a few questions. I was one of the lucky ones whose question was posed to him. Here is a summary of his key lessons to my question:

“How do you and fellow astronauts handle coming back to Earth? That is, the depression that comes after the high of achieving your goal/mission. “I just did that… now what?””

  • There is a misperception about going to space. It’s not just a random good thing that happens to you out of the blue – the mission has been an endeavor that is decades in the making (26-years for him from the time he decided to become an astronaut to his first mission). Even if he wasn’t chosen to go to space, he still enjoyed his job. Going to space afforded him unique experiences that honed his skills. He was gathering experiences and capabilities, then after coming back from space he could take those skills to support others and apply them in other areas of his life. He sees it as a tremendous set of gifts, tools, and new abilities to tackle the rest of his life. If you try to measure your life by one or two shiny peaks, then by definition you’ll make your life dismal. (As a side note, I read his book “An Astronaut’s Guide To Life on Earth” after his speech, and in it he goes into greater detail of what happens to astronauts after they come back. The experience doesn’t end; the job of being an astronaut has succession plans built into it that keeps astronauts useful. They spend months debriefing the mission to identify best practices that will keep future astronauts safe. They help train others, and handle mission control duties. They also help support the families of other astronauts when their loved ones are away on mission. The impression I got is that the job is designed to be a.) in service of others, and b.) purpose-driven).
  • Don’t spend a lot of time looking backwards. “If you spend a lot of your life looking backwards, you’re going to bump into your future. That’s not where things are coming from; they’re not coming from the past.”
  • The most important decision you’ll ever make is “What am I going to do next?” Some of your opportunities and skills will diminish as you age, but that doesn’t mean it can’t be vital, important, interesting, or challenging to you.
  • There are cool things happening to you everyday. Allow yourself to succeed everyday, it doesn’t have to matter to anyone else. Celebrate it. Recognize that yeah, there is crappy stuff happening, but there are cool things happening to you too, so try and choose to focus on them. There are compulsory things you have to do, but like in figure skating there are freestyle points. Try to revel in the freestyle. That leads to a life well-lived.

I’m so glad I got a chance to hear him speak and that my question was selected for response. I devoured his book and dropped many bookmarks in to return to so that I can absorb his experiences. It really drove home the problem with many self-help books that are released today – the books are written by people who are telling the stories of others. The purpose of the book (aside from sales) is to collect stories from the deeds of others in order to fit a narrative or thesis. There is an assumption that because someone else made things work that the author has the borrowed authority to provide advice to others.

I’ve learned that it’s much more instructive to turn to the primary sources and read the undiluted message from those who’ve actually been “in the arena.”

Stay Awesome,

Ryan

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

Optimizing, Values, and the Right Answer

Engineers love clear problems with delineated right and wrong answers. Data, especially quantified data they think, is objective and clean. Without painting too strong of a stereotype, they don’t like to muck around with soft skills, or social/political factors in problems. They like to keep engineering pure.

The problem with this view is that it’s not correct – it makes an underlying assumption about what makes something a right or wrong answer to a problem. Most problems that engineers deal with when designing a solution are not value neutral. When we think of problems with clear right or wrong answers, we think of problems that are purely mathematical or having discrete binary solutions (e.g. “will the object handle the forces that it will be subjected to under normal conditions?”). The secret is that all problems have “right” and “wrong” solutions based on the underlying values you are trying to optimize for.

An engineering problem that is optimizing for maximizing return on investment might have different solutions than one that optimizes for addressing systemic inequity for particular people. The tradeoffs are not just opportunity costs, but instead are tradeoffs on which values inform the vision of the final outcome of your solution. When you seek to return on investment, to maximize profit, the answers are pretty clear – drive down expenses, raise prices as high as the market will bear, communicate the value proposition to the customer, and produce enough goods at the right rate to meet demand without excess goods sitting idle. When you seek to address systemic inequity, your solutions will have decidedly different considerations – your expenses will go up as you pay fair wages, prices might not maximize your margins, you will be more candid with your customers, and your manufacturing and distribution will be likely slower and more intentional as you make ethical considerations in your processes. You will also consider all sorts of other externalities that pop up as a result of your solutions, boosting the positives while capping the downsides.

This is not to say that all solutions will be equally easy to implement under any one set of values systems that you choose. However, it’s fallacious to believe that the same answer will always be given for “can we build this?” and “should we build this?” if you aren’t also examining the underlying values that you set in your assumptions.

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

Cross-Domain Knowledge

I’m a huge fan of cross-domain knowledge. Coming from an academic background in philosophy, I feel my greatest strategy for creating and building a career is leaning in hard to knowledge and skills that are learned in one domain or context, then applying it to a unique area. You get a large confidence boost when you make connections by spotting patterns and connections that map analogical cases to each other.

The first time I truly appreciated this was in my days working for the university gambling lab. We were collecting data on slot machine players by recruiting participants into our study to measure the effects properties of the machine user-interface had in gambler’s cognitive awareness. In other words, did how the graphics and sounds play on the screen help the gambler understand their relative wins and losses over time. In one study, the simulation we were using for participants to play on during the trial had been modified, but on some of the laptops the wrong version of the software was copied over, and we didn’t realize the mistake until the end of the day. Of the three laptops, two had the right software, and one did not. At the end of each session, we uploaded the user data to a secure repository and deleted the local files, which meant that once we were back in the lab, there was no way of knowing which participant file batch came from the defective software.

We thankfully caught the issue early and limited the damage, but afterwards we had an issue with figuring out which files to exclude from analysis. On the face of it, there was no way of knowing from the participant’s biometric data which simulation they used. So instead we had to dig into the debug files that were spit out by the machine to verify that the simulation ran successfully.

All the files were generated in an XML format, however I had neither experience in basic coding nor reading XML files. I had to figure out a way of showing whether the version of the software was correct. To me, the XML files were largely gibberish.

But, I was able to spot a pattern in the files that reminded me of my formal logic courses from undergrad. While I did poorly in the courses at the time, I did retain some of the strategies taught for understanding the structuring of the syntax of formal logic arguments, specifically how nested arguments worked and how assumptions were communicated. I started to see the same structure in the XML code, how sub- and sub-sub arguments were written to call different files into the program, and where those files were being drawn from.

And there it was. At the bottom of one of the debug files, was a list of the files being called on by the simulation. In the broken simulation, the file path to a certain sound that was meant to be played was empty, meaning that when the simulation was supposed to play and auditory cue, there was no file name to look for, and so the simulation moved on.

I compared this with the files we knew came from the working simulators and saw that this was the main difference, giving us the key for finding the bad data points and justifiably excluding them from the overall data set. By finding this, I saved an entire day’s worth of data files (a cost savings that includes the some-30 participant files, their remuneration, three research assistant wages, per diem costs, travel, and consumable materials on site).

I grant that computer programming is entirely built on the foundations of formal logic and mathematics, so it’s not that I was gaining a unique insight into the problem by bringing knowledge from one separate domain into another. However, this was one of the first times I encountered a problem where I lacked the traditional knowledge and skill to address it, so I came at the problem from another angle. It was a case where I gained confidence in myself to be resourceful and tap into previous learning to address new/novel problems.

As I noted above, being trained in academic philosophy has pushed me in this direction of career development. On a superficial level, relying on cross-domain knowledge is a career survival strategy because philosophy doesn’t always teach you skills that are easily applicable to the working world. I have sadly, never once, had to use my understanding of Plato’s arguments in my workplace. But on a deeper level, I think training in philosophy naturally pushes you into this kind of problem-solving. Most of my experiences in philosophy involves approaching a thought experiment or line of thinking, considering what it’s trying to tell us, then testing those arguments against counter-factuals and alternative arguments or explanations. To do this well, you have to reduce a problem down into its constitutive parts to tease out relevant intuitions, then test them out, often by porting those intuitions from one context into another to see if they still hold as both valid and sound.

It’s not all that dissimilar to the processes used by engineers or designers to gather data and accurately define the problem they are intending to design for. Whereas the engineer will apply the tools they’ve been taught fairly linearly to create a design for the problem, my strategy is to adopt cross-domain knowledge to make connections where they might previously had not been apparent. The results can often be solved quicker or more efficiently if I had the relevant domain knowledge (e.g. an understanding of coding), however when I lack the specific experience to address the problem, as a generalist thinker I have to rely on analogical thinking and a wider exposure to ideas to suss out those connections. What I lack in a direct approach, I make up for in novelty and creative/divergent thinking, which has the benefit of sometimes opening up new opportunities to explore.

Stay Awesome,

Ryan

Stepping Back Into The River

As the saying goes from Heraclitus, you can’t step in the same river twice. There are two ways we can interpret this metaphor. The most common interpretation is that you cannot step in the same river twice because the river is constantly changing. The water is flowing past, the flux of the water is changing the boundaries and composition of the river, and so it’s impossible to step into the exact same river twice. But another way to interpret the metaphor is to place more emphasis on the you – You can’t step in the same river twice – whereby the you stepping into the river changes and is not the same over time. This can be taken as literally as when describing the flux of the river – your cells are changing, etc. But I like the more poetic version of the metaphor that speaks to us changing with our experiences through our lives.

When you return to a river (the river being a stand-in for any number of things), you are a different person, and your past experiences make the phenomenological event that you experience different. The first time I encountered this was retaking a course in high school. I was the kid that took a course called Writer’s Craft, loved it and the instructor so much that in the following year I enrolled in it again with the same teacher. However, the materials selected for the class by the teacher, and indeed my fellow students, were all different. It was different, less enjoyable this time around. I still enjoyed studying under my teacher, Mr. Steffler, but with it being a different cohort of students (students from the grade below me), I realized that the experience lacked the magic of when I took it with my original cohort. I tried to step in the same river twice and was surprised when it was different; that I was different.

There is also the case where you revisit a book you read previously and it speaks to you on a different level. Maybe your experiences help you connect with the characters on a different level, or you empathize with the characters differently. Your values might have changed. Or just that you are older and more knowledgeable, you understand more of the text and draw different connections.

This happened to me recently. My job promotion at work was approved, and I’m taking on management tasks as part of my portfolio. Maybe because I have mild imposter syndrome (I sometimes believe I am continuing to fail upwards), or maybe because I’m trying to be proactive, I decided to pull my copies of books by Peter Drucker off the shelf to learn what it means to be in management and how to do it well. I started with a short text of his called Managing Oneself, which I read back in 2017.

Something in the book landed differently this time, which I think breaks down to two differences about me now versus who I was five years ago. The first is I am busier now than I was then. This isn’t to say I was idle then – I was working three jobs, heading up a non-profit, in a relationship, etc. However now my life feels fuller with things that feel more critical – a higher stakes position at work with more responsibility, co-managing a household with my wife, the responsibilities of family and childcare, dealing with a pandemic, etc. I might have fewer work domains on my radar than I did in the past, but things have higher stakes now, and the idea of more effectively managing myself speaks to who I am as a person, where I’m trying to be mindful of others, plan for the future, and lay down a good foundation to support our family as we go.

The second thing that landed differently was the section about learning more about yourself and how you operate as you manage yourself/your life. I don’t remember this sticking in quite the same way (and based on my blurb from Instagram, it seems I was slightly underwhelmed by the text). For as much as I feel like I’m an imposter sometimes, I also know myself more now, am more confident in my skills, and have cultivated experience and expertise as I travelled along my career path from then until now. And so to revisit this section about managing yourself (that is, identifying what you should prioritize your focus on nurturing and developing) speaks to me. Rather than being frenetic and jumping on every opportunity while you are early in your career, it is better to slow down, be mindful, and think through what will add value to your life.

I don’t need to worry about losing out on opportunities by not acting fast. Instead, I can think about enhancing quality, enriching life, and paring down the things that no longer serve me.

I thought I was going to read the book a second time to remind myself of its content. Instead, I realized I was coming at the book afresh, for the first time, ready to learn.

Stay Awesome,

Ryan

Blocking Distraction

For as much as think I am in control of my impulses, the reality is I am buffeted around by my whims far more than I wish were true. The biggest bane to my daily work is the mighty well of distraction that is YouTube. I’ve lost hours of time in a day allowing my subscriptions to serve me fresh content. I try to justify it to myself – “I’m just going over for a quick mental break,” or “I just need to see a tutorial on how to do x-action in Excel.”

Then, I look up and hours might have passed without me consciously knowing it.

Some time ago, I used a browser blocker to prevent me from accessing the worst offenders for distraction (all social media, YouTube, and Reddit specifically). I’m no stranger to signing an Odysseus contract, which I’ve written about before. However during the pandemic, I relaxed it a bit since, hey, we are all going through a rough time.

As of late, I’m forced to conclude that enough is enough, it’s time to hold myself to a higher standard. I went back in, and toggled StayFocusd back on, and so far have done a better job of accounting for my time. Between blocking distractions, using pomodoro sprints, and writing down what I do in my time blocks (quick estimates, nothing too detailed), I’ve done a pretty good job of limiting distracted time.

It’s not perfect, but it’s more than a 1% improvement, which will hopefully compound over time.

Stay Awesome,

Ryan