Monday, November 16, 2026

Leadership Aphorisms III

According to the Merriam-Webster online dictionary, the word aphorism is defined as a concise statement of principle or a terse formulation of a truth or sentiment, often by a famous author from antiquity.  I have scraps of paper with various leadership aphorisms scattered throughout my office, both at home and work.  I have shared some of these in previous posts (see "Reflections on Leadership", "Leadership Aphorisms I", and "Leadership Aphorisms II").  Since my last post on this topic, I've collected some new favorites that I would like to share today:

"When in command.  Command." Admiral Chester W. Nimitz

The Battle of Midway was one of those pivotal moments that changed the course, at least for the Pacific Theater, of World War II.  The U.S. Navy's Pacific Fleet was still recovering from the devastating surprise attack on Pearl Harbor on December 7, 1941.  The Japanese military forces had won victory after victory over the next six months, scoring victories and capturing island military bases in the Philippines, Guam, Wake Island, and the Dutch East Indies.  To say that the Japanese had the Allied Forces on their heels would be a vast understatement.  

The U.S. Navy cracked the Japanese military's secret code and intercepted transmissions about planned attacks on both Midway Island and the Aleutian Islands.  The new Commander-in-Chief of the Pacific Fleet, Admiral Chester Nimitz, believed that the attack on the Aleutian Islands was only a feint to trick the U.S. into sending forces there.  Look at the map below and you can see why the U.S. would worry about an attack on the Aleutian Islands (see how close they are to the continental United States)!











The U.S. Pacific Fleet was down to just three aircraft carriers, the USS Enterprise, the USS Hornet, and the USS Yorktown, which had recently sustained heavy damage in the Battle of the Coral Sea.  Admiral Nimitz was making a huge gamble that the Japanese military's true objective was Midway Island, but the question that weighed heavily on his mind was how to defend both the Aleutians and Midway.  and he wanted to move all three carriers in order to make a stand there.

According to Admiral (retired) William McRaven (see his superb book, The Wisdom of the Bullfrog), Admiral Nimitz was considering going on the offensive, moving all three aircraft carriers to Midway, and attacking the Japanese Fleet there.  But he remained apprehensive.  It was a huge gamble - what if the Japanese Navy's true objective was the Aleutian Islands?  Legend has it that during a conversation with Admiral "Bull" Halsey, Nimitz confessed his apprehension. Halsey bluntly reminded Nimitz of something that he had frequently told him.  Halsey began, "You once old me that when in command, command."  It was the clarion call that Nimitz needed.  He moved all three aircraft carriers to Midway, and the U.S. Navy scored a major victory over the Japanese Navy, turning the tide of the war in the Allies' favor. 

Leaders are expected to make the tough decisions.  They are expected to act with purpose, confidence, and conviction.  Leaders "lead" from the front.  No matter how difficult the situation, no mater how uncertain the circumstances, a leader should lead.  

"You manage things; you lead people." Rear Admiral Grace Murray Hopper

I've posted about Rear Admiral Grace Hopper a number of times in the past (see "A few of history's greatest leaders" and "Organizational enemas").  She was an American computer scientist, mathematician, and Naval Officer who is perhaps best known for being the first to devise the theory of machine-independent programming language (which subsequently led to the development of the COBOL computer programming language) and for being one of the first to program the Harvard Mark I computer.  Rear Admiral Hopper also was the first to coin the term "bug" for computer programming.  As the story goes, it was a warm, late summer day in 1947 (September 9, 1947 to be exact) when a team of engineers and computer scientists at Harvard University were working on the Mark II computer.  The computer program kept delivering an error.  According to legend, Hopper opened up the back of the computer to check one of the relays and found a dead moth.  She carefully fished the moth out of the computer with a pair of tweezers, taped it into her logbook (see photo below), and wrote the message, "first actual bug found."  Hopper reportedly said afterwards, "From then on, when anything went wrong with a computer, we said it had bugs in it."















