<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Christoffer Soop</title>
	<atom:link href="http://christoffer.soop.ch/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://christoffer.soop.ch/wordpress</link>
	<description>Random Thoughts</description>
	<lastBuildDate>Tue, 22 Feb 2011 20:31:37 +0000</lastBuildDate>
	<language>se</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>What is Strategy?</title>
		<link>http://christoffer.soop.ch/wordpress/2011/02/what-is-strategy/</link>
		<comments>http://christoffer.soop.ch/wordpress/2011/02/what-is-strategy/#comments</comments>
		<pubDate>Tue, 22 Feb 2011 20:30:28 +0000</pubDate>
		<dc:creator>Christoffer Soop</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[mba]]></category>
		<category><![CDATA[patching]]></category>
		<category><![CDATA[rules]]></category>
		<category><![CDATA[strategy]]></category>
		<category><![CDATA[tactic]]></category>

		<guid isPermaLink="false">http://christoffer.soop.ch/wordpress/?p=69</guid>
		<description><![CDATA[<p>As an assignment in the Strategy and Marketing course of my ongoing MBA studies we were required to give our personal view of what strategy is and I thought I should publish the result here. Part of the reading for the assignment included five articles from Harvard Business Review, three by Michel Porter and two by Kathleen Eisenhardt.</p>

<p>The three articles by Porter takes a high level perspective, defining strategy in terms of the nation state, the industry as a whole and strategy at the highest level of the enterprise. Essentially this is a top-down perspective, or perhaps one could call it outside-in. For Porter strategy is about making conscious trade-offs (what not to do), supported by a unique set of activities that reinforce each other and are difficult to reproduce, all in all creating a unique strategic position giving a sustainable competitive advantage (<em>What is Strategy</em>, p 70).</p>

<p>In the two articles by Eisenhardt et al strategy is something emergent, arising from the pattern of activities (patching and the application of simple rules). It is more about the internal strategy process than finding a strategic position. Essentially this is more of a bottoms-up perspective on strategy, or perhaps one could say inside-out.</p>

<p>Porter and Eisenhardt also differ in the time scale of strategy. Strategy in the eyes of Porter is long term; if a strategy does not lead to a sustainable advantage with a high performance outcome, it is not strategy or at least not <em>successful</em> strategy. As a counter point, the two articles by Eisenhardt et al discuss strategy with a shorter horizon (“internet time”).</p>

<p>The two following quotes make the differences particularly evident. In <em>Strategy as Simple Rules </em>(p 116), Eisenhardt says:<p>

<blockquote>Like all effective strategies, strategy as simple rules is about being different. But that difference does not arise from tightly linked activity systems or leveraged core competencies, as in traditional strategies. It arises from focusing on key strategic processes and developing simple rules that shape those processes. When a pattern emerges from the processes-a pattern that creates network effects or economies of scale or scope - the result can be a long-term competitive advantage like the ones Intel and Microsoft achieved for over a decade. More often, the competitive advantage is short term.</blockquote>

<p>This is the exact opposite of what Porter says in <em>What is Strategy </em>(p 75):</p>

<blockquote>Strategy is creating fit among a company's activities. The success of a strategy depends on doing many things well-not just a few- and integrating among them. If there is no fit among activities, there is no distinctive strategy and little sustainability</blockquote>.

<p>Personally I tend to think about strategy in military terms: strategy is about winning the war; tactics however is about winning a battle. To me it seems like Eisenhardt’s patching and simple rules are more about tactics and less about strategies. They tell you how to maneuver in everyday business but they do not tell you much about how competitive advantage can be sustained. For Eisenhardt, sustainable competitive advantage is reached more by accident than deliberate choice. Another way to look at it is that she discusses two strategies in particular, strategies that both serve well in a volatile business environment. By continuously reconfiguring the business to fit the current business environment (patching) and by creating simple rules allows an organization to maneuver with agility in the short term. It does not say anything about what the right direction or what business the company should be in. It is in effect, giving up strategy and focusing only on tactics. In Eisenhardt’s view, this is the right choice since finding a sustainable strategic position is very difficult or even near impossible in todays accelerating business context.</p>

<p>An interesting, and I would say even somewhat damaging fact about <em>Strategy as Simple Rules</em>, is that several of the provided examples that in hindsight really should be considered strategic failures: Enron’s simple rules were certainly not right since it eventually led the company to bankruptcy in 2001; Yahoo though being one of the dot-com stars have not done so great after the dot-com bubble burst and Dell is struggling with the competition that has imitated its business model with an innovative supply and channel management. Dell really is a case in point of Porter’s argument on Operational Efficiency from <em>What is Strategy</em>. Although these examples do not invalidate her argument about the benefit of using simple rules, I believe it does illustrate rules more tactical than strategic nature.</p>

<p>The business impact of a more “Porteresque”, long term view of strategy is really that business should be clear on what business it is in. Trying to do things better or be more nimble is not a sustainable position; in the long term the pack will always catch up. Both Porter and Eisenhardt agree that strategy is about being different (<em>What is Strategy</em>, p 62 and the Eisenhardt quote above). This is something I believe to be almost trivially true: you will not be long term competitive by doing the same thing in the same way as everybody else. Thus a business has to think seriously on what it is doing, how it is doing it, who it is doing it for etc and make sure defends this position vigorously. To close with a another military analogy: a company has to choose its battles wisely.</p>

<p><em>Primary reference sources</em>:</p>

<p>Porter, M. (1996). What is strategy? <em>Harvard Business Review. </em>(November-December) p. 61-78.</p>

<p>Eisenhardt, K &#38; Sull, D. (2001). Strategy as simple rules. <em>Harvard Business Review</em>. (January) p. 106-116.</p>

<p><em>Secondary reference sources</em>:</p>

<p>Porter, M. (2008). The Five Competitive Forces that Shape Strategy. <em>Harvard Business Review</em>. (January) p. 78-93.</p>

<p>Porter, M. (1990). The Competitive Advantage of Nations. <em>Harvard Business Review</em>. (March-April) p. 73-93.</p>


Personally I tend to think about strategy in military terms: strategy is about winning the war; tactics however is about winning a battle. To me it seems like Eisenhardt’s patching and simple rules are more about tactics and less about strategies. They tell you how to maneuver in everyday business but they do not tell you much about how competitive advantage can be sustained. For Eisenhardt, sustainable competitive advantage is reached more by accident than deliberate choice. Another way to look at it is that she discusses two strategies in particular, strategies that both serve well in a volatile business environment. By continuously reconfiguring the business to fit the current business environment (patching) and by creating simple rules allows an organization to maneuver with agility in the short term. It does not say anything about what the right direction or what business the company should be in. It is in effect, giving up strategy and focusing only on tactics. In Eisenhardt’s view, this is the right choice since finding a sustainable strategic position is very difficult or even near impossible in todays accelerating business context.]]></description>
		<wfw:commentRss>http://christoffer.soop.ch/wordpress/2011/02/what-is-strategy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Back up!</title>
		<link>http://christoffer.soop.ch/wordpress/2010/10/back-up/</link>
		<comments>http://christoffer.soop.ch/wordpress/2010/10/back-up/#comments</comments>
		<pubDate>Sun, 03 Oct 2010 21:03:30 +0000</pubDate>
		<dc:creator>Christoffer Soop</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://christoffer.soop.ch/wordpress/?p=62</guid>
		<description><![CDATA[The blog has been down for a long time but is now on-line again!]]></description>
		<wfw:commentRss>http://christoffer.soop.ch/wordpress/2010/10/back-up/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Diaspora Seeds</title>
		<link>http://christoffer.soop.ch/wordpress/2010/05/diaspora-seeds/</link>
		<comments>http://christoffer.soop.ch/wordpress/2010/05/diaspora-seeds/#comments</comments>
		<pubDate>Mon, 17 May 2010 15:17:14 +0000</pubDate>
		<dc:creator>Christoffer Soop</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[social network]]></category>

		<guid isPermaLink="false">http://christoffer.soop.ch/wordpress/en/?p=60</guid>
		<description><![CDATA[Recently a couple of New York college students made a stir when they announced that they would write an open source and distributed social network server as an alternative to Facebook. This is really in the true spirit of the internet, where everyone can set up his or her own server and have them commicate, [...]]]></description>
		<wfw:commentRss>http://christoffer.soop.ch/wordpress/2010/05/diaspora-seeds/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Toyota and Waterfall methdology for developing software</title>
		<link>http://christoffer.soop.ch/wordpress/2010/03/toyota-and-waterfall-methdology-for-developing-software/</link>
		<comments>http://christoffer.soop.ch/wordpress/2010/03/toyota-and-waterfall-methdology-for-developing-software/#comments</comments>
		<pubDate>Wed, 17 Mar 2010 07:57:55 +0000</pubDate>
		<dc:creator>Christoffer Soop</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Toyota]]></category>

		<guid isPermaLink="false">http://christoffer.soop.ch/wordpress/en/?p=51</guid>
		<description><![CDATA[As you may know Agile software development is inspired by the principles of Lean Manufacturing which in turn is derived from the Toyota Production System (TPS). One Agile methodology, Lean Software Development even borrows the name Lean to make the connection explicit. Since the principles in Lean and TPS have much in common with how [...]]]></description>
		<wfw:commentRss>http://christoffer.soop.ch/wordpress/2010/03/toyota-and-waterfall-methdology-for-developing-software/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>REST for Scott</title>
		<link>http://christoffer.soop.ch/wordpress/2009/11/rest-for-scott/</link>
		<comments>http://christoffer.soop.ch/wordpress/2009/11/rest-for-scott/#comments</comments>
		<pubDate>Sat, 28 Nov 2009 07:07:22 +0000</pubDate>
		<dc:creator>Christoffer Soop</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[REST]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://christoffer.soop.ch/wordpress/en/?p=36</guid>
		<description><![CDATA[At the thanksgiving dinner of a friend from work I tried to explain REST-ful applications &#8211; and I think I failed miserably. Even though there are plenty of good introductions out there I felt I needed to organize my thoughts a bit. Having some spare time on the train on the way home I made [...]]]></description>
		<wfw:commentRss>http://christoffer.soop.ch/wordpress/2009/11/rest-for-scott/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SOA is Dead (but the corpse is still kicking)</title>
		<link>http://christoffer.soop.ch/wordpress/2009/04/soa-is-dead-but-the-corpse-is-still-kicking/</link>
		<comments>http://christoffer.soop.ch/wordpress/2009/04/soa-is-dead-but-the-corpse-is-still-kicking/#comments</comments>
		<pubDate>Thu, 23 Apr 2009 10:03:06 +0000</pubDate>
		<dc:creator>Christoffer Soop</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[REST]]></category>
		<category><![CDATA[SOA]]></category>
		<category><![CDATA[WOA]]></category>

		<guid isPermaLink="false">http://christoffer.soop.se/wordpress/?p=32&#038;lang=en</guid>
		<description><![CDATA[In a famous post from january this year (which I missed) Ann Thomas Manes declares SOA dead. She is a Reasearch Director within the Burton Group, has worked with SOA in the Burton Group and elsewhere, and is a co-author of the WS-* specifications.

 

The post has sparked fierce defence from vendors like Oracle. During the half day SOA Architect forum this Tuesday, Oracle spent the first seminar repeating that “SOA is not dead” many times to reinforce the message. It seemed to be one of the mayor points they wanted to get across.]]></description>
		<wfw:commentRss>http://christoffer.soop.ch/wordpress/2009/04/soa-is-dead-but-the-corpse-is-still-kicking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Universal Assembly Cache &#8211; Dependency Management for Mono and Microsoft.NET</title>
		<link>http://christoffer.soop.ch/wordpress/2009/02/distributed-gac-dependency-management-for-mono-and-microsoftnet/</link>
		<comments>http://christoffer.soop.ch/wordpress/2009/02/distributed-gac-dependency-management-for-mono-and-microsoftnet/#comments</comments>
		<pubDate>Tue, 24 Feb 2009 12:40:16 +0000</pubDate>
		<dc:creator>Christoffer Soop</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[Build]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[Tool]]></category>

		<guid isPermaLink="false">http://christoffer.soop.se/wordpress/?p=31&#038;lang=en</guid>
		<description><![CDATA[In the Java world there are several ways of handling dependencies between project components in a shared development environment. Maven is a generic build tool that creates a standardized way of creating, building and publishing component artifacts. Dependencies between the different components are declared in a Maven build file and Maven automatically downloads the dependencies [...]]]></description>
		<wfw:commentRss>http://christoffer.soop.ch/wordpress/2009/02/distributed-gac-dependency-management-for-mono-and-microsoftnet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Self programming language</title>
		<link>http://christoffer.soop.ch/wordpress/2008/10/self-programming-language/</link>
		<comments>http://christoffer.soop.ch/wordpress/2008/10/self-programming-language/#comments</comments>
		<pubDate>Wed, 01 Oct 2008 19:34:17 +0000</pubDate>
		<dc:creator>Christoffer Soop</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[oop]]></category>
		<category><![CDATA[programming]]></category>

		<guid isPermaLink="false">http://christoffer.soop.se/wordpress/?p=30&#038;lang=en</guid>
		<description><![CDATA[A while ago I reflected on Object Oriented Programming and the fact that it really is more about classes than objects. Reading up on Newspeak, the new langugage proposed by Gilad Bracha I came across Self, one of the language on which Newspeak is indebted to. In Self no classes exists, only objects. More on [...]]]></description>
		<wfw:commentRss>http://christoffer.soop.ch/wordpress/2008/10/self-programming-language/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Crystal Clear &#8211; by Alistair Cockburn</title>
		<link>http://christoffer.soop.ch/wordpress/2008/04/crystal-clear-by-alistair-cockburn/</link>
		<comments>http://christoffer.soop.ch/wordpress/2008/04/crystal-clear-by-alistair-cockburn/#comments</comments>
		<pubDate>Wed, 09 Apr 2008 21:18:29 +0000</pubDate>
		<dc:creator>Christoffer Soop</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Method]]></category>

		<guid isPermaLink="false">http://christoffer.soop.se/wordpress/?p=26</guid>
		<description><![CDATA[True to this the book’s reading instructions call readers experienced in Agile development methods to read the last chapter first and then (after they stop smirking) go back to read certain key chapters. Knowing something about Scrum and XP this is exactly what I did, including the smirking part…]]></description>
		<wfw:commentRss>http://christoffer.soop.ch/wordpress/2008/04/crystal-clear-by-alistair-cockburn/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beyond Software Architecture &#8211; Creating and Sustaining Winning Solutions &#8211; by Luke Hohmann</title>
		<link>http://christoffer.soop.ch/wordpress/2008/03/beyond-software-architecture-creating-and-sustaining-winning-solutions-by-luke-hohmann/</link>
		<comments>http://christoffer.soop.ch/wordpress/2008/03/beyond-software-architecture-creating-and-sustaining-winning-solutions-by-luke-hohmann/#comments</comments>
		<pubDate>Sun, 23 Mar 2008 23:17:23 +0000</pubDate>
		<dc:creator>Christoffer Soop</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Business]]></category>
		<category><![CDATA[Development]]></category>

		<guid isPermaLink="false">http://christoffer.soop.se/wordpress/?p=24</guid>
		<description><![CDATA[In Beyond Software Architecture, Luke Hohmann addresses all things paramount to software product development that are usually not covered in books on software development. These things include licensing, software protection, branding, marketing and business plans and how they relate to the technical architecture and more. Every developer or architect that has been around a few projects probably will probably recognize the importance of some, if not all of these areas, in relation to creating and sustaining a winning solution.

The first and probably most important topic covered is the relation between the business model and the technical architecture. It is really an understatement to claim that the chosen business model has a serious and real impact on the technical architecture – it should be self evident that there the architecture will look quite different in an ASP scenario and a single user desktop application… Less self evident is the relation between the business plan and the technical architecture. What business segments are being targeted and in which order really does bear on the architecture. Each business segment will have its particular needs to be addressed as features in the software solution. The order is important since it will help spell out the technical roadmap for future releases.

The book covers a large number of topics and gives advice on a number of specific issues, too many to cover here. I have chosen but a few that have stuck after finishing the book.]]></description>
		<wfw:commentRss>http://christoffer.soop.ch/wordpress/2008/03/beyond-software-architecture-creating-and-sustaining-winning-solutions-by-luke-hohmann/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

