How I Work
I bring fresh eyes, thoughtful questions, and practical solutions that make your work easier.
Thoughtful questions before quick answers.
I start by understanding the situation. What is happening? What problem are we trying to solve? How is it affecting the organization?
Sometimes the answer is straightforward. Sometimes the initial request points to a different problem underneath. Either way, my first step is to understand the full context before proposing the solution.
I bring fresh eyes, not a predetermined solution.
The people inside an organization have knowledge and perspective that I don't. My role is to bring another perspective: to ask questions, notice patterns, investigate what I don't understand, and consider possibilities that may not be obvious from inside the organization.
If I don't know something, I'll find out. Depending on the situation, that might mean research, talking with someone who has the relevant expertise, testing an idea, or working through the question with you.
The work is iterative.
I rarely expect to have the perfect answer at the beginning. I make an initial assessment and develop a proposal based on what I've learned, then refine it in conversation with the client.
That back-and-forth is especially important when we're changing how people work. The people who will actually use a system or document often have insights that only become apparent when they see a first version. Their reactions are useful information, not just approval or disapproval.
I adapt to the work—and to the people doing it.
Some projects are best handled independently. Others require close collaboration and frequent conversation. I adjust the level of involvement to what the work requires.
I also recognize that clients have different amounts of time and capacity. Sometimes the best thing I can do is take something off your plate and work it through independently. Sometimes I need your input to make sure we're solving the right problem.
Practical structure, without unnecessary complexity.
The goal isn't to create a system for its own sake. It's to make something clearer, more manageable, and easier to sustain.
That might mean a formal procedure, a simple checklist, a better way to organize information, a spreadsheet, a revised workflow—or sometimes just clarifying who does what and when. I strive for only the amount of structure that is useful for the situation.