Kelly Has Thoughts.

For many years, I was the backup plan.

I was the person who knew where everything lived, remembered why the process worked the way it did, and could be trusted with one more thing when the day started falling apart. If someone needed coverage, I stepped in. If a project didn’t have an owner, I took it. If a new employee needed training, I trained them. If a report was broken or an important assignment needed to cross the finish line, people knew they could hand it to me.

And I would get it done.

I’m proud of that. I earned the reputation of being dependable because I was dependable. I cared about the quality of my work, learned quickly, and didn’t need someone standing over me to make sure I followed through.

That reliability created opportunities. It helped me build relationships across departments, develop skills beyond my job description, and become the subject matter expert, trainer, problem-solver, and right-hand person people came to when they needed an answer.

A significant part of my career was built by saying, “I can take care of that.”

But there’s a point where being trusted with important work can quietly become being used as the solution to every gap. The employee who’s always willing gets asked first. Then they get asked most often. Eventually, people stop asking and start assuming.

Of course she can cover it. Of course she knows the answer. Of course she’ll stay late. Of course she can train the new person, fix the report, handle the escalation, finish the project, and still meet every expectation attached to her actual job.

She always does.

At first, that level of trust feels like recognition. Sometimes it genuinely is. Strong employees want meaningful responsibility. We want to be challenged, included, and trusted with work that matters.

But more work isn’t always development, and dependency isn’t the same thing as recognition.

I know what it’s like to be given responsibilities beyond my title without the authority that should accompany them. I know what it’s like to carry institutional knowledge no one has made an effort to document or distribute. I also know how flattering it can feel to hear, “You’re the only person I trust with this.”

And how heavy that compliment becomes when you hear it often enough.

Being that person taught me how to operate under pressure, solve unfamiliar problems, communicate across teams, recognize patterns, and create structure where none existed. Those experiences helped make me the leader and operator I am today.

They also taught me what happens when a business repeatedly rewards competence with more work.

The employee becomes essential, and being essential starts to feel a lot like being stuck. Their reliability becomes the reason they can’t be moved, promoted, or allowed to step away. The business benefits from everything they know, but no one makes a serious effort to transfer that knowledge or develop someone else who can carry part of the load.

That experience shaped the leader I became.

When I started leading teams of my own, I understood why managers repeatedly turn to the person who always delivers. When the stakes are high and the timeline is short, choosing your strongest employee feels responsible.

But because I had been that employee, I learned to ask a different question:

Am I giving this person an opportunity, or am I making them responsible for compensating for weaknesses in the operation?

An opportunity gives an employee visibility, authority, support, and a chance to build a skill they can carry forward. An obligation is the thing they keep receiving because everyone knows they’ll handle it without creating another problem.

The difference isn’t always the assignment itself. It’s what surrounds it.

Did the employee choose it? What’s being removed from their plate to make room? Will they receive credit? Are they being given authority equal to the responsibility? Will the work help them move forward, or does it only help the business survive another week?

My experience also made me deliberate about giving people credit. I know what it’s like to contribute the idea, solve the problem, or complete the work without having your role fully recognized. As a leader, I wanted the people doing the work to be visible. I wanted executives to know their names, understand their contributions, and see what they were capable of becoming.

I didn’t want to keep talented people hidden simply because they made my job easier.

Your strongest employees aren’t always the ones who will tell you they’re overwhelmed. They’re often the ones who figure it out, reorganize their priorities, and keep delivering because being dependable has become part of who they are.

I recognize that instinct because I still have it. When I see something without an owner, my first reaction is to take responsibility for it. That instinct has made me a strong operator and a leader who knows how to move work forward.

But capable people still have limits.

If the most important work always goes to the person who can do it fastest, no one else develops the same knowledge or confidence. Then, when that employee takes time off, gets promoted, or leaves, everyone discovers how much of the operation lived inside one person’s head.

That isn’t a succession plan. It’s a single point of failure disguised as a high performer.

Strong employees should be challenged, but they should also be developed beyond the role of permanent rescuer. That means cross-training, documenting processes, rotating responsibilities, and helping people grow into their next opportunity instead of making their current value the reason they can never leave.

Most importantly, it means recognizing that their value isn’t limited to how much they’re willing to carry.

I’m proud that I was the person people trusted. I’m proud of the reputation I built, the problems I solved, and the number of times I helped steady the room when something went sideways.

But those experiences also showed me the kind of leader I wanted to become: one who recognizes the person quietly holding everything together, gives them credit instead of only giving them more work, and never mistakes their reliability for permission to make them responsible for everything.

My experience as the backup plan made me a stronger employee.

Learning what it cost made me a better leader.

Your best employee should be part of your succession plan, not your contingency plan.

There. I said the quiet part out loud.

I’m bad at interviewing.

That’s a strange thing to admit publicly while actively searching for a job. Every piece of career advice tells you to project confidence, lead with your strengths, and never give someone a reason to doubt you.

But it’s true.

I spent most of my career at the same company. After a while, I didn’t have to sell myself anymore. My reputation preceded me, and my work spoke for itself.

I was the subject matter expert. The right-hand person. The go-to. The one whose plate could always hold one more thing because everyone knew I would get it done, and I would get it done right.

