"How big is your support team?" Wrong question. Here's what you should be asking instead: 'How effective is your support team?' After a decade+ leading support teams, here's what I've learned: Small teams can create massive impact ↳ It's not about headcount, it's about strategy Elite teams focus on leverage ↳ Tools + Training > More bodies Where smart leaders invest: • Upskilling their current team • Automating repetitive tasks • Building self-service solutions • Cross-functional collaboration • AI-powered efficiency The math is simple: 10 highly skilled agents + AI > 30 undertrained agents Real growth isn't measured in team size ↳ It's measured in customer outcomes ↳ It's measured in employee development ↳ It's measured in operational efficiency Stop trying to build the biggest team. Start building the most impactful one. P.S. What's one way you've helped your team do more with less? Drop it in the comments 👇
Totally agree—impact > size every time. We’ve embraced AI to handle repetitive tasks, freeing our team to focus on complex problems that drive real value. Pairing this with upskilling has transformed both customer outcomes and team morale. It’s not about adding headcount—it’s about building capability.
💯 agree! You don't always need to scale linearly if you're smart about truly understanding the needs and expectations of your customers and team, leveraging technology in the right way, and embracing constant innovation, learning, and iteration. I've experienced the power of what smaller teams can achieve if you invest in them, give them opportunities to grow, and promote collaboration, married to strategies for scaling Support exponentially. For example, aside from harnessing Salesforce Einstein AI solutions and a chatbot, my team and I implemented CX methodology to scale without adding headcount. We conducted research, competitive and data analysis, and mapped the customer journey to truly understand and solve pain points from both customer and team perspectives. These deeper insights enabled us to partner cross-functionally, gain buy-in, and create holistic targeted solutions within and outside the product that improved both the customer experience and operational efficiency. None of us had experience with CX methodology, but we grew as a team and researched, trained, practiced, and rolled it out operationally. By adopting this strategy, we successfully reduced case volume by over 23% and achieved significant scalability!
The size says nothing. The type of leader you are is not dependent on size but EFFICACY! Love this post!
I ended up pivoting my career to content after seeing the value (and impact) of self-serve resources and proactive communication with our users. Investing in content goes a really long way in providing more seamless user experiences, more resources for internal teams (more than just support!), AND better training for machine learning tools just to name a few 😊
Great points! It’s a timely reminder for those finalizing budgets!
At Itetable we had planned off days in the queues. This might sounds counter intuitive but giving people off days actually help them learn new skills, work on projects and clean up their queues.
Love this post @kenji! It’s about operational efficiency..
This is important. I've been on teams of 300+ and teams of 2 doing support. the right people the right tools the right metrics = the outcomes you need to succeed.
Well said! I am big on upskilling the team and providing career growth opportunities while driving efficiency!
I’m always looking at where their time is spent, and what they hate doing, and try to focus on reducing those. How can we better provide self-service / clarify the product, automate those busy tasks, train/educate on tasks that take the team a lonnngg time to deal with. I haven’t gone past a Support Team of 3, and am even thinking 4 will be over-staffing it because we focus so much on reducing the load. It’s not about throwing bodies at the problem. It’s about consistently structuring unstructured problems, going from unstructured > semi-structured > structured > automated > and getting better and better at repeating that process for each problem. Here’s the way I look at how my team spends their time: (and the yellow arrows are how we improve each step) Great call out Kenji Hayward !!