How Much Does A New Feature Cost?

Summary

The article emphasizes that the cost of a new feature extends far beyond the immediate engineering expenses to include a wide range of hidden and ongoing expenses.

Abstract

The article "How Much Does A New Feature Cost?" delves into the underestimated and multifaceted costs associated with releasing a new feature in product development. It highlights that while the immediate benefits of a new feature are tangible and exciting, the costs are often downplayed or overlooked. These costs encompass not only the direct implementation expenses across various disciplines but also the long-term expenses such as maintenance, documentation, training, and opportunity costs. The text underscores that engineering costs are just a fraction of the total expenditure, which includes incremental improvements, internal and external marketing, coordination across teams, and the impact on system complexity and usability. The article concludes by cautioning that many features may end up being underused, suggesting that the full spectrum of costs should be carefully considered before deciding to add a new feature.

Opinions

The article suggests that discussing costs is less appealing than focusing on the benefits of new features, indicating a potential bias towards optimism in product development.
It implies that there is a tendency to underestimate the total cost of ownership for new features, which can lead to unexpected financial and operational strain.
The author expresses that a significant number of features are either unused or rarely used, questioning the return on investment for such additions.
The article conveys a sense of inevitability regarding the payment of these costs over time, even if they are not immediately apparent.
It emphasizes the importance of considering opportunity costs, implying that resources spent on one feature could be detrimental to other potential projects or improvements.
The text suggests that the complexity of a system increases with each new feature, leading to slower engineering processes and the need for additional resources.
The author hints at a preference for simplicity and efficiency over feature proliferation, advocating for a judicious approach to feature development.

More Than You Think …

One of the fundamental challenges of product development is understanding the true cost of releasing a new feature. The benefits feel concrete. Shipping feels great. Talking costs is a downer.

Consider …

Opportunity costs across all disciplines

Cost to implement feature (engineering, UX, product)

Cost to implement incremental improvements (engineering, UX, product)

Cost to deliver feature (processing, storage, monitoring)

Cost to train people internally to sell the feature

Cost to train people internally to support the feature

Cost to market the feature to existing customers

Cost to market the feature to new customers

Coordination costs across all teams

Cost to document and train users/customers on new feature

Cost to maintain that extra documentation

Cost to train engineers on more complex codebase

Cost of slower engineering, caused by increased system complexity and maintenance

Cost to hire more resources to account for slower engineering

Cost of reduced flexibility, caused by increased system complexity and maintenance

Cost of maintaining system usability as system broadens

… until the feature reaches end-of-life (unless you retire it)

It turns out that engineering costs are but a small part of the puzzle.

Wow. So I guess it isn’t just a week or two of work! The good news is that you don’t need to cut a check for these things right away. The hard news is that you’ll end up paying in the long run. And many features end up going unused (or rarely used).

So … consider this expanded list of costs the next time you think about tacking on a new feature. Is it still worth it?