From Software to Spirit: Rebuilding Academic Ethics Through Game Design Principles

TL;DR

Can the logic used to program an educational game help a university faculty find its moral compass? This paper argues "Yes." By repurposing the Discovery-Translation-Verification framework from software engineering, the University of Puerto Rico successfully transformed a dry list of rules into a living "Statement of Values" (SOV) that fosters community solidarity and pedagogical innovation.

The Motivation: Moving Beyond "Code Compliance"

Most professional codes of ethics feel like user manuals: they tell you what not to do to avoid getting sued or fired. The authors point out a critical flaw in this approach—it breeds conformity rather than character. In a complex academic environment like the College of Business Administration (ADEM), stakeholders are often lost in a sea of overlapping regulations (reglamentos).

The insight here is radical: instead of treating ethics as a set of constraints to be policed, treat them as features to be designed. By shifting from a "top-down" expert model to a "bottom-up" stakeholder model, the authors sought to create an aspirational framework that people actually want to follow.

Methodology: The Three-Stage Pipeline

The paper adapts the methodology proposed by Flanagan et al. for the "RAPUNSEL" project, which designed games to teach girls programming. The process follows a rigorous three-step pipeline:

1. Discovery (The "Pirate" Strategy)

How do you get people to talk about values without being boring? You start with pirates. Workshop participants analyzed the "Pirate Articles of Agreement"—a document with questionable morals but clear functional values (like fair distribution of loot). This critical exercise opened the door to analyzing real professional codes and eventually identifying five core values for their own community: Justice, Responsibility, Respect, Trust, and Integrity.

2. Translation (From Abstract to Actionable)

Values like "Integrity" are often too vague to be useful. The translation phase involved creating Value Profiles. An external ethicist helped articulate these values into:

• A formal description.
• A list of specific characteristics.
• Minimum threshold rules vs. high-level ideals.

(Note: Figure illustrating the conceptual flow from game design to community values.)

3. Verification (Stress-Testing the Ethics)

In software, you run unit tests. In ethics, you "challenge the credo." The community verified their SOV through:

• Pedagogical Integration: Using the SOV to teach teamwork skills to students.
• Linguistic Translation: Translating the SOV from English to Spanish revealed deep conceptual nuances (e.g., the difference between fairness as "equidad" vs. "impartiality").
• Structural Challenges: Staff members argued that Integrity should be listed first as a "meta-value" that synthesizes all others.

The Results: A Living "Moral Ecology"

The experiment proved that applying software techniques to ethics reverses the usual power dynamic; instead of technology being "checked" by ethics, technology’s design rigors provide a much-needed scaffolding for ethical clarity.

The most significant outcome wasn't just the document itself, but the solidarity built during the process. By involving everyone from non-teaching staff to students, the "buy-in" wasn't forced—it was engineered.

Critical Analysis & Conclusion

The "Takeaway"

This paper is a masterclass in interdisciplinary borrowing. It proves that the "Why" (Values) and the "How" (Implementation) are inseparable. If you want a community to be ethical, you don't just give them a handbook; you involve them in the "system design" of their own moral environment.

Limitations

While the bottom-up approach is excellent for engagement, it is time-intensive. The paper notes that workshops were held over several years. This might be difficult to scale in fast-paced corporate environments where "speed to market" often trumps "depth of discovery."

Future Outlook

As AI and automated systems begin to govern more of our daily lives, this "Values-Based Design" approach is more relevant than ever. This paper suggests that "Verifying" a value is just as important as "Discovering" it—a lesson the tech industry would do well to learn today.