Case Study: A Data Ethics Portfolio — Building Your Professional Identity

"Your resume tells people what you've done. Your portfolio tells people who you are." — Adapted from professional development literature

Overview

This case study is different from those in previous chapters. It is not about an organization, a technology, or a policy failure. It is about you — and the professional identity you are building.

Throughout this textbook, you have studied data governance from every angle: theoretical frameworks, legal architectures, corporate structures, algorithmic systems, social impacts, and emerging technologies. You have analyzed case studies, debated ethical dilemmas, and (if your course included the Python chapters) built computational models. The question now is: how do you translate this knowledge into a professional identity that communicates your values, your competence, and your commitment to responsible data practice?

The data ethics portfolio is the answer. It is a curated collection of work that demonstrates — not just claims — that you can identify data governance challenges, analyze them rigorously, and propose actionable solutions.

Skills Applied: - Translating course knowledge into professional artifacts - Curating and presenting evidence of ethical competence - Connecting academic learning to professional practice - Planning a trajectory of ongoing professional development

Meet the Graduates

This case study follows four fictional graduates of Dr. Adeyemi's course, each pursuing a different career path but all building data ethics portfolios.

Priya — Aspiring Privacy Engineer

Priya studied computer science with a focus on data systems. She wants to work as a privacy engineer — designing and implementing privacy-preserving technologies.

Portfolio contents:

  1. Technical implementation: Differential privacy module. Priya built a Python module implementing local differential privacy for survey data collection. Her portfolio includes the code (documented and tested), a technical report explaining the privacy guarantees, and a reflection on the trade-off between privacy protection and data utility.

  2. Privacy impact assessment. For a course project, Priya conducted a privacy impact assessment of her university's learning management system. She documented data flows, identified privacy risks, assessed compliance with relevant regulations, and recommended specific technical and policy changes.

  3. Bias audit. Priya audited a publicly available machine learning model (a recidivism risk prediction tool) for demographic bias, using the fairness metrics from Chapter 15. Her audit report includes methodology, findings, and recommendations.

  4. Blog post series. Priya maintains a technical blog where she writes accessible explanations of privacy-enhancing technologies. Her portfolio includes three posts: one on federated learning, one on homomorphic encryption, and one on the limitations of anonymization.

  5. Reflection: "When Technical Solutions Are Not Enough." A 500-word essay reflecting on a moment in the course when Priya realized that a technical problem she was trying to solve was actually a governance problem requiring institutional, not just technical, solutions.

Marcus — Aspiring Policy Analyst

Marcus studied political science and took data governance courses as electives. He wants to work at a policy organization focused on technology regulation.

