Frugal Innovation

First break all the rules

The device is a masterpiece of simplification. The multiple buttons on conventional ECGs have been reduced to just four. The bulky printer has been replaced by one of those tiny gadgets used in portable ticket machines. The whole thing is small enough to fit into a small backpack and can run on batteries as well as on the mains. This miracle of compression sells for $800, instead of $2,000 for a conventional ECG

Frugal products need to be tough and easy to use. Nokia’s cheapest mobile handsets come equipped with flashlights (because of frequent power cuts), multiple phone books (because they often have several different users), rubberised key pads and menus in several different languages. Frugal does not mean second-rate.

The article goes on to talk about several methods for how to profit from reducing costs which seem misguided. Frugal innovation is about thinking about meeting the needs of huge numbers of customers that can’t afford conventional solutions. By talking a new look at the situation and attempting to find solutions with significant price constraints new markets can be opened. Often this requires thinking similar to disruptive innovation (products that serve a similar need but less completely than current options).

It also requires the engineering principles of appropriate technology. I highlight this thinking in my Curious Cat Engineering blog and find it very worthwhile. For organizations that have a true mission to serve some purpose using such thinking allows a greatly expanded potential market in which to make a difference in the world.

There is a great quote from Jeff Bezos that captures one reason why organizations so often fail to address frugal innovation: “There are two kinds of companies, those that work to try to charge more and those that work to charge less.” Many organizations are focused on trying to charge more, not less. Another problem is that decision makers often have no life experience with cheap solutions – this doesn’t prevent frugal innovation but it does make them less likely to see the need and to decide to solve those customer needs.

Related: Appropriate ManagementManaging InnovationProcess Improvement and Innovation

Posted in Creativity, India, Innovation, quote | Tagged , , , , , , | 1 Comment

Classic Management Theories Are Still Relevant

Good management is good management: it doesn’t matter if someone figured out the good idea 100 years ago or last week.

Are “Classic” Management Theories Still Relevant?

It did make me wonder about the staying power of management models, processes, skills, and conventional wisdom…

There are way too many people in our field that are not true professionals – they don’t do their homework, and rely too much on their own personal experience. They’re the ones who tend to jump from one fad to the next, enthusiastically promoting each one with an almost religious passion.

However, there’s also a danger of not keeping up with the times and sticking with models or skills that really have outlived their usefulness. At best, you run the risk of coming across as a dinosaur when you explain a management model that was developed in the 1920’s to a group of Millennials. Even worse, you may be relying on models that really don’t apply in today’s world.

Classic management ideas are definitely very valuable today. It is amazing how little use of long known good leadership lessons actually takes place in organizations. You don’t need to discover secrets to improve, just adopt ideas others ignore since they are not new (or whatever justification they use for ignoring them).

One of the main things I have been trying to do with my web sites is to get people to use the already well documented successful management practices.

Bad management ideas are bad: Regardless if they were good ideas 40 years ago, or not. I find bad management practices most often never were good practices so worrying about outdated good practices is not something that merits much time. Just avoid bad practices, don’t worry about when the practices were adopted.

As Dan McCarthy says in his post: “Read and respect the classics and keep up with the latest.”

And if you have to focus on one, focus on the classics. Most of what is new isn’t worthwhile so you will likely spend a lot of time reading about fads that die before you can even try to adopt the ideas into your organizational system. There are good new ideas – read Clayton Christensen, for some good new ideas (even many of those are nearly 10 years old now). Agile software development is another area where good tactics seem new. Mainly agile management offers good ideas on tactics for applying lots of good management ideas (often these ideas are not new), it seems to me.

Related: New or Different? Just Choose BetterManagement Advice FailuresNew Management Truths Sometimes Started as HeresiesNot New Rules for Management

Posted in Deming, Management, quote, Systems thinking | Tagged , , , , , | 6 Comments

Statistical Engineering Links Statistical Thinking, Methods and Tools

In Closing the Gap Roger W. Hoerl and Ronald D. Snee lay out a sensible case for focusing on statistical engineering.

We’re not suggesting that society no longer needs research in new statistical techniques for improvement; it does. The balance needed at this time, however, is perhaps 80% for statistics as an engineering discipline and 20% for statistics as a pure science.

True, though I would put the balance more like 95% engineering, 5% science.

There is a good discussion on LinkedIn [the link was broken by LinkedIn, so it has been removed]:

Davis Balestracci [link updated]: Unfortunately, we snubbed our noses at the Six Sigma movement…and got our lunch eaten. Ron Snee has been developing this message for the last 20 years (I developed it in four years’ worth of monthly columns for Quality Digest from 2005-2008). BUT…as long as people have a computer, color printer, and a package that does trend lines, academic arguments won’t “convert” anybody.

Recently, we’ve lost our way and evolved into developing “better jackhammers to drive tacks”…and pining for the “good ol’ days” when people listened to us (which they were forced to do because they didn’t have computers, and statistical packages were clunky). Folks, we’d better watch it…or we’re moribund

