I&#x27;d really appreciate an article that explained how to say &quot;no&quot; to stakeholders diplomatically. Most engineers and product people understand the danger of feature bloat but are at frequently at the mercy of people who don&#x27;t.<p>I lead a small engineering team at a product company working for non technical cofounders and this is the hardest thing about my job. Two policies I&#x27;ve implemented have helped me a great deal:<p>1) We must thoroughly discuss the problem before proposing solutions<p>2) New features must be discussed and fully fleshed out at least three weeks before they can be built.