NavalX reposted this
Focus on capabilities, not requirements. Unlock the huge potential of the non-traditional defense tech companies by adequately defining the problem sets the Navy and Marine Corps have today and as well as tomorrow. At NavalX, this is one of the focus areas we are working towards -- getting an appropriately detailed, formatted, and consistent problem statement, entered in a common database so it is searchable and can be matched to the plethora of non-traditional defense industry technologies, many dual-use commercial and defense solutions! Can we shout this louder? Let's Go! Noam Oz Scott Bewley Graham "Gray" Chynoweth Carrie Lake Jamie Dean William Treseder
1000% agree. Often the requirement don’t addres the underlying issue or problem that needs to be solved. Somewhere in the mosh pit of bureaucracy involving senior staff and the pretorian guard of the acquisition cadre, the underlying problem sets are forgotten - sometimes pursuing requirements/solution that miss the mark. https://lnkd.in/e8gwe7zA
We agree, and that is the premise behind the establishment of Battlelab
I’m still entertained that when we started running innovation challenges against a problem statement, many in the industry still wanted the requirement statement. With some even formally complaining that we wouldn’t provide a requirement document. We’ve proved this is a better way, especially when the solution requires specialist knowledge not always found in the Defence team.
Joel Uzarski 100% you nailed it. That’s why I’m so excited about your fleet focused efforts at NavalX!
100%
Technology, defense policy and international defense reporter. Emmy award winner.
1moVery attractive insight. Would you say that smaller organizations are better at keeping focus on the warfighter and larger enterprises tend to digress toward requirements Joel Uzarski?