← Back to Writing
LinkedIn·2026-11-17·1 min

The number was 77.

The problem was not the people. The problem was the system they were working inside.

That was how many critical customer incidents the company had logged in the prior twelve months. Critical meant an account was at risk of walking.

Not frustrated. Not escalating. Done.

Leadership was looking for answers. The testing teams were overwhelmed. And the pressure to fix it was landing on everyone at once.

Before he proposed a single change, he went and listened.

He sat with the test engineers. Not to audit them. Not to deliver a verdict. Just to understand what their days actually looked like. What they were responsible for. What kept slipping through. What they did not have time to do well.

What he heard was not what leadership expected.

These were skilled people. They were not cutting corners or coasting. They were stretched across too many product groups, expected to cover too many kinds of testing, with no clear ownership of any of it. The structure had been built for a smaller organization and never redesigned after the layoffs reshuffled everything.

The problem was not the people. The problem was the system they were working inside.

He redesigned it. A cross-functional team of senior testers helped define the new structure themselves, organized around testing specialties instead of individual products. They wrote their own responsibilities, their own handoffs, their own best practices. When people help build the system, they do not need to be convinced to follow it.

Seven months later, the new process was embedded into standard releases.

Critical customer incidents dropped to zero that year.

The lesson from that engagement is one worth returning to constantly. When a team keeps struggling, the instinct is to look at the people. To ask who is not performing, who needs to be replaced, who is not working hard enough.

But sometimes the team is not the problem. Sometimes the team is doing exactly what the system allows them to do.

And the system is broken.

When you look at a team that keeps struggling, how often do you ask whether the system is the problem before you ask whether the people are?

JD

Joseph Diele

Founder, Diele Consulting · Author of Sustainable Quality

35 years in engineering, operations and manufacturing — from engineer to director to founder. Joe helps leaders develop their strongest technical people into leaders.

If this resonated, let's talk about what it looks like for you.

Schedule a Conversation →