Less Tools, More Mastery
I'll admit it — I used to be a tool junkie. Every time a new productivity app launched, I was first in line to try it. My digital workspace was a graveyard of half-configured tools, abandoned workflows, and forgotten subscriptions. I thought the right tool would solve my productivity problems, but all those tools were actually making things worse.
The turning point came when I realized that tools should serve your workflow, not define it. I did a complete audit of everything I was using, ruthlessly cut anything that wasn't earning its place, and committed to mastering the few tools that remained. The result was a dramatic improvement in both my productivity and my mental clarity.
The philosophy: depth over breadth
Before I share specific tools, I want to share the philosophy behind my choices. I believe in going deep with a small number of tools rather than going shallow with many. When you master a tool completely — when you know every shortcut, every hidden feature, every way to customize it to your needs — it becomes an extension of your thinking rather than an obstacle between you and your work.
Most people use about 10% of any given tool's capabilities. They switch to a new tool when the old one feels limiting, but the limitation was usually in their knowledge of the tool, not in the tool itself. Before adding any new tool to my workflow, I ask: "Have I fully explored what my current tools can do?" The answer is almost always no.
For writing and thinking
Writing is at the core of everything I do, so my writing tool is the most important piece of my stack. I use a plain-text editor with minimal formatting options. No fonts to fiddle with, no templates to browse, no distracting features. Just me and the words. This simplicity is intentional — it forces me to focus on the quality of my thinking rather than the aesthetics of the page.
For longer-form thinking and planning, I use a networked note-taking approach where ideas can link to each other. This has been transformative for connecting concepts across different projects and seeing patterns I would have otherwise missed. The key is that I treat my notes as a living, evolving system rather than a static archive.
For project management
I've tried every project management tool imaginable — from complex enterprise solutions to simple to-do lists. What I've settled on is deliberately minimal: a kanban-style board with three columns (To Do, In Progress, Done) for active work, and a separate document for quarterly planning and long-term goals.
The simplicity is the feature. When your project management system requires its own management, something has gone wrong. I want to spend my time doing the work, not organizing the work. Every minute I spend moving cards around a board or updating status fields is a minute I'm not creating value.
For recurring tasks, I use a simple checklist that resets each week. No automations, no dependencies, no Gantt charts. Just a list of things that need to happen every week to keep the machine running.
For communication and collaboration
Communication tools are where most people's productivity goes to die. The constant pinging, the red notification badges, the expectation of instant responses — it's a recipe for shallow, fragmented work. My approach is to batch communication into dedicated time blocks and be very intentional about which channels I monitor and when.
I check messages twice a day — once around midday and once in the late afternoon. Outside those windows, notifications are completely silenced. This felt radical at first, and some people were initially frustrated by the delay. But over time, people adapted, and the quality of my responses actually improved because I was giving them my full attention instead of firing off distracted one-liners between tasks.
For content creation and publishing
My content pipeline is designed around removing friction between having an idea and publishing it. I use a system where ideas move through distinct stages — capture, develop, draft, edit, publish — and each stage has its own dedicated space. This prevents half-formed ideas from cluttering my drafts folder and ensures that nothing slips through the cracks.
The publishing step is intentionally one-click. When a piece is ready, I want to be able to get it out into the world immediately without wrestling with formatting, scheduling, or platform-specific quirks. Any friction at the publishing stage is a potential reason to procrastinate, and I've eliminated as much of it as possible.
The meta-lesson
The biggest lesson from my tool journey isn't about any specific app or system — it's that your tools should be invisible. When your workflow is working well, you shouldn't be thinking about your tools at all. They should fade into the background, leaving you free to focus on the actual work.
If you find yourself spending more time configuring, customizing, and switching between tools than actually doing creative work, it might be time for an audit. Strip everything back to the essentials, master what you keep, and watch your productivity transform.