If there was a problem without an owner, I owned it. If something needed to be built, fixed, organized, or explained, people knew they could bring it to me. I didn’t have to describe how I handled pressure, earned trust, or solved messy problems. The people around me had watched me do it for years.

I earned new opportunities because someone had already seen what I was capable of. They knew how I worked when things went wrong. They knew I could manage competing priorities, have difficult conversations, and follow through without being chased.

My work was the interview.

When I left that company, I moved into a role where relationships once again helped open the door. It was a small organization of about 35 people, and I already knew roughly 15 of them.

I’m not going to pretend that didn’t help me get my foot in the door. It did.

But relationships may open a door. They don’t do the work for you once you walk through it.

I earned the trust of my clients and executives. I built relationships with my peers. I learned how to translate between clients and developers, turn unclear requests into actionable work, and protect technical teams from being pulled into conversations or responsibilities that didn’t require their expertise.

I took ownership of difficult situations, recovered projects, rebuilt client confidence, and made myself useful.

People who knew me gave me an opportunity. What I did with that opportunity belonged to me.

When that role changed and I chose to leave, I entered completely unfamiliar territory.

For the first time in a very long time, I had to convince complete strangers to take a chance on me.

And honestly, it hasn’t been easy.

An interview asks me to take more than a decade of work, judgment, relationships, decisions, failures, growth, and results and package it into a few polished answers for someone who has never seen me operate.

Tell me about yourself.

What’s your leadership style?

Tell me about a challenging situation.

Why should we hire you?

I know the answers to those questions. I’ve lived them.

But knowing the answer and delivering it neatly in two minutes are very different skills.

My brain doesn’t always retrieve the perfect story on demand. Sometimes I give too much context because the context mattered. Sometimes I answer the question I think someone is asking instead of the exact one they asked. Sometimes I remember the strongest example fifteen minutes after the conversation ends.

Sometimes I leave an interview knowing I showed them only a fraction of who I am at work.

That’s the frustrating part.

I wish I could walk into a business and do the job for one week. Give me the customers, the employees, the backlog, the unclear process, the unhappy client, or the problem everyone has learned to work around.

Let me listen. Let me ask questions. Let me find the pattern. Let me create some structure, take ownership, and make something easier than it was when I arrived.

At the end of the week, the hiring manager could ask themselves one question:

Would we like to keep her?

I genuinely believe that 9.5 times out of 10, the answer would be yes.

That isn’t arrogance. It’s confidence built from evidence.

I know how I show up once I’m inside the work. I know the trust I’ve earned from employees, peers, clients, and executives. I know how often “Can you help with this?” became “Kelly will handle it.” I know what I’ve built when no one handed me a playbook, and I know how many problems stopped being problems because I took responsibility for them.

But hiring managers don’t get to watch me work for a week before making a decision.

They have a résumé, a conversation, and maybe an hour of my time. It’s my responsibility to help them see the evidence clearly enough to imagine what I could do for their team.

That’s the part I’m still learning.

For years, I thought being good at my job should be enough. I’m realizing that communicating what makes me good at my job is a separate skill, and like every other skill I’ve developed, it requires practice.

So I’m practicing.

I’m learning how to tell a ten-year story without telling every part of it. I’m learning to trust that a concise answer can still be an honest one. I’m learning to lead with the outcome instead of making someone travel every step of the journey with me.

I’m learning that talking about my accomplishments isn’t bragging when I can explain the work behind them. I’m learning that the things that felt like “just another Tuesday” to me were often evidence of leadership, judgment, resilience, and skill.

Most importantly, I’m learning that struggling to interview doesn’t mean I’m unqualified for the job.

It means I’m still learning how to translate the employee I know myself to be into something a stranger can recognize in one conversation.

I don’t know whether I’ll ever become the person who finishes an interview and thinks, “I absolutely nailed that.”

Maybe I will.

For now, I’m trying to become someone who walks away knowing I gave them an honest, clear picture of what I can do.

I may not always be the most polished person in the interview.

But give me the work, and I’ll show you why I deserved to be in the room.

Some of the most valuable work I’ve done in my career started with something no one asked me to do.

Our frontline contact center had launched a customer satisfaction survey. At the end of an interaction, agents transferred customers directly to the survey, giving us a new way to measure how people felt about their experience.

We had the scores. What we didn’t have was a meaningful process for learning from them.

When an agent received a low score, the response was usually individual coaching. Review the call, talk to the employee, remind them of the expectations, and encourage them to get better scores.

That wasn’t necessarily wrong. Sometimes the agent genuinely had handled the interaction poorly and needed feedback.

But “get better scores” isn’t a strategy.

A number can tell you that a customer was unhappy, but it can’t tell you why. It can’t tell you whether the employee lacked knowledge, whether the workflow failed them, whether a policy created unnecessary frustration, or whether the customer received the correct answer and simply didn’t like it.

Without that context, we were treating every low score like an agent performance problem.

Meanwhile, my escalation team was seeing a very different side of the customer experience. When a frontline conversation went south, my team took the call. They spoke with the customers who were still frustrated after the first interaction and were often responsible for untangling whatever had happened before the transfer.

Over time, they started noticing patterns. Certain agents transferred far more customers than others. The same types of complaints kept reaching us. Some policies were repeatedly misunderstood. There were situations frontline employees could’ve resolved themselves if they’d had better information, clearer authority, or a more effective escalation process.

