Change is inevitable, but change without context is chaos.
In support operations especially, things are always changing: new tools, new processes, new client needs, new expectations. Telling people to just “get comfortable with change” does not make them feel safe.
What does make a difference is helping people understand why things are changing, what the team is trying to accomplish, and how they can be part of building the solution.
A winning team is not built by expecting people to have every answer. It’s built by making it safe for people to notice problems, bring forward ideas, test solutions, learn when something does not work, and try again.
The people excited to change and grow are already on your team; you just have to recognize them, give them permission, and support them.
When someone comes to you excited about an idea, your response matters a lot. They might ask you to review a deck, a document, a ClickUp task, or a proposal. It’s easy to say, “I’ll look at it tomorrow,” get busy, and never come back to it. But that sends a message (even if it’s unintentional): your idea is not important.
Instead, take the time to ask questions. What problem are they trying to solve? Why do they think this could work? What would it take to test it? Even when an idea isn’t quite right, curiosity creates space for people to keep contributing. It tells them that their perspective matters.
One way to make that consistent is through regular career conversations, separate from normal one-on-ones. Ask the same questions every month: What is working? What is not working? Who on the team may be struggling? What do you want to learn over the next four weeks?
Repeating these prompts gives people a predictable space to share what they see and where they want to grow.
Not every idea needs to become a company-wide rollout. Small bets are welcome. If a new approach is too risky to put in front of 10,000 customers, try it with 200. Pilot it. Watch what happens, and then adjust. The goal is not to avoid failure; it is to make failure useful.
When something ends up not working, the response shouldn’t be, “You shouldn’t have done that.” It should be, “What did we learn, and what will we try next?” That shift turns improvement into a shared team responsibility instead of an individual risk.
Leaders can also help people move from ideas to ownership by asking, “What help do you need to implement this?” Sometimes the answer is a budget process, a new skill, or access to the right people. Supporting someone does not mean taking the idea off their plate, it means helping them build the confidence and capability to carry it forward successfully
Continuous improvement or learning and development can’t be treated like an optional side project people are supposed to squeeze in between everything else.
If growth matters, make intentional room for it. Set aside time for people to learn a new tool, deepen their knowledge of workforce management, build skills for the next level of support, or develop in areas that will help them take on more responsibility. That investment sends a clear message: improvement is part of the work. It is not extra credit.
People watch how leaders respond to ideas, learning, and mistakes. They notice when follow-through happens, and they also notice when it does not. If someone repeatedly hears, “I’ll review that Friday,” but never receives feedback, they learn that bringing ideas forward is not worth the effort.
If they are met with questions, support, and real engagement, they learn that this is a safe place to build and collaborate.
When results improve, it can be tempting to check the box and move on. CSAT goes up. Resolution time goes down. QA improves. Great. Next item. But skipping the celebration sends a message, too: improvement is just the baseline, and no one did anything special.
Recognition helps make improvement visible and repeatable. There are three easy ways to celebrate a win:
At Boldr, quarterly spotlight awards create another opportunity to recognize people through feedback from their peers, teams, and clients. Recognition also doesn’t need to be public to matter. Sharing a client’s positive feedback directly in a one-on-one can be just as meaningful.
Celebration spreads behavior. When people see that thoughtful ideas, experimentation, collaboration, and persistence are recognized, they are more likely to bring those same things forward.
Sometimes people leave because of compensation but often, they leave because they don’t feel seen. They don’t feel that their contributions matter. They feel that their ideas go nowhere, their work is uncredited, or change keeps happening without explanation.
Retention is a culture problem before anything else.
People want to work somewhere they can grow, try new things, recover from mistakes, and succeed alongside a team that notices their effort. They want to know that when they bring an idea forward, someone will listen. They want to feel that success is shared and that failure is something the team can learn from together.
The work isn’t complicated, but it does require intention: give people context, invite their ideas, create room for small bets, support their learning, and celebrate the people building alongside you. That is how you create a team people want to stay with and grow with.