Discussion
While I am #software #dev saavy, am not a #ui / #ux pro.
But to my mind if you have a control, that one might normally expect to see somewhere, that can be disabled by some global or scoped restriction or in this case a #Windows #domain/group #policy... DONT HIDE THE FUCKING THING.
Show the button in the same place, but disabled. And if you mouse over if it says "Disabled by <setting>" or "Restricted by group policy <name of policy>".
@tezoatlipoca the heuristic you’re looking for is “visibility of system status”, could bring that up with them 👀 “Has this been tested?” is also always a good question to ask
Or, you know, like if your star #ux person threatens to quit or the PM has a stick up their butt unless you "hide the controls that are inactive", then make it apparent that "we've hidden something here, click / hover to find out what" - I can think of half a dozen clever ways to do this.
@tezoatlipoca it pays off to have good communication with the rest of the team. The UX designer will appreciate if someone tells him/her about a UX issue in a timely manner and he/she is able to solve the issue. It’s better to avoid going behind his/her back.
@tezoatlipoca your reasons are sound from the UX standpoint, but the solution can use some work.
As part of the development team, if you agree to something and then sneakily do something else, you’ll will get yourself and the rest of the team in trouble.
I suggest that you point out the issue using relevant sources (you may not be in charge of UX) and negotiate that the suggestion can be carried out as a refactor or quick fix.
This is a bonfire demo instance for testing purposes. This is not a production site. There are no backups for now. Data, including profiles may be wiped without notice. No service or other guarantees expressed or implied.
