A Community Guide to working with Aquisitions

Introduction

The traditional U.S. military acquisition system can be slow, bureaucratic, and overly complex. This has led to significant inefficiencies in fielding necessary capabilities promptly. In contrast, conflict zones like Ukraine have demonstrated the effectiveness of an agile approach—rapidly deploying and refining technology based on real-time needs.

This guide is designed to help service members understand how they can influence the acquisition process, write better requirements, and push for necessary changes to streamline procurement and fielding efforts.

For training in this lane see Learning#Defense_Acquisition_University_(DAU)

Understanding the Problem

The current acquisition process is dominated by:

• Waterfall Planning – Long, inflexible cycles prioritizing predictability over adaptability.
• Unrealistic Requirements – Complex, contradictory requirements delay progress.
• Bureaucratic Bottlenecks – Lengthy approvals, redundant oversight, and outdated policies.
• Siloed Efforts – Lack of interoperability between systems and service branches.
• Institutional Resistance – A culture of risk aversion that discourages rapid iteration and innovation.

If you are frustrated with these issues, the good news is that you can do something about it.

What You Can Do

1. Write Better Requirements

• Keep requirements simple, clear, and focused on solving a specific problem.
• Avoid creating "do-it-all" systems that try to fulfill every need but end up being ineffective.
• Use objective-based requirements instead of hard specifications.
• Look at the USMC model—reducing a 200-requirement system to a two-page Statement of Need reduced development costs by 40% and unit costs by 25-30%.

2. Push for Rapid Prototyping and Field Testing

• Utilize Tactical Innovation and Combat Initiatives (TiC) to test solutions in the field.
• Work with program offices to bypass bureaucratic delays.
• Challenge outdated testing and evaluation requirements under DOT&E oversight.

3. Demand Interoperability Standards

• Advocate for plug-and-play architectures that prevent vendor lock-in.
• Push for standardized software, cabling, and networking frameworks.
• Reference standards such as:
  • MIL-STD-2525 (military symbology and data structures)
  • Joint sUAS CDD (requirements for joint UAS interoperability)

4. Use Existing Rapid Acquisition Pathways

• Joint Urgent Operational Need Statements (JUONS) & Joint Emergent Operational Need Statements (JEONS) – Accelerate fielding for urgent requirements.
• SOCOM DIR 71-4 – Provides a streamlined process for rapid prototyping.
• APFIT (Accelerated Procurement Funding for Innovative Technologies) – A funding stream for cutting-edge solutions.
• SORRD (Special Operations Rapid Requirements Development) – An alternative pathway for rapid fielding.

5. Engage Your Acquisition Personnel

• Find your TRADOC Capability Developer, Program Office POC, or G8/S8 representative.
• Write and submit an Unfunded Requirement Justification for critical needs.
• Use existing mechanisms such as SOF RAPTOR IV (SR-IV) IDIQ to fund innovative technologies.

6. Break Down Cultural Resistance

• Educate leadership on successful rapid acquisition models.
• Push for an iterative development approach rather than waiting for "perfect" solutions.
• Highlight past failures of rigid acquisitions (e.g., IVAS receiving $20B but still facing major usability issues).

Questions That Need Answers

The following are key acquisition issues that remain unresolved:

• How can we consolidate Joint COP tools to eliminate redundant, non-communicating systems?
• What is the best approach to accelerate DOT&E oversight for rapid fielding?
• How do we enforce interoperability across service branches to prevent silos?
• What are specific examples of bad requirements, and how should they be fixed?

Actionable Steps for Every Service Member

| Step | Action | |---------|----------| | 1. Find Your Acquisition POC | Identify who in your command is responsible for requirements and procurement. | | 2. Write a Simple, Focused Requirement | Use the USMC model or SORRD format—avoid overcomplicated specifications. | | 3. Push for Field Testing | Advocate for TiC initiatives and rapid prototyping under SOCOM DIR 71-4. | | 4. Use Rapid Acquisition Pathways | Submit JUONS/JEONS, APFIT proposals, or utilize SORRD for rapid fielding. | | 5. Enforce Interoperability Standards | Ensure all new tech aligns with Joint sUAS CDD, MIL-STD-2525, and government-owned architectures. | | 6. Educate Your Leadership | Present successful case studies (e.g., Marine Corps rapid acquisition model). |

Conclusion

The acquisition process can be slow and frustrating, but real change is possible when capability developers, warfighters, and leadership work together. By writing clear, focused requirements, pushing for rapid prototyping, and leveraging existing rapid acquisition channels, service members can cut through bureaucracy and ensure our forces get the capabilities they need—when they need them.

If every service member reading this guide takes just one step on Monday—whether it’s finding their acquisition contact, submitting an unfunded requirement, or challenging outdated processes—we will move the needle toward a more agile, responsive, and effective military acquisition system.