<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>A Proposed Evaluation of Just Not Sorry, a Technology to Influence Language Use</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Janet Davis</string-name>
          <email>davisj@whitman.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer Science Whitman College</institution>
          ,
          <addr-line>Walla Walla, WA 99362</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This poster will present plans for an empirical evaluation of Just Not Sorry, a Gmail plug-in designed for women in business and leadership. As the user composes email, Just Not Sorry highlights words that could undermine an image of confidence or authority. The proposed study seeks not only to evaluate the effectiveness of Just Not Sorry as a persuasive technology, but also to characterize reasons and values un- derlying decisions about adoption.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Background</title>
    </sec>
    <sec id="sec-2">
      <title>Goals and Research Questions</title>
      <p>The goal of this poster presentation will be to obtain feedback on a proposed empirical
evaluation of Just Not Sorry. Through this study, I seek to address two main research
questions:
RQ1. What reasons and values inform decisions (not) to adopt Just Not Sorry ?
RQ2. Once adopted, does Just Not Sorry change behaviors and attitudes?</p>
      <p>
        Why study adoption? At a surface level, Just Not Sorry is a boring technology [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ],
an email plug-in inspired by the “spellcheck” metaphor [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. It is simple to understand
and adopt, and fits effortlessly into everyday habits. At another level, the behavior
change that Just Not Sorry seeks to promote is surprisingly controversial. A recent
media analysis investigates published opinions about Just Not Sorry with respect to
underlying values and perspectives on feminism [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. An empirical study would investigate
whether reasons for deciding against adoption are similar to reasons for opposition
expressed in the media.
      </p>
      <p>
        Why study effectiveness? First, Reiss claims that Just Not Sorry is effective at
influencing both behaviors and attitudes [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], but presents only anecdotal evidence to support
this claim. Second, while Just Not Sorry achieved a significant user base, it has shrunk
over time by a factor of ten. This fact could be interpreted as evidence of either failure
of long-term adoption, or of success at changing attitudes or behaviors making further
use unnecessary. Finally, to the best of my knowledge, no work presented in the
PERSUASIVE conference series has addressed the effectiveness of persuasive
technology at changing habits of language use. Beyond intrinsic interest, the proposed study
may inform future evaluation studies of tools now under development, e.g., to mitigate
gender bias in academic recommendation letters [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Investigating reasons and values</title>
      <p>
        Our recent media analysis [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] suggests some possible answers to RQ1, but there is no
reason to think that published opinions about Just Not Sorry are either exhaustive or
representative of a broader public. Therefore, a study addressing RQ1 should support
both quantitative analysis to assess the representativeness of the published opinions,
and qualitative analysis to uncover values and reasons that were left out. The choice to
use surveys, interviews, or a combination of both will depend on decisions about the
need to reach a large number of participants versus the ability to probe their answers.
      </p>
      <p>The media analysis suggests possible reasons for adopting Just Not Sorry that we
would seek to confirm:
– to enhance one’s confidence, achievement, or social power;
– to become more mindful of one’s habitual use of apologies, hedge words, and
intensifiers, and hence to use such language more intentionally or sincerely;
– to promote the status of women in the workplace and thus gender equality.
The media analysis also discovered reasons for opposing the adoption of Just Not Sorry
:
– concerns that Just Not Sorry will undermine rather than enhance confidence,
achievement, or social power;
– concerns that Just Not Sorry is insensitive to linguistic or situational context;
– valuing apologies, hedge words, and intensifiers as women’s language or as a form
of politeness;
– a belief that Just Not Sorry is a distraction from more fundamental problems of
gender inequality.</p>
      <p>We can also imagine more personal reasons for choosing not to adopt Just Not Sorry
that may not have appeared in the media as reasons to recommend against its use, such
as
– satisfaction with one’s current behavior;
– annoyance at receiving feedback while writing;
– reliance on an email system other than GMail or a web browser other than Chrome.</p>
      <p>
        Just Not Sorry ’s support for users’ autonomy and privacy were discussed as positive
attributes in the media opinions, and we would be surprised to see these cited as reasons
to choose not to adopt the tool. While the operation of Just Not Sorry is generally
transparent, currently there is no end-user documentation of the phrases it flags [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], which
might be a deterrent for some.
      </p>
      <p>
        To add nuance to discussion of gender equality and tools to support changing
language use, an interview might invite participants to compare Just Not Sorry to a tool
such as the #GenderBias Slack plug-in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], which also employs a spellcheck metaphor
but flags biased terms used to describe other people.
4
      </p>
    </sec>
    <sec id="sec-4">
      <title>Investigating effectiveness</title>
      <p>
        Hypotheses regarding RQ2 are informed by the “Change” dimension of the O/C matrix
[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], focusing on interactions between compliance, behavior change, and attitude
change. Specifically:
H1. The number of suggestions per email per user will decline over time, as users
change their behavior to avoid proscribed words and phrases.
      </p>
      <p>H2. Compliance will never reach 100%, as users will make deliberate choices not to
comply with suggestions they deem inappropriate.</p>
      <p>H3. Compliance will decline over time. As a user begins to avoid proscribed words and
phrases, an increasing portion of the suggestions will be deemed inappropriate.
H4. Some users will stop using the extension because their behavior has changed and
suggestions are no longer deemed valuable.</p>
      <p>H5. Users will develop a more confident attitude with respect to the tone of their
emails.</p>
      <p>H6. Users will report that they avoid using target words and phrases in other speech
and writing, beyond email.</p>
      <p>To address hypotheses 1-3, we will develop an instrumented version of Just Not
Sorry that tracks, for each user, the suggestions offered by the system, which the user
complies with, and which they do not. Participants who indicate a willingness to use
Just Not Sorry in the initial interview about adoption will
be invited to install this instrumented version and use it for an extended period of time,
likely 4–6 weeks.</p>
      <p>The collected data will also reveal when users stop using Just Not Sorry, which
addresses part of hypothesis 4. Reasons for discontinuing use, as well as attitude change,
will be addressed through a post-intervention survey or interview.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgements</title>
      <p>Thanks to Whitman College, and specifically the Louis B. Perry Summer Re- search
Endowment and the Microsoft Chair in Computer Science, for supporting this work.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Catalyst: #BiasCorrect Slack Plugin</surname>
          </string-name>
          (
          <year>2020</year>
          ), https://www.catalyst.org/biascorrect/
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Davis</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nyatichi</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Values and Politics of a Behavior Change Support System</article-title>
          .
          <source>In: 18th International Conference on the Ethical and Social Impacts of ICT. La Rioja</source>
          ,
          <source>Spain (Jun</source>
          <year>2020</year>
          ), meeting Name:
          <article-title>ETHICOMP 2020 Reporter: 18th Inter- national Conference on the Ethical and Social Impacts of ICT</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>Def</given-names>
            <surname>Method: Just Not Sorry - the Gmail</surname>
          </string-name>
          Plug-in
          <source>(v1.6</source>
          .0)
          <issue>(</issue>
          <year>Mar 2019</year>
          ), https://chrome.google.com/webstore/detail/just
          <article-title>-not-sorry-the- gmail/fmegmibednnlgojepmidhlhpjbppmlci?hl=en-</article-title>
          <string-name>
            <surname>US</surname>
          </string-name>
          , reporter: Chrome Web Store
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. JimLynchCodes:
          <article-title>Document Phrases The Algo Looks For In README? · Issue #57 defmethodinc/just-not-</article-title>
          <string-name>
            <surname>sorry</surname>
          </string-name>
          (
          <year>Jan 2020</year>
          ), https://github.com/defmethodinc/just- not-sorry/issues/57
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Oinas-Kukkonen</surname>
          </string-name>
          , H.:
          <article-title>A foundation for the study of behavior change support sys- tems</article-title>
          .
          <source>Personal and Ubiquitous Computing</source>
          <volume>17</volume>
          (
          <year>Aug 2013</year>
          ), reporter: Personal and Ubiquitous Computing
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Reiss</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Just Not Sorry! (the backstory)</article-title>
          (
          <year>Dec 2015</year>
          ), https://medium.com/@tamireiss/just
          <article-title>-not-sorry-the-backstory-33f54b30fe48, reporter: The Medium</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Saderi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>This open-source tool shines a light on gender bias</article-title>
          (May
          <year>2018</year>
          ), https://medium.com
          <article-title>/read-write-participate/this-open-source-tool-shines- a-light-on-genderbias-4a51bb5ff4ac</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. @tamireiss: ”
          <article-title>@alicegoldfuss I made an app that 350k ppl use #justnotsorry #WITBragDay https</article-title>
          ://t.co/a3pyq9ujp3” (
          <year>Aug 2017</year>
          ), https://twitter.com/tamireiss/status/896384586833432576, reporter: Twitter
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Twersky</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Davis</surname>
          </string-name>
          , J.: “
          <string-name>
            <surname>Don't Say</surname>
          </string-name>
          <article-title>That!”</article-title>
          . In: Persuasive Technology. pp.
          <fpage>215</fpage>
          -
          <lpage>226</lpage>
          . Lecture Notes in Computer Science, Springer International Publishing (
          <year>2017</year>
          ), reporter: Persuasive Technology
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Wai</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mortensen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Persuasive Technologies Should Be Boring</article-title>
          . In: Persua- sive
          <source>Technology</source>
          . pp.
          <fpage>96</fpage>
          -
          <lpage>99</lpage>
          . Lecture Notes in Computer Science, Springer, Berlin, Heidelberg (
          <year>2007</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>540</fpage>
          -77006-012
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>