What Business Executives Can Learn from National Security Strategy

I spent decades operating inside the United States Intelligence Community — an environment where the cost of a wrong decision is not a missed quarter or a lost contract. It is measured in lives, in national sovereignty, in the security of millions of people who will never know your name.

That kind of pressure clarifies thinking in ways that no MBA program can replicate.

The frameworks, disciplines, and mental models forged in that environment are not classified. They are not reserved for generals and cabinet secretaries. They belong in every boardroom in America — and most executives have never encountered them.

Here are the ones that matter most.

In business, the words "risk" and "uncertainty" are used interchangeably. In national security, that imprecision can get people killed.

Risk is a known unknown. You can assign a probability to it. You can model it, hedge against it, buy insurance for it. A cyberattack on your infrastructure is a risk. A recession is a risk. A competitor launching a new product is a risk.

Uncertainty is an unknown unknown. You cannot assign a probability because you do not know what you do not know. The emergence of a new technology paradigm is uncertainty. A black swan geopolitical event is uncertainty. The COVID-19 pandemic was uncertainty.

The intelligence community treats these two categories with entirely different tools. Risk gets quantitative analysis. Uncertainty gets scenario planning, red teaming, and pre-mortem analysis.

Most businesses apply risk management tools to uncertainty problems — and wonder why they keep getting blindsided.

The fix: Build two parallel planning processes. One for managing known risks. One for stress-testing your strategy against scenarios you have not imagined yet. The second process is the one most organizations skip.

In the intelligence community, we have a concept called all-source intelligence — the integration of signals intelligence, human intelligence, imagery intelligence, open-source intelligence, and more into a single coherent picture.

The reason is simple: no single source tells the whole story. SIGINT tells you what someone said. HUMINT tells you what they meant. Imagery tells you what they built. Open source tells you what they want you to believe. Only when you fuse all of it together do you approach something resembling truth.

Your organization has the same problem, and almost no one solves it.

Your sales team has intelligence about customer behavior. Your finance team has intelligence about cost structures. Your operations team has intelligence about process failures. Your frontline employees have intelligence about what is actually happening versus what the dashboard says.

But in most organizations, these streams never converge. Strategy is made from partial pictures. Decisions are made from single-source reporting.

The fix: Create deliberate mechanisms for cross-functional intelligence fusion. Not just quarterly business reviews where each silo presents its own data. Structured sessions where disparate data streams are synthesized into a unified operational picture — and where the gaps and contradictions are surfaced, not smoothed over.

Red teaming is one of the most powerful and least-used tools in strategic planning.

In the military and intelligence communities, a red team is a dedicated group whose job is to think like your adversary — to find the holes in your plan, exploit your assumptions, and identify the ways your strategy could fail before you execute it.

The red team is not there to validate your thinking. They are there to destroy it. And if they cannot destroy it, you have earned more confidence in your plan.

I have seen red teams save operations that would have been catastrophic. I have also seen commanders ignore their red teams — and pay the price.

In business, the equivalent is almost never done rigorously. Strategy sessions are dominated by confirmation bias. The people in the room are invested in the plan. Dissent is socially costly. The result is a strategy that has never been seriously challenged before it meets reality.

The fix: Before any major strategic initiative, convene a formal red team. Give them the plan, give them time, and give them explicit permission — even a mandate — to find every way it could fail. Bring in outside perspectives. Reward the people who find the fatal flaws before you launch.

The intelligence community operates on a disciplined cycle: Direction → Collection → Processing → Analysis → Dissemination → Feedback.

Every step matters. Most organizations only do two of them.

They collect enormous amounts of data. And then they skip directly to dissemination — sharing dashboards and reports — without ever doing the hard work of processing and analysis.

Processing means cleaning, organizing, and contextualizing raw data. Analysis means applying judgment, expertise, and critical thinking to extract meaning. These are not automated steps. They require human intelligence — the kind that understands context, history, and the difference between correlation and causation.

The result of skipping these steps is what I call "data-rich, insight-poor" organizations. They have more information than they can process and less understanding than they need to act.

The fix: Invest in analysis, not just data collection. Hire or develop people whose job is to synthesize information and produce actionable insights — not just report numbers. Create a feedback loop that tells you whether your intelligence is actually improving your decisions.

In the intelligence community, information is compartmentalized on a strict need-to-know basis. Not everyone gets access to everything. This protects sources, methods, and operational security.

But over-compartmentalization is its own failure mode. When the left hand does not know what the right hand is doing, you get the kind of intelligence failures that led to 9/11 — where critical pieces of information existed in the system but were never connected because the people who needed to see them did not have access.

Business organizations make both mistakes simultaneously. They over-share information that should be protected — competitive strategy, personnel decisions, financial projections — while under-sharing operational intelligence that would help frontline teams make better decisions.

The fix: Audit your information architecture. Ask two questions: What information are we protecting that should be more widely shared? And what information are we sharing broadly that creates risk? The answers will surprise you.

The deepest lesson I carry from the intelligence community is not a framework or a tool. It is a mindset.

In national security, you are always operating under time pressure, with incomplete information, against an adversary who is actively trying to deceive you. You cannot wait for certainty. You cannot afford paralysis. You must make the best decision possible with what you have, execute it with discipline, and adapt as new information emerges.

That is not a military problem. That is the condition of every business leader operating in a competitive market.

The executives who thrive are the ones who have internalized this reality — who have built the mental models, the organizational processes, and the personal discipline to operate effectively in ambiguity.

The ones who struggle are still waiting for certainty that will never come.

MG (Ret.) Pete Gallagher is the founder of Six Eight Alliance LLC. He spent decades at the intersection of national security and organizational leadership, advising senior government officials and business executives. To explore how these frameworks can be applied in your organization, reach out today.