<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Jon Freach</title>
    <link>http://www.boxesandarrows.com/person/1785</link>
    <pubDate>Fri, 26 Jan 2007 14:53:46 GMT</pubDate>
    <description>Comments by Jon Freach</description>
    <item>
      <description>&lt;p&gt;Jeanene:&lt;br /&gt;Congratulations on your contributions to helping parents and kids with this condition and on a fine article.&lt;/p&gt;

	&lt;p&gt;I feel compelled to note four issues that were apparent to me as I read your post.&lt;/p&gt;

	&lt;p&gt;1. Branding&lt;br /&gt;I was confused by the name of the organization because Schwab is such a prominent financial services brand. Your backstory was helpful, but I think most folks wouldn&amp;#8217;t associate &amp;#8220;Schwab&amp;#8221; with &amp;#8220;learning difficulties,&amp;#8221; &amp;#8220;parents,&amp;#8221; or &amp;#8220;kids.&amp;#8221; Could a name that is more descriptive of Learning Difficulties be a quicker read?&lt;/p&gt;

	&lt;p&gt;2. Research Documentation&lt;br /&gt;The research seemed quite informative, but the graphic documentation appears to be a bit melodramatic, thin on data and hard to access. For example, the diagram illustrating &amp;#8220;Mom&amp;#8217;s evolution of knowledge&amp;#8221; seems terribly confusing (I&amp;#8217;m not sure where to begin reading this one) while the user type diagram showing the four basic interaction models would probably communicate better using a simple numeric hierarchy to communicate most important-to-least important tasks.&lt;/p&gt;

	&lt;p&gt;3. Wireframes&lt;br /&gt;The usability issues you described appear to be a result of the interface design tactics used at the low-fidelity level. If the wireframes actually looked more like an interface that a confused parent would be interacting with and less like a deliverable from a consultant, then maybe the first round of usability testing would have revealed some of the insights discovered during the second round.&lt;/p&gt;

	&lt;p&gt;4. Site Maintenance and  Site Degradation&lt;br /&gt;The current version of the home page seems to have abandoned the simple, straightforward and seemingly useful homepage design of February 2002. Can you comment on why you think this degradation has occurred? It has the look of retail, rather than the accessibility of a service.&lt;/p&gt;

	&lt;p&gt;Finally, please pardon the criticism, but as a former Director of User Experience at Sapient I was rather surprised to see this quality of work. While I understand that you were pleased with your service and deliverables, I see much room for improvement.&lt;/p&gt;

	&lt;p&gt;Thanks.&lt;br /&gt;Jon&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/schwablearning_org_a_case_study#content_4356</link>
      <guid>http://www.boxesandarrows.com/view/schwablearning_org_a_case_study#content_4356</guid>
      <pubDate>Fri, 26 Jan 2007 14:53:46 GMT</pubDate>
      <author>Jon Freach</author>
    </item>
    <item>
      <description>&lt;p&gt;I should also note that this article will cite case studies for M. D. Anderson Cancer Center in Houston, Texas; UMass Memorial Hospital in Worcester, Massachusetts; and, Central DuPage Hospital in Winfield, Illinois.&lt;/p&gt;

	&lt;p&gt;For each hospital, I lead a team of researchers, environmental graphic designers and interaction designers during the concept, design and implementation phases of an integrated wayfinding system. An integrated wayfinding system combines traditional wayfinding tools such as signs and maps with non-traditional tools such as web sites, touch screens and standardized verbal scripts to help visitors find their way to and around a complex medical campus and/or institution.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/4201#content_4364</link>
      <guid>http://www.boxesandarrows.com/idea/view/4201#content_4364</guid>
      <pubDate>Fri, 26 Jan 2007 14:53:46 GMT</pubDate>
      <author>Jon Freach</author>
    </item>
  </channel>
</rss>

