The Systematic Problem of Building Productivity Systems
Jamie Todd Rubin
Jamie Todd Rubin often feels the need to build his own productivity systems instead of using off-the-shelf products, which he finds inadequate. He realizes that this habit stems from enjoying the challenge of creating systems, but it can also complicate things unnecessarily. Recently, he developed a personal archive system that has simplified his workflow, allowing him to focus more on writing rather than system-building.
28 Feb 2025
The answer to the first question—why I feel the need to build up these systems in the first place—is more about the challenge and less about the benefits than I like to admit. I build software systems for a living, so why not take advantage of that skillset? On the one hand it consumes countless hours that I could spend on other things; on the other hand, it hones my skills. This probably explains why I move from system to system. Once I’ve built up my system, the fun part is over. Using the system, the practical part is, well, boring. I find another system to build and see how I can improve based on lessons I learned the last time around.