top of page

Before You Blame the Team, Test the System

Writer: Biana Lerman
Biana Lerman
Oct 28
9 min read
Three colleagues examine a gap in a wooden pathway where brass balls have collected, illustrating a system failure blocking progress.

The accountability blind spot that keeps leaders solving the wrong problem.


Imagine a marketing meeting where everyone has come prepared to explain why the campaign isn’t working.


  • The targeting needs refining.

  • The messaging isn’t strong enough.

  • Sales says the leads aren’t qualified.

  • Marketing wants to know how quickly sales is following up.

  • Someone suggests changing agencies.


Then someone opens the website on their phone, fills out the inquiry form, and presses submit.


An error message appears.


They try again. Same result.


For the past forty minutes, the team has been discussing how to persuade more people to take an action the website won’t let them complete.


This is a hypothetical situation, but the question it raises applies far beyond marketing:

Are we examining what’s actually wrong, or simply blaming whoever is closest to the problem?


Everyone had an explanation. Nobody had tested it.


A professional discovers an error while testing a website inquiry form on a smartphone as colleagues discuss campaign results in the background.

In marketing, there are plenty of places to look when results fall short.


  • Audience selection

  • Creative

  • Positioning

  • Budget

  • Timing

  • Follow-up

They all deserve attention, but before rewriting the campaign, someone needs to follow the path the customer is supposed to take.


  • Click the ad.

  • Read the landing page.

  • Try it on a phone.

  • Submit the form.

  • Check where the inquiry goes.

  • Find out what happens next.


A successful submission is only part of the journey. An inquiry can arrive in an unmonitored inbox, get assigned to someone who has left the company, or trigger a confirmation promising a response nobody is responsible for sending.

The customer has done what we asked. We haven’t completed our part.

Research by James Oldroyd, Kristina McElheran, and David Elkington, published in Harvard Business Review in 2011, examined responses to online sales inquiries and identified slow follow-up as a business problem. Although the research is older, it offers a useful reminder to investigate what happens after an inquiry arrives, alongside the work of generating it.


That distinction matters when we’re deciding what to fix.


A team can spend weeks improving a headline while inquiries sit unanswered. It can generate more traffic without discovering that a form fails on mobile. It can hire another agency and hand over the same broken process.


There may still be problems with the campaign. Testing the system helps establish which problems we actually have.


The accountability blind spot appears when we scrutinize results without including our own processes, assumptions, and decisions in that examination. We know how something was supposed to work. We approved it. We remember testing it when it launched. That familiarity can make it easy to skip the most basic question: does it still work for the person using it?

The customer is still trying to get help


A frustrated customer reviews repetitive automated support responses on a laptop, with a disputed bill and phone beside her.

Now consider a customer contacting a company about an incorrect charge. The automated assistant provides a billing article. The customer explains that the article doesn’t address the issue. The assistant offers another version of the same answer.


They ask for a person. They’re sent back to the menu.


Inside the company, the discussion may focus on reducing support volume and improving efficiency. Outside the company, someone has spent twenty minutes trying to correct a charge they should never have received.

Both sides are looking at the same system. They are experiencing very different results.

Automation can be useful. In a 2026 Gartner survey of 3,566 business and consumer customers, half said generative AI made their customer service interactions easier. Yet 87 percent also considered access to a human essential when companies use that technology. People can appreciate convenient automation and still need help when it cannot resolve their problem.


The leadership question is whether we have made that transition possible. If fewer calls reach the team, do we know how many problems were resolved? Do we know how many customers gave up?


A process designed to save time can transfer the work to the customer. They have to repeat information, interpret instructions, find another contact method, and explain why their previous attempts failed.


Eventually, their frustration reaches an employee. That employee is expected to deliver a calm, helpful experience within the limitations of a system they didn’t design. Their response matters. So do the decisions that created the situation they are being asked to manage.


Before concluding that the team needs more customer service training, someone should experience what customers must do to reach that team.


Then someone tells the leader


An employee points to documented examples while a leader leans back with a raised hand, illustrating how feedback can be dismissed before it is investigated.

An employee raises the problem. Customers can’t reach us when they need help. The form isn’t reliable. The handoff between departments is failing.


The leader has asked for honest feedback, so the employee brings examples.

There is an explanation for each one. That customer misunderstood the instructions. That week was unusually busy. The team hasn’t fully adopted the process. The employee doesn’t have the broader context.


