I tend to approach work with a pretty simple question: What needs to happen, and what is standing in the way? I like to understand the bigger picture, figure out where the problem actually is, and then build something that works. That might mean managing day-to-day operations, solving a complicated problem, organizing information, or finding a better way to do something that has always been done the same way.
I also think the best work usually involves people. I try to listen before assuming I have the answer, communicate clearly, and understand where different people are coming from. I’m naturally curious, I like figuring out how things work, and I’m comfortable taking ownership when something needs to be figured out. At the end of the day, I’m less interested in just being busy than I am in leaving something better than I found it.
I organize my work around a simple goal: make the most of the time and resources available to me. When everything feels urgent, I step back and determine what actually matters most, what can wait, and what can be handled more efficiently.
One framework I use is the Eisenhower Matrix, particularly when managing competing priorities or a long list of tasks. It helps me separate what is truly urgent from what simply feels urgent, while keeping longer-term priorities from getting pushed aside. I tend to tackle the most difficult or demanding work first, then use smaller tasks and opportunities to maximize my time. When possible, I also look for ways to accomplish multiple things at once rather than treating every task as completely separate.
I rely on a combination of digital and physical systems to keep everything organized. My calendar is detailed, with notes, addresses, reminders, and daily priorities. For larger projects, I create dedicated files and organized Google Drive folders, often with subfolders and work logs so information stays easy to find and projects don't become mixed together. I also keep a flexible daily to-do list alongside longer-term priorities.
The system isn't meant to be rigid. When something unexpected becomes urgent, I reassess, adjust, and get to work. Good organization, to me, isn't about having a perfect system. It's about creating enough structure to stay focused, adapt when circumstances change, and make the most of the 24 hours everyone has.
A simple framework I use to separate what needs attention now from what deserves time, planning, or less attention.
I start by taking a step back. Before changing a process, I want to understand how it works, where the friction is, and what is actually causing the problem. I focus on the root cause rather than rushing to fix the symptoms.
I also don't believe something needs to change simply because I would do it differently. I look for practical opportunities to save time, reduce unnecessary steps, improve access to information, lower costs, or create a better experience for the people using the system.
Much of my work has involved taking existing systems and making them work better. I have built a centralized grant database, digitized paper records into a searchable shared system, and standardized constituent intake to make casework more consistent. Each started with a practical problem and developed into a system designed around the people who would use it.
I believe improvement is collaborative. I build, test, gather feedback, and refine. The first version doesn't have to be perfect. It needs to be useful enough to learn from and improve.