[munchbunny]

Bike-shedding doesn't need any specific process to happen, it just needs people who want to bike-shed. If it's not over the severity label on the feedback, it'll just take some other manifestation.

The solution isn't to try to design a process to prevent bike-shedding, because you can't. It's to practice a culture that frowns upon bike-shedding and focuses on the using time well.

> I can also see a certain path of dysfunction where people get known by their perception of problems. Suddenly Joe doesn't get asked for many reviews because he's "the mountain guy" that always thinks things are blockers.

Joe probably doesn't need to declare everything "mountain" to become the guy that makes mountains out of molehills, and probably doesn't need the formalism to be the guy people don't like to ask for code reviews.

> There really needs to be some thought around calibration and review of people's prioritization.

Usually this is where we'd expect the manager to talk to Joe about being more constructive in code reviews.