Operations 02
Design & Decisions
Is design converting cleanly, and where does it cause rework?
Not connected10 measures specified
What is blocking this surface
No design event is dated. Revision rounds, approval cycles and handoff times all need a record per proposal, and proposals live in files rather than records.
Already exists — do not rebuild
The Designer Coordination Packs define the gates and the acceptance test in detail. What is missing is the record, not the standard.
The three-impact gate
NOT_CONNECTED — the three impacts are not fields anywhereA decision must not reach customer approval until all three impacts are recorded: usage, cost and visual.
usage impactcost impactvisual impact
It converts a matrix that is currently a way of thinking into a gate that can refuse. Two of three completed is not an opinion about readiness — it is a stop.
Measures specified
none computable — not connected| Measure | State |
|---|---|
| Brief-to-first-proposal time | Not connected |
| First-presentation approval rate | Not connected |
| Average revision rounds | Not connected |
| Drawing approval cycle | Not connected |
| Selections matched to an approved SKU | Not connected |
| Selections matched to a verified supplier | Not connected |
| Specification completeness | Not connected |
| Design-to-quotation handoff time | Not connected |
| Approved-design versus installed-result variance | Not connected |
| Design decisions that caused rework, delay or margin loss | Not connected |