- ### __Bias : __ - Time-saving bias - ### __Definition : __ - The time-saving bias describes people's tendency to misestimate the time that could be saved (or lost) when increasing (or decreasing) speed. - ### __OODA Class : __ - Decide Phase - ### __OODA Subclass : __ - Complexity - ### __Classification Reasoning : __ - Time misestimations often occurs due to lack of perception about the complexities involved. Decisions could be made on the presumption that increasing the factors such as the number of involved in the implementation of a project leads to saving time. - ### __Example : __ - Assuming that adding more people to a late project results in faster implementation: In many projects, developers are promoted to a managerial position without proper training in project management. When dealing with sharp deadlines, it is not uncommon to see such managers deciding to add some extra workforce in a bid to meet the timelines. - ### __Impact : __ - This is a classic case is based on [[Brooke’s Law]] which states that “adding human resources to a late software project makes it later”. - ### __Debiasing Techniques : __ - There are exceptions to the above scenario. It is applicable only with respect to projects which are already late. Adding people to a project early on would be beneficial. Also, highly skilled contributors could be another exception as they would be able to contribute within a short time frame. - ### __Related Biases : __ - [[Complexity Bias]], [[Parkinson’s Law of triviality (Bias)]],[[Planning Fallacy (Bias)]]