7 Teamwork, Safety, and Professional Responsibility
7.1 Design is a team activity
A useful project structure assigns roles and deliverables without assuming every team member has identical expertise. Maintain a decision log, versioned files, meeting notes, and explicit owners for open actions.
7.2 Risk and responsibility
Engineers must consider safety, public welfare, environmental effects, cybersecurity where relevant, accessibility, and foreseeable misuse. Professional obligations cannot be reduced to satisfying a client or meeting a course deadline.
7.3 Communicating uncertainty
When test evidence is incomplete, say so. A transparent list of assumptions and residual risks is more useful than a confident claim unsupported by data.
7.4 A short review routine
At each major milestone, review the technical evidence, decision rationale, unresolved risks, and whether the original problem still warrants the selected solution.
Discussion: A sponsor asks your team to omit an unsuccessful safety test from a demonstration. What documentation, escalation, and retesting actions are appropriate?
Living chapter. This is an initial working treatment. Derivations, examples, and references will be expanded in future editions.