<?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 for onVector Consulting Group</title>
	<atom:link href="http://www.onvectorconsulting.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.onvectorconsulting.com</link>
	<description>Line of Sight to Performance Excellence</description>
	<lastBuildDate>Sat, 04 Jan 2014 18:28:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.2.18</generator>
	<item>
		<title>Comment on 2014: The Year of Touchpoint Renewal by The Anatomy of a Touchpoint &#124; onVector Consulting Group</title>
		<link>http://www.onvectorconsulting.com/2014-the-year-of-touchpoint-renewal/#comment-447</link>
		<dc:creator><![CDATA[The Anatomy of a Touchpoint &#124; onVector Consulting Group]]></dc:creator>
		<pubDate>Sat, 04 Jan 2014 18:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.onvectorconsulting.com/?p=2959#comment-447</guid>
		<description><![CDATA[[&#8230;] &#8592; Previous [&#8230;]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] &larr; Previous [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 2011- Year of the Squirrel by Tammy</title>
		<link>http://www.onvectorconsulting.com/2011-year-of-the-squirrel-2/#comment-116</link>
		<dc:creator><![CDATA[Tammy]]></dc:creator>
		<pubDate>Sun, 01 Jan 2012 17:21:40 +0000</pubDate>
		<guid isPermaLink="false">http://epmedge.com/?p=1400#comment-116</guid>
		<description><![CDATA[Great analogy with the movie Up! What I have often found is that some of the distractions are ego-based.  A leader sees the opportunity to get some fame and other public kudos from a venture and then chases it like crazy or more likely, causes the worker-bees to chase it like crazy and no one calls them off. And those who observe are always hesitant to say that the emperor is not wearing clothes. I think this is where a Board comes in and time and time again, I see the failure of Boards to provide this type of direction.]]></description>
		<content:encoded><![CDATA[<p>Great analogy with the movie Up! What I have often found is that some of the distractions are ego-based.  A leader sees the opportunity to get some fame and other public kudos from a venture and then chases it like crazy or more likely, causes the worker-bees to chase it like crazy and no one calls them off. And those who observe are always hesitant to say that the emperor is not wearing clothes. I think this is where a Board comes in and time and time again, I see the failure of Boards to provide this type of direction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Customer Nirvana  -When great products meet awesome service&#8230; by Bob Champagne</title>
		<link>http://www.onvectorconsulting.com/customer-nirvana-when-great-products-meet-awesome-service/#comment-111</link>
		<dc:creator><![CDATA[Bob Champagne]]></dc:creator>
		<pubDate>Tue, 29 Nov 2011 22:41:04 +0000</pubDate>
		<guid isPermaLink="false">http://epmedge.com/?p=1270#comment-111</guid>
		<description><![CDATA[Thanks for the comments- all good points. I think &quot;incrementalism&quot; can kill us on both fronts. On the operational front, it leads to &quot;just enough to get by&quot; behavior and prevents step changes in efficiency and production. On the product side, it prevents the advances that are only made by creating and innovating rather than reacting and following. What both of you are pointing to is a &quot;culture&quot; of innovation that needs to be part of operations as well as product development and innovation.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the comments- all good points. I think &#8220;incrementalism&#8221; can kill us on both fronts. On the operational front, it leads to &#8220;just enough to get by&#8221; behavior and prevents step changes in efficiency and production. On the product side, it prevents the advances that are only made by creating and innovating rather than reacting and following. What both of you are pointing to is a &#8220;culture&#8221; of innovation that needs to be part of operations as well as product development and innovation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Customer Nirvana  -When great products meet awesome service&#8230; by Tammy</title>
		<link>http://www.onvectorconsulting.com/customer-nirvana-when-great-products-meet-awesome-service/#comment-110</link>
		<dc:creator><![CDATA[Tammy]]></dc:creator>
		<pubDate>Tue, 29 Nov 2011 05:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://epmedge.com/?p=1270#comment-110</guid>
		<description><![CDATA[I think it&#039;s important to focus in on the iterative process that measurements and refining products and services requires. Nothing is constant and we can bogle our minds trying to understand what influences thinking and changes in our thinking. 

Actually, Doug&#039;s glove scenario above is indicative of this very thing and I&#039;m impressed with the way he took the customer culture and applied it in a safety &quot;lineside&quot; setting. That&#039;s what we should all be striving for.]]></description>
		<content:encoded><![CDATA[<p>I think it&#8217;s important to focus in on the iterative process that measurements and refining products and services requires. Nothing is constant and we can bogle our minds trying to understand what influences thinking and changes in our thinking. </p>
<p>Actually, Doug&#8217;s glove scenario above is indicative of this very thing and I&#8217;m impressed with the way he took the customer culture and applied it in a safety &#8220;lineside&#8221; setting. That&#8217;s what we should all be striving for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Deafening Silence &#8212; Failing to communicate in times of chaos&#8230; by Dean</title>
		<link>http://www.onvectorconsulting.com/deafening-silence-failing-to-communicate-in-times-of-chaos/#comment-115</link>
		<dc:creator><![CDATA[Dean]]></dc:creator>
		<pubDate>Sun, 20 Nov 2011 02:17:02 +0000</pubDate>
		<guid isPermaLink="false">http://epmedge.com/?p=1327#comment-115</guid>
		<description><![CDATA[Bob, not only was the outage and lack of communication frustrating, I received the system generated calls 3 times to confirm my power was back, and it was not.]]></description>
		<content:encoded><![CDATA[<p>Bob, not only was the outage and lack of communication frustrating, I received the system generated calls 3 times to confirm my power was back, and it was not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What Can Social Media Teach Us About Performance Management? by Blog &#124; Marketing Innovators &#124; Inspiring People to Greater Performance &#124; Marketing Innovators</title>
		<link>http://www.onvectorconsulting.com/what-can-social-media-teach-us-about-performance-management/#comment-19</link>
		<dc:creator><![CDATA[Blog &#124; Marketing Innovators &#124; Inspiring People to Greater Performance &#124; Marketing Innovators]]></dc:creator>
		<pubDate>Fri, 18 Nov 2011 19:46:26 +0000</pubDate>
		<guid isPermaLink="false">http://performancemanagementperspectives.wordpress.com/?p=180#comment-19</guid>
		<description><![CDATA[[...] http://epmedge.com/2011/02/07/what-can-social-media-teach-us-about-performance-management/ [...] ]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] <a href="http://epmedge.com/2011/02/07/what-can-social-media-teach-us-about-performance-management/" rel="nofollow">http://epmedge.com/2011/02/07/what-can-social-media-teach-us-about-performance-management/</a> [&#8230;] </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Metrics that make you go&#8230;YAWN&#8230; by Tammy</title>
		<link>http://www.onvectorconsulting.com/metrics-that-make-you-go-yawn/#comment-114</link>
		<dc:creator><![CDATA[Tammy]]></dc:creator>
		<pubDate>Wed, 02 Nov 2011 03:31:23 +0000</pubDate>
		<guid isPermaLink="false">http://epmedge.com/?p=1283#comment-114</guid>
		<description><![CDATA[Great points. I think that metrics suffer when they don&#039;t tie back to the overall strategy. I also think that metrics of any type suffer when we get into the incremental gain game. So, two things that we can do to move beyond? talk to customers to see if we&#039;re measuring the right things from their perspective and invent a new future - how can we come up with some wild gains (even if we don&#039;t publish them internally).]]></description>
		<content:encoded><![CDATA[<p>Great points. I think that metrics suffer when they don&#8217;t tie back to the overall strategy. I also think that metrics of any type suffer when we get into the incremental gain game. So, two things that we can do to move beyond? talk to customers to see if we&#8217;re measuring the right things from their perspective and invent a new future &#8211; how can we come up with some wild gains (even if we don&#8217;t publish them internally).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Customer Nirvana  -When great products meet awesome service&#8230; by Douglas Dale (@DouglasCDale)</title>
		<link>http://www.onvectorconsulting.com/customer-nirvana-when-great-products-meet-awesome-service/#comment-109</link>
		<dc:creator><![CDATA[Douglas Dale (@DouglasCDale)]]></dc:creator>
		<pubDate>Tue, 01 Nov 2011 14:32:57 +0000</pubDate>
		<guid isPermaLink="false">http://epmedge.com/?p=1270#comment-109</guid>
		<description><![CDATA[Interesting concept Bob, I am in complete agreement about the idea that solutions need to be first looked at before trying to improve the process.  Matter of fact, I believe that too often incremental improvement is the death of innovation.    More often than not, companies do not go back and try to answer the original question that they were trying to solve which prevents them from innovating.  I have started to help clients go back and &quot;stay in the question&quot; longer and work toward new more innovative solutions rather than getting a process change or improvement and calling it “good”.  I believe that it is human nature to recycle old solutions and really never get to the more creative approach. 
For example, one utility client who was dealing with safety performance issues kept trying to improve their pre-job briefs and developed KPI’s for how long and how often they were occurring. After their performance continued to slip, we tried a new approach. By staying in the question longer, we found out that many of the safety issues had to do with cutting and scraping their hands and they were actually using the wrong type of gloves for many of the tasks they were performing.  The group created a board that showed the different types of gloves that were available in the tool crib and the application for each (they also got rid of several types of gloves).  This one action improved their safety performance and had little to do with how effective the pre-job briefs were or the way they measured safety performance.]]></description>
		<content:encoded><![CDATA[<p>Interesting concept Bob, I am in complete agreement about the idea that solutions need to be first looked at before trying to improve the process.  Matter of fact, I believe that too often incremental improvement is the death of innovation.    More often than not, companies do not go back and try to answer the original question that they were trying to solve which prevents them from innovating.  I have started to help clients go back and &#8220;stay in the question&#8221; longer and work toward new more innovative solutions rather than getting a process change or improvement and calling it “good”.  I believe that it is human nature to recycle old solutions and really never get to the more creative approach.<br />
For example, one utility client who was dealing with safety performance issues kept trying to improve their pre-job briefs and developed KPI’s for how long and how often they were occurring. After their performance continued to slip, we tried a new approach. By staying in the question longer, we found out that many of the safety issues had to do with cutting and scraping their hands and they were actually using the wrong type of gloves for many of the tasks they were performing.  The group created a board that showed the different types of gloves that were available in the tool crib and the application for each (they also got rid of several types of gloves).  This one action improved their safety performance and had little to do with how effective the pre-job briefs were or the way they measured safety performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Metrics that make you go&#8230;YAWN&#8230; by Dennis Adsit</title>
		<link>http://www.onvectorconsulting.com/metrics-that-make-you-go-yawn/#comment-113</link>
		<dc:creator><![CDATA[Dennis Adsit]]></dc:creator>
		<pubDate>Mon, 31 Oct 2011 20:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://epmedge.com/?p=1283#comment-113</guid>
		<description><![CDATA[Yawn?  It is actually worse than that, Bob.  It makes me want to call the BBB or a lawyer to see if they can be sued for malpractice.

Here is a novel metric:  Let&#039;s measure the % of time agents do what they are supposed to do, by call type.  Customers call us for many reasons...to activate a phone, to replace a credit card, to order cable services or we call them to upsell them or collect money.  There are certain things that are supposed to be said to customers and done in desktop systems on those calls...those things are, in part, what make it a good call for the customer and a good call for the company.

There are two struthious reasons why few centers have this metric at all let alone accompanied by a drill-down by call type.  The first is that for most centers, it is a hard measure to gather.  You have to dedicate speech analytics programming or you have to dedicate monitors to sampling calls and listening to see if the required call components are there and you have to do it regularly to see if progress is being made.  Instead they make a dashboard of what is easy to measure.  In so doing, they are like the drunk looking for his keys under a street lamp, even though that is not where he lost them, because &quot;the light is better here.&quot;

The second reason is actually a bit more insidious.  They don&#039;t measure it because they have unplugged the smoke alarms.  They know it is a problem but they don&#039;t measure it because they don&#039;t know how to fix it.  They have tried monitoring and coaching but they can&#039;t move the needle.  What they may or may not realize is monitoring and coaching can not fix process variation, but they do know that they don&#039;t know what else to do.

Until we measure whether we are doing what we are supposed to do on each call and taking steps to reduce the inevitable between agent variation in process and outputs we really are way beyond boring.  We are failing our employees, who want to do the right thing, we are failing our customers who expect us to know what we are doing, and we are failing our shareholders by leaving revenue on the table (eg, failing to upsell), increasing costs (eg, callbacks), and putting the company at risk (eg, failing to give required disclosures).  If interested, you can read more in this isixsigma.com article:  http://www.isixsigma.com/index.php?option=com_k2&amp;view=item&amp;id=1567:fixing-between-agent-variation-can-make-all-the-difference&amp;Itemid=223

Sincerely,

Dennis Adsit]]></description>
		<content:encoded><![CDATA[<p>Yawn?  It is actually worse than that, Bob.  It makes me want to call the BBB or a lawyer to see if they can be sued for malpractice.</p>
<p>Here is a novel metric:  Let&#8217;s measure the % of time agents do what they are supposed to do, by call type.  Customers call us for many reasons&#8230;to activate a phone, to replace a credit card, to order cable services or we call them to upsell them or collect money.  There are certain things that are supposed to be said to customers and done in desktop systems on those calls&#8230;those things are, in part, what make it a good call for the customer and a good call for the company.</p>
<p>There are two struthious reasons why few centers have this metric at all let alone accompanied by a drill-down by call type.  The first is that for most centers, it is a hard measure to gather.  You have to dedicate speech analytics programming or you have to dedicate monitors to sampling calls and listening to see if the required call components are there and you have to do it regularly to see if progress is being made.  Instead they make a dashboard of what is easy to measure.  In so doing, they are like the drunk looking for his keys under a street lamp, even though that is not where he lost them, because &#8220;the light is better here.&#8221;</p>
<p>The second reason is actually a bit more insidious.  They don&#8217;t measure it because they have unplugged the smoke alarms.  They know it is a problem but they don&#8217;t measure it because they don&#8217;t know how to fix it.  They have tried monitoring and coaching but they can&#8217;t move the needle.  What they may or may not realize is monitoring and coaching can not fix process variation, but they do know that they don&#8217;t know what else to do.</p>
<p>Until we measure whether we are doing what we are supposed to do on each call and taking steps to reduce the inevitable between agent variation in process and outputs we really are way beyond boring.  We are failing our employees, who want to do the right thing, we are failing our customers who expect us to know what we are doing, and we are failing our shareholders by leaving revenue on the table (eg, failing to upsell), increasing costs (eg, callbacks), and putting the company at risk (eg, failing to give required disclosures).  If interested, you can read more in this isixsigma.com article:  <a href="http://www.isixsigma.com/index.php?option=com_k2&#038;view=item&#038;id=1567:fixing-between-agent-variation-can-make-all-the-difference&#038;Itemid=223" rel="nofollow">http://www.isixsigma.com/index.php?option=com_k2&#038;view=item&#038;id=1567:fixing-between-agent-variation-can-make-all-the-difference&#038;Itemid=223</a></p>
<p>Sincerely,</p>
<p>Dennis Adsit</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Metrics that make you go&#8230;YAWN&#8230; by Haim Toeg</title>
		<link>http://www.onvectorconsulting.com/metrics-that-make-you-go-yawn/#comment-112</link>
		<dc:creator><![CDATA[Haim Toeg]]></dc:creator>
		<pubDate>Fri, 28 Oct 2011 19:53:32 +0000</pubDate>
		<guid isPermaLink="false">http://epmedge.com/?p=1283#comment-112</guid>
		<description><![CDATA[Bob - I always enjoy reading your posts and mostly find I agree with them.  I wrote several posts discussing metrics and organizational objectives (http://www.haimtoeg.com/?p=35 for example, using the same road trip metaphor used here).  One of the things I try to do is avoid using the term &quot;KPI&quot; - It became synonymous with metric, losing the fact that it is &quot;key&quot; to something.  

To overcome that, I try to think of metrics in two groups, those you manage to and those that you monitor.  The first is determined by strategy and operational objectives, the second contains everything else that indicates the health of your operation but is not necessarily associated with your objectives.  Borrowing from the road trip example, if your engine maintains its temperature it has no influence on your trip, but if it overheats it will surely spoil your day.]]></description>
		<content:encoded><![CDATA[<p>Bob &#8211; I always enjoy reading your posts and mostly find I agree with them.  I wrote several posts discussing metrics and organizational objectives (<a href="http://www.haimtoeg.com/?p=35" rel="nofollow">http://www.haimtoeg.com/?p=35</a> for example, using the same road trip metaphor used here).  One of the things I try to do is avoid using the term &#8220;KPI&#8221; &#8211; It became synonymous with metric, losing the fact that it is &#8220;key&#8221; to something.  </p>
<p>To overcome that, I try to think of metrics in two groups, those you manage to and those that you monitor.  The first is determined by strategy and operational objectives, the second contains everything else that indicates the health of your operation but is not necessarily associated with your objectives.  Borrowing from the road trip example, if your engine maintains its temperature it has no influence on your trip, but if it overheats it will surely spoil your day.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
