ENGGEN 115 Chap.8 Communicating and Defending a Design
Communicating and Defending a Design
A design report or presentation is an auditable argument, not a chronological diary. It links requirements to concept decisions and then to drawings, analysis, prototype observations or tests. Representations are selected for the claim they help a reader verify, while captions interpret what matters instead of naming the image.
Communication changes emphasis for stakeholders, technical reviewers and fabricators without changing the underlying engineering truth. Strong conclusions state both supported decisions and the evidence boundary that controls the next step.
What this chapter covers
- 01
Requirement-to-evidence traceability
- 02
Claim and evidence structure
- 03
Purposeful figure selection
- 04
Audience-specific emphasis
- 05
Limitations and uncertainty
- 06
Final recommendation audit
Worked example · free
Defend a bracing revision
- +1State the requirement being investigated: limiting lateral deformation while preserving the required frame function.
- +1Identify the controlled evidence: matched loading position, input and measured top movement across the two versions.
- +1Describe the observed direction of change without inventing precision or a mechanism not examined.
- +1Recommend retaining triangulation for the next iteration because it improved the measured response in this setup.
- +1Bound the claim by noting that full service performance still needs appropriate analysis and broader verification.
Key terms
- Design argument
- A connected explanation that relates requirements, claims, evidence, decisions and limitations.
- Evidence boundary
- The limit beyond which a drawing, calculation or test result does not support a broader claim.
- Traceability
- The ability to follow a requirement through design decisions to verification evidence and conclusions.
- Technical caption
- A complete statement explaining what a representation encodes and what the reader should notice.
- Recommendation
- A proposed decision or next action justified by the available evidence and its limitations.
Communicating and Defending a Design FAQ
How is a design argument different from a project diary?
A diary records activities in time order. A design argument organises information around decisions: what requirement mattered, which alternatives were considered, why one was selected, what evidence supports it and what remains uncertain. Meetings or sketches appear only when they help establish that chain for the reader.
What makes a figure useful in a report?
A useful figure lets the reader verify a relationship, geometry, change or result more efficiently than prose alone. The chosen view must expose the relevant feature, labels must be legible, and the caption should interpret the evidence. Decorative renders cannot substitute for drawings, measurements or analysis tied to a claim.
How should I answer challenges during a presentation?
Identify the assumption or requirement behind the question, then point to the relevant evidence and state its limit. If evidence is missing, acknowledge the uncertainty and name the analysis or test that would resolve it. A bounded answer is more credible than defending a conclusion beyond what the work supports.
What should a technical caption include?
State what relationship, geometry or comparison the figure encodes and direct the reader to the feature that matters for the decision. Include conditions or units when they control interpretation. Avoid captions that merely repeat a title such as final design, because they do not explain what the representation proves.
How do I tailor one design for different audiences?
Keep requirements, evidence and numerical facts consistent while changing the entry point and detail. A stakeholder needs the need, benefit and unresolved risk; a technical reviewer needs assumptions and verification; a fabricator needs complete drawing information. Tailoring reorganises the same engineering truth rather than hiding limitations from one group.
Exam move
Create a traceability table for one project with columns for requirement, decision, evidence, limitation and next action. Test every major claim in both directions: find its supporting artefact, then inspect each artefact and identify the decision it supports. Practise a three-minute explanation covering the problem, chosen concept, strongest evidence and largest remaining risk.
Repair contradictions in numbers, names or dimensions before polishing visual style. Draft captions before selecting final images; if a caption cannot name the encoded relationship and observation, the figure may not have an analytical purpose. Rehearse the same recommendation for a stakeholder, technical reviewer and fabricator, noting which detail changes and which facts remain fixed.
Build a challenge list around criterion weights, model assumptions, prototype scale and missing service conditions, then answer each with evidence and a boundary. Finish by checking that every value in prose matches the current drawing, table and calculation after the latest revision. Record one question you could not answer and name the evidence needed.
Turning that gap into planned analysis or testing is stronger than adding unsupported certainty to the conclusion. Remove any figure whose absence would not change the reader's ability to verify a decision.