Affirmation Charts

[jaedoucette]

As a PM, I want to develop and release metrics as quickly as possible, so that we can add value to our product and get customer feedback.

As a PM, I have a December 2019 delivery for a client (GT) and would like to give them as many new metrics as possible, so that they feel like they are getting more value and that we are able to have direct customer feedback and delivery.

Mockup of metrics layout is here: https://balsamiq-wireframes.appspot.com/?state={%22action%22:%22open%22,%22ids%22:[%221mGW0wxD7_7hzQ45EA6AYL2WDp06tRq8H%22],%22userId%22:%22115623783603948978633%22}

*** Acceptance Criteria ***

• Two new Interruption metrics that use the same display as the "Influence" metrics, as described below.
• The back of the "who affirmed you" card should read "This metric shows how many times you were affirmed. Affirmations indicate interest and attention to what you are saying".
• The back of the "who you affirmed card" should read "This metric shows how many times you affirmed another person. Affirmations indicate interest and attention to what others are saying".

** Background **
Users want to see an affirmations chart, showing who affirmed whom during a meeting. This story is about creating a prototype design for such a chart.

This chart should look very similar to the existing influence and interruption charts.

An affirmation event is identical to an interruption event, except that in the data is computed with a slightly different algorithm. An affirmation event is defined as:

• One person started speaking while someone else was speaking (i.e. their utterance starts while someone else is speaking).
• The overlap in speaking is > 0.25 seconds
• The total length of the affirming utterance is < 2s.
• The affirming utterance ends before the speaker it interrupted stops talking.

The affirmation chart should be identical to the existing influence chart, but with the caption "Who You Affirmed" and "Who Affirmed You" instead of "Who You Influenced" and "Who Influenced You".

The feature should be written so that it is easy to configure the cutoffs (> 0.25 seconds, < 2 seconds), so that we can easily tune this during testing.

After the feature is implemented, we should test it during many Riff meetings.

[brecriffs]

PR posted and attached to #154

[adonahue]

Reviewed this story in Chrome, and accepted in terms of metrics display. More testing on how the metrics get generated would be useful. Text on the back of the card is different than the story criteria but makes sense given how the graphic evolved.