Skip to main content

The Profit Recipe

Two colleagues discussing work at a desk in a shared office.

Will Your Team Bring You Bad News a Second Time?

What we do after a concern is raised helps determine whether we hear the next one.

Key takeaways

  • What happens after someone raises a concern can influence whether they speak up again.
  • Defending an existing process too quickly can keep us from finding the real Issue.
  • IDS® helps Leadership Teams move from concern to resolution with clear ownership.
  • Reporting back helps people see their concerns were considered, even when a change isn’t possible.

The first time someone raises a concern, our response matters. What matters even more is what happens next.

Imagine a teammate tells us customer information keeps getting lost between sales and delivery. People are chasing details and redoing work.

We can thank them for speaking up. But if we never explain what happens next, will they tell us when they spot another problem?

Certified EOS Implementer® Isabel Porzecanski names an often-overlooked skill: “Listening and asking the right questions.”

That starts with how we respond when someone tells us a process isn’t working.

In TalentLMS research, 56% of surveyed U.S. employees who hadn’t reported workplace misconduct said they believed speaking up wouldn’t make a difference.

That finding concerns misconduct, not routine process problems. Still, it raises a useful question for us: have we given people a reason to expect a response?

How Do Leaders Discourage Honesty Without Meaning To?

Discouraging honesty doesn’t always look like anger. Sometimes, it looks like defending the process before understanding the problem. Other times, it means thanking someone for speaking up and never following up.

When we’ve put time into building a process, defending it can feel natural. We might point out that the steps are documented and everyone knows what to do.

That may be true. It still doesn’t explain why information is going missing, and it can end the conversation before we understand the problem.

The business consequences are practical:

  • Repeated work: Teams keep correcting the same preventable mistakes.
  • Delayed delivery: Missing information slows work and creates unnecessary follow-up.
  • Larger Issues: Small problems continue until they become harder to solve.
  • Missed improvements: Employees stop suggesting ways to make the business work better.

Fewer complaints don’t always mean fewer problems. Sometimes, they mean people have stopped expecting anything useful to happen when they raise them.

Gallup’s Q12® Employee Engagement Survey includes whether employees feel their opinions count at work. Gallup also emphasizes feedback loops and honest responses to ideas we can’t adopt.

Listening matters, but so does letting someone know what became of their input.

How Should We Respond the Moment a Concern Is Raised?

When someone on our team raises a concern, our first job is to understand it. We don’t need to agree immediately, defend the current process, or start solving the problem ourselves.

A useful first response has four parts:

  1. Acknowledge the concern. Let the person know we’re taking it seriously.
  2. Ask what happened. Understand where the problem appeared and whether it has happened before.
  3. Clarify the impact. Identify which customers, teams, or parts of the process are affected.
  4. Avoid assigning blame too early. Understand the Issue before deciding what caused it.

Fernando Delgado, Professional EOS Implementer®, at The Profit Recipe connects communication breakdowns to a deeper problem: “A ‘lack of communication’ often masks systemic issues like poor accountability and unclear roles, which drive dysfunction.”

Taking someone seriously doesn’t mean accepting their diagnosis. Ask whether the problem is missing information or unclear ownership of the handoff.

Once we understand the concern, we can agree on a next step and an update date.

We don’t need to own every problem ourselves, and the person who raised it shouldn’t automatically inherit it. Responsibility belongs with the role best positioned to address the Issue.

How Does IDS® Turn a Concern into a Resolution?

IDS® (Identify, Discuss, Solve), an Entrepreneurial Operating System® (EOS®) tool, gives our Leadership Team a way to resolve the concern without getting stuck in blame or vague reminders to “communicate better.”

1. Identify the real Issue. “Customer information keeps going missing” describes the symptom. The underlying Issue may be that nobody owns confirmation that all required information is complete before work moves to delivery.

2. Discuss what matters. Once we’ve identified the root Issue, we can hear the relevant facts, concerns, and perspectives from sales and delivery. What does each team need for the handoff to work?

3. Solve it with clear ownership. We might agree that one person in sales owns confirming all required customer information is documented before delivery begins.

For example, the sales lead could update the handoff checklist by Friday and test it on the next three orders.

That gives us a specific action, an owner, and a deadline, along with a way to check whether the change helped.

Review that To-Do at the next Level 10 Meeting® so the agreed action has a regular place for follow-through.

Report Back, Even When the Answer Is ‘Not Yet’

An Issue can be resolved in a meeting while the person who raised it is still wondering whether anyone listened. We need to bring that person back into the conversation.

Our update should explain:

  • What the team understood
  • What was decided and why
  • Who owns the next action
  • When another update will come

That follow-through is a leadership responsibility, not another step of IDS®.

If we promised an update by Friday, we owe that update on Friday, even if more work is needed. An unfinished fix doesn’t have to mean silence.

For example: “We’re testing the revised checklist on three orders before changing it across the team. I’ll check in with you next Friday to see whether delivery is getting the information it needs.”

The same applies when we don’t adopt a suggestion. Explaining the reason helps someone understand the decision without having to chase us for an answer.

Once a change is in place, we need to check whether it worked. Is delivery receiving complete information? What does the teammate who first raised the concern notice?

If the problem continues, we can return it to the Issues List and work through what’s still getting in the way.

FAQs About Responding to Employee Concerns

How should a leader respond when an employee raises a concern?

Thank them, ask what happened, clarify the impact, and agree on the next step and update date. Understand the Issue before defending the process or assigning blame.

How does IDS® help a team address employee concerns?

IDS® means Identify, Discuss, Solve. It helps the team find the root Issue, discuss relevant perspectives, and agree on a solution with clear ownership.

What if we can’t act on an employee’s suggestion?

Explain the decision and its reasoning. If it’s deferred, name what needs to happen next and when you’ll update them. Don’t leave silence as the answer.

How soon should we follow up after someone raises a concern? 

Agree on a specific update date in the first conversation and keep it, even if the fix isn’t finished.

Who should own fixing the problem? 

The role best positioned to address the Issue. It shouldn’t automatically fall to the leader or to the person who raised it.

Give the Next Concern Somewhere to Go

We can’t promise every concern will lead to change. We can show that raising it was worthwhile.

Give someone a meaningful update this week before they have to ask.

Following through is easier when it’s part of how the business runs, not something a leader has to remember. The Profit Recipe helps Leadership Teams implement EOS® so that every Issue can be worked through with IDS®, every To-Do has an owner, and the weekly Level 10 Meeting® keeps each agreed action moving. If your Leadership Team is ready for that to be normal, talk with us about implementing EOS.

Sign up!
Receive updates to our expert content series by dropping your email below.