How to be Productive

Table of Contents

How to be Productive

I have recently come across a beautiful infographic by Anna Vital.

I have been a productivity enthusiast for ages, but my approach has evolved over time, so it’s time to make some kind of summary here. When I look at the elements in this great mind map, I recognize almost all of them. Most of them I have tried, and many I still use. But now, I view such things differently than I did ten years ago. Back then, they were just a bundle of handy hints that I read from time to time, and they didn’t mean much to me — just like all those fancy “good practices” that everyone knows but very few apply. It was a time when I was hungry for fast solutions — easy ten points that would change my life. But they didn’t, of course.

Because important changes require time. They require patience and perseverance, which are increasingly uncommon these days.

It took me almost a year to figure out how to manage my anxiety through workouts, such as running, with all the nuances needed to do it effectively. And believe me, I’m a smart guy, so the delay wasn’t due to stupidity.

I spent almost a year to REALLY experience what it means to focus on important things and suppress the urgent. Most organizations don’t do this, even if they claim to. It’s not easy to tell your customer, with courage in your heart, “We will not do this under these conditions, within that timeframe.”

It took me a couple of months to start making conscious decisions about healthy eating, to understand and feel the consequences.

I tried at least ten times before I gave up staying connected with the news.

It took me TEN years before I really understood and experienced that lack of sleep is disastrous and contrary to any productivity goals.

And so on and so forth. All that stuff because unpracticed knowledge is just noise.

After those ten years, I realized that the most important thing is to slow down and give yourself time. Important changes require time, and you cannot accomplish them in fast-track mode. Many books and trainers promise us quick results, but remember, it’s just marketing.

I recall that ten years ago, I loved such lists because, as a tech guy, I liked having short lists with the most important information. So I read them, but nothing lasted in my head.

They are great as reminders if you practice all this stuff, but not particularly helpful for incorporating into a daily routine when you’re starting. You need at least a book on each subject, or better yet, attend training, and after that, practice it for months. Then you’ll succeed.

There is one revelation when you have a deep understanding of a rule after long practice: you don’t need that rule at all. You have it built-in and know exactly when to apply it and when to break it. But that comes with time. No shortcuts.

Finally, there’s an obsession with productivity, but we must remember that productivity is the opposite of creativity. As a knowledge worker, you cannot be productive 100% of the time; otherwise, you just become a reflectionless robot.

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Related Posts

Call for Code Samples

Call for Code Samples

I would gladly present the idea of the natural order of refactoring using an example code. Unfortunately, for obvious reasons, I cannot use our clients’ production code, and I do not have the time to prepare an example for this purpose. However, perhaps someone would be willing to allocate their piece of code, a project that doesn’t have too many (or any) restrictions on public publication.

Read More

Building Knowledge in Teams: Main Mistakes and Strategies

Building Knowledge in Teams: Main Mistakes and Strategies

The topic of knowledge management in teams is largely overlooked by IT leaders. There is a silent assumption that it happens automatically. To some extent, it does, as programmers are accustomed to constantly learning to stay ahead. However, this is not sufficient. It’s not enough for everyone (or realistically, half) to learn individually. If the team is to be effective, cohesive and up-to-date knowledge is needed. Knowledge of new technologies or solutions holds limited value compared to this.

Read More

If You Were to Do One Thing, It Should Be...

Avoid Starting Unnecessary Projects

I have had an interesting conversation with my friend who is also a manager in one of the Polish companies. At a certain moment, he said:

Read More