Portfolio contents:

  1. Policy brief: Age-appropriate design legislation. Marcus wrote a 2,000-word policy brief analyzing proposed state-level age-appropriate design legislation, drawing on Chapter 35's analysis of COPPA, GDPR Article 8, and the UK AADC. He assessed the legislation's likely effectiveness and proposed amendments.

  2. Regulatory comparison. Marcus produced a detailed comparison of data protection authorities in three jurisdictions (UK ICO, French CNIL, and Ireland's DPC), analyzing their mandates, budgets, enforcement records, and independence.

  3. Stakeholder analysis. For the encryption debate (Chapter 36), Marcus mapped all major stakeholders, their positions, their interests, and the points of genuine disagreement versus strategic posturing.

  4. Public comment. Marcus submitted a formal public comment during an FTC rulemaking on commercial surveillance, drawing on concepts from Chapters 4, 9, and 11. His portfolio includes the comment and the FTC's response.

  5. Reflection: "Who Is Missing from the Table?" A reflection on attending a technology policy hearing and noting which perspectives were represented and which were absent — connecting his observation to the participation deficit (Chapter 39).

Amira — Aspiring Community Data Advocate

Amira studied sociology and community organizing. She wants to work with communities affected by data systems to build data governance capacity.

Portfolio contents:

  1. Community data literacy workshop. Amira designed and facilitated a two-hour workshop for residents of a public housing complex, explaining how the building's smart energy management system collects and uses data. Her portfolio includes the workshop plan, participant feedback, and a reflection on what worked and what she would change.

  2. Community data governance charter. Inspired by Eli's work, Amira drafted a data governance charter for a neighborhood association, including provisions for community consent, data access, and oversight. The charter was adopted by the association.

  3. Oral history project. Amira interviewed five community members about their experiences with data systems (welfare algorithms, credit scoring, immigration databases). Her portfolio includes excerpts (with consent) and an analysis connecting personal narratives to the textbook's structural themes.

  4. Data cooperative feasibility study. Amira assessed the feasibility of a data cooperative for rideshare drivers in her city, including governance structure, legal requirements, and potential benefits.

  5. Reflection: "Data Governance Is Community Organizing." A reflection on how the skills of community organizing — listening, facilitating, building trust, maintaining accountability — are the same skills needed for participatory data governance.

David — Aspiring Corporate Data Ethics Professional

David studied business with a minor in philosophy. He wants to work in corporate data ethics — building governance programs inside companies.

Portfolio contents:

  1. Ethics program design. David designed a data ethics program for a hypothetical mid-size technology company, drawing on Chapter 26. His design includes governance structure, decision-making processes, training programs, and accountability mechanisms.

  2. Incident response plan. Inspired by Chapter 30's analysis of what happens when things go wrong, David created a data breach response plan that includes technical remediation, legal compliance, stakeholder communication, and post-incident governance review.

  3. Vendor assessment framework. David developed a framework for evaluating the data practices of third-party vendors, including privacy standards, bias audit requirements, and contractual governance provisions.

  4. Business case for data ethics. Drawing on the economics of privacy (Chapter 11) and corporate governance (Chapters 26-30), David wrote a business case arguing that investment in data ethics programs generates measurable returns through reduced regulatory risk, improved talent acquisition, and enhanced customer trust.

  5. Reflection: "The Pragmatic Insider." A reflection on Ray Zhao's archetype from Chapter 40, examining the tension between working within corporate structures and maintaining ethical standards — and how David plans to navigate it.

Portfolio Design Principles

Based on the four examples above, effective data ethics portfolios share several principles:

Show, don't tell. A portfolio demonstrates competence through completed work, not through claims of virtue. An ethics audit, a policy brief, or a community workshop plan is more persuasive than a statement that you "care about data ethics."

Combine technical and ethical analysis. The most effective portfolios show the integration of technical knowledge and ethical reasoning — not just identifying a bias problem, but analyzing it technically and proposing governance solutions.

Include reflection. Ethics is a reflective practice. Each portfolio above includes a personal reflection — a piece of writing that shows the graduate's capacity for self-examination, intellectual honesty, and ongoing learning.

Demonstrate range. A strong portfolio includes different types of work — technical implementations, policy analyses, community engagement, and written reflections — showing that the graduate can operate across the domains discussed in the textbook.

Be honest about limitations. No audit is perfect. No policy brief considers every angle. No community workshop engages every resident. Acknowledging limitations demonstrates intellectual maturity and aligns with the Practitioner's Oath's commitment to continuous learning.

Discussion Questions

  1. Which of the four graduates' portfolios is most impressive to you, and why? What does your answer reveal about your own values and career orientation?

  2. If you were hiring for a data protection officer position, which portfolio would you find most relevant? What about for an AI ethics researcher position? A community data advocate?

  3. What portfolio items would you add that none of the four graduates included? What skills or competencies are missing from their collective portfolios?

  4. How does portfolio-building relate to the Practitioner's Oath? Which provisions of the oath are easiest to demonstrate through portfolio work? Which are hardest?

  5. Dr. Adeyemi told the class: "Your first data ethics portfolio will be imperfect. Build it anyway. Perfection is the enemy of practice." What does this advice mean for someone just starting their career in data governance?

Your Assignment

Design your own data ethics portfolio. Identify five specific items you would include, describe each briefly, and explain how each demonstrates a skill or competence from this course. At least one item should involve community engagement, at least one should involve technical or legal analysis, and at least one should be a personal reflection.