How I Work

These are the principles that guide every engagement. They're not aspirational slogans; they're commitments I hold myself to. If you work with me, this is what you can expect.

Standards & Ownership

Own It

When I take something on, I'm accountable for the outcome, not just the effort. That means following through, following up, and never leaving something half-done or hoping someone else picks it up.

Early in my career, I was the only person standing in front of the problem. There was no escalation path, no one to hand it off to. That forged something in me that never went away. When I take on work, I own it completely: the outcome, the follow-through, and the follow-up. No finger-pointing, no excuses. If something isn't right, I'll be the first to say so and the first to fix it.

Raise the Standard

I can't always control what things cost, but I can always control the quality and value of what I deliver. I hold myself and everyone I work with to an exceptionally high standard, because the people trusting us deserve nothing less.

I've never been able to accept mediocre work. From my very first job, I couldn't control what customers were charged, but I could control the quality and value they received. That's the lens I bring to every engagement. I hold myself and anyone I work with to an exceptionally high standard, not because perfection is the goal, but because the people trusting us with their business deserve our absolute best effort.

Player-Coach

I don't just direct the work; I do the work. Whether it's writing a policy, reviewing architecture, or troubleshooting alongside the team, I lead from the front because that's how trust gets built and real problems get solved.

I've never been the type of leader who delegates everything and waits for a status report. When the work needs doing, I'm in it: writing the policy, reviewing the architecture, troubleshooting the issue alongside the team. Leading from the front builds trust, keeps me sharp, and means my recommendations come from hands-on experience, not theory.

Communication & Clarity

Clear Is Kind

Direct, honest communication isn't harsh; it's respectful. I don't soften findings to spare feelings or bury critical issues in footnotes, because ambiguity wastes time, erodes trust, and helps no one.

Brené Brown said it best: clear is kind, unclear is unkind. I don't soften findings to spare feelings, and I don't bury critical issues in footnotes. Whether I'm presenting to a board or briefing a technical team, I communicate directly and plainly. Vague language creates confusion, and confusion creates risk. You'll always know exactly where things stand.

Bad News Travels Fast

Problems don't age well. The longer bad news sits, the worse it gets and the fewer options you have. When I find something that needs attention, I surface it immediately because I'd rather have an uncomfortable conversation early than a crisis later.

Problems don't age well. The longer bad news sits, the worse it gets and the fewer options you have. When I find something that needs attention, whether it's a critical vulnerability, a missed deadline, or a scope issue, I surface it immediately. I'd rather have an uncomfortable conversation early than a crisis later. That's not pessimism. That's respect for your ability to make informed decisions.

No Jargon Walls

Technology and security are complex, but that complexity is my problem to manage, not yours. If I can't translate a risk or recommendation into language that makes sense to the person who needs to act on it, I haven't done my job.

Technology and security are complex, but that complexity is my problem to manage, not yours. If I can't translate a finding, a risk, or a recommendation into language that makes sense to the person who needs to act on it, then I haven't done my job. I tailor every conversation to the audience, whether that's a CEO, a board, or a systems administrator.

Thinking & Problem Solving

First Principles

Too many decisions get made because 'that's how it's always been done.' I break problems down to their fundamentals and reason up from what's actually true. Starting from the foundation leads to better answers than layering new assumptions on top of old ones.

Too many decisions in technology and security are made because 'that's how it's always been done' or 'that's what the last consultant recommended.' I break problems down to their fundamentals before building solutions. What's actually true? What are the real constraints? What does the business actually need? Starting from the foundation leads to better answers than layering new assumptions on top of old ones.

Outcome Over Activity

It's easy to fill time with meetings, reports, and process; it's harder to stay focused on what actually moves the needle. I don't measure progress by hours logged or documents produced. I measure it by whether the organization is in a better position than when we started.

It's easy to fill time with meetings, reports, and process. It's harder to stay focused on what actually moves the needle. Every action I take ties back to a result that matters to the business. I don't measure progress by hours logged or documents produced; I measure it by whether the organization is in a better position than when we started.

Right-Sized, Not Oversized

I've seen too many organizations get sold programs they can't staff, can't maintain, and can't afford. I build solutions sized for your people, your budget, and your risk profile, because a program that works on Monday morning beats one that only looks good in a presentation.

I've seen too many organizations get sold enterprise-grade programs they can't staff, can't maintain, and can't afford. A security program that looks impressive on paper but collapses under its own weight helps no one. I build solutions sized for your organization: your people, your budget, your risk profile. The goal is a program that works on Monday morning, not just in a presentation.

Leadership & People

Bring Out the Best

I've seen it over and over, people who didn't realize what they were capable of until someone invested in them, challenged them, and held them to a higher standard. Great leadership isn't about being the smartest person in the room; it's about creating the conditions where everyone can do their best work.

I've seen it over and over throughout my career, people who didn't realize what they were capable of until someone invested in them, challenged them, and held them to a higher standard. That's what I believe great leadership does. It's not about having the smartest person in the room. It's about creating the conditions where everyone in the room can do their best work and grow beyond what they thought possible.

Massive Action

Analysis paralysis kills more initiatives than bad decisions do. I believe in making informed decisions quickly, taking decisive action, and adjusting course as you learn. Waiting for perfect information while the world moves around you isn't caution; it's a risk in itself.

Analysis paralysis kills more initiatives than bad decisions do. I believe in making informed decisions quickly, taking decisive action, and adjusting course as you learn. Perfect information is a luxury you rarely have, especially in security. Waiting for certainty while the threat landscape evolves around you isn't caution; it's a risk in itself. Progress beats paralysis every time.

Hire Smarter Than You

Earlier in my career, I learned the hard way what happens when you don't build a team that's stronger than you are. The best leaders surround themselves with people who are better than them in their respective domains. Your job isn't to be the smartest person on the team; it's to build the smartest team.

Earlier in my career, I made the mistake of not hiring people with deeper technical skills than my own, and I paid for it by constantly falling back on my own abilities instead of building a team that could operate beyond my reach. That lesson stuck. The best leaders surround themselves with people who are better than them in their respective domains. Your job isn't to be the smartest person on the team. Your job is to build the smartest team.

Character & Integrity

Do Right By People

Too many technology professionals use their knowledge to get ahead at the expense of their customers. I use what I know to help people make better decisions, not to create confusion or dependency, rooted in the values of faith, family, and service that guide everything I do.

Too many technology professionals use their knowledge to get ahead at the expense of their customers. That doesn't sit right with me; it never has. The people I work with are smart, capable, and deserving of honest guidance. I use what I know to help them make better decisions, not to create confusion or dependency. This is rooted in the values that guide everything I do: faith, family, service, and treating people the way I'd want to be treated.

Disagree and Commit

If I see a decision heading in a direction I believe is wrong, I'll say so, clearly and respectfully. But once we've had the conversation and a direction is set, I commit fully. Candor before the decision, commitment after it.

If I see a decision heading in a direction I believe is wrong, I'll say so, clearly and respectfully. That's what you're paying for. But I also understand that not every decision is mine to make. Once we've had the conversation and a direction is set, I commit fully. No passive resistance, no 'I told you so' if things get hard. Candor before the decision, commitment after it.

Sound like a good fit?

If these principles resonate with how you want to work, let's talk.