The average developer makes hundreds of decisions every day. This applies to programmers of all types including newbies, seniors, leads, and architects. They prioritize the work to be accomplished, which bugs to investigate, how to fix issues, and the programmatic path taken to solve problems. Although some of these decisions are smaller than others, they all have varying levels of impact. When too many competing needs arise, seeking guidance on priority is a simple, yet smart decision. Eliminating the haze helps to align the importance of work and reduce the static/noise. But what about the smaller decisions in a day? Although smaller, each of these materialize in different ways.