
{"id":3599,"date":"2017-08-20T22:40:04","date_gmt":"2017-08-20T22:40:04","guid":{"rendered":"http:\/\/pages.uncc.edu\/aaron-toscano\/?page_id=3599"},"modified":"2017-08-21T22:24:52","modified_gmt":"2017-08-21T22:24:52","slug":"informationdesignprinciples","status":"publish","type":"page","link":"http:\/\/pages.charlotte.edu\/aaron-toscano\/engl4182-5182fall2017\/engl4182-5182august21\/informationdesignprinciples\/","title":{"rendered":"Rhetorical Principles of Information Design"},"content":{"rendered":"<p>Most of this class is inspired by Kimball and Hawkins now out-of-print <em>Document Design<\/em> book. Unless otherwise noted, the page citations are from textbook<\/p>\n<hr \/>\n<h1><del><\/del>Introducing Information Design<\/h1>\n<p>Document design is part of a larger field called <strong><a href=\"http:\/\/en.wikipedia.org\/wiki\/Information_design\">Information Design (ID)<\/a><\/strong>. Saul Carliner&#8217;s definition of ID works on three levels:<\/p>\n<ol>\n<li>Physical&#8211;providing meaningful visual design<br \/>\n&#8220;From the users\u2019 perspective, good physical design lets them find information of interest easily&#8221; (564)<\/li>\n<li>Cognitive&#8211;understand information through design choices<br \/>\n&#8220;Cognitive design primarily focuses on the design process: adequately defining the users\u2019 performance goals and preparing a solution that addresses them&#8221; (566)<\/li>\n<li>Affective&#8211;motivate users to act<br \/>\n&#8220;Before users can perform the tasks describe[d] in communication products, they need to feel compelled to read about them&#8230;.After attracting readers\u2019 attention, technical communicators must motivate readers to use information in the communication product&#8221; (568).<\/li>\n<\/ol>\n<p>Additionally, Kimball &amp; Hawkins claim &#8220;Document designers work to understand the problems and situations of information users and information providers and then craft documents that help solve those problems within those situations&#8221; (p. 3). Although it might seem outdated to discuss &#8220;documents&#8221; as opposed to sites of content, &#8220;documents are best understood as a site where one person can\u00a0mark information for the use of another&#8221; (p. 5). Basically, effective design stems from understanding <strong>audiences<\/strong> and <strong>purposes<\/strong> for a potential document. You might have had discussions about audience and purpose in other classes, and you should have because they are the key elements to consider when communicating: The best communication in the world will fail if the author doesn&#8217;t understand his or her audience and doesn&#8217;t have a clear sense of the purpose of the communication.<\/p>\n<p>Below are the groups that make up the document design relationship:<\/p>\n<ul>\n<li>Clients (needs and agendas)<\/li>\n<li>Users (needs and\u00a0desires)<\/li>\n<li>Designers (solve the problem for both)<\/li>\n<\/ul>\n<p>An effective designer is aware of his or her clients&#8217; and audiences&#8217; needs and, more importantly, expectations. Being culturally aware helps uncover a broad range of user expectations. Remember, users are members of cultures who understand meanings that are constructed by their experiences and lives in a particular society.<\/p>\n<p>Finally, let&#8217;s get to rhetoric, which is a subject we&#8217;ll analyze throughout the semester. There are three extremely important appeals to consider:<\/p>\n<ul>\n<li>Ethos:<br \/>\n1) the presentation of or appeal to one&#8217;s character<br \/>\n2) the characterization of a document or speaker (consider this to be the &#8220;look and feel&#8221; of a document, its attributes)<br \/>\nNotice the two parts of this definition&#8230;be able to analyze a document from both parts separately. <strong>I will explain what this means every class period until the semester is over.<\/strong><\/li>\n<li>Pathos: appeal to emotions<\/li>\n<li>Logos:<br \/>\n1) appeal to logic; explicit or implicit deductive arguments<br \/>\n2)\u00a0stating assumed facts (e.g., statistics, addresses, date\/time)<\/li>\n<\/ul>\n<p>Consider the &#8220;look and feel&#8221; of the following Web pages:<\/p>\n<ul>\n<li><strong><a href=\"http:\/\/www.facets.org\/academy\/filmcamp\/\">FACETS Multimedia<\/a><\/strong><\/li>\n<li><strong><a href=\"http:\/\/www.charlottesgotalot.com\/family-friendly-attractions-listings\">Family Friendly Charlotte<\/a><\/strong><\/li>\n<\/ul>\n<p>We will come back to ethos, pathos, and logos throughout the semester. Please, please, please ask questions if the terms are confusing. If we have time tonight, though, we&#8217;re going to go over assumptions based on experience, bias, conventional wisdom, etc. Time permitting, we&#8217;ll discuss a group of designs for pizza&#8230;<\/p>\n<ul>\n<li><strong><a href=\"https:\/\/www.toppers.com\/\">Toppers Pizza<\/a><\/strong><\/li>\n<li><strong><a href=\"http:\/\/giacomospizzeria.com\/\">Giacomo&#8217;s Pizzeria<\/a><\/strong><\/li>\n<li><strong><a href=\"http:\/\/tonysbigpizza.com\/\">Tony&#8217;s Pizza<\/a><\/strong><\/li>\n<li><strong><a href=\"http:\/\/www.farleyspizzeria.com\/\">Farley&#8217;s Pizzeria<\/a><\/strong><\/li>\n<li><strong><a href=\"http:\/\/www.iniziopizza.com\/\">Inizio Pizza Napoletana<\/a><\/strong><\/li>\n<\/ul>\n<p><strong><a href=\"http:\/\/hawthornespizza.com\/\">Hawthorne&#8217;s Pizza<\/a><\/strong> can be said to have a &#8220;contemporary&#8221; design. What other page does it look like? You probably visit this page a lot! Here&#8217;s another Italian-style restaurant, <strong><a href=\"http:\/\/www.mamaricottas.com\/\">Mamma Ricotta&#8217;s<\/a><\/strong>.<\/p>\n<h2>Principles of Design<\/h2>\n<p>Kimball &amp; Hawkins (and Robin Williams) discuss principles of design. As a preview, I&#8217;ve listed some important terms we&#8217;ll return to throughout the semester:<\/p>\n<ul>\n<li>Design Objects&#8211;text is visual<\/li>\n<li>Seven\u00a0Visual Variables (pp. 23-27)\n<ul>\n<li>Shape: two dimensional area covered<\/li>\n<li>Orientation: the directions in which the design points users<\/li>\n<li>Texture: pattern applied to objects<\/li>\n<li>Color: [<strong><span style=\"color: red\">not<\/span> <span style=\"color: yellow\">much<\/span> <span style=\"color: blue\">more<\/span> <span style=\"color: orange\">to<\/span> <span style=\"color: green\">say<\/span><\/strong>]<\/li>\n<li>Value: relative lightness and darkness of an object compared to its surroundings (important when we discuss <em>contrast<\/em>)<\/li>\n<li>Size: bigness or smallness of objects<\/li>\n<li>Position: location on a two dimensional plane<\/li>\n<\/ul>\n<\/li>\n<li>Six Principles of Design (pp. 27-35)\n<ul>\n<li>Similarity: how alike objects are<\/li>\n<li>Contrast: emphasis; calling attention to<\/li>\n<li>Proximity: grouping and belonging (not direction per se as in <em>orientation<\/em>)<\/li>\n<li>Alignment: showing connection and coherence<\/li>\n<li>Order: users have socially constructed expectations for sequences in documents based on their experiences in a culture<\/li>\n<li>Enclosure: boxes or such for containing or separating objects<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>We will return to the above concepts throughout the semester, so please make sure you&#8217;re using the appropriate vocabulary because these terms capture design principles and help us quickly and (one hopes) accurately assess your document&#8217;s effectiveness.<\/p>\n<hr \/>\n<p>Works Cited<\/p>\n<p>Carliner, Saul. &#8220;A Three-part Framework for Information Design.&#8221; <em>Technical Communication<\/em>, vol. 47, no. 4, 2000, pp. 561-576.<\/p>\n<p>Kimball, Miles and Anne Hawkins. <em>Document Design<\/em>. Bedford, 2008.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most of this class is inspired by Kimball and Hawkins now out-of-print Document Design book. Unless otherwise noted, the page citations are from textbook Introducing Information Design Document design is part of a larger field called Information Design (ID). Saul Carliner&#8217;s definition of ID works on three levels: Physical&#8211;providing meaningful visual design &#8220;From the users\u2019 [&hellip;]<\/p>\n","protected":false},"author":598,"featured_media":0,"parent":3593,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"class_list":["post-3599","page","type-page","status-publish","hentry"],"jetpack_shortlink":"https:\/\/wp.me\/P2HAOx-W3","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3599","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/users\/598"}],"replies":[{"embeddable":true,"href":"http:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/comments?post=3599"}],"version-history":[{"count":8,"href":"http:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3599\/revisions"}],"predecessor-version":[{"id":3646,"href":"http:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3599\/revisions\/3646"}],"up":[{"embeddable":true,"href":"http:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/pages\/3593"}],"wp:attachment":[{"href":"http:\/\/pages.charlotte.edu\/aaron-toscano\/wp-json\/wp\/v2\/media?parent=3599"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}