Harvard Business Review (HBR) first published an article by Abraham Zelznik in 1977 that highlighted the differences between leadership and management.  Since that time, the question on whether leaders and managers are different has been posed in several articles published both in HBR and elsewhere (see, for example, "What Leaders Really Do", "Do Managers and Leaders Really Do Different Things?", "Leadership vs. Management: What's the Difference?").  It's an age-old question, and some experts say that the debate goes all the way back to Niccolò Machiavelli (others say the debate goes as far back as Plato).  Leadership and Management are the proverbial two sides of the same coin.  They can't exist in isolation, because in reality, we need both.  Rear Admiral Hopper suggests that we should manage the work and lead the people (for a similar perspective, see another article by Vineet Nayar in HBR).  As I stated in my post "Leader, Manager, or Both?", "In order to be effective, an executive needs to be a good leader AND a good manager.  It's not an or question, it's an and one." 

"When I give a minister an order, I leave it to him to find the means to carry it out." Napoleon Bonaparte

I've written extensively about the High Reliability Organization principle of "Deference to Expertise", which has become so important to my own philosophy on leadership.  Napoleon was one of the greatest military leaders of all time.  He rose to prominence around the time of the French Revolution, eventually becoming Emperor of all France from 1804 through 1814.  During that time, he fought a number of successful military campaigns during the so-called Napoleonic Wars.  He was exiled to the island of Elba for a time, before returning as Emperor for a brief time during the "Hundred Days" in 1815.  

Napoleon's military leadership philosophy depended upon speed and massed decisive force.  Speed, in turn, required organizing his army into several independent, self-sustaining corps that marched quickly along separate routes before converging rapidly at the point of attack to surprise the enemy with overwhelming force.  Napoleon led from the front, though he often gave operational independence to trusted commanders and avoided micromanaging them.











As leaders, we should always provide a general framework (what I call "guardrails") for achieving the ultimate objective, but then we need to step away and let our front-line leaders do the work (see my posts, "Empowering employees doesn't mean leaving them alone..." and "Do not command more than is necessary...").  It is the same philosophy that is at the core of the military concepts of Commander's Intent, Mission-type tactics, and auftragstaktik (a form of "Deference Expertise" used by the German Army in World Wars I and II).

"The very essence of leadership is that you have to have a vision. It's got to be a vision you articulate clearly and forcefully on every occasion. You can't blow an uncertain trumpet." Reverend Theodore Hesburgh

The late Reverend Theodore Hesburgh was the President of the University of Notre Dame from 1952 to 1987.  He remained a beloved fixture at Notre Dame for the remainder of his life, and when he died in 2015, the student body at the University honored him with a candlelight vigil, and speakers and attendees at his funeral and memorial service included former President Jimmy Carter, Condoleezza Rice, Lou Holtz, then cardinal Theodore McCarrick and cardinal Roger Mahony, former U.S. senator Harris L. Wofford, Indiana governor Mike Pence, former First Lady Rosalynn Carter, former U.S. senator Alan K. Simpson, U.S. senator Joe Donnelly, William G. Bowen, and a video message from then President Barack Obama.

"Father Ted" as he was affectionately known was the recipient of the Presidential Medal of Freedom in 1964 and the Congressional Gold Medal in 2000 for his humanitarian work.  He was a civil rights leader (see picture below), public servant, and activist for social justice who holds 150 honorary degrees, which is a record.  He dedicated his life to "God, Country, and Notre Dame" (which is the title of his excellent autobiography).










To say that Father Hesburgh was an inspirational and visionary leader is a vast understatement.  A leader must be all that and more.  Father Hesburgh suggests that a leader must have vision, but he or she must also have the ability to communicate that vision in words and deeds that are clear, concise, and unambiguous.  His admonition to "blow a certain trumpet" comes from the 1 Corinthians 14:8 ("For if the trumpet makes an uncertain sound, who will prepare for battle").  By "sounding the trumpet", a leader sends a strong, clear signal of that vision.  Conviction.  Clarity.  No mixed messages.  These things are all part of leadership.

"Everything in war is very simple, but the simplest thing is difficult." Carl von Clausewitz

