Step 4: Full View

Entities, provisions, decisions, and narrative

Back to Case
Criticism of Engineering in Products
Step 4 of 5

148

Entities

0

Provisions

1

Precedents

17

Questions

17

Conclusions

Transfer

Transformation
Transfer Resolution transfers obligation/responsibility to another party
Engineer A's public-welfare obligation transfers from the private employer-employee relationship (where it could be constrained by faithful-agent/loyalty duties) into the civic-legislative arena (Citizens Committee advocacy and legislative testimony), effectively taking the obligation out of Engineer B's and XYZ's sphere of control. The Board's conclusions ratify this transfer: because the duty and its exercise now reside in the civic/regulatory 'scenario set,' Engineer B's attempt to reassert employer-based control over it (the discharge threat) is treated as an improper reach into a domain from which the obligation had already moved.
Full Entity Graph
Loading...
Context: 0 Normative: 0 Temporal: 0 Synthesis: 0
Filter:
Building graph...
Entity Types
Synthesis Reasoning Flow
Shows how NSPE provisions inform questions and conclusions - the board's reasoning chain

The board's deliberative chain: which code provisions informed which ethical questions, and how those questions were resolved. Toggle "Show Entities" to see which entities each provision applies to.

Nodes:
■ Provision (e.g., I.1.) ◆ Question: Board = board-explicit, Impl = implicit, Tens = principle tension, Theo = theoretical, CF = counterfactual ▬ Conclusion: Board = board-explicit, Resp = question response, Ext = analytical extension, Synth = principle synthesis ▬ Entity (hidden by default)
Edges:
→ informs → answered by → applies to
Provisions (0)
View Extraction
This is a 1967 BER case (BER 67-10). It predates the current NSPE Code of Ethics structure (the three-part I/II/III format was adopted in January 1981) and cites the historical numbered-Canon code (e.g. Canon 15, Canon 27), which does not map to the current Code provisions. An empty list here is expected, not an extraction gap.

