Desperately Seeking Reassurance: Analyzing Requestive Hint Miscommunication in an Email Exchange

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Desperately Seeking Reassurance: Analyzing Requestive Hint Miscommunication in an Email Exchange - Presentation Transcript

    1. Desperately seeking reassurance: Analyzing requestive hint miscommunication in an email exchange
      A presentation by Andrew Boon
      (Toyo Gakuen University)
    2. Email
      has transformed the way we communicate.
      is an asynchronous medium – carefully crafted messages but email writers often think in speech mode (Grosvenor, 1998).
      can support near-synchronous interaction.
      is fast and convenient but often reduces interaction to the exchange of minimalist messages (Waldvogel, 2002).
      can create miscommunication between sender and recipient.
    3. The interlocutors
    4. The email exchange
      Email 1:
       
      From: Steve
      Date: Thursday, August 17, 2006 6:48 AM
      To: John
       
      1] Hi John, 2] I think that was my best scoring assignment actually - 3] 85 (distinction). 4] I remember reading somewhere that we need an average 5] of credit to advance - you'll be able to do that OK. I 6] got lower grades than you with A university (Bs) but had 7] mainly distinctions with B university. This might change 8] soon though - assignments are getting harder! 9] I'm writing one now - can I send it to you sometime10] early next week? The deadline is ages away - but I11] want to knock one on the head during the holidays.12] all the best13] Steve
      (Steve, personal communication, August 17, 2006)
       
    5. The email exchange
      Email 2:
       
      From: John
      Date: Thursday, August 17, 2006 6:51 AM
      To: Steve
       
      1] Steve, 2] Thanks for the info!! 3] Sure - I also have one due in 2 weeks which I haven't started yet!!
      4] John.
      (John, personal communication, August 17, 2006)
       Email 3:
       
      From: Steve
      Date: Thursday, August 17, 2006 6:52 AM
      To: John
      1] yep - send it over.
      (Steve, personal communication, August 17, 2006)
      Miscommunication?
    6. Analysis
      The utterance is successfully understood as being an indirect request
      The intended perlocutionary effect of the requestive hint is unsuccessful
    7. Reasons for Steve’s interpretation
      1] Steve seeks to find the quickest route to the implicit relevance of the requestive hint.
      2] “Differences in the communicative worlds of the interlocutors can bring about divergent understandings” (Weigand, 1999).
      3] The speed of the exchange (6.51am - 6.52am).
      4] Previous email history - lack of requestive hints between John and Steve.
      5] Use of double exclamation marks to subtly imply a sense of concern!! - too individualistic and ambiguous.
    8. Analysis continued
      The requestive hint is framed to maintain face at the expense of clarity
    9. Conclusion
      Non-conventional indirect speech acts via email greatly enhance the potential for miscommunication
      Consider the cost to “face” versus being understood
      So what? What are the pedagogical implications of this study?
      SAVE THE TREES! – Boon, A. 2008. Desperately seeking reassurance: Analyzing requestive hint miscommunication in an email exchange. Bulletin of Toyo Gakuen University 16: 57-65 (Available online).

    + Andy  BoonAndy Boon, 2 months ago

    custom

    185 views, 0 favs, 0 embeds more stats

    This presentation is a companion to the research pa more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 185
      • 185 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 2
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories