After the Cambridge Analytica scandal, the tech industry goes through an ethical reckoning. This thesis for the design engineering program at Harvard synthesizes and distills the cultural discourse around tech ethics into a speculative platform that pragmatically resolves the problem. Although speculative, the platform is not a video but an interactive digital prototype that simulates an object and context in a fictional near-future. The undertaking of this project was also a methodological synthesis of wicked problems, design thinking, and data engineering. Methods developed from this class was applied to the USCIS and generalized into a studio curriculum at the University of Michigan.
It is how we design product, not what product we design, that leads to ethical problems.
Origo connects the product team with the information they need to anticipate and mitigate ethical problems at the point of design.
Problem Statement
It is how* we design product, not what product we design, that leads to ethical problems.
* how = people + process
Vision Statement
Origo believes the future of tech ethics lies in creating a continuous feedback loop between software development and regulatory legislation while enabling a plurality of stakeholders to participate in the construction of data models without needing to be "technical." By democratizing the construction of data models and grounding ethics in everyday context and operations, teams can spot, assess, and mitigate ethical risks in a sandboxed environment while collaboratively sharing their learnings with lawyers and regulators. Technology can be designed to be safe, and regulations can update closer and more elegantly to the speed of innovation.
Mission Statement
Reasons to Believe
1
Lawyer-in-the-Loop
Base requirements are collected directly from lawyers so the product team can bootstrap their data model and design ethically without costly refactors.
2
Legible Ethical Value
Protocols that become design requirements can be created and reused by lawyers, traced, and audited at scale so that the product team's work is visible and of consumer value.
3
Input Diversity
Context on design problems are collected through references representing a spectrum of temporal change and diversity of stakeholders.
4
Product Knowledge Management
References and requirements are collected and managed in direct relation to the product data model so that context is never divorced from object.