We tracked our customer interactions so we could report on those trends at the end of each month, but our data had a significant blind spot.

Customers could only complete the satisfaction survey when their interaction ended with a frontline agent. If the customer was transferred to my escalation team, the original agent’s call was no longer represented in the survey results.

That meant we had two incomplete pictures. The survey captured customers who ended their calls with frontline employees, including low scores we weren’t investigating deeply enough. My team captured escalated complaints, including patterns the survey couldn’t show us at all.

The information existed. We just hadn’t connected it.

Once I saw that gap, I couldn’t unsee it.

We were sitting on an enormous amount of customer feedback and using only the number at the end. We were telling agents to improve their scores without consistently determining what had caused those scores. We were hearing recurring complaints in escalations without knowing how widespread they really were.

No one asked me to build a Voice of the Customer team.

I built one because the business needed it.

I selected two of my strongest employees and created a process specifically for them. Each day, they reviewed the lowest-scoring calls from the previous day and listened for more than whether the agent had sounded friendly.

They determined what had actually happened. Was it an agent behavior issue? Was there a knowledge or training gap? Had a poor escalation workflow made the interaction harder than it needed to be? Was a process creating unnecessary friction? Or had the employee handled the call appropriately, but the customer was simply unhappy with the policy?

Those distinctions mattered.

If an employee had been dismissive, impatient, or unwilling to help, that required coaching and accountability. If several capable employees were giving the same incorrect answer, that pointed to a training or knowledge problem. If customers repeatedly became frustrated at the same point in a process, we needed to examine the process. If the call had been handled correctly and the customer simply disagreed with the policy, coaching the agent to “get a better score” wasn’t going to solve anything.

The research gave us a much clearer picture of what our customers and employees were actually experiencing. It also challenged some of our assumptions.

Before the VoC team, it was easy to believe that the complaint we heard most loudly was the issue causing the greatest harm. Once we had structured data, we could see which problems were truly recurring, which affected the most customers, and which created repeat contacts or unnecessary escalations.

We also uncovered inefficiencies in processes we thought were working.

Employees had learned to navigate around those problems, so they weren’t always reporting them. The work still got completed, but it took longer, required extra steps, or pushed customers into another contact they shouldn’t have needed to make.

From a distance, the processes appeared functional. The calls told us otherwise.

The reviews also identified employees whose behavior wasn’t aligned with the experience we wanted to provide. These weren’t isolated low scores from customers who disliked an answer. They were patterns of incomplete assistance, poor communication, avoidable transfers, or a lack of ownership.

The goal was never to use customer feedback as a weapon against employees. It was to stop guessing.

The VoC team wasn’t only responsible for analyzing calls. They also closed the feedback loop with the customer. If we could resolve the original concern, we did. If we couldn’t change the outcome, the customer still received a call acknowledging that we’d heard their complaint and were addressing what had happened internally.

That mattered to me. A survey shouldn’t feel like a message sent into a void. If we ask customers to tell us about their experience, we should be prepared to do something with the answer.

Building the team required more than assigning two employees to listen to calls. I created the training materials that defined how I wanted them to present themselves when contacting customers. I developed the process for dividing the work, tracking each review, documenting findings, and submitting recommendations for process or knowledge changes.

I also created QA rubrics for their interactions and reviewed their work to ensure the team was delivering the same level of quality we expected them to evaluate in others. I established weekly and monthly reporting so the findings could move beyond our team. We tracked patterns, shared progress, and made recommendations grounded in evidence instead of anecdotes.

Eventually, I presented the team’s work and its results at our P&L meeting.

The impact was measurable. The insights helped us improve workflows, strengthen training, update knowledge resources, and address performance issues with greater accuracy. Repeat contacts decreased by approximately 20 percent. Frontline CSAT improved by 11 percentage points, and quality scores increased by four points.

But the outcome I’m proudest of isn’t a single metric.

We changed what customer feedback meant inside the operation.

It was no longer just a score attached to an employee. It became a source of operational intelligence that helped us understand where customers were struggling, where employees needed support, where processes created friction, and where the business needed to change.

That team existed because I noticed something valuable was being missed and decided to build a solution.

I wasn’t assigned a Voice of the Customer program. There wasn’t a finished playbook waiting for me. No one handed me a project plan or told me exactly what success should look like.

I saw disconnected information, created a structure around it, chose the right people, trained them, measured the work, communicated the findings, and turned those findings into action.

That experience changed how I think about the value we bring to our jobs.

Doing what’s asked of you matters. Reliability matters. Execution matters. Every business needs people who can take responsibility for an assignment and deliver it well.

But that’s only one kind of value.

The other kind begins with curiosity. What are we missing? What are customers telling us that we haven’t learned how to hear? Which problems have become so normal that no one thinks to question them anymore? What could be better, even if no one has formally assigned someone to improve it?

The people who create lasting value aren’t always the ones completing the most tasks. Often, they’re the ones who notice the problem hiding between those tasks. They bring ideas. They pursue passion projects with legitimate business purposes. They build the processes that don’t exist.

Then they do the less exciting work required to make those ideas credible. They document them, train people, measure the results, improve the process, and prove that it works.

An idea alone isn’t impact.

The value is in seeing what’s missing and caring enough to build it.

