<?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: Vertical and Horizontal Dimensions of Strategy &#8211; Part I</title>
	<atom:link href="http://tenacioustortoise.com/index.php/2009/06/09/vertical-horizontal-strategy/feed/" rel="self" type="application/rss+xml" />
	<link>http://tenacioustortoise.com/index.php/2009/06/09/vertical-horizontal-strategy/</link>
	<description>insights and consulting for change</description>
	<lastBuildDate>Wed, 07 Apr 2010 23:54:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Robert S. Gold</title>
		<link>http://tenacioustortoise.com/index.php/2009/06/09/vertical-horizontal-strategy/comment-page-1/#comment-24</link>
		<dc:creator>Robert S. Gold</dc:creator>
		<pubDate>Fri, 12 Jun 2009 19:22:14 +0000</pubDate>
		<guid isPermaLink="false">http://tenacioustortoise.com/?p=685#comment-24</guid>
		<description>Bob:

Thanks for your comment. While the concept of top-to-bottom vertical themes (TBVT) makes logical sense, in practice it has been a challenge. Cause-and-effect relationships don&#039;t usually fit a one-to-one sequence leading up the map. A typical objective at the bottom of the map, such as &quot;Drive a culture of performance and accountability&quot; is certain to be seen by management as a driver for many objectives in a process perspective above. The use of arrows to denote cause-and-effect relationships becomes a bit of a clutter when there are these one-to-many relationships. In reality, there are very few maps with TBVT, and I hope I&#039;ll not be using that acronym any more.

Even when themes don&#039;t necessarily span all perspectives, they are a great way of organizing strategy review meetings, especially for relatively new BSCs. However, leadership teams with mature BSCs often use the first few minutes of the review meeting for a high-level review of all objectives, and then do a &quot;deep dive&quot; on just one or two objectives. The evolution of the strategy review meeting was the topic of an &lt;a href=&quot;http://harvardbusinessonline.hbsp.harvard.edu/relay.jhtml?name=itemdetail&amp;id=B0503E&quot; rel=&quot;nofollow&quot;&gt;article&lt;/a&gt; I co-authored in Balanced Scorecard Report back in 2005. Perhaps I&#039;ll be revisiting the topic here soon.

Thanks again for your support.</description>
		<content:encoded><![CDATA[<p>Bob:</p>
<p>Thanks for your comment. While the concept of top-to-bottom vertical themes (TBVT) makes logical sense, in practice it has been a challenge. Cause-and-effect relationships don&#8217;t usually fit a one-to-one sequence leading up the map. A typical objective at the bottom of the map, such as &#8220;Drive a culture of performance and accountability&#8221; is certain to be seen by management as a driver for many objectives in a process perspective above. The use of arrows to denote cause-and-effect relationships becomes a bit of a clutter when there are these one-to-many relationships. In reality, there are very few maps with TBVT, and I hope I&#8217;ll not be using that acronym any more.</p>
<p>Even when themes don&#8217;t necessarily span all perspectives, they are a great way of organizing strategy review meetings, especially for relatively new BSCs. However, leadership teams with mature BSCs often use the first few minutes of the review meeting for a high-level review of all objectives, and then do a &#8220;deep dive&#8221; on just one or two objectives. The evolution of the strategy review meeting was the topic of an <a href="http://harvardbusinessonline.hbsp.harvard.edu/relay.jhtml?name=itemdetail&#038;id=B0503E" rel="nofollow">article</a> I co-authored in Balanced Scorecard Report back in 2005. Perhaps I&#8217;ll be revisiting the topic here soon.</p>
<p>Thanks again for your support.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Frelinger, CGEIT</title>
		<link>http://tenacioustortoise.com/index.php/2009/06/09/vertical-horizontal-strategy/comment-page-1/#comment-22</link>
		<dc:creator>Bob Frelinger, CGEIT</dc:creator>
		<pubDate>Fri, 12 Jun 2009 13:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://tenacioustortoise.com/?p=685#comment-22</guid>
		<description>Great post!  Thanks.  Two concerns.  1.  The idea of verticals, or strategic themes, that do not span the four perspectives seems to undermine the logic behind driving toward the cause-and-effect relationship among the objectives. My experience has been that folks are keen on understanding and being able to visualize how focusing on a certain learning and growth objective, for example, helps deliver on the financial objectives.  They want to see the linkage.  It seems to me that verticals that span all perspectives help visualize this linkage.  2.  Beyond the map itself, Drs. Kaplan and Norton describe Theme Monitoring as a representative activity of a Strategy Review Meeting.  If the strategic theme doesn&#039;t span all perspectives, then might we say that Perspective Monitoring is a better activity for the Strategy Review Meeting?</description>
		<content:encoded><![CDATA[<p>Great post!  Thanks.  Two concerns.  1.  The idea of verticals, or strategic themes, that do not span the four perspectives seems to undermine the logic behind driving toward the cause-and-effect relationship among the objectives. My experience has been that folks are keen on understanding and being able to visualize how focusing on a certain learning and growth objective, for example, helps deliver on the financial objectives.  They want to see the linkage.  It seems to me that verticals that span all perspectives help visualize this linkage.  2.  Beyond the map itself, Drs. Kaplan and Norton describe Theme Monitoring as a representative activity of a Strategy Review Meeting.  If the strategic theme doesn&#8217;t span all perspectives, then might we say that Perspective Monitoring is a better activity for the Strategy Review Meeting?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

