Impact vs. Effort
This is a helpful framework to get a team out of the mindset that every fiddly thing needs to be the most perfect, well-thought-out pocket opus. It can strike down perfectionists of all backgrounds: Product Managers, Designers, Engineers. I've even had a customer service colleague hem and haw over an ideal draft that was clearly only going to warrant several expletives in response. Checking in on what the expected impact is for several options of effort is a collaboration opportunity for stakeholders. Many times, I've been surprised to hear, "I don't care if it's a hideous, manual process—I just need to be able to do it next week." The button just needs to be clickable. The slideshow just needs to have a release date. This relates heavily to making things scalable and avoiding the sunk cost fallacy , particularly when it comes to "fed is best." That's something people console you with when you say something incredibly brave like "we're...