When You Dismiss the Complaint, You Inherit the Problem

-

In the summer of 1995 I was part of a work crew operating under the Job Training and Partnership Act, traveling between two counties doing maintenance, painting, and lawn work. It was my second year with the program and I was looking forward to it. What I was not looking forward to was what the summer actually became.

The team leader, whose name I will change to Mark for the purposes of this piece, was not much of a leader. Within the first two weeks it was clear that he had little interest in working. Off-color jokes were a regular feature of the day. So was sitting around while hours ticked by. I brought my concerns to the regional supervisor, a woman I will call Scarlet. Her response was simple and direct: if I did not like it, I could quit.

I did not quit. I stayed because I did not have time to find something else on short notice, and I needed the work. What followed was a long summer of profanity, inappropriate humor, and minimal productivity. And then, predictably, things got worse. Mark and a close colleague on the crew began padding their timesheet hours with a specific goal in mind: accumulating enough money to take their girlfriends on a weekend trip to St. Louis. Eventually someone in the program noticed the discrepancies. Three days before the summer assignment was scheduled to end, both of them were terminated and the crew was disbanded. Mark, on his way out, stole the maintenance equipment.

Scarlet had been given an early warning. She had a choice and she made one. By telling a concerned worker to quit rather than investigating a legitimate complaint, she did not make the problem go away. She simply ensured that it would grow until it could no longer be ignored, and that the eventual cost would be higher than it needed to be.

This dynamic plays out in organizations every day, though usually with less colorful endings. An employee raises a concern about a team member's conduct or performance and is met with dismissal, deflection, or subtle pressure to let it go. The message received is that complaints are unwelcome, that the burden of a bad situation belongs to the person experiencing it rather than the leadership responsible for addressing it. So the employee goes quiet. The behavior continues. And the problem compounds.

The research on this is consistent. Employees who feel their concerns are taken seriously are more engaged, more loyal, and more likely to surface problems early when they are still manageable. Organizations that create genuine channels for raising concerns and respond to them with transparency and follow-through catch misconduct before it escalates. Those that signal, even subtly, that complaints are inconvenient tend to discover their problems much later, at considerably greater cost.

Dismissing a complaint is not a neutral act. It is a decision with consequences that compound quietly until they cannot be ignored. The question for any leader is not whether problems will surface. It is whether they will hear about them early enough to do something about it, or late enough that the damage is already done. Scarlet found out. She just found out too late.

Popular posts from this blog

The Dual Faces of Technology: Enhancing and Replacing Jobs

-
Image
Automation has been on my mind a lot lately, more immediately due to a book I read , but also because of the looming reality of artificial intelligence. To understand what's involved, making the distinction between replacing technologies and enabling technologies is crucial. As we traverse the timeline of the 20th century, we observe how each type of technology has distinctly influenced employment. Automated technologies have transformed industries by replacing manual labor with machines. Consider the automated switchboards introduced in the early 20th century. Previously, telephone operators manually connected calls using physical connectors on a switchboard. With the advent of automated switchboards in the 1920s and 1930s, many of these jobs were eliminated as calls were routed through electromechanical systems. Similarly, in agriculture, the introduction of mechanical harvesters like the combine harvester in the 1930s drastically reduced the need for manual labor. These machine...
Read more

The Technology Trap: Capital, Labor and Power in the Age of Automation (Book Review)

-
Image
In his compelling book, " The Technology Trap: Capital, Labor, and Power in the Age of Automation ," Carl Benedikt Frey offers a sweeping examination of the historical and ongoing impact of mechanization and automation on society. Starting with the onset of the first Industrial Revolution, Frey deftly navigates through the evolution of technology up to the modern age of artificial intelligence, presenting a nuanced view of how technological innovations have reshaped labor markets and power dynamics. Frey categorizes technological innovations into two types: enabling technologies, like the typewriter, which enhance worker productivity without displacing the labor force, and replacing technologies, such as robotic machinery in factories, which eliminate certain job roles altogether. This distinction forms the backbone of Frey’s analysis, as he explores the varying implications of each type of technology on different segments of the workforce. The book traces a historical patter...
Read more

Deputy Product Owners

-
Image
"The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner." - The Scrum Guide There are a lot of ways in which my approach to Scrum differs from what's in the official guide, and since that document refers to Scrum as 'immutable,' let's just call what I do 'Notscrum™.' In Scrum, there is only one product owner per team. That person is the sole person responsible for the product backlog, and the person who advocates for the work to be done. In Notscrum there is one product owner, but there can be multiple deputy product owners. Here's how it works. When my program at Viacom was first forming I met with the then-director of the Library & Archive group and learned that while he set the priorities on work done, the archivists were organized in three distinct areas with a team lead ...
Read more