Carl von Clausewitz was a Prussian military leader who is perhaps best known for his book On War, in which he coined the phrase "fog of war" to describe the confusion, uncertainty, and ambiguity of combat that forces leaders to make rapid decisions with incomplete or even false information.  I would say that the same concepts are true for leaders outside of the military, particularly in the VUCA world that we live in today.  I will paraphrase Clausewitz by saying that "Everything in leadership is very simple, but the simplest things are difficult."  



Thursday, November 12, 2026

"One Shining Moment"

I recently attended the Children's Hospital Association Annual Leadership Conference in Phoenix, Arizona.  One of the plenary speakers was the author and entrepreneur Lisa Sun, who is also the founder and CEO of Gravitas.  I really enjoyed the talk!  While she made several really great points, one of the things that resonated with me the most was a comment she made about March Madness, the NCAA Division 1 men's and women's basketball tournament that takes place every year during the month of March.  Every year, at least since I can remember, the television network plays a highlight montage of the tournament with Luther Vandross singing in the background, "One Shining Moment".  It's one of my wife's favorite parts about March Madness every year - and apparently it's one of Lisa Sun's favorite parts too!  

The song lasts just over three minutes, but according to Sun the winner of the tournament is shown only for about twenty seconds (I've looked back at several versions over the years just to fact check Lisa Sun's claim).  Most of the video montage during the song actually shows footage from the 67 teams that didn't make win!  It's not about who won or even who made a shot - the song and the video montage are about the proverbial "blood, sweat, and tears" that went into the game itself.  In other words, what's really important is the fact that the players gave it their all.  Sun writes that it's not about missing the shot, "It was about the sweat and tears of those teammates who gave it their best."

Grantland Rice was a legendary sports writer from the 1920's, which has been called the "Golden Age of Sports".  Rice famously wrote in his 1941 poem, Alumnus Football, "For when the One Great Scorer comes to mark against your name, he writes – not that you won or lost – but how you played the Game."  Sports, and life, is not always about winning and losing.  It's about playing hard, with integrity, with honesty, and with sportsmanship.  

The song by Luther Vandross says something very similar:

In the blinking of an eye
All that moment's gone
And when it's done
Win or lose
You always did your best
'Cause inside you knew
That one shining moment
You reach deep inside
One shining moment
You knew you were alive.

I think if we spent a lot more time worrying about how we played the game of life, as opposed to who wins or loses, the world would be a lot better place.

Wednesday, November 11, 2026

"Tell the Spartans, stranger passing by, that here obedient to their laws we lie..."

Today we celebrate our military veterans, both past and present.  Veterans Day is celebrated every year on November 11th, and it's a day in which we honor all military veterans for their service and patriotism.  Importantly, Veterans Day honors all those who have served in our nation's armed forces, both living and deceased and during peacetime or wartime.  Memorial Day, celebrated on the last Monday in May every year, specifically honors those men and women who have died while serving their country.

Abraham Lincoln once said, "Any nation that does not honor its heroes will not long endure."  We should honor our veterans every day, but today most of all.  It is with profound respect, admiration, and gratitude that I honor our veterans, most of all those who "gave the last full measure of devotion" so that we may have a life of freedom.

The title of today's post comes from one of the greatest books that I have ever read, Gates of Fire by Steven Pressfield.  Pressfield opens his historical novel of the ancient Battle of Thermopylae with this ancient Greek epitaph carved into a stone placed on top of the burial mound of the 300 Spartans that heroically died at Thermopylae (see the ending scene of the 2006 film 300 which was based on the Battle of Thermopylae) .  The words were likely first written around 480 BC, shortly after the battle itself, by the poet Simonides of Ceos.

The Battle of Thermopylae was fought in 480 BC between the invading Persian army under Xerxes I and an allied force of Greek city-states led by Leonidas I of Sparta.  The Greeks were vastly outnumbered - classic sources (principally the Greek historian Herodotus) estimate that the Persian army numbered in the millions, while the Greeks consisted of about 7,000 men, including 300 Spartan hoplite soldiers.  Modern historians reject these numbers, suggesting that the Persian army numbered between 40,000 to 300,000 soldiers.  Modern estimates of the size of the Greek army are much closer to the estimates of ancient sources.  Regardless of the exact numbers, what is not disputed is the fact that the Persian army greatly outnumbered the Greeks.

