"When building a product, it is sometimes difficult to draw the line between what features to build and which ones to let go of."

"If that line is not drawn early and often, you end up with the most horrifying term any product will ever encounter: feature bloat."

"Also known as feature creep, feature fatigue, or feature overload — having too many features is something all teams must watch out for."

"The ‘what’ and ‘why’ of features"

"What problem are we trying to solve?"

"Why are we trying to solve it?"

"A good place to get started is to use a product problem template. This template can be used by anyone in your team when they’re proposing a new idea."

"It changes the conversation from ‘let’s do x’ to ‘how might we be able to solve this problem?’ establishing product-thinking throughout your entire organization."

"Stop validating, start invalidating"

"They try to gather “requirements” and “new feature requests”"

"They try to validate what they already know"

"Instead, start calling these feature requests ‘customer feedback.’"

"This also allows you to ask questions, understand problems, and implement solutions that benefit your customers and product."

"Don’t validate what you already know"

"Instead, approach things differently and start asking questions that will help you invalidate what you know so far."

"This might actually help you avoid adding product features altogether."

"You can prioritize half of the things you think you need to build by starting with your decision-making process at the very top of the funnel with a clear roadmap."

"a simple and solid place to get started is by setting clear objectives."

"Build what is actually useful in its most viable and essential form, present it to the customer, and then re-assess the next iteration."