I'm a freaking O-3, I have nowhere near enough 'pull' required to tell organizations led by O-5 all the way through O-9s to get their collective organizations off of their collective asses, even if I felt like 'getting dirty'.
But, even if I felt like it, what happens when I leave and the next guy comes along who doesn't care at all? The situation I'm talking about here isn't one of my primary duties, it merely happens to be related. Right now this issue is essentially no one's primary duty, which is one of the problems.
My proposed solution is a tested principle from software refactoring, applied to organizations writ large. In fact I've often been surprised at how well software engineering practices can translate over to organizational systems design practices.
Ah - got it now. Harder to look around when you're in the military, and the stakes are higher.
I've noticed similar in software practices (especially project management and metrics) leading broader org design. I'm not sure if it's because the failures are bigger, or the orgs are more willing to experiment, but software firms do seem to drive HR and organizational design trends.
But, even if I felt like it, what happens when I leave and the next guy comes along who doesn't care at all? The situation I'm talking about here isn't one of my primary duties, it merely happens to be related. Right now this issue is essentially no one's primary duty, which is one of the problems.
My proposed solution is a tested principle from software refactoring, applied to organizations writ large. In fact I've often been surprised at how well software engineering practices can translate over to organizational systems design practices.