Psychology Program operations Organizational systems Technology
I’m a recent graduate with a background in psychology and organizational leadership. Over the past three years, I’ve worked inside young, fast-moving programs where much of the operating structure had to be built, helping run the work while creating the workflows onboarding, information systems, and AI-assisted tools it needed. That experience taught me that the work people compensate for often reveals more about an organization than its documented processes ever can.
What did the two-hour savings estimate actually measure?
When a behavioral health organization turned estimated AI time savings into higher productivity expectations, I designed an assessment to find out who was saving time, who was not, and what support effective use required.
The pattern beneath the work
What someone first names may be the problem, but it may also be a symptom, a workaround, or simply the point where pressure became visible. Before deciding what to build, I look at the problem across the people doing the work, the process they were given, the tools available, and the organizational conditions shaping what is possible.
A documented process tells me what was supposed to happen. I also want to know what people actually do, where they pause, what they carry outside the process, and which workarounds have become normal. That is often where the real problem first becomes visible.
I look for recurring patterns, structures, assumptions, incentives, handoffs, role boundaries, and gaps between the formal process and actual behavior. The point is not to make the problem sound bigger. It is to understand why it keeps returning and which part of the organization is capable of changing it.
Software may be one answer. So may training, clearer ownership, a different workflow, a shared resource, added capacity, or a policy decision. I compare the options against the people involved, the work each option would add, the behavior it would require, and whether the organization could realistically support it.
Once the diagnosis is clearer, I can decide what is worth building and how far it needs to go. The goal is not always the smallest answer. It is the response that addresses enough of the real problem without introducing more work, cost, or structure than the organization can carry.
I define what the response is supposed to change, which assumptions need to be tested, and what evidence would show that the work improved. A launch, completed deliverable, or adoption number is not the result. The result is whether people can work more clearly, reliably, and manageably because something changed.
I kept building what the work was missing.
Three years of operations and program management inside a young community nonprofit and a behavioral health group, both growing faster than their infrastructure, working across most parts of each.
How I got hereGraduate Study
An M.A. in Organizational Leadership, with a concentration in Change Leadership, gave the things I had been noticing at work a vocabulary and a discipline: systems thinking, organizational diagnosis, change leadership, evidence-informed decision making. The capstone turned that into a four-part diagnostic workbook.
Read the graduate workNotebook
The Notebook shows the thinking that a finished project page cannot: questions I am testing, ideas that are changing, and places where I have not reached an answer yet. It is a record of learning in motion.
Read the Notebook