Curiosity
I don’t accept a requirement until I understand why. The first request is rarely the whole problem.
I thrive in ambiguity. I’m most energized by technical problems without obvious answers—where requirements are evolving, systems are highly integrated, and teams need clarity before they can move forward.

“A problem is just a solution that hasn't been found yet.”
I begin by understanding the current state: production behavior, repositories, APIs, business rules, technical documentation, and customer experiences.
From there, I partner with engineers, architects, and experience designers to challenge assumptions, simplify complexity, and create scalable solutions that preserve technical integrity while making the experience understandable and usable.
I lead with curiosity, empathy, and evidence—because I’m not driven by being right. I’m driven by finding the right answer.
I don’t accept a requirement until I understand why. The first request is rarely the whole problem.
I slow the room down long enough to make sure we are solving the right problem, then create the shared language teams need to move.
The best ideas come from the room—not from hierarchy. Engineers, designers, architects, operators, and business partners all improve the solution.
I challenge assumptions with evidence, including vendor and leadership assumptions, when the long-term decision needs another look.
People do their best thinking when they feel heard. I create space for questions, dissent, and different kinds of expertise.
I’m comfortable saying I don’t know. Then I research, ask, test, and keep going until the system makes sense.
2025 cohort
Recruiting Lead
Directed 25+ events engaging 7,000+ students
B.S. Information Systems & Accounting · Millikin University
Certified ScrumMaster (CSM) · Scrum Alliance