If this category is not applicable for this technology, please select 'Yes'.
It is important to understand the limitations of data and it is equally important to design your technology accordingly. Are you aware of limitations to the data used. How do you cope in your technology with concepts like subjectivity, incomplete datasets, feedbackloops and so on.
An example: GriefbotYes, dependent on the available data, the personality of the griefbot might be close or far from the deceased person. The limits are clear to us. The griefbot can't "cope" with it, so we would make the users aware of its limitations.
Data and insights about data change over time. Do you take this in account and how? How do you improve on the way you handle data? Do you consider that measuring something influences the thing you are measuring?
An example: GriefbotWe will let the griefbot develop itself, there will only be moderation on extreme new behaviour arisen from the self-learning of the bot.
When using data to predict future behaviour, think about how sustainable these insights are: (1) what are the long term legal permissions to process the data? (2) can the data and used algorithms be kept current (3) is the data available for a reasonable period of time in the future, even when the source generator(s) are discontinued or sold to a third party?
An example: GriefbotThe bot might develop itself to a future version of the deceased that might never have excisted. On the other hand it might not evolve, and keep certain believes in a time frame (eg. the view on same sex marriage), while if the deceased might have lived, they might have evolved in their believes.
If you profit from the use or sale of user data, do your users share in that profit? What options would you consider for giving users the right to share profits on their own data?
An example: GriefbotThere is no business model behind the grief bot.
The idea of the technology impact tool is that it stimulates you to think hard about the impact of your technological solution (question 1-4). The answer can lead to changes in design or implementation, which is a good thing. Please list them here.
An example: GriefbotNot at the moment, no.