As Achilles explains, the issue usually isn’t access to information. Most companies already have dashboards, metrics, and reporting systems everywhere. The problem is that people often go into the data already believing they know the answer. Instead of exploring what the data is saying, they search for validation.

And that can create dangerous blind spots.

One of the more interesting points in the discussion is how organizations react emotionally to data depending on what color it shows up as. Green metrics often get ignored. Red metrics create panic. But neither response is necessarily productive unless teams are trained to slow down, evaluate context, and understand what the data is actually telling them.
Achilles also breaks the conversation into two sides: technical and business.

On the technical side, he emphasizes the importance of letting the data guide the investigation. Whether it’s tensile testing, process validation, or operational metrics, the goal shouldn’t be proving yourself right. The goal should be understanding what’s really happening.

On the business side, he points out a mistake many organizations make: involving financial partners too late in the process. When finance teams aren’t brought into initiatives early, expectations become disconnected from operational reality. But when they’re part of the journey from the beginning, organizations make better decisions together.

At its core, the conversation is really about maturity. Data alone doesn’t make an organization smarter. How people utilize it does.

It’s not just about logging complaints. It’s about how they come in, who’s responsible for capturing them, and how quickly they move through the system.

Shelly points out that breakdowns often happen at the front end. Sales teams holding onto complaints too long. Disconnected communication between departments. Missing reporting timelines because information didn’t flow the way it should have. In MedTech, that’s not just inefficient, it can lead to real compliance risk.

The fix isn’t complicated, but it does require discipline. Strong intake channels. Clear communication across teams. Training people to recognize and escalate complaints immediately. And just as important, making sure nothing falls through the cracks by tracking against external databases and regulatory expectations.

But what really stands out is the human side of it.

Closing the loop matters. Not just internally, but with the person who raised the issue in the first place. Because at the end of the day, complaint handling isn’t just a regulatory function. It’s customer service. People want to know they’ve been heard and that something was actually done.

And behind all of it is the team. The structure, the accountability, and the ability to scale when things spike.

Done right, complaint handling isn’t a burden. It’s a system that protects the business, supports the customer, and keeps everything moving forward.

​Looking for more information?
If you have questions about this topic or want to explore how our team can help with your Medtech project, contact us here.
Want to see what we do?
Visit our Services page or contact us directly to talk through your project and see if we’re the right fit.

He frames it in a way that’s hard to forget. Think of it like doubles in pickleball. You don’t control every shot, but you’re still accountable for the outcome. Success depends on how well you communicate, how clearly roles are understood, and how much trust exists between teammates.

That’s where most breakdowns happen.

Not because people don’t care. But because they rely too heavily on passive communication. A couple of emails. Maybe a Teams message. And when there’s no response, the work just… stops.

Achilles challenges that mindset directly.

Ownership doesn’t look like waiting. It looks like action. Picking up the phone. Walking over. Creating a real conversation that uncovers what’s actually blocking progress.

Because once things escalate, the problem isn’t just the work anymore. Now trust is on the line too.

It’s a simple shift. But in a matrix organization, it makes all the difference.