In a big enough organization, it is a complex system with unpredictable outcome. Pouring your soul into it may lead to unexpected consequences as opposed to simpler environments where your contribution actually make a relative difference.
True, that's why if I get to work for a big organization again I'll not even entertain the idea of trying to make a difference in improving processes. I'll just gulp the salary and never stick my nose out of my direct responsibilities as written in the contract.
Making a difference can only happen in small tight-knit teams.
"Appreciate the feedback but we got this covered. Please resume your duties."
> 2. Recruit some good people
Did you miss the part where I said that my comment is from the point of view of a working programmer and not an executive?
> 3. Suggest and execute some positive changes
See my reply to your (1) above.
> “there’s this thing called source control and it’s great…”
"Don't be a condescending smart-ass please, you are not being a team player right now."
> “seems like the reports we built aren’t that useful—how can we make this better”
"They work well enough for us and we have no time budget for any modifications, and we are not convinced the said modifications are necessary at all".
---
Your move.