Managing Feature Injection

​Time is running out, and new features are cropping up like bunnies.  How do you decide what goes in and what gets relegated to the backlog?

Every company is different, but here is a simple decision tree that may help you make quick decisions.

Focus on high-value, low-cost initiatives that address a consumer need and align with your North Star. Some experts put the value matrix ahead of consumer need and goal alignment, but if the feature does not solve a problem or further your goals, it is noise.   ​

What do you do with those "maybe" features? Can you introduce the feature with minimal disruption? If so, go for it. If not, here is where you get to be creative.  

• Are there are external factors, such as new regulations, that make the disruption ROI worth it?  
• Are your stakeholders willing to take a schedule or budget hit?  
• Is it critical to take advantage of an emerging opportunity? 
• Has the problem space evolved? 
• Are you able to postpone planned features to accommodate the change? 

If you said yes to any of these, you should consider adding the feature.

Can you think of other reasons why you should or should not include a "maybe" feature?

YMMV with this approach.  Always use your judgment and validate your decision against your particular context. As with any feature, have a framework in place to test and measure success and make adjustments as necessary.