As the military enters a significant downsizing period, it's important to talk through relevant issues and solutions. Enter your response below, and if it gets the most Up votes, you win a free iPad Mini and we will personally deliver your thoughts to our Advisory Board, which includes retired Generals George Casey and Norton Schwartz, the recent Chiefs of Staff of the Army and Air Force, respectively.<div><br></div><div>Tip: Get all your friends to vote Up your response by the end of the contest on Oct 7, 2013.</div>
Posted 7 y ago
<div>> Retain the top personnel. Spend effort (a team of smart unpaid outsiders, like interns from good schools, who know data analysis, anthropology, industrial engineering) into getting some good data analytics on NCOERs/OERs/deployment experience in order to make a decision on who the low performers will be and who the high performers will be. Pay the high performers to stay and deal with the pains associated with downsizing, and pay the low performers to depart.</div><div><br></div><div>> Get the contractors out of IT/C2 and forget the sunk costs and sunk legacies. CPOF, DTMS, etc. are great ideas troubled with poor understanding and horrible implementation because the input/interface is non-obvious by design. You don't need training to use your iPhone, but even with training it can take a team to figure a CPOF report feature out (this isn't true everywhere obviously)... Our network-centric infrastructure's robustness is dependent upon civilians who work set hours, set days, can be furloughed, and who are invested in bureaucracy; our signal Soldiers down at the battalions lose their rights to fix problems over to higher civilian oversight as a form of reactionary stop-gaps and fears of what those Soldiers could do, because the Army can't afford to pay the contracts necessary to fix the software such that it conforms to the user. Instead, the Soldier must conform to the software's oversight or issue, and we get more new policies and new training. "FRAGO to the FRAGO" and so on in regards to a policy that our E-1s have to be trusted to implement for our own OPSEC... which has a direct impact on our agility. Let units program their own ground-up, low-level databases and queries in a contained cloud to automate and synchronize the administrative stuff and then customize how that query presents to the Soldier! Let units share those products with other units. Open this market to smart Soldiers we have all over the place, not companies that must design the IT/C2 products such that they need eternal maintenance, updates, and field service reps to coax paychecks. 3 Soldiers could make a better, usable DTMS in a year if only they had the space, rights, and we weren't afraid to replace the fragmented network of separated databases that don't communicate. How many databases must my SSN be in...? When Soldiers have IA violations they need to get their certificates again, but the IA training videos are contracted (cost money, cumbersome to change) and not updated to reflect these policy changes upon policy changes - so nothing is learned and time is wasted; it's a punitive solution to a problem that shouldn't exist in any organization that values robustness and agility. Our IT/mission command problems at battalions are pervasive, crippling, and getting sillier every day.</div><div><br></div>
Let all the individuals who want to leave get out, next get rid of everyone not meeting the standards. Then conduct the most extensive recruiting effort of quality warriors ever. There are thousands who really want a job.<div><br></div><div><br></div><div><br></div>
Inspire innovation. We need to find better/different ways of doing things and not accepting a process/program is good enough as is. From big things to little things, we need to all stop and think if what we are doing every moment is really being done the best way.
Read This Next