• Decide what habit you want to have and record why you want this habit
• Start with the smallest amount of effort possible
• Increase the amount of effort regularly until you reach the desired amount of regular effort
• Track your habit in a habit recording system such as Loop Habit Tracker
• Review on a regular basis (monthly) whether you want to keep this habit or not
  • If you decide not to keep the habit, record why you decided to drop the habit such that if you decide to pick it up again, you can determine whether you might end up dropping it again.
• It's not a problem if you miss doing your habit, just make sure to do it when you're supposed to

My habits

Daily

• Daily planning
• Daily review
• Eat/Drink
• Shower
• Wash dishes
• Cook
• Exercise
• Read
• Watch TV shows
• Floss
• Brush teeth

Weekly

• Weekly planning
• Weekly review
• Wash clothes
• Clean apartment
• Buy groceries

Monthly

• Monthly planning
• Monthly review
• Pay bills

Yearly

• Yearly planning
• Year review

My prompts

• Daily planning at 10 am
• Weekly planning on Mondays
• Monthly planning on the first of the month
• Pay credit card on the first of the month

My prompt sources

• Google Keep
• Google Calendar
• Google Mail
• Slack
• Daylio
• Notion

Question

Given a library of processes, how can you determine which process you should be following?

Answer

Make a list of all the processes you have. Link to all the procedures to follow in each case. Some processes you will use so frequently that you will learn them.

Processes have starting points, that is, a trigger that initiates them. For example, if you have a process for code reviews, the starting point is the creation of a pull request by someone else. Another trigger might be the beginning of a new project. You should look for and recognize those triggers. If possible, when you document your processes, indicate what will trigger the instantiation of one of these projects.

Try to frequently look at the list of triggers and think about what you are working on or will be working on. This will allow you to catch processes that should have been started and followed, as well as let you prepare for processes that are about to start.

As you accumulate more and more processes, you will observe that there is a hierarchical organization to them. As one process starts, you can already prepare a list of processes you may have to follow soon.

You will also observe that the completion of a process often will lead to the start of another one. Once you've established enough chains (sequences of processes), it will be easier to identify and do the processes.

References

• How can I be systematic in applying processes?

Question

How can I be systematic in applying processes?

Answer

The first step is to always make your processes explicit. Write the various steps you go through while doing something. First, simply write down those steps as you do them. Then indicate the dependencies between the steps. You may notice that some steps can be done earlier in the process if all their dependencies are already completed.

As you write down more and more of your processes, make sure that you can easily refer to them. If possible, keep them in a centralized location where it is easy for you to edit them. In my case, I write my processes in this blog.

When you begin doing something which you've never done before, create yourself a document and write down the steps you are doing as you do them. Once you are done with the task, save your document.

When you begin doing something for which you already have a process in place, open up your process document and quickly glance at it. Start going through the process without using the document and jot down what you do. After you are done, look at what you did and compare it against the existing process. Is it the same or has something changed? Did you forget to do something? Did you do something new? Did you change the order of some of the steps? Apply the changes you think are useful to your process and repeat this discovery phase a few times.

After you've established a process, you can simply open the process document and follow it. If you notice that some steps are still missing, do add them to the document. If you version control your processes, you will be able to observe how it evolves over time.

One benefit of making your processes explicit is that it allows you to stop doing them for an extended period of time. When you need to do them again, you can simply look at them again and know what you need to do. It is also beneficial if you work in a team where you could delegate some of those processes to other people.

References

• Reducing your error rate

• Define what is it you want to communicate
• Define why it is you want to communicate what you want to communicate
• Write down all the topics you want to cover
• Organize the topics in a structured manner (i.e., an outline)
• Write a draft
• Expand the points of the draft
• Review the grammar with https://www.grammarly.com/
• Use keywords services to find topics that may be related and interesting to cover

• Define the audience
• Define the purpose
• Define the assumptions
• Provide a way to contact the author
• Provide a way to ask additional questions