12 direct reports. 5 concurrent projects. 6 countries. My approach to leadership isn't a template — it's a toolkit built from real pressure, across regulated industries, military service, and global teams.
I've led people who need directness and people who need rapport-building first. People who thrive on autonomy and people who need structured check-ins. Great leadership means reading which mode is needed and switching fluidly — not defaulting to the same style with everyone.
Over the years I've found ways to navigate complex personalities as a leader, a peer, and a direct report. The goal is always the same: build teams that deliver extraordinary results and develop individuals who outgrow the role you hired them into.
"Management is about persuading people to do things they do not want to do, while leadership is about inspiring people to do things they never thought they could."— Steve Jobs
Some people want the task and nothing else. Others need relationship-building before they'll engage fully. I identify which mode each person needs and meet them there — not the other way around.
Classic "compliment sandwich" for some, direct critique for others. The delivery mechanism is less important than whether the feedback actually changes behavior. I calibrate to the individual.
My goal isn't to maintain my team — it's to make them outgrow it. The best outcome is someone I mentored becoming a team lead themselves. I've seen it happen repeatedly.
Military service taught me that leadership under real stakes is different from leadership in comfort. I bring that calm under ambiguity into every high-pressure product sprint, stakeholder conflict, or resource crisis.
These aren't theories. They're field-tested methodologies I developed across real projects — frameworks that kept being used by teams long after I moved on.
Most research methodologies are designed for waterfall projects — they generate findings after the work is done. This methodology was built specifically for Agile environments, generating actionable findings within each sprint cycle, not after them.
Stakeholders don't have time for 40-slide decks. This readout framework distills research findings into a format that executive stakeholders can absorb in 10 minutes and act on immediately. It's also a training tool — I've used it to teach dozens of researchers how to present findings effectively.
Managing 12 direct reports across 5 projects simultaneously required a system that ensured no one fell through the cracks. My 1:1 structure balances project check-ins with individual development — so conversations never default to status updates at the expense of growth.
After working across 8+ regulated industries, I've accumulated a mental model of what design patterns succeed under compliance constraints — and which ones break. This cross-industry perspective is one of the most tangible things I bring into a new engagement from day one.
I've mentored and trained UX practitioners — researchers, designers, and usability experts — across six countries. Not virtually. In the room, on the project, under real deadlines.
This global experience shapes how I lead: I've navigated cultural differences in feedback styles, professional communication norms, and expectations around hierarchy. A good framework works in Bucharest and Bangalore as well as it does in Baltimore.
Below are screenshots from projects where I was leading, training, or mentoring team members. Drop in your actual project screenshots here — whiteboard sessions, workshop photos, team readouts, or research sessions.
📎 Artifact Placeholder
Insert 4–6 screenshots from team projects, whiteboard sessions, research readouts, or mentorship workBefore UX, I was a 19D Cavalry Scout in the U.S. Army — a reconnaissance role that demands leadership above your grade, decision-making under incomplete information, and the ability to keep people focused and functional under real pressure.
I served on a Police Mentor Team instructing U.S. Soldiers and Afghan police forces. I was routinely entrusted with responsibilities significantly above my grade level — leading teams on critical missions and receiving commendations for leadership performance.
That's not background color. That's where I learned that leadership isn't about authority — it's about preparing people to perform when it matters.
19D Cavalry Scout · Reconnaissance · U.S. Army · 2002–2010 · Police Mentor Team · Afghanistan
January 2002 to March 2010 — active duty
Cavalry Reconnaissance — operated above grade level
Leading through ambiguity is the foundation of how I manage teams
Developing people is a mission, not a HR task
I'm open to roles where UX leadership, team building, and strategic design matter as much as pixel-perfect output.