Throughout my career, I have worked for plenty of different types of leaders.

Some were warm and collaborative. Some were direct and demanding. Some gave me room to operate independently, while others wanted to be involved in every detail.

One of the most valuable workplace skills I have developed is the ability to adapt to the person leading me. That has occasionally meant adjusting which parts of my personality show up most strongly each day. Sometimes I needed to ask more questions. Sometimes I needed to bring more structure. Sometimes I needed to speak up sooner, and sometimes I needed to listen longer.

That kind of adaptability becomes a natural part of surviving and succeeding in the workplace.

But I have also learned something else:

You can learn just as much from a bad manager as you can from a great one.

Early in my career, I worked for a manager who simply did not like me.

To this day, I cannot tell you exactly why. She never sat me down and explained that there was a performance issue or a behavior I needed to change. My metrics were consistently strong. I rarely missed work. I volunteered for extra projects, responsibilities, and hours.

Still, she made it clear that I was not her cup of tea.

She would ask me to complete a project and then present it as her own work without mentioning my contribution.

She once moved my desk while I was off, despite explicitly telling the team that no one would touch our personal belongings.

She would give me opportunities or privileges and then quietly take them away without speaking to me. I would find out when someone from another department called or messaged me.

“You’re not helping with training anymore?”

“I heard you were suspended from admin work. What happened?”

The problem was that I did not know what happened either.

There had been no formal conversation. No warning. No explanation. I was learning about decisions affecting my work and reputation from people who assumed I already knew.

It was embarrassing. It was isolating. And because none of it was ever addressed directly, I spent a lot of time wondering whether I was imagining it.

Maybe I was being too sensitive.

Maybe I was reading too much into things.

Maybe there was something wrong with me that everyone else could see and no one was willing to explain.

I kept working hard, partly because that is who I am and partly because leaving felt like admitting she had been right about me. Some days, it felt like I was staying out of spite. Other days, I thought that if I worked hard enough, I could finally prove whatever she believed about me was wrong.

Looking back, the only explanation that makes sense to me is that something about my work ethic, relationships, or ambition felt threatening to her. I do not say that to inflate my own ego. I say it because I cannot find another explanation for repeatedly hiding the contributions of an employee who was dependable, engaged, and eager to do more.

Still, I questioned my own perception until a new senior manager joined the organization.

She oversaw our department and became my manager’s manager. Not long after arriving, she asked why I was not in leadership.

She was told, “You don’t really know her. You would regret promoting her.”

Fortunately for me, she had one hell of a backbone.

She said she would take her chances.

She did not regret it.

I eventually became her right hand, and she became the best leader I have worked for to this day.

She gave me credit when I earned it. She gave me feedback when I needed it, both good and bad. She trusted me with meaningful work, challenged me to expand my skills, and told me directly when I needed to approach something differently.

She did not make leadership easy for me. She made growth possible.

The contrast between those two managers taught me more about leadership than any course ever could.

One showed me how deeply a manager can damage someone without ever writing them up, raising their voice, or formally declaring there is a problem.

The other showed me what can happen when a leader looks past someone else’s opinion and evaluates a person based on their actual work, character, and potential.

From one, I learned how important it is to give people credit.

I learned that feedback should be delivered directly, not communicated through removed responsibilities, whispered explanations, or conversations happening everywhere except with the employee.

I learned never to give someone an opportunity just so I could later use it as leverage.

I learned that uncertainty can be more damaging than difficult feedback because people will fill silence with their worst assumptions about themselves.

That experience is part of why one of my leadership philosophies is so simple:

Clear is kind.

Clear feedback may be uncomfortable. It may disappoint someone. It may require a conversation neither person particularly wants to have.

But it is far kinder than asking an employee to decode a disappearing responsibility, a changed relationship, or a decision everyone seems to know about except them.

People deserve to know where they stand. They deserve the opportunity to understand, respond, improve, or disagree. Silence does not protect them from the truth. It only leaves them alone with their imagination.

From the other manager, I learned the power of advocacy.

I learned what it feels like when someone sees potential in you before you are fully confident in it yourself. I learned that honest feedback and genuine support can exist in the same relationship. I learned that a strong leader does not need to hide talented people to protect their own position.

And I learned that sometimes one person’s opinion of you is simply that: one person’s opinion.

I want to be careful about the lesson here.

I am not saying people should remain indefinitely in workplaces where they are being mistreated. Staying worked out for me, but it could just as easily have continued costing me confidence, opportunities, and peace. No future possibility is guaranteed, and no employee owes an unhealthy environment unlimited patience.

What I am saying is that a bad manager does not have to be the only thing you take away from the experience.

You can learn from what hurt.

You can notice which behaviors made you question yourself and decide that the people you lead will never have to decode where they stand with you.

You can remember what it felt like to have your work hidden and become the leader who gives credit loudly.

You can remember what it felt like to hear about decisions from everyone except your manager and become the leader who has the direct conversation.

You can remember what it felt like to be dismissed and become the person willing to take a chance on someone else.

Both of those women shaped the leader I became.

One showed me the kind of leader I wanted to follow.

The other showed me the kind of leader I never wanted to become.

There are very few decisions I’ve made as a leader that I still think about years later. This is one of them.