While the geography has changed significantly over the centuries, Thermopylae (from the Greek, "Hot Gates," so named from the local hot sulfur springs in the area which were once believed to be an entrance to Hades, the Greek Underworld) used to be a narrow pass between the mountains on one side and the ocean on the other.  Leonidas I chose to place his army at the narrowest point, which was approximately 20 meters wide.  At the same time, allied Greek naval forces blocked the sea route at the Straits of Artemisium, where a naval battle with the Persian navy occurred simultaneously to the land battle at Thermopylae.  The Greeks held off the Persians for a time, before Leonidas withdrew all but his 300 Spartan hoplites and 700 Thespians, as well as 900 Helots and 400 Thebans, though this is disputed.  This remaining rear guard, with the exception of the Thebans, who reportedly surrendered en masse, fought to their death in a heroic "last stand" that lasted for another three days.  Leonidas, too, died with his men.

The Gates of Fire tells the story of the Battle of Thermopylae from the perspective of Xeones, a Greek perioikos (a free person, though not a citizen, of Sparta) who was captured by the Persians near the end of the battle and asked to dictate his story to Xerxes through his court historian, Gobartes.  Xerxes is amazed on how well the Spartans, in particular fought.  He asks Xeones directly why the Spartans fought so hard for Leonidas.  Xeones tells Xerxes:

I will tell His Majesty what a king is.  A king does not abide within his tent while his men bleed and die upon the field.  A king does not dine while his men go hungry, nor sleep when they stand at watch upon the wall.  A king does not command his men's loyalty through fear nor purchase it with gold; he earns their love by the sweat of his own back and the pains he endures for their sake.  That which comprises the harshest burden, a king lifts first and sets down last.  A king does not require service of those he leads but provides it to them.  He serves them, not they him.

