ao link
Business Reporter
Business Reporter
Business Reporter
Search Business Report
My Account
Remember Login
My Account
Remember Login

American View: Your People Might Not Be Leaving You for Pay, Titles, or Remote Work

Linked InTwitterFacebook

I’ve been delving into far too many grim and depressing topics recently, so let’s take a well-deserved break from COVID world and ponder a more light-hearted subject: abuse of managerial authority the resulting corruption of process integrity, and its effect on employee retention.

What? It’s 2022. This is about as “light-hearted” as I can get these days. Besides, the story I’m telling today is kinda funny … now that I’ve had ten years to get over being mad about it.

The setting for this story is the U.S. Air Force back at the turn of the millennium. I’d just been appointed the new commanding officer of my wing’s IT support unit. My primary missions, according to my new boss, were to eliminate the unprofessional squabbles plaguing the unit, drastically improve customer service, and fix the unit’s broken IT equipment inventory process.

The unit I’d inherited was a mess, but I knew that going in. I’d been one of their “customers” for a couple of years and I despised their incompetence like everyone else in the wing. I saluted my new boss smartly and got to work, starting with my third objective.

For context, the USAF’s approach to “Automated Data Processing Equipment” management was to assign all new computer-y stuff (like PCs, monitors, printers, , etc.) to a wing’s IT shop, which would record all the stuff by unique government property management tags in a big inventory ledger, and then “issue” the stuff to a designated IT inventory person in each squadron. That squadron inventory person would then “issue” the kit down to their shops, groups, or users. In the end, the big inventory management database would have records of where each item was physically located and who was responsible for it.

One a year, every unit-level inventory person was required to conduct a complete inventory of every item they’d signed for. This included noting all moves, adds, and changes so my IT property shop could enter the latest location and assignment data into our inventory database. This process was followed by hundreds of units all over the world and it worked fine … so long as everyone involved in the process did their jobs correctly.

Try to imagine the exact opposite of every stock photo with the word “team” in its description.
Try to imagine the exact opposite of every stock photo with the word “team” in its description.

Guess what our unit didn’t do? If you guessed “everything” you’d be right. I’ll only highlight three glaring problems our of dozens to keep this article from becoming a novella.

First, I discovered that our previous inventory database manager had stopped entering moves, adds, and changes into the database years before he retired. He just … didn’t do his job. The inventory reports that we’d been sending down to the squadron inventory people were so hopelessly wrong that they came back covered in red ink. We learned it would take us months to straighten up what we had on the books. We also learned that our lack of corrective action had been frustrating our unit level inventory reps who thought that our team was incompetent.

Second, it was our unit’s job to demilitarize and get rid of all obsolete ADPE. When we replaced an old PC with a new one, for example, it was out job to rip out its hard drive out and then send the clunker to a Dept. of Defense junkyard where it would be sold as scrap. Did we do that? Nope! I learned that our previous property manager hadn’t been doing that. We had over one million dollars’ worth of junk ADPE stuffed in our warehouse. Because it was all still legally in our possession, it all had to be inventoried before we could start to prep it for disposal.

Finally, our unit’s customer service had been so poor for so long that people throughout our wing had ignored USAF procurement regulations and bought their own IT parts. I understood why; when I first joined the unit, I discovered the computer assigned to my office wouldn’t power on. Even though my office was directly across the call from the IT Help Desk, it took over a year and three separate “support” tickets to get my PC fixed. I empathized … but all that “rogue” IT kit had to be found and added to the property database.

There were more problems. Our situation was abysmal. Nonetheless, we did our best to get the program back on track. We implemented new standards for quality control, dedicated extra time and manpower to clear the data entry backlog, etc. We made slow but steady progress until we reached 95% accuracy … and cleared two semi-trailers worth of junk out of our warehouse.

