Habit Tracking Success
It’s important to invest in yourself, regardless of your employment situation. This is especially true if you work in a sector or field like research. And it’s even more true if you’re at the trainee stage of your career (e.g. PhD students, postdocs).
And for the longest time, I feel like I really struggled with this, often because as an interdisciplinary researcher, there is just to much to learn and do. You both want to knowledgeable about all things music, but you also need to be able to use the tools of the sciences in a way that actually warrants their use and are not just stamping a half baked idea with a significance test.
At several points over the last few years, the feeling that I wasn’t actually “on track” (self imposed) to be learning what I knew I wanted to learn was very disheartening. Weeks or months (or years…) felt like they would go by and I still had made no progress on something I knew would be helpful to know or do, but just hadn’t made a priority. And then at the most random of times, I’d be reminded of this lack of attending to it, and give myself a bit of a guilt trip over it. The guilt trip would be worse if it was a skill that in the long run I knew would actually make my life easier.
A great example of this for academics like myself in similar positions is learning about computer science and programming. Unfortunatly, I am a self-taught programmer for the most part. This means that my teacher was me, who didn’t know much about where I should be spending my time and energy while learning. What guided my progress was having to exectue a specific task or analysis, often with a very real due date and responsibility to other people, which just added to the stress of having to learn some skill.
In practice, what this looked like (with R being my first langauage) was starting out thinking that programming was akin to typing out the point-and-click ritual of something that you’d do in something like SPSS, with the eventual end goal of just being able to do more and more complex analyses. Maybe borrowing or getting inpiration from other people’s code, eventually absorbing good and bad practice, almost haphazardly.
The times in which I would find something better, the experience was always transformative.
I specifically remember the feeling of relief early on in my R programming of copying and pasting some do.call()
to get a bunch of csv
s to merge or re-factoring some repeated code into a set of functions that I could use and just reference in another file.
Knowing how helpful each of these little experiences were in the moment, it makes sense that if I have to work for the next thirty or so years, that there must be other “things” that I can learn that are going to make my life a lot easier in the long run. In the case of programming, this is by far the clearest example. But there are other activities like learning new langauges, becoming more knowledaglbe about statistics, playing piano, and staying healthy that also fall into this category.
All of these things (and more) is a lot to keep track of, especially with actual work responsibilities to manage. And until recently, I never felt like I really was actually on top of it, or at least on track. That is until recently, when I sort of had two ideas collide.
The first was the result of listening to a lot of audio books (something I actually do a lot of since getting an Audible subscription, found it’s great for going about my daily life in London). Every so often I read a “productivty book” (Getting Things Done, Deep Work, things your tech bro colleauges make their personality for a few months) and a few months ago this was Atomic Habits.
My honest opinion of the book is that it could have been a pamphlet, but the ideas in the book were generally pretty good and were a nice condensation of thoughts on how to actually build habits.
But one small anecdote that really stood out to me was where the author talked compounding interest in the context of building habits. The idea (though confounded in many ways) was that a 1% decrease in your ability is always going to take more out of your ability than a 1% increase.
As a computational model, I don’t think this makes any sense (in this form). But it did resonate with my experience of the pain of having many days go by in which I did not at least somewhat engage with something I wanted to do.
The second point came from reading Getting Things Done last year and now being on a quest to slowly intergrate that methodology more in my life. A big key to GTD is having a weekly review (for several reasons). But specific to this whole situation I have been talking about, the weekly review allows you to take a pro-active look at all the things that you are choosing not to prioritise at the moment, rather than having some lurking idea or project spring itself on you when you are already feeling down on yourself.
This may seem minor, but is actually very important to not have that pang of guilt hit you when you STILL have not started project X, Y, or Z for however many weeks, months, or years after it’s been hiding out of sight, out of mind.
So these two ideas have come together in using this Habits App that you can get on the app store. The TLDR of this post is that I just now use this app and really, really like it.
The way it works is you set up a few habits that you just want to keep an eye on, then just literally set up the least ambitious version of the habit, setting the rate that you want to attend to it (always low balling what you can actually do).
So, for example, I have been using Duolingo to help me learn Dutch phrases and volcabulary. With this, the question then becomes, what is the smallest unit of learning Dutch I could do? In the case of keeping Duo happy (you know what I am talking about if you’ve used this app before), it’s just one lesson. None of this ambitious 15 minutes a day or watching some Dutch TV or whatever. Just log on, do some lesson, get a tick on the streak.
For the langauge learning, it’s one of the few I actually want to set a rate of learning every day. The only other one is drinking two litres of water.
The other ones happen less frequently. For example, I am trying to play more piano. On a good week, I’d play (remember, literally just sit down and play through one lead sheet for example) maybe four out of seven days a week.
But the thing is, most days I want to keep going once I actually am in front of the piano. Sometimes it’s just ten minutes, but often I will just keep on going much longer than that.
And some of this list have been languishing, such as playing piano or lifting weights regularly. But that’s OK. Sometimes I don’t have access to a place where I can make a lot of noise or am around weights I can lift. But the point of seeing it with the other habits is that it links back to GTD of meeting it first and knowing you will make it a priority when you can and you want to, not it just flashing in your mind when you need to find more things to beat yourself up about.
Of course there is a temptation to just pile on a lot onto this app (a bad idea, future projects should go on in the “Future Projects” list), the point of this app is to more have general categories of areas of meaning in your life that you want to spend time doing regularly.
It’s very true that how you spend your days is how you spend your life, so having this structure really protects and priortises this.
But the biggest win I have had basically doing this (and thinking about this recently), is that I have not had any of those “Ah, why haven’t I started learning X, Y, or Z” in the past few months. It feels like I have more control or maybe agency in how I spend my day to day.
The reason I am now thinking out loud about this is because I am now again working with Masters and PhD students and want to also pass on what I find to be helpful in cultivating skills in such unstructured environment where the amount that you have to do in the future often seems insurmountable. So more posts like this to come in the future.