<?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>Business901</title>
	<atom:link href="http://www.business901.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.business901.com</link>
	<description>Lean your Marketing</description>
	<lastBuildDate>Fri, 19 Mar 2010 02:34:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Sustaining Lean in Manufacturing</title>
		<link>http://www.business901.com/blog1/sustaining-lean-in-manufacturing/</link>
		<comments>http://www.business901.com/blog1/sustaining-lean-in-manufacturing/#comments</comments>
		<pubDate>Thu, 18 Mar 2010 15:10:00 +0000</pubDate>
		<dc:creator>business901</dc:creator>
				<category><![CDATA[Lean Six Sigma]]></category>
		<category><![CDATA[Manufacturers]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[lean manufacturing]]></category>
		<category><![CDATA[Manufacturer]]></category>
		<category><![CDATA[Standard Work]]></category>

		<guid isPermaLink="false">http://www.business901.com/blog1/sustaining-lean-in-manufacturing/</guid>
		<description><![CDATA[Lonnie Wilson, the owner and principal of Quality Consultants is an expert in Lean Manufacturing techniques and applications. He not only instructs management professionals in the applications of these lean techniques; he is an on-the-floor-implementation professional. His new book, How To Implement Lean Manufacturing, was released by McGraw Hill, August 2009.
Listen to answers like this [...]]]></description>
			<content:encoded><![CDATA[<p>Lonnie Wilson, the owner and principal of <a href="http://www.qc-ep.com/">Quality Consultants</a> is an expert in Lean Manufacturing techniques and applications. He not only instructs management professionals in the applications of these lean techniques; he is an on-the-floor-implementation professional. His new book, <a href="http://www.amazon.com/gp/product/0071625070?ie=UTF8&amp;tag=business901-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0071625070">How To Implement Lean Manufacturing</a><img src="http://www.assoc-amazon.com/e/ir?t=business901-20&amp;l=as2&amp;o=1&amp;a=0071625070" border="0" alt="" width="1" height="1" />, was released by <a href="http://www.mhprofessional.com/product.php?search_crawl=true&amp;isbn=0071625070">McGraw Hill, August 2009</a>.</p>
<p>Listen to answers like this in part 1 of 2 of the podcast;</p>
<blockquote><p><strong>Joe</strong>:  What makes sustaining them so difficult for people? You put a process in, this is what we are going to do from now on. What makes that tough?</p></blockquote>
<blockquote><p><strong>Lonnie:</strong> I get asked that question frequently. It seems to be almost obvious that people would say &#8220;Well, OK, we made this gain, now let&#8217;s sustain it.&#8221; It&#8217;s a whole lot better to build on progress than deterioration. The truth of the matter is that people in real life, people have tremendous, tremendous problems sustaining the gains. I think the single, biggest thing that I can put my finger on is the business&#8217; attitude towards problems. I find, particularly in the West, and I don&#8217;t like to make a Japanese/Western dichotomy, but at some level there is.</p>
<p><a href="http://www.business901.com/wp-content/uploads/2010/03/LWPicture.jpg"><img style="margin: 5px; display: inline; border: 0pt none;" title="Lonnie Wilson       " src="http://www.business901.com/wp-content/uploads/2010/03/LWPicture_thumb.jpg" border="0" alt="Lonnie Wilson       " width="175" height="194" align="left" /></a> I find, in the West, that we look at problems as a royal pain in the &#8220;tush.&#8221; We don&#8217;t want them. The fewer problems we have, the happier we are. Some of my Japanese clients, when they find a problem they almost celebrate it. They recognize they found a weakness in the system. The system is, therefore, deficient and now we have got a way to improve it.</p>
<p>They look at problems as opportunities to make their system better, and I think that carries over into then, how they finish up those problems. Once you have solved the problem: To sustain it, there&#8217;s a whole series of activities you need to do. You need to maintain it. You need to standardize it. All of that is just good old fashioned hard work.</p>
<p>To me, that is the most fundamental thing that I find that makes people, makes companies, shy away from sustaining issues, is first, how they view the problem. I think the second thing is that once a problem gets fixed, it&#8217;s very easy to jump to the next problem, because you don&#8217;t have any more symptoms.</p>
<p>What happens is you take on the next problem. Everybody&#8217;s interested in progress, so they want to make more and more progress. They forget that the last thing they fixed maybe isn&#8217;t fixed completely. It&#8217;s fixed enough so they don&#8217;t have any current symptoms, but it&#8217;s going to reappear at a later date. That discipline that it takes to think through the possible future problems, put fixes in place for things that haven&#8217;t even gone wrong; anticipate what might happen. That just isn&#8217;t quite as sexy as moving onto the next problem and solving it.</p>
<p>The third thing that I find that really prevents sustainability, is our system of goals and objectives. You&#8217;ll very often find out that companies have all kinds of production and financial goals and profits, and those are far more important than quality goals. One quality goal we implemented in one place that was particularly progressive, was the goal of zero for things we really didn&#8217;t do that well.</p>
<p>They made a list of the problems that reappeared and put them on the list of &#8220;things we didn&#8217;t do really well.&#8221; Then they made that a highlighted issue within the company. That company was the very best of any that I&#8217;ve ever worked at in my 40 years at sustaining the gains.</p></blockquote>
<div><object id="mp3playerdarksmallv3" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="210" height="25" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="align" value="middle" /><param name="allowScriptAccess" value="sameDomain" /><param name="quality" value="high" /><param name="bgcolor" value="#ffffff" /><param name="wmode" value="transparent" /><param name="src" value="http://www.podbean.com/podcast-audio-video-blog-player/mp3playerdarksmallv3.swf?audioPath=http://business901.podbean.com/mf/play/zt59p3/ImplementingLeanPart1of2.mp3&amp;autoStart=no" /><param name="name" value="mp3playerdarksmallv3" /><embed id="mp3playerdarksmallv3" type="application/x-shockwave-flash" width="210" height="25" src="http://www.podbean.com/podcast-audio-video-blog-player/mp3playerdarksmallv3.swf?audioPath=http://business901.podbean.com/mf/play/zt59p3/ImplementingLeanPart1of2.mp3&amp;autoStart=no" name="mp3playerdarksmallv3" wmode="transparent" bgcolor="#ffffff" quality="high" allowscriptaccess="sameDomain" align="middle"></embed></object><br />
<a style="border-bottom-style: none; padding-left: 41px; font-family: arial, helvetica, sans-serif; color: #2da274; font-size: 11px; font-weight: normal; text-decoration: none;" href="http://www.podbean.com">Powered by Podbean.com</a></div>
<p>.Part 2 of the Podcast: <a href="http://www.business901.com/blog1/implementing-lean/">Implementing Lean </a></p>
<div id="scid:0767317B-992E-4b12-91E0-4F059A8CECA8:e1224201-92c1-49ae-8957-0300f25379b0" class="wlWriterEditableSmartContent" style="margin: 0px; display: inline; float: none; padding: 0px;">Technorati Tags: <a rel="tag" href="http://technorati.com/tags/Lean">Lean</a>,<a rel="tag" href="http://technorati.com/tags/Lean+manufacturing">Lean manufacturing</a>,<a rel="tag" href="http://technorati.com/tags/Standard+Work">Standard Work</a>,<a rel="tag" href="http://technorati.com/tags/Manufacturer">Manufacturer</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.business901.com/blog1/sustaining-lean-in-manufacturing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Work in Process is Wasteful even in Sales and Marketing</title>
		<link>http://www.business901.com/blog1/work-in-process-is-wasteful-even-in-sales-and-marketing/</link>
		<comments>http://www.business901.com/blog1/work-in-process-is-wasteful-even-in-sales-and-marketing/#comments</comments>
		<pubDate>Wed, 17 Mar 2010 17:19:29 +0000</pubDate>
		<dc:creator>business901</dc:creator>
				<category><![CDATA[Agile Marketing]]></category>
		<category><![CDATA[Kanban]]></category>
		<category><![CDATA[Marketing Funnel]]></category>
		<category><![CDATA[Inventory]]></category>
		<category><![CDATA[JIT]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Prospects]]></category>
		<category><![CDATA[Sales Cycle]]></category>
		<category><![CDATA[Work in Process]]></category>

		<guid isPermaLink="false">http://www.business901.com/blog1/work-in-process-is-wasteful-even-in-sales-and-marketing/</guid>
		<description><![CDATA[One of the tenants I am convinced of is that Work in Process is wasteful and unproductive. If you look at this from a Sales and Marketing Process it basically says that the more people you have in your sales and marketing funnel the more unproductive you are. A blog recently by Jim Benson of [...]]]></description>
			<content:encoded><![CDATA[<p>One of the tenants I am convinced of is that Work in Process is wasteful and unproductive. If you look at this from a Sales and Marketing Process it basically says that the more people you have in your sales and marketing funnel the more unproductive you are. A blog recently by Jim Benson of Personal Kanban said this (and more) in a recent post <a href="http://personalkanban.com/primers/inventory-makes-work/">Inventory makes Work</a>:<a href="http://www.business901.com/wp-content/uploads/2010/03/Prospect.jpg"><img style="margin: 5px 0px; display: inline; border-width: 0px;" title="Prospects" src="http://www.business901.com/wp-content/uploads/2010/03/Prospect_thumb.jpg" border="0" alt="Prospects" width="214" height="240" align="right" /></a></p>
<blockquote><p>Inventory lowers organizational effectiveness because the time and money spent taking care of the inventory could have been spent making the company more successful. Therefore, Lean organizations tend to receive the things they need to operate at the last responsible moment, this is called “Just in Time” (JIT). A JIT organization does not take on inventory until the moment they need it and therefore spends as little as possible maintaining inventory, greatly reducing the risk of having overstock.</p>
<p>But inventory isn’t just “stuff.” Inventory for us as individuals includes anything we have that requires maintenance or on-going attention. We have responsibilities, they aren’t going away. We will have a yard, it will need to be mowed. Dishes need to be washed. Children need to be raised.</p></blockquote>
<p>Inventory for sales and marketing is prospects! As you think about what stops your marketing from being effective it is all about trying to appeal to the masses and as a result losing effectiveness both in time and money. As Jim said above, you should be taking the time making your company more successful and working on ineffective or wasteful leads is not going to do it.</p>
<p>The past several years the buzz word has been Inbound Marketing. Though I am a advocate of the basic approach and an advocate of using Social Media I have found that it really has resulted in a failed marketing strategy for many companies. Though it has increased the number of prospects it has done little to increase qualified buyers. That is why there has been push back from many organizations. It just has not been effective as the principle seems to indicate. Just because we automated the process does not mean we are managing <strong>Work in Process</strong> better.</p>
<p>So what happens if we limit work in process or the numbers of leads that we receive? Marketing to a targeted audience results in a cost savings and time savings. Would you need to hire more salespeople? Would you be able to use more experienced people at the right time and in the right place more often? Would you nurture and promote to a better qualified prospect? I believe the most important part of limiting Work in Process is that your message would simply be better. Not only would your information packet be much more targeted and information rich, it would also have a better chance to be delivered on time or in other words when a prospect is ready for it. Giving a prospect what he needs, when he needs it and how he wants it is a pretty important factor in today’s market. If you look at what vehicles prospects and your customers use to acquire the information they need, you will notice one important factor: they are just about all different. Multiplying that number by the number of prospects should certainly give you reason to start narrowing your field.</p>
<p>Why is now, the best time to convert to this strategy? The market itself has caused a constriction for most companies. This constriction has narrowed your market that should enable you to readily identify your target market. What are the last minute adjustments or concessions you make (JIT) to capture the sale? These are the present value drivers of your business. Are these the value drivers that you are willing to live with in the long term? How do they help you in identifying your present and future market?</p>
<p>Work in process is wasteful. It is wasteful in your personal life when not managed well, it is bad in manufacturing, it is bad from a sales and marketing perspective. Quit marketing at the top of your funnel. Instead learn how to manage your <strong>Work in Process</strong>!</p>
<p>P.S. By the way, I don’t even believe in a marketing funnel anymore. I will tell you more about that later!</p>
<p>Related Posts:</p>
<p><a href="http://business901.com/blog1/improve-throughput-cut-your-customers-in-half/">Improve  throughput, cut your customers in half!</a></p>
<p><a href="http://business901.com/blog1/lean-your-marketing-thru-segmentation/">Lean  your Marketing thru Segmentation</a></p>
<div id="scid:0767317B-992E-4b12-91E0-4F059A8CECA8:db8a139d-6ccd-4910-949a-989f6cfc453a" class="wlWriterEditableSmartContent" style="margin: 0px; display: inline; float: none; padding: 0px;">Technorati Tags: <a rel="tag" href="http://technorati.com/tags/Lean">Lean</a>,<a rel="tag" href="http://technorati.com/tags/Sales+Cycle">Sales Cycle</a>,<a rel="tag" href="http://technorati.com/tags/Marketing+Funnel">Marketing Funnel</a>,<a rel="tag" href="http://technorati.com/tags/Work+in+Process">Work in Process</a>,<a rel="tag" href="http://technorati.com/tags/JIT">JIT</a>,<a rel="tag" href="http://technorati.com/tags/Inventory">Inventory</a>,<a rel="tag" href="http://technorati.com/tags/Prospects">Prospects</a>,<a rel="tag" href="http://technorati.com/tags/Kanban">Kanban</a>,<a rel="tag" href="http://technorati.com/tags/Agile+Marketing">Agile Marketing</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.business901.com/blog1/work-in-process-is-wasteful-even-in-sales-and-marketing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Digging deeper with User Stories</title>
		<link>http://www.business901.com/blog1/digging-deeper-with-user-stories/</link>
		<comments>http://www.business901.com/blog1/digging-deeper-with-user-stories/#comments</comments>
		<pubDate>Wed, 17 Mar 2010 02:38:54 +0000</pubDate>
		<dc:creator>business901</dc:creator>
				<category><![CDATA[Agile Marketing]]></category>
		<category><![CDATA[Lean Six Sigma]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Invest]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[Stories]]></category>
		<category><![CDATA[User Story]]></category>

		<guid isPermaLink="false">http://www.business901.com/blog1/digging-deeper-with-user-stories/</guid>
		<description><![CDATA[The INVEST acronym from the User Stories Applied: For Agile Software Development book by Mike Cohn I think serves as a good guideline for defining User Stories. The following is from Doug Seven’s take on INVEST. INVEST stands for Independent, Negotiable, Valuable, Estimatable, Small and Testable.

Independent: The story should not carry with it dependencies, which [...]]]></description>
			<content:encoded><![CDATA[<p>The INVEST acronym from the <a href="http://www.amazon.com/gp/product/0321205685?ie=UTF8&amp;tag=business901-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0321205685">User Stories Applied: For Agile Software Development</a><img style="border-bottom-style: none !important; border-right-style: none !important; margin: 0px; border-top-style: none !important; border-left-style: none !important" border="0" alt="" src="http://www.assoc-amazon.com/e/ir?t=business901-20&amp;l=as2&amp;o=1&amp;a=0321205685" width="1" height="1" /> book by Mike Cohn I<a href="http://www.business901.com/wp-content/uploads/2010/03/Storybook.jpg"><img style="border-bottom: 0px; border-left: 0px; margin: 5px; display: inline; border-top: 0px; border-right: 0px" title="Storybook" border="0" alt="Storybook" align="right" src="http://www.business901.com/wp-content/uploads/2010/03/Storybook_thumb.jpg" width="160" height="107" /></a> think serves as a good guideline for defining User Stories. The following is from <a href="http://blogs.msdn.com/dseven/archive/2006/10/10/Writing-Stories-for-Scrum.aspx">Doug Seven</a>’s take on INVEST. INVEST stands for Independent, <i>Negotiable</i>, <i>Valuable</i>, <i>Estimatable</i>, <i>Small</i> and <i>Testable</i>.</p>
<ul>
<li><b><u>Independent: </u></b>The story should not carry with it dependencies, which can lead to estimating problems. Instead the story should be completely independent so that it can be worked on without pulling in a set of other stories. </li>
<li><b><u>Negotiable: </u></b>Stories should have room to negotiate – they are a starting point, not a contract. </li>
<li><b><u>Valuable: </u></b>The story should communicate the value to a user or customer, not to the developer. The story should define not only what a user can do, but what value the user gets from the implemented story. If there is no value, cut the story. </li>
<li><b><u>Estimateable: </u></b>You need to be able to estimate the amount of work required to implement the story. If it is too big and too daunting (an epic), break it up into smaller stories. </li>
<li><b><u>Small: </u></b>Similar to the previous, stories need to be small. Large stories are too complex to manage, and are typically more than one story compounded together. </li>
<li><b><u>Testable: </u></b>The implementation of the story needs to be testable. Define the tests that can be performed to validate the story was correctly implemented. </li>
</ul>
<p>From a marketing perspective, you could develop user stories for many of your projects. For an example, consider developing a direct mail piece for a home roofing contractor: Using the standard outline for developing a user story: “As a [end user role], I want [the desire] so that [the rationale]. The user story may go something like this: As a roofing contractor, I would like to develop a 4-part mailing program targeting subdivisions of 20 to 24 year old homes.</p>
<ul>
<li>Using INVEST, I could look at this user story and conclude: </li>
<li>Independent: Yes it is very independent. </li>
<li>Negotiable: I think it is negotiable from the standpoint that you might be able to yse a 3 or 5 part or make some recommendations after initial testing. </li>
<li>Valuable: I think presently it is rather weak in that area. </li>
<li>Estimable: Time frames are very easily estimated. </li>
<li>Small: The actual story is very small and well-defined. </li>
<li>Testable: I think like most direct mail pieces, unless under a time constraint sample pieces could be sent and feedback given as additional pieces are developed and modified from the feedback. </li>
</ul>
<p>Though this is a very easy initial user story, it still could be broken down into a variety of story points to put in the backlog, However, I think user stories for marketing should even go a step further. Using this example, they really should be re-directed so that they are written from the home owner’s perspective (the end user). </p>
<p>What could we create using our standard outline: “As a [end user role], I want [the desire] so that [the rationale]. As a homeowner, I would like information on the telltale signs that my roof needs inspected. </p>
<p>With this approach, you can see not only the need for supplying relevant content that is of value to the consumer but this story will strengthen your marketing. As you develop the piece, you may even find more content and/or a more targeted message. </p>
<p>P.S. Notice that I did not say replaced but inspected. </p>
<p><strong>Related Post:</strong></p>
<p><a href="http://www.business901.com/blog1/using-stories-to-explain-your-marketing-efforts/">Using Stories to explain your Marketing Efforts </a></p>
<p><a href="http://business901.com/blog1/start-your-marketing-with-a-user-story/">Start your Marketing with a User Story </a></p>
<div style="padding-bottom: 0px; margin: 0px; padding-left: 0px; padding-right: 0px; display: inline; float: none; padding-top: 0px" id="scid:0767317B-992E-4b12-91E0-4F059A8CECA8:0b90dae0-53ec-4849-a9ba-a91b2ddefbbc" class="wlWriterEditableSmartContent">Technorati Tags: <a href="http://technorati.com/tags/Stories" rel="tag">Stories</a>,<a href="http://technorati.com/tags/Agile" rel="tag">Agile</a>,<a href="http://technorati.com/tags/Marketing" rel="tag">Marketing</a>,<a href="http://technorati.com/tags/User+Story" rel="tag">User Story</a>,<a href="http://technorati.com/tags/Invest" rel="tag">Invest</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.business901.com/blog1/digging-deeper-with-user-stories/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Implementing Lean</title>
		<link>http://www.business901.com/blog1/implementing-lean/</link>
		<comments>http://www.business901.com/blog1/implementing-lean/#comments</comments>
		<pubDate>Tue, 16 Mar 2010 02:04:00 +0000</pubDate>
		<dc:creator>business901</dc:creator>
				<category><![CDATA[Kaizen]]></category>
		<category><![CDATA[Lean Six Sigma]]></category>
		<category><![CDATA[Manufacturers]]></category>
		<category><![CDATA[implementing lean]]></category>
		<category><![CDATA[lean manufacturing]]></category>
		<category><![CDATA[Lean Transformation]]></category>
		<category><![CDATA[Problem Solving]]></category>
		<category><![CDATA[Standard Work]]></category>

		<guid isPermaLink="false">http://www.business901.com/blog1/implementing-lean/</guid>
		<description><![CDATA[Lonnie Wilson, the owner and principal of Quality Consultants is an expert in Lean Manufacturing techniques and applications. He not only instructs management professionals in the applications of these lean techniques; he is an on-the-floor-implementation professional. His new book, How To Implement Lean Manufacturing, was released by McGraw Hill, August 2009. 
He is well versed [...]]]></description>
			<content:encoded><![CDATA[<p>Lonnie Wilson, the owner and principal of Quality Consultants is an expert in Lean Manufacturing techniques and applications. He not only instructs management professionals in the applications of these lean techniques; he is an on-the-floor-implementation professional. His new book, <a href="http://www.amazon.com/gp/product/0071625070?ie=UTF8&amp;tag=business901-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0071625070">How To Implement Lean Manufacturing</a><img style="margin: 0px; border-style: none !important;" src="http://www.assoc-amazon.com/e/ir?t=business901-20&amp;l=as2&amp;o=1&amp;a=0071625070" border="0" alt="" width="1" height="1" />, was released by <a href="http://www.mhprofessional.com/product.php?search_crawl=true&amp;isbn=0071625070">McGraw Hill, August 2009</a>. <a href="http://www.business901.com/wp-content/uploads/2010/03/Wilson.jpg"><img style="margin: 5px; display: inline; border-width: 0px;" title="Lean Manufacturing" src="http://www.business901.com/wp-content/uploads/2010/03/Wilson_thumb.jpg" border="0" alt="Lean Manufacturing" width="160" height="201" align="right" /></a></p>
<p>He is well versed in problem solving skills. He is an expert in statistical problem solving as well as logical techniques such as Kepner-Tregoe methodology. He is a Certified Six Sigma Master Black Belt and he not only utilizes the Six Sigma tools but he is an active Six Sigma trainer. He is very comfortable in the classroom and even more so on the factory floor. He is equally adept at working with top management as well as the line worker. He is an aggressive problem solver and with his 39 years in industry, Mr. Wilson has developed the ability to reduce complex problems to simple workable solutions.</p>
<p>In addition to his work in Six Sigma and Lean Manufacturing, Mr. Wilson has developed and taught classes in a wide variety of topics including many statistical tools such as DOE, SPC MSA, QFD and human relations skills such as Advanced Facilitation, Hoshin-Kanri Policy Deployment and Team Based Problem Solving, to name a few.</p>
<p>This is actually part 2 of 2 of the podcast I had with Lonnie. I found his description of Standard Work, Audits, Quality and Leaderships of such value that I wanted to publish this episode first. So, don’t be surprised that I jump right into the conversation on Standard Work after the introduction.</p>
<div><object id="mp3playerdarksmallv3" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="210" height="25" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="align" value="middle" /><param name="allowScriptAccess" value="sameDomain" /><param name="quality" value="high" /><param name="bgcolor" value="#ffffff" /><param name="wmode" value="transparent" /><param name="src" value="http://www.podbean.com/podcast-audio-video-blog-player/mp3playerdarksmallv3.swf?audioPath=http://business901.podbean.com/mf/play/hsjyd5/ImplementingLeanPart2of2.mp3&amp;autoStart=no" /><param name="name" value="mp3playerdarksmallv3" /><embed id="mp3playerdarksmallv3" type="application/x-shockwave-flash" width="210" height="25" src="http://www.podbean.com/podcast-audio-video-blog-player/mp3playerdarksmallv3.swf?audioPath=http://business901.podbean.com/mf/play/hsjyd5/ImplementingLeanPart2of2.mp3&amp;autoStart=no" name="mp3playerdarksmallv3" wmode="transparent" bgcolor="#ffffff" quality="high" allowscriptaccess="sameDomain" align="middle"></embed></object></p>
<p><a style="font-family: arial, helvetica, sans-serif; font-size: 11px; font-weight: normal; padding-left: 41px; color: #2da274; text-decoration: none; border-bottom: none;" href="http://www.podbean.com">Powered by Podbean.com</a></div>
<p>Related Posts: I found it very interesting how some of Lonnie’s thoughts so closely reminded me of my podcast with Michael Balle.</p>
<p><a href="http://www.business901.com/blog1/developing-a-kaizen-spirit/">Developing a Kaizen Spirit</a></p>
<p><a href="http://business901.com/blog1/developing-a-kaizen-conscious-with-shingo-prize-winner-michael-balle/">Developing a Kaizen Conscious with Shingo Prize winner Michael Balle</a></p>
<p><a href="http://business901.com/blog1/how-much-planning-is-enough-use-lean-and-standardize/">How much Planning is enough – Use Lean and Standardize</a></p>
<p><a href="http://business901.com/blog1/it-takes-guts-to-start-with-lean-training-in-a-turnaround/">It takes guts, to start with lean training in a turnaround!</a></p>
<div id="scid:0767317B-992E-4b12-91E0-4F059A8CECA8:f4d48caa-d8cc-47e4-8bc6-0fcbd999f71e" class="wlWriterEditableSmartContent" style="margin: 0px; display: inline; float: none; padding: 0px;">Technorati Tags: <a rel="tag" href="http://technorati.com/tags/lean+manufacturing">lean manufacturing</a>,<a rel="tag" href="http://technorati.com/tags/implementing+lean">implementing lean</a>,<a rel="tag" href="http://technorati.com/tags/lean+transformation">lean transformation</a>,<a rel="tag" href="http://technorati.com/tags/standard+work">standard work</a>,<a rel="tag" href="http://technorati.com/tags/problem+solving">problem solving</a>,<a rel="tag" href="http://technorati.com/tags/Kaizen">Kaizen</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.business901.com/blog1/implementing-lean/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Using Stories to explain your Marketing Efforts</title>
		<link>http://www.business901.com/blog1/using-stories-to-explain-your-marketing-efforts/</link>
		<comments>http://www.business901.com/blog1/using-stories-to-explain-your-marketing-efforts/#comments</comments>
		<pubDate>Mon, 15 Mar 2010 01:00:00 +0000</pubDate>
		<dc:creator>business901</dc:creator>
				<category><![CDATA[Agile Marketing]]></category>
		<category><![CDATA[Mirror Marketing]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Marketing stories]]></category>
		<category><![CDATA[Scrumban]]></category>
		<category><![CDATA[Stories]]></category>
		<category><![CDATA[stroyboard]]></category>
		<category><![CDATA[XP]]></category>

		<guid isPermaLink="false">http://www.business901.com/blog1/using-stories-to-explain-your-marketing-efforts/</guid>
		<description><![CDATA[`In Scrum, work is expressed in the backlog as user stories. A team may write its user stories in a number of ways as long as they are written from the perspective of the end user. Put another way, team members are encouraged to think of their work from the perspective of who will use [...]]]></description>
			<content:encoded><![CDATA[<p>`In Scrum, work is expressed in the backlog as user stories. A team may write its user stories in a number of ways as long as they are written from the perspective of the end user. Put another way, team members are encouraged to think of their work from the perspective of who will use it, hence “user” story.</p>
<p>In the <a href="http://scrummethodology.com/">Scrum Methodology</a> blog they stated:</p>
<blockquote><p>Many Scrum teams have adopted the user story template developed by Mike Cohn, which identifies who the end user is, what the end user wants, and why in a single sentence. This model of the user story is most often written like this: “As a [end user role], I want [the desire] so that [the rationale].</p>
<p>They also defined it further in a contest that they had by asking for these requirements:</p>
<ul>
<li>The Problem. What was going wrong at your organization that made you decide to implement agile or Scrum?</li>
<li>The Application. Once your organization decided to use Scrum to surface dysfunction and transform its processes, how did you go about doing it? What were the first steps you took? Was it an organization-wide adoption or just on the team level? Did you use training or tools?</li>
<li>The Solution. What was the result? Can you quantify the improvements that Scrum and agile helped realize? Have other teams at your organization begun adopting agile management techniques?</li>
</ul>
</blockquote>
<p>Stories are used because they make it easier to understand,  remember and use. The limitation is that you do not know if you have been given all the facts.  A short clip from a training class Paul of <a href="http://www.youtube.com/user/ThinkSticky">ThinkSticky</a> teaches on the content of the book, Made to Stick. This hands-on training illustrates how those qualities can be leveraged in your daily work.</p>
<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="344" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/MLbpEzceVhw&amp;hl=en_US&amp;fs=1&amp;" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="425" height="344" src="http://www.youtube.com/v/MLbpEzceVhw&amp;hl=en_US&amp;fs=1&amp;" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
<p>I have started to use stories in explaining the outcome that is desired in a marketing campaign or event. I  plan on further developing this topic in a series of blog post. This is the first blog in this series.</p>
<p>Related posts:</p>
<p><a href="http://business901.com/blog1/agile-marketing-maybe/">Agile Marketing – Maybe? </a></p>
<p><a href="http://business901.com/blog1/start-your-marketing-with-a-user-story/">Start your Marketing with a User Story </a></p>
<p>Further reading:</p>
<p><a href="http://www.amazon.com/gp/product/1400064287?ie=UTF8&amp;tag=business901-20&amp;linkCode=as2&amp;camp=1789&amp;creative=9325&amp;creativeASIN=1400064287">Made to Stick: Why Some Ideas Survive and Others Die</a><img style="margin: 0px; border-style: none !important;" src="http://www.assoc-amazon.com/e/ir?t=business901-20&amp;l=as2&amp;o=1&amp;a=1400064287" border="0" alt="" width="1" height="1" /></p>
<p><a href="http://www.amazon.com/gp/product/0321205685?ie=UTF8&amp;tag=business901-20&amp;linkCode=as2&amp;camp=1789&amp;creative=9325&amp;creativeASIN=0321205685">User Stories Applied: For Agile Software Development</a><img style="margin: 0px; border-style: none !important;" src="http://www.assoc-amazon.com/e/ir?t=business901-20&amp;l=as2&amp;o=1&amp;a=0321205685" border="0" alt="" width="1" height="1" /></p>
<div id="scid:0767317B-992E-4b12-91E0-4F059A8CECA8:19088959-e6a5-472e-adb4-6a44808c4b41" class="wlWriterEditableSmartContent" style="margin: 0px; display: inline; float: none; padding: 0px;">Technorati Tags: <a rel="tag" href="http://technorati.com/tags/Stories">Stories</a>,<a rel="tag" href="http://technorati.com/tags/stroyboard">stroyboard</a>,<a rel="tag" href="http://technorati.com/tags/Scrumban">Scrumban</a>,<a rel="tag" href="http://technorati.com/tags/Agile">Agile</a>,<a rel="tag" href="http://technorati.com/tags/XP">XP</a>,<a rel="tag" href="http://technorati.com/tags/Marketing+stories">Marketing stories</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.business901.com/blog1/using-stories-to-explain-your-marketing-efforts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why are we doing this?</title>
		<link>http://www.business901.com/blog1/why-are-we-doing-this/</link>
		<comments>http://www.business901.com/blog1/why-are-we-doing-this/#comments</comments>
		<pubDate>Sat, 13 Mar 2010 03:31:00 +0000</pubDate>
		<dc:creator>business901</dc:creator>
				<category><![CDATA[Learning]]></category>
		<category><![CDATA[Marketing System]]></category>
		<category><![CDATA[Common Sense]]></category>
		<category><![CDATA[Effective-Marketing]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[Why]]></category>

		<guid isPermaLink="false">http://www.business901.com/blog1/why-are-we-doing-this/</guid>
		<description><![CDATA[ Do you ask this question before your start a marketing campaign or project? Sometimes it is really hard to come up with a number or a goal, but should we not try before doing it? I hear more people discussing why you should not measure things rather than why you should. But I think [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.business901.com/wp-content/uploads/2010/03/Yweb.jpg"><img style="margin: 5px; display: inline; border-width: 0px;" title="Letter &quot;Y&quot; girl" src="http://www.business901.com/wp-content/uploads/2010/03/Yweb_thumb.jpg" border="0" alt="Letter &quot;Y&quot; girl" width="156" height="240" align="right" /></a> Do you ask this question before your start a marketing campaign or project? Sometimes it is really hard to come up with a number or a goal, but should we not try before doing it? I hear more people discussing why you should not measure things rather than why you should. But I think it really pays to have a goal or some sort of metric, even one that is not worth very much.</p>
<p>The goal might change and be adjusted during the process but I certainly think having good solid reasoning would be worthwhile to most people. Especially, when you get in the middle of the project and start wondering what you should be doing today. I know this sounds rather trivial and many may think that I am rather foolish in discussing it. However, I think if you sit back and look at some of your last marketing projects or maybe even your last sales call, you might find that this answer is a little “Grayer” than what it should be.</p>
<p>By answering such a simple question you may clarify for your whole team decisions based on outcomes, cost, time, and resources, that get allocated. Without the question you may not even build a process to answer, why you did it.</p>
<p>I would challenge organizations to not only consider this question. But spend time thinking of how it fits into a larger picture. If you have ever heard me talk about what works in marketing, you know that I believe that one single event by itself seldom works. Effective marketing is the strength of the connections between each single event.</p>
<p>Why are we doing this? I like that question!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.business901.com/blog1/why-are-we-doing-this/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