Our boss felt we were making satisfactory progress … and then she retired. Her replacement – we’ll call him “Colonel Bob” IAW SOP [1] – was a gen-u-ine sadist and petty tyrant. Colonel Bob didn’t give a hoot about how well we performed our jobs or what improvements we’d made. Colonel Bob was only interested in one thing: what could he use to torture us? That was Bob’s favourite game: making life so miserable for his subordinate commanders and Senior NCOs that they resigned in frustration. He was quite good at it, too. By the end of his command tour, five of the seven squadron commanders he’d inherited, and half the Chief Master Sergeants had left.

One of Colonel Bob’s torture techniques was to make fiery speeches to us about the “criticality” of property management excellence, excoriating me and my team for failing to achieve perfection. Then he’d threaten us with all sorts of dire, Old Testament inspired consequences if we didn’t achieve the highly improbable. We didn’t need any additional motivation; the oratory and threats were just Bob’s way of getting away with being a complete crap-hat in public.

It’s said that “Rank Hath Its Privileges” … The evidence supports that. Colonel Bob was rank, caustic, abusive, and vile with pretty much everyone under his authority.
It’s said that “Rank Hath Its Privileges” … The evidence supports that. Colonel Bob was rank, caustic, abusive, and vile with pretty much everyone under his authority.

Despite his blistering screeds, Colonel Bob didn’t actually want us to succeed. What fun was that? To ensure that we’d never meet our goals, Colonel Bob changed the official USAF rules when it came to inventories: instead of following the global Air Force standard of one massive inventory of all IT assets every year, our wing would hold a complete inventory every fiscal quarter.

 

Yeah … Colonel Bob quadrupled our workload, claiming that this would “guarantee” accuracy. Except it didn’t. It hindered more than it helped, since the property management team spent all their time generating and processing unit inventory paperwork rather than getting new equipment ready to issue or clearing out obsolete gear that really needed to vamoose.

 

Then, because Colonel Bob was a gifted sadist, he added another unique complication: after every unit IT inventory person completed their quarterly inventory, one of my Airmen was required to go in behind the unit rep and repeat the inventory to “validate” their findings.

 

This “improvement” did nothing for accuracy; it only served to punish my people through extra labour. The mandate crippled our unit’s operating efficiency. We spent nearly all our time chasing down the same collection of old Dell PCs Viewsonic monitors, and Lexmark printers month after month. We generated reams of reports, all of which had to be cross-referenced and signed by the inventory tech, the property management sergeant, by me … and by Colonel Bob. No quarterly inventory was ever “finished” until he signed it … which he would deliberately delay until they were “late,” thereby justifying why he felt “required” to extend his burdensome programme for another year. Just one more trip up the mountain, Major Sisyphus! 

 

 

I said at the beginning that I intended to write about “corruption” and “process integrity.” I’m using the Wikipedia functional definition here because it’s more nuanced than the entry in the Oxford English Dictionary:

 

“Corruption is a form of dishonesty or a criminal offense which is undertaken by a person or an organization which is entrusted in a position of authority, in order to acquire illicit benefits or abuse power for one’s personal gain” [2]

 

To be clear, Colonel Bob’s actions were blatantly dishonest. While he claimed that his changes were necessary to “improve accuracy” in property control, he knew that we knew he was lying. His scheme was harassment, pure and simple. He did have the authority to make us do it; we couldn’t lawfully refuse his orders. As for “personal gain,” he wasn’t making money off us. His abuse was meant to satisfy his pathological need to dominate and inflict misery on people who couldn’t fight back. The man was a bully, plain and simple.

 

And as to the effect of Bob’s “inventory octupling” scheme on the property control process, it did exactly what you’d expect it to do: it exhausted us all, generated massive discontent, and caused many Airmen – good ones and bad alike – to transfer out or quit the military entirely. My people were demoralized. Far too many necessary service and capability improvements were delayed or scrapped altogether because we couldn’t spare the time to implement them. Colonel Bob achieved his desired effect: he made us miserable, and that sated his need to harm others.

 

