A filter Tamar Yehoshua uses to sort inbound feature requests (from sales, customers, stakeholders): ask which of the many requested items would actually change company outcomes if built, not which ones are merely asked-for most often. Her framing: a team can build 80–90% of everything requested and still not move the needle on company success, because volume of requests is not correlated with impact. Related to "Is This On Strategy?" Filter and Explicit Trade-off Prioritization, but specific to triaging sales/stakeholder feature lists rather than general roadmap prioritization.
Apply: when sales or customer-facing teams hand over a long feature wishlist, push back by asking which small subset would actually move company success, and consciously deprioritize the rest — even if that means visibly declining well-argued individual requests.