Comfortable Being Uncomfortable
For 35 of my 37 years on this planet, I’ve lived in the state of Minnesota. Notorious for its cold winters, I’ve grown a certain affinity for the discomfort January and February bring. With a record low of -32°F (-35.6°C) in my lifetime1, I’ve had a lot of cold weather experience.
I like to get outside and feel the bite of the cold and see my breath hanging in the air, for me it’s an invigorating experience! Some days, I endure the cold by driving to the store to pick up dinner or more wood for the fire. Other days, I want to embrace the cold by putting on my biggest coat and warmest boots and head out for a walk across a frozen lake.
I take a similar approach to new data projects as I do to cold weather, looking for uncomfortable moments as signals that an opportunity has arrived. Those moments are a time when I can get outside my comfort zone and experience something new. They can come in the form of a tool that doesn’t work quite right, a table that’s missing the field I need, or being faced with a concept I don’t know.
I often encounter these moments while developing the first iteration of a product or feature, when novelty is at its highest and I’m discovering and testing new ways to work with data. Once I’ve found something uncomfortable, deciding how to react is the key to making those moments work for me rather than frustrate or block me from finishing what I set out to do.
Here are three ways I react to discomfort in data:
Enduring discomfort and solving issues locally has often been my first reaction. Whatever the cause of the discomfort, I can solve it and go on with my day. These issues are small, limited in scope, and quickly solved. As an example, let’s say my data input has a “sales” field coming in as a string with some punctuation mixed in.
To solve this discomfort, I could write some logic to correct the format and data type.For the moment, the problem causing my discomfort has been solved! A great local solution for me, but the root issue remains. I’ve both endured the discomfort today, but allowed the root cause to also endure and strike again!
If the situation is one where I need to deliver quickly, it’s unlikely I will perform the same operation in the future, or I’m exploring a dataset for the first time, enduring discomfort can be a short-term time saver. However, I’ve been resisting the impulse to apply these small-scale band-aid solutions more as my career progresses, since it has little upside for me or for my team.
Working with data is, at times, an exercise in embracing discomfort and growing to enjoy it, turning small “data aches” into moments of growth. I take advantage of these moments to discover novel solutions to a problem or learn a new concept.2
I’ve spent most of my career working with low-code tools that abstract away what’s happening with my data. Seemingly simple operations can actually require a series of complex and interesting steps to arrive at the result that’s displayed. Do I need to understand why dates in Excel start on January 1, 19003 or how the sorting function works4? No way. Is it a chance to explore how these systems function and broaden my ability to work with data in the future? Definitely!
We aren’t often incentivized to spend time exploring and learning new concepts during the normal course of work. Learning a new way to solve a problem takes time and mental effort, and our personal “R&D budgets” are often set aside for other priorities. I use moments of discomfort as opportunities to fit development of new skills into the natural flow of my day.
There will be times when tolerating discomfort isn’t the right thing to do and I work to eliminate the source of discomfort. I found being the “Data Hero” analyst who hacks together a solution to every problem thrown at me fun and rewarding, but I was covering up systemic issues that would haunt me as I tried to make meaningful long-term progress. I learned to identify smelly patterns, like manually importing the Excel spreadsheet from sales5 every day, and looked for more stable solutions. These can take time to build since the changes are often structural in nature, but saving my future-self frustration is worth it. Discomfort is one thing I don’t want to scale.
These posts help to improve my writing and crystallize my thoughts on topics relating to data, analytics, and product! Thanks for reading!
I love learning concepts rather than tool specific methods. They have better shelf life and are more portable. Tools come and go, concepts and techniques are forever. ↩︎
You know the one, it’s called
Daily Sales 2020 - v2_updated2023_FINAL(copy2)(3).xlsx↩︎