At one of the large companies I worked for, IT took that "just pave it" approach for _everything_. Maybe because of the contrast between that and my day job of

At one of the large companies I worked for, IT took that "just pave it" approach for _everything_. Maybe because of the contrast between that and my day job of spending weeks to months root-causing really weird distributed systems issues, it stuck me as penny-wise-pound-foolish. At least in this example, that attitude was used as an excuse to never actually investigate anything, even issues that recurred within days of a re-image. Outlook won't connect? Here, go watch the installer for a couple of hours, use your device for a day or two then back to square one. Eventually, it's easy to get so sick of IT's obvious unwillingness to actually fix shit that IT is avoided unless absolutely necessary, and everyone's productivity suffers as a result. At that company, IT was at the top of the negatives column on every internal survey. It is definitely an effective attitude to take at scale, but it has to be paired with at least some troubleshooting of the class of issue. Otherwise, severe bugs get swept under the rug by user exhaustion and IT inaction.