Building a team is hard work! Figuring out a company culture for a company that doesn't exist is a bit like trying to grab an eel with your elbows, however it's absolutely vital to get right first-time.
Fortunately, there's a set of questions we can test ourselves against:
- Who gets to use what we make? Who are we leaving out? How does what we make facilitate or hinder access?
- What data are we using? Whose labor produced it and what biases and assumptions are built into it? Why choose this particular phenomenon for digitization or transcription? And what does the data leave out?
- What systems of authority are we enacting through what we make? What systems of support do we rely on? How does what we make support other people?
- What kind of community are we assuming? What community do we invite through what we make? How are our own personal values reflected in what we make?
-- “Toward a new hacker ethic” by Allison Parrish
For us, "data" includes secondary sources (metrics, bug reports, player telemetry), but also means content produced by creators.