<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Building Many Roads to a Single Destination</title>
	<atom:link href="http://webiscope.com/2008/01/building-many-roads-to-a-single-destination/feed/" rel="self" type="application/rss+xml" />
	<link>http://webiscope.com/2008/01/building-many-roads-to-a-single-destination/</link>
	<description>Internet Healthcare Collaboration</description>
	<lastBuildDate>Fri, 11 Dec 2009 10:10:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rush-Copley Medical Center Launches User-Focused Web Site &#171; Geovoices: A Geonetric blog</title>
		<link>http://webiscope.com/2008/01/building-many-roads-to-a-single-destination/comment-page-1/#comment-500</link>
		<dc:creator>Rush-Copley Medical Center Launches User-Focused Web Site &#171; Geovoices: A Geonetric blog</dc:creator>
		<pubDate>Fri, 12 Dec 2008 15:21:52 +0000</pubDate>
		<guid isPermaLink="false">http://webiscope.com/2008/01/building-many-roads-to-a-single-destination/#comment-500</guid>
		<description>[...] Building Many Roads to a Single Destination [...]</description>
		<content:encoded><![CDATA[<p>[...] Building Many Roads to a Single Destination [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Capn</title>
		<link>http://webiscope.com/2008/01/building-many-roads-to-a-single-destination/comment-page-1/#comment-258</link>
		<dc:creator>Capn</dc:creator>
		<pubDate>Fri, 04 Jan 2008 21:13:16 +0000</pubDate>
		<guid isPermaLink="false">http://webiscope.com/2008/01/building-many-roads-to-a-single-destination/#comment-258</guid>
		<description>Can&#039;t agree more with the &quot;persona&quot; method.  Especially when it comes to explaining the rationale behind any content organization decision made for the web.  By assigning a persona, you are &#039;humanizing&#039; the visitor - who is essentially nameless and faceless to the institution - and creating something almost tangible for those on the inside of the institution to latch onto.  Give a persona a name, a face, and a story to go along with the reason they&#039;re visiting your site - and all the sudden the room is full of great ideas.  

As we&#039;re re-designing our public site, we&#039;ve just storyboarded an entire family of personas to match all the primary service lines we want to reach with the phase one roll out.  They include a young couple, recently relocated (husband/father is an MI tech looking for work - touches up on the HR requirements; wife/mother wants to become a nurse - leads to our school of nursing) - they have a newborn/premie w/ issues (NICU).  They have parents in the area w/ various mid-life issues (arthritis, high BP, etc), and they have elderly parents with their own issues (palliative care, etc), not to mention an in-law with a chemical dependency ... I mean, it&#039;s a soap opera.  But each individual (persona) will give the various &#039;shareholders&#039; in our institution something to think about - and a legitimate touchstone from which to focus their creative input.

It&#039;s actually pretty neat to watch - and that was just the quick brainstorming session we had to &quot;design&quot; our personas.  I can&#039;t wait to see what happens when we introduce them to the staff being interviewed ...</description>
		<content:encoded><![CDATA[<p>Can&#8217;t agree more with the &#8220;persona&#8221; method.  Especially when it comes to explaining the rationale behind any content organization decision made for the web.  By assigning a persona, you are &#8216;humanizing&#8217; the visitor &#8211; who is essentially nameless and faceless to the institution &#8211; and creating something almost tangible for those on the inside of the institution to latch onto.  Give a persona a name, a face, and a story to go along with the reason they&#8217;re visiting your site &#8211; and all the sudden the room is full of great ideas.  </p>
<p>As we&#8217;re re-designing our public site, we&#8217;ve just storyboarded an entire family of personas to match all the primary service lines we want to reach with the phase one roll out.  They include a young couple, recently relocated (husband/father is an MI tech looking for work &#8211; touches up on the HR requirements; wife/mother wants to become a nurse &#8211; leads to our school of nursing) &#8211; they have a newborn/premie w/ issues (NICU).  They have parents in the area w/ various mid-life issues (arthritis, high BP, etc), and they have elderly parents with their own issues (palliative care, etc), not to mention an in-law with a chemical dependency &#8230; I mean, it&#8217;s a soap opera.  But each individual (persona) will give the various &#8217;shareholders&#8217; in our institution something to think about &#8211; and a legitimate touchstone from which to focus their creative input.</p>
<p>It&#8217;s actually pretty neat to watch &#8211; and that was just the quick brainstorming session we had to &#8220;design&#8221; our personas.  I can&#8217;t wait to see what happens when we introduce them to the staff being interviewed &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neal</title>
		<link>http://webiscope.com/2008/01/building-many-roads-to-a-single-destination/comment-page-1/#comment-257</link>
		<dc:creator>Neal</dc:creator>
		<pubDate>Thu, 03 Jan 2008 15:11:45 +0000</pubDate>
		<guid isPermaLink="false">http://webiscope.com/2008/01/building-many-roads-to-a-single-destination/#comment-257</guid>
		<description>That is a tried and true approach. Ask any 10 people how they found the same piece of content, and you are likely to get 11 different answers.  Amazing to me, though, is how many in the organization question when we offer more than one path to the same content. &quot;Waste of valuable real estate,&quot; they claim.  I think they couldn&#039;t be more wrong.</description>
		<content:encoded><![CDATA[<p>That is a tried and true approach. Ask any 10 people how they found the same piece of content, and you are likely to get 11 different answers.  Amazing to me, though, is how many in the organization question when we offer more than one path to the same content. &#8220;Waste of valuable real estate,&#8221; they claim.  I think they couldn&#8217;t be more wrong.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