Admiral William McRaven, of whom I have posted about numerous times in the past (see "A shepherd should smell like his sheep" for one most relevant to the subject of today's post), recites this exact passage during a lecture on leadership delivered at the National Football Foundation's William V. Campbell Trophy Summit (I believe in August, 2023).  Admiral McRaven says, "If you’re a leader, everyday you have to bring it. The only thing you’re entitled to as a leader is more hard work...Men and women will follow you as a leader if you are the first to lift the heaviest burden and the last to put it down."

There is a reason that Gates of Fire has appeared on the professional reading list for several branches of the United States military.  Its major themes stress core leadership concepts such as duty, honor, commitment, self-sacrifice, and esprit de corps.  While it is historical fiction, the story and the lessons that can be learned from it are timeless.  Let us honor all veterans today by living by the leadership philosophy and example of King Leonidas I.  Thank you to all of our veterans!

Monday, November 9, 2026

"Leave it better than you found it!"

As I've mentioned before (see for example my post, "Leadership Aphorisms I", "Stick to the Code", and "Fatherly Leadership"), I was a Boy Scout throughout my childhood and adolescence.  One of the lasting lessons that has stayed with me today is a concept that was first articulated by Robert Baden-Powell, a British army officer, writer, and original founder of the Boy Scouts.  Baden-Powell said, "Try and leave this world a little better than you found it, and when your turn comes to die, you can die happy in feeling that at any rate, you have not wasted your time but have done your best."  I've even incorporated this concept into my personal mission, vision, and values.

We were always taught as Boy Scouts to "leave it better than you found it" when it came to the outdoors, which has has evolved over time into the "Leave No Trace" conservation movement.  Whenever we went camping, we always made certain that we cleaned up the campsite to the point where the area was even better than when we had arrived.  But consider Baden-Powell's quote - he wasn't just speaking about the environmental movement or conservation.  He was speaking more generally about life itself.  We should be making an impact so that we leave the world a better place for future generations.

I've been thinking a lot about Baden-Powell's quote lately in the context of change in organizations.  As a matter of record, change is quite difficult.  And leading the kind of change required for an organizational transformation is exceedingly so.  Perhaps the best that any leader can hope for when it comes to organizational transformation is to "leave it better than you found it."  

Oday Kamal wrote an article about leading organizational transformation for the World Economic Forum (see "Organizational change is tough. Here are three rules to help get it right").  Kamal referenced the 19th century French chemist Henry Louis Le Chatelier who described a fundamental principle about systems in general that can be applied to organizations.  Kamal explained this principle as follows:

Every stable system will respond to change by trying to restore its original condition. Put another way, he deduced that any system will favor the least disruptive path.  This fundamental principle changed the course of chemistry in the 19th century. But it is not limited to the laws of thermodynamics. It describes how systems, organizations, and teams can learn to change.

In my own experience, I have found that organizations respond to change by trying to restore back to their original default mode.  The consulting firm, McKinsey, once cited a statistic that over 70% of all organizational transformation efforts fail.  While that is probably true, I've found that most consulting firms have failed to improve upon this statistic.  Change is hard.  Transformation takes time.  And many leaders don't have enough time to see the transformation to the end.  So I am left with the following conclusion - we can (and should) aim high as leaders, but perhaps the best that we can ever achieve is to "leave the organization better than we found it."

Thursday, November 5, 2026

What's in a promise?

Most of the public believes that before they graduate from medical school, new physicians have to raise their right hand and recite the Hippocratic Oath.  And if asked what is in the Hippocratic Oath, most people would say "First, do no harm" (perhaps a few would even recite the Latin version from the original Greek translation, "Primum non nocere").  Just to correct a common misconception, "First, do no harm" is often attributed to the ancient Greek physician Hippocrates, but it actually doesn't appear in his famous Oath.    

To correct another common misconception, most graduating physicians don't actually recite the Hippocratic Oath.  Many medical schools use more contemporary versions, and at least according to the Association of American Colleges, over half of medical schools in the United States use their own customized version, often written in collaboration with their medical students in order to emphasize more modern ethical principles such as health equity and patient advocacy.  Many medical schools use a version during the "White Coat Ceremony" (which often takes place when medical students start their clinical years of training) as opposed to graduation.

I recently came across the Oath of Maimonides, named after the 12th century rabbi, philosopher, and physician, Maimonides.  While some physicians recite the Oath of Maimonides at graduation from medical school, the Oath is more often used in other professions, including pharmacists.  Here it is:

The eternal providence has appointed me to watch over the life and health of Thy creatures. May the love for my art actuate me at all times; may neither avarice nor miserliness, nor thirst for glory or for a great reputation engage my mind; for the enemies of truth and philanthropy could easily deceive me and make me forgetful of my lofty aim of doing good to Thy children.

May I never see in the patient anything but a fellow creature in pain.

Grant me the strength, time and opportunity always to correct what I have acquired, always to extend its domain; for knowledge is immense and the spirit of man can extend indefinitely to enrich itself daily with new requirements. Today he can discover his errors of yesterday and tomorrow he can obtain a new light on what he thinks himself sure of today.

Oh, God, Thou has appointed me to watch over the life and death of Thy creatures; here am I ready for my vocation and now I turn unto my calling.

There's something to be said about making a promise, following a covenant, or reciting an oath (see my post, "Stick to the code").  I think it just means more than simple words on a piece of paper.  And studies suggest that they matter - for example, people who take an oath to act honestly actually do act honestly (compared to those who don't take an oath to act honestly).  Reciting an oath or promise represents a true commitment to a specific purpose.  The physical act of reciting an oath, as opposed to even signing one, just means more.