Some of those explanations might be accurate, but in this scenario, none leads to an investigation. Each one closes the conversation. The leader leaves believing they clarified the situation. The employee leaves wondering what evidence would have been enough.


Research offers a reason to examine this dynamic. Across four studies published in 2011, Kelly See, Elizabeth Morrison, Naomi Rothman, and Jack Soll investigated power, confidence, and advice-taking. Their findings linked greater power with increased confidence and reduced use of others’ advice. In the fourth study, higher-power participants also made less accurate final judgments.


That doesn’t mean every confident leader dismisses feedback. It gives us a reason to ask whether confidence is helping us assess information or making it easier to disregard.


If I request your perspective but spend the conversation defending what I already believe, how much room have I given your perspective to influence anything?


A useful response might begin with, “Show me what happened.”


It might require looking at the process together, reviewing the examples, or acknowledging that the person closest to the work has information we don’t.


We don’t have to agree with every complaint. We do need a way to examine concerns that doesn’t depend on whether they fit our first explanation.


I have to include myself in this


AI-generated illustration of Biana Lerman listening to a colleague and taking notes as they review a concern together, representing openness to feedback and personal accountability.

I’ve made mistakes. I’ve overlooked things. I know what it feels like to move quickly and realize afterward that something needed more attention.


That is part of why I care about what happens when a concern surfaces. In my experience, there is often a communication problem somewhere in the middle. Someone notices something but doesn’t know who needs to hear it. A message gets passed along without a clear owner. People discuss an issue and assume someone else is handling it.

By the next meeting, everyone remembers the conversation. Nobody can say whether the problem was resolved.

The expectation needs to be shared: raise the concern, involve the right people, and keep communicating until there is a clear outcome.

That requires me to slow down, too. To ask another question when I think I understand. To check whether my instructions were clear. To consider whether a decision I supported is creating a problem I haven’t seen.


Experience helps us recognize patterns, but it doesn’t give us complete access to what everyone else is experiencing. I can understand why a process was created and still need to change it. I can have good reasons for a decision and still need to examine its consequences. Finding out that something isn’t working can be uncomfortable, especially when we approved it; but that information gives us a chance to act.


What changes once we know?


Three colleagues verify a website fix together, checking a successful form submission on a smartphone and documenting next steps.

There is a difference between overlooking a problem and repeatedly explaining away evidence that it exists. A form can break without anyone immediately knowing. A support process can create an unintended obstacle. A leader can misunderstand what an employee is trying to communicate.


What happens after discovery matters.


  • Who will investigate?

  • What needs to happen next?

  • When will someone check that the fix worked?

  • Who will communicate with the people affected?


Without those decisions, acknowledgment can become another stopping point. Everyone agrees that something should improve, while the people experiencing the problem continue to absorb the cost.


Accountability needs to reach the people who can change the conditions. That includes those who approved the process, set the priorities, allocated the resources, or decided what would be measured.


Individual performance still deserves examination. A broken process doesn’t explain every missed commitment or poor decision, but neither does an employee’s mistake establish that the process is sound.


We need to investigate both.


Back in that hypothetical marketing meeting, discovering the broken form doesn’t answer every question about performance. It gives the team somewhere useful to start.

Someone can fix the error. Someone can test the full inquiry process. The group can revisit its assumptions using evidence it didn’t have when the meeting began.


Before your next conversation about disappointing results, walk through the process you’re holding someone else accountable for.


What do you discover when you try it yourself?


About the Author


Biana Lerman, founder of Your Growth Leader and author of The Rise of Scarlet Rose.

Biana Lerman, founder of Your Growth Leader and author of The Rise of Scarlet Rose, with experience in business operations, leadership, entrepreneurship, and working with clients and teams.

Biana Lerman is the founder of Your Growth Leader, where she explores Psychological Leadership™, identity, self-trust, organizational behavior, and the patterns that influence how people live and work.

Her writing draws on her experience in business operations, leadership, entrepreneurship, and working with clients and teams. She is also the author of the forthcoming novel The Rise of Scarlet Rose.


Through Your Growth Leader and her Substack publication, The Rise with Biana Lerman, Biana brings together professional experience, psychological insight, and storytelling to encourage deeper conversations about personal and professional growth.


Frequently Asked Questions


