There is a particular kind of frustration that comes with watching someone else accomplish a task differently than you would have done it. You gave clear guidance. You explained what needed to happen. You provided the resources, established the timeline, and identified the desired outcome. Then you stepped back and watched as your subordinate took an approach that seemed unnecessarily complicated, inefficient, or simply wrong. You knew a better way. You had done it before, perhaps dozens of times, and you could have saved everyone considerable time and effort by explaining exactly how to do it. So you stepped in, corrected the approach, and showed them how it should be done.
Congratulations. You may have improved the immediate outcome, but you might also have missed an opportunity to develop a leader.
One of the most difficult lessons for experienced leaders to learn is that their preferred way of accomplishing a task is not necessarily the only acceptable way, or even the best way. Experience provides perspective, but it can also create rigidity. The more successful we become, the more likely we are to confuse the methods that worked for us with the methods that must work for everyone else. Eventually, we begin to mistake our personal preferences for professional standards. We stop evaluating whether our subordinates are achieving the desired results and start evaluating whether they are achieving those results the way we would have.
That distinction matters enormously, particularly in organizations that claim to value initiative, adaptability, and the development of future leaders.
Mission Command Is More Than a Doctrinal Catchphrase
The United States Army’s philosophy of mission command is built around a deceptively simple idea: commanders should tell their subordinates what needs to be accomplished and why, while allowing them the freedom to determine how best to accomplish it. Army Doctrine Publication 6-0, Mission Command: Command and Control of Army Forces, emphasizes, among other things, the exercise of disciplined initiative within the commander’s intent, supported by mutual trust, shared understanding, and the acceptance of prudent risk.
Those principles sound straightforward in a classroom. They become considerably more difficult when a subordinate makes a decision that a senior leader would not have made. Mission command requires leaders to surrender a degree of control, and that is uncomfortable for people who have spent their careers being rewarded for making good decisions. It requires accepting that subordinates will occasionally make mistakes, take inefficient approaches, or produce results that fall short of what an experienced leader might have achieved personally. More importantly, it requires understanding that those imperfections are not necessarily evidence of failure. Sometimes, they are the price of developing independent judgment.
The purpose of mission command is not to create a force of subordinates who can perfectly replicate their commander’s thought processes. It is to create a force of leaders who can understand an objective, assess changing circumstances, make sound decisions, and act without waiting for someone else to tell them what to do.
That cannot happen if every decision is made for them.
The Difference Between Standards and Preferences
There is an important distinction between accepting something that is good enough and accepting something that is inadequate. Leaders have an obligation to establish and enforce standards. Safety, ethics, legality, operational effectiveness, and mission accomplishment are not optional considerations. A commander who tolerates unnecessary risk, poor discipline, or substandard performance under the guise of empowering subordinates is not practicing mission command. That commander is simply failing to lead.
But standards and preferences are not the same thing.
Suppose a platoon leader is tasked with establishing a defensive position. The company commander provides the mission, identifies the critical terrain, explains the purpose of the defense, establishes necessary control measures, and communicates the desired end state. The platoon leader then develops a plan that satisfies those requirements but organizes the defense differently than the company commander would have preferred.
If the plan is tactically sound, accomplishes the mission, and remains within the commander’s intent, what exactly is gained by forcing the platoon leader to change it?
Perhaps the company commander’s preferred approach is marginally better. Perhaps it is significantly better. But unless the difference materially affects mission accomplishment or creates unacceptable risk, the commander should consider whether imposing that preference is worth the developmental cost.
The same principle applies outside the military. A business leader assigns a project to a junior manager, provides clear objectives, establishes a deadline, and explains the desired results. The manager develops a workable plan that is different from the one the boss envisioned. If the boss immediately intervenes to dictate the process, the organization may get a slightly better product in the short term, but it also gets an employee who has learned that independent thinking is less important than anticipating the boss’s preferences. Over time, that becomes an expensive lesson for the organization.
The Tyranny of Narrow Left and Right Limits
Military leaders frequently establish “left and right limits” to define the boundaries within which subordinates may exercise initiative. Properly employed, these limits provide essential clarity. They identify constraints, protect against unacceptable risks, and help ensure that decentralized actions remain consistent with the larger mission. But there is a point at which guidance becomes restriction, and restriction becomes micromanagement.
Some leaders establish so many conditions, caveats, approval requirements, and restrictions that their subordinates have almost no meaningful freedom of action. They describe this as providing clear guidance, but what they have actually done is create an elaborate system of centralized control disguised as decentralized execution. The subordinate is technically responsible for accomplishing the mission, but every significant decision has already been made by someone else.
The irony is that these same senior leaders will often complain that their junior officers and NCOs lack initiative. Of course they do. Initiative is a skill that must be exercised to be developed, and it is difficult to develop that skill in an environment where every deviation from the commander’s preferred approach is treated as a mistake.
Leaders cannot simultaneously demand initiative and punish independent judgment simply because it produces an unfamiliar solution. Nor can they reasonably expect subordinates to demonstrate confidence when their decisions are constantly second-guessed, revised, or overridden. When the left and right limits become so narrow that there is only one acceptable path forward, we should stop pretending that we are practicing mission command. We are issuing detailed instructions and expecting compliance. There are circumstances where that approach is necessary, but it should not be confused with developing leaders.
My technique is to make those left and right limits, that “empowerment box” in which my subordinates have to operate, as large as the situation, and their level of competence, allow. Yes, this requires me to assume some level of risk. Yes, I might get a different path to success than the one I would have chosen. But just as often, I’ve been pleasantly surprised by creative outcomes, ones that would not have occurred to me. And it helps me avoid becoming a micromanager.
Micromanagement Is Often Disguised as High Standards
Most micromanagers do not think of themselves as micromanagers. They think of themselves as demanding leaders who insist on excellence. They believe their constant involvement demonstrates commitment, attention to detail, and a refusal to accept mediocrity. Sometimes, that is true. More often, it reveals an inability to distinguish between ensuring a successful outcome and personally controlling every step required to achieve it.
Micromanagement can also emerge from good intentions. A senior leader remembers the mistakes made early in their own career and wants to spare younger subordinates the embarrassment, frustration, or consequences of repeating them. That impulse is understandable, but it overlooks an uncomfortable truth: many of the lessons that made the senior leader successful were learned precisely because someone allowed them to make mistakes. Experience is a valuable teacher partly because its lessons are not always pleasant.
There is also an important difference between coaching and controlling. A good leader asks questions that help subordinates recognize weaknesses in their plans. A micromanager simply replaces the subordinate’s plan with their own. One approach develops judgment; the other develops dependency. And dependency has consequences.
In organizations dominated by overbearing leaders, subordinates eventually learn that the safest course of action is to avoid making decisions. They seek approval for matters that should fall comfortably within their authority. They stop offering unconventional ideas because those ideas are unlikely to survive the approval process. They become skilled at predicting what the boss wants rather than determining what the mission requires.
Eventually, the organization produces exactly the kind of subordinate leaders its senior leadership claims to despise: hesitant, risk-averse, and reluctant to act without explicit direction. Worse, this kind of leadership erodes morale. People want to believe their judgment matters. They want to know that their superiors trust them to perform the responsibilities they have been assigned. When every decision is second-guessed and every minor imperfection becomes an opportunity for correction, even talented and motivated people begin to disengage. They may continue doing their jobs, but they stop taking ownership of them.
Developing Leaders Requires Accepting Imperfection
One of the central responsibilities of leadership is preparing others to lead when we are no longer present. That responsibility requires us to think beyond the immediate task and consider the long-term development of the people entrusted to us. A subordinate who executes a plan perfectly because the boss dictated every detail has demonstrated an ability to follow instructions. That may be useful, but it is not the same as demonstrating leadership.
A subordinate who develops an imperfect plan, recognizes problems, makes adjustments, and ultimately accomplishes the mission has learned something considerably more valuable. They have practiced making decisions, accepting responsibility, adapting to changing circumstances, and living with the consequences of their choices. Those experiences build confidence and competence in ways that detailed instructions never can.
This does not mean leaders should allow subordinates to fail unnecessarily, particularly when lives, significant resources, or critical missions are at stake. The Army’s emphasis on prudent risk exists for a reason. Commanders must balance the potential benefits of subordinate initiative against the consequences of failure, and the acceptable degree of risk will vary considerably depending on the situation.
A training exercise offers opportunities for experimentation that might be inappropriate during a combat operation. An administrative project can tolerate mistakes that would be unacceptable in a live-fire environment. Good leaders understand those distinctions and adjust their involvement accordingly. But the principle remains the same: when the risk is acceptable and the mission can still be accomplished, allowing a subordinate to pursue a different approach may produce greater long-term value than insisting on the theoretically perfect solution.
That is especially true when developing young leaders. The lieutenant who makes a less-than-optimal decision during a field training exercise may become the captain who makes a decisive, independent decision under fire. The junior manager who struggles through a difficult project may become the executive who can navigate a crisis without constant supervision. Neither develops those abilities by spending their formative years executing someone else’s decisions.
Commander’s Intent Should Liberate, Not Constrain
At its best, commander’s intent provides a framework for independent action. It explains the purpose of an operation, identifies the key tasks that must be accomplished, and describes the desired end state. It allows subordinates to understand not merely what they are supposed to do, but why they are doing it. That understanding is what makes disciplined initiative possible.
When circumstances change, communications fail, or the original plan becomes unworkable, subordinates who understand the commander’s intent can adapt their actions without waiting for new instructions. They can recognize opportunities, respond to threats, and continue pursuing the larger objective even when the situation no longer resembles the one envisioned during planning. But none of that matters if the commander has conditioned subordinates to believe that deviation from the original plan will be punished.
Trust must be more than a word in a leadership philosophy. It has to be demonstrated through actual decisions, particularly when a subordinate chooses a course of action that the commander would not have chosen. This is where mission command becomes a test of the senior leader’s character as much as the subordinate’s competence. It is easy to claim that we trust our people when they do exactly what we expect. The real test comes when they do something different.
If the result is acceptable, the mission is accomplished, and the commander’s intent has been satisfied, perhaps the appropriate response is not to explain how we would have done it better. Perhaps the appropriate response is simply to acknowledge that the subordinate made a sound decision and achieved the desired outcome. And then, leave it alone.
Sometimes, Good Enough Really Is Good Enough
There is a tendency among ambitious, high-performing leaders to believe that every task must be executed to the highest possible standard, every process must be optimized, and every result must be improved. That mindset can produce extraordinary individual performance, but it can also become an obstacle to organizational effectiveness. But not every task requires perfection. Not every decision needs to be made by the most experienced person in the room. Not every deviation from the boss’s preferred approach requires correction.
Sometimes, the additional effort required to move a result from good to excellent is justified. Sometimes, the consequences of failure are so significant that close supervision and strict adherence to established procedures are absolutely necessary. But sometimes, the pursuit of marginal improvement costs more than it delivers, especially when that cost includes lost initiative, diminished morale, and missed opportunities to develop future leaders.
The best leaders recognize that distinction. They establish clear expectations, communicate their intent, provide necessary resources, and define meaningful boundaries. They remain available to coach, advise, and intervene when circumstances genuinely require it. But they also have the confidence and discipline to allow their subordinates to exercise judgment, even when that judgment produces a solution different from their own. Most importantly, they understand that developing leaders is itself part of the mission. An organization in which every decision must be made by the boss may function efficiently while the boss is present. It may even produce consistently excellent results. But it is also an organization whose effectiveness depends disproportionately on one individual, and that is a dangerous form of institutional weakness.
Leadership is not about proving that we can do everything better than the people who work for us. It is about developing people who can accomplish the mission without us, and eventually do things better than we ever could. Sometimes, that means watching a subordinate take the long way around. Sometimes, it means accepting a solution that is less elegant, less efficient, or simply different from the one we would have chosen. Sometimes, it means resisting the urge to intervene, even when we are certain that we know a better way. That’s because the goal is not always to produce a perfect result today. Sometimes, the more important goal is to develop a better leader for tomorrow.
And sometimes, “good enough” really is good enough.
_____________________________
Charles served over 27 years in the US Army, which included seven combat tours in Iraq and Afghanistan with various Special Operations Forces units and two stints as an instructor at the United States Military Academy at West Point. He also completed operational tours in Egypt, the Philippines, and the Republic of Korea and earned a Doctor of Business Administration from Temple University as well as a Master of Arts in International Relations from Yale University. He is the owner of The Havok Journal, and the views expressed herein are his own and do not reflect those of the US Government or any other person or entity.
As the Voice of the Veteran Community, The Havok Journal seeks to publish a variety of perspectives on a number of sensitive subjects. Unless specifically noted otherwise, nothing we publish is an official point of view of The Havok Journal or any part of the U.S. government.
Buy Me A Coffee
The Havok Journal seeks to serve as a voice of the Veteran and First Responder communities through a focus on current affairs and articles of interest to the public in general, and the veteran community in particular. We strive to offer timely, current, and informative content, with the occasional piece focused on entertainment. We are continually expanding and striving to improve the readers’ experience.
© 2026 The Havok Journal
The Havok Journal welcomes re-posting of our original content as long as it is done in compliance with our Terms of Use.