Setting yourself up to succeed

Sandor Dargo - Feb 28 '18 - - Dev Community

This article has been originally published on my blog.

In this post, I'm going to share with you who I schedule my time and how I identify which road to take next.

First, let's make it clear what success means in the actual context. Let's say that success is about how much you are inline with your internal goals. An internal goal is something that you set for yourself and not your manager for example. If the goals articulated by you and your manager are the same, you are either very lucky or you have no will, no vision at all.

In order to achieve your goals, you have to work smart and don't get deceived by people promising overnight success, you have to work hard as well. For that you need time. I think you already see what direction I am going to if you have ever read any of the modern motivational authors.

In order to succeed you have to spend your time on what really matters to you, what makes you progress. One would call it time management, others argue and call it priority management. In the end, what matters is what you work on.

I think I've understood this for quite some time. I've been using schedules, agendas and task lists for long years. I was more or less following them, but more or less is usually not enough. I knew I could do better, but I didn't know how.

I read a few times about the pomodoro technique, but never really felt the urge to try it. Then I came across Soft Skills: The software developer's life manual by John Sonmez and simpleprogrammer.com. I don't remember exactly where he mentioned this, but he said that he tried pomodoro once, but didn't really like it. Then a friend of his convinced him to give it a try once more, but this time strictly following the rules. John resisted for some time, but then he gave in. He tried it and guess what?! The pomodoro technique combined with some tools totally changed the way he worked. This resistance, this fear of new things was so human that it really resonated with me. I said I also give it a try.

So about half a year ago I started to deploy a systematic approach for designing my workdays and weeks. In the explanation, I'm going to follow a bottom-up approach.

Those sweet tomatoes

I work in pomodori, so in units of 25 minutes. After each pomodoro, I take a 5 minutes break that sometimes lasts a little bit longer. After four pomodori I take a break of 15 minutes.

What do I do in those breaks?

In the short ones, I might walk a bit, or read a short article, or just answer a few chats, go the printer if I need to, etc.

In the long breaks, I can answer some emails, read some medium-sized articles, complete some quick tasks, whatever. But usually, my first big break starts when our daily standup meeting starts.

What do I use a pomodoro for? So just to emphasize, a pomodoro in our context means 25 minutes of uninterrupted activity. The same activity. Unless it's my wake-up or go-to-bed reading, I read in pomodori. I write blog posts timeframed. I work on wine-disco in pomodori, I do my day-to-day job based on pomodori. I do everything based on those tomato units that have any chance to last for at least 25 minutes.

It keeps me focused on the given task, don't let my mind wander that much and I always know what to take as a next task.

Kanban

But how do I know that to next you might ask? I have a sort of kanban board in order to list, to schedule my tasks. I use the free scheme of KanbanFlow. I have a column for each day of the week (well, I only do it for the workdays) and one column named next week and one for done tasks.

Each end of the week/beginning of the week I take tasks from the Next week column and I move them for a given day.

On a given day when I complete a pomodoro, I have to choose among three options.

  • I move the task to Done
  • I keep the task because I want to work more on it the same day
  • I move it to another day or the Next week column, for future work

If you want more details, you can watch a video from John Sonmez here.

I don't only add tasks that I work on in pomodori, but smaller ones that serve more as a reminder. For example that I shouldn't forget to print a reservation confirmation.

So that's how I organize my work.

There are a lot of tasks that are recurring. For example almost every day I write for 25 minutes. I'm writing a longer article about how we bought our apartment, but I'm also preparing a book about how I became a software developer. It's more a bio of my first twenty-something years.

Each Monday I dedicate one pomodoro during my lunchtime to review my goals. Not just the weekly ones, but the ones for longer terms too.

Setting my goals

I have a few spreadsheets filled with my goals, approach from different aspects. Let me go into some details.

A bucket list of 100

In one I name 100 goals. It's like a bucket list about what I want to achieve, to try, to see in my life. I read them every week so that I keep them in focus. If I can achieve just 5 per year, in 20 years I will have completed them and I will be still only 51 (I started it about a year ago). I took this technique from Jon Westenberg.

Design my growth

I create a few small lists that I update regularly.

On a yearly basis:

  • I write down my motivations
  • I note my most important values
  • I check what are my top strengths and weaknesses

On a quarterly basis:

  • I set three objectives and also the measures so that I can check if I achieved them

I review my objectives every week to see if I made some progress, if not how I should adjust. For example, for this quarter I have an objective about learning JS and to publish my article about how we bought or flat.

A-B-C technique

This technique I took from Ben Hardy and I try to include it in my weekly goal setting pomodoro every once in a while.

I created three columns:

  • In column A I wrote down activities irritating me. Like time-waster meetings, commuting.
  • Into column B I put things that sort of okay, like washing the dishes or cutting fruits for the next days. You might be surprised, but washing the dishes after a day of coding can be refreshing.
  • Into the last column (C), I save the things that are great, like spending time with my family, coding, writing, hiking, cooking...

The point is that most people spend too much time on activities coming from the first two columns whereas we all should spend much more time on activities that we find uplifting. So given your three columns, the big task is to eliminate everything or at least most of them from column A and preferably from B too.

There is a very interesting exercise related to this technique. You take one of your items from column C and you ask yourself why do you like that. Let's say you have there that you like coding. Then you ask yourself why do you like coding. The answer might be because you like to solve problems. Then you ask the question again. Why? Why do you like solving problems. Repeat these steps until you dig down for at least five levels. Keep doing this with several items and you will learn a lot about yourself and your strongest whys.

Summing it up

As you can see I try to live my life in a planned, scheduled way so that I can the distractions minimal. I use the pomodoro technique in order to limit the interruptions on the low level and I organise the tomatoes with the help on Kanbanflow so that I know what task comes after the other.

In order that my tasks make sense I dedicate one pomodoro each week to reflect on my goals and to see what should come next. It helps to remove distractions from my long-term perspectives and to keep up my motivation by slicing big goals into smaller ones. And actually like that by the time you achieve a goal, you have the next one right in front of your eyes, so you limit the chance of an "after success depression and a burnout".

Call for action

In order to boost your productivity, explore the pomodor techinque and start using it immediately.
Once you start enjoying and valuing uninterrupted chunks of work, think about what you want to achieve with the extra time you have. Try the tools and techniques I described:

  • Kanbanflow to organize your tasks
  • Build a bucket list to know what you want in your life
  • Design your growth to have mid-term objectives supporting your long-term goals
  • Use the A-B-C technique to identify and get rid of time waters and to understand your deepest whys.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terabox Video Player