Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Bad UX. "Risiko Begegungen" are not reflected in the "Risiko Status" #113

Closed
yanosz opened this issue Jul 12, 2020 · 23 comments
Closed

Bad UX. "Risiko Begegungen" are not reflected in the "Risiko Status" #113

yanosz opened this issue Jul 12, 2020 · 23 comments
Labels
enhancement New feature or request mirrored-to-jira This item is also tracked internally in JIRA

Comments

@yanosz
Copy link

yanosz commented Jul 12, 2020

Current Implementation

Presumably harmless encounters (e.g. short distance, short time), are displayed as risky "Risiko-Begungen". Nevertheless, they do do not have a noticeable impact on the risk status (e.g. green).

This is confusing. It is warning people about risky things, but the risk doesn't change.

Suggested Enhancement

Reconsider the UX, for instance:

  • Relable "Risiko Begegnungen" to "Mögliche Risiko Begegnungen" "Infizierten Begegnungen"
  • Show seperate counters "Risiko Begegnungen" and "Nicht Risiko Begegungen"
  • If risk is expressed by one comportment (i.e. counter) it should by reflected by all other components (e.g. total status)

Rule of thumb: If there's a risk solely triggered by presumably harmless encounters, than it has to be reflected in the total risk status, e.g. Relabel the risk status to "Leicht Erhöht", when encountering such contacts.

Expected Benefits

UI-Consistency:

  • Better user acceptance by less confusion

Internal Tracking Id: EXPOSUREAPP-2061

@yanosz yanosz added the enhancement New feature or request label Jul 12, 2020
@daimpi
Copy link

daimpi commented Jul 16, 2020

Related: #100

@akuckartz
Copy link

Maybe change "Risiko Begegnungen" to something like "Begegnungen mit Infizierten", that is: remove "Risiko" from that text.

@SonaliDK SonaliDK added the mirrored-to-jira This item is also tracked internally in JIRA label Aug 10, 2020
@yanosz
Copy link
Author

yanosz commented Aug 13, 2020

Now its called "Risiko-Begegnung mit niedrigem Risiko"

  • The text is rather long'ish taking two lines on my screen - "Begegnung mit niedrigem Risiko" would be better, imho
  • Still, the general UX problem remains. The user is warned and informed, but the risk assesment remains unchanged. That doesn't make much sense to me. A quick-fix could be to place this information outside the risk assessment card and not to mention "Risiko" in the label; whereby also outlining that this counter is solely for information purposes.

@yanosz
Copy link
Author

yanosz commented Aug 20, 2020

The associated confusion hit mainstream media: https://www.tagesschau.de/inland/corona-warn-app-risikoermittlung-101.html

Edit: Given a project budget of 68 000 000 € and a bug report rotting for more than month as of today, it is somewhat peculiar that tagesschau is in the need to explain the UX.

@daimpi
Copy link

daimpi commented Oct 23, 2020

@yanosz are your concerns mitigated by the new texts which are live for a while now?

If so feel free to close this issue 🙂.

@yanosz
Copy link
Author

yanosz commented Oct 24, 2020

@daimpi - I don't see any relevant change: The initial problem remains. The App lists risky things "1 Begegnung mit geringem Risiko" but the risk status "green" does not change.

As I said before: If there is a risk by these encouters, this has to be reflected in the total risk status. But in the new screens, the risk relfected in the text componenent is not reflected in the card component (green). The generated confusion is discussed at various web pages.

