I recently had to work on a project with people who were absolutely computer illiterate demanding that a product designed for use by technical savvy data analysts be modified. Despite the fact that they weren't the users, they assumed that if they couldn't understand it, nobody could. It was a fucking nightmare. In their world, input = contribution = proof of value. The fact that they aren't able to contribute anything of value because they have failed to maintain even a minimally relevant set of skills eludes them.
This isn't only a problem with computer & IT related things. It is present in virtually every technical field.
It's called "bikeshedding" or "Parkinson's Law of Triviality" -- and smart/savvy project managers know EXACTLY how to deal with it.
You make ALL of the big complex decisions, and then you "create" the opportunity for them to fight over/debate/have input -- on things that don't really make a damned bit of difference. So you make certain that both the building of the proverbial "atomic reactor" AND the "bikeshed" (especially what color to paint the latter) are equal items on the agenda... that way you can get the atomic reactor approved, and move on to the bikeshed, where EVERYONE can give their input on what color(s) to paint it, whether there should be flowers or trees planted around it, etc.
In the case of IT projects, it is critical to the success of the project that the ID10T type people be kept super busy & preoccupied deciding/debating over trivial things: what the LOGO should look like, and what photos and colors the startup page (background, etc) should have -- like should there just be a generic "stock" photo of some help desk person, or should there be a rotating mixture of people, including various ethnic & gender & age groups -- and then should they be actual photos of employees or ??? (Ideally you fob them all off onto some advertising/marketing subgroup or subcontractor and keep them busy with "focus groups" and other such nonsense.)
Of course you CAN'T ever let them know that those things are trivia/nonsense -- you have to do the opposite, and continually talk up just how important they are to the overall "user experience", etc.