ZaneMeyers/zmVault
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2025-10-10 14:37:17

Browse Source
This commit is contained in:
Zane Meyers
2025-10-10 14:37:17 -04:00
parent fb46ae17d3
commit 55b9385f62
79 changed files with 860 additions and 728 deletions
Download Patch File Download Diff File Expand all files Collapse all files
estimating-detail.md
+14 -8
View File
@@ -2,31 +2,36 @@
id:
aliases: []
tags:
- destiny/uncertain
- status/incomplete
- topic/estimating
- type/philosophy
title: Estimating Detail
---
# Estimating Detail
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.
The acceptable level of detail of an estimate
in [[construction-estimating]] is a contentious subject.
What's worse, estimators often disagree
on what makes an estimate more detailed than another.
The commonly repeated answer is this:
> As detailed as possible, given required turnaround and available estimating resources.
> As detailed as possible,
> given required turnaround and available estimating resources.
This analysis is flawed
because it implies more time ought to be preferred,
when the reality is that when considering larger organizational factors (strategy),
because it implies more time always ought to be preferred,
when the reality is that when considering larger organizational factors,
ideal estimate certainty is likely far lower than most expect.
The _correct_ correct answer involves optimizing for these factors:
The 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|risky]] bid,
but **it is not the role of the estimator to determine acceptable risk**.
but it is not the role of the estimator to determine acceptable risk.
## Experiment
@@ -35,7 +40,8 @@ the maximum amount you would ever consider using,
and measure the time required to do so,
as well as the cost of the scope.
Have another estimator takeoff the same scope using the proposed time saving strategy.
Have another estimator takeoff the same scope
using the proposed time saving strategy.
Repeat the test on additional projects.