Trusted System != Trusted Softwarefleeting
trusted system != trusted software misconceptions about gtd,
To me, a trusted system is the aggregation of
- a trusted software,
- routines (like the weekly review),
- intellectual honesty,
Somehow, confusing both may for some time reach the goal of reducing the cognitive load, because you might believe that everything is under cruise control. After some time though, you will likely realize that stuffs not only don’t get done, but also stack up and make the software unusable to the point of creating much cognitive resistance using it.
For example, “clean the kitchen sink” might go in a context @kitchen and never be done, because:
- you actually never are in the kitchen,
- or you never think about looking at this list when in the kitchen,
- or if you look at it, you don’t feel like doing it,
Routines like the weekly review help you identify such issues and intellectual honesty helps you realize that you have to adapt your system.
About the kitchen sink cleaning, you might either:
- find out this is not that important (dichotomy of control),
- adapt your contexts so that they fit your habit (context ninja),
- plan the task in another context (in my case, it might be something like “plan some time to clean the kitchen sink” in @orgfiles),