@chronodekar
Sadly, I've seen something like that in real life at least 2 times through my career in computer programming.
The first was deciding on a new office microwave (it broke), we had 3 meetings on it, and people actually argued color, handle, brand, the need for a popcorn and speed buttons, etc...
Early on I had suggested the idea that maybe all we needed was one to fit the counter top, but I was sadly talked down and they went on from there.
In the end, after all that was decided, it was agreed to send 2 people out one day to pick it up. It took a week and a half.
The second was we were working on a huge project at the time, and myself and two others were ordered to use a specific book, and go over the meeting notes of another internal group using it on a different project.
The thing to consider was this was big on department interaction and meeting decisions all being documented at official meetings.
I had pointed out that the particular book was meant for *much* bigger projects and the format would actually bog us down in procedures.
sadly I was overruled by management. And we started plowing through those notes.
Apparently that other team actually thought the same way and were bored one day... because we found evidence that they had a meeting to discuss what food and drink was allowed at meetings. We found evidence they had brought up, disussed, made a vote, documented the vote, and added it to the rules that any drink taken into a meeting had to be more than 60% water based....
I kid you not... myself and the other two going through this were flabbergasted...
Those were a long time ago. These days, I tend to be quiet at meetings and just watch the paint peel