Weekly Musings 154

Welcome to this edition of Weekly Musings, where each Wednesday I share some thoughts about what's caught my interest in the last seven days.

This edition of the letter looks at something that I've been struggling with a bit as of late. Something that some people around me don't fully appreciate, don't fully embrace when it comes to some of the more important undertakings in their lives.

With that out of the way, let's get to this week's musing.

On Needing a “Why”

In early 2021, my wife decided to take a language course at a local college. It had been a while since she'd done something like that and, in an effort to keep up with the other students in her class, my wife threw herself into her studies. To be honest, it was good to see her (at times) losing herself in something new.

As she does when she wades deeply into waters like that, my wife tried to push me into joining her in learning that language. To say that I was reluctant and resistant is something of an understatement.

Of all people, my wife should have known better than to suggest that I try to learn another tongue. It's not just that I lack a brain wired for learning languages. It's not just that I was a complete failure in my previous attempts to learn a new language (one of those failures my wife witnessed up close). It's just that I didn't, and still don't, have a why to learn that language.

What's a why you're asking? It's a strong, unshakable reason to learn or to do something. A why isn't something that you can develop into while learning or doing. It's not something that you can conjure out of thin air.

A why is something that you have or you don't. It's that simple.

The main reason I didn't have a why to join my wife on her language learning journey was that it's unlikely that I'd ever use the language. I didn't, and probably would never, engage with the language. In this case, engagement doesn't just encompass seeing the occasional sign written in the language or hearing an announcement on public transport. By engagement, I mean regularly and actively listening to, reading, conversing in, writing, and working in that language.

Without a why, all my efforts would have been fruitless. They'd have led to little or nothing besides a considerable amount of time spent in pursuit of at best meagre results.

But what about learning or doing something just for fun or for sake of learning or doing it? As I discussed in Musing 112, there's nothing wrong with that. Especially if no stakes are involved or it's something in which you're interested but not deeply passionate about. But if there are stakes involved or it's something you are deeply passionate about, having a why is essential to you continuing and having a hope of succeeding.

Your why isn't, and shouldn't be, a vague reason. It needs to be focused. Having a focused why provides you with motivation — both to continue and to succeed. Having a focused why helps keep you on path to achieving whatever goal have around whatever you're learning or doing.

That why doesn't need to be something grand. It could be something simple like I'd like to be able to comfortably travel in country where language x is spoken without using my native language too often. Using that as your starting point, you can hone your approach, pick the right materials and tool to learn or do what you want or need to learn or do.

In the middle of 2010s, a friend started learning the Python scripting language. She didn't make much headway, mainly because (as she confessed) she took up Python because people online were saying that was the programming language to know. When I quizzed her about her real reason for learning it, she said it was because she had piles of information that she needed to sift through and Python seemed best bet for helping do that.

After a bit of rethinking, she refocused. She adopted learning Python to meet the need to perform efficient data analysis as her why. My friend found a few courses which were devoted to just task, and she quickly made progress.

My friend's why around Python expanded to being catalyst for career change. These days, she works as a data scientist. Python (and her facility with it) is one of her key tools.

Having a why, though, isn't enough. No matter how hard your focus or try, you will succumb to the temptations of distraction. You will be hit by malaise and self doubt and boredom. For that reason, it's useful (as my Python-learning friend did) to break down your why into smaller ones, with each smaller why building on the last one. Over time, you fit those whys together like LEGO® bricks to create a whole that fulfills your overall why.

That said, you shouldn't feel guilty about not having a why. You shouldn't feel guilty (or be made to feel guilty) about not learning or doing something. Especially something that, say, a self-styled expert/guru/ninja/rockstar/influencer on InstaTube or TweetBook is proclaiming that you must learn/do or that everyone is learning/doing.

But if you do have a why that applies to anything, embrace it. Let it take you to where you want or need to go. Or, at the very least, as close to that destination as possible.

Something to ponder.

Scott Nesbitt