CFP: IEEE Special Issue: Designing a Better User Experience for Self-Service
"lex_v_v" <[email protected]> Thu, 30 Jun 2011 11:44:29 -0000
| Newsgroups | gmane.comp.hci.experiencedesign |
|---|---|
| Message-ID | <[email protected]> |
--iaNvh2GAIPQhivWrSA2QOh0SqpHFX8JFVMFOrXP Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable IEEE Transactions on Professional Communication Call for Submissions: Autumn 2012 Special Issue on Designing a Better User Experience for Self-= Service Systems Guest editors: Thea van der Geest, Judy Ramey, Stephanie Rosenbaum, Lex van= Velsen Format and goals: Have you conducted formal research or done a case study on some aspect of = the design of the user experience for a `self-service' application? Have yo= u faced the challenge of creating and systematically analyzing or evaluatin= g the user experience for systems where users do what clerks, government em= ployees, or other "services" people used to do for them?=20 If so, we invite you to contribute to the Autumn 2012 special issue of=20 IEEE Transactions on Professional Communication on Designing a Better User Experience for Self-Service Systems We aim at bringing together a set of empirical and critical service design = studies and user-focused evaluations of the user experience of "self-servi= ce" systems.=20 If you think your study is a good fit for this special issue, be sure to le= t us know as soon as possible. Submit a two-page abstract summarizing your = approach and your findings before 1 September. We will use the abstracts to= select authors, who will be invited to submit a complete article. (See bel= ow for the timeline for submissions.) =20 Prospective authors should have: =95 Taken part in a systematical evaluation or case study of a self-servic= e system or process =95 Analyzed or evaluated the problems and solutions for creating a good s= elf-service user experience =95 Obtained organizational approval for publishing about the self-service= systems study. Requirements for abstracts: Abstracts for reports on empirical, user-focused studies on self-service (t= wo pages long) should address: 1. Theoretical perspective: from what point of view are you analyzing and e= valuating the self-service process or system?=20 2. Research questions: what was the self-service research focus, and how wi= ll it add to our understanding and knowledge of self-service? 3. Method: how did you go about investigating the research questions? Who w= ere your participants, and how did you collect data and analyze it? 4. Findings: what did you learn? 5. Discussion: what are the possible implications and limitations of your r= esults for service application designers and other professional communicato= rs? What future work is called for? To help the authors use criteria similar to our peer reviewers and clarify = their experience in a manner that others can use to generalize from, abstra= cts for case studies (two pages long) should address at least the following= :=20 1. Explicit description of the problem(s) designers were trying to solve. 2. Methodology: How the case study data was compiled. 3. Project particulars: Relative budget, relative amount of development tim= e, constraints, technologies used (i.e. proprietary or open source). The case studies should address one or more of the following themes: 1. Pre-design approaches, methods, or results: User studies of context of = use, users' expectations of service, prior knowledge, etc. 2. Actual design: What cues were included for boosting users' performance a= nd perceptions (sense of trust, privacy protection, confidence, empowerment= )? How were user problems with the self-service avoided or solved?=20 3. Failure strategies: How could people escalate their `problem' from the s= elf-service situation to an interaction with human or organizational suppor= t, then return successfully to the self-service environment? 4. Results: Approaches, methods, and metrics for determining the impact and= quality of self-service. Prospective authors who have other ideas for relevant articles for this spe= cial issue, please contact the editors.=20 Timeline for submissions 1. Drop a note if you're interested to contribute, as soon as possible! 2. Abstract submission deadline: September 1st, 2011. 3. Notification of authors: October 1st , 2011. Those whose abstracts are a= ccepted will be invited to submit a complete article. 4. Submission of complete articles: January 15th , 2012. 5. Review back to authors: March 1st , 2012. 6. Revised and resubmitted articles submitted for second review: May 1st, 2= 012. 7. Final and complete articles submitted: July 1st, 2012. For all questions and notes concerning the special issue, and for the abstr= act of your proposed article, please send a e-mail to:=20 Thea van der Geest, [email protected] or the co-editors, Judy Ramey, [email protected] Stephanie Rosenbaum, [email protected] Lex van Velsen, [email protected] --iaNvh2GAIPQhivWrSA2QOh0SqpHFX8JFVMFOrXP Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/htm= l4/strict.dtd"> <html> <head> </head> <body style=3D"background-color: #fff;"> <span style=3D"display:none"> </span> <!--~-|**|PrettyHtmlStartT|**|-~--> <div id=3D"ygrp-mlmsg" style=3D"position:relative;"> <div id=3D"ygrp-msg" style=3D"z-index: 1;"> <!--~-|**|PrettyHtmlEndT|**|-~--> <div id=3D"ygrp-text" > =20=20=20=20=20=20 =20=20=20=20=20=20 <p>IEEE Transactions on Professional Communication Call for Submissio= ns:<br> Autumn 2012 Special Issue on Designing a Better User Experience for Self-= Service Systems<br> Guest editors: Thea van der Geest, Judy Ramey, Stephanie Rosenbaum, Lex van= Velsen<br> <br> Format and goals:<br> Have you conducted formal research or done a case study on some aspect of = the design of the user experience for a `self-service' application? Have yo= u faced the challenge of creating and systematically analyzing or evaluatin= g the user experience for systems where users do what clerks, government em= ployees, or other "services" people used to do for them? <br> <br> If so, we invite you to contribute to the Autumn 2012 special issue of <br> IEEE Transactions on Professional Communication on<br> Designing a Better User Experience for Self-Service Systems<br> We aim at bringing together a set of empirical and critical service design = studies and user-focused evaluations of the user experience of "self-= service" systems. <br> <br> If you think your study is a good fit for this special issue, be sure to le= t us know as soon as possible. Submit a two-page abstract summarizing your = approach and your findings before 1 September. We will use the abstracts to= select authors, who will be invited to submit a complete article. (See bel= ow for the timeline for submissions.)<br> <br> Prospective authors should have:<br> =95 Taken part in a systematical evaluation or case study of a self-servic= e system or process<br> =95 Analyzed or evaluated the problems and solutions for creating a good s= elf-service user experience<br> =95 Obtained organizational approval for publishing about the self-service= systems study.<br> <br> Requirements for abstracts:<br> Abstracts for reports on empirical, user-focused studies on self-service (t= wo pages long) should address:<br> 1. Theoretical perspective: from what point of view are you analyzing and e= valuating the self-service process or system? <br> 2. Research questions: what was the self-service research focus, and how wi= ll it add to our understanding and knowledge of self-service?<br> 3. Method: how did you go about investigating the research questions? Who w= ere your participants, and how did you collect data and analyze it?<br> 4. Findings: what did you learn?<br> 5. Discussion: what are the possible implications and limitations of your r= esults for service application designers and other professional communicato= rs? What future work is called for?<br> <br> To help the authors use criteria similar to our peer reviewers and clarify = their experience in a manner that others can use to generalize from, abstra= cts for case studies (two pages long) should address at least the following= : <br> 1. Explicit description of the problem(s) designers were trying to solve.<b= r> 2. Methodology: How the case study data was compiled.<br> 3. Project particulars: Relative budget, relative amount of development tim= e, constraints, technologies used (i.e. proprietary or open source).<br> The case studies should address one or more of the following themes:<br> 1. Pre-design approaches, methods, or results: User studies of context of = use, users' expectations of service, prior knowledge, etc.<br> 2. Actual design: What cues were included for boosting users' performance a= nd perceptions (sense of trust, privacy protection, confidence, empowerment= )? How were user problems with the self-service avoided or solved? <br> 3. Failure strategies: How could people escalate their `problem' from the s= elf-service situation to an interaction with human or organizational suppor= t, then return successfully to the self-service environment?<br> 4. Results: Approaches, methods, and metrics for determining the impact and= quality of self-service.<br> <br> Prospective authors who have other ideas for relevant articles for this spe= cial issue, please contact the editors. <br> <br> Timeline for submissions<br> 1. Drop a note if you're interested to contribute, as soon as possible!<br> 2. Abstract submission deadline: September 1st, 2011.<br> 3. Notification of authors: October 1st , 2011. Those whose abstracts are a= ccepted will be invited to submit a complete article.<br> 4. Submission of complete articles: January 15th , 2012.<br> 5. Review back to authors: March 1st , 2012.<br> 6. Revised and resubmitted articles submitted for second review: May 1st, 2= 012.<br> 7. Final and complete articles submitted: July 1st, 2012.<br> <br> For all questions and notes concerning the special issue, and for the abstr= act of your proposed article, please send a e-mail to: <br> Thea van der Geest, <a href=3D"mailto:t.m.vandergeest%40utwente.nl">t.m.van= [email protected]</a><br> or the co-editors,<br> Judy Ramey, <a href=3D"mailto:jramey%40uw.edu">[email protected]</a><br> Stephanie Rosenbaum, <a href=3D"mailto:stephanie%40teced.com">stephanie@tec= ed.com</a><br> Lex van Velsen, <a href=3D"mailto:l.s.vanvelsen%40utwente.nl">l.s.vanvelsen= @utwente.nl</a><br> <br> </p> </div> =20=20=20=20=20 <!--~-|**|PrettyHtmlStart|**|-~--> <div style=3D"color: #fff; height: 0;">__._,_.___</div> =20=20=20=20=20=20=20=20 =20=20 =20=20=20 <div id=3D"ygrp-actbar" style=3D"clear: both; margin-bottom: 10px; whit= e-space: nowrap; color: #666; padding-top: 15px;"> <div> <a href=3D"mailto:[email protected]?subject=3DRe%3A%20CFP= %3A%20IEEE%20Special%20Issue%3A%20Designing%20a%20Better%20User%20Experienc= e%20for%20Self-Service" style=3D"margin-right: 0; padding-right: 0;"> Reply to <span style=3D"font-weight: 700;">sender</span></a> | <a href=3D"mailto:[email protected]?subject=3DRe= %3A%20CFP%3A%20IEEE%20Special%20Issue%3A%20Designing%20a%20Better%20User%20= Experience%20for%20Self-Service"> Reply to <span style=3D"font-weight: 700;">group</span></a> | <a href=3D"http://groups.yahoo.com/group/AIGAExperienceDesign/po= st;_ylc=3DX3oDMTJwaHZiM285BF9TAzk3MzU5NzE0BGdycElkAzEwMjAwNTIEZ3Jwc3BJZAMxN= zA2MDIzODUxBG1zZ0lkAzMxNTIEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxMzA5NTQzMDky?act= =3Dreply&messageNum=3D3152">Reply <span style=3D"font-weight: 700;">via web= post</span></a> | <a href=3D"http://groups.yahoo.com/group/AIGAExperienceDesign/= post;_ylc=3DX3oDMTJlN3YxMmYzBF9TAzk3MzU5NzE0BGdycElkAzEwMjAwNTIEZ3Jwc3BJZAM= xNzA2MDIzODUxBHNlYwNmdHIEc2xrA250cGMEc3RpbWUDMTMwOTU0MzA5Mg--" style=3D"fon= t-weight: 700;">Start a New Topic</a> </div> <a href=3D"http://groups.yahoo.com/group/AIGAExperienceDesi= gn/message/3152;_ylc=3DX3oDMTM0Z2hjZjhuBF9TAzk3MzU5NzE0BGdycElkAzEwMjAwNTIE= Z3Jwc3BJZAMxNzA2MDIzODUxBG1zZ0lkAzMxNTIEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxMzA= 5NTQzMDkyBHRwY0lkAzMxNTI-">Messages in this topic</a> (<span style=3D"font-weight: 700;">1</span>) </div>=20 <!------- Start Nav Bar ------> <!-- |**|begin egp html banner|**| --> <div id=3D"ygrp-vital" style=3D"background-color: #e0ecee; font-family: Ver= dana; font-size: 10px; margin-bottom: 10px; padding: 10px;"> <span id=3D"vithd" style=3D"font-weight: bold; color: #333; text-tran= sform: uppercase; ">Recent Activity:</span> <ul style=3D"list-style-type: none; margin: 0; padding: 0; display: inl= ine;"> <li style=3D"border-right: 1px solid #000; font-weight: 700; di= splay: inline; padding: 0 5px; margin-left: 0;"> <span class=3D"cat"><a href=3D"http://groups.yahoo.com/group/AIGAExpe= rienceDesign/members;_ylc=3DX3oDMTJmamZjNWhhBF9TAzk3MzU5NzE0BGdycElkAzEwMjA= wNTIEZ3Jwc3BJZAMxNzA2MDIzODUxBHNlYwN2dGwEc2xrA3ZtYnJzBHN0aW1lAzEzMDk1NDMwOT= I-?o=3D6" style=3D"text-decoration: none;">New Members</a></span> <span class=3D"ct" style=3D"color: #ff7900;">2</span> </li> </ul> =20=20=20=20 <div style=3D"clear: both; padding-top: 2px; color: #1e66ae;"> <a href=3D"http://groups.yahoo.com/group/AIGAExperienceDesign;_ylc=3DX3= oDMTJlMm8xaTh0BF9TAzk3MzU5NzE0BGdycElkAzEwMjAwNTIEZ3Jwc3BJZAMxNzA2MDIzODUxB= HNlYwN2dGwEc2xrA3ZnaHAEc3RpbWUDMTMwOTU0MzA5Mg--" style=3D"text-decoration: = none;">Visit Your Group</a> </div> </div> <div id=3D"ygrp-grfd" style=3D"font-family: Verdana; font-size: 12px;= padding: 15px 0;"> =20=20=20=20=20=20 <!-- |**|begin egp html banner|**| --> - - - - A I G A E X P E R I E N C E D E S I G N - - - -<B= R> <BR> PURPOSE OF THE LIST: The objective of AIGA Experience Design is to bu= ild an interdisciplinary community of professionals who design for a world = in which experiences are increasingly digital and connected. This list has = been established as a forum for the exchange of information among community= members.<BR> <BR> TO VIEW ARCHIVED MESSAGES: visit <a href=3D"http://groups.yahoo.com/group/A= IGAExperienceDesign">http://groups.yahoo.com/group/AIGAExperienceDesign</a>= <BR> <BR> ETIQUETTE: We ask that participants observe common principles of civility a= nd e-mail etiquette in their postings. Specifically, it is more appropriate= to challenge ideas than individuals, and the list should *not* be used for= personal communications, self-promotion, commercial solicitations or job p= ostings.<BR> <BR> JOB POSTINGS: Please post job listings on AIGA Design Jobs <a href=3D"http:= //www.aiga.org/designjobs">http://www.aiga.org/designjobs</a><BR> <BR> TO UNSUBSCRIBE: Send e-mail to AIGEExperienceDesign-unsubscribe@yahoogroups= .com<BR> <BR> MORE INFORMATION: <a href=3D"http://experiencedesign.aiga.org">http://exper= iencedesign.aiga.org</a><BR> =20=20=20=20=20=20 <!-- |**|end egp html banner|**| --> </div> =20=20 <div id=3D"ft" style=3D"font-family: Arial; font-size: 11px; margin-top: 5p= x; padding: 0 2px 0 0; clear: both;"> <a href=3D"http://groups.yahoo.com/;_ylc=3DX3oDMTJkOGRvdXZjBF9TAzk3MzU5Nz= E0BGdycElkAzEwMjAwNTIEZ3Jwc3BJZAMxNzA2MDIzODUxBHNlYwNmdHIEc2xrA2dmcARzdGltZ= QMxMzA5NTQzMDky" style=3D"float: left;"><img src=3D"http://l.yimg.com/a/i/u= s/yg/logo/us.gif" height=3D"15" width=3D"137" alt=3D"Yahoo! Groups" style= =3D"border: 0;"/></a> <div style=3D"color: #747575; float: right;">Switch to: <a href=3D"mailto= :[email protected]?subject=3DChange Delivery= Format: Traditional" style=3D"text-decoration: none;">Text-Only</a>, <a hr= ef=3D"mailto:[email protected]?subject=3DEmail De= livery: Digest" class=3D"margin-rt" style=3D"text-decoration: none;">Daily = Digest</a> • <a href=3D"mailto:AIGAExperienceDesign-unsubscribe@yahoog= roups.com?subject=3DUnsubscribe" style=3D"text-decoration: none;">Unsubscri= be</a> • <a href=3D"http://docs.yahoo.com/info/terms/" style=3D"text-d= ecoration: none;">Terms of Use</a></div> </div> <!-- |**|end egp html banner|**| --> </div> <!-- ygrp-msg --> <!-- Sponsor --> <!-- |**|begin egp html banner|**| --> <div id=3D"ygrp-sponsor" style=3D"width:160px; float:right; clear:none; m= argin:0 0 25px 0; background: #fff;"> <!-- Start Recommendations --> <div id=3D"ygrp-reco"> </div> <!-- End Recommendations --> </div> <!-- |**|end egp html banner|**| --> <div style=3D"clear:both; color: #FFF; font-size:1px;">.</div> </div> <img src=3D"http://geo.yahoo.com/serv?s=3D97359714/grpId=3D1020052/grpspI= d=3D1706023851/msgId=3D3152/stime=3D1309543092/nc1=3D3848644/nc2=3D5898818/= nc3=3D5008817" width=3D"1" height=3D"1"> <br> <div style=3D"color: #fff; height: 0;">__,_._,___</div> <!--~-|**|PrettyHtmlEnd|**|-~--> </body> <!--~-|**|PrettyHtmlStart|**|-~--> <head> <style type=3D"text/css"> <!-- #ygrp-mkp { border: 1px solid #d8d8d8; font-family: Arial; margin: 10px 0; padding: 0 10px; } #ygrp-mkp hr { border: 1px solid #d8d8d8; } #ygrp-mkp #hd { color: #628c2a; font-size: 85%; font-weight: 700; line-height: 122%; margin: 10px 0; } #ygrp-mkp #ads { margin-bottom: 10px; } #ygrp-mkp .ad { padding: 0 0; } #ygrp-mkp .ad p { margin: 0; } #ygrp-mkp .ad a { color: #0000ff; text-decoration: none; } #ygrp-sponsor #ygrp-lc { font-family: Arial; } #ygrp-sponsor #ygrp-lc #hd { margin: 10px 0px; font-weight: 700; font-size: 78%; line-height: 122%; } #ygrp-sponsor #ygrp-lc .ad { margin-bottom: 10px; padding: 0 0; } a { color: #1e66ae; } #actions { font-family: Verdana; font-size: 11px; padding: 10px 0; } #activity { background-color: #e0ecee; float: left; font-family: Verdana; font-size: 10px; padding: 10px; } #activity span { font-weight: 700; } #activity span:first-child { text-transform: uppercase; } #activity span a { color: #5085b6; text-decoration: none; } #activity span span { color: #ff7900; } #activity span .underline { text-decoration: underline; } .attach { clear: both; display: table; font-family: Arial; font-size: 12px; padding: 10px 0; width: 400px; } .attach div a { text-decoration: none; } .attach img { border: none; padding-right: 5px; } .attach label { display: block; margin-bottom: 5px; } .attach label a { text-decoration: none; } =20=20 blockquote { margin: 0 0 0 4px; } .bold { font-family: Arial; font-size: 13px; font-weight: 700; } .bold a { text-decoration: none; } dd.last p a { font-family: Verdana; font-weight: 700; } dd.last p span { margin-right: 10px; font-family: Verdana; font-weight: 700; } dd.last p span.yshortcuts { margin-right: 0; } div.attach-table div div a { text-decoration: none; } div.attach-table { width: 400px; } div.file-title a, div.file-title a:active, div.file-title a:hover, div.fi= le-title a:visited { text-decoration: none; } div.photo-title a, div.photo-title a:active, div.photo-title a:hover, div= .photo-title a:visited { text-decoration: none; } div#ygrp-mlmsg #ygrp-msg p a span.yshortcuts { font-family: Verdana; font-size: 10px; font-weight: normal; } .green { color: #628c2a; } .MsoNormal { margin: 0 0 0 0; } o { font-size: 0; } #photos div { float: left; width: 72px; } #photos div div { border: 1px solid #666666; height: 62px; overflow: hidden; width: 62px; } #photos div label { color: #666666; font-size: 10px; overflow: hidden; text-align: center; white-space: nowrap; width: 64px; } #reco-category { font-size: 77%; } #reco-desc { font-size: 77%; } .replbq { margin: 4px; } #ygrp-actbar div a:first-child { /* border-right: 0px solid #000;*/ margin-right: 2px; padding-right: 5px; } #ygrp-mlmsg { font-size: 13px; font-family: Arial, helvetica,clean, sans-serif; *font-size: small; *font: x-small; } #ygrp-mlmsg table { font-size: inherit; font: 100%; } #ygrp-mlmsg select, input, textarea { font: 99% Arial, Helvetica, clean, sans-serif; } #ygrp-mlmsg pre, code { font:115% monospace; *font-size:100%; } #ygrp-mlmsg * { line-height: 1.22em; } #ygrp-mlmsg #logo { padding-bottom: 10px; } #ygrp-mlmsg a { color: #1E66AE; } #ygrp-msg p a { font-family: Verdana; } #ygrp-msg p#attach-count span { color: #1E66AE; font-weight: 700; } #ygrp-reco #reco-head { color: #ff7900; font-weight: 700; } #ygrp-reco { margin-bottom: 20px; padding: 0px; } #ygrp-sponsor #ov li a { font-size: 130%; text-decoration: none; } #ygrp-sponsor #ov li { font-size: 77%; list-style-type: square; padding: 6px 0; }=20 #ygrp-sponsor #ov ul { margin: 0; padding: 0 0 0 8px; } #ygrp-text { font-family: Georgia; } #ygrp-text p { margin: 0 0 1em 0; } #ygrp-text tt { font-size: 120%; } #ygrp-vital ul li:last-child { border-right: none !important;=20 }=20 --> </style> </head> <!--~-|**|PrettyHtmlEnd|**|-~--> </html> <!-- end group email --> --iaNvh2GAIPQhivWrSA2QOh0SqpHFX8JFVMFOrXP--