Can we design sociotechnical systems that don’t suck?

Can we design sociotechnical systems that don’t suck?:

Many hard problems require you to step back and consider whether you’re solving the right problem. If your solution only mitigates the symptoms of a deeper problem, you may be calcifying that problem and making it harder to change.

Ethan’s essay is a long response to Shane Snow’s proposals for prison reform. In short, Snow is aiming to adjust conditions inside of prisons without considering whether there is a broader series of social issues that are responsible for actually leading to incarcaration. And, worse, he’s making his proposals without lived experiences of what prison itself is like.

The crux of Ethan’s argument, really, doesn’t concern the kinds of prison reform which are(n’t) appropriate so much as this: is it appropriate for a given person, or group, to solve the problem(s) in the first place? Are they capable of even identifying what are the problem(s)?

I think that this kind of attitude – of humbleness and appreciation for one’s limited perspective on the world – is something that should be taken up by more technologists, policy makers, and law makers. Too often we assume we know how to help without even knowing whether, and if so why and under what conditions, help is needed in the first place.