Hm. At my current workplace, management isn't particularly computer-savvy, which has benefits and limitations when it comes to innovation :-). On one hand, things tend to be a matter of "if it gets the job done, it's good enough" as far as solution design goes, so I essentially have my pick of how solutions are developed (working in an itty-bitty shop lessens the pressure there quite a bit!). This has lead to some out-of-the-box thinking, like designing a once-every-four-hour e-mail notification routine for management to know that the servers are still up and running, which then got a weather report attached to it that's called in from PowerShell (in the event that a power-failure-inducing storm is inbound; we sadly don't have much in the way of backup power), or a shipping rate calculator that utilizes C# and PowerShell to generate data for our SQL Server to ingest and do comparisons on (SQL Server is best at handling data; web API calls, procedural loops, and text formatting gets done by languages that are better at those things).

On the other hand, that same lack of computer savviness can lead to problems, too. Management often doesn't know exactly where my limits are in regards to programming, so if there's something that can't be done (like getting more information from our distributors than they can provide), it gets a little messy trying to explain the situation fully. But the good comes with the bad, as it goes.