# Case Study Template Design
###### tags: `ethics team`

:::info
**Using HackMD**
HackMD is a collaborative, text editor that uses Markdown—an easy-to-read language that is well-suited to the web.

If you are new to Markdown, please just treat this as a plain text editor. Or, click on the `?` at the top of the screen to access a cheatsheet.
:::

## Example

This is an [example handout](https://thealanturininstitute-my.sharepoint.com/:b:/g/personal/cburr_turing_ac_uk/ETMl2t4dg6BFt5v54VyntwUBvkdjl2vqEOmTSkgF4gLeXw?e=2hA72h) that we have used in the TAS Hub project to support workshops with students.

## Designing a Case Study Template

### Functions

:::success
**Question**
What are the functions of a good case study?
:::

1. Function 1
2. Allow users/stakeholders to better understand and contextualise purpose, impact, and considerations (i.e. put themselves in the 'use case' shoes)
3. Including stakeholder considerations beyond their own
4. To ground principles into concrete examples
5. To provoke reflection and engagement
6. To help us map unchartered territory where applicable
7. To reveal features, uses, problems that were probably not considered by the provider or a tool or service (aka 'blind spots').
8. to exemplify information/ideas not used prior in one area into another
9. Establish common understanding of key terms, theories, or principles
10. To account for all impacted persons and groups.

### Sections

:::success
**Question**
What sections should be included in a case study?
:::

1. General description including intended context of use, audience
2. Intended purpose of the tool or service - what the provider 'thinks' it's meant to do.
3. Applicable regulation / best practices if relevant
4. What's currently not covered by regulation (but should be)
5. Why regulation hasn't covered it?
6. Potential benefits of the technology / practice
7. Potential harms of the technology / practice
8. Explanation of key terms (if there are any)
9. Allude to potential future work, if relevant
10. Reveal the relevant types of data
11. Any opportunities for further engagement
12. Possible contexts of use
13. Categories of "user"
14. Consideration of impact on non-users of the tool - (e.g., crowdsourced app that predicts a neighbourhood's 'sketchiness' - how it affects those who live there)
15. data sharing concerns

### Activities

:::success
**Question**
What activities could these case studies support?
:::

1. Inventory of benefits and harms likely to occur
2. Distinguish among the stakeholders likely to experience benefits vs. harms (e.g, landlords vs. tenants in a service designed for and marketed to landlords)
3. Relate the case to a similar example from the participants' experience
4. Empirical work, for example, testing out a tool, answering a survey, conducting a user study
5. Map out where regulation is missing
6. Map out where more than one regulatory body might have jurisdiction & potentially conflicting views (eg if we are arguing for a unified approach)
7. identify conditions of acceptable use/limitation of acceptability

### Intended Audience

:::success
**Question**
Who is the intended audience for a case study?
:::

1. Civil servants
2. Potentially impacted communities
3. Anyone? The same case study can be tweaked slightly in terms of content and language for specific stakeholders
4. Developers/researchers
5. guardians/institutes that speak/securitise on behalf of another group that is silenced or does not have the means to engage
6. civil society
7. Advocacy groups
8. Teachers/students