meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
conversational_maxims [2019/07/11 07:58]
amandahass_wiki [Quality] 		conversational_maxims [2019/08/07 16:21] (current)
lisa.illgen_concentrix.com
Line 3: Line 3:
 ==== Conversational Maxims ==== ==== Conversational Maxims ====
 ==== What are the conversational maxims? ==== ==== What are the conversational maxims? ====
-The conversational maxims (also known as "​[[http://​en.wikipedia.org/​wiki/​Paul_Grice| Gricean maxims"​]]) are a framework for explaining how conversation proceeds rationally and efficiently. For conversational speech applications,​ they provide a reasonable though incomplete set of communication guidelines. Following them will facilitate straightforward communication;​ violating them will cause difficulties - "​Failure to adhere to the maxims.... opens the door to miscommunication with and mistrust of the application"​ (Lewis, 2011, p. 34).+The conversational maxims (also known as "​[[http://​en.wikipedia.org/​wiki/​Paul_Grice| Gricean maxims"​]]) are a framework for explaining how conversation proceeds rationally and efficiently. For conversational speech applications,​ they provide a reasonable though incomplete set of communication guidelines. Following them will facilitate straightforward communication;​ violating them will cause difficulties - "​Failure to adhere to the maxims.... opens the door to miscommunication with and mistrust of the application"​ ([[references#​lewis2011|Lewis, 2011]], p. 34).
  
 The conversational maxims are: The conversational maxims are:
Line 11: Line 11:
   * **Manner**: Avoid obscure expression, avoid ambiguity, be brief, and be orderly.   * **Manner**: Avoid obscure expression, avoid ambiguity, be brief, and be orderly.
  
-In addition to their obvious application to VUI design, the maxims have been used as the basis for standardized questionnaires to assess of the quality of conversational systems and IVRs (R. Bloom et al., 1999; Polkosky, 2002, 2005a, 2005b, 2008).+In addition to their obvious application to VUI design, the maxims have been used as the basis for standardized questionnaires to assess of the quality of conversational systems and IVRs ([[references#​bloom1999|R. Bloom et al., 1999]]; Polkosky, ​[[references#​polkosky2002|2002]], [[references#​polkosky2005a|2005a]], [[references#​polkosky2005b|2005b]], [[references#​polkosky2008|2008]]).
  
 Note that an underlying theme that runs across the maxims is one of conversational efficiency -- provide the necessary information but no more; don't lie or provide potentially misleading information;​ be relevant, clear, brief, and orderly. Note that an underlying theme that runs across the maxims is one of conversational efficiency -- provide the necessary information but no more; don't lie or provide potentially misleading information;​ be relevant, clear, brief, and orderly.
Line 43: Line 43:
 It's important to address common caller goals, regardless of what the business wants to do with them. Say a certain common task must be done on the website. It should still be included in the IVR menus, with an explanation of what the caller needs to do. Omitting it just means the caller will take a roundabout way to an agent who probably can't help them. It's important to address common caller goals, regardless of what the business wants to do with them. Say a certain common task must be done on the website. It should still be included in the IVR menus, with an explanation of what the caller needs to do. Omitting it just means the caller will take a roundabout way to an agent who probably can't help them.
  
 +**// Example of Broken Relation Maxim //**\\
 +Giving instructions for things that are not currently useful, such as explaining a return policy before someone has even placed an order.
 ==== Manner ==== ==== Manner ====
 **// Organize information clearly //**\\ **// Organize information clearly //**\\
Line 56: Line 58:
 This is consistent with the maxims of both Quantity and Manner. It is well known that callers find it very irritating to answer a question in the IVR, only to have to provide that same information again following transfer to an agent. The conversational maxims and their underlying focus on conversational efficiency help to explain this irritation. For this specific example, the solution is to ensure that the system includes computer-telephony integration (CTI -- also see [[ Multi-Item Menus | Partial Automation vs. Full Automation]]),​ and that agents are trained to use it. This is consistent with the maxims of both Quantity and Manner. It is well known that callers find it very irritating to answer a question in the IVR, only to have to provide that same information again following transfer to an agent. The conversational maxims and their underlying focus on conversational efficiency help to explain this irritation. For this specific example, the solution is to ensure that the system includes computer-telephony integration (CTI -- also see [[ Multi-Item Menus | Partial Automation vs. Full Automation]]),​ and that agents are trained to use it.
  
 +**// Example of Broken Manner Maxim //**\\
 +As mentioned above, using technical jargon that confuses the user will only create a negative experience.
 ==== Other maxims ==== ==== Other maxims ====
 There are other maxims or guiding principles not directly related to conversational maxims. There are other maxims or guiding principles not directly related to conversational maxims.
Line 63: Line 67:
  
 **// Minimize data dip latency //**\\ **// Minimize data dip latency //**\\
-This is a general guideline not necessarily implied by the conversational maxims, other than the underlying theme of efficiency. A common industry goal is for 95% of system responses to occur within two seconds of the end of a caller’s input (Balentine & Morgan, 2001; Fried & Edmondson, 2006). Toward reaching this goal, it is important to minimize the data dip latency -- the amount of time it takes to get data from a database.+This is a general guideline not necessarily implied by the conversational maxims, other than the underlying theme of efficiency. A common industry goal is for 95% of system responses to occur within two seconds of the end of a caller’s input ([[references#​balentine2001|Balentine & Morgan, 2001]]; [[references#​fried|Fried & Edmondson, 2006]]). Toward reaching this goal, it is important to minimize the data dip latency -- the amount of time it takes to get data from a database.
  
-When it will take longer than 2 seconds for an application to respond to a caller'​s input, it is necessary to manage the caller experience during the wait (Lewis, 2011). Often, simply saying something like, "Just a moment while I look that up" serves this purpose. Several researchers (e.g., Boyce, 2008; Fröhlich, 2005) have published data that support guidelines for the management of processing time.+When it will take longer than 2 seconds for an application to respond to a caller'​s input, it is necessary to manage the caller experience during the wait ([[references#​lewis2011|Lewis, 2011]]). Often, simply saying something like, "Just a moment while I look that up" serves this purpose. Several researchers (e.g., ​[[references#​boyce2008|Boyce, 2008]]; [[references#​fröhlich|Fröhlich, 2005]]) have published data that support guidelines for the management of processing time.
  
 Use the following table to guide the management of processing time in conversational systems. Use the following table to guide the management of processing time in conversational systems.