Strategic Foresight: Identifying Future DoD Needs

Advanced

strategic-leadership innovation market-research strategic-foresight

Strategic Foresight: Identifying Future DoD Needs

Here’s the hard truth: By the time you see the RFP, you’ve already lost.

I’ve spent over two decades in Air Force acquisition—sitting on both sides of the table, writing requirements, managing programs, watching billions in taxpayer dollars move through the system. And I’ll tell you what separates the contractors who build lasting value from those who chase revenue: foresight.

Most companies in this industry are operating backward. They’re waiting forSAM.gov notifications, scrambling for teaming agreements two weeks before proposal due dates, and wondering why their win rates hover in the single digits. They’re tactical actors in a strategic game they don’t understand.

This isn’t about being smarter. It’s about seeing the battlefield before the fight starts.

Let me walk you through how we do this at Craftsman Leadership—how we identify needs before they become requirements, influence strategy before it solidifies into budgets, and position ourselves not as vendors, but as strategic partners in the defense ecosystem.

Strategic Foundations (Think): Understanding the Defense Planning Horizon

The Department of Defense doesn’t wake up and decide to buy things. It operates on a rigid, predictable, and utterly unforgiving planning cycle that stretches years into the future. Your job isn’t to understand today’s acquisition; it’s to understand the capability gap that will exist three to five years from now.

The Architecture of Need

The DoD generates requirements through the Joint Capabilities Integration and Development System (JCIDS). This isn’t bureaucratic alphabet soup—this is where warfighting capability gaps get identified, validated, and prioritized. But here’s what most contractors miss: The gap exists before the JCIDS process starts. By the time a Capability-Based Assessment is published, the conceptual framework is already solidifying.

Strategic foresight requires you to operate left of need—upstream from the formal requirements process. This means understanding the National Defense Strategy, the Capstone Concept for Joint Operations, and the specific Integrated Priorities Lists (IPLs) coming out of the Combatant Commands (COCOMs).

When I was managing acquisition portfolios at the major command level, the contractors who got my attention weren’t the ones responding to my RFIs. They were the ones who had read the same strategic documents I had—and were already floating operational concepts that solved problems I hadn’t yet formalized into requirements documents.

Strategic Patience in Market Development

This is where most business development teams fracture. Strategic foresight requires patience. You’re building relationships and conceptual frameworks for needs that won’t hit the budget cycle for 18-36 months. That feels like an eternity when quarterly revenue targets are breathing down your neck. But understand this: The defense acquisition timeline is glacial, but inexorable. Once a requirement hits the Program Objective Memorandum (POM), the train has left the station.

Partners—not products—understand that influencing Phase 0 (Concept Refinement) pays dividends in Phase 2 (Engineering and Manufacturing Development) while product-pushers fight for scraps in Phase 3 (Production and Deployment).

Innovation Within Constraints

The Pentagon doesn’t need disruptive technology for the sake of disruption. It needs innovation within the constraints of military utility, interoperability, and sustainment. Strategic foresight means understanding not what could be built, but what should be built given the operational environment, existing infrastructure, and budget reality.

When you analyze future needs, you must think in terms of capability portfolios, not point solutions. The Air Force isn’t buying a drone; it’s buying distributed sensing architectures. The Army isn’t buying software; it’s buying decision advantage at the tactical edge. If you’re thinking in terms of your product catalog, you’re already irrelevant.

Operational Leadership (Lead): Building Your Foresight Infrastructure

Thinking strategically is worthless if you can’t operationalize it into action. This requires building systems—not just having insights, but creating the organizational capability to generate, validate, and act on foresight consistently.

The Buyer’s Perspective: How Requirements Actually Emerge

Let me pull back the curtain from my time in uniform. Requirements don’t emerge from immaculate conception. They come from warfighters who encounter friction in training or operations, from analysts watching adversary capability developments, from technologists seeing commercial applications, and yes—from contractors who understand the mission well enough to articulate unmet needs better than the customer can.

The most valuable contractors I worked with operated as embedded strategists. They attended the same professional military education courses I did. They read the same Joint Vision documents. They attended industry days not to pitch, but to listen for the unstated assumptions behind the questions being asked.

When a Program Manager asks about modularity, they’re usually wrestling with obsolescence management and spiral development. When they ask about open architectures, they’re fighting vendor lock-in from the last generation. When they emphasize “speed of relevance,” they’re reacting to a failure in the traditional acquisition system’s ability to pace the threat.

Your foresight infrastructure needs to map the decision-making ecosystem, not just the contracting chain. Who writes the Concepts of Operations (CONOPS)? Who chairs the working groups that feed the Joint Requirements Oversight Council (JROC)? Who actually controls the experimentation budget that validates new approaches?

These aren’t the contracting officers. These are the operational users, the capability analysts, the experimentation leads. These relationships require investment years before the requirement formalizes.

The Three Horizons of Defense Intelligence

Operationalize your foresight through systematic horizon scanning:

Horizon 1 (0-2 years): Budget Execution

  • Analyze unfunded priorities lists (UPLs) from each service
  • Track Congressional markups and plus-ups
  • Monitor Middle Tier Acquisition (MTA) and Other Transaction Authority (OTA) activity
  • Watch for rapid capability office (RCO) investments