Was there really a good old days when business listened to statisticians? Of course occasionally they did, but “good old days”? Here is a report from 1986 the theme of which seems to me to be basically how to get statisticians listened to by the people that make the important decisions: The Next 25 Years in Statistics, by Bill Hunter and William Hill. Maybe I do the report a disservice with my understanding of the basic message, but it seems to me to be how to make sure the important contributions of applied statisticians actually get applied in organizations. And it discusses how statisticians need to take action to drive adoption of the ideas because currently (1986) they are too marginalized (not listened to when they should be contributing) in most organizations.
Continue reading

Posted in Science, Six sigma, Statistics | Tagged , , , , , , , | 1 Comment

Management Improvement Carnival #99

Mark R. Hamel is hosting Management Improvement Carnival #99 on the Gemba Tales blog, highlights include:

  • The Downside of Automation by Dan Markovitz – “…When I see companies leaping at technological solutions for time and attention management, I have a feeling that they’re in for a big disappointment.”
  • Inefficiency through Default Meeting Times by Tim McMahon – “…Who decided meetings should be 30 or 60 minutes?”
  • Fake Lean and the Spotting Thereof by Jon Miller – “…While lean is journey of continuous improvement and there is no such thing as arriving at state where we can say ‘we are lean’ there are plenty of false paths, dead ends and wilderness areas on this journey that we can label ‘fake lean’.”
  • Everyone Is Responsible for Their Systems by Jamie Flinchbaugh – “…I believe we (meaning lean thinkers) send blame up the organizational chart too far, as a natural reaction to too much blame being pushed down on people in traditional organizations.”

Related: Management Improvement Carnival #62Management Improvement Carnival #36Curious Cat Management Search Engine

Posted in Carnival, Management | Tagged | Comments Off on Management Improvement Carnival #99

Incentivizing Behavior Doesn’t Improve Results

In the webcast Dan Pink’s shares research results exploring human motivation and ideas on how to manage organization given the scientific research on motivation.

  • “once a task called for even rudimentary cognitive skill a larger reward led to poorer performance”
  • “Pay people enough to take the issue of money off the table. Pay people enough so they are not thinking about money they are thinking about the work.”
  • “3 factors lead to better performance: autonomy, mastery and purpose” [not additional cash rewards]
  • Open source software is created by highly skilled people contributing their time to collaborative projects that are then given away (such as Linux, Ruby, Apache). For large efforts their are often people paid by companies to contribute to the open source software but many people contribute 20-30, and more hours a week for free to such efforts, why? “Challenge, mastery and making a contribution”
  • “When the profit motive becomes unmoored from the purpose motive, bad thing happen. Bad things ethically sometimes, but also bad things like not good stuff, like crappy products, like lame services, like uninspiring places to work… People don’t do great things”
  • “If we start treating people like people… get past this ideology of idea of carrots and sticks and look at the science we can actually build organization and work life that make us better off, but I also think they have the promise to make our world a just a little bit better.”

The ideas presented emphasize respect for people, an understanding of psychology and validating beliefs with data. All of it fits very well with Deming’s ideas on management and the idea I try to explore in this blog. It isn’t easy to adjust your ideas. But the evidence continues to pile up against some outdated management practices. And good managers have to learn and adapt their practices to what is actually effective.

Related: Extrinsic Incentives Kill CreativityThe Trouble with Incentives: They WorkRighter IncentivizationIndividual Bonuses Are Bad Management

Posted in Creativity, Data, Deming, Management, Psychology, quote, Respect, Science | Tagged , , , , , , | 3 Comments

Finding Great Management Articles, Posts and Resources

Reddit is a web site that ranks web pages by user votes. The site uses an algorithm that has a very large timeliness factor. So top ranked links move down the list fairly quickly. This results in a nice site to look at to find links others have found interesting recently.

I created a management sub-reddit (a distinct topic-focused-area on the management improvement topics covered in this blog) in 2008. The sub-reddit seems to be about ready to reach a critical mass, so I am making a push to get those interested in management and specifically Deming, lean management, agile software development, six sigma and the things I normally write about on this blog to participate.

If you sign up you can not only vote on the links displayed but add new links (that then will be voted on by others). I think Reddit does a very good job of using social aspects of the internet to provide recommendations that are worthwhile (I have used the site for years).

The management subreddit depends on the community of users to voice their opinions. And I have an interest in having the community form around the management ideas I value (see my other blog posts for what that is). So I encourage you to give it a try and vote on links you enjoy and add new articles, web sites, blog posts… The benefit of this subreddit will grow as we grow the number of participants and if it develops a shared culture of value.

Related: Creating the Management Sub-Reddit (2008)John Hunter’s social site links (Reddit, Kiva, LinkedIn)Dell, Reddit and Customer FocusCurious Cat Management Improvement LibraryManagement Improvement Blog Carnival

Posted in Lean thinking, Management, Management Articles | Tagged , , , | 1 Comment

People Cannot Multitask

There is plenty of research showing that people can’t multitask. But this knowledge is missed by many people. Here is another study showing this: Why We Can’t Do 3 Things at Once

