Chapter 45 — Independent design review
Lesson map
Lesson 45 published. Map, example, EX133.
flowchart TD
N0["Learning outcomes"]
N1["45.1 Preparing"]
N2["45.2 Findings"]
N3["45.3 Responding"]
N4["45.4 After review"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX133"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["45.1 Preparing"]
N2["45.2 Findings"]
N3["45.3 Responding"]
N4["45.4 After review"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX133"]
[Learning outcomes]
|
v
[45.1 Preparing]
|
v
[45.2 Findings]
|
v
[45.3 Responding]
|
v
[45.4 After review]
|
v
[Worked example] --> [Exercise EX133]
Learning outcomes
You will (1) prepare a design for independent review; (2) respond to reviewer findings; (3) record decisions after review.
45.1 Preparing
Halfway through the capstone, Kofi's design goes to an independent review by an engineer from another utility and a data governance consultant, neither involved in the project. He prepares a review pack: problem statement, scope, design, decision records, test plans and known weaknesses. He lists weaknesses openly so reviewers can spend their time on unknown problems. Prof. Varga explains that independent review is valuable precisely because reviewers lack the designer's assumptions and will question what the designer takes for granted. The pack is sent a week ahead.
45.2 Findings
Reviewers raise three findings. First, the rules treat all pressure sensors alike, though sensors at critical points need tighter thresholds. Second, lineage stops at the leakage estimate and does not show where pressure data feed customer complaint analysis. Third, the owner map names the operations manager for all pressure data, which concentrates too much in one person. They also praise the decision records for making reasoning easy to follow and test. Each finding is written with an explanation and the evidence that led the reviewers to raise it.
45.3 Responding
Kofi responds to each finding in writing: he adds sensor categories with different thresholds, extends lineage to complaint analysis after confirming the dependency with the customer team and splits ownership between the operations manager for critical sites and district managers for others. For each response he records the change, the reasoning and the residual concern. He discusses one finding where he partly disagrees, explaining his reasons, and the reviewers accept a compromise. The compromise concerns the number of sensor categories, which is reduced from five to three.
45.4 After review
The review record lists findings, responses, changes and open items. It goes into the capstone evidence dossier. Kofi reflects that reviewers found issues he had missed despite careful work, because familiarity hides gaps. Prof. Varga notes that welcoming review rather than defending against it marks a mature engineer, and that a documented review trail shows assessors how the design improved, which is more convincing than a design presented as if flawless from the start. The open items are scheduled for the second half of the capstone.
Worked example
Kofi prepares a review pack listing weaknesses, receives three findings on thresholds, lineage and ownership, responds in writing with changes and a negotiated compromise and records the review.
Synthetic case. The review is synthetic.
Errors and limits
Hiding known weaknesses wastes reviewers' time.
Exercises
- EX133 — Threshold finding. What did reviewers say about thresholds? Rubric: 3 = critical sensors need tighter thresholds;; 2 = partly correct;; 1 = vague;; 0 = none.
- EX134 — Ownership change. How was ownership split? Rubric: 3 = operations manager for critical sites, district managers for others;; 2 = partly correct;; 1 = partial;; 0 = none.
- EX135 — Why review. Why are independent reviewers valuable? Rubric: 3 = they lack the designer's assumptions;; 2 = partly correct;; 1 = vague;; 0 = none.
Continue studying — lesson 45 (chapter 45 of 50)
← Chapter 44 · Course chapter index · Chapter 46 →
Continue to the next authored lesson.