Horizon 2 (2-5 years): Program Development

  • Track POM submissions andprogrammatic decisions
  • Monitor Analysis of Alternatives (AoA) milestones
  • Follow Science and Technology (S&T) investment portfolios
  • Analyze COCOM war game results (unclassified summaries often reveal capability emphases)

Horizon 3 (5+ years): Strategic Concept

  • Monitor Advanced Technology Demonstrations (ATDs)
  • Track DoD Research and Engineering Enterprise priorities
  • Analyze Great Power Competition posture adjustments
  • Watch for shifts in overseas contingency operations driving modernization backlogs

Values-based decisions mean you don’t chase every opportunity. You identify where your expertise genuinely aligns with strategic direction, then have the discipline to ignore the rest. Strategic patience means saying no to the RFP today so you can own the market segment tomorrow.

Tactical Execution (Do): Converting Foresight into Contract Reality

Insight without action is just academic exercise. Here’s how you move from knowing what the DoD will need to actually influencing what they buy and winning the work when it materializes.

The Intelligence Collection Plan

You need a systematic approach to gathering foresight data:

  1. Financial Forensics: Don’t just look at the President’s Budget. Look at the RDT&E (Research, Development, Test, and Evaluation) budget lines moving between budget activities. Money moving from BA 6 (RDT&E Management Support) to BA 4 (Advanced Component Development and Prototypes) signals maturation. Money disappearing from BA 2 (Applied Research) into classified SAPs (Special Access Programs) signals operational urgency.

  2. Personnel Tracking: Set up alerts for key personnel movements. When a new Deputy Assistant Secretary or Program Executive Officer takes office, read their last Congressional testimony or published articles. When operators rotate from combatant commands to the Pentagon, they bring operational imperatives that become budget priorities.

  3. Experimentation Hooks: DoD pours billions into experimentation—Rapid Prototyping Events, Project Convergence, Northern Edge, Emerald Flag. These aren’t just demonstrations; they’re requirement generators. Get your technology into these events, not to sell, but to learn. The feedback you gather here shapes the real requirement.

The “Requirement Shaping” Playbook

Once you identify the emerging need, you must shape the requirement before it solidifies. This isn’t unethical influence; it’s professional education. Most government customers don’t know what’s technically possible until industry tells them—and whoever frames the solution space often frames the competition.

  1. White Paper Campaigns: Write unsolicited white papers that address capability gaps, not products. Cite the same strategic documents your customer is reading. Articulate the operational problem better than they have. End with “For further discussion” contact information, not a sales pitch.

  2. Subject Matter Exchange: Offer to brief working groups on commercial best practices relevant to their capability gaps. This positions you as a thought partner, not a bidder.

  3. Prototype Prior to Production: If possible, invest in internal R&D to demonstrate concepts before government funding appears. This proves feasibility and reduces perceived risk when the formal requirement emerges.

The Capture Strategy Timeline

Advanced foresight requires adjusted capture timelines:

  • 36 Months Out: Relationship establishment, concept development, stakeholder mapping
  • 24 Months Out: Requirements influence, AoA participation, white paper submission
  • 18 Months Out: Draft solicitation monitoring, team structure validation, gap analysis
  • 12 Months Out: Capture team activation, solution architecture refinement, color team reviews
  • 6 Months Out: Proposal development, competitive intelligence, final teaming

Notice where the heavy lifting happens? In the first half of that timeline, when “nothing is happening” according to SAM.gov.

Strategic Takeaways: The Craftsman Leadership Position on Foresight

1. Partners Invest in Understanding; Vendors React to Announcements If your market intelligence comes from FedBizOpps, you’re a vendor. If it comes from reading the same strategy documents the Joint Staff reads, you’re a partner. Choose which you want to be.

2. Strategic Patience Requires Organizational Fortitude Your BD team will pressure you to chase revenue today. Your board will question the ROI on “relationship building” with no contract vehicle in sight. Hold the line. The contracts won through foresight have higher margins and longer tails than those won through lowest-price technically acceptable responses.

3. Innovation Within Constraints Is the Only Innovation That Matters The DoD doesn’t need your Silicon Valley disruption fever dream. It needs capabilities that work in contested logistics environments, with intermittent connectivity, operated by 19-year-old maintainers, against peer adversaries. Design for that reality, not the demo.

4. Values-Based Foresight Means Ethical Boundaries Don’t use foresight to create requirements that only your proprietary solution can meet. Don’t exploit understanding of classified gaps to front-run acquisition strategies. Use your insight to solve real national security problems, not to engineer vendor lock-in. The craftsman builds worthily; he doesn’t manipulate the blueprint to ensure only his tools fit.

5. The Ultimate Competitive Advantage Is Seeing the Board Government contracting isn’t won in proposal rooms. It’s won in the years preceding the RFP, when you’ve already shaped the requirement, educated the customer, and positioned your solution as the logical answer to a problem you helped them articulate.

Strategic foresight isn’t a business development tactic. It’s a leadership discipline. It requires you to care more about the mission outcome than the contract award, to think in terms of capability gaps rather than product features, and to accept that the most important decisions you make this quarter won’t show revenue impact for years.

That’s the Craftsman way. We don’t chase contracts. We anticipate needs. We build partnerships. We deliver value.

Now get to work. The warfighter’s next capability gap isn’t going to identify itself.