<?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: Found in the Translation</title>
	<atom:link href="http://blog.jthawes.com/2009/07/20/found-in-the-translation/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jthawes.com/2009/07/20/found-in-the-translation/</link>
	<description>Helping Smart People Think Clearly About Strategy</description>
	<lastBuildDate>Fri, 27 May 2011 09:41:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jason Katraouzos</title>
		<link>http://blog.jthawes.com/2009/07/20/found-in-the-translation/comment-page-1/#comment-57</link>
		<dc:creator>Jason Katraouzos</dc:creator>
		<pubDate>Mon, 20 Jul 2009 23:25:06 +0000</pubDate>
		<guid isPermaLink="false">http://tomhawes.wordpress.com/?p=367#comment-57</guid>
		<description>That was a great blog entry Tom and it correlates well with my CI experience. About 5 years ago I started constructing timelines of competitor actions so I could review the entire chain of industry events over time. I now partially use it to gauge competitor culture and make predictions. For instance, how aggressive was Competitor X in the market in the past 3 years, and why hadn&#039;t Competitor Y introduced a new product in 10 years? Looking at timelines helped me see competitor culture to some extent. Competitor X is an aggressive company from New York that likes dominating the market through frequent marketing and product introductions. Competitor Y is a strong risk manager that uses its conservatism to avoid bad risks and survive over the long-term with strong financial strength fueled by other product lines. These insights help determine how aggressive we&#039;re willing to be in directly competing with these companies.

As you mentioned too, knowing the key people who are involved in determining the competitors&#039; business strategy is beneficial. It&#039;s interesting that you can&#039;t easily know that sometimes. Many of the key personnel for my company&#039;s competitors don&#039;t even have a Linkedin account or post much info on the Internet. Industry conferences have helped with that to some extent. Observing the body language and having private conservations with them can be invaluable.

Jason</description>
		<content:encoded><![CDATA[<p>That was a great blog entry Tom and it correlates well with my CI experience. About 5 years ago I started constructing timelines of competitor actions so I could review the entire chain of industry events over time. I now partially use it to gauge competitor culture and make predictions. For instance, how aggressive was Competitor X in the market in the past 3 years, and why hadn&#8217;t Competitor Y introduced a new product in 10 years? Looking at timelines helped me see competitor culture to some extent. Competitor X is an aggressive company from New York that likes dominating the market through frequent marketing and product introductions. Competitor Y is a strong risk manager that uses its conservatism to avoid bad risks and survive over the long-term with strong financial strength fueled by other product lines. These insights help determine how aggressive we&#8217;re willing to be in directly competing with these companies.</p>
<p>As you mentioned too, knowing the key people who are involved in determining the competitors&#8217; business strategy is beneficial. It&#8217;s interesting that you can&#8217;t easily know that sometimes. Many of the key personnel for my company&#8217;s competitors don&#8217;t even have a Linkedin account or post much info on the Internet. Industry conferences have helped with that to some extent. Observing the body language and having private conservations with them can be invaluable.</p>
<p>Jason</p>
]]></content:encoded>
	</item>
</channel>
</rss>

