<?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"
	>
<channel>
	<title>Comments on: A Framework for Engagement - Implementation</title>
	<atom:link href="http://blog.jimnovo.com/2008/02/04/framework-engagement-implementation/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jimnovo.com/2008/02/04/framework-engagement-implementation/</link>
	<description>Moving from a Low Accountability to a High Accountability Business Model</description>
	<pubDate>Fri,  5 Sep 2008 18:10:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Theo Papadakis</title>
		<link>http://blog.jimnovo.com/2008/02/04/framework-engagement-implementation/#comment-17682</link>
		<dc:creator>Theo Papadakis</dc:creator>
		<pubDate>Tue, 05 Feb 2008 13:21:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/2008/02/04/framework-engagement-implementation/#comment-17682</guid>
		<description>By benchmark i mean set a threshold 'average degree of engagement'.  Although it is a engagement/disengagement is a proces it seems necessary to set an average, a point, over or under which the customer is engaging or disengaging.</description>
		<content:encoded><![CDATA[<p>By benchmark i mean set a threshold &#8216;average degree of engagement&#8217;.  Although it is a engagement/disengagement is a proces it seems necessary to set an average, a point, over or under which the customer is engaging or disengaging.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Novo</title>
		<link>http://blog.jimnovo.com/2008/02/04/framework-engagement-implementation/#comment-17679</link>
		<dc:creator>Jim Novo</dc:creator>
		<pubDate>Tue, 05 Feb 2008 13:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/2008/02/04/framework-engagement-implementation/#comment-17679</guid>
		<description>Benchmarking? Perhaps, but there already is a universal standard measurement for dis-engagement - "time since last engagement action". And dis-engagement is not typically an event, it's a process. So the measurement is really not about over / under, it's about degree and likelihood. What is likelihood customer is still engaged? This drives voice, how you speak to the customer.

So, for example, the campaign by Steve Jackson and his "Inactive Registrant Index”. Customer registers for the MMS program but takes no action, or takes action but then stops. The longer you wait to address that inactivity, that dis-engagement, the less likely it will be you can re-activate the customer.

You can set a threshold (Latency) "if they don't re-engage within 2 weeks we will send a coupon" or you can scale the message and effort based on behavior (Recency), if they don't re-engage within 1 week we will send an e-mail, those who don't re-enage after another week will get a coupon, those who don't re-enage after a 3rd week will get 2 coupons".

The point is to make the message and offer more relevant to the state of the customer based on their behavior while at the same time optimizing the cost side. Act only when you have to and always at the point of maximum impact. 

There might be benchmarks for different industries but it's much more likely - as is the point of this whole strategy - that these "time since" metrics will be different for different industries, and most important, different for different customers.  You have to test and optimize.  Once you find the optimal re-engagement point from a response / cost perspective for each segment, it tends to remain stable for that segment. 

If you want more on the details, see:

http://blog.jimnovo.com/2007/04/25/measuring-engagement/</description>
		<content:encoded><![CDATA[<p>Benchmarking? Perhaps, but there already is a universal standard measurement for dis-engagement - &#8220;time since last engagement action&#8221;. And dis-engagement is not typically an event, it&#8217;s a process. So the measurement is really not about over / under, it&#8217;s about degree and likelihood. What is likelihood customer is still engaged? This drives voice, how you speak to the customer.</p>
<p>So, for example, the campaign by Steve Jackson and his &#8220;Inactive Registrant Index”. Customer registers for the MMS program but takes no action, or takes action but then stops. The longer you wait to address that inactivity, that dis-engagement, the less likely it will be you can re-activate the customer.</p>
<p>You can set a threshold (Latency) &#8220;if they don&#8217;t re-engage within 2 weeks we will send a coupon&#8221; or you can scale the message and effort based on behavior (Recency), if they don&#8217;t re-engage within 1 week we will send an e-mail, those who don&#8217;t re-enage after another week will get a coupon, those who don&#8217;t re-enage after a 3rd week will get 2 coupons&#8221;.</p>
<p>The point is to make the message and offer more relevant to the state of the customer based on their behavior while at the same time optimizing the cost side. Act only when you have to and always at the point of maximum impact. </p>
<p>There might be benchmarks for different industries but it&#8217;s much more likely - as is the point of this whole strategy - that these &#8220;time since&#8221; metrics will be different for different industries, and most important, different for different customers.  You have to test and optimize.  Once you find the optimal re-engagement point from a response / cost perspective for each segment, it tends to remain stable for that segment. </p>
<p>If you want more on the details, see:</p>
<p><a href="http://blog.jimnovo.com/2007/04/25/measuring-engagement/" rel="nofollow">http://blog.jimnovo.com/2007/04/25/measuring-engagement/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Theo Papadakis</title>
		<link>http://blog.jimnovo.com/2008/02/04/framework-engagement-implementation/#comment-17655</link>
		<dc:creator>Theo Papadakis</dc:creator>
		<pubDate>Tue, 05 Feb 2008 10:31:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/2008/02/04/framework-engagement-implementation/#comment-17655</guid>
		<description>Very interesting. According to what you say, it is therefore imperative to clearly define how and when a customer has begun dis-engaging. 

This requires to benchmark website or industry performance and define what an average degree of engagement is. Anything below this number is dis-engagement and anything above it - engagement (which of course can and should be further refined and segmented according to progressive degrees of greater engagement/disengagement).</description>
		<content:encoded><![CDATA[<p>Very interesting. According to what you say, it is therefore imperative to clearly define how and when a customer has begun dis-engaging. </p>
<p>This requires to benchmark website or industry performance and define what an average degree of engagement is. Anything below this number is dis-engagement and anything above it - engagement (which of course can and should be further refined and segmented according to progressive degrees of greater engagement/disengagement).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
