Support Leadership Philosophy

Support, operations, and the work behind better customer experiences.

I have spent most of my career in and around customer support organizations: service centers, regulated operations, high-growth technology teams, global support models, vendor partnerships, workforce planning, tooling, automation, and the day-to-day reality of leading teams under pressure.

The resume covers the titles and outcomes. This page is meant to explain how I think about the work.

Contact Visit the Lab

I see support first as a service function. Customers need clear, timely help from people and systems that understand what they are trying to do. But when support is working well, it is also one of the clearest signals a company has about where customers are meeting friction, where workflows are breaking down, and where the business is creating avoidable work for itself.

Support should not try to become everything. Not every customer issue is a strategic insight. Not every escalation belongs upstream. But repeated friction, preventable demand, unclear policy, weak handoffs, or broken workflows should not live only inside a queue. Good support leadership helps separate noise from signal and turns that signal into something the business can actually use.

Service First

Support has to deliver clear, timely, useful help before it earns permission to be strategic.

Signal Over Noise

Recurring friction matters when it is structured, repeated, tied to impact, and useful to partner teams.

Standards With Context

Good teams need expectations that are real, visible, and applied with judgment rather than fear.

How I Think About Support

Support and customer experience are closely linked, but they are not the same thing. Customer experience is the broader journey a customer has with the business. Support is one part of that journey, and often the point where underlying problems become visible.

Support shapes the experience through speed, clarity, empathy, ownership, and resolution quality. But it does not control the full experience on its own. Product design, policies, billing, onboarding, communication, operational decisions, and the basic ease of doing business all shape what customers feel before they ever contact support.

The healthier model is that support owns the quality of the support experience while also acting as an informed partner in improving the broader customer experience.

How I Lead

People who have worked with me would probably describe me as a coach first. I care about helping people understand their strengths, their growth areas, and what strong performance actually looks like. I want people to leave stronger than they were when I started leading them.

That does not mean lowering the bar. Standards matter. People should know what is expected, how performance is measured, and what the team needs to rely on from one another. But accountability should not feel like a surprise or a threat. Healthy accountability is clear, timely, specific, and tied to something a person can understand and act on.

The standard can stay consistent while the leadership approach remains human.

How I Think About Operations

A healthy support operation usually feels predictable. Not because nothing goes wrong, but because people understand how work enters the system, how it is prioritized, who owns it, what happens when it gets stuck, and how decisions get made when something falls outside the normal path.

An unhealthy operation feels reactive all the time. Work sits in the wrong places. Escalations happen too late or too often. Managers lack visibility until the problem is already obvious. Teams compensate for broken workflows with effort, stress, and informal workarounds.

To me, scalable support is not just support with more headcount. It is a model that can absorb growth, complexity, and change without becoming more chaotic every time demand increases.

Metrics, AI, and Judgment

Metrics matter. SLA, CSAT, QA, backlog, response time, resolution time, productivity, forecast accuracy, staffing efficiency, and cost-to-serve all tell part of the story.

But metrics are not the whole story. They usually point to symptoms. A number can tell you that something changed. It does not always tell you why. The work is understanding what sits behind the number and whether the answer is coaching, staffing, workflow design, tooling, automation, policy change, or clearer expectations.

I think about AI and automation the same way: useful, important, and worth investing in, but not a philosophy by themselves.

Where AI Helps

AI can help with intake, triage, routing, knowledge surfacing, summarization, suggested responses, quality review, and repeatable resolution paths. Internally, it can help agents move faster and reduce manual work.

Where leaders need to be careful is trust. If a customer feels stuck, misrouted, ignored, or trapped in an automated path, the tool is no longer helping. It is part of the problem.

The best AI work in support improves access, consistency, and leverage while keeping humans focused on work that still requires judgment, empathy, risk awareness, and exception handling.

What I Have Learned

Regulated environments taught me discipline: documentation, consistency, control, risk awareness, and the importance of doing things the same way for the right reasons.

Startups and scale-ups taught me adaptability: building while moving, making decisions with incomplete information, creating structure where little exists, and changing the model as the business changes.

The best support operations need both. Too much rigidity and the team cannot adapt. Too much improvisation and the operation becomes unstable.

The Kind Of Work That Fits

I tend to do my best work in environments that are serious about improving how support operates. That can mean better tooling, clearer processes, stronger manager routines, more thoughtful workforce planning, responsible automation, better escalation paths, or a more mature support model.

I can work in companies where support is already respected, and I can work in companies where support has mostly been treated as cleanup. What matters is whether there is some openness to improving how things work.

Running a solid operation matters. But I am most engaged when there is also a meaningful opportunity to make the operation stronger for customers, for the team, and for the business.

I care less about looking sophisticated than about building something a team can actually run.

If this way of thinking is relevant to the kind of support organization you are building, I am open to a practical conversation.

Start a Conversation