“Yes, if,” versus “No, because.”

A Negotiator’s Mindset for Breaking Pentagon Paralysis

In the long corridors of the Pentagon, where competing priorities and entrenched processes often collide, progress can stall not because the answer is wrong—but because the default answer is no. Not a thoughtful no. Not a strategic no. But a knee-jerk, cover-your-backside "No, because..." That three-word phrase, repeated daily across departments and directorates, has killed more good ideas than enemy fire ever could.

But there’s a way out. A mindset shift. A deceptively simple phrase I first encountered during my years in the private sector, negotiating with Japanese manufacturers and industrial partners: "Yes, if..."

This isn’t just a more polite way to say no. It’s a cultural and strategic tool rooted in Japan’s deeply embedded values of harmony, respect, and forward movement. It reframes rejection into possibility. Rather than slamming the door, "Yes, if…”holds it open—just wide enough to talk solutions.

I first came to admire this concept while managing high-stakes production schedules and cost negotiations with Japanese firms. They didn’t default to objections. They countered with conditions. I’d make a proposal that strained timelines or resources. Rather than say, "No, it can’t be done," they’d say, "Yes, if we can realign this team," or "Yes, if delivery slips two weeks." The technique didn’t just soften the blow. It created an instant framework for problem-solving.

I carried that technique with me when I transitioned into public service—first in diplomacy-adjacent security cooperation work, and now as a senior military leader navigating the gnarled bureaucracy of the Department of Defense. At the Air War College, and more recently in the Air National Guard Squadron Commander Course, I’ve taught this mindset block to rising leaders. And again and again, I’ve seen the shift it creates: away from bureaucratic rigidity and toward adaptive execution.

Consider the difference in tone and trajectory:

• “No, because we don’t have an Authority to Operate.”
  — The discussion ends.
• “Yes, if we can secure an interim ATO through the CIO office.”
  — The path opens.
• “No, because it’s not in the POM.”
  — A dead stop.
• “Yes, if we reprogram funds from FY25 or find another sponsor.”
  — A chance to move forward.

When we say "No, because..." we abdicate responsibility. We default to gatekeeping. We protect the system at the expense of the Warfighter. And worst of all, we signal that process is more important than progress.

But when we say "Yes, if...", we shift from rejecting to refining. We force ourselves to think like owners, not custodians. We draw the roadmap for how to say yes—because, frankly, if there’s any way to support the Warfighter within our existing authorities and resources, it’s our duty to find it.

Recently, I was gratified—and validated—when the Honorable Hondo Geurts, a legend in the acquisition community, visited JRAC and echoed this very principle. Without prompting, he emphasized that one of the most powerful tools in government innovation is this shift to "Yes, if…". Coming from a leader who’s driven transformation across the Navy, SOCOM, and beyond, it was a moment of professional convergence. Different sectors, same solution.

This mindset isn’t theoretical. It’s a tool I’ve used negotiating multimillion-dollar contracts in the private sector, hammering out base access deals in allied countries, and fast-tracking urgent acquisitions at the highest levels of defense. It’s also a cornerstone of leadership—because leaders don’t just critique obstacles. They clear them.

If we’re serious about innovation…
If we’re serious about delivering faster…
If we’re serious about winning wars that unfold at machine speed…

Then we must replace "No, because..." with "Yes, if..."

Because momentum matters.
Because trust matters.
Because the Warfighter isn’t waiting for clean staffing packages.

It’s not about being reckless. It’s about being responsible—to the mission. And that starts with owning the solution.