Discussion about this post

User's avatar
Kevin S. Whisman's avatar

In the immortal words of one of my C.O.’s “When the sh*t hits the fan, I don’t need people to clean up up the sh*t, I need someone who knows how to turn off the fan.”

Expand full comment
John Graveen's avatar

This was a really well written piece. We really have a problem where much of the current baseline of the Navy is broken and we know fixing it the right way will be hard, so we fall for the "miricle cure" approach. While this can work in a start-up (where the examples come from), this rarely works in an established enterprise.

The Intergrated Pay and Personnel systems that Navy (along with Army and Air Force) continue to try to implement is the perfect example. All of the legacy systems were cobbled together over many years, worked only with significant manual work and couldn;r be supported in a modern network environment. Clearly they needed to be replaced. Each service used the DOD software acquisistion guidance and set off in search of what they belived it requied - adapting off the shelf software for a commercial application. Except, military pay and personnel isn't a commercial application. Each service got bogged down into trying to make a commercial product (which successfully uses the idea of making your processes conform to the product) adapt to the constraints which Congress and others have imposed on us. This involved customizing the software beyond the creators imagination at great time and expense. The vendor told us that what we were doing wasn't wise, but we pushed ahead. They were happy to take our money!

Meanwhile the Marine Corps kept upgrading their legacy system which was purpose built for the military pay and personnel process. OSD didn't like it, but amazingly, the Marine Corps remains the only integrated pay and personnel system in DOD.

Expand full comment
111 more comments...

No posts