SYSTEMS. INFORMATION. PEOPLE. PROCESS

When something isn't working, I want to understand why.

I look beyond the visible problem to examine what is happening across the system, the information, the people using it, and the process surrounding it. 

I trace what happens, where information changes or gets lost, where people are having to work around the system, and where a problem that looks simple may actually have several connected causes.

The goal isn't just to find where something went wrong.

It's to understand what is actually happening so the right problem can be solved.

Different people need different things from the same information.

I translate what is happening into language that makes sense for the people involved—business teams, technical teams, users, Leaders, or different organizations working together. The information stays transparent and accurate, but I tailor how I communicate it to the person or group who needs it.

I also look at the impact. What does the situation mean for each group or person? What does it cost to make a change? What does it cost not to make one? Where are time, money, resources, risk, or effort being added unnecessarily?

The goal is to remove the unnecessary complexity between point A and point B.

Each group should be able to understand what matters to them, what they need to do, what the system or process is doing,  what the impact is, and what happens next—without having to understand everyone else's world to get there. 

People often know what they need, but don't always have the words to explain it in a way that translates into a requirement or a test.

I want to hear what they're actually saying—even when it comes out as frustration, confusion, or “I don't know how to explain it.” I ask questions, look at the work from their perspective, and connect what they are experiencing to what the system or process needs to do.

Then I test the solution against what people actually need—not simply whether it does what the requirement says.

The goal is more than a system that technically works.

It's a solution people understand, can use, and actually want to use.

A process can work and still make no sense.

Sometimes the biggest opportunities are hidden in the little things people have simply learned to live with—the extra step, the workaround, the repeated task, the piece of information that has to be entered twice, or the small annoyance nobody thinks to mention.

I look at how work actually moves from beginning to end—not just how the process is supposed to work on paper. I ask about the things people have stopped questioning, because those small things can reveal where time, effort, information, or money is being lost.

Sometimes changing one seemingly insignificant part of a process can change the entire outcome.

The goal is to make the work make sense—and make it easier to do well.

Documentation is only useful if people can understand it and use it.

Sometimes the information is correct but stated in a way that doesn't make sense to the person reading it. Sometimes a step is missing. 

Sometimes the process hasn't changed at all, but the documentation is outdated because no one has formally reviewed it, confirmed it, and updated its version and date.

I look at the information itself, how it is communicated, what may be missing, and whether it still reflects what people actually need to know. I create, correct, clarify, and organize documentation so people don't have to rely on memory, guesswork, or the person who happens to know how things work.

The goal is to make knowledge clear, trustworthy, usable, and able to move with the organization.

A good solution can still fail if the implementation isn't thought through.

I look at what needs to happen before a change goes live. Does everyone know what they are responsible for? Is the order of the work correct? Are the timelines realistic? Which deadlines are hard lines, and which have flexibility? Are the right people involved—and are people who don't need to be involved being pulled into the process unnecessarily?

I also believe testing belongs before something goes live. Production is not the place to discover whether a solution works. By the time a change reaches the live environment, it should have been tested, understood, and prepared for—with the people responsible for it ready to support the transition.

The goal is to make the change work in the real world—not just on paper—and to give people a clear path from what they do today to what they need to do next.

I use generative AI as a working tool for research, information organization, analysis, problem exploration, and development.
I work across tools including ChatGPT, Claude, and Gemini, using each to explore possibilities, organize information, test ideas, and accelerate work.
But AI output is not the finish line. I question it, compare it with what I know, verify important information, identify what may be missing, and refine the result.
The value isn't simply getting an answer faster. It's knowing what to do with the answer once you have it.