What is an accountability blind spot in leadership?


In this article, an accountability blind spot describes what happens when leaders examine other people’s performance without adequately examining their own decisions, assumptions, or the systems influencing that performance. It is a practical description rather than a formal psychological term.


How can leaders distinguish a process problem from a performance problem?


Review specific examples, observe the work firsthand, and check whether expectations, resources, and responsibilities are clear. Follow the process from beginning to end. The evidence may reveal a process failure, an individual performance issue, or a combination requiring more than one response.


How should leaders respond to feedback they disagree with?


Ask for specific examples and clarify what happened before offering an explanation. Review the evidence together where possible. If the feedback does not lead to a change, explain the reasoning and identify what would prompt another review.


How can businesses evaluate customer service automation?


Test whether customers can complete the tasks the automation is intended to support. Include situations it cannot resolve. Check whether customers can reach a person without unnecessarily repeating information, and examine whether their problem is resolved alongside measures of speed or contact volume.


Does examining the system reduce individual accountability?


No. It helps establish what each person could reasonably control and where responsibility belongs. Employees remain responsible for their actions, while leaders remain responsible for examining expectations, resources, processes, and decisions that influence the work.


About The RISE Method™


The RISE Method™ is Your Growth Leader’s approach to recognizing and changing the patterns that influence how we live, work, and lead.

  1. Recognize: Understand the beliefs, expectations, and patterns influencing your decisions.

  2. Interrupt: Question automatic responses that no longer serve you.

  3. Self-Lead: Make intentional decisions grounded in your values and responsibilities.

  4. Evolve: Apply what you’ve learned as you grow and your circumstances change.


Explore More From Your Growth Leader

Your Growth Leader: Explore articles, resources, and perspectives on identity, leadership, and personal growth.

The RISE Method™: Learn about the four stages of recognizing patterns, interrupting old responses, self-leading, and evolving.

The Rise with Biana Lerman — Substack: Join the deeper conversation about identity, growth, relationships, and the experiences that shape who we become.


The Rise of Scarlet Rose: Discover Biana’s forthcoming novel exploring identity, relationships, expectations, and the complicated process of choosing yourself.


Work With Biana


The patterns that influence your personal decisions can also affect how you communicate, lead, and operate professionally.


Your Growth Leader explores the connection between identity and leadership, helping individuals and organizations recognize recurring patterns and make more intentional decisions.


If you’re ready to examine how those patterns show up in your work, explore the available leadership services and ways to connect.



Your Growth Leader | Personal growth written for professional impact.


Subscribe to The Rise


Some of the expectations worth questioning are the ones we’ve lived with for years.

In The Rise with Biana Lerman, I explore identity, growth, relationships, and the experiences that make us reconsider how we want to live and work.

If those are conversations you’re having, too, I’d love to have you join us.


Research and References

  1. Oldroyd, J. B., McElheran, K., & Elkington, D. (2011). The short life of online sales leads. Harvard Business Review, 89(3), 28.

  2. Publication information and abstract

  3. This research examines how businesses respond to online sales inquiries. It provides context for examining follow-up processes alongside lead-generation efforts. It is historical research, not a current benchmark for response times.

  4. Gartner. (2026, August 4). Gartner survey finds 87% of customers say companies using GenAI for customer service must provide access to a human agent.

  5. Read the Gartner survey announcement

  6. This survey of 3,566 business and consumer customers examines attitudes toward generative AI in customer service, including the importance of maintaining access to human assistance.

  7. See, K. E., Morrison, E. W., Rothman, N. B., & Soll, J. B. (2011). The detrimental effects of power on confidence, advice taking, and accuracy. Organizational Behavior and Human Decision Processes, 116(2), 272–285.

  8. Read the research paper

  9. This paper examines how power and confidence influence people’s willingness to incorporate advice into their judgments. It provides context for the discussion of leadership receptiveness without establishing that every leader responds in the same way.

  10. Research is included to provide psychological and business context. Personal experiences and interpretations in this article are the author’s own and should not be treated as universal psychological findings.

Comments


© 2026 Your Growth Leader™
All Rights Reserved.

​

  • Linkedin
  • Instagram
  • Screenshot 2026-11-10 at 4.18.52 PM
  • Pinterest

AI may be used to support research and synthesis. Decisions, strategy, and judgment remain human-led.

bottom of page