<?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: Monday&#8217;s Musings: Users Now Expect More Advocacy From Their User Groups</title>
	<atom:link href="http://blog.softwareinsider.org/2009/08/03/mondays-musings-users-now-expect-more-advocacy-from-their-user-groups/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.softwareinsider.org/2009/08/03/mondays-musings-users-now-expect-more-advocacy-from-their-user-groups/</link>
	<description>Your buy side advocate for enterprise apps strategies, vendor selection, &#38; contract negotiations</description>
	<lastBuildDate>Tue, 07 Sep 2010 23:56:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Doug Hadden</title>
		<link>http://blog.softwareinsider.org/2009/08/03/mondays-musings-users-now-expect-more-advocacy-from-their-user-groups/comment-page-1/#comment-2324</link>
		<dc:creator>Doug Hadden</dc:creator>
		<pubDate>Mon, 03 Aug 2009 17:20:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareinsider.org/?p=1610#comment-2324</guid>
		<description>Many vendors and customers view user groups in a traditional manner. The results show two aspects of the traditional approach: company-to-customer planning and tactical considerations rather than strategic.

&lt;b&gt;Company to Customer&lt;/b&gt;
Enterprise customers seem to expect that vendors will dictate the product roadmap, enhancements and innovations during user group meetings. Customers hope that they can influence important changes such as the high rating for &quot;address product issues&quot; and &quot;influence roadmaps&quot;. The world has changed. Customers can and should leverage the user group and other mechanisms like forums to set product roadmaps. Customers should not try to influence the roadmap - they should be able to make wholesale changes to it. 

&lt;b&gt;Tactical rather than Strategic&lt;/b&gt;
The items in the survey that relate to the customer to vendor relationship shows a preference for tactical aspects. It is particular disturbing to see &quot;liaise with executives&quot; at the bottom of the list. Perhaps vendor executives rarely interact with customers (a bad sign) or the user group is managed by the product management group as a feel good exercise and executives are window dressing. Perhaps previous interaction with executives did not have positive results for customers.

&lt;b&gt;A Different approach - the steering committee&lt;/b&gt;
There is a viewpoint that following customer tactical requirements will result in going out of business. It is true that tactical product needs often does not reflect what customers will need 2 or 3 years down the road. The mechanism of user groups tends to support majority rules. Yet, it is the outliers that will often drive the product future. 

My company has been leveraging the steering committee approach. We have run into some resistance from some customers who expect to be consumers rather than participants. We have developed a few rules that we can share:

- The steering committee is an adjunct, not a replacement of the user group.
- Outlier customers participate in the steering committee. The vendor picks steering committee members. The user group has the ability to add additional customers.
- Only company executives and company domain experts attend the steering committee meetings. In particular, salespeople should not be there.
- Executives must be fully prepared and know what the issues are. Executives should attend these sessions without a safety net.
- Presentations, where the company broadcasts information, should be limited.
- Presentations by customers should be the first order of business.
- Workshops using various brainstorming techniques should be used to draw out ideas and support decisions.
- Customers change priorities and the roadmap.
- The roadmap window under discussion is 1 to 3 years out, rather than enhancements for the next release.
- Progress on the roadmap and other vendor action items should be provided on a quarterly basis to the chairperson of the steering committee.

We have found that this approach addresses many of the items that you describe

- &lt;i&gt;Dedicating executive resources&lt;/i&gt; to user group initiatives because executives participate in the meetings
- &lt;i&gt;Increasing transparency in the requirements prioritization process &lt;/i&gt;through enabling the committee to make wholesale changes to the roadmap
- &lt;i&gt;Creating resources to share benchmarking information&lt;/i&gt; is partly satisfied through the customer presentations. 
- &lt;i&gt;Reporting more frequently on progress &lt;/i&gt;through quarterly updates.</description>
		<content:encoded><![CDATA[<p>Many vendors and customers view user groups in a traditional manner. The results show two aspects of the traditional approach: company-to-customer planning and tactical considerations rather than strategic.</p>
<p><b>Company to Customer</b><br />
Enterprise customers seem to expect that vendors will dictate the product roadmap, enhancements and innovations during user group meetings. Customers hope that they can influence important changes such as the high rating for &#8220;address product issues&#8221; and &#8220;influence roadmaps&#8221;. The world has changed. Customers can and should leverage the user group and other mechanisms like forums to set product roadmaps. Customers should not try to influence the roadmap &#8211; they should be able to make wholesale changes to it. </p>
<p><b>Tactical rather than Strategic</b><br />
The items in the survey that relate to the customer to vendor relationship shows a preference for tactical aspects. It is particular disturbing to see &#8220;liaise with executives&#8221; at the bottom of the list. Perhaps vendor executives rarely interact with customers (a bad sign) or the user group is managed by the product management group as a feel good exercise and executives are window dressing. Perhaps previous interaction with executives did not have positive results for customers.</p>
<p><b>A Different approach &#8211; the steering committee</b><br />
There is a viewpoint that following customer tactical requirements will result in going out of business. It is true that tactical product needs often does not reflect what customers will need 2 or 3 years down the road. The mechanism of user groups tends to support majority rules. Yet, it is the outliers that will often drive the product future. </p>
<p>My company has been leveraging the steering committee approach. We have run into some resistance from some customers who expect to be consumers rather than participants. We have developed a few rules that we can share:</p>
<p>- The steering committee is an adjunct, not a replacement of the user group.<br />
- Outlier customers participate in the steering committee. The vendor picks steering committee members. The user group has the ability to add additional customers.<br />
- Only company executives and company domain experts attend the steering committee meetings. In particular, salespeople should not be there.<br />
- Executives must be fully prepared and know what the issues are. Executives should attend these sessions without a safety net.<br />
- Presentations, where the company broadcasts information, should be limited.<br />
- Presentations by customers should be the first order of business.<br />
- Workshops using various brainstorming techniques should be used to draw out ideas and support decisions.<br />
- Customers change priorities and the roadmap.<br />
- The roadmap window under discussion is 1 to 3 years out, rather than enhancements for the next release.<br />
- Progress on the roadmap and other vendor action items should be provided on a quarterly basis to the chairperson of the steering committee.</p>
<p>We have found that this approach addresses many of the items that you describe</p>
<p>- <i>Dedicating executive resources</i> to user group initiatives because executives participate in the meetings<br />
- <i>Increasing transparency in the requirements prioritization process </i>through enabling the committee to make wholesale changes to the roadmap<br />
- <i>Creating resources to share benchmarking information</i> is partly satisfied through the customer presentations.<br />
- <i>Reporting more frequently on progress </i>through quarterly updates.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