That’s because, when faced with two tasks, a part of the brain known as the medial prefrontal cortex (MFC) divides so that half of the region focuses on one task and the other half on the other task. This division of labor allows a person to keep track of two tasks pretty readily, but if you throw in a third, things get a bit muddled.

“What really the results show is that we can readily divide tasking. We can cook, and at the same time talk on the phone, and switch back and forth between these two activities,” said study researcher Etienne Koechlin [the broken link was removed] of the University Pierre et Marie Curie in Paris, France. “However, we cannot multitask with more than two tasks.”

I wouldn’t base my judgement on this one study. But we don’t have to. Multitasking decreases productivity. The siren song of multitasking. Multi-tasking: why projects take so long. What we should strive for is flow, the opposite of multi-tasking.

The real world often requires dealing with many interruptions (forcing you not to multi-task but to break up your tasks into fragments). Single piece flow shows the value (the efficient system performance) of getting one thing done then picking up the next. Many interruptions force you to keep stopping and starting tasks. People think they are multi-tasking but in fact they are just doing 4 tasks serially switching back and forth between them. Which slows them down and increases the odds of forgetting something. In these environments checklists are even more important than if you are not being interrupted frequently.

Related: costs of context switchingThe Multi-Tasking MythInterruptions Can Severely Damage Performance

Posted in Psychology, Quality tools | Tagged , , | 2 Comments

Management Improvement Carnival #98

Karen Wilhelm is hosting Management Improvement Carnival #98 on the Lean Reflections blog.

She highlights the LeanBlog Podcast #90 featuring Tim Turner, a plant team member at Toyota Kentucky, who compiled stories from 80 fellow team members from every level of the organization about what it feels like to be part of Toyota.

She also mentions the management “subreddit” which I have been encouraging people to use. The sites community votes to highlight management links they found valuable which provides some interesting suggestions reading. Some of the most popular links their in the last few weeks are:

Pete Abilla’s discussion of taking customer service agents for a little gemba walk and a quick activity to demonstrate a few lean fundamentals.

Who’s Got the Monkey?
A Harvard Business Review Classic (pdf) with some advice on how managers can avoiding getting stuck with difficult issues others want to pass on to them.

And How Zappos was Born: Place Bets on Passionate People by founder Tony Hsieh.

Posted in Carnival, Management | Tagged | Comments Off on Management Improvement Carnival #98

Mistake Proofing Deployment of Software Code

This is a continuation of my previous post: Improving Software Development with Automated Tests. Lets look at a typical poka-yoke example. A USB connector must be put in the right way up – for the connection to work properly and the communication to occur as intended. So to mistake proof the process the connector won’t allow the USB device to be put in upside down – the hardware connection designed to not allow that type of connection.

Using a deployment process that prevents code from being submitted that has an error follows a nearly identical process. The process blocks an error from being made. It seems to me a process that blocks code with a bug from being deployed with an error is the basically the same as a USB connection that will not accept the device being put in upside down.

Mistake proofing in no way should limit focusing on improving the process. Mistake-proofing a process both improves it (many poka-yoke solutions make the process easier to use) and prevents an error in case you still try something wrong. So I see the automated tests as a way to serve as a backstop, in case the process improvement you made to the software development process failed in some form. Then the automated testing required to deploy would prevent the introduction of that error to the production environment.

Related: Checklists in Software DevelopmentBaking in Quality to Software DevelopmentCombinatorial Testing for Software DevelopmentGreat Visual Instruction Example

Posted in Management, Quality tools, Software Development | Tagged , , , , | 6 Comments

Combinatorial Testing – The Quadrant of Massive Efficiency Gains

My brother, Justin Hunter, gives a lightning talk on Combinatorial Testing – The Quadrant of Doom and The Quadrant of Massive Efficiency Gains in the video above. The following text is largely directly quoted from the talk – with a bit of editing by me.

When you have a situation that has many many many possible parameters and each time only a few possible choices (a few items you are trying to vary and test – in his example in the video, 2 choices) you wind up with a ridicules number of possible tests. But you can cover all the possibilities in just 30 tests if your coverage target is all possible pairs. When you have situations like that you will see dramatic efficiency gains. What we have found in real world tests is greatly reduced time to create the tests and consistently 2 to 3 times as many defects found compared to the standard methods used for software testing.

You can read more on these ideas on his blog, where he explores software testing and combinatorial testing. The web base software testing application my brother created and shows in the demo is Hexawise. It is free to try out. I recommend it, though I am biased.

Related: Combinatorial Testing for SoftwareVideo Highlight Reel of Hexawise – a pairwise testing tool and combinatorial testing toolYouTube Uses Multivariate Experiment To Improve Sign-ups 15%What Else Can Software Development and Testing Learn from Manufacturing? Don’t Forget Design of Experiments (DoE)Maximize Test Coverage Efficiency And Minimize the Number of Tests Needed

Justin posted the presentation slides online at for anyone who is interested in seeing more details about the test plan he reviewed that had 1,746,756,896,558,880,852,541,440 possible tests. The slides are well worth reading.
Continue reading

Posted in Quality tools, Software Development | Tagged , , , , | 3 Comments