<?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>Knowledge Fulcrum &#187; Alignment</title>
	<atom:link href="http://knowledge-fulcrum.com/tag/alignment/feed/" rel="self" type="application/rss+xml" />
	<link>http://knowledge-fulcrum.com</link>
	<description></description>
	<lastBuildDate>Wed, 22 Sep 2010 21:10:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>LEAN = Seeing Small Things That Make a Big Difference</title>
		<link>http://knowledge-fulcrum.com/2009/04/09/lean-seeing-small-things-that-make-a-big-difference/</link>
		<comments>http://knowledge-fulcrum.com/2009/04/09/lean-seeing-small-things-that-make-a-big-difference/#comments</comments>
		<pubDate>Thu, 09 Apr 2009 14:36:25 +0000</pubDate>
		<dc:creator>johnstepleton</dc:creator>
				<category><![CDATA[Change Management]]></category>
		<category><![CDATA[Employee Empowerment]]></category>
		<category><![CDATA[People & Process]]></category>
		<category><![CDATA[Alignment]]></category>
		<category><![CDATA[Culture]]></category>
		<category><![CDATA[Sustainable Work]]></category>
		<category><![CDATA[Visual Management]]></category>

		<guid isPermaLink="false">http://knowledge-fulcrum.com/?p=511</guid>
		<description><![CDATA[Over the years, I&#8217;ve discovered that what makes LEAN so illusive isn&#8217;t that it&#8217;s a complex idea, but that it&#8217;s a simple idea that happens to be hard to implement. LEAN &#8211; the name commonly used to describe the Toyota Production System -  is the systematic removal of waste from any system on a constant and [...]]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-medium wp-image-512" title="img_mindlikewater" src="http://knowledge-fulcrum.com/wp-content/uploads/2009/04/img_mindlikewater-300x200.jpg" alt="img_mindlikewater" width="300" height="200" /></p>
<p>Over the years, I&#8217;ve discovered that what makes LEAN so illusive isn&#8217;t that it&#8217;s a complex idea, but that <em>it&#8217;s a simple idea that happens to be hard to implement</em>.</p>
<p>LEAN &#8211; <a href="http://en.wikipedia.org/wiki/Lean_manufacturing" target="_blank">the name commonly used to describe the Toyota Production System</a> - <span style="color: #ff0000;"> </span>is the <em>systematic removal of waste</em> from any system on <em>a constant and never ending basis</em>.   When I first started to study the Toyota philosophy, I struggled to see where I could find the kind of improvements that would generate the kinds of results I had read about.  That&#8217;s where I went wrong.  LEAN is about <em>creating a rhythm</em> where everyone in the organization is trained to see the small things.  <em>Small things</em>, when observed alone, seem insignificant &#8211; but when compounded over time and across many people &#8212; small things add up fast.</p>
<p>Here&#8217;s a a perfect &#8220;real world&#8221; example:</p>
<p>In my last <a href="http://www.rddfs.com/" target="_blank">company</a>, we operated call centers where we conducted primary research studies for organizations.  On any given shift, an agent would work on an average of 3 different projects.  Because of how the software was originally developed, in order to change to another project, an agent would need to alert a floor supervisor to be &#8220;moved&#8221; to the next program.   This required the agent to get up and walk to the end of the floor to alert the supervisor.   For 12 years this was &#8220;standard procedure.&#8221;  No one ever stopped to think about what the cumulative &#8220;cost&#8221; of having the agent get up and request a change actually was.</p>
<p>When we started our LEAN journey, we began to look for small things that were simple to correct.  We started to measure everything we could.  Eventually someone decided to measure the average time it took an agent to &#8220;change&#8221; projects.   It was an average of 1.2 minutes.  Not all that significant, right?  But when seen in the context of the entire organization and over the entire year, the numbers began to add up very fast.</p>
<p style="padding-left: 30px;">Average # of Agents per Day &#8211; 250</p>
<p style="padding-left: 30px;">Average # of Study Changes &#8211; 3</p>
<p style="padding-left: 30px;">Number of Working Days per Year &#8211; 350</p>
<p style="padding-left: 30px;">Average Time per Study Change &#8211; 1.2 <span style="color: #000000;">min</span></p>
<p style="padding-left: 30px;">Average Cost per Agent ($11.20 loaded) &#8211; $0.1867/min</p>
<p style="padding-left: 30px;">Total Cost to Change Studies each Year = 250 X 3 X 350 X 1.2 X $0.1867 = <strong>$58,810.50</strong></p>
<p>The solution was simple.  We made cardboard &#8220;signals&#8221; that agents would raise when ready to change studies.  These &#8220;signals&#8221; alerted the floor supervisor, who then changed them over on the system.   <em>In 24 hours</em>, we were able to reduce the average change over time from 1.2 minutes to just .23 minutes.   That simple solution resulted in a <span style="text-decoration: underline;">net savings</span> of <strong>$47,538 </strong>a year.  It only cost us a few dollars in card stock and a 15 minute training for every employee.</p>
<p><img class="aligncenter size-medium wp-image-513" title="visual-signal" src="http://knowledge-fulcrum.com/wp-content/uploads/2009/04/visual-signal-199x300.jpg" alt="visual-signal" width="199" height="300" /></p>
<p>LEAN is not about BIG improvements.  LEAN is about <em>seeing</em> the business <em>in a different way</em> and <em>constantly making small changes that overtime create significant savings</em> for the business.   Now more than ever, we all should be thinking LEAN.</p>
]]></content:encoded>
			<wfw:commentRss>http://knowledge-fulcrum.com/2009/04/09/lean-seeing-small-things-that-make-a-big-difference/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Now What?  Continuous Improvement Program PART II</title>
		<link>http://knowledge-fulcrum.com/2009/03/26/now-what-continuous-improvement-program-part-ii/</link>
		<comments>http://knowledge-fulcrum.com/2009/03/26/now-what-continuous-improvement-program-part-ii/#comments</comments>
		<pubDate>Thu, 26 Mar 2009 17:41:38 +0000</pubDate>
		<dc:creator>johnstepleton</dc:creator>
				<category><![CDATA[Change Management]]></category>
		<category><![CDATA[People & Process]]></category>
		<category><![CDATA[Alignment]]></category>
		<category><![CDATA[Customer Value]]></category>

		<guid isPermaLink="false">http://knowledge-fulcrum.com/?p=474</guid>
		<description><![CDATA[Now I want to walk you through the process we used to document our value stream, and what we were interested in measuring. Generally it&#8217;s good to start your process mapping by looking at the job function level.  Depending on the complexity of your business, you may want to do this by individual department.  You will know [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #000000;"><img class="aligncenter size-medium wp-image-498" title="zero-waste" src="http://knowledge-fulcrum.com/wp-content/uploads/2009/03/zero-waste-300x213.jpg" alt="zero-waste" width="300" height="213" /><br />
</span></p>
<p><span style="color: #000000;">Now I want to walk you through the process we used to document our value stream, and what we were interested in measuring.</span></p>
<p><span style="color: #000000;">Generally it&#8217;s good to start your process mapping by looking at the <em>job function level</em>.  Depending on the complexity of your business, you may want to do this by individual department.  You will know if you need to break it down.  <em>Map the current state first</em>.</span></p>
<p><span style="color: #000000;"><em>Use post-its</em> to define each discrete job function in order.  You can use swimming lanes if there are concurrent processes you&#8217;d like to map.  Ideally, you&#8217;d also be gathering accurate information on the following metrics &#8211; to start you may just want to use your best estimates:</span></p>
<ul>
<li><span style="color: #000000;">Cycle Time &#8211; this is the average time it takes <em>to do the task</em>.</span></li>
<li><span style="color: #000000;">Process Time &#8211; this is the average time it takes <em>including any waiting</em> before or after the task.</span></li>
<li><span style="color: #000000;">Percent Complete &amp; Accurate - an estimate of what % of the time the task is received complete &amp; accurate.</span></li>
<li><span style="color: #000000;">Percent Exceptions &#8211; this is a measure of <em>how frequently there are exceptions</em> which require special handling.</span></li>
<li><span style="color: #000000;">Number of Hand-offs &#8211; how many times does the work change hands (don&#8217;t forget figuratively, if information is emailed around the company).</span></li>
</ul>
<p><span style="color: #000000;">Now you can start to see how much time is spent on activities other than doing the necessary work.  Be sure to include documents or reports that are built into certain job functions.  For those who are more detailed oriented, you may continue to break job functions down into discrete tasks.</span></p>
<p><span style="color: #000000;">I would start broad until you get a feel for how this works.  If possible, remember to include people from every job function and department.</span></p>
<p><span style="color: #000000;">Now you can add up each type of time.  The total Cycle Time is the actual time spent doing the work to produce your product or service.  The total Process Time is how long it takes you to get the product or service out the door and into the hands of the customer.  Usually the Cycle to Process ratio is VERY low.  But now you should start to see where there&#8217;s opportunity to take waste out.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://knowledge-fulcrum.com/2009/03/26/now-what-continuous-improvement-program-part-ii/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Why Employee Suggestion Boxes Don&#8217;t Work</title>
		<link>http://knowledge-fulcrum.com/2009/02/18/why-employee-suggestion-boxes-dont-work/</link>
		<comments>http://knowledge-fulcrum.com/2009/02/18/why-employee-suggestion-boxes-dont-work/#comments</comments>
		<pubDate>Wed, 18 Feb 2009 14:32:45 +0000</pubDate>
		<dc:creator>johnstepleton</dc:creator>
				<category><![CDATA[Change Management]]></category>
		<category><![CDATA[Employee Empowerment]]></category>
		<category><![CDATA[Orgainzational Culture]]></category>
		<category><![CDATA[Problem Solving]]></category>
		<category><![CDATA[Alignment]]></category>
		<category><![CDATA[Culture]]></category>

		<guid isPermaLink="false">http://knowledge-fulcrum.com/?p=315</guid>
		<description><![CDATA[What does your employee feedback program look like?  Do you have one of these boxes in your office?  How do you gauge the mood of the employees in your organization?  Do you know what&#8217;s getting in the way of your people&#8217;s performance?  How do you know?   Let&#8217;s start over &#8211; why should you care?  First, I&#8217;ll start with why some  employee feedback [...]]]></description>
			<content:encoded><![CDATA[<p style="TEXT-ALIGN: center"><img class="size-full wp-image-316 aligncenter" title="suggestion-box-is-dead" src="http://knowledge-fulcrum.com/wp-content/uploads/2009/02/suggestion-box-is-dead.png" alt="suggestion-box-is-dead" width="313" height="383" /></p>
<p>What does <em>your</em> employee feedback program look like?  Do you have one of these <a href="http://en.wikipedia.org/wiki/Suggestion_box" target="_blank">boxes</a> in your office?  How do you gauge the mood of the employees in your organization?  Do you know what&#8217;s getting in the way of your people&#8217;s performance?  How do you<em> know</em>?   Let&#8217;s start over &#8211; why should you care? </p>
<p>First, I&#8217;ll start with why some  employee feedback programs don&#8217;t work:</p>
<ul>
<li>Feedback systems are <em>black boxes</em>.  Ideas and suggestions either never get seen or fall on deaf ears.    If you aren&#8217;t willing to take action, then DON&#8217;T ASK FOR SUGGESTIONS.</li>
<li><em>Feedback isn&#8217;t timely</em>.  If the system is designed to gather information, but it&#8217;s not noticed or acted on immediately, then the problem either already did its damage or has grown into a bigger problem. </li>
<li><em>Suggestions are poorly defined</em>.  Too often, employee feedback systems are only used to vent personal issues about peers, managers and customers and don&#8217;t identify the core operation or process that is broken.  </li>
<li><em>Lack of accountability</em>.  Most systems don&#8217;t provide any feedback loops to ensure corrective measures are identified, implemented and standardized.</li>
<li><em>Feedback is ad hoc, not systematic</em>.  If you don&#8217;t make it a priority everyday, or every week &#8211; then feedback systems won&#8217;t stick long-term.</li>
</ul>
<p>If you&#8217;re still unsure as to the benefit of good feedback systems &#8211; then perhaps you can <a href="http://www.gazelles.com/columns/Market%20Intelligence.pdf" target="_blank">read a bit more </a>about world-class organizations that implement feedback systems that produce results (Thanks, <a href="http://www.gazelles.com/columns/Market%20Intelligence.pdf" target="_blank">Verne</a>!).  </p>
<p>Now the good news.  This doesn&#8217;t have to be <em>rocket science &#8211; </em>here are  a few tips to get you started:</p>
<ul>
<li>Make it a <em>habit.</em></li>
<li>Keep it <em>anonymous.</em></li>
<li>Make it <em>about what</em>, not about who.</li>
<li>Good systems ask for feedback on corrective <em>measures that will</em> <em>work</em>; good systems are not just looking for complaints.</li>
<li>Don&#8217;t shoot the messenger &#8211; if you aren&#8217;t ready to hear the <a href="http://www.jimcollins.com/lab/brutalFacts/index.html" target="_blank">brutal facts, </a>then go to another website.</li>
<li>Make sure the issues are <em>visible</em> so EVERYONE can weigh-in on what issues need addressing first.</li>
<li><em>Never, ever stop</em>!  It&#8217;s continuous improvement.</li>
<li><em>Offer rewards</em> when improvements save the company time, energy and money.  It only works if everyone has a stake in the outcome.</li>
<li>When you listen &#8211; don&#8217;t defend but <em>keep an open ear and mind</em> to what your people have to say.</li>
</ul>
<p>Today more than ever we all need to work together to identify and solve the issues that are holding our performance back.   Employees <span style="text-decoration: underline;">and</span> owners can no longer look to the other for the answers - we need to work together to make our organizations and ourselves stronger, better and more effective.</p>
]]></content:encoded>
			<wfw:commentRss>http://knowledge-fulcrum.com/2009/02/18/why-employee-suggestion-boxes-dont-work/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How Transparent is Your Culture?</title>
		<link>http://knowledge-fulcrum.com/2009/02/16/how-transparent-is-your-culture/</link>
		<comments>http://knowledge-fulcrum.com/2009/02/16/how-transparent-is-your-culture/#comments</comments>
		<pubDate>Mon, 16 Feb 2009 14:22:09 +0000</pubDate>
		<dc:creator>johnstepleton</dc:creator>
				<category><![CDATA[Benchmarking]]></category>
		<category><![CDATA[Orgainzational Culture]]></category>
		<category><![CDATA[People & Process]]></category>
		<category><![CDATA[Vision & Purpose]]></category>
		<category><![CDATA[Alignment]]></category>
		<category><![CDATA[Core Values]]></category>
		<category><![CDATA[Culture]]></category>
		<category><![CDATA[Employee Empowerment]]></category>
		<category><![CDATA[Vision]]></category>

		<guid isPermaLink="false">http://knowledge-fulcrum.com/?p=299</guid>
		<description><![CDATA[What is the essence of an organization&#8217;s culture?  What makes it work?  For some time now I&#8217;ve had this image in my mind &#8211; it&#8217;s the purest description of Organizational Culture I&#8217;ve been able to think of .     It has been said before that organizations with a strong culture are those in which the staff respond [...]]]></description>
			<content:encoded><![CDATA[<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"><img class="aligncenter size-full wp-image-303" title="culture1" src="http://knowledge-fulcrum.com/wp-content/uploads/2009/02/culture1.jpg" alt="culture1" width="365" height="304" />What is the essence of an organization&#8217;s culture?  What makes it work?  For some time now I&#8217;ve had this image in my mind &#8211; it&#8217;s the purest description of <a href="http://en.wikipedia.org/wiki/Organizational_culture" target="_blank">Organizational Culture </a>I&#8217;ve been able to think of .  </div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"> </div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left">It has been said before that organizations with a <em>strong culture</em> are those in which the staff respond to stimulus because of their alignment to organizational values.    Companies like <a href="http://www.businessweek.com/bschools/content/mar2007/bs20070305_813282_page_2.htm" target="_blank">Nike</a>, <a href="http://www.southwest.com/careers/culture.html">Southwest Airlines</a>, <a href="http://news.cnet.com/8301-13505_3-9758178-16.html" target="_blank">Apple</a>, <a href="http://www.google.com/corporate/culture.html" target="_blank">Google</a> &#8211; they all have what most would describe as a <em>strong culture</em>. </div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"> </div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left">I would argue that culture goes beyond simply aligning the employees around a set of organizational values.  I would say that strong cultures have very defined and distinct components around three broad areas:</div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"> </div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"><strong>Purpose &#8211; </strong>This is a much better word than &#8220;values.&#8221;  <em>Purpose </em>defines a broad sense of one&#8217;s aim, intention, role, determination and resolve.  Simply aligning people around a set of values will not get you results.  <em>Purpose</em> provides people &#8211; in this case employees and customers - the ability to link cause and effect to the achievement of a goal in a given system.  <em>Purpose</em> is what guides decision-making in choosing appropriate actions within a range of strategies based on varying degrees of abiguityof knowledge that creates a context for action.  More simply put &#8211; <em>purpose</em> allows people to change the conditions in an environment in order to make it better.  This is a complex yet powerful concept.</div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"> </div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"><strong>Alignment - </strong>This<strong> </strong>goes well beyond organizational structure.  <em>Alignment </em>is the adjustment of an object or activity <em>in relation to</em> other objects or activities.   It goes much deeper than the &#8221;structure&#8221; an organization&#8217;s decision-making takes.  In this context, <em>alignment</em> refers not just to the people but also the activities <span style="text-decoration: underline;">and</span> the information.  When combined with a common purpose - employees will re-orient their position, activities and behaviors in order to achieve the desired results.  Too many have confused &#8220;command and control&#8221; with <em>alignment</em>.  Go to any successful restaurant and walk into the kitchen.  A well-aligned kitchen means that everyone knows precisely their necessary activity, and everyone has the &#8221;information&#8221; to pull all the dishes together in the most efficient manner.</div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"> </div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"><strong>Empowerment - </strong>This is the last piece to the puzzle.  <em>Empowerment </em>provides people with information and resources to make decisions and take action.   This is also where individuals take initiative to improve how they currently do their work in an effort to seek a more effective and more efficient method.  It is also where individuals learn that they are a part of the continuous process where change is never ending, and change is self-initiated.   <em>Empowerment</em> is also where your employees gain (or enhance) a positive self image.  Empowerment is also where your employees identify, deal with and overcome barriers; this increases their ability to use discreet thinking to sort out right from wrong. </div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"> </div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"><strong>Three simple words</strong> to describe a complex, dynamic, yet difficult state to achieve.  Everything that&#8217;s part of your culture exists within these three simple areas.  What I do know is that achieving results like the companies mentioned - is not an easy task.  It takes never-ending faith, focus and effort &#8211; not just by you the CEO, but by everyone in the organization.  It&#8217;s up to you to decide if it&#8217;s worth it or not.</div>
<div class="mceTemp mceIEcenter" style="TEXT-ALIGN: left"> </div>
]]></content:encoded>
			<wfw:commentRss>http://knowledge-fulcrum.com/2009/02/16/how-transparent-is-your-culture/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

