Good q. Personally I had to redefine bikeshedding as it appeared in different contexts, as part of a lessons-learned approach to wrapping up work days spent wit

Good q. Personally I had to redefine bikeshedding as it appeared in different contexts, as part of a lessons-learned approach to wrapping up work days spent with projects. For example, I found that some of the bikeshedding was a healthy and fun mental exploration, a very zen use of natural gifts that take very little energy and are more like meditation. So I was more hands-off about it being an issue when that was the case, and instead tried to capture more of the value from what I had done, so I could reuse or leverage it in the future. In other cases the lack of a useful framework for getting up to speed is a really beautiful setup for the more frustrating form of bikeshedding. I had this happen once with contracts, because a client changed their scheme for coming to contract. God the amount of stuff I learned about LibreOffice while spinning my tires in the mud! In that case I developed a completely speculative framework for navigating contracting method changes, after all was said and done. It helped a lot later. Prioritization is also more variable or modular to me now. I prioritize most often depending on ease of access to tasks, rather than importance. Good luck, I hope some of this helps.