People have Needs. Technology can help meet needs! It may have Value. Technology can also influence needs to be unmet! It may have Harm. Descriptions of the Value of technology are easily found - that's Marketing. Descriptions of the Harm of technology are harder to find. Which technologies usually cause what Harms? Which Harms are usually caused by what tech?
Tech Researchers! We can make that list together, here.
Tech Creators! We can use this information to help build products which provide more value.
Our concern is human well-being. News articles describing upset about technology come out every day. Once the media cycle is over, it's difficult to track the concern. What happened? What was the event or situation? What was the Value, and what was the Harm? If we don't have a detailed understanding of the problem, it will be difficult to create (or evaluate!) solutions.
(In progress! Wiki forthcoming...)
We're going to take References to specific events and actions about a Technology, Organization, or Process, and make a list of Harm and Value described in it.
We'll start with References - observed, specific, reported events, actions, and harms. From a reference page, we create abstracts with the main harms and values linked out to their respective pages. From some references, we can gather categories of harms based on research.
There are a few Audience + Contributor bases for TechHarms, separated by steps of the process.
First, we start with what exists before this project.
There are a lot of people out there!
TechHarms can fit in here, to help build understanding.
A Tech Researcher will see the reporting and decide it needs further documentation, and will use their background in Journalism, Industry Research, Academic Research, Law, Activism, or other disciplines. (If you consider yourself a Tech Researcher and don't consider yourself represented, we would like to hear! Contact us!) Researchers start to make sense of how this event or situation fits in with the larger history of technology impact.
A Tech Creator could have background in Product, Design, Engineering, Marketing, Sales, Operations, Support, Management, or other disciplines. (If you consider yourself a Tech Creator and don't consider yourself represented, we would like to hear! Contact us!) Creators can see how products, features, processes, and designs work in general, based on the above observations
An audience we do not explicitly target, but who will inevitably be attracted to the site are tech consumers who are concerned with the harms of products in their lives.
This is in progress.
This is going to require people from different backgrounds working together productively and harmoniously to achieve the desired goal. We're going to need the people who have used the technologies and suffered harms to trust that they can talk about this without repercussions. We need technology creators to feel safe describing what they do and how they do it, so that we can understand better. We need researchers to be able to share their results and feel heard, regardless of the results.
To help everyone feel safe working together, the project and all work towards it has a requirement of avoiding Blame, Criticism, Judgment. We are going to generally be avoiding "Right / Wrong" language, including "Good / Bad" evaluations, or uses of Should Statements.
Instead, we will focus on the needs people are trying to meet. Producer needs, Consumer needs. Collective needs, Individual needs. All people are trying to meet their needs.
Respect is a universal human need.
~~Care is a~~ (reword for business context)
Iterative: as good as needed based on resources available, adapt (constant feedback)
Resource-driven: scale up/down
Continuous: Infinite project. Mundane, ordinary, consistent progress.
Not news anymore, but a simple example we can use to understand how the process might work (for now!)
Many high-circulation international news sources reported on this incident, several citing the same local Seattle news source, KIRO 7.
"My husband and I would joke and say I'd bet these devices are listening to what we're saying," said Danielle, who did not want us to use her last name.
Every room in her family home was wired with the Amazon devices to control her home's heat, lights and security system.
But Danielle said two weeks ago their love for Alexa changed with an alarming phone call. "The person on the other line said, 'unplug your Alexa devices right now,'" she said. "'You're being hacked.'"
That person was one of her husband's employees, calling from Seattle.
"We unplugged all of them and he proceeded to tell us that he had received audio files of recordings from inside our house," she said. "At first, my husband was, like, 'no you didn't!' And the (recipient of the message) said 'You sat there talking about hardwood floors.' And we said, 'oh gosh, you really did hear us.'"
Danielle listened to the conversation when it was sent back to her, and she couldn't believe someone 176 miles away heard it too.
"I felt invaded," she said. "A total privacy invasion. Immediately I said, 'I'm never plugging that device in again, because I can't trust it.'"
(A reminder analysis that is absent blame, judgment, or criticism is very difficult, but essential for all parties to work together. This might not go perfectly, but is a goal we strive, correct, and iterate towards, with a concern for the well being and needs of everyone involved.)
An Amazon Alexa Speech Recognition unit (unknown version) in a home had an Unintended Activation, resulting in Surreptitious Recording of a Private Conversation, with Unintended Disclosure by sending the recording to a contact in the owner's device-accessible Address Book.
"Unintended Activation" in this case means no Consent, and either no reported or unacknowledged Feedback.
What is the probability of a recognizer misinterpreting an activation command in a corpus of normal speech per hour?
How many hours of speech happen in hearing range of the devices?
(this would be cross linked or embedded from the Alexa functionality description. It should have links to product manuals, and where available, source code.)
Unlike many problems out there, this seems quite tractable. There are only a few thousand technologies to be covered - too much for an individual, but it would only take a few thousand people learning the process and researching and each making one page to be able to completely document the landscape. Even a few dozen people researching a few dozen technologies each should be able to achieve reasonable coverage.
Sound interesting? I could use your help! Please contact me!
Wiki - forthcoming
Discussion - forthcoming
Identity - no idea yet (pretty curious how that's going to play out)
First discussion! Which tools meet which needs?
This might not yet meet your needs. I would love to help get it there. Please mail me and let me know your thoughts.
CARE RESPECT NEEDS
try it, check! re-evaluate, iterate!
What I was asking them requires a literacy of expressing needs and an ability to understand one another's needs.
- Marshall Rosenberg, Living Nonviolent Communication
DONATE NOW! (FORTHCOMING)
SUBSCRIBE TO OUR NEWSLETTER (FORTHCOMING)
AVAILABLE FOR HIRE TO CONSULT FOR YOUR PROJECT