I was managing a team of contact center agents who handled specialized escalations. These weren’t your average customer service calls. By the time someone reached my team, they were usually already angry, sometimes very angry. My team was trained to de-escalate, problem-solve, and absorb a level of frustration that I would never expect a frontline agent to handle.

One of my employees was going through a particularly difficult time with her mental health. She was open with me about it, and she was actively working on it. She wasn’t one of my highest performers, but she was solid. Dependable. Middle of the road in the most complimentary sense of the phrase. And she was trying.

One day, she took a call from an extremely angry customer. The customer was physically at one of our locations, so my employee was trying to coordinate a solution between him and the property manager who was there in person.

At some point, the interaction reached a boiling point. The customer began hurling racist insults at the property manager.

And something in my employee snapped.

She went off on him. She yelled. She swore. She was visibly and audibly angry. Everything we trained our escalation agents not to do, she did.

Then the call ended. She clocked out and immediately called me.

She didn’t wait to see if the call got pulled for quality. She didn’t hope the property manager wouldn’t report it. She didn’t try to soften what happened. She told me exactly what she had done.

She also told me that she had made an emergency appointment with her therapist and that she was taking herself out for the rest of the day because she didn’t want what had happened to bleed into another customer interaction.

And here is the part that might sound strange:

I was proud of her.

Not for screaming at a customer. Not for using profanity. Those things weren’t acceptable, and she knew that.

I was proud of the human being underneath the mistake. She watched another person being subjected to racist abuse and instinctively stood up for them. When she realized she had lost control of her emotions, she removed herself from a situation where it could happen again. She sought help. And when she had every incentive to keep quiet, she picked up the phone and told her manager the truth.

Then I had a decision to make.

I could handle the situation within my team, or I could report the interaction to HR. And if I am being completely honest about my reasoning at the time, part of my decision came down to protecting myself.

If someone else discovered the call later and learned that I knew about it and hadn’t reported it, what would that mean for me?

So I reported it.

I wrote up what happened. I attached the interaction. I documented what my employee had done immediately afterward, and I gave my recommendation: write her up. Make it serious. Make it clear that regardless of the circumstances, speaking to a customer that way could not happen again.

But don’t fire her.

HR disagreed. The decision was termination.

I remember sitting with my HR representative afterward. She asked whether I could deliver the termination or whether I wanted her to do it. I told her I didn’t agree with the decision, but I would do it. She reminded me that we needed to be on the same page when we spoke with the employee. I said I would support the decision that had been made.

And the next day, I fired her.

I have thought about that decision for years. Not because I think employees should be allowed to scream and swear at customers. They shouldn’t. Not because I think being provoked makes every reaction acceptable. It doesn’t. And not because I think I necessarily could have changed the outcome.

Maybe I couldn’t have.

What I regret is that I didn’t find out.

I gave my recommendation. HR made its decision. And somewhere in that process, I decided that being a good leader meant accepting the decision and presenting a united front.

Today, I think I confused alignment with advocacy.

I wish I had asked more questions. Why termination instead of a final warning? How much weight were we giving to the circumstances of the interaction? Did her history with the company matter? Did the fact that she immediately reported herself matter? Did recognizing that she was no longer in a state to work and proactively removing herself from the queue matter? Did seeking immediate help matter?

Did any of it matter?

And if the answer was still termination, I wish I had made someone explain to me why.

Maybe I would have walked out of that room with the exact same decision. Maybe I would have fired her the next day anyway. But I would know that before I asked one of my employees to live with the consequences of one of her worst moments, I had done everything I could to make sure the people making that decision saw more than those few minutes of a phone call.

I didn’t do that. I advocated for her once, and then I accepted the answer.

There is a version of leadership that gets praised a lot in corporate environments: disagree behind closed doors, then commit to the decision. There is value in that. Teams cannot function if every manager treats every decision they dislike as optional.

But I’ve learned there is another question worth asking:

Have I actually disagreed enough yet?

I know which one happened that day.

That’s why I still think about it.

I don’t regret reporting the call. I don’t regret recognizing that what happened required a consequence. And I don’t know that fighting harder would have changed what happened next.

I regret believing that reporting it meant my part in the decision was over.

If I could sit across from the manager I was then, I wouldn’t tell her to hide the call. I wouldn’t tell her to ignore what happened. And I wouldn’t tell her that consequences weren’t warranted.

I’d tell her one thing:

Fight harder.

Not because your employee is automatically right. Not because HR is automatically wrong.

Fight harder because you’re the person in the room who knows the whole story. And if the decision is going to change someone’s life, make damn sure the whole story gets heard.

A client once came to me with a clear request.

They knew what they wanted. They could explain why they wanted it. The work was important, and they wanted us to move quickly.

There was just one problem.

The solution they requested was going to cost them money twice.

The client was a personal injury law firm using Salesforce to manage cases that could remain active for months or even years. Those cases generated a lot of documents, and the people working them needed reliable access to everything their clients had provided.

Salesforce storage is expensive, so the CRM had been designed to move documents into Dropbox after 30 days. That allowed the firm to keep its storage costs under control while preserving the files for future use.

Financially, the process made sense.

Operationally, it was becoming a headache.

Attorneys and their teams did not always need a document within the first 30 days. A case might sit quietly for a while and become active again months later. When that happened, the file they needed was no longer available where they expected to find it.

