<?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>Studio Notes - Musings on design matters, technology and culture &#187; Why Design Matters</title>
	<atom:link href="http://danielmckenzie.com/blog/category/design/why-design-matters/feed/" rel="self" type="application/rss+xml" />
	<link>http://danielmckenzie.com/blog</link>
	<description>Musings on design matters, technology and culture.</description>
	<lastBuildDate>Mon, 30 Aug 2010 18:24:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Why Some Startups Fail</title>
		<link>http://danielmckenzie.com/blog/2009/09/why-startups-fail/</link>
		<comments>http://danielmckenzie.com/blog/2009/09/why-startups-fail/#comments</comments>
		<pubDate>Tue, 15 Sep 2009 22:10:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Interaction Design]]></category>
		<category><![CDATA[Product Design]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Why Design Matters]]></category>
		<category><![CDATA[book]]></category>
		<category><![CDATA[Marty Cagan]]></category>
		<category><![CDATA[startup]]></category>

		<guid isPermaLink="false">http://danielmckenzie.com/blog/?p=175</guid>
		<description><![CDATA[I recently finished reading a book by Marty Cagan titled Inspired &#8211; How to Create Products Customer’s Love. For all of you who don’t like to read, this is only 225 pages with pithy chapters of only 3-4 pages in length. In short, the book is a gem and has loads of advice from an [...]]]></description>
			<content:encoded><![CDATA[<p>I recently finished reading a book by Marty Cagan titled <a href="http://www.amazon.com/Inspired-Create-Products-Customers-Love/dp/0981690408/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1253039111&amp;sr=8-1" target="_blank">Inspired &#8211; How to Create Products Customer’s Love</a>. For all of you who don’t like to read, this is only 225 pages with pithy chapters of only 3-4 pages in length. In short, the book is a gem and has loads of advice from an industry veteran. My edition is mostly stained with yellow highlight, but the section that made the biggest impact for me was chapter 28: “Startup Product Management—It’s All About Product Discovery”. It boldly shines light on an engineer-driven industry that too often puts technology before everything else.</p>
<p>Cagan argues that startups work terribly inefficiently in spite of limited funding and time. Not only does this inefficiency cost money and time, it may also cause many startups to never reach it to market!!! According to Cagan, this is why many startups fail. They ”simply don’t have the funding to go to two years before they gain traction in the marketplace. So they hire engineers, take their best shot, and see what happens. Ready, fire, aim.”</p>
<p>Here’s the complete scenario as he describes it:</p>
<p><em>Someone with an idea get some seed funding, and the first thing he does is hire some engineers to start building something. The founder will have definite ideas on what she wants, and she’ll typically act as product manager and often product designer, and the engineering team will then go from there. The companies are typically operating in “stealth mode” so there’s little customer interaction. It takes much longer than originally thought for the engineering team to build something, because the requirements and the design are being figured out on-the-fly.</em></p>
<p><em>After six months or so, engineers have things in sort of an alpha or beta state, and that’s when they first show the product around. This first viewing rarely goes well, and the team starts scrambling. The run rate is high because there’s now an engineering team building this thing as fast as they can, so the money is running out and the product isn’t yet there. Maybe the company gets additional funding and a chance to get the product right, but often it doesn’t. Many startups try to get more time by outsourcing engineering to a low-cost offshore firm, but they’re still left with the same process and the same problems.</em></p>
<p>So as Cagan states, engineers are typically brought into a project at an early stage and they’re running around like chickens with their heads cut off trying to code and test new ideas at the same time. Sometimes weeks of coding are thrown out the window as the company “feels” itself through the unfolding product. For small startups it’s like pouring a house’s foundation and at the same time, deciding where the walls go.</p>
<p>But Marty Cagan isn’t some cranky product manager trying to wreak havoc on the startup community. He continues to describe what a more efficient process might look like:</p>
<p><em>Here’s a very different approach to new product creation, one that costs dramatically less and is much more likely to yield the results you want: the founder hires a product manager, an interaction designer, and a prototyper. Sometimes the designer can also serve as prototyper, and sometimes the founder can serve as a product manager, but one way or another, you have these three functions lined up—product management, interaction design, and prototyping—and the team starts a process of very rapid product discovery.</em></p>
<p>Cagan emphasizes that the focus is on product discovery via a high-fidelity prototype that mimics the desired user experience. But this isn&#8217;t enough—you must validate the product design with real users that fit your target audience. Without testing real users, you’re still in the dark when it comes to understanding how your users may respond to your product or service.</p>
<p>What then continues is a refinement process that includes several versions of the prototype in order to get closer to a winning product. The end result is that you have:</p>
<p><em>(a) identified a product that you have validated with the target market, (b) a very rich prototype that serves as a living spec for the engineering team to build from, and (c) a much greater understanding of what you’re getting into, and what you’ll need to do to succeed.</em></p>
<p>The engineers are then brought on and they’re able to build something based on a clear vision of the product and a stable spec. Not only does this make the engineers’ job much easier, but the company has reduced the risk of shipping a flop and has also saved a lot of time and money on development. The startup is building a successful product “on purpose”.</p>
<p>Cagan finishes his argument by asking:</p>
<p><em>So why don’t all startup teams do this? Because we’re such an engineering-driven industry that we just naturally start there. But any startup has to realize everything starts with the right product, so the first order of business is to figure out what that is before burning through $500K or more in seed funding.</em></p>
<p>&#8230;Definitely something to think about for your next startup.</p>
<img src="http://danielmckenzie.com/blog/?ak_action=api_record_view&id=175&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://danielmckenzie.com/blog/2009/09/why-startups-fail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What Wall Street Could Learn from Good Design</title>
		<link>http://danielmckenzie.com/blog/2008/10/what-wall-street-could-learn-from-good-design/</link>
		<comments>http://danielmckenzie.com/blog/2008/10/what-wall-street-could-learn-from-good-design/#comments</comments>
		<pubDate>Fri, 17 Oct 2008 16:48:23 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Principles]]></category>
		<category><![CDATA[Why Design Matters]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[cooper]]></category>
		<category><![CDATA[design principles]]></category>
		<category><![CDATA[human-centered design]]></category>
		<category><![CDATA[Wall Street]]></category>

		<guid isPermaLink="false">http://danielmckenzie.com/blog/?p=48</guid>
		<description><![CDATA[As the US teeters on the brink of a financial meltdown, I can’t help but to think how often man gets himself in trouble by designing something that doesn’t serve his own interests. Examples of man in conflict with his technological prowess include the creation of nuclear warheads, fossil fuel-run machines, fishing nets that “sweep” [...]]]></description>
			<content:encoded><![CDATA[<p>As the US teeters on the brink of a financial meltdown, I can’t help but to think how often man gets himself in trouble by designing something that doesn’t serve his own interests. Examples of man in conflict with his technological prowess include the creation of <span class="zem_slink">nuclear warheads</span>, fossil fuel-run machines, fishing nets that “sweep” the ocean’s floors and less world-threatening inventions such as chemically altering drugs, credit cards, processed food, and television (to name just a few). All of these were invented by us but in the long run, don’t serve us well.</p>
<p>Our own financial system in <span class="zem_slink">the United States</span> seems to be driven by not only extreme neurotic mood swings that any psychiatrist would deem psychotic, but also in part by newly created complex attributes such as derivatives—highly complex computer-generated financial instruments—which Warren Buffet refers to as “weapons of financial destruction.”</p>
<p>Richard Dooling wrote <a href="http://www.nytimes.com/2008/10/12/opinion/12dooling.html?scp=1&amp;sq=opinion%20and%20wallstreet%20and%20computers&amp;st=cse" target="_blank">in a recent article for the New York Times</a>:</p>
<p>&#8220;Somehow the genius quants—the best and brightest geeks <span class="zem_slink">Wall Street</span> firms could buy—fed $1 trillion in subprime mortgage debt into their supercomputers, added some derivatives, massaged the arrangements with computer algorithms and—poof!—created $62 trillion in imaginary wealth. It’s not much of a stretch to imagine that all of that imaginary wealth is locked up somewhere inside the computers, and that we humans, led by the silverback males of the financial world, <span class="zem_slink">Ben Bernanke</span> and <span class="zem_slink">Henry Paulson</span>, are frantically beseeching the monolith for answers. Or maybe we are lost in space, with Dave the astronaut pleading, ‘Open the bank vault doors, Hal.’&#8221;</p>
<p>Has the system taken over? Our politicians up to now seem to have had a lot of faith in the Market— as in “<em>The Market</em> will correct itself.” What the Market has proven is that, like some other man-made inventions, it’s not necessarily working to our benefit. We have put too much confidence in numbers and computations and somewhere along the road forgot to apply the algorithm for human-ness—as in <em>humans are prone to make errors and are often driven by greed or fear</em>.</p>
<p>From a designer’s point of view, the technologist’s took over and decided to build a bunch of functionality that while very fun to tinker with, doesn’t serve the general good. As <span class="zem_slink">Thomas Friedman</span> says “They were engineering money from money.”</p>
<p>Policy makers could learn a few things from the design community when it comes to creating sound policy and regulations. In recent years, design attitudes have changed putting more attention on customer (human) behavior rather than purely, business goals. Companies are slowly realizing that customers can’t be measured by demographics and spreadsheets alone. The attitude is that good design must <em>serve</em>—when was the last time you felt you had been <em>served</em>?</p>
<p>As a country and global community, we need to start a new paradigm that stems from human-centered design and apply it to everything we do. The environmental movement, still in its infancy, has known this for years.</p>
<p>What’s the point if we’re not designing to better our lives and create a more habitable world? Shouldn’t it be obvious that all design stem from a focus on the well-being of <span class="zem_slink">human beings</span>?</p>
<p>Cooper, an interaction design agency, describes the following principles in their book “About Face”:</p>
<p>&#8220;[Design principles] encourage the design of product behaviors that support the needs and goals of users, and create positive experiences with the products we design”…”At the core of these values is the notion that technology should serve human intelligence and imagination (rather than the opposite), and that people’s experiences with technology should be structured in accordance with their abilities of perception, cognition and movement.&#8221;</p>
<p>Now, imagine that applied to our financial systems? Revolutionary!</p>
<p>We know that there is something fundamentally wrong with any design when it promotes the attributes of fear and greed. We also know something is very wrong when the action made by a few negatively affects the many.</p>
<p>According to Cooper, design solutions that aim to serve the needs of humans are:</p>
<p><strong>Ethical </strong>(considerate, helpful)<strong> </strong><br />
• Do no harm<br />
• Improve human situations</p>
<p><strong>Purposeful</strong> (useful, usable)<br />
• Help users (humans) achieve their goals and aspirations<br />
• Accommodate user contexts and capacities</p>
<p><strong>Pragmatic</strong> (viable, feasible)<br />
• Help commissioning organizations achieve their goals<br />
• Accommodate business and technical requirements</p>
<p><strong>Elegant</strong> (efficient, artful, affective)<br />
• Represent the simplest complete solution<br />
• Appropriately accommodate and stimulate cognition and emotion</p>
<p>Hopefully, the US and the world will learn something from this financial catastrophe that we’re all so intertwined in. There’s a great sense in the US that we need change at many levels—health care, energy, <span class="zem_slink">education</span> and now more than ever, our financial systems. What we need most is to get back to ideas that serve humans and our most noble of characteristics.</p>
<img src="http://danielmckenzie.com/blog/?ak_action=api_record_view&id=48&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://danielmckenzie.com/blog/2008/10/what-wall-street-could-learn-from-good-design/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Why Design Matters</title>
		<link>http://danielmckenzie.com/blog/2008/09/why-design-matters/</link>
		<comments>http://danielmckenzie.com/blog/2008/09/why-design-matters/#comments</comments>
		<pubDate>Tue, 09 Sep 2008 22:59:49 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Why Design Matters]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[strategy]]></category>

		<guid isPermaLink="false">http://danielmckenzie.com/blog/?p=15</guid>
		<description><![CDATA[I just wanted to expand on a topic that began in my newsletter. I hope this is an ongoing conversation because there seems to be a lot of confusion about the value design brings to a business. &#8220;Design&#8221; in many people&#8217;s minds is nothing more than making it &#8220;pretty&#8221; when in fact, this is just [...]]]></description>
			<content:encoded><![CDATA[<p>I just wanted to expand on a topic that began in my newsletter. I hope this is an ongoing conversation because there seems to be a lot of confusion about the value design brings to a business. &#8220;Design&#8221; in many people&#8217;s minds is nothing more than making it &#8220;pretty&#8221; when in fact, this is just one small part of it. Design also encompasses functionality, usability, strategy, brand and-yes-aesthetics (making it pretty). Below are some quotes that might help clarify the confusion.</p>
<blockquote><p>&#8220;Design is not just what it looks like and feels like. Design is how it works.&#8221;  - Steve Jobs</p></blockquote>
<p>In the case of building a website, all parties are working with design: information architects, interactive designers, engineers and business strategists. Everyone is involved in giving the site meaningful order and appeal—design.</p>
<blockquote><p>&#8220;We [designers] provide a process, a managerial discipline with its alternate phases of analysis and creative exploration, which in itself is an invaluable guide to the company&#8217;s strategic future. This process allows management to visualize and test its strategic options. It makes strategies appear real before rollout production decisions are made.&#8221;  - James G. Hansen, Chairman and Co-founder, Source/Inc.</p></blockquote>
<p>So much for designers not playing a meaningful business role in an organization. Designers make it possible for companies to test the waters before going public. In other words, design reduces the risk of danger! Unfortunately, often as a result of impatience and lack of strategic planning, many companies oversee this important step to their product development and wonder later, why their product hasn&#8217;t been received well. Audience studies, competitive analysis, personas, scenarios, user tasks, prototypes and user testing are often seen as gratuitous and ways for designers to make more money from their clients! While it does take more time and money, the result is correcting problems before, not after you&#8217;ve spent a ton of money on layered Photoshop files, HTML development and programming. And everyone knows how difficult it is to change things after the beast has launched.</p>
<blockquote><p>&#8220;Many clients are also surprised to learn that the way the company and its products &#8220;look&#8221; not only influences sales (the consumer), but also, and perhaps even more significant from a strategic point of view, the way in which its own management, sales force, and distributors perceive it.&#8221; - James G. Hansen, Chairman and Co-founder, Source/Inc.</p></blockquote>
<p>Does it really matter how your employees see your products? Remember those ugly black leather shoes your parents used to make you wear to church? Remember those uniforms they made you wear at your first job when you were 16? Remember playing soccer as a youngster and discovering that the other team had better uniforms?</p>
<blockquote><p>&#8220;&#8230;Information only has value when it is successfully communicated. If it cannot be accessed or understood it does not have value.&#8221;  - Dirk Knemeyer, Thread Inc.</p></blockquote>
<p>OK, so you have some great website features that are going to make Facebook and Flickr look like a Cub Scout project. You built your website with feature-centered design and know that users will be crawling all over it once they find out all the cool things it can do to make their lives easier. You launch your site with the expectation &#8220;build it and they will come&#8221;. They come (some of them), the problem is they soon leave. What happened? Nobody &#8220;gets it&#8221;, that&#8217;s what happened. A shift in priorities from feature-centered design to customer-centered design would have saved you a lot of strife. Also, a good dose of user testing and iterative design would have helped. For 1-2 weeks more of work you could&#8217;ve saved yourself a headache. The value of smart design is crucial to the success of not only your project, but in most cases, your business too.</p>
<img src="http://danielmckenzie.com/blog/?ak_action=api_record_view&id=15&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://danielmckenzie.com/blog/2008/09/why-design-matters/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
