<?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: Design the stakeholder experience</title>
	<atom:link href="http://fronttoback.org/2009/08/20/design-the-stakeholder-experience/feed/" rel="self" type="application/rss+xml" />
	<link>http://fronttoback.org/2009/08/20/design-the-stakeholder-experience/</link>
	<description>Your users experience it that way around.</description>
	<lastBuildDate>Fri, 16 Jul 2010 23:00:21 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dennis Williams</title>
		<link>http://fronttoback.org/2009/08/20/design-the-stakeholder-experience/comment-page-1/#comment-22664</link>
		<dc:creator>Dennis Williams</dc:creator>
		<pubDate>Thu, 15 Oct 2009 07:02:10 +0000</pubDate>
		<guid isPermaLink="false">http://fronttoback.org/2009/08/20/design-the-stakeholder-experience/#comment-22664</guid>
		<description>there&#039;s a saying that goes - sell like you&#039;re buying. I&#039;ve always seen that as - If I were them - what would put me off - and what would I like. When I buy something I go look at the features, skip the marketing splurb and the go hunt for the bad reviews in order to make an informed decision. So I guess the same goes for when I try convince someone to buy in. I try and anticipate the shortcomings and be transparent about it from the start - which people appreciate and it also makes them feel part of the solution - because they have input all the time. They don&#039;t feel like I&#039;m telling them what to do - but rather start seeing the whole process as something collaborative.  Also, from the start of each project I sort of do a little guerrilla inquiry by basically trying to figure out who&#039;s who - preferences they have personalities, the interpersonal behavior and who&#039;s really calling the shots. I try to pick up on previous projects and most of all what their personal experiences were - why they didn&#039;t like things or what went wrong. I make notes of these and then decide on a strategy of how I&#039;m going to best achieve what I want to by targeting or engineering for the people I know will have the biggest influence on the project.  A lot of the time the boss is not the biggest obstacle. The dynamics on any project are driven by the people in the team and by truly understanding the people - and designing your own service around who they are and what they want make things go a lot smoother. With every presentation I do, I try to work up personas of the people that&#039;s going to be listening to my presentation - these influence time, language, domain topics and content, what they&#039;re trying to get from my talk (on a personal level and not just professional) - anybody in the presentation I know of that will be more resistant or influential - and if so - I want to focus more on that person whilst not alienating the rest. Nobody else sees my personas, so quick little notes and stickies which I add to my project folder and refer to throughout.</description>
		<content:encoded><![CDATA[<p>there&#8217;s a saying that goes &#8211; sell like you&#8217;re buying. I&#8217;ve always seen that as &#8211; If I were them &#8211; what would put me off &#8211; and what would I like. When I buy something I go look at the features, skip the marketing splurb and the go hunt for the bad reviews in order to make an informed decision. So I guess the same goes for when I try convince someone to buy in. I try and anticipate the shortcomings and be transparent about it from the start &#8211; which people appreciate and it also makes them feel part of the solution &#8211; because they have input all the time. They don&#8217;t feel like I&#8217;m telling them what to do &#8211; but rather start seeing the whole process as something collaborative.  Also, from the start of each project I sort of do a little guerrilla inquiry by basically trying to figure out who&#8217;s who &#8211; preferences they have personalities, the interpersonal behavior and who&#8217;s really calling the shots. I try to pick up on previous projects and most of all what their personal experiences were &#8211; why they didn&#8217;t like things or what went wrong. I make notes of these and then decide on a strategy of how I&#8217;m going to best achieve what I want to by targeting or engineering for the people I know will have the biggest influence on the project.  A lot of the time the boss is not the biggest obstacle. The dynamics on any project are driven by the people in the team and by truly understanding the people &#8211; and designing your own service around who they are and what they want make things go a lot smoother. With every presentation I do, I try to work up personas of the people that&#8217;s going to be listening to my presentation &#8211; these influence time, language, domain topics and content, what they&#8217;re trying to get from my talk (on a personal level and not just professional) &#8211; anybody in the presentation I know of that will be more resistant or influential &#8211; and if so &#8211; I want to focus more on that person whilst not alienating the rest. Nobody else sees my personas, so quick little notes and stickies which I add to my project folder and refer to throughout.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
