Patch, Feature Patch, and Product Strategy

When a product has a bug, we provide patches to fix those bugs. 

When we have functional gaps, we analyze the requirements and develop the product features.

When the product feature has issues and not working as expected, those are bugs.  To fix them so the product works as designed is the normal patch to fix the bug.

However, in some cases, the product feature introduced earlier was based on lack of the understanding of the full requirement or is based on a short term thinking, the design itself may be problematic.  One way is to fix the feature by enhancing it, another way is to create a new (unrelated) feature and try to fix it by providing alternatives.  Either ways, I consider these are Feature Patches.  

Feature Patches may be considered reacting to customers' feedback, so it is customer-oriented, but actually they are not.

They are reflecting the fact that the development is rush to deliver something that is lack of the thought and perhaps customer validations.

It may be a good mistake that a development organization makes as it typically means that the execution is strong but lack of the thinkers, the product strategist.  

What a product strategist does is to bring the focus and foresee what people will ask and what customers are asking for, but avoid the whole organization to be in the reaction mode.  It is hard as normal people may not understand since the base is not something that can be easily seen.  

People may feel stronger when they are fighting and then win, and those fighter may not really think why they are in the fighting situation.