Human Practices is not a checkbox

In iGEM, "Human Practices" is the name for the work of asking whether a project is good for the world, and for whom. It includes talking to the people a project claims to help, examining safety and security, thinking about ethics and regulation, and documenting how all of that shaped the project. It is judged, and it is frequently the weakest part of a team's work.

The usual failure is sequencing. A team designs a system in the spring, builds it over the summer, and in September remembers that it needs a Human Practices section. It sends a survey, interviews a professor, writes two pages, and moves on. Nothing about the project changes, and judges notice.

Start with the people, not the parts

The order should be reversed. Before a team commits to a design, it should talk to the people who have the problem. A biosensor for aquaculture water is a different project after an afternoon with a fish farmer: it turns out the farmer tests the water at dawn, cannot wait two hours for a result, and does not have a refrigerator at the pond. Each of those facts constrains the design, and each one found early saves weeks.

Good Human Practices work produces specifics. "We spoke to stakeholders" is not a finding. "Three of four farmers we visited said a result slower than thirty minutes would not change what they do, so we abandoned the plate-based readout in favour of a colorimetric strip" is.

Safety and security are design questions

Biosafety asks whether the organisms and procedures can harm people or the environment. Biosecurity asks whether the work could be misused. Both are easy to treat as paperwork and both are better treated as design inputs: can the system work in a chassis with no history of causing disease, can a kill switch or containment design be included, is there a way to achieve the same goal without a part that raises concern?

Ethics without the sermon

Students sometimes write ethics sections that read like moral essays. Judges and readers want something narrower: what values does this project assume, who benefits, who bears the risk, and what would the team do differently if those answers were uncomfortable. A project that honestly names its own limits is more credible than one that claims to have none.

Document the change

The most important artifact of Human Practices is a record of decisions: what the team learned, from whom, and what it changed as a result. A simple table in the wiki, with a date, a source, a lesson and a design change, says more than any amount of prose. It is also the record a team is proudest of a year later, because it shows the project grew up.