What Is Sunk Cost
Sunk costs is a commonly used term for any form of a resource, invested attempting to reach future gains, that is not possible to gain back in any form, regardless of the investment outcome. Taken into account the nature of software development, sunk costs can be represented by the following example. The product manager/owner is given a proposal for a feature to be built which leads to user research, prototyping, and user testing, only to find out the feature is not widely demanded or not well understood or perhaps it just doesn't deliver much value compared to the overall development costs.All of the employees time and their salaries are sunk costs. Business can never get them back and will never profit from the resources spent on it.
Source: Sunk Cost
Unfortunately, not every decision-maker is wise enough to walk away from such an unfeasible feature. This may result in doing more research, redefining the scope or, god forbid, developing the feature, and going into production. This phenomenon is called Sunk cost fallacy, loosely translated as one's inability to walk away from an idea, which doesn't work, due to the knowledge of already wasted resources without any return and hoping it will pay off in the future as long as more resources are invested. Reasons for this phenomenon are plentiful ranging from the fear of wasting the resources, hoping you can flip into success to simply being in love with the idea.
How to Minimize Sunk Costs
- Iterate and fail fast
- Agile methodologies like retrospectives do better than traditional Waterfall methods due to faster time to market delivery. Luckily, development can be avoided from the beginning as long as thorough research and validation is done prior to it.
- Validate frequently with stakeholders
- Validating with users, investors, potential customers, and other stakeholders is essential to learn as much information as possible to make the right decision.
- Stop and reevaluate other options
- When knees deep in problems, in order to avoid the Sunk cost fallacy, one should look for other alternative options and evaluate their future potential (ignoring the sunk cost).
- Keep in mind it happens to everyone
- Every successful product or service has been through many sunken costs and most likely has faced multiple sunk cost fallacy moments
Simply put, fail fast, look into the future rather than the past and learn from your mistakes.
Resources for Sunk Cost
Want to write for DXKB?
Feel free to contribute. People from DXKB community will be more than happy.
A Product Owner represents the voice of stakeholders. The Product Owner decides what needs to be delivered by the developers to satisfy the stakeholders and to maximize the value of the product.Read more
A Bus Factor measures the minimum number of team members who have to be hit by a bus to put the project in jeopardy. The goal is to increase your Bus Factor as much as possible.Read more
Tech Writing is the practice of documenting software, hardware, or process to make the work easier. As Tech Writer, you manage knowledge and information.Read more
An icebreaker is an activity you can use at the beginning of a meeting to make attendees more comfortable with each other, encouraging them to speak up, listen up, join in, and open up to new ideas.Read more
Proper Bug Reporting
Proper bug reporting is a crucial practice for development. It helps to understand where the product lacks its functionality or performance. Bug reports are descriptions of bugs found by testers.Read more