Skip to content

Systems have to be fault tolerant

Dear Reader,

In scuba diving, you breath through a device called a regulator. Regulators are designed to fail “open”. If something goes wrong, it is better for a diver to have too much air than no air at all. The designers of the regulators acknowledge that at some point, the devices will fail, and try to minimize the damage done by failure.

The same thinking should go into our personal systems. I didn’t make resolutions this year, I setup systems. These systems have to take into account that ‘life happens’.  Resolutions fail hard, systems are fault tolerant.

Whether you are diving, coding, or living, build your systems to be fault tolerant.

Until next time,
I <3 |<
=C=

p.s. for more information on creating systems vs. setting goals, check out my post “Systems, Not Goals

Systems, not goals

Dear Reader,

I spent many years setting New Year’s resolutions only to see them slip by the wayside by the end of January to be forgotten like a child’s toy whose batteries had run dry. Then one year I just stopped. I recognized the futility of the process and just stopped making New Years resolutions. Or at least I stopped telling people that I made them. I still ha them in my mind. I changed what I was calling them, they are now  ‘goals for the new year’.

It didn’t help.

Then somewhere around March of last year, I started reading again. One of the books I read was Scott Adams’ “How to Fail at Everything and Still Win Big“. In it he talks about ‘systems, not goals’. For example, if you want to write more, don’t set a goal of 1,000 words per week, setup a system that will force you to write.

So this year, while I still have resolutions/goals, I am setting up systems to get to them and focusing on working the systems, not the goals themselves. Time will show us if this is a better way.

Until next time,
I <3 |<
=C=