One of the most important elements of this years-long misadventure wasn’t the gruelling, unnecessary work itself; we were military folks. Pointless, unnecessary work was part and parcel of our trade. Think “painting the grass” for “area beautification.” No, the most demoralizing aspect of this experience came fro knowing that there were multiple people and groups empowered to prevent abuses of authority like this from occurring … all of whom did nothing. They turned a blind eye to Colonel Bob’s abuse of his authority for years. That was what broke so many of my people’s will to carry on. The people who were supposed to protect us … didn’t.

That’s the inherent flaw in all behaviour oversight programmes: the people empowered and trusted to rein in misconduct often refuse to act, because admitting that misconduct happened under their watch exposes the supervisor to accusations of incompetence for allowing the misconduct to happen under their watch. They’re incentivized to turn a blind eye.

 

But surely, you might think, this story – while kinda schadenfreude-y – reflects something unique to the military, and therefore has no bearing my life as a businessperson. I understand that position and submit that it’s incorrect. Consider: the military has regulations, not processes. Rules that cannot be broken on pain of termination, discharge, or imprisonment. Further, there are entire suborganizations in the military devoted to overseeing compliance with our regulations, investigating misconduct, and removing bad personnel.

 

The corporate world doesn’t have any such thing. Their policies and “rules” are arbitrary and subject to change at any time. Enforcement is done on a whim if it’s done at all. As for oversight, an organisation might have a pseudo-anonymous “complaint” hotline that they probably ignore. The only commandment in business is “make money.” Every other “principle” is optional and will be jettisoned as soon as it becomes inconvenient. Thus, nearly any abuse of authority will be tolerated in the corporate world so long as the abuser is delivering on the One True Goal™.

 

So, what’s the main takeaway here? That military life sucks? No; I wanted to share the story of Colonel Bob’s “inventory death march” game to point out that employee morale and retention isn’t soured nearly as much as you’d think by hard work, long hours, or a dearth of branded merch. People in the military and in corp space alike feel proud when they do important work. They relish a challenge and celebrate their victories. People’s morale tanks when they perceive their work to be pointless. Retention tanks when workers realize that their pointless work is being inflicted on them deliberately rather than operational necessity.

 

I recommend that you take a hard look at your organisation and tell me if there are mandatory work processes in-play that are inefficient or actively detrimental to your team’s efficiency, effectiveness, morale, or esprit de corps. Work that drains your people’s fidelity and motivation. Work that feels like petty abuse than rather than necessary activity. Work that inexplicably could be performed more easily but is instead required by someone in your organisation to be conducted as inefficient as possible. Work that seems designed for you to fail it. Those are the activities that are going to drive your people away.  

 

I argue that such work might be the natural product of good intentions married to poor process design, but probably isn’t. More often than not, I’d wager it’s the deliberate action of some petty, sour-minded, jack-wagon who’s deliberately abusing their power to cause misery solely for their own satisfaction. The question to ask, in such a case, is “what will my organisation do about this? Is there anyone we can turn to that can and will make this stop? Or is my only recourse to resign and try my luck somewhere else?”

 

If you find one of these problems, you can either fit it at the root – remove the offender(s) – or you can rebuild from scratch after all your critical personnel have left you for somewhere that doesn’t treat them like a spoiled godling’s playthings.

 

 

[1] “In Accordance With Standard Operating Procedure.” Universal military jargon.

[2] Emphasis added.

Linked InTwitterFacebook
Business Reporter

Winston House, 3rd Floor, Units 306-309, 2-4 Dollis Park, London, N3 1HF

23-29 Hendon Lane, London, N3 1RT

020 8349 4363

© 2024, Lyonsdown Limited. Business Reporter® is a registered trademark of Lyonsdown Ltd. VAT registration number: 830519543

We use cookies so we can provide you with the best online experience. By continuing to browse this site you are agreeing to our use of cookies. Click on the banner to find out more.
Cookie Settings