|
|
|
|
|
|
by awesomerobot
3580 days ago
|
|
|
Clearly defined goals (literally write them down on a whiteboard if you can) and a little time management? It's tough. If you've got an hour-long meeting and 30 minutes in you're talking about the color of a button, reestablish the goal of the meeting — "hey, we're halfway through this meeting and we're still stuck on the button color — maybe we should make a decision now or move on" I've found that a lot of bikeshedding ends up being uninformed opinions/bias. If there's no evidence one way or the other it always seems more efficient to just pick one path and do it. Flip a coin, do an A/B test. |
|
|
I worked with a PM who wanted to cut bikeshedding a while back. When some executive vociferously argued that we should do things B way, the PM just asked him to document why it's important in an email and then told him we'd do it.
A week later an email went out with the executive's strongly worded argument why B is important at the top. At the bottom is "we A/B tested, there is no statistically significant difference between A and B. Guess $executive was wrong."
After a few go-rounds of this, bikeshedding was significantly reduced.
Bikeshedding is easy and fun! But having an email go out to everyone a week later proving statistically that you were wrong is less fun.