Department of Defense

A software closed loop user feedback process.

Make a policy or law requiring a closed loop user feedback process for new, current and future Government Information Systems (software). This would provide Lean Six Sigma quantifiable data for senior leader decision makers. Not what the vendors, contractors think.


As software products are developed this will ensure the feedback is collected by a closed loop system to measure the usage, effectiveness and correct issues along the way giving senior leadership accurate correct measureable data (metrics). In a real time environment! This is nested with the fifth element of combat power “INFORMATION”. Accurate information not only saves money it increases the speed and quality of decision making using the Military Decision Making Process (MDMP). Everyone WINS!


Google, Microsoft, Toyota, Ford, GM, Chrysler, KIA, Mazda just to mention a few use closed processes.


Feedback drives change: organizational and cultural change that produces growth and profit, driving superior business performance. Voice of the Customer research with a closed loop gets us out of the research business and into the operational business, giving us great opportunities. Department of Defense (DOD) Net-Centric Data strategy in 2003 mentioned users feedback. But had no detailed plan to collect or measure the effeteness of the software product. The current DOD Net-Centric Data Transformation plan has To Be Determined (TBD) in the metric column.


User feedback in a closed loop process will provide measurable data to determine the success of the development team and Software.


The country’s been at War for 10 years. Senior leaders are being taken advantage of by bad information presented in PowerPoint presentations. No metrics! Government employees using the software will NOT tell a lie! Project managers, vendors are and will continue until we do what the industry does! Listen to the people!


175 votes

I agree to have my idea, not my name or information, posted online. YES


Idea No. 248