<?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>Noodleplay &#187; business strategy</title>
	<atom:link href="http://www.ideacouture.com/blog/tag/business-strategy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ideacouture.com/blog</link>
	<description></description>
	<lastBuildDate>Fri, 27 Jan 2012 16:01:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>&#8220;Elegant&#8221; Is Often Use For High  Design. But What Does It Mean For Engineering, Interface Or Business Models?</title>
		<link>http://www.ideacouture.com/blog/2009/10/19/elegant-is-often-reserved-for-use-in-the-high-design-world-but-what-does-it-mean-for-engineering-interface-or-business-models-what-can-businesses-learn-from-it/</link>
		<comments>http://www.ideacouture.com/blog/2009/10/19/elegant-is-often-reserved-for-use-in-the-high-design-world-but-what-does-it-mean-for-engineering-interface-or-business-models-what-can-businesses-learn-from-it/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 18:40:23 +0000</pubDate>
		<dc:creator>Idris Mootee</dc:creator>
				<category><![CDATA[Art and Culture]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[beauty]]></category>
		<category><![CDATA[Blackberry]]></category>
		<category><![CDATA[business strategy]]></category>
		<category><![CDATA[chanel]]></category>
		<category><![CDATA[complex]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[elegant]]></category>
		<category><![CDATA[hermes]]></category>
		<category><![CDATA[human factor]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[jil sander]]></category>
		<category><![CDATA[kindle]]></category>
		<category><![CDATA[marc jacob]]></category>
		<category><![CDATA[oliver wendell holmes]]></category>
		<category><![CDATA[SAP]]></category>
		<category><![CDATA[user friendly]]></category>
		<category><![CDATA[warren buffet]]></category>

		<guid isPermaLink="false">http://ideacouture.com/blog/?p=3010</guid>
		<description><![CDATA[El·e·gant, an adjective and define or characterized by or exhibiting refined, tasteful beauty of manner, form, or style. Marc Jacob? Chanel? Jil Sander? Hermes? All are unquestionably elegant by design in the fashion world. How about Amazon Kindle? Apple iPhone? Blackberry?  Are they elegant? Is elegant a word reserved solely for design world. That world [...]]]></description>
			<content:encoded><![CDATA[<p>El·e·gant, an adjective and define or characterized by or exhibiting refined, tasteful beauty of manner, form, or style. Marc Jacob? Chanel? Jil Sander? Hermes? All are unquestionably elegant by design in the fashion world. How about Amazon Kindle? Apple iPhone? Blackberry?  Are they elegant? Is elegant a word reserved solely for design world. That world likes to use words such as “elegant”, “simple” and “user friendly”, many designers understand how to subtract in creating simple and elegant design solutions. Human factors usually subtract more than add. Good designers often take away complexity in objects or interfaces. Can business learn from this design principle? Can a business strategy be “elegant”? Or can a particular management style be described as “elegant”?</p>
<p><span style="font-family: Trebuchet MS;"><span style="color: #282223;"><span style="font-size: x-small;"><span style="font-size: 10pt;"><a href="http://ideacouture.com/blog/wp-content/uploads/2009/10/0317-jil-sander-uniqlo-japan.jpg"><img class="aligncenter size-full wp-image-3048" title="0317-jil-sander-uniqlo-japan" src="http://ideacouture.com/blog/wp-content/uploads/2009/10/0317-jil-sander-uniqlo-japan.jpg" alt="0317-jil-sander-uniqlo-japan" width="500" height="346" /></a><br />
</span></span></span></span></p>
<p>Anything elegant is often simple; not everything simple is elegant. Things that are simple are often user friendly, not everything simple is user friendly. Sometimes complexity is needed. Simplicity has different meanings. Good businesses need to be simple and easy to understand, and that’s the investment criteria for Warren Buffet. Businesses are getting too complex these days and most executives, let alone CEOs, know all the moving pieces or have any idea of their risk exposure. And some rely on SAP to manage their enterprise and that’s unrealistic.</p>
<p>There are many different kinds of simplicity, sometimes in form and sometimes in function and sometimes both. Oliver Wendell Holmes Jr. once said, “I wouldn’t give a fig for simplicity on this side of complexity, but I would give my life for simplicity on the other side of complexity.” Elegance is “far side” simplicity that is emotionally engaging, profoundly intelligent, and artfully crafted to be two things at once: simple and powerful. Why elegance? Is it an elusive target? Is it only applicable to design?</p>
<div class="im">
<p>Are there always simple answers to even the most wicked problems? Do we have to reduce complexity so we can understand it or do we need complex solutions to solve complex problems? Scientists, engineers, mathematicians, system thinkers, economists research for theories hoping to explain highly complex phenomena in simple ways.</p>
<p>Business executives and strategists are dealing with more and more complex business models. I don’t think that a simpler solution is necessarily superior than a complex one. If you consider a particular business as a system, the business model corresponds pretty exactly to the function of that system. The business in operation is a combination of architecture, function and performance. As with many complex systems, it can sometimes be difficult to distinguish between the three.</p>
<p><a href="http://ideacouture.com/blog/wp-content/uploads/2009/10/thetopiade21.jpg"><img class="aligncenter size-full wp-image-3054" title="thetopiade21" src="http://ideacouture.com/blog/wp-content/uploads/2009/10/thetopiade21.jpg" alt="thetopiade21" width="500" height="436" /></a></div>
<p>A business model includes the raw function of what we (economist) refer to as its &#8220;industry&#8221; (it&#8217;s a bank or a retail chain or a newspaper, for example), but can also include particular ways of operating the raw function (a branchless bank or low-cost airline, a discount retailer or a free online social network, for example). Thus the business model &#8220;function&#8221; can shade into &#8220;performance&#8221; when particular approaches to types of customer, levels of service and brand ethos are considered. The architectural side of the business model is how the core components are stacked together and that impacts the function as well as the performance. It can be simple and elegant AND it can be complex and elegant.</p>
<div class="im">
<p>Elegant doesn’t have to simple. It is easier to be elegant when things are simple.</p></div>
]]></content:encoded>
			<wfw:commentRss>http://www.ideacouture.com/blog/2009/10/19/elegant-is-often-reserved-for-use-in-the-high-design-world-but-what-does-it-mean-for-engineering-interface-or-business-models-what-can-businesses-learn-from-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What’s your problem-solving pathway? There are N ways to X.</title>
		<link>http://www.ideacouture.com/blog/2009/05/28/what%e2%80%99s-your-problem-solving-pathway-there-are-n-ways-to-x/</link>
		<comments>http://www.ideacouture.com/blog/2009/05/28/what%e2%80%99s-your-problem-solving-pathway-there-are-n-ways-to-x/#comments</comments>
		<pubDate>Thu, 28 May 2009 16:45:32 +0000</pubDate>
		<dc:creator>Cheesan Chew</dc:creator>
				<category><![CDATA[Strategic Innovation]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[business strategy]]></category>
		<category><![CDATA[designers]]></category>
		<category><![CDATA[methods]]></category>
		<category><![CDATA[problem solving]]></category>

		<guid isPermaLink="false">http://ideacouture.com/blog/?p=362</guid>
		<description><![CDATA[How many ways are there to draw a circle? What about building a chair? Or architecting a software application? There are a thousand ways to reach any of these ends. But which one is right? This is likely the reason there often argument and debate between collaborators on choosing a method – the means often [...]]]></description>
			<content:encoded><![CDATA[<p>How many ways are there to draw a circle? What about building a chair? Or architecting a software application? There are a thousand ways to reach any of these ends. But which one is right? This is likely the reason there often argument and debate between collaborators on choosing a method – the means often determines the success of the end.</p>
<p>Problem solving is what business strategists, human factor specialists, designers, engineers do. It is what they are, trained for, or should be, good at. At one time the basic problem solving skills all engineers needed were developed in school. Sadly it is no longer the case. A look at system show us why many students going in to university have had very little basic training in the process of problem solving: the “problems” set tend to be largely single step tests of knowledge of individual principles.  Not many undergraduates today have the confidence and mental structure available to say “I really don&#8217;t know how to solve this problem yet, but if I’m given some time to set about it systematically and logically think about it I think I can work it out”</p>
<p>Let’s take an everyday common example faced by people in all types of organizations – writing business cases. Should you write a case top down or bottom up? The top down approach works as a high level guesstimate of a final value in a case  &#8211; you take some high level numbers, run a back of the envelope calculation and voila, you’ve got about 80% of the answer with about 20% of the effort. The bottom up approach advocates a different tact – meticulously including detailed numbers to build the case from scratch. The optimal approach is really determined by a number of key factors.</p>
<ol>
<li><strong>Do the methods under consideration differ materially in the end result? </strong>Identify these differences up front and eliminate any of those that likely will not provide you with desired results.</li>
<li><strong>Are the methods proven? </strong>Proven methods are not necessarily the best, but do provide comfort and stability.</li>
<li><strong>Are you under time constraints? </strong>Some methods require more time than others. – it obviously takes longer to construct a bottom up approach vs. a top down approach. Choose the method that gets you to the final product on time.</li>
<li><strong>What is your team makeup? </strong>If you’re working with others that have expertise in one method vs. another, it will make your process decision easier.</li>
<li><strong>Who is your audience? </strong>Will you have to explain or follow some pre-determined method? If so, choosing one that is structured and easily comprehensible is an important consideration.</li>
<li><strong>Is there an industry or organizational “accepted” practice to be considered? </strong>An accepted practice is not always the best one to choose, but will often be met with less resistance.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.ideacouture.com/blog/2009/05/28/what%e2%80%99s-your-problem-solving-pathway-there-are-n-ways-to-x/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