The client wanted us to overhaul the entire archiving process.

From their perspective, that was the obvious solution. If employees needed easier access to documents, stop moving the documents somewhere else.

Simple enough.

I brought the request to the development team so we could understand what would be required. It quickly became clear that the project would be a much larger lift than the client probably expected.

That alone did not make it a bad idea. Large projects can still be worthwhile when they solve an important problem.

The bigger concern was what would happen after we completed it.

The client would pay us to rebuild the archiving process. Then, because more documents would remain in Salesforce, they would continue paying higher storage costs long after our work was finished.

They would be paying us to help them pay more.

Technically, we could have done exactly what they asked.

We could have scoped the project, estimated the hours, prepared the proposal, secured approval, and delivered a functioning solution. Everyone could have checked the appropriate boxes. The client asked for something, and we built it.

But completing a request is not the same as creating a good outcome.

The development team stepped back and looked at what the client was actually trying to accomplish.

They did not truly care where the documents were stored.

They cared that their attorneys and staff could retrieve those documents when they needed them without searching through multiple systems or asking someone else for help.

That was the problem we needed to solve.

The team proposed a much simpler option. Instead of rebuilding the entire archiving process, we could add a button within the documents section of the case. When an employee needed an archived file, they could use that button to retrieve it from Dropbox without leaving the workflow they were already using.

The documents could continue moving out of Salesforce after 30 days. The client could avoid higher storage costs. Their employees could access the files more easily. The development effort would also be significantly smaller.

Same business need. Better answer.

When I brought the alternative back to the client, I did not frame it as their original idea being wrong. It was not wrong. It was based on the information they had and the frustration their team was experiencing.

My responsibility was to give them the rest of the picture.

They chose the simpler solution, and it worked.

That interaction has stayed with me because it captures something I think gets lost in conversations about customer success.

We talk a lot about listening to customers.

We should.

We talk about responding quickly, removing friction, and making customers feel heard.

All important.

But sometimes we treat listening as though it means agreeing. A customer makes a request, we write it down, and the work begins. Saying yes feels helpful. Pushing back feels risky, especially when the customer is frustrated or the proposed work would generate additional revenue.

I do not think customer success is measured by how often we say yes.

It is measured by whether the customer succeeds.

Those are not always the same thing.

Clients are experts in their businesses. They understand their employees, customers, pressures, and priorities in ways an outside partner never fully will.

Technical teams bring a different kind of expertise. They understand the systems, dependencies, limitations, and consequences that may not be visible when a request is first made.

Someone has to connect those perspectives.

That was a large part of my role.

I did not need to be the person writing the code. I needed to understand the client’s experience well enough to explain what was getting in their way. Then I needed to understand the developers well enough to communicate their concerns and recommendations accurately.

There was usually some repeating back involved.

“So, what I hear you saying is…”

“Let me make sure I understand…”

“If we do this, what happens to that?”

I would rather ask the extra question and sound overly cautious than confidently carry the wrong information into the next conversation.

In this case, those questions helped us get past the requested feature and into the reason behind it.

That distinction matters.

If we only listen for what a customer wants us to build, we can miss what they are trying to fix. We may deliver beautiful work that takes too long, costs too much, creates another problem, or never gets used.

It may meet every documented requirement and still fail the people who needed it.

Good client leadership sometimes requires a little discomfort.

That is not resistance.

That is partnership.

The goal is not to win an argument or prove that the technical team knows more. The goal is to make sure the client understands their options and the consequences attached to each one.

They still own the decision.

My job is to make it an informed one.

That project did not succeed because we followed the request perfectly. It succeeded because the client, development team, and project leadership stayed curious long enough to find a better answer.

I will take that outcome over a larger statement of work every time.

Because customer success is not giving customers everything they ask for.

Sometimes, it is caring enough to ask what they are really trying to accomplish before anyone starts building.

One of the most important lessons I learned about leadership happened long before anyone considered me a leader.

I had just started my first call center job, working in customer care for a very well-known consumer-products company. If you have personal-care or home-care products in your house, there is a pretty good chance this company made at least some of them.

I worked specifically on the baby-care team.

Diapers and wipes. Exactly as glamorous as it sounds.

I became the subject-matter expert for those products. I knew the materials, sizes, features, common concerns, and troubleshooting questions inside and out. The complaints were usually predictable, the solutions were fairly consistent, and most conversations followed a familiar path.

A parent called with a concern. I asked the right questions, figured out what had happened, offered the appropriate resolution, and usually ended the call with a customer who felt heard and supported.

I liked being good at it.

I have always been a rule follower, especially at work. I want to understand what success looks like, and then I want to exceed it. A lot of my self-worth has always been tied to the work I do every day. Whether that is healthy is probably a different Kelly Has Thoughts post, but it is true.

I wanted the strong quality scores. I wanted my leaders to know they could depend on me. I wanted to be the person who understood the work better than anyone else.

But there have also always been lines I will not cross simply because someone with a higher title tells me to.

At one point, the company introduced a new initiative intended to create more personal connections with parents. If someone called with a complaint involving diapers in sizes newborn through size two, we were expected to ask how old the baby was and then bring up a developmental milestone the child may have reached.

“Are they noticing the ceiling fan?”

“Are they blowing bubbles?”

“Have they taken their first step?”

