I build tools and systems that make space to think.
A good tool rewards repetition the way an instrument does. As you become fluent, you can give more of your attention to what you're trying to express. You know how it will respond, and that familiarity gives you room to improvise. I want that same relationship with the tools I work with. The actions I repeat most should take the least effort, and the tool should respond reliably enough that I can stay with the thought.
For a long time, much of running my agency demanded a different kind of attention. Starting a campaign meant carrying information across four apps. Pitching meant matching music to curators in spreadsheets. Reporting meant gathering evidence scattered across platforms and emails. All of it needed care, and all of it competed for the attention I wanted to give the music, the clients, and the business.
Building better systems changed where that attention went. Kickoff now prepares the records, invoice, folder, and client email for me to review. Pitching assembles a target list with its reasoning attached, leaving me to judge whether the music actually fits. Reporting gathers campaign results and prepares the dashboards and email drafts. Each system takes on the preparation that used to occupy me before I could make the call. I can spend more time listening, considering a campaign's direction, or thinking about what a client needs to hear.
That's why I care about these improvements beyond the hours they save. When work feels like a treadmill stuck on high, it's difficult to see the bigger picture. Working *on* the systems gave me enough distance from the daily administration to reconsider the work itself. Campaigns received more deliberation where it mattered, client relationships got more attention, and I had room to think about where the agency should go.
My consulting work starts with the same question: what is consuming someone's attention before they can use their judgment? For a real-estate team, it was keeping track of deals across tools and people. For a tour manager, it was remembering which show details were missing and keeping the day sheet, calendar, and email threads consistent. The systems I built give that information somewhere dependable to live, inside tools the teams already use. Their usefulness depends on how much easier they make the next decision.
I've also learned that having room to think means being able to leave the desk. Dubs lets me listen to a document on a walk and dictate notes into it as ideas arrive. Writ keeps my audio inputs and outputs where I want them, removing a recurring interruption. These products come from paying attention to the conditions in which I think well.
Making work playable means designing those conditions deliberately. With an instrument, fluency gives you more freedom in what you can play. I build systems because I want that freedom in my working day: enough familiarity to move easily, and enough room to follow an idea I hadn't planned on.