I do not remember reciting the Hippocratic Oath at my own graduation (and we didn't have anything like the "White Coat Ceremony" back then), but I remember taking my Oath of Office on the day that I accepted my U.S. Navy commission like it was yesterday.  It was a big day for me for sure.  As I reflect more on what my Oath of Office meant to me personally, I can't help but wonder whether our world would be a lot more trusting (and trustworthy) if we used oaths, covenants, and promises more frequently?

Tuesday, November 3, 2026

Let's draw straws!

Today is Election Day in the United States of America.  It's an important day, when we all exercise our responsibility of citizens to vote on our choice for government leaders, at the local, state, and federal level.  While conducting some research for today's post, I went down a surprisingly deep rabbit hole when I looked up whether we had a legal right to vote or a duty to vote.  Whether we choose to vote or not is not the subject of today's post.  I will also refrain from entering the debate on whether states should allow early voting, mail-in ballot voting, or require a photo identification in order to vote.  

Today, I wanted to write about a concept known as sortition.  Sortition has roots in ancient Greece and refers to the selection of government officials or jurors at random, in order to obtain a truly representative sample of all stakeholders.  Apparently, ancient Athens in particular used sortition, believing it to be even more democratic than selecting leaders by popular vote.  Sortition is basically similar to the selection method of drawing straws (whoever draws the shortest straw is the leader).  As I look at the current dysfunction in government, I can't help but wonder whether we would be better off choosing our government leaders by sortition.  As it turns out, I am not alone in asking this question (see the article appearing a few years ago on Vox.com, "Can randomly selected citizens govern better than elected officials?").  Similarly, the author and organizational psychologist Adam Grant advocated for sortition in an article that he wrote in The New York Times in 2023 (see "The Worst People Run for Office.  It's Time for a Better Way").  

But I'm not going to write about that in today's post either!  Instead, I wanted to talk about whether we should be using sortition, or something similar, to identify all leaders, not just those in government.  In his NYT article, Adam Grant referred to an older series of experiments published by Alexander Haslam in the journal Group Dynamics: Theory, Research, and Practice (see "Inspecting the Emperor's Clothes: Evidence That Random Selection of Leaders Can Enhance Group Performance").  Haslam and his colleagues found that groups made better decisions when the leaders were chosen at random than when they were elected by the group or based on their skills!

In the first experiment, groups had to imagine that they were stranded on a remote island and were asked to rank in order the items that they would want in order to survive.  Groups chose their leaders via one of three methods - random selection (i.e. sortition), election, or based on reported leadership skill.  The equipment and supplies that each group selected was compared against the gold standard - a list chosen by survival experts.  Groups with a randomly selected leader did much better (i.e. their list of equipment and supplies looked more similar to that of the survival experts) compared to groups in which leaders were elected or selected based upon their leadership expertise.

The second experiment was very similar.  Groups were tasked with coming up with a list of equipment and supplies necessary to survive a nuclear apocalypse.  Again, groups whose leaders were selected randomly did much better at the task compared to those groups in which leaders were elected or selected based upon their leadership expertise.

If these results seem counterintuitive, it's because they are (which Haslam and colleagues showed in their third experiment).  In a small group scenario, we generally believe that groups will perform better when the leaders are selected by vote (probably the most common scenario) or based upon their expertise, knowledge, and skills.  The results of these experiments suggest otherwise!

I should also mention a study published by a group of investigators working with the National Bureau of Economic Research (NBER) (see "How do you find a good manager?").  These investigators found that individuals who aggressively campaign for a group leadership position perform worse than group leaders selected at random.  Self-nominated leaders, at least in this study, tended to be overconfident, particularly in regards to their leadership and social skills.  

So, what should we conclude from these studies?  Is Adam Grant on to something here?  Should we be selecting our leaders at random?  I think it's difficult to extrapolate small group performance to a more macro level, like the organization.  I don't think we will be randomly selecting corporate CEO's anytime soon, and that's probably a good thing.  However, when it comes to smaller teams, perhaps we should be selecting our group leaders by random, say by drawing straws!  We at least should beware of individuals who campaign for the group leader position.

I will conclude today's post with a simple request.  Please go out and vote today.  It's an important responsibility for all of us, and every vote counts.

Monday, November 2, 2026

The Producer's Button

You probably know of Leland Sklar, even if his name doesn't ring a bell.  Well, you probably know of him if you are around my age or listen to classic rock music.  Leland Sklar is a famous bass player who is perhaps most famous for playing in James Taylor's band, but he has also toured or recorded in the studio with artists such as Linda Ronstadt, Phil Collins, Jackson Browne, Toto, The Doors, and Carole King.  Oh, and he even played bass on a number of television song tracks from the 1970's and 1980's, including The Rockford Files, Magnum, P.I., Hill Street Blues, The A-Team, to name a few.  He is a musical legend!

I mention Sklar, as there is a post that is making it's way around the Internet, in which he claims to have used what he calls the "Producer's Switch" on his bass guitar.  I am always skeptical of what I read on social media, but the story turns out to be true (I fact-checked with a number of sources, including "Guitar World" magazine and a website called "Ultimate Guitar" - there's even a live interview on YouTube in which Sklar tells the story).  Basically, the "Producer's Switch" is a dummy toggle switch on his bass guitar that does absolutely nothing!  Sklar says, "If I’m on a session and the producer asks me to get a different sound, I make sure he sees me flip this switch and then I just change my hand position a bit. There are no wires of anything that go to this switch. It's a placebo, but it’s saved me a lot of grief in the studio."  The producer invariably believes that the switch changed the sound to his or her liking and almost always approves.  Sklar has used the "Producer's Switch" for over a decade, and it has become a famous signature feature on his custom German-made Warwick Star Bass.

It's actually a funny story.  But as I thought about it more, I had to ask myself how many times leaders inadvertently created something similar to the "Producer's Switch" in their organizations.  In other words, as leaders, we should be asking ourselves, "How many times have our teams developed something to basically give us the information that they think we want to hear or see?"  Or worse, how many times have our teams created the metaphorical "Producer's Switch" in an attempt to make us feel like we were in control of the situation?

There's no question that teams develop workarounds, shortcuts, or sometimes, even a "Producer's Switch".  All of these indicate the presence of friction in the workplace, whether due to an inefficient process, bureaucratic hassle, or even micromanagement by the leader.  While these quick fix interventions may at least resolve the initial problem at hand, in the end they actually harm the organization.  As John Burns writes in his blog post (see "When Workarounds Become Workflow: How Small Exceptions Become Systemic Failures"), "Over time, these workarounds start to shape workflows, and before you know it, the entire system is running on exceptions, not standards."  This is not how High Reliability Organizations are supposed to work!

One of the biggest drawbacks to workarounds (and shortcuts) is that the root problem is not addressed.  The workaround effectively sacrifices long-term efficiency for the immediate term - it's a temporary fix to a much bigger problem.  Just as important, the workaround is rarely documented or codified in a standard operating procedure (SOP) or policy.  When team members leave, a new team member is trained on the "official" SOP but not the "unofficial" workaround.  Problems then ensue.  Notably, this particular issue played a major role in the famous "Friendly Fire" accident during Operation Provide Comfort in 1994, discussed at length in Scott Snook's book of the same name.  

In a similar way, the "Producer's Switch" doesn't change the leader's behavior.  It's another example of a short-term "fix" substituting for a longer term issue or problem.  Rather than addressing the issue, the team has effectively created a workaround.  

Workarounds, shortcuts, and the "Producer's Switch" collectively create hidden risk, wasted resources, and erosion of trust.  Leaders should find out how the work is really done, not how it is set forth in SOPs and organizational policies.  They should seek feedback from their teams on how things are really operating, and set clear expectations that if a process is not working effectively, it should be changed.  Finally, leaders need to create environments of psychological safety, where team members can raise their concerns, provide feedback, and at times even openly disagree with the leader.

The last thing I will say about Sklar's "Producer's Switch" is that the both Sklar and the producers in question are neglecting the HRO principle of "Deference to Expertise".  The producers in question fail to acknowledge that Sklar is a professional with expertise in his craft.  On the flip side, Sklar is failing to acknowledge that the producer is also a professional with expertise in his or her craft.  One would hope that in a psychologically safe environment, both the producer and the musician could have had a productive conversation about their shared goals, as well as their individual ones.  It's a funny story nevertheless, but one with a great lesson for all of us in leadership.