Anchoring is a cognitive bias where an initial piece of information (the "anchor") heavily influences subsequent judgments and decisions. This bias can infiltrate various aspects of our lives, including workplace interactions and negotiations. Recognizing how anchoring works is crucial to making informed and unbiased decisions. Custom software is difficult to estimate and using an anchor too early or without the necessary rigour can create issues.
For example, in meetings, it's vital to be aware of anchoring, as the first opinions can shape entire discussions. Seniors and experts can influence a meeting's direction and create anchoring effects; therefore, they should offer their ideas last.
An anchor can limit adaptability, making it harder to find mutually agreeable solutions. For instance, a developer’s best guess on a project budget might discourage the client from choosing your solution looking for other options that could be better suited and more cost-effective.
Sales need to establish the client’s anchor, if they have one, by asking:
When asked for an early estimate on a new project, a developer might say "I reckon it'll cost around $50,000". This off-the-cuff estimate sets an unverified anchor that might restrict further discussion and lead to budget constraints based on a premature guess.
❌ Figure: Bad example - Premature estimation without due diligence can lead to inaccurate budgeting and client expectations
Conversely, when asked for an early estimate, a more experienced developer might respond, "To give you an accurate estimate, we should conduct a Specification Review where we can consider all aspects of the project. This way, we can provide a detailed and reliable estimate that reflects the project's complexity".
✅ Figure: Good example - Suggesting a Spec Review ensures that any estimates provided are well-informed and considered