On paper, I imagine it sounded warm and thoughtful.

Someone was probably sitting in a meeting trying to answer a reasonable question: How do we make these conversations feel less transactional and more human?

The problem was that this idea did not account for all of the humans who might be on the other end of the phone.

Before I worked in a contact center, I spent time as a behavioral therapist supporting children with autism and other disorders or injuries that could benefit from applied behavior analysis therapy.

I had watched children miss milestones that other families might consider simple or automatic. I had seen the worry, grief, frustration, and sometimes devastation their parents experienced while waiting for progress that might come much later, or might look completely different from what they once expected.

So when I was instructed to casually ask parents about developmental milestones during a diaper complaint, I could not stop thinking about those families.

What was intended to be a friendly moment could become a painful one without warning.

A parent might be calling because a package of diapers leaked, and suddenly a stranger was asking whether their child had done something they had been desperately waiting, hoping, and working to see.

I was not going to do it.

I understood that refusing could affect my quality score. I understood that the question was now part of the expected call flow. I understood that following the process was part of my job.

I also understood that no quality score was worth knowingly creating pain for a parent just so I could check a box on a form.

I raised the concern with my leader. I tried to explain why the question could be harmful and why my experience made me uncomfortable asking it.

She was not interested in discussing it.

It was a corporate decision, and that was that.

At the time, I was a frontline representative at my first call center job. I did not have an impressive title. I did not have the authority to change the program. I was not in the room when the initiative was created, and I was not considered one of the people responsible for deciding whether it was a good idea.

But I had information the people in that room may not have had.

My concern did not come from negativity, laziness, or resistance to change. It came from experience. That experience had nothing to do with diapers and everything to do with understanding the person on the other end of the question.

That is the problem with treating decisions as though they should only travel from the top down.

Leadership may have the broader business strategy, but the people closest to the work have something equally valuable: proximity.

And sometimes, they bring experiences from entirely different chapters of their lives that allow them to see a consequence no one else considered.

None of that insight appears on an organizational chart.

A title tells us what authority someone has. It does not tell us everything they know.

When I eventually became a leader, I carried that call-center experience with me. I remembered what it felt like to raise a genuine concern and have it dismissed, not because the concern lacked merit, but because the decision had already come from somewhere higher.

I vowed that I would never put my team in that position without, at minimum, listening intently and trying to find another solution.

Listening does not mean leaders can always give employees the answer they want. Sometimes a policy cannot be changed. Sometimes the business need is real, the expectation is reasonable, and the employee still has to follow it.

But “this came from corporate” should never be the end of our curiosity.

And if the process truly cannot change, can I at least explain the reasoning, acknowledge the concern, and make sure the employee knows they were heard?

People do not need leaders to agree with them every time. They do need leaders who take them seriously.

The best ideas do not always begin in a conference room. The most important warning may not come from the most senior person in the building. A frontline employee, a new hire, or someone whose résumé looks completely unrelated to the current problem may be the only person in the conversation who sees what everyone else is missing.

Good leadership requires enough confidence to make decisions, and enough humility to recognize that wisdom can come from anywhere.

The people at the bottom of the organizational chart are not at the bottom of the value chain.

They are often the closest people to the customer, the process, and the consequences of the decisions being made above them.

If we want better ideas, stronger operations, and more human customer experiences, we cannot only invite feedback from the people with the biggest titles.

Sometimes the person with the least authority in the room has the perspective everyone else needs.

Burnout does not always arrive with an employee announcing that they are overwhelmed.

Sometimes, it looks like another absence.

Sometimes, it looks like a dip in customer satisfaction, less patience during a difficult interaction, or an employee who is technically doing everything correctly but no longer sounds like themselves.

And sometimes, when those signs begin appearing across an entire team, the answer is not another coaching conversation.

I led a team responsible for handling escalated customer concerns across multiple channels. By the time customers reached us, they were often already frustrated. My employees spent their days talking to people who were angry, disappointed, or demanding an outcome we could not always provide.

Being yelled at was not an unusual event. It was part of the job.

As leaders, we can acknowledge that reality without accepting that it should have no effect on the people doing the work. Employees can be skilled, resilient, and deeply committed to their customers, and still become exhausted from absorbing that level of emotion every day.

The work was made even more difficult by the constant switching between phone calls, emails, chats, social media conversations, research, documentation, and follow-up tasks. An employee might finish a tense phone call and immediately need to respond to an entirely different customer in writing, using a completely different tone and thought process.

There was very little room to breathe between one problem and the next.

Over time, I began noticing signs that the team was struggling. Absences were becoming more common, and our customer satisfaction results were not as consistent as I knew the team was capable of producing.

It would have been easy to view each absence as an individual attendance problem or every disappointing survey as a coaching opportunity. Accountability mattered, and individual performance still needed to be addressed when appropriate.

But the pattern was bigger than any one employee.

Before I asked the team to work harder, improve their attitudes, or become more resilient because "that's the job you were hired for", I needed to ask whether the way we had structured the work was sustainable.

It was not.

The employees needed time away from the constant stream of escalated conversations, but the business still needed coverage. I could not eliminate difficult customers, reduce our responsibilities, or simply take the team offline whenever the work became overwhelming.

So, I created a rotating admin day.