Trying to do some "Think aloud" (https://en.wikipedia.org/wiki/Think_aloud_protocol), I come up with this these questions:

  • Why is it called "Risiko Begungen" and not "Begegnungen mit Infizierten"? Is there a subtential difference? If so, which?
  • Is there Risiko originating from presumable these encounters? In case its not: this is not a "Risiko Begegung" - why is it called "Risiko Begegnungen", then?
  • Why is the risk still "green"? What is the exact reason?
    • How can I estimate my personal risk?
    • How can I get more Information on the encounter? When was it? Who was infected?
    • How many "Begegnung mit niedrigem Risiko" are fine? 1? 10? 100? 1000? Per day, per week, at all?
  • What's the chance that the App is wrong and a transmission occured anyway?
  • Will the counter decrement again? When does it do so? Why is it decremented after n days?

Some ideas:

  • If the counter is not used for estimating the total risk, it should be placed outside the green-red card, cause the card is where people expect information on this. If it is, the actual, statistical impact should be outlined.
  • The App could inform tech savvy users about 3rd party possibilites for retrieving more details (e.g. https://github.com/mh-/corona-warn-companion-android)
  • Avoid "Risiko" in the label. It is used to name different things. There is a clear difference between these two concepts. They should be named differently.
    • A statistics related counter, possibly used in the calculation of a risk - but not, to a comprehensible extent. I.e. a possible input parameter for the calcuation
    • The risk of a transmission - i.e. the actual result of the calculation

IMHO people tent to understand the "Risiko" as the actual result, cause the App as a whole is used to estimate the Risiko. IMHO this is the actual confusion expressed by all media sources discussing "Begegnungen mit Geringem Risiko". For this, it's a bad thing to even label presumably harmless encounters as some kind of "Risiko".

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Oct 24, 2020

@yanosz

Just a small remark from me:
Did you see that the App now calls it "Begegnungen mit niedrigem Risiko"?

@yanosz
Copy link
Author

yanosz commented Oct 24, 2020

@yanosz

Just a small remark from me:
Did you see that the App now calls it "Begegnungen mit niedrigem Risiko"?

Yes. Which is even more confusing, cause "niedriges Risiko" in the encounter is not "niedriges Risiko" in the card. People expect some relation - same name -, but it is still uncomprehensible.

@rugk
Copy link

rugk commented Oct 24, 2020

Also there is a huge long explanation text if you tap on the card.

Will the counter decrement again? When does it do so? Why is it decremented after n days?

Yes, if the "Risikobegenung" is longer than 14 days ago.

@yanosz
Copy link
Author

yanosz commented Oct 24, 2020

Also there is a huge long explanation text if you tap on the card.

Edit - sorry, missed that point
Correct. Some tl;dr / wall-of-text kind of message. And even when multiple encouters are present, the text says "Sie hatten eine Begegung", well .. there is more than one.

Will the counter decrement again? When does it do so? Why is it decremented after n days?

Yes, if the "Risikobegenung" is longer than 14 days ago.

this somehow misses the point of the think aloud protocol. These questions should be answered in the App, not on github...

The question is raised, because the relationship of "für ihre Risikoermittlung wird nur der Zeitraum der letzten 14 Tage betrachtet" and "Dennoch als niedrig eingestuft" is confusing. IMHO it is not comprehensible, to what extent the counter is impacting the estimated risk ... and if the note on 14 days also applies to the counter.

E.g. having "in der Corona-App wird nur der Zeitraum der letzten 14 Tage betrachtet" is better, imho.

@yanosz
Copy link
Author

yanosz commented Oct 24, 2020

P.S. I'd like to make this explicit https://www.corodok.de/app-risiko-ohne-risiko/ boils it down to:

"Es gibt also eine Warnung, bei der man nichts tun muß, ein Risiko ohne Risiko."

IMHO this is also a good way of describing the associated confusion

P.P.S.

  1. Relable "Begegnungen mit niedrigem Risiko" to "Begegnungen mit infizierten"
  2. Change "Sie hatten eine" to reflect the actual number
  3. Change the tl;dr porblem by rephrasing the text without changing its meaning.
    Some phrases almost appear to be included twice "Infektionsrisiko wird auf Grundlage der Daten der Risiko-Ermittlung" - "Das Infektionsrisiko wird anhand der Daten der Risiko-Ermittlung". Some sentences are spawning up to eight lines on the screen and are really hard to read. That's easy to fix. Consider "Einfache Sprache"
  4. Add a note on privacy: "Die Corona-App respektiert Ihre Privatheit. Wir wissen nicht, wo und wann genau Sie infizierte getroffen haben. Die Daten sind dennoch auf Ihrem Smartphone gespeichert."
  5. Add a brief explanation on how many presumably harmless encounters are ok. I have no proposal atm.

IMHO, this would remove some confusion.

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Oct 24, 2020

@yanosz
So looks like you are against showing low risk exposures at all?
Maybe take a look at: #181

Change "Sie hatten eine" to reflect the actual number

See #178

@yanosz
Copy link
Author

yanosz commented Oct 25, 2020

Heiho,

@yanosz
So looks like you are against showing low risk exposures at all?
Maybe take a look at: #181

I proposed to relabel it. It's fine to have such a counter. But this value is way too "raw" to express some kind of risk. It's a parameter for calculating the risk. It does not express any risk by itself. ... just give it a proper label.

Take it this way:
Everybody understands, that she or he encounteres infected people if there are a lot. You can explain this and everything is fine.
This basically shows that the App is working fine and that other people are using the app to protect each other. That's good!

The point is, that the UX mistakenly suggest that this value determines some total risk to a certain, comprehensible and relativly higher degree. This is not given.

@webermike
Copy link

Please show Date and Time of later on announced risk contacts, even if this leads to still having a green status.

As such contacts might occur only at shopping or eating in a restaurant, one can reconstruct with Date and Time where one habe been and if shopping or queuing anywhere is the risk reason.

This would enhance the analyse and discussion and avoiding of behavior in the future much, when it ia shown if the risk contact was at 8:00 in the bus ir at 12:00 in the McDonalds restaurant or at work at 10:00 o'clock at a certain date/day.

so it is not about "10 days ago" but about exact time and day.

Thanks for implementing that local showup fast.

@yanosz
Copy link
Author

yanosz commented Nov 8, 2020

Please show Date and Time of later on announced risk contacts, even if this leads to still having a green status.

Unfortunatly, this is OT as of this issue. Please check other, already existing tickets or have a look at https://github.com/mh-/corona-warn-companion-android

@yanosz
Copy link
Author

yanosz commented Dec 21, 2020

Mainstream media still is still discussing the issue, while the bug is still rotting in the tracker:

https://taz.de/Unverstaendliche-Corona-Warn-App/!5735104/

@heinezen
Copy link
Member

With ENFv2 used in the newest app version, some of the suggestions were addressed: Harmless encounters with distance > 8m (73dB signal strength) and duration of less than 10 minutes are filtered out by the app and are not displayed as risk encounters. See https://www.coronawarn.app/en/faq/#encounter_count_19 for details.


Corona-Warn-App Open Source Team

@yanosz
Copy link
Author

yanosz commented Dec 21, 2020

With ENFv2 used in the newest app version, some of the suggestions were addressed: Harmless encounters with distance > 8m (73dB signal strength) and duration of less than 10 minutes are filtered out by the app and are not displayed as risk encounters. See https://www.coronawarn.app/en/faq/#encounter_count_19 for details.

Corona-Warn-App Open Source Team

Sure about the ticket? That's not suggested in this one.

@heinezen
Copy link
Member

@yanosz Yes, in particular, harmless encounters are now filtered and multiple low risk encounters count towards a total risk score that can lead to an overall high risk.


Corona-Warn-App Open Source Team

@yanosz
Copy link
Author

yanosz commented Dec 27, 2020

@yanosz Yes, in particular, harmless encounters are now filtered and multiple low risk encounters count towards a total risk score that can lead to an overall high risk.

@heinezen : To avoid misunderstandings: Filtering harmless encounters is not part of this ticket. This ticket addresses the UX mismatch between risk expressed in different components:
The "risk" expressed by the status "green" is not reflected in the risk expressed by the counter that counts "risk" encounters. The proposal is to rename "risk encounters" to "infectious encounters", because the counter value is too raw, i.e., it does not express risk to some determined and comprehensible degree.

Are status and counter aligned as of now? I.e., does an increasing counter result in risk status red as of now?

@heinezen
Copy link
Member

heinezen commented Jan 7, 2021

@yanosz You mentioned harmless encounters in your introduction, so I thought this information would be useful here. Sorry if it was confusing.

Are status and counter aligned as of now? I.e., does an increasing counter result in risk status red as of now?

Yes! This is what I wanted to say. The ENFv2 evaluation considers multiple this now. The normalized exposure time of low risk encounters is summed up for the day. So multiple low risk encounters will lead to a high risk score if the sum of their individual score is higher than the "high risk" threshold.

See here for more information: https://github.com/corona-warn-app/cwa-documentation/blob/master/images/risk_calculation/risk_calculation_enf_v2_overview.pdf

@ndegendogo
Copy link

ndegendogo commented Jan 7, 2021

So multiple low risk encounters will lead to a high risk score if the sum of their individual score is higher than the "high risk" threshold.

I think the confusing fact is, that the number shown is not the sum of the risk scores.
cwa before version 1.9 showed number of encounters. As far as I understand, since v 1.9 it will show number of days with encounters. But the risk score is still hidden from the user.

@yanosz
Copy link
Author

yanosz commented Jan 8, 2021

closed, fixed

@yanosz yanosz closed this as completed Jan 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request mirrored-to-jira This item is also tracked internally in JIRA
Projects
None yet
Development

No branches or pull requests