All provisions in play for this case: the union of board-stated references and analysis-found citations (see each provision's provenance badge). The OntServe case page's Cited NSPE Provisions panel shows the subset actually cited by the committed conclusions, so its count can be lower.

No provisions extracted for this case.

Cross-Case Connections
View Extraction
Explicit Board-Cited Precedents 1

Cases explicitly cited by the Board in this opinion. These represent direct expert judgment about intertextual relevance.

Principle Established:

Engineers assigned to design a commercial product of lower quality should not question the company's business decision but have an obligation to point out safety hazards and may offer personal opinions to management.

Citation Context:

The Board distinguished this case, which dealt with engineers assigned to design a specific commercial product of lower quality, noting that their obligation was limited to pointing out safety hazards rather than opposing the business decision itself; this differs from the present case involving broader public advocacy not tied to a particular company's product.

Relevant Excerpts
discussion: "What we have said does not conflict with the holding in Case 61-10, in which it was found that engineers assigned to the design of a commercial product of lower quality should not question the company's business decision, but have an obligation to point out any safety hazards in the new design, and may offer their personal opinions and comments to management."
Implicit Similar Cases 10 Similarity Network

Cases sharing ontology classes or structural similarity. These connections arise from constrained extraction against a shared vocabulary.

Component Similarity 64% Facts Similarity 64% Discussion Similarity 73% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 60% Facts Similarity 56% Discussion Similarity 68% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 59% Facts Similarity 52% Discussion Similarity 30% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 58% Facts Similarity 52% Discussion Similarity 65% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 57% Facts Similarity 48% Discussion Similarity 60% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 56% Facts Similarity 60% Discussion Similarity 50% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 56% Facts Similarity 38% Discussion Similarity 33% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 55% Facts Similarity 59% Discussion Similarity 56% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 55% Facts Similarity 37% Discussion Similarity 55% Outcome Alignment 100%
Same outcome unclear View Synthesis
Component Similarity 55% Facts Similarity 44% Discussion Similarity 56% Outcome Alignment 100%
Same outcome unclear View Synthesis
Questions & Conclusions (2 board)
View Extraction
Board Board question 1

Was Engineer A in violation of the Code of Ethics?

Board conclusion Engineer A was not in violation of the Code of Ethics.
Resolved by: The Board weighed Engineer A's public welfare and civic service duties against his faithful agent duty and found no conflict because his advocacy stayed generic and never implicated his employer specifically. (confidence 0.50)
3 principles 3 facts Conditions Narrative
Implicit (2)

Even though Engineer A never named his employer or any specific company, could his public advocacy on product quality still create a reasonable perception of criticism toward his employer, and how should that risk be weighed against his right to civic engagement?

AnalyticalThe Board's finding that Engineer A was not in violation implicitly establishes that the absence of an explicit naming of the employer or its products is the critical factual distinction that shields advocacy from being recast as employer criticism. This suggests a broader principle: an engineer's civic advocacy on general industry-wide issues is protected under the Code even when it touches on subject matter directly relevant to the engineer's own employer's business, so long as the advocacy remains generic and does not single out the employer. The Board did not address how much specificity would be required before advocacy tips into actionable criticism, leaving unresolved where the line lies between permissible general advocacy and disguised employer criticism.
Resolved by: This extension weighs generic civic advocacy against potential employer criticism by treating specificity, not subject matter overlap, as the deciding factor. (confidence 0.50)
3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q101: Because Engineer A never identified his employer or any specific company, any perception of criticism directed at XYZ Manufacturing Company would rest on inference by third parties rather than on anything Engineer A actually stated. The Code's protection of civic and professional expression on matters of public welfare should not be diminished merely because an outside observer might speculatively connect generic advocacy to a particular employer operating in the same industry. The risk of misperception is outweighed by the value of engineers speaking on matters of public safety and product quality.
Resolved by: The Board weighed the speculative risk of third-party misperception of employer criticism against the Code's affirmative protection of civic and professional expression on public welfare matters, and found the latter controlling because no actual identification occurred. (confidence 0.85)
3 principles 3 facts Conditions Narrative

Should the Board have examined whether Engineer A's role as a public spokesman for the Citizens Committee created any implicit conflict of interest with his duties as a faithful agent of his employer, even in the absence of explicit criticism?

AnalyticalRegarding Q104: Engineer A's role as a spokesman for the Citizens Committee does not create a conflict of interest with his duties as a faithful agent of his employer, because his advocacy addressed general industry-wide quality standards rather than his employer's specific products, decisions, or proprietary information. A conflict of interest requires a nexus between the outside activity and the employer's particular interests, which is absent here.
Resolved by: The Board weighed the faithful-agent obligation against the civic-service obligation and found no actual tension because the advocacy's generality prevented any nexus to the employer's specific interests. (confidence 0.80)
3 principles 3 facts Conditions Narrative
Principle tension (1)

Is there a meaningful distinction between Public Welfare in Advocacy Case and Public Welfare in Product Quality Advocacy, and does treating them as separate principles change how the Board should evaluate Engineer A's conduct?

AnalyticalThe differential outcomes for Engineer A and Engineer B illustrate a broader prioritization rule embedded in the Code: civic and public welfare duties are treated as baseline professional obligations that supervisors may not override through coercive employment threats, even when the supervisor's motivation is protection of a legitimate business interest such as reputation. The case thus establishes that Employer Loyalty in Advocacy Warning is subordinate to Public Welfare in Advocacy Case whenever the advocacy remains sufficiently generic and public-facing, reinforcing that engineers' civic rights function as a floor that employer-interest principles cannot breach through threats of discharge, regardless of how plausible the employer's concern for embarrassment may seem to the supervisor.
Resolved by: The board weighed employer-interest principles against civic and public welfare duties by treating the latter as a baseline that employer loyalty concerns cannot override through coercive threats, so long as the advocacy stays generic and public-facing. (confidence 0.80)
3 principles 3 facts Conditions Narrative
Theoretical (2)

From a deontological perspective, did Engineer A fulfill his duty to protect public welfare by publicly advocating for minimum quality standards on commercial products?

AnalyticalRegarding Q301: From a deontological perspective, Engineer A fulfilled his duty to protect public welfare by exercising his professional judgment and civic voice to advocate for minimum quality standards, an action consistent with the Code's affirmative obligation that engineers hold paramount the safety, health, and welfare of the public. His conduct reflects duty-based fidelity to the profession's core obligations independent of any consequences to his employer.
Resolved by: The Board applied a duty-based lens, treating Engineer A's fulfillment of his public welfare duty as self-justifying regardless of downstream employer consequences, so no competing obligation was found to outweigh it. (confidence 0.75)
3 principles 3 facts Conditions Narrative

From a consequentialist perspective, did the societal benefit of raising public awareness about product quality outweigh the risk of reputational harm to XYZ Manufacturing Company that motivated Engineer B's threat?

Counterfactual (1)

If Engineer A had explicitly named XYZ Manufacturing Company's products as examples of shoddy quality in his public advocacy, would the Board still have concluded that Engineer A was not in violation of the Code?

AnalyticalRegarding Q401: Had Engineer A explicitly named XYZ Manufacturing Company's products as examples of shoddy quality, the Board's analysis would likely shift, as such conduct could raise questions about breach of duties of loyalty, confidentiality, or fair criticism of an employer's products, potentially requiring closer scrutiny of whether Engineer A's statements were truthful, objective, and in the public interest rather than merely disparaging.
Resolved by: The board weighs public welfare advocacy against loyalty/confidentiality only once the employer is concretely identified, shifting the balance toward scrutiny of truthfulness and motive. (confidence 0.75)
3 principles 3 facts Conditions Narrative
Board Board question 2

Was Engineer B in violation of the Code of Ethics?

Board conclusion Engineer B was in violation of the Code of Ethics.
Resolved by: The Board weighed Engineer B's claimed employer loyalty concern against Engineer A's and the profession's public welfare duty, and found the loyalty concern illegitimate because it lacked a factual basis, so it could not override the public welfare obligation. (confidence 0.50)
3 principles 3 facts Conditions Narrative
Implicit (2)

Does the fact that Engineer B invoked 'employer embarrassment' as grounds for a discharge threat, absent any actual identification of the employer by Engineer A, suggest that Engineer B was protecting the company's business interests rather than any legitimate ethical concern?

AnalyticalThe Board's conclusion that Engineer B violated the Code can be extended to recognize that Engineer B's threat was not merely a personnel management misstep but a direct attempt to subordinate the profession's public welfare mission to narrow corporate reputational interests. Because Engineer A had not identified any specific company, Engineer B's justification of 'employer embarrassment' reveals that the threat was preemptive and speculative rather than a response to any concrete harm, reinforcing that Engineer B's action was aimed at suppressing lawful civic engagement rather than addressing a legitimate breach of loyalty or confidentiality obligations.
Resolved by: This extension weighs the speculative nature of Engineer B's reputational concern against the profession's public welfare mission, concluding the former was illegitimate and therefore could not justify overriding the latter. (confidence 0.50)
3 principles 3 facts Conditions Narrative
AnalyticalRegarding Q102: Engineer B's invocation of 'employer embarrassment' as the stated justification for threatening discharge, in the absence of any identification of the employer by Engineer A, indicates that Engineer B's true motivation was protection of the company's business reputation rather than a genuine ethical concern about Engineer A's conduct. This suggests Engineer B subordinated the profession's public welfare obligations to a perceived business interest, reinforcing the Board's finding that Engineer B violated the Code.
Resolved by: The Board weighed Engineer B's stated business-protection rationale against the profession's obligation to hold public welfare paramount, concluding that the former improperly displaced the latter given the absence of any real embarrassment trigger. (confidence 0.80)
3 principles 3 facts Conditions Narrative

What responsibility does XYZ Manufacturing Company itself bear for permitting or encouraging a supervisor to suppress an employee's lawful civic and professional activities?

AnalyticalBeyond evaluating the individual conduct of Engineer A and Engineer B, the Board's analysis leaves unexamined the institutional responsibility of XYZ Manufacturing Company for tolerating or implicitly encouraging a supervisory culture in which civic and professional advocacy on matters of public welfare is treated as a disciplinary risk. Even though the Code of Ethics does not directly bind corporate entities, the case suggests that organizational norms enabling supervisors like Engineer B to threaten discharge over lawful advocacy may systematically discourage engineers from fulfilling their public welfare obligations, a structural concern the Board's narrow individual-conduct framing does not capture.
Resolved by: This extension weighs individual accountability against unaddressed institutional responsibility, noting the Board's narrow framing left organizational enabling conditions unweighed. (confidence 0.50)
3 principles 3 facts Conditions Narrative
Principle tension (1)

How should Employer Loyalty in Advocacy Warning be weighed against Engineer B's own Public Welfare Duty, given that suppressing legitimate civic advocacy on product safety may itself undermine the public interest?

Also discussed in: C303
Theoretical (2)

Did Engineer B act with professional integrity when he threatened to discharge Engineer A for engaging in civic advocacy that did not identify any specific employer or product?

AnalyticalRegarding Q303: Engineer B did not act with professional integrity in threatening discharge, because the threat was not grounded in any actual breach of confidentiality, defamation, or identification of the employer by Engineer A, but rather in an anticipatory and unsubstantiated fear of embarrassment. Professional integrity requires that supervisory authority be exercised in accordance with the Code's principles rather than to suppress protected civic engagement.
Resolved by: The Board weighed the supervisor's authority to protect business interests against the Code's requirement that such authority be exercised consistently with public welfare principles, finding the unsubstantiated threat failed that standard. (confidence 0.80)
3 principles 3 facts Conditions Narrative

From a deontological perspective, did Engineer B's duty of loyalty to his employer conflict with, and improperly override, his own duty to support the public welfare mission of the profession?

AnalyticalRegarding Q304: Engineer B's duty of loyalty to his employer improperly overrode his higher-order obligation to support the profession's public welfare mission. Under a deontological framework, loyalty to an employer is a conditional duty that cannot justify suppressing an engineer's fulfillment of the paramount duty to protect public safety and welfare through legitimate civic means.
Resolved by: Loyalty to the employer was treated as a conditional, lower-order duty that cannot override the paramount duty to protect public welfare through legitimate civic action. (confidence 0.80)
3 principles 3 facts Conditions Narrative
Counterfactual (2)

If Engineer A had named his employer's products, would Engineer B's threat to discharge him still constitute a violation of the Code, or would it become a defensible response to a legitimate business concern?

AnalyticalRegarding Q402: Even if Engineer A had named his employer's products, Engineer B's response of threatening discharge would still likely be viewed as an inappropriate first response absent evidence that Engineer A's statements were false or maliciously intended; a more defensible course would involve internal dialogue, correction, or measured disciplinary review rather than an immediate threat to end his employment for engaging in civic advocacy on matters of public welfare.
Resolved by: Even with a concrete employer link, the board favors measured internal responses over immediate discharge threats unless falsity or malice is shown, preserving public welfare advocacy while allowing legitimate employer concern. (confidence 0.75)
3 principles 3 facts Conditions Narrative

If Engineer B had merely expressed disagreement with Engineer A's advocacy rather than threatening discharge, would the Board still have found Engineer B in violation of the Code?

AnalyticalRegarding Q403: If Engineer B had merely expressed disagreement or concern rather than threatening discharge, the Board would likely not have found a violation, since expressing a differing opinion about the wisdom or effect of Engineer A's advocacy falls within legitimate managerial discourse, whereas conditioning continued employment on cessation of protected civic activity crosses into coercive suppression of public welfare advocacy.
Resolved by: The board distinguishes between permissible expression of managerial opinion and impermissible coercive conditioning of employment, finding only the latter to violate public welfare protections. (confidence 0.80)
3 principles 3 facts Conditions Narrative
Analytical questions (2)

Questions the analysis generates beyond the board’s explicit questions: implicit issues, principle tensions, theoretical framings, and counterfactuals. A question with an identified source board question appears nested under that question above.

Principle tension (2)

How should Public Welfare in Product Quality Advocacy be balanced against Employer Loyalty in Advocacy Warning when an engineer's civic activities, though not naming the employer, touch on the same industry the employer operates in?

AnalyticalThe case resolves the tension between Public Welfare in Product Quality Advocacy and Employer Loyalty in Advocacy Warning by giving categorical priority to civic-oriented public welfare advocacy over an employer's speculative reputational interest, but only because Engineer A structured his conduct to avoid direct conflict: he never identified his employer or its products. This shows that the Code does not treat employer loyalty and public advocacy as inherently competing principles requiring a balancing test; rather, loyalty obligations are only triggered once an engineer's public statements actually implicate the employer specifically. Where that link is absent, public welfare advocacy operates as an unconstrained right, and no true principle conflict exists for the Board to adjudicate.
Resolved by: The board resolves the apparent principle conflict by holding that loyalty obligations are only triggered once the employer is specifically implicated, so absent that link, public welfare advocacy operates as an unconstrained right requiring no balancing. (confidence 0.80)
3 principles 3 facts Conditions Narrative

Does Civic Service by Citizens Committee conflict with Loyalty in Employer Threat, and if so, which principle should take precedence when an employer perceives reputational risk from an engineer's participation in a public interest group?

AnalyticalEngineer B's conduct demonstrates that Loyalty in Employer Threat cannot be invoked defensively when there is no underlying breach of a faithful-agent duty to protect. Because Engineer A's Faithful Agent Duty was never actually implicated (his advocacy did not name or identify the employer), Engineer B's attempt to elevate perceived corporate embarrassment above Engineer A's Public Welfare Duty and Civic Service Duty was not a legitimate exercise of competing loyalty principles but an improper subordination of public welfare to unfounded business self-interest. This suggests that when engineers or supervisors invoke loyalty principles, the Code requires an actual, demonstrable nexus to the employer's interests, not merely a generalized fear of association or embarrassment.
Resolved by: Because no underlying faithful-agent breach existed to trigger loyalty, the board treated Engineer A's public welfare and civic service duties as controlling over Engineer B's invocation of employer loyalty. (confidence 0.82)
3 principles 3 facts Conditions Narrative
Decisions & Arguments (4)
View Extraction

Should Engineer A join the citizens advocacy group to address declining product quality standards?

Options considered:
O1 Engineer A becomes a member of the citizens committee formed to address declining product quality standards in the industry. Board's choice
O2 Engineer A declines to join any advocacy group and takes no public role regarding the product quality concern.
Argument structure (Toulmin):
Grounds

Product quality standards in Engineer A's industry were declining, and a citizens committee had been formed to address the issue.

Warrant

Engineers must hold paramount the safety, health, and welfare of the public, and are encouraged to participate constructively in civic affairs; these duties license engagement in public interest groups addressing matters of public concern.

Rebuttal

Would not apply if joining the group required disclosure of proprietary employer information or if the group's stated purpose targeted Engineer A's specific employer.

Duty to Regard Public Welfare as Paramount and Duty to Seek Constructive Service in Civic Affairs

Should Engineer A escalate his advocacy into a public campaign naming no specific employer, or restrain his public advocacy to minimize any perceived conflict with his employer?

Options considered:
O1 Engineer A serves as public spokesman for the committee, advocating for industry-wide quality standards without naming his employer or any specific company. Board's choice
O2 Engineer A explicitly identifies his employer or its products as targets of the advocacy campaign.
O3 Engineer A curtails his public involvement in the campaign to avoid any possible embarrassment to his employer.
Argument structure (Toulmin):
Grounds

Engineer A served as spokesman for the citizens committee and publicly advocated for minimum quality standards without identifying his employer or any specific company.

Warrant

Engineers must hold paramount the public welfare and may engage constructively in civic affairs; this duty licenses generic industry advocacy so long as it does not single out the employer, which would instead implicate the faithful agent duty.

Rebuttal

Would not apply if Engineer A's statements, though not naming the employer, were specific enough that a reasonable observer could only understand them as targeting his employer's particular products or decisions.

Duty to Seek Constructive Service in Civic Affairs balanced against Duty to Act as Faithful Agent or Trustee

Should Engineer B threaten Engineer A with discharge over the public advocacy campaign, or address any employer concerns without coercive suppression of Engineer A's civic activity?

Options considered:
O1 Engineer B warns Engineer A that continued public advocacy tied to employer embarrassment could result in termination.
O2 Engineer B raises any legitimate loyalty or confidentiality concerns with Engineer A through non-coercive means, without threatening his job over lawful civic engagement. Board's choice
Argument structure (Toulmin):
Grounds

Engineer A's public campaign caused embarrassment to the employer, though Engineer A had not identified the employer by name; Engineer B responded by threatening discharge, citing employer embarrassment.

Warrant

Engineers must hold paramount the public welfare, and faithful agent loyalty to an employer does not license suppression of an engineer's lawful advocacy on matters of public safety; where these duties conflict, public welfare prevails.

Rebuttal

Would not apply if Engineer A had disclosed proprietary employer information or explicitly identified and disparaged his employer, giving Engineer B a legitimate loyalty-based ground for discipline.

Duty to Regard Public Welfare as Paramount

Should XYZ Manufacturing Company tolerate a supervisory practice of threatening discharge over employees' lawful civic advocacy, or establish organizational norms protecting such advocacy?

Options considered:
O1 The company permits supervisors like Engineer B to treat employees' lawful public advocacy as grounds for discharge threats.
O2 The company adopts organizational norms that protect employees' lawful civic and professional engagement on public welfare matters from supervisory discipline. Board's choice
Argument structure (Toulmin):
Grounds

Engineer B, a supervisor at XYZ Manufacturing, threatened Engineer A with discharge over a lawful civic advocacy campaign that did not identify the employer.

Warrant

The engineering profession's obligation to hold public welfare paramount depends on organizational conditions that do not penalize employees for lawful, generic civic advocacy on matters of public safety.

Rebuttal

Would not apply if the company's policies were shown to target only advocacy that breached confidentiality or specifically disparaged the employer, rather than lawful generic advocacy.

Institutional responsibility for enabling employees' public welfare obligations
Event Timeline (7)
7 sequenced 4 actions 3 events
Case timeline
An industry-wide trend toward the production of cheap, inferior, and shoddy commercial products, attributed in large part to inadequate engineering, develops in the marketplace.
State changes (1)
  • began: Engineer A Quality Trend Concern
Engineer A becomes concerned about the trend toward cheap products and comes to believe that increased engineering effort could produce products of greater durability and efficiency. This concern arises in him rather than being a deliberate intervention.
State changes (1)
  • began: Committee Members Sincere Public Interest Belief
Engineer A joined a group of like-minded engineers from multiple companies who together formed the Citizens Committee for Quality Products to advocate for higher commercial product quality.
Fulfills (2)
  • Duty to Regard Public Welfare as Paramount
  • Duty to Seek Constructive Service in Civic Affairs
Causal-normative reasoning(confidence 0.80)
Joining the advocacy group directly answers the professional concern created by declining product quality, so it fulfills the duty to place public welfare first and to pursue constructive civic engagement, setting in motion the subsequent public campaign that expresses that same commitment.
Engineer A became the leading spokesman for the Citizens Committee, making public statements, writing letters to local newspapers, and appearing before legislative bodies in support of laws imposing minimum standards for commercial products.
Fulfills (2)
  • Duty to Regard Public Welfare as Paramount
  • Duty to Seek Constructive Service in Civic Affairs
Causal-normative reasoning(confidence 0.80)
Because the public advocacy campaign is the direct escalation of Engineer A's group involvement, it continues to fulfill the duties of paramount public welfare and constructive civic service even though it foreseeably leads to employer embarrassment, showing that the ethical justification of the action rests on its public purpose rather than its reputational costs to the employer.
State changes (1)
  • began: Advocacy Versus Employer Tension
Throughout his advocacy, Engineer A deliberately refrained from mentioning the products of his employer or any other specific company, keeping his campaign directed at industry-wide quality rather than particular products.
Fulfills (1)
  • Duty to Act as Faithful Agent or Trustee
Causal-normative reasoning(confidence 0.75)
Generic advocacy restraint fulfills the duty to act as a faithful agent to the employer while still being guided by public welfare concerns, indicating an attempt to balance loyalty to the employer against the same public interest that motivated the campaign, without itself causing the embarrassment or threat that follow from unrestrained advocacy.
XYZ Manufacturing Company is placed in an embarrassing position as a consequence of Engineer A's public advocacy activities, even though Engineer A never mentioned his employer or any specific company.
State changes (1)
  • began: Advocacy Versus Employer Tension
Engineer B, Engineer A's supervisor, warned Engineer A that he would be discharged if he continued his Citizens Committee activities, on the ground that they were putting the employer in an embarrassing position.
Violates (1)
  • Duty to Regard Public Welfare as Paramount
Causal-normative reasoning(confidence 0.85)
The discharge threat, arising causally from the employer embarrassment produced by the campaign, violates the duty to regard public welfare as paramount because Engineer B uses faithful-agent loyalty to the employer as a pretext to suppress advocacy that was itself protecting the public, revealing a conflict between employer loyalty and the higher public welfare obligation.
State changes (1)
  • began: Engineer A Discharge Threat
Narrative (4 main characters)
View Extraction
Opening Context

Written in second person from the engineer's point of view, so you read the case as the professional experienced it. Underlined names link to the character's profile below.

You are Engineer A, employed by XYZ Manufacturing Company, a firm that produces and sells a variety of commercial home-use products. Over time you have grown concerned about a trend toward cheap, inferior products entering the consumer market, a trend you believe results from inadequate engineering effort rather than unavoidable cost constraints. You have joined a group of engineers from various companies who share this concern, forming the Citizens Committee for Quality Products, and you have become one of its leading public voices, writing letters to newspapers and testifying before legislative bodies in favor of laws establishing minimum quality standards for commercial products. In none of these public statements have you named XYZ Manufacturing or any other specific company. Despite this, your supervisor, Engineer B, has warned you that continuing this advocacy will result in your discharge, on the grounds that your activities are putting the company in an embarrassing position. You now face decisions about your continued involvement in this advocacy and how to respond to the pressure being placed on you.

Main characters (4)

Each card shows the roles a person holds and the tensions those roles raise for them. A single person may carry several roles in the case, and a tension between obligations can implicate more than one person at once. Click Show all tensions for the full list.

Engineer A Roles in this case: Employed EngineerCitizens Committee Spokesman

Guided by: Public Welfare in Product Quality Advocacy, Employer Loyalty in Advocacy Warning, Public Welfare in Advocacy Case

The classic engineering ethics tension arises where Engineer A's loyalty to the employer as a faithful agent (protecting proprietary interests and following directives) conflicts with the paramount duty to hold public safety, health, and welfare above all other considerations, especially if the employer's products or practices raise quality or safety concerns that the Citizens Committee is investigating.

Attaches to role: Employed Engineer

Engineer A's duty to protect the public through participation in the Citizens Committee for Quality Products directly conflicts with the employer's demand that Engineer A cease such advocacy. Complying with the cessation demand would require abandoning or muting the public welfare duty, while continuing the advocacy risks violating the employer's directive and potentially the employee's duty of loyalty.

Attaches to role: Employed Engineer

Engineer A's obligation to act as a faithful agent of the employer, which typically implies discretion and support of the employer's interests, is in tension with the separate civic duty to serve the public through voluntary participation in a consumer oriented committee that may scrutinize or criticize the employer's products. Fulfilling one role fully can undermine the credibility or availability required for the other.

Attaches to role: Employed Engineer
Engineer B Roles in this case: Supervisor
XYZ Manufacturing Roles in this case: Company Employer

The classic engineering ethics tension arises where Engineer A's loyalty to the employer as a faithful agent (protecting proprietary interests and following directives) conflicts with the paramount duty to hold public safety, health, and welfare above all other considerations, especially if the employer's products or practices raise quality or safety concerns that the Citizens Committee is investigating.

Engineer A's duty to protect the public through participation in the Citizens Committee for Quality Products directly conflicts with the employer's demand that Engineer A cease such advocacy. Complying with the cessation demand would require abandoning or muting the public welfare duty, while continuing the advocacy risks violating the employer's directive and potentially the employee's duty of loyalty.

Engineer A's obligation to act as a faithful agent of the employer, which typically implies discretion and support of the employer's interests, is in tension with the separate civic duty to serve the public through voluntary participation in a consumer oriented committee that may scrutinize or criticize the employer's products. Fulfilling one role fully can undermine the credibility or availability required for the other.

Citizens Committee Roles in this case: for Quality Products

The classic engineering ethics tension arises where Engineer A's loyalty to the employer as a faithful agent (protecting proprietary interests and following directives) conflicts with the paramount duty to hold public safety, health, and welfare above all other considerations, especially if the employer's products or practices raise quality or safety concerns that the Citizens Committee is investigating.

Engineer A's duty to protect the public through participation in the Citizens Committee for Quality Products directly conflicts with the employer's demand that Engineer A cease such advocacy. Complying with the cessation demand would require abandoning or muting the public welfare duty, while continuing the advocacy risks violating the employer's directive and potentially the employee's duty of loyalty.

Engineer A's obligation to act as a faithful agent of the employer, which typically implies discretion and support of the employer's interests, is in tension with the separate civic duty to serve the public through voluntary participation in a consumer oriented committee that may scrutinize or criticize the employer's products. Fulfilling one role fully can undermine the credibility or availability required for the other.

The Board’s deliberation

How the Board of Ethical Review resolved the case, verbatim from its published conclusions.

Engineer A was not in violation of the Code of Ethics.
Engineer B was in violation of the Code of Ethics.
Opening States (8)
Engineer A Discharge Threat Advocacy Versus Employer Tension Engineer A Quality Trend Concern Committee Members Sincere Public Interest Belief Engineer B Code Conflict Engineer B Employer Loyalty Conflict Code Inapplicability To Companies Unnamed Employer In Advocacy
Summary
  • An engineer's off duty civic participation in a public interest consumer group is protected by the paramount duty to public health, safety, and welfare, and an employer cannot lawfully or ethically demand its cessation.
  • The faithful agency duty owed to an employer is not absolute and does not override an engineer's independent obligation to serve the public, especially when the activity occurs outside the scope of employment.
  • Engineers can hold dual roles as employee and private citizen without automatically creating a disloyalty violation, as long as confidential employer information is not misused.

© Licensed under the GNU GPL v3