Once a month, each employee received a scheduled day away from the phones. We avoided the first and last weeks of the month because of business needs, and we rotated the days to protect service levels and ensure that everyone had the same opportunity.

This was not a day off.

It was protected time for employees to complete follow-up work, review cases, organize outstanding responsibilities, and focus without immediately being pulled into another emotionally demanding interaction.

More importantly, it gave them a chance to exhale.

The admin day was not a massive organizational initiative. It did not require expensive technology, a new department, or a complete redesign of the operation. It was a relatively small adjustment based on what the team was telling me, both through their words and through their performance.

But small operational changes can make a meaningful difference when they address the right problem.

The team felt heard and prioritized. Absences decreased. Customer satisfaction became more consistent, and our team average improved by approximately two percentage points.

That improvement mattered, but the lesson behind it mattered more.

The team did not suddenly become more capable because of one day away from the phones. They had always been capable. They needed a work environment that recognized what the job was asking of them and created enough space for them to keep doing it well.

Leaders are often expected to manage burnout by encouraging resilience. We remind people to take their breaks, use their time off, protect their boundaries, and practice self-care.

Those things have value, but they can also place the entire responsibility for surviving an unhealthy system on the employee experiencing it.

Sometimes, the leader needs to change the system.

That does not mean every performance issue is caused by burnout. It does not mean expectations disappear because the work is difficult, and it does not mean accountability becomes optional.

It means that before we decide an employee does not care, we should understand what is happening around them.

Good performance management requires us to look at both the person and the environment. If one employee is struggling, they may need clarity, coaching, resources, or accountability. If an entire team begins struggling in similar ways, leadership should be willing to look in the mirror.

The rotating admin day worked because it was not created around what I assumed the team needed. It was created from paying attention to what their behavior, feedback, and performance were already telling me.

Burnout does not always look dramatic.

Sometimes it looks like a good employee calling out more often.

Sometimes it looks like a strong team becoming inconsistent.

Sometimes it looks like people who still care deeply but have less and less of themselves available to give.

The responsibility of a leader is not simply to notice when performance changes. It is to become curious about why, and to be willing to change something when the problem is not the people, but the way we are asking them to work.

Some of the most important conversations we have as leaders do not feel particularly successful while they are happening.

A few years ago, I was coaching an employee who wanted to move into leadership. She was talented, hardworking, and more than capable of producing strong results. She had the ambition, and I could see the potential.

But there was something standing between where she was and where she wanted to go.

The way she communicated in group settings did not always land the way she intended. Her confidence could be perceived as dismissiveness. Her directness could make it seem as though she was unreceptive to other perspectives. Having many conversations with her, I personally knew that was not reflective of her intentions, but leadership is not judged solely by what we intend. It is also judged by how the people around us experience us.

I knew that if no one was honest with her about that disconnect, she might continue doing excellent work while wondering why the next opportunity never came.

So, we talked about it.

I connected the feedback directly to the future she said she wanted. I explained that being ready for leadership was about more than producing good numbers or knowing the work. People would also need to trust her, feel heard by her, and believe they could bring her a different point of view without being shut down.

She became defensive.

Honestly, I understood why. It is difficult to hear that the version of yourself you believe you are presenting may not be the version other people are receiving. She explained her intentions, challenged some of the feedback, and did not immediately agree with everything I said.

It would have been easy to soften the message until it no longer meant anything. It also would have been easy to become frustrated, label her as resistant to coaching, and end the conversation there.

I did neither.

Instead, I listened to her. I acknowledged what she was trying to communicate and made room for the fact that the feedback hurt. But I did not retreat from the truth simply because it was uncomfortable for either of us.

Empathy does not mean avoiding the difficult conversation. Sometimes empathy is being willing to have it carefully, honestly, and with the other person’s future in mind.

At the time, I was not sure how much of the conversation she had accepted. There was no dramatic breakthrough. There was no movie-scene moment where everything clicked, the music swelled, and she thanked me for changing her life.

We simply finished the conversation and went back to work, but I continued to stay close to her. I gave her pointers when she sent a group message. She would ask for feedback before publicly publishing anything. We walked the walk, together.

Eventually, I left the company.

A few months later, she reached out to me.

She told me that she had changed how she showed up. She was earning recognition, receiving awards, and being considered for leadership opportunities. The feedback had stayed with her even though I was no longer there to reinforce it, track it, or take any credit for what came next.

That message meant more to me than almost any performance metric I had ever received.

Leaders are often measured by what happens while we are in the room: whether the team hits its goals, whether customers are satisfied, whether service levels are met, and whether the operation runs smoothly. Those things matter. I am proud of the measurable results my teams have achieved.

But I think the truest measure of leadership may be what continues after we leave the room.

The growth in this story belongs to her. She was the one who reflected, adjusted, and did the work. My role was to care enough about what she wanted to tell her something that was difficult to hear, and then stand by her side while she attempted to make the changes.

That is the strange thing about developing people: you do not get to take the finished product with you.

The process documents stay with the company. The improved performance stays with the team. The confidence, skills, and lessons belong to the person who earned them.

Sometimes, the only evidence you receive is a message months or years later that says, in one way or another, “What you told me mattered.”

And sometimes, that is the best proof of leadership there is.

The goal is not to make people successful only while they work for you. It is to help them build something they can carry long after they no longer do.