The TRIZ JournalCelebrating 10 Years On The Web
Part of the RealInnovation Network
AIT Group - Competitive Strategy and Innovation Inventioneering - Innovation is in our DNA Valeocon Management Consultants - Value Innovation Click To Learn More About PremiumLinks
Home  >  Real Innovation Commentary
Search:
  • Subscribe
  • What is TRIZ?
  • Contradiction Matrix
    & 40 Principles
  • Archives
  • Best Practices
    • General
    • Software, Innovation and Creativity
    • Consultants, Innovation and Creativity
  • Call For Papers
  • Dictionary
  • Events Calendar
  • Jobs
  • News
  • Commentary
  • Discussion Forum
  • Related Topics
  • Business Process Mgt
  • Innovation
  • Outsourcing
  • Six Sigma
  • Quick Access
  • Help
  • Search
  • Advertising
  • Article Archive
  • Newsletter Archive
  • Reader Feedback
  • Editorial Panel
Cass Pursell

Commentary by Cass Pursell

Email and RSSSubscribe via Email or RSS   |   Cass Pursell's Biography Biography
October 30, 2007
Print | Email

Coping with Process Variation

I have talked before about Little's Law and its role in improving the speed of the innovation process ("One critical issue that must be better understood is the cause of long innovation lead times," from my post on August 29th.) According to Micheal George, the author of some of the best business books in my library, using Little's Law is just the first step in controlling lead time in the innovation process. As a reminder, Little's Law is a function of work in progress and average completion rate, and it teaches us how to release projects into the development pipeline in such a way as to help us to maximize the speed of the process. But what happens after the project is released into the development pipeline? How do we account for the reality that some work gets done more quickly than planned and other work defeats our best estimates and takes far longer than we believed it would?

I work frequently with software developers, who are purposely scheduled at very high utilization rates. On average, the higher the utilization rate of a developer, the longer any given project that depends on that developer will spend waiting for him or her to come available. In other words, if a developer is 90% utilized, an average project that requires him or her as a resource will wait in queue a lot longer than if the developer were only 50% utilized. This is true because inevitably, developers run into problems; for developers with higher utilization rates, projects will begin to pile up as those problems are worked through. This effect is known as the Law of Innovation Variation, and it can create potentially seismic impacts on lead time via its impact on average completion rate. Becoming familiar with the Law of Innovation Variation is a good first step for managers who are interested in creating visibility into how much "bunching up" of tasks will occur; it allows managers to isolate the point in the innovation process where this bunching up occurs, and helps to identify the critical resource(s) associated with the bunching up.

By using Little's Law in conjunction with the Law of Innovation Variation, time-to-market can be compressed. Even if you're not in a highly commoditized environment, shrinking time-to-market will likely have a positive impact on both revenue and operating margins, and that's always a good thing.

Comments [0] | Permalink
Categories: Management

COMMENTARY COMMENT
ADD A COMMENT
ADD COMMENT
(*) indicates required fields
author (*) :
email address :
url :
 
  bold italic underline add hyperlink add email hyperlink centre unorder list order list add image quote emoticon smiles
 
comment (*) :

max characters : 1500

characters remaining :
remember me :
To help us prevent spam-generated submissions,
please enter the summation of 5 and 2 below:
 
 
 
RECENT ENTRIES
RSS
  • A Vote for Process Innovation
  • Structure is a Good Thing
  • You Measure What Matters
  • The Decline of the Corporate Lab Rat?
  • Where's My Return on Innovation?!
  • Wal Mart Saves the World

LATEST COMMENTS
  • The Customer-Centered Innovation Map by Ellen Domb
  • All Solutions Are Not Equal by Ellen Domb
  • Teaching Innovation by mike Lafond
  • The Customer-Centered Innovation Map by Navneet Bhushan
  • Dogwood in the Moonlight by Lynda Curtin
  • Dogwood in the Moonlight by Ellen Domb

COMMENTATORS
Katie Barry [39]  RSS Katie Barry's Biography
Ellen Domb [35]  RSS Ellen Domb's Biography
Praveen Gupta [34]  RSS Praveen Gupta's Biography
Michael S. Slocum [33]  RSS Michael S. Slocum's Biography
Cass Pursell [27]  RSS Cass Pursell's Biography
James Todhunter [16]  RSS James Todhunter's Biography
Jack Hipple [13]  RSS Jack Hipple's Biography
Michael Cyger [10]  RSS Michael Cyger's Biography
Lynda Curtin [7]  RSS Lynda Curtin's Biography
Bob Carter [4]  RSS Bob Carter's Biography
Guest Commentator [3]  RSS Guest Commentator's Biography
All Commentators

CATEGORIES
About Commentators [10]  RSS
Buzz/Press [38]  RSS
Companies [15]  RSS
Conference [37] RSS
General [94]  RSS
Leadership [4]  RSS
Management [44]  RSS
Methodology [61]  RSS
Strategy [60]  RSS

ARCHIVES
RSS
  

* Current Month
* Full Archive



Ad Links
Design for Six Sigma eLearning

TRIZ training, business & technical applications

Innovation programs from BMG

Business Innovation in the 21st Century (eBook)

Innovaton-TRIZ


Legal Information. © 2006 CTQ Media LLC. All rights reserved. v1.0, 0.1 Submit an Article • About The TRIZ Journal • Contact Us • Privacy Policy • Site Map