{"id":1237,"date":"2021-04-20T13:55:47","date_gmt":"2021-04-20T13:55:47","guid":{"rendered":"http:\/\/janbosch.com\/blog\/?p=1237"},"modified":"2021-04-20T13:55:49","modified_gmt":"2021-04-20T13:55:49","slug":"rule-4-automate-repetitive-tasks","status":"publish","type":"post","link":"https:\/\/janbosch.com\/blog\/index.php\/2021\/04\/20\/rule-4-automate-repetitive-tasks\/","title":{"rendered":"Rule 4: Automate repetitive tasks"},"content":{"rendered":"\n
\"\"
Image by Gerd Altmann from Pixabay<\/figcaption><\/figure>\n\n\n\n

Do you work above or below the API? Recently, I was introduced to the concept by a newsletter of Mark Manson<\/a> where he talked about people being left behind because they get stuck in a rut and fail to reinvent themselves. The idea is that when you work below the API, you\u2019re basically working for an algorithm that tells you what to do. The only reason your job still exists is that you\u2019re cheaper than the fully automated solution.<\/p>\n\n\n\n

We tend to think of jobs below the API as those requiring limited \nskills, such as Uber drivers, but with the emergence of AI, whitecollar \njobs are affected as well. For instance, ML\/DL systems are better than \nradiologists at analyzing medical images. In practice, this means that \nmedical images are analyzed by algorithms and those tell the radiologist\n what to do next to best diagnose and treat the patient. Similarly, for \nlawyers, NLP algorithms autonomously analyze massive amounts of \ndocuments to detect anomalies and then tell humans which ones to look \ninto. The same is used in accounting for bookkeeping records and \nquarterly and annual reports.<\/p>\n\n\n\n

The ambition for anyone has to be to work above the API, ie to engage\n in those tasks and activities that are difficult if not impossible (for\n now) to automate and to, directly or indirectly, program the algorithms\n below the API to do their job optimally. Of course, our ability to \nautomate tasks and activities constantly improves, meaning that the API \nis ever moving upwards towards more demanding tasks, as measured in \nterms of required education, intelligence and creativity.<\/p>\n\n\n\n

In our professional lives, the principle of working above the API applies, of course, directly. Some people I meet relish in repeatable, predictable tasks and get a lot of comfort and structure out of them. The work then becomes more of a habit, executable on automatic pilot. The more repetitive and structured a task is, the easier it is to automate and consequently, you\u2019re setting yourself up for obsolescence. I often hear as a counterargument that there are lots of subtle differences between the repetitions of tasks and it would thus be hard to automate. In practice, however, automating a task almost always requires a standardization of the context in which the task is performed.\u00a0\u00a0 <\/p>\n\n\n\n

Rule 4 for thriving in a digital world is to automate repetitive \ntasks. This means that you constantly look for ways to use software to \nperform tasks automatically whenever there\u2019s even the slightest \nrepetitive nature to them. Examples include simple things like \nautomatically redirecting emails into different folders so that you \ndon\u2019t have to waste time on irrelevant ones or elaborate spreadsheets \nwhere you only have to put in a few numbers to get the results of a \ncomplex analysis presented back to you. Of course, more complex \nsolutions include robotic process automation (RPA) and machine learning.\n You may feel that some of this is beyond your capabilities, but there \nare more and more low-code and no-code solutions that make it \nexceedingly easy even for non-programmers to create solutions.<\/p>\n\n\n\n

The reason for automating the repetitive tasks is for you to free up \ntime for the work for which your unique skills and capabilities are \noptimally used. This requires you to deeply engage with the subject \nmatter and to get into the flow that allows you to do your best work. \nConstant interruption triggered by urgent but relatively unimportant \ntasks is highly detrimental to your ability to deliver the quality of \nresults you\u2019re looking for.<\/p>\n\n\n\n

Privately, of course, automation of repetitive tasks is important to \nensure that you can spend your time on things that you care about. This \ncan range from automating monthly payments that you can\u2019t skip anyway to\n buying a robot vacuum cleaner to free up time, but also include hiring a\n tax expert to file your taxes for you or a personal trainer to ensure \nthat your time in the gym has the biggest impact. The latter isn\u2019t \nnecessarily a form of automation (yet) but serves the same purpose of \nfreeing your time up so you can spend it on things that are uniquely \nyours.<\/p>\n\n\n\n

Working below the API is a recipe for obsolescence. You should actively seek to identify repetitive tasks in your work and, once you do, investigate ways to automate them. This allows you to spend the majority of your time and energy above the API, where your unique skills, education and creativity are optimally used. Build the habit of continuously questioning and, where necessary, reinventing your habits for optimal outcomes.<\/p>\n\n\n\n

To get more insights earlier, sign up for my newsletter at <\/em>jan@janbosch.com<\/em><\/a> or follow me on<\/em> janbosch.com\/blog<\/em><\/a>, LinkedIn (<\/em>linkedin.com\/in\/janbosch<\/em><\/a>), Medium<\/a> or Twitter (<\/em>@JanBosch<\/em><\/a>).<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Do you work above or below the API? Recently, I was introduced to the concept by a newsletter of Mark Manson where he talked about people being left behind because they get stuck in a rut and fail to reinvent themselves. The idea is that when you work below the API, you\u2019re basically working for … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"generate_page_header":"","footnotes":""},"categories":[15,8,10,1],"tags":[],"_links":{"self":[{"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1237"}],"collection":[{"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1237"}],"version-history":[{"count":2,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1237\/revisions"}],"predecessor-version":[{"id":1240,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1237\/revisions\/1240"}],"wp:attachment":[{"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1237"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1237"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/janbosch.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1237"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}