“It is not enough to do your best; you must know what to do, and then do your best.”
— W. Edwards Deming

I first encountered the second step of the Military Decision-Making Process (MDMP) as a staff officer with a Michigan National Guard cavalry squadron preparing to deploy in support of Operation Iraqi Freedom. As I shared in my previous post on Step 1: Receipt of Mission, I didn’t take it seriously at first, and my inattention to detail showed. It was a lesson I took to heart—and one that I’ve shared often in my work at the community college: researching a problem and paying attention to detail early in the decision-making process matters as much, or more, than anything else you will do.
In the military, the second step of MDMP is called Mission Analysis (MA). We call it that because in Step 1 we receive a mission from higher headquarters. In higher education, what usually happens in Step 1 is that a problem—or opportunity—is identified. What some of us have been practicing at my college is something similar: problem analysis.
We conclude this step with a mission statement that we craft from our analysis and the problem statement we were given in Step 1. In the Army, Mission Analysis begins with inputs such as the higher headquarters’ order, any initial guidance from the commander, details about the area of operations, relevant higher-level information, and current data about your unit (often called “running estimates”).
These inputs can be voluminous. With this information, the commander’s team goes to work. That team includes personnel, intelligence, operations, communications, and logistics staff—as well as the chaplain, engineers, civil affairs, and anyone else with relevant expertise. Under the leadership of the battalion (or squadron) executive officer, this group prepares a formal briefing for the commander.
Leaving the commander out of the room at this stage is intentional. The goal is to allow the staff to analyze freely and prepare an organized presentation so that, when briefed, the commander receives the best information possible—and can ask informed, targeted questions of a well-prepared team.
When the time allotted for Mission Analysis ends, the staff conducts the Mission Analysis Briefing. When I served on that cavalry squadron staff, this was the most comprehensive briefing in the entire MDMP process—and one we constantly referred back to during later stages. It included the area of operations and interest, anticipated weather, enemy forces, civil considerations, and the friendly forces situation, among many other factors. We also briefed key facts and assumptions, critical information requirements, potential risks, constraints, and finally a proposed mission statement and timeline from the present moment through mission execution.

Adapting the Framework to Higher Education
At my community college, we’ve adapted this military model to our own context while keeping its core strengths: disciplined analysis and a shared understanding before moving forward. We call ours a Problem Analysis Briefing. It’s not yet a formal procedure, but more and more teams are beginning to use it.
Our current Problem Analysis Briefing format includes:
- Mission Statement of the College
- The problem statement we’ve been assigned to solve
- Constraints from leadership
- Leadership’s criteria for evaluating proposed solutions
- A proposed decision matrix or rubric for leadership’s use
- Implied tasks
- Available resources internally and externally
- Research and case studies showing how other institutions addressed similar challenges
- Critical facts related to the problem
- Assumptions being made as we frame solutions
- Risks and potential second- and third-order effects of our proposed solutions
- A proposed mission statement to guide us in developing those solutions
Leadership is seated for this briefing and asked to approve the proposed mission statement. As in the Army, approval is not guaranteed—they may ask for more data, modify our language, or even rewrite the statement themselves. Once approved, they may issue updated intent, constraints, or priorities.
Why the Leader Should Stay “Out of the Room”
Just as the commander remains out of the room during Mission Analysis, it’s often wise for the leader to remain out during the Problem Analysis phase. This isn’t about exclusion—it’s about clarity.
When the leader steps back, it allows the team to examine the issue honestly, without shaping their findings around what they think the leader wants to hear. It encourages creative thinking, balanced critique, and a full airing of data and perspectives. When the leader later reenters the process, they encounter a cohesive, prepared team—one that has wrestled with the complexity, organized its findings, and can now brief the leader confidently and clearly.
In both the Army and higher education, that separation builds trust. The leader demonstrates confidence in their team’s analytical ability, and the team, in turn, delivers sharper, more objective insights. The result is the same in both worlds: better understanding leads to better decisions.
And then, just like in the field, we move on to Step 3: Course of Action Development—where artistry and creativity meet the discipline of analysis.
That’s where ideas begin to take shape, built on the firm foundation of shared understanding.




