The behaviour of engineered products is becoming less evident from their outward appearance. Thus many current engineered products have unseen properties that become evident only after protracted investigation, analysis or use. Nevertheless marketing staff, potential users, disposal experts, financiers and so on will wish to make informed decisions about products and commonly their choices will be based on more accessible descriptions, explanations, scenarios and accounts of a products use rather than their direct experience. Engineers usually work with others in enterprises that produce things or provide services. The engineer rarely provides the service or makes the goods but, as a professional, the engineer guides the rest of the enterprise and persuades others to take particular courses of action. It is clear that an engineer's central interest is the artefact. Interestingly the artefact may be in the process of design or the subject of a feasibility study and hence will have no material existence, but it will be circumscribed by a wide variety of texts including specifications, technical reports and standards. Using their specialist language and analytical techniques, the individual engineer will gain assurance about his or her view of the artefact through discussions with fellow engineers, but at some point they will have to convey that view to non-technical specialists. Within the enterprise the engineer will become either an advocate or an adversary of the artefact faced by other individuals or groups who because of their professional or cultural background will value things in different way. The role of the engineer is then as a protagonist or opponent of the artefact within, using Bruno Latour’s evocative phrase, a “Parliament of Things”. And competent engineers, as competent advocates of artifacts, need fluent linguistic and rhetorical skills as well as analytical proficiency and the knowledge that will give them the confidence to project their views. The paper examines the implications for engineering education.
[1]
G. DeFriese,et al.
The New York Times
,
2020,
Publishing for Libraries.
[2]
Peter Törlind,et al.
Distributed design teams: embedded one-on-one conversations in one-to-many
,
2002
.
[3]
Working in the dark.
,
1987,
Nursing times.
[4]
Louis L. Bucciarelli,et al.
Reflective practice in engineering design
,
1984
.
[5]
Rosalind H. Williams,et al.
"All That Is Solid Melts into Air": Historians of Technology in the Information Revolution
,
2000
.
[6]
C. A. R. Hoare,et al.
The emperor's old clothes
,
1981,
CACM.
[7]
Andreas Larsson,et al.
Making sense of collaboration: the challenge of thinking together in global design teams
,
2003,
GROUP.
[8]
J. L. LIONS.
Flight 501 Failure
,
1996
.
[9]
Darren Tofts.
The digital unconscious
,
1995
.
[10]
John Monk,et al.
Ceremonies and Models
,
2003
.
[11]
B. Latour.
We Have Never Been Modern
,
1991
.
[12]
Peter Lloyd,et al.
Storytelling and the development of discourse in the engineering design process
,
2000
.