Ryan Tseng 🇺🇸’s Post

View profile for Ryan Tseng 🇺🇸, graphic

Building the world's best AI pilot. Join us!

Gov acquisition processes fail at step 1

  • text
Michael Brabner

Air Branch Chief at US Army

4d

Our emerging requirements for the J-sUAS CDD are less dumb.

Jacob Meade

Sr. Consultant | Aircraft Mechanic | Problem Solver | Powered by ADHD and Coffee!

4d

I would slip one more in there... Actually talk to the people on the ground doing the work, typically they already have a solution to the issue but no one has ever asked them..

Rob Murtha

Using science to design experiences that people need and want.

4d

By the time a Requirement makes its way into an acquisition package, it was influenced and morphed by a variety of individuals that are contextually detached from the building/creation of the thing they need. Requirements gathering always seems to conflate the “what”, “why”, and “how” — you have “SMEs” that understand the “why” really well, providing input on the “how” and it turns the Requirement definition into an inaccurate disaster. The Requirement becomes impossible to understand, fund, and build. I recommend managing context and input effectively during the Requirement development process; introduce self-awareness across the team that recognizes the “risk of the unknown” and the chaotic variables that an environment throws at an engineering initiative. Build that flexibility into the acquisition.

Vanishree Shivakumar

Senior Director, Ralph Lauren

4d

Love step 2… in many private and public sectors, there are too many edge cost centers, edge systems, edge procedures .. but no edge … actually drives people to the edge rather… bluntly put, gotta cut the edge to be cutting edge!! 😂

DoD will soon be unrecognizable in a great way (see as Vivek and Elon make this look like a business versus a good old greasing palms setup) I can’t even imagine any great successful company say “we need to pick vendor A because they check a box not they are the best vendor!). Billions saved in DoD and it will be fine tuned and run XX times better for it

Dave F.

USMC Veteran | Unmanned Aviation Executive | Growth Enabler | Board Member

4d

On this we can agree.

It fails at step 0: allow gov to craft the requirement The Gov (to include DoD) needs to stay out of engineering and IT because they can't do it well. . . let them govern (policy) and fight (DoD)

Like
Reply

Talk to the people performing the end tasks/processes before defining requirements. Having individuals two and three steps removed from reality when creating requirements is one of the many reasons they often miss the mark.

See more comments

To view or add a comment, sign in

Explore topics