"Needs approval from Marketing, UX, Engineering, Legal, and Accessibility".
That's all?
She left out Contracts, Bids, Product Design, Project Design, Publishing, Training, Budget, Project Management, Customer Service, Warranty Support, Site Deployment...
And yes, I've seen this war. To make things worse, there were three independent display systems, so any change in one had to be reflected in the others, with all published user manuals and training documents kept in sync.
Product Design mandated that all colour maps had to be kept in isolated data files, not in code, and have scripts to update the code. That way all three subsystems could use each other's data file and scripts.
One system used a colour map of RGB codes, stored in an XML file, and had a Ruby script to control it. Object sizes were stored as meters.
The second system used a colour map of BGR codes, also kept in an XML file, and used a Perl script to control it. Object sizes were stored as centimetres.
The third system used a colour map as HSV codes, in a JSON file, and used a Python script to control it. Object sizes were stored as millimeters.
Management would tell PMs that all subsystems met the PD requirement, which they did. PMs would then assume that updating object colours and sizes would be easily copied between subsystems, which was less true.
I worked at a company with products in the health field, so our UI color decisions had to follow strict guidelines and went through many levels of approval. Oddly enough, most of our colors were grey on a white background. Red, green and blue were rare. And yet, my grey buttons needed approval via numerous meetings.
This cartoon is funny because it is 100% accurate.
"... and you don't want to know what'll happen if you start talking about rounded corners..."
stakeholders!!!
Is this the desk for user feedback requests? Or maybe it's the programmer dodging extra work 🤔😜
This needs to be ran by usergroups. If it's something as critical as flipping it from red to blue, you may need to align with congress too.
"Needs approval from Marketing, UX, Engineering, Legal, and Accessibility".
That's all?
She left out Contracts, Bids, Product Design, Project Design, Publishing, Training, Budget, Project Management, Customer Service, Warranty Support, Site Deployment...
And yes, I've seen this war. To make things worse, there were three independent display systems, so any change in one had to be reflected in the others, with all published user manuals and training documents kept in sync.
Product Design mandated that all colour maps had to be kept in isolated data files, not in code, and have scripts to update the code. That way all three subsystems could use each other's data file and scripts.
One system used a colour map of RGB codes, stored in an XML file, and had a Ruby script to control it. Object sizes were stored as meters.
The second system used a colour map of BGR codes, also kept in an XML file, and used a Perl script to control it. Object sizes were stored as centimetres.
The third system used a colour map as HSV codes, in a JSON file, and used a Python script to control it. Object sizes were stored as millimeters.
Management would tell PMs that all subsystems met the PD requirement, which they did. PMs would then assume that updating object colours and sizes would be easily copied between subsystems, which was less true.
😦
Rounded vs straight corners too 🤣
I worked at a company with products in the health field, so our UI color decisions had to follow strict guidelines and went through many levels of approval. Oddly enough, most of our colors were grey on a white background. Red, green and blue were rare. And yet, my grey buttons needed approval via numerous meetings.
Someone has to show those posers in Marketing, UX, Engineering, Legal, and Accessibility who’s boss. 💪
This is Sparta! ⚔️ 🔥
I will accept nothing less than war. 💥