Useful updates regarding changes in status of Pandemic.
Google Maps adds new COVID-19 alerts as more cities reopen
Maps will remind you to wear a face covering on public transit
By Chris Welch@chriswelch in Theverge
Google is continuing to build more helpful new features into Google Maps to assist people trying to navigate around cities that have begun emerging from the COVID-19 pandemic. When you look for public transit directions, you’ll now see “relevant alerts” from transit agencies about mandatory precautions you’ll need to take — such as wearing a face covering. And if a public transit line is temporarily suspended due to the ongoing COVID-19 response, you’ll hopefully get a heads-up about that, too. ... "
Showing posts with label Alerting. Show all posts
Showing posts with label Alerting. Show all posts
Friday, June 19, 2020
Wednesday, April 15, 2020
The Effect of Privacy Notices
An example of behavioral response to alerting consumers,
The Bulletproof Glass Effect: When Privacy Notices Backfire
by Aaron R. Brough, David A. Norton, and Leslie John in HBSWK
Consumers regularly encounter privacy notices explaining if and how their personal information will be collected, stored, used, and shared. Evidence in this study demonstrates that privacy notices, though designed to promote a sense of confidence that personal data will not be misused, can undermine consumer trust and decrease purchase intent.
Author Abstract
Firms typically provide assurances to consumers about data management practices in the form of privacy notices. This manuscript proposes that ironically, such assurances can fuel rather than alleviate privacy concerns. Indeed, we show that consumers react to assurances as if they were warnings—a counterintuitive phenomenon because unlike warnings, which communicate danger, assurances are designed to communicate protection. Across one field experiment and five lab experiments, we show that a salient (vs. an absent or less salient) privacy notice can lead to decreased rather than increased purchase intent. This effect is mediated by consumer trust and is robust to the language in the privacy notice—it occurs even when the notice is overtly assuring, as well as when consumers see only a link to the notice but do not view its contents. The attenuation of the effect in joint (vs. separate) evaluation suggests that consumers’ hesitation to transact with organizations that have a salient privacy notice is not likely driven by an active aversion to assurances but rather by the arousal of dormant privacy concerns.
Paper Information
Full Working Paper Text (pdf) http://www.hbs.edu/faculty/pages/download.aspx?name=20-089.pdf
Working Paper Publication Date: February 2020
HBS Working Paper Number: HBS Working Paper #20-089
Faculty Unit(s): Negotiation, Organizations & Markets .... "
The Bulletproof Glass Effect: When Privacy Notices Backfire
by Aaron R. Brough, David A. Norton, and Leslie John in HBSWK
Consumers regularly encounter privacy notices explaining if and how their personal information will be collected, stored, used, and shared. Evidence in this study demonstrates that privacy notices, though designed to promote a sense of confidence that personal data will not be misused, can undermine consumer trust and decrease purchase intent.
Author Abstract
Firms typically provide assurances to consumers about data management practices in the form of privacy notices. This manuscript proposes that ironically, such assurances can fuel rather than alleviate privacy concerns. Indeed, we show that consumers react to assurances as if they were warnings—a counterintuitive phenomenon because unlike warnings, which communicate danger, assurances are designed to communicate protection. Across one field experiment and five lab experiments, we show that a salient (vs. an absent or less salient) privacy notice can lead to decreased rather than increased purchase intent. This effect is mediated by consumer trust and is robust to the language in the privacy notice—it occurs even when the notice is overtly assuring, as well as when consumers see only a link to the notice but do not view its contents. The attenuation of the effect in joint (vs. separate) evaluation suggests that consumers’ hesitation to transact with organizations that have a salient privacy notice is not likely driven by an active aversion to assurances but rather by the arousal of dormant privacy concerns.
Paper Information
Full Working Paper Text (pdf) http://www.hbs.edu/faculty/pages/download.aspx?name=20-089.pdf
Working Paper Publication Date: February 2020
HBS Working Paper Number: HBS Working Paper #20-089
Faculty Unit(s): Negotiation, Organizations & Markets .... "
Monday, June 03, 2019
Betrayed by GPS and Assistants
What does this mean? Can it also imply that visualizations are more trusted than they should be? I have only been betrayed by GPS/Maps a couple of times in a long history of using them. By my own navigation skills many more times.
Been a long time promoter of visualization of data and process. But have also always cautioned that visualizations can be a means of delivering confirmation bias via a clever picture. An assumed narrative of truth.
Note also that in the example below only part of it is a map. It is an assistant giving directions, a different thing. So does this means we need to take different kinds of cautions with step by step directions? What does that look like? I point back to my post on 'alerts', which if done intelligently can give us early warning we have gone astray.
Running in Circles: Why Our GPS Devices Can Betray Us in UnDark
Our unshakeable faith in maps — digital or otherwise — has its roots in the cartographic revolution.
05.31.2019 / By M.R. O’Connor ...
Been a long time promoter of visualization of data and process. But have also always cautioned that visualizations can be a means of delivering confirmation bias via a clever picture. An assumed narrative of truth.
Note also that in the example below only part of it is a map. It is an assistant giving directions, a different thing. So does this means we need to take different kinds of cautions with step by step directions? What does that look like? I point back to my post on 'alerts', which if done intelligently can give us early warning we have gone astray.
Running in Circles: Why Our GPS Devices Can Betray Us in UnDark
Our unshakeable faith in maps — digital or otherwise — has its roots in the cartographic revolution.
05.31.2019 / By M.R. O’Connor ...
Seeking Better Alerting
Seems an obvious thing, but the use of alerts has come up in recent interactions as being key to getting things done effectively. How, How often and Followups. Interaction with Risk and Trust of the system and its resource components. Mature Alerts? Here specifically about site reliability, but broadly useful. O'Reilly does a good overview of the topic:
Reduce Toil through better Alerting
How SREs can use a hierarchy for mature alerts.
By Štěpán Davidovič, Betsy Beyer
Check out "The Site Reliability Workbook" for real-world examples of how to put SRE principles and practices to work in your environment.
SRE best practices at Google advocate for building alerts based upon meaningful service-level objectives (SLOs) and service-level indicators (SLIs). In addition to an SRE book chapter, other site reliability engineers at Google have written on the topic of alerting philosophy. However, the nuances of how to structure well-reasoned alerting are varied and contentious. For example, traditional "wisdom" argues that cause-based alerts are bad, while symptom-based or SLO-based alerts are good.
Navigating the dichotomy of symptom-based and cause-based alerting adds undue toil to the process of writing alerts: rather than focusing on writing a meaningful alert that addresses a need for running the system, the dichotomy brings anxiety around deciding whether an alert condition falls on the “correct” side of this dichotomy.
Instead, consider approaching alerting as a hierarchy of the alerts available to you: reactive, symptom-based alerts—typically based on your SLOs—form the foundation of this hierarchy. As systems mature and achieve higher availability targets, other types of alerts can add to your system's overall reliability without adding excessive toil. Using this approach, you can identify value in different types of alerts, while aiming for a comprehensive alerting setup. ....
As detailed below, by analyzing their existing alerts and organizing them according to a hierarchy, then iterating as appropriate, service owners can improve the reliability of their systems and reduce the toil and overhead associated with traditional cause-based and investigative alerts. .... "
Reduce Toil through better Alerting
How SREs can use a hierarchy for mature alerts.
By Štěpán Davidovič, Betsy Beyer
Check out "The Site Reliability Workbook" for real-world examples of how to put SRE principles and practices to work in your environment.
SRE best practices at Google advocate for building alerts based upon meaningful service-level objectives (SLOs) and service-level indicators (SLIs). In addition to an SRE book chapter, other site reliability engineers at Google have written on the topic of alerting philosophy. However, the nuances of how to structure well-reasoned alerting are varied and contentious. For example, traditional "wisdom" argues that cause-based alerts are bad, while symptom-based or SLO-based alerts are good.
Navigating the dichotomy of symptom-based and cause-based alerting adds undue toil to the process of writing alerts: rather than focusing on writing a meaningful alert that addresses a need for running the system, the dichotomy brings anxiety around deciding whether an alert condition falls on the “correct” side of this dichotomy.
Instead, consider approaching alerting as a hierarchy of the alerts available to you: reactive, symptom-based alerts—typically based on your SLOs—form the foundation of this hierarchy. As systems mature and achieve higher availability targets, other types of alerts can add to your system's overall reliability without adding excessive toil. Using this approach, you can identify value in different types of alerts, while aiming for a comprehensive alerting setup. ....
As detailed below, by analyzing their existing alerts and organizing them according to a hierarchy, then iterating as appropriate, service owners can improve the reliability of their systems and reduce the toil and overhead associated with traditional cause-based and investigative alerts. .... "
Subscribe to:
Posts (Atom)