Features vs. Benefits: Features are what your app does; Benefits are what your customers value.
Because engineers always want to make something "better", and they consider that in terms of the product in isolation (not in terms of the customer), they often keep improving features beyond what customers value, and so "overshoot" customer needs.
This is so predictable that it fits into Christensen's "disruption" thesis: e.g. minicomputer manufacturers kept improving their product after PC's appeared. They were always better than PC's (feature), but PC's were soon good enough for their customers (benefit). And so DEC got killed. Today, x86 PC's are better than ARM netbooks/tablets/phones...
If you squint your eyes, you can also see this as a case of premature optimisation ("root of all evil" and "don't; not yet").
This is so predictable that it fits into Christensen's "disruption" thesis: e.g. minicomputer manufacturers kept improving their product after PC's appeared. They were always better than PC's (feature), but PC's were soon good enough for their customers (benefit). And so DEC got killed. Today, x86 PC's are better than ARM netbooks/tablets/phones...
If you squint your eyes, you can also see this as a case of premature optimisation ("root of all evil" and "don't; not yet").
now with coffeetime™ technology!