These principles were shaped through real support operations work and now serve as the foundation for Support Ops One.
Failures at the agent level are often failures in leadership, hiring, onboarding, systems, or enablement.
Strong support organizations don't build teams around rigid rule-following. They build teams around judgment, context, and continuous learning.
- Hire and onboard for judgment, not rule-following.
- Diagnose before prescribing.
- Build career capital, not just job skills.
- Great support talent should be developed, not controlled.
- Long-term success comes from building strong people, not simply enforcing stronger processes.
A pyramid is only as tall as its base is wide. The broader the knowledge foundation, the stronger the support organization.
Knowledge powers:
- Agent confidence
- AI accuracy
- Self-service
- Consistency
- Scale
Knowledge is not optional. Every interaction is an opportunity to improve the system. Capture it. Improve it. Scale it.
AI is a copilot, not the pilot.
Its job is to:
- Automate the repeatable
- Spot trends before they're obvious
- Suggest content, summarize context, and surface urgency
- Help people make faster, more informed decisions
- Provide insights, not just answers
Deflecting tickets is not the goal.
Helping humans do a better job is.
AI should create more time for judgment, empathy, problem solving, and meaningful customer conversations—not simply fewer conversations.
Support should feel effortless.
"Wow" moments don't matter if the baseline experience is broken.
Focus on:
- Removing friction
- Fixing repeat frustrations
- Simplifying customer journeys
- Designing clear paths to resolution
Pain is a signal.
Customers, support agents, and teams constantly reveal where systems are breaking down. Those signals deserve attention.
Data is valuable, but it is often a lagging indicator.
Support agents experience customer reality in real time. They see confusion, friction, bugs, and emerging trends long before most reports do.
- Use data to validate what people are already observing.
- Connect feedback, searches, escalations, and knowledge gaps.
- Use data to understand patterns over time.
- Use data to tell the story at scale.
But don't wait for a dashboard before taking action.
Waiting for metrics to spike is reactive.
Action starts with people, not reports.