<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-5037683482221783083</id><updated>2011-08-03T00:39:03.623-04:00</updated><title type='text'>information design</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>16</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-402411423289273022</id><published>2011-03-19T16:30:00.000-04:00</published><updated>2011-03-19T16:30:16.011-04:00</updated><title type='text'>Creating a delightful customer experience with effective customer communications management.</title><content type='html'>When was the last time you had a “delightful customer experience”? Chances are good that a big part of your experience was created by a special “someone” who contributed that little something extra, without which, there wouldn’t have been a wonderful experience worth remembering. In today’s world of customer communications, the challenge is figuring out how to add that special “something” extra into the processes, designs, and technologies used to deliver relevant, impactful communications that delight the customer. &lt;br /&gt;Fundamentally, the entire customer communications management process can be separated into two buckets. The technologies and the people. Or, said another way, the tools and the expertise; the bow and the archer, the kitchen and the cook, etc. Few of us would argue that Julia Childs easily created delightful customer experiences using some basic tools any of us could also pick up at a local grocer…a chicken, some herbs, and butter (and more butter). It was Julia’s expertise that made her meals quite different than anything you or I could possibly create.&lt;br /&gt;&lt;br /&gt;Simply put expertise matters. And that’s wonderful news to anyone willing to invest their time and energy into building customer communications management skills that can help create more delightful customer communications experiences. One critical aspect of effective customer communications management that’s often overlooked is Information Design, which simply means making information easier for the intended audience to both understand and act upon. &lt;br /&gt;Check out an article I wrote for the Insurance and Technology Magazine at:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.insurancetech.com/blogs/229300488"&gt;http://www.insurancetech.com/blogs/229300488&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-402411423289273022?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='related' href='http://www.insurancetech.com/blogs/229300488' title='Creating a delightful customer experience with effective customer communications management.'/><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/402411423289273022/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2011/03/creating-delightful-customer-experience.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/402411423289273022'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/402411423289273022'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2011/03/creating-delightful-customer-experience.html' title='Creating a delightful customer experience with effective customer communications management.'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-8264627889386560187</id><published>2011-01-28T17:22:00.000-05:00</published><updated>2011-01-28T17:22:45.620-05:00</updated><title type='text'>ID Doc's comment on Plain English is greek to some</title><content type='html'>&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;This article brings to light some of the problems and challenges with the understandability of financial documents. The new requirements while a good start as&lt;span style="mso-spacerun: yes;"&gt;&amp;nbsp; &lt;/span&gt;plain language experts, Annetta Cheek and Joe Kimble have said, I would like to expand upon one area that Joe touched on. As an information design and clear communications expert, I employ plain language in all of my work (mostly financial statements and forms) but I need to stress the importance of other aspects of clear communications such as readable fonts, points sizes large enough, but not to large, for comfortable reading, proper use of white space within the document and a clear hierarchy of information. For example, text written in all capital letters has been proven to be hard to read and slows down the process of getting through a document. While underlining seems to be a way of emphasis, it dates back to typewriters when it was the main way stress important information. In today's world we can use other techniques like larger point sizes and bolding for emphasis. Besides, in today's world, underlining often means a link to another page in the internet. Another issue is the audience. For most documents, there are multiple audiences. The document should be able to comfortably address all audiences. &lt;/div&gt;&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;a href="http://www.investmentnews.com/article/20110123/REG/301239983"&gt;http://www.investmentnews.com/article/20110123/REG/301239983&lt;/a&gt;&lt;/div&gt;&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-8264627889386560187?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/8264627889386560187/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2011/01/id-docs-comment-on-plain-english-is.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/8264627889386560187'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/8264627889386560187'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2011/01/id-docs-comment-on-plain-english-is.html' title='ID Doc&apos;s comment on Plain English is greek to some'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-7138016827201385356</id><published>2010-10-20T13:40:00.001-04:00</published><updated>2010-10-21T11:27:52.122-04:00</updated><title type='text'>clarity 2010</title><content type='html'>I&amp;nbsp;just returned from the CLARITY 2010 conference in Lisbon, Portugal. It was an excellent conference with attendees and speakers from all over the world, USA, UK, South Africa, Australia, Hong Kong, to name just a few. CLARITY promotes plain legal language. I spoke on the topic "beyond plain language." As most of you know, I believe that plain language is only part of clear communications and sometimes not a very important part. My talk centered around plain language, graphic design, psychology and usability, focusing on the last three. I wanted to point out that plain language does not necessarily solve the problem of clear communications and that is, after all, what we are all trying to achieve.&lt;br /&gt;&lt;br /&gt;I&amp;nbsp;used examples showing use of white space, fonts, usability testing, etc. The presentation seemed to be well received and i got positive feedback after it. For me,&amp;nbsp;I achieved a few things:&amp;nbsp;First,&amp;nbsp;I got in front of an audience that had an idea of what I&amp;nbsp;was talking about but also was willing to listen and learn. Second, I met many old friends and made new friends. It was especially gratifying to put faces to names of people I have corresponded with through emails and lists. As a fellow of the Communications Research Institute, I was joined by Karen Schriver and Karel van der Waarde. Karel and I had never met, but we spent some talking and it was most enjoyable. Other conversations were just as exciting and rewarding. &lt;br /&gt;&lt;br /&gt;Most of the sessions were very worthwhile, but the days were long. My only regret was I couldn't attend all sessions and there was almost no time for questions and discussions. Having attended numerous conferences, I understand the problems with time and logistics and, unfortunately, I don't have any quick solutions.&lt;br /&gt;&lt;br /&gt;The fact that&amp;nbsp;I was able to meet people from all over the world, doing similar work was most rewarding. Let me not forget to mention that Lisbon is a very interesting and exciting city and Portugal is a wonderful country. That just added to the overall success of the conference.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-7138016827201385356?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/7138016827201385356/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2010/10/clarity-2010.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/7138016827201385356'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/7138016827201385356'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2010/10/clarity-2010.html' title='clarity 2010'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-6185763393014936168</id><published>2010-09-20T19:49:00.000-04:00</published><updated>2010-09-20T19:49:24.366-04:00</updated><title type='text'>CLARITY 2010 CONFERENCE</title><content type='html'>The&amp;nbsp;Information Design Doc has been invited to share his knowledge and expertise at the CLARITY 2010 conference in Lisbon, Portugal, October 14-15, 2010. His presentation is entitled:&lt;br /&gt;&lt;strong&gt;“CLARITY...beyond plain language. Or you can't have one without the others”&lt;/strong&gt; &lt;br /&gt;Clarity is an association of lawyers, judges and lay people dedicated to researching and promoting the use of plain legal language. Clarity2010, its fourth international conference, will focus on multidisciplinary ways of achieving clarity in legal, administrative and corporate communications.&lt;br /&gt;&lt;br /&gt;i hope to see you there!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-6185763393014936168?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/6185763393014936168/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2010/09/clarity-2010-conference.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/6185763393014936168'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/6185763393014936168'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2010/09/clarity-2010-conference.html' title='CLARITY 2010 CONFERENCE'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-3603200092627745602</id><published>2010-05-14T11:33:00.001-04:00</published><updated>2010-05-14T11:35:32.481-04:00</updated><title type='text'>what makes a good document design?</title><content type='html'>Xplor International is doing one of their Lunch and Learn Webinars next Thursday, may 20, &amp;nbsp;from 1-2 eastern time. The title is “what makes a good document design?” I will be one of the panelists on the webinar. If you would like to join, it is free, either click on this link &lt;a href="https://www2.gotomeeting.com/register/983290786"&gt;https://www2.gotomeeting.com/register/983290786&lt;/a&gt; or go to www.Xplor.org and click on the “lunch and learn webinar” title, then the what makes a&amp;nbsp;good document design title&amp;nbsp;and there will be registration form.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-3603200092627745602?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/3603200092627745602/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2010/05/what-makes-good-document-design.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/3603200092627745602'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/3603200092627745602'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2010/05/what-makes-good-document-design.html' title='what makes a good document design?'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-5749818540531984200</id><published>2010-04-07T09:39:00.002-04:00</published><updated>2010-04-07T09:41:21.093-04:00</updated><title type='text'>step two</title><content type='html'>A while ago I talked about step one in the process of the redesign of a document. Just to remind you, step one consists of creating a project team and establishing goals. I also talked about the main purpose of the document, that is, what do you want this document to do? Is it an invoice and so needs to get paid? Is it a statement and needs to explain the different components of an account (bank, brokerage retirement, etc.)? Is it an application that needs to be filled out and return for processing (and then processed)? &lt;br /&gt;&lt;br /&gt;Whatever the main purpose is, that should be the ultimate goal and what all discussions are focused on. I often see discussions straying from this and leading down other paths that wind up in confusion, lack of purpose and an unsuccessful document.&lt;br /&gt;&lt;br /&gt;Fortunately or unfortunately, the members of any good project team represent all areas of an organization and their input is sound and valuable, but the group needs to come together and work as a team.&lt;br /&gt;Step two is the gathering information stage. This step has different parts to it. First, information needs to be gathered about the production of the document – is it produced on line? Or hardcopy, fill-in, system generated, etc? What are the constraints – color, bar codes, mailing, etc?&lt;br /&gt;&lt;br /&gt;Then ALL users need to be interviewed. These include not only end users, but all who touch the document through the course of its existence. Most often internal users are not consulted and they often will have information no one else has that may be critical to the document.&lt;br /&gt;&lt;br /&gt;Many years ago, I talked to a client who told me they had many lock box addresses and someone within the organization decided to eliminate all but one. Then we did our information gathering and found out there were real and necessary reasons for the multiple ones and that having just one would strangle the organization.&lt;br /&gt;&lt;br /&gt;As you go through the gathering information stage, remember the four most important questions to ask:&lt;br /&gt;&lt;br /&gt;What is the document’s real purpose?&lt;br /&gt;What other documents must it work with?&lt;br /&gt;Who are the internal and external users?&lt;br /&gt;What are their needs?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-5749818540531984200?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/5749818540531984200/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2010/04/step-two.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/5749818540531984200'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/5749818540531984200'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2010/04/step-two.html' title='step two'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-319731828310512981</id><published>2010-02-24T14:35:00.002-05:00</published><updated>2010-02-24T14:39:36.807-05:00</updated><title type='text'>center for plain language awards</title><content type='html'>It has been a while since I have written anything on my blog. I apologize for that and plan on being more diligent in the future. &lt;br /&gt;Right now I would like to urge you to submit examples of good and bad plain language or information design to the first annual competition sponsored by the Center for Plain Language (CPL). CPL is a non-profit organization located in Washington, DC. They want government and business documents to be clear and understandable. This competition is to see how far documents have come and to view the long road ahead. &lt;br /&gt;The competition is in two parts: ClearMark for those that are the best examples in a variety of categories; print, on line and web in the private, public and non profit sectors in both original and revised documents. The worst examples are vying in for the WonderMark award in two categories – private and public.&lt;br /&gt;The bad news is the &lt;strong&gt;deadline is March 1, 2010&lt;/strong&gt;, but the good news is I am a judge and will not be entering anything. That greatly increases your chances to win.&lt;br /&gt;Go to &lt;strong&gt;&lt;a href="http://www.centerforplainlanguage.org/"&gt;http://www.centerforplainlanguage.org/&lt;/a&gt;&lt;/strong&gt; for more information and entry forms.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-319731828310512981?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/319731828310512981/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2010/02/center-for-plasin-language-awards.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/319731828310512981'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/319731828310512981'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2010/02/center-for-plasin-language-awards.html' title='center for plain language awards'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-1179024999704783629</id><published>2009-11-04T14:12:00.001-05:00</published><updated>2009-11-04T14:13:28.296-05:00</updated><title type='text'>response to comment by Rob Waller</title><content type='html'>Rob suggests that bills (and other documents) are read in stages and that the focus changes as they are read and as decisions are made (See his comment below). While I agree with his point, the issue I was addressing has to do with the main purpose (in this case payment of a bill) and how it has been diluted by companies that feel they need to add additional content.  My example shows 4 messages that come under the heading of “important”, but they are not as important as paying the bill. The bill detail should be the priority, not the messages. While it may be desirable to add these messages as well as other types of content, keep in mind that payment is the first priority.&lt;br /&gt;&lt;br /&gt;Rob’s other comment is in regards to “transpromo” or as Rob says used to be called “relationship communications” or I say used to be called “cross sell.” This is all the same and it is all some form of marketing. Transpromo is utilizing documents to sell other products and services. Often, companies think they need to fill up any “white space” with marketing promotions and messages. While I agree that transactional documents (invoices, bills, statements, etc) are perfect opportunities to market, I believe that companies sometimes go too far and the main purpose of the document becomes diluted.&lt;br /&gt;&lt;br /&gt;As an aside “white space” is an important tool in usability. It helps define areas within a document and helps to identify and highlight important information. If this space is used to add marketing messages, ads, etc., then important information becomes harder to find, read and act upon.&lt;br /&gt; The use of transpromo (the current buzz word) in transactional documents needs to be done judicially. If companies go overboard, then customers will stop reading the messages, stop reading the personal information and may, even stop doing business with the company.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-1179024999704783629?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/1179024999704783629/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/11/response-to-comment-by-rob-waller.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/1179024999704783629'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/1179024999704783629'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/11/response-to-comment-by-rob-waller.html' title='response to comment by Rob Waller'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-4175241535840793291</id><published>2009-10-31T23:04:00.002-04:00</published><updated>2009-10-31T23:05:39.989-04:00</updated><title type='text'>the purpose of the document</title><content type='html'>&lt;a href="http://1.bp.blogspot.com/_rXQaiWNSELc/Suz63ufQUMI/AAAAAAAAADw/8CqXeyLexLI/s1600-h/lease+pages.jpg"&gt;&lt;img style="MARGIN: 0px 10px 10px 0px; WIDTH: 178px; FLOAT: left; HEIGHT: 200px; CURSOR: hand" id="BLOGGER_PHOTO_ID_5398965888589254850" border="0" alt="" src="http://1.bp.blogspot.com/_rXQaiWNSELc/Suz63ufQUMI/AAAAAAAAADw/8CqXeyLexLI/s200/lease+pages.jpg" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;div&gt;Last time, I gave some suggestions about starting a redesign project. But I ended with the statement that you MUST determine the main purpose of the document first.&lt;br /&gt;&lt;br /&gt;Most of the variable data documents I work with are perfect vehicles for marketing or cross selling or transpromo and no whatever you want to call it, they are all the same.&lt;br /&gt;&lt;br /&gt;But bear in mind that each of these documents have one and only one main purpose. All other uses are secondary and should be treated as such.&lt;br /&gt;&lt;br /&gt;So we agree, don’t we? There is only one main purpose. Let’s say it is an invoice and the company needs to get paid as soon as possible. The example I have included is my own lease invoice (shown above). This invoice (the company shall remain anonymous) has a detail section that consists of one line with the principal, interest and total (top of page 2). This is all the detail information I need to pay the invoice. In fact, this whole bill including my mailing address, return address, due date, etc. would actually take up only about ½ of a page. So it is safe to assume that one side of one sheet of paper is enough to do the job. Yet, there were months when four, yes I said 4, messages (listed as “important”) were included and preceded the detail information. This pushed the detail section to a second sheet of paper. Towards the end of the lease, the detail began appearing on the back of the first sheet, so only one piece of paper was used.&lt;br /&gt;&lt;br /&gt;These four messages included: pay on line, pay by phone, in case of accident and remittance. All of these messages are important to a certain degree, but all are secondary to the payment of the invoice. These messages should have appeared after the detail and only those that could fit on one page should appear and in some kind of hierarchical order. Not every message is “important.” Generally speaking only one message is important, while others are “nice to haves.”&lt;br /&gt;&lt;br /&gt;The simple answer to why this happened, I would guess marketing may have been involved, no one took the time to determine the purpose of the document, the user and the cost of adding pages, either the back of the first page or the second sheet.&lt;br /&gt;&lt;br /&gt;I didn’t even talk about how often and how many of these messages get read. So, determining the main purpose and sticking to it, is critical.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-4175241535840793291?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/4175241535840793291/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/10/purpose-of-document_31.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/4175241535840793291'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/4175241535840793291'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/10/purpose-of-document_31.html' title='the purpose of the document'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_rXQaiWNSELc/Suz63ufQUMI/AAAAAAAAADw/8CqXeyLexLI/s72-c/lease+pages.jpg' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-1154835032177668887</id><published>2009-10-06T09:45:00.000-04:00</published><updated>2009-10-06T09:47:13.611-04:00</updated><title type='text'>step one</title><content type='html'>There are many steps to a successful information document redesign. Keep in mind, the number of steps and the amount of time and detail required will vary depending on the complexity of the document or if there are multiple documents. First, let me say that when looking at an organization total forms and documents, it is always best to start small and build on successful redesign projects. Otherwise, the project may bog down and fail. Often times, we will start with one document or with one area of an organization and the documents that might be valuable within that area.&lt;br /&gt;&lt;br /&gt;The first step in any redesign project is to create a project team and establish goals.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;PROJECT TEAM&lt;/strong&gt; - The project team should consist of key players within the organization. Often we have a large group, but a small subset is the day to day working team. The large group, however, needs to include a representative of the key departments that touch the document. This usually will include marketing, IT, legal, regulatory, customer service and more depending on the document. The members need to be people who can make a decision or at the very least, get to a decision maker within their department easily. This ensures two things, the project will keep moving and all departments will have a say and buy in to the decisions.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;ESTABLISH GOALS&lt;/strong&gt; – this is critical since to make the project a success, there needs to be a starting point from which to compare the results. Sometimes I found that this is difficult since most customer service groups don’t have hard facts about the problems with a document. But, there are other possible measurements; production savings, mailing and printing costs, error reductions and service time. All of these are important measurements and will help to determine the success of a project.&lt;br /&gt;&lt;br /&gt;And, of course, determine the &lt;strong&gt;main purpose&lt;/strong&gt; of the document.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-1154835032177668887?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/1154835032177668887/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/10/step-one.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/1154835032177668887'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/1154835032177668887'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/10/step-one.html' title='step one'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-7901203991268240901</id><published>2009-09-11T10:26:00.002-04:00</published><updated>2009-09-11T10:30:58.745-04:00</updated><title type='text'>a new definition for you</title><content type='html'>Here’s a new definition for you to ponder.&lt;br /&gt;&lt;br /&gt;Information Design is not only the appropriate use of plain language, color, typography, the organization and logical grouping of content and the effective management of white space, &lt;strong&gt;BUT a clear and comprehensive understanding of the audiences for which the communications is intended.&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;Writers write, designers design, programmers program, testers test, etc, but who combines it all? I say I do as an Information Designer.&lt;br /&gt;&lt;br /&gt;Although I’m still not sure what to call this thing I do, I think the definition is more concise, usable and understandable. In my mind it encompasses it all; graphic design, plain language, implementation, user testing, etc.&lt;br /&gt;&lt;br /&gt;If any step in the process is left out, how do we know the document is successful?&lt;br /&gt;&lt;br /&gt;In a recent post, Ginny Redish, made a very interesting observation about different types of materials when she referred to research done in the 70s and 80s. She said that they were put into two categories – “reading to learn” and “reading to do.” She goes on to say the “reading to learn” are textbooks whereas “reading to do” are documents in the workplace and in our functioning in every day life. They are used as reference documents and are skimmed and scanned to appreciate the types of information in them and then are returned to check specific information as the need arises.&lt;br /&gt;&lt;br /&gt;Our lives are full of these “reading to do” documents. Unfortunately, most are confusing.&lt;br /&gt;&lt;br /&gt;Most companies and organizations don’t want to spend the time and money to do testing of their critical documents. The reasons vary from cost to we know what is right. This is all well and good, but in reality it is the users who need to find information and act on it. And that brings up another point – users.&lt;br /&gt;&lt;br /&gt; The definition of users is ALL of the people that touch or interact with a document, NOT just the outside customer. Take for instance, an invoice, yes, the customer must receive, review and pay it, but customer service people need to use it when answering inquiries, the payment coupon needs to be handled and read by someone within the organization who receives it and then acts upon it.&lt;br /&gt;&lt;br /&gt;good information design encompasses many disciplines.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-7901203991268240901?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/7901203991268240901/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/09/new-definition-for-you.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/7901203991268240901'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/7901203991268240901'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/09/new-definition-for-you.html' title='a new definition for you'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-4123150688951216167</id><published>2009-08-13T13:23:00.002-04:00</published><updated>2009-08-13T13:25:37.840-04:00</updated><title type='text'>poor information design CAN hurt companies</title><content type='html'>I’m back from my vacation to Colorado.&lt;br /&gt;&lt;br /&gt;One of my biggest concerns, I’ve touched on this previously, is the lack of understanding within an organization of the negative reaction to poor information design.&lt;br /&gt;&lt;br /&gt;A survey of people filling out forms was done a few years ago by the American Institutes for Research (AIR). They found out that when people had trouble with the form, didn’t understand it or found it too difficult, not only did they stop filling out the form, but 58% of the people stopped using the products or services of the company that generated the form.&lt;br /&gt;&lt;br /&gt;This survey shows that organizations don’t understand the power of good information design. They lose customers and business without even realizing it! Most people understand the easiest and cheapest way to increase business is through existing clients. Companies don’t think about the impact of their every day, business documents (reports, bills, statements, even form letters, etc.) on their customers. But as the AIR survey shows, many people walk away to a competitor.&lt;br /&gt;&lt;br /&gt;Companies generate invoices simply because they have to in order to stay in business, i.e., they send them out to get paid. But what happens when they are received. People will review them and if they are easy to understand (what am I being charged for? Is the amount correct?), then they will be paid in the normal course of events. That is assuming the due date and remittance address, etc. are easy to find.&lt;br /&gt;&lt;br /&gt;But what happens if the invoice is not understood? Or perhaps seems to be wrong? Think of a credit card bill where the purchase description is not what you thought you bought. Many times the name is a different company. First off, you are not happy, next you might contact the company – think customer service time here (a real cost to the company) and your time talking with someone. Depending on the call, the question might not be answered necessitating further contact and customer service time. While waiting, you put the invoice aside and pay others. This costs the company money since they will wait for payment. And the bottom line for the customer is – this is not a pleasant experience – will they take their business elsewhere?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-4123150688951216167?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/4123150688951216167/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/08/poor-information-design-can-hurt.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/4123150688951216167'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/4123150688951216167'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/08/poor-information-design-can-hurt.html' title='poor information design CAN hurt companies'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-3378344334971705776</id><published>2009-07-19T17:02:00.001-04:00</published><updated>2009-07-19T17:04:52.062-04:00</updated><title type='text'>usability testing</title><content type='html'>So, here I am again, with another post and hoping for some responses.&lt;br /&gt;&lt;br /&gt;One of the biggest areas of concern is usability testing. When I talk to clients and potential clients, I am often told that it is not necessary. The reasons are many from budget TO our sales force knows what the clients are looking for TO customer service will tell us and more. Unfortunately, this information is generally not complete nor accurate. This is because either people are making assumptions or the wrong questions are being asked.&lt;br /&gt;&lt;br /&gt;The reality is that unless testing is done (and retesting) you really don’t know how people perceive and use information. And then there is the type of testing – do you use focus groups, one-on-ones, etc. For statements, we use one-on-ones because statements are very personal and are generally used by individuals. This gives us a more realistic situation and allows us to ask pointed questions about the information contained in the document.&lt;br /&gt;&lt;br /&gt;To this day, I am still surprised by the some of answers we get!&lt;br /&gt;&lt;br /&gt;One time I did testing on an auto insurance policy. First we tested the existing policy package which contained about 30 individual pages and asked people to open and review the materials. One individual removed the pages and organized then in neat piles by category. I thought to myself – this person actually reads this stuff! When we started asking specific questions it turned out he had no clue what we were asking and where to find the information.&lt;br /&gt;&lt;br /&gt;I take a lead from David Sless of Communications Research Institute (CRI) and talk testing, testing, and testing. Although this is very important part of information design, most clients don’t understand its value or how to conduct the testing to ensure the greatest value. I have found the statement usability testing is treated much like marketing testing. That is, people are asked which one they “like” and other subjective questions that don’t get to the root of understanding the document and the information contained in it.&lt;br /&gt;&lt;br /&gt;If more companies tested their documents, they would be more successful and errors would be reduced, time would be saved internally, money would be saved in production and the customer base would have a more positive view of the organization.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-3378344334971705776?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/3378344334971705776/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/07/usability-testing.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/3378344334971705776'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/3378344334971705776'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/07/usability-testing.html' title='usability testing'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-5896058791235571966</id><published>2009-07-01T08:55:00.001-04:00</published><updated>2009-07-01T09:13:55.996-04:00</updated><title type='text'>What I do.</title><content type='html'>&lt;div&gt;&lt;br /&gt;Well, in order to facilitate this blog/discussion, I think is important to let everyone know what I do and how I see myself fitting into this broad arena of information design.&lt;br /&gt;&lt;br /&gt;My area of expertise lies mostly in the financial, insurance and healthcare industries. My focus is on paper documents, such as statements (brokerage, retirement, bank, etc), forms (enrollment, application, etc) and bills/invoices (utility, credit card, telecom, etc.).&lt;br /&gt;The hardest part for me is explaining to people, whether it is clients, potential clients, friends or even my mother, what it is I do.&lt;br /&gt;&lt;br /&gt;I try to encompass what I consider all aspects of good information design in the documents I work on, usability testing, plain language, graphic design, understanding of all the users, etc. But, more about that in future posts.&lt;br /&gt;&lt;br /&gt;People should be able to find information easily and quickly and be able to understand it so that they can act upon it in the way that the company would like them to. If it is a bill, it needs to be paid, if it is a retirement statement – how much do I have, etc.&lt;br /&gt;&lt;br /&gt;A lot of statement work comes from the marketing departments and they generally don’t understand the purpose of the document – in fact I think companies see documents as a necessary evil and are viewed as “we have to send an invoice” or “we are required by law” type of documents. No thought is given to the importance and the potential ramifications, both positive and negative, of these documents. It is interesting that companies spend thousands, hundreds of thousands, even millions of dollars producing slick full color brochures, ads, and other marketing materials to get new business whereas any good salesman (or woman) knows that the quickest, easiest, cheapest way to generate new business is through existing customers.&lt;br /&gt;&lt;br /&gt;Statements, invoices and other documents are sent to existing clients on a regular basis (monthly, yearly, etc) with personal information that WILL get read and they present an excellent opportunity to generate new business.&lt;br /&gt;&lt;br /&gt;BUT, it must be done with care and the first step is to keep the existing customer happy. &lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-5896058791235571966?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/5896058791235571966/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/07/what-i-do.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/5896058791235571966'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/5896058791235571966'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/07/what-i-do.html' title='What I do.'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-1461715634468524918</id><published>2009-06-25T10:04:00.001-04:00</published><updated>2009-06-25T15:10:08.956-04:00</updated><title type='text'>information design - definitions?</title><content type='html'>Well, here I am again. I will try every few days to keep adding my thoughts to this blog and hope that you will react and add yours too.&lt;br /&gt;&lt;br /&gt;I have enough topics to last for a while and you will see random thoughts but they will all be centered on this thing I call “information design.”&lt;br /&gt;&lt;br /&gt;I hate to get into a discussion about the definition since all of us have our own. But maybe that is one of the problems. If you go to any of the websites: PLAIN. CPL, IIID, CRI, IDA, Wikipedia, etc. you will find different definitions. If you talk to information/graphic designers, writers/plain language experts, usability experts, user experience experts, etc., you will find different definitions, but we are all dealing with similar issues and are looking for the same end.&lt;br /&gt;&lt;br /&gt;I’ll put my definition out there, but be forewarned, it is long and wordy. I have been struggling with this for many years. The reason for its wordiness is twofold, one – I am trying to incorporate many aspects and two – &lt;strong&gt;I’m not a writer!&lt;br /&gt;&lt;/strong&gt;&lt;br /&gt;“Information design is the result of a clear and comprehensive understanding of the businesses and audiences for which the communications is intended. And the appropriate use of plain language, the organization and logical grouping of information, the appropriate use of color and typography, and the effective management of white space.”&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;I warned you it was wordy!&lt;br /&gt;&lt;/strong&gt;&lt;br /&gt;Here’s another way:&lt;br /&gt;&lt;br /&gt;“Information design is communicating effectively by providing the right information to the right person at the right time in a tried and tested way that it is easily understood.”&lt;br /&gt;&lt;br /&gt;Again, I’m not sure it is the best. When it comes down to it, we, as communicators, need to be able to explain it, simply, clearly, understandably. When I was strictly a “graphic” designer, I used to open presentations by saying that it took my mother 10 years to understand what I do! Now, it is almost impossible!&lt;br /&gt;&lt;br /&gt;I don’t want to get stuck on definitions, although at sometime we need something to put out there that easily explains our expertise. So if any of you want to chime in, please do.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-1461715634468524918?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/1461715634468524918/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/06/information-design-definitions.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/1461715634468524918'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/1461715634468524918'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/06/information-design-definitions.html' title='information design - definitions?'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-5037683482221783083.post-396735071085406581</id><published>2009-06-23T15:36:00.000-04:00</published><updated>2009-06-23T15:57:04.659-04:00</updated><title type='text'>first time - many questions</title><content type='html'>I'm new to this blogging thing and i thought it would be interesting to get like minded people involved in discussions about what i call "information design." Now i know there are other sites, blogs, etc., but i hope that i will be coming from a different perspective.&lt;br /&gt;&lt;br /&gt;First, i'm not sure if information design or plain language or anything else for that matter, is the right title.&lt;br /&gt;&lt;br /&gt;Most of us are doing the same thing, that is, &lt;strong&gt;trying to get information to end users in a way that it is easily understood and acted upon&lt;/strong&gt;. But, we come from all different walks of life, experiences, backgrounds, etc and although we agree on the end result, we disagree on how to get there.&lt;br /&gt;&lt;br /&gt;There are writers (plain language experts), graphic designers (those more visual), user experience experts, software developers, psycologists, sociologists, usability experts, etc. the list is long and, to me, confusing. Some of us work online (user interface), some with paper documents (me), some in small formats (PDAs,) etc, yet somehow we are all trying to do the same thing.&lt;br /&gt;&lt;br /&gt;Many people i meet think that what they do is the solution. I disagree. My premise is that in order to deliver information clearly and effectively, all of our expertise needs to come together.&lt;br /&gt;&lt;br /&gt;I often tell plain language experts that if they show me a document where the language is terrible, i will make it seem to the reader that they understand it because of the way i organize the information within the document. On the other hand, it you give me the same document written in very clear plain language, i will make it so it will be totally unreadable.&lt;br /&gt;&lt;br /&gt;My point is that it all has to work together. My hope is that with this blog, contributions from others and a meeting of the minds, we can create a unifed powerful industry working together.&lt;br /&gt;&lt;br /&gt;i hope that this blog will set up a dialogue among the many different practitioners.&lt;br /&gt;&lt;br /&gt;Let me hear from you.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5037683482221783083-396735071085406581?l=informationdesigndoc.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://informationdesigndoc.blogspot.com/feeds/396735071085406581/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/06/first-time-many-questions.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/396735071085406581'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5037683482221783083/posts/default/396735071085406581'/><link rel='alternate' type='text/html' href='http://informationdesigndoc.blogspot.com/2009/06/first-time-many-questions.html' title='first time - many questions'/><author><name>info design doc</name><uri>http://www.blogger.com/profile/18272028059242079178</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://1.bp.blogspot.com/_rXQaiWNSELc/SsuXSeDanlI/AAAAAAAAABc/aupCBZ0GE5A/S220/linsky.jpg'/></author><thr:total>0</thr:total></entry></feed>
