vault backup: 2025-09-29 13:43:57
This commit is contained in:
@@ -6,28 +6,24 @@ tags:
|
||||
---
|
||||
# Estimating Detail
|
||||
|
||||
In [[construction-estimating]], the acceptable level of detail of an estimate is a contentious subject.
|
||||
The acceptable level of detail of an [[construction-estimating|estimate]] is a contentious subject.
|
||||
What's worse, estimators often disagree on what makes an estimate more detailed than another.
|
||||
With our [[risk-oriented-estimating]] approach,
|
||||
detail is essentially the inverse of epistemic [[uncertainty]].
|
||||
|
||||
That said, the correct answer is this.
|
||||
The commonly repeated answer is this:
|
||||
|
||||
> As detailed as possible, given required turnaround and available estimating resources.
|
||||
|
||||
%%
|
||||
TODO: This analysis is not much better than the common belief.
|
||||
A commonality of both is the implication that more time ought to be preferred,
|
||||
This analysis is flawed
|
||||
because it implies more time ought to be preferred,
|
||||
when the reality is that when considering larger organizational factors (strategy),
|
||||
ideal estimate certainty is likely far lower than most expect.
|
||||
|
||||
The _correct_ correct answer involves optimizing for these factors:
|
||||
* value of increased bid certainty
|
||||
* value of increased estimate volume
|
||||
%%
|
||||
|
||||
An estimate's detail is irrelevant to its quality.
|
||||
A less detailed estimate is a more [[risk]]y bid,
|
||||
A less detailed estimate is a more [[risk|risky]] bid,
|
||||
but **it is not the role of the estimator to determine acceptable risk**.
|
||||
|
||||
## Experiment
|
||||
|
||||
Reference in New Issue
Block a user