Children are Amazingly Creative At Solving Problems
Posted on July 8, 2014 Comments (1)
This story at NPR reminded my of Russell Ackoff talking about the creativity kids show in solving problems* – and how school often stifles that creativity.
This is flexible, fluid thinking — children exploring an unlikely hypothesis. Exploratory learning comes naturally to young children, says Gopnik. Adults, on the other hand, jump on the first, most obvious solution and doggedly stick to it, even if it’s not working. That’s inflexible, narrow thinking. “We think the moral of the study is that maybe children are better at solving problems when the solution is an unexpected one,” says Gopnik.
And that flexibility may disappear earlier than we think. Gopnik’s lab has also compared toddlers and kindergartners in doing these tests of abstract thinking, and found that the diaper set are actually better at focusing on the relationship between the objects, rather than on the things.
To those, like me, that use Deming’s ideas to help understand and improve management it is apparent these findings relate directly to two areas of Deming’s management system: psychology and theory of knowledge (how we know what we know).
Understanding how our psychology limits are effectiveness can be used to counter those tendencies.
And as Daniel Boorstin said:
“The greatest obstacle to discovery is not ignorance – it is the illusion of knowledge.”
Understanding the limits of our knowledge and our tendency to become rigid in our thinking can help us avoid blinding ourselves to options. Our brains overrule options without us consciously even knowing that is happening; it takes effort to overcome this tendency.
The Benefits of Blogging
Posted on July 3, 2014 Comments (0)
A couple of my quotes from the article:
One of the benefits I didn’t appreciate before I started was how blogging helps build your knowledge and understanding—in the same way teaching helps you learn the topic you are discussing in a deeper way.
I find myself more thoughtful and engaged with ideas because I think about how I can build on those ideas in a blog post. When I start writing, I sometimes realize I don’t actually understand the idea or topic as well as it seemed I did. So I must think about it more to be able to understand it well enough to write about it.
See the whole article to see the rest of my responses and thoughts from Mark Graban, Jennifer Stepniowski, Jimena Calfa and Daniel Zrymiak. The article is available for free, though you do have to register to view that article (registering will also let you view the other articles ASQ has made available to non-members).
Gerald Suarez on Creating the Future
Posted on June 25, 2014 Comments (2)
Without the proper foundation for planning for the future (contemplation and desire),
In talking to a senior executive at a Fortune 500 company about a promotion to VP that the executive doesn’t want to take because of all that accepting the VP position would require.
Gerald: But if you say yes it will ruin your life, which is worse?
I see similar situations and most of the time people “chose” career without much thought. They don’t think they have options. I am traveling around China now after presenting a seminar for The W. Edwards Deming Institute in Hong Kong.
I decided I didn’t want to spend my life working “9 to 5.” There are tradeoffs. It sure is nice having a nice paycheck every 2 weeks without much risk. But control of my life mattered more. My choice is more extreme than most. But I believe people need to consciously question what they want out of life and make those choices by considering their options. Too many people don’t take the time to realize they have many more choices than they ever consider.
Gerald quotes a very apt Turkish proverb
This is often hard, and gets harder the longer we are on the wrong road. Sunk costs often pull us in the direction of continuing on the path we invested so much in. It makes all the sense to turn back if it is the wrong path, but our psychology often makes it hard to act in that way.
Gerald’s book, Leader of One: Shaping Your Future through Imagination and Design, was just released.
Related: Transformation and Redesign at the White House Communications Agency (WHCA) Better Thinking About Leadership – Think Long Term, Act Daily – Build an Environment Where Intrinsic Motivation Flourishes – Dr. Russell Ackoff Webcast on Systems Thinking
Root Cause, Interactions, Robustness and Design of Experiments
Posted on June 18, 2014 Comments (0)
Eric Budd asked on The W. Edwards Deming Institute group on LinkedIn
If observed performance/behavior in a system is a result of the interactions between components–and variation exists in those components–the best root cause explanation we might hope for is a description of the interactions and variation at a moment in time. How can we make such an explanation useful?
A single root cause is rare. Normally you can look at the question a bit differently see the scope a bit differently and get a different “root cause.” In my opinion “root cause” is more a decision about what is an effective way to improve the system right now rather than finding a scientifically valid “root cause.”
Sometimes it might be obvious combination which is an issue so must be prevented. In such a case I don’t think interaction root cause is hard – just list out the conditions and then design something to prevent that in the future.
Often I think you may find that the results are not very robust and this time we caught the failure because of u = 11, x = 3, y = 4 and z =1. But those knowledge working on the process can tell the results are not reliable unless x = 5 or 6. And if z is under 3 things are likely to go wrong. and if u is above 8 and x is below 5 and y is below 5 things are in trouble…
To me this often amounts to designing systems to be robust and able to perform with the variation that is likely to happen. And for those areas where the system can’t be made robust for some variation then designing things so that variation doesn’t happen to the system (mistake proofing processes, for example).
In order to deal with interaction, learn about interaction and optimize results possible due to interactions I believe the best method is to use design of experiments (DoE) – factorial experiments.
George Box Webcast on Statistical Design in Quality Improvement
Posted on June 11, 2014 Comments (0)
George Box lecture on Statistical Design in Quality Improvement at the Second International Tampere Conference in Statistics, University of Tampere, Finland (1987).
Early on he shows a graph showing the problems with American cars steady over a 10 years period. Then he overlays the results for Japanese cars which show a steady and significant decline of the same period.
Those who didn’t get to see presentations before power point also get a chance to see old school, hand drawn, overhead slides.
He discusses how to improve the pace of improvement. To start with informative events (events we can learn from) have to be brought to the attention of informed observers. Otherwise only when those events happen to catch the attention of the right observer will we capture knowledge we can use to improve. This results in slow improvement.
A control chart is an example of highlighting that something worth studying happened. The chart will indicate when to pay attention. And we can then improve the pace of improvement.
Next we want to encourage directed experimentation. We intentionally induce informative events and pay close attention while doing so in order to learn.
Every process generates information that can be used to improve it.
He emphasis the point that this isn’t about only manufacturing but it true of any process (drafting, invoicing, computer service, checking into a hospital, booking an airline ticket etc.).
He then discussed an example from a class my father taught and where the students all when to a TV plant outside Chicago to visit. The plant had been run by Motorola. It was sold to a Japanese company that found there was a 146% defect rate (which meant most TVs were taken off the line to be fixed at least once and many twice) – this is just the defect rate before then even get off the line. After 5 years the same plant, with the same American workers but a Japanese management system had reduced the defect rate to 2%. Everyone, including managers, were from the USA they were just using quality improvement methods. We may forget now, but one of the many objections managers gave for why quality improvement wouldn’t work in their company was due to their bad workers (it might work in Japan but not here).
He references how Deming’s 14 points will get management to allow quality improvement to be done by the workforce. Because without management support quality improvement processes can’t be used.
With experimentation we are looking to find clues for what to experiment with next. Experimentation is an iterative process. This is very much the mindset of fast iteration and minimal viable product (say minimal viable experimentation as voiced in 1987).
There is great value in creating iterative processes with fast feedback to those attempting to design and improve. Box and Deming (with rapid turns of the PDSA cycle) and others promoted this 20, 30 and 40 years ago and now we get the same ideas tweaked for startups. The lean startup stuff is as closely related to Box’s ideas of experimentation as an iterative process as it is to anything else.
He also provided a bit of history that I was not aware of saying the first application of orthogonal arrays (fractional factorial designs) in industry was by Tippett in 1933. And he then mentioned work by Finney in 1945, Plackett and Burman in 1946 and Rao in 1947.
The Education System
Posted on June 8, 2014 Comments (1)
The current topic for ASQ Influential Voices to address is the importance of the education system and the impact on the capability of employees.
The education system is important and not very good in my opinion. As a kid I found it boring and constraining and a system designed more to extinguish my quest for knowledge than increase my desire to learn. As a kid I was told by adults that adults knew better and I shouldn’t complain.
I was told “don’t you realize you are in one of the best school systems in the USA?” With a bit of data I was convinced that seemed likely. To me this seemed like an even more ominous sign. If the best was this bad what was everything else like?
The argument that made the most sense to me (for why I should be happy with, or at least accept, the lousy system I was stuck in) was that as a kid I probably just didn’t understand why this environment that seemed to bore not just me, but most all the kids around me and this system that crushed our desire to learn must somehow be working otherwise the adults would certainly fix it.
As an adult what I find is my thoughts as a kid were essentially completely correct (except that last one that adults wouldn’t stick with some pitiful system without good reason) and plenty of education experts had been saying the same things. Adults seem perfectly fine not adopting proven better education practices just as they are fine not adopting proven better management practices.
When Dr. Deming was asked what to do instead of performance appraisal, when he railed against performance appraisal, he said do “whatever Peter Scholtes says.” To the question of what we should we do about the education system I say do whatever David Langford and Alife Kohn say.
I know more about the specifics of what educational systems following David Langford’s idea are like, and all I can say is they are wonderful. If I had kids I would definitely consider moving somewhere that had such a system (like Leander, Texas where they have been moving down that path for 20 years). They focus on helping student learn in a way that is so much more sensible than the one I had to sit through and most everyone reading this had to sit through.
The percentage of students that graduate with a desire to keep learning from an educational system like Leander is much greater than the traditional path. My high school had more National merit scholars than any public high school in the USA the year I graduated (some prep schools beat us, but only a few – partially because we were so large and they are often small). We had many students that were smart, dedicated and capable of succeeding at prestigious universities. Of course with tons of University of Wisconsin faculty as parents this is not a very surprising result.
Practicing Mistake-Promoting Instead of Mistake-Proofing at Apple
Posted on June 5, 2014 Comments (3)
Mistake proofing is a wonderful management concept. Design systems not just to be effective when everything goes right but designing them so mistakes are prevented.
I have had several bad customer experiences in the short time I have had my iPad mini. One of the most pitiful is caused by mistake-promoting process design. As the name implies that isn’t a good idea. Mistake-proofing processes is a good practice to strive for; processes that create extra opportunities for failure impacting customers negatively are a bad idea.
My experience below is but one mistake-promoting practice that has caught me in its grips in the short time I have owned my iPad mini. I want to view books on the mini but can’t find any book reader. So I decide, fine I’ll just install the Kindle reader app.
I go to do so (run into additional issues but get through them) and then Apple decides for this free app, on an iPad I just bought with my credit card a week ago, to block me from getting what I need and force me to revalidate my credit card. This is lame enough, but I am used to companies not caring about the customer experience, so fine, what hoops does Apple want to force me through?
But guess what, the unnecessary steps Apple decided to force me through are broken so I can’t just waste my time to make them happy. No. They have created a failure point where they never should have forced the customer in the first place.
So they not only didn’t mistake-proof the process they mistake-promoted the process by creating a unnecessary step that created an error that could have been avoided if they cared about mistake proofing. But instead they use a mistake-promoting process. As a consumer it is annoying enough to cope with the failures companies force me through due to bad management systems that don’t mistake proof processes.
Companies creating extra opportunities to foist mistakes onto customers is really something we shouldn’t have to put up with. And when they then provide lousy and then even incomprehensible “support” such the “change your name” vision Apple decided to provide me now it is time to move on.
After 5 years of buying every computing device from Apple, they have lost my entire good will in one week of mess ups one after the other. I knew the reason I moved to Apple, the exceptional Macbook Air, was no longer the unmatched hardware it once was; but I was satisfied and was willing to pay a huge iPad premium to avoid the typical junk most companies foist on you. But with Apple choosing to make the process as bad as everyone else there isn’t a decent reason to pay them a huge premium.
Toyota Post Record Profit: Splits $15 million in Pay and Bonus for top 21 Executives
Posted on June 2, 2014 Comments (0)
After posting record profits of $17.9 billion Toyota proposes to increase the pay and bonus for the top 21 executives to $14.9 million. That is not as you might expect just the increase in the bonus to the CEO. That is the entire pay and bonus for the top 21 executives. That places all 21 together below the top 50 CEO paydays in the USA.
Toyota’s net income for the year surged 89.5%. While the profits are partially due to good management at Toyota the decline in value of the yen also great aided results.
Toyota proposed 1.52 billion yen ($14.9 million) in combined compensation and bonuses to 21 directors, including President Akio Toyoda, in a notice to shareholders Tuesday. The Toyota City, Japan-based company paid 1.28 billion yen the previous fiscal year.
By comparison, total pay for union workers increased 8.2 percent on average from last fiscal year. The carmaker granted the union’s request for workers’ average bonus to rise to 2.44 million yen, the equivalent of 6.8 months of salary.
The company forecasts a 2% slip in net profit to $17.5 billion for 2015.
Toyota continues to generate cash flow extremely well and has over $20 billion in cash at the end of their 2014 FY. They are also increasing the dividend to stockholders and buying back more stock.
Less than a handful of USA CEOs that is took more from their companies treasuries than all 21 off the Toyota leaders take together led their company to greater earnings than Toyota (only a few companies earned more: Apple, Google, Exxon…). The thievery practiced by senior executives in the USA is immoral and incredibly disrespectful to the other workers at the company and the stockholders.
ExxonMobil did earn more and their CEO took $28.1 million. I think Chevron and Wells Fargo may have earned more than Toyota with a CEOs taking $20.2 and $19.3 million respectively.
Alan Mulally, Ford CEO, took $23.2 million while the company earned $7 billion. If you can ignore his massive and disrespectful taking what he doesn’t deserve he has been an acceptable CEO in other ways.
Building a Great Software Development Team
Posted on May 29, 2014 Comments (1)
Adam Solove: Why do you think that happened? They hired for passion, rather than experience?
If I had to pick one thing, passion would likely be it but really it is a complex assortment of things. Passion for the right things, based on what we aimed to be, mattered a great deal. That took the form of being passionate about the user experience, being passionate about good software development practices, being passionate about good software itself, being passionate about treating each other with respect, being passionate about learning and improving.
I think there were several other important factors, such as: the skill to turn a passion for good software into actual good software. This required intelligence, interest and knowledge about software development but didn’t require specific experience (computer science degree, 2 years of Ruby on Rails development, certification or any such thing). Hiring based on experience is a big mistake. In my opinion hiring based on capability and potential (which is based partially on experience) is wise.
Another factor is that we had people (those first few hires were critical) that were really knowledgable about programing good software and that became a self reinforcing process. The gaps one person’s ability and knowledge could be filled by someone else helping them understand and get better.
The expectation was that we found great solutions. If we didn’t we kept looking and asked each other for help (another factor in creating a great team). We didn’t just accept that we were confident the solution wasn’t very good but couldn’t find any better options so I guess this is the best we can do.
We were interested enough in good results that we would push for better options instead of just accepting something that was kind of ok. This shouldn’t be such a big deal; but in practice it is huge. So many places just end up avoiding conflict to the extent that it is a huge detriment to results.
Without confidence, honest debate about ideas is suppressed as people are constantly taking things personally instead of trying to find the best ideas (and if doing so means my idea is criticized that is ok). Our group was great at this. It is something I find it a bit silly to say a workplace was “great” at but in most places I find the fear of someone being concerned stifles discussion to an unbelievable extent.
This is also one of many areas where the culture within the team was self reinforcing. As new people came on they understood this practice. They saw it in practice. They could see it was about finding good ideas and if their idea was attacked they didn’t take it nearly as personally as most people do in most places. I sought to understand if people we looked at hiring would be comfortable in such an environment.
Cognition: How Your Mind Can Amaze and Betray You
Posted on May 27, 2014 Comments (0)
The webcast above is from the excellent folks at Crash Course. This webcast provides another view into the area of Deming’s management system on the theory of knowledge (the one most people forget), how we know what we know and how that belief isn’t always right.
Two of the four components of Dr. Deming’s management system were about our brains (psychology is the other) which makes a great deal of sense when you think about how focused he was on the human element in our organizations (and the others are viewed significantly by how they interact with our brains – how we view variation, how we often fail to look at the whole system when drawing conclusions, etc.).
I believe most people don’t give nearly enough attention to theory of knowledge especially and also psychology within the context of an organization. They are a bit messy and vague and dependent and not easy to create simple cut and paste instructions for how to manage. This webcast takes a different look at it without connections back to management but I think most people need to spend more time thinking about these ideas. This video can help you do that.
If you are constantly (multiple times a minute in this video) seeing the connections with Deming and how the points relates to management that is a good sign. If not, that probably means you should spend more time reading and thinking about the theory of knowledge and psychology (see managing people posts).
A Good Management System is Robust and Continually Improving
Posted on May 22, 2014 Comments (2)
This is a fairly good quote on a good management system. Some people might not like the mechanistic model – comparing an organization to a clock, and I agree that isn’t the right model, but even so it is a good quote.
The quote, from a story about the San Antonio Spurs captures what should happen with a good management system. Things just keep running well as inevitable changes take place (and keep getting better in the case of a management system).
A good management system doesn’t rely on heroic efforts to save the day. The organization is designed to success. It is robust. It will succeed with all the variation thrown at it by the outside world. A good management system takes advantage of the contributions people offer, but it is not perform poorly when others are relied on.
A well run organization has graceful degradation (when one component fails or one person is missing the performance doesn’t suffer, bad results are avoided).
An organization succeeds because of the efforts of many great people. But the management system has to be created for an organization to prosper as what we all know will happen, happens: people will leave and need to be replaced. And the people that stay will need to adjust to new conditions inside the organization and in response to external forces. A good management system is constantly improving performance, innovating, increasing the robustness of systems and increasing the capability of people.
Related: Bad Weather is Part of the Transportation System – How to Sustain Long Term Enterprise Excellence – Performance dependent on specific individuals is not robust and not capable of continuous high quality performance – European Blackout: Human Error-Not
Your Purpose Must Be About You
Posted on May 19, 2014 Comments (1)
Guest post by Jurgen Appelo
I’m a writer. It’s the one thing that I intend to do for the rest of my life. That means, when I focus on writing, I cannot focus on knitting. Somebody else will have to do the knitting, so I can focus on the writing. And maybe later, I can trade my wonderful book for someone’s beautiful sweater. This concept applies to all other professionals too. Everyone is entangled in a web of economic dependencies, and therefore, the purpose you choose for yourself should somehow generate value for the others around you. Or else nobody will give you a knitted sweater.
This all makes perfect sense to complexity scientists, who have known for a while that complex adaptive systems find a global optimum through local optimizations and interdependencies. (At Home in the Universe by Stuart Kauffman) The parts in a complex system all try to optimize performance for themselves, but their efforts depend on the dependencies imposed on them by the parts around them. With a mix of competition and collaboration, the parts interact with each other without any focus on a global purpose. Nevertheless, the end result is often an optimized system. Biologists call it an ecosystem. Economists call it an economy. I call it common sense.
Putting the “Why” in Your Mission Statement
Most management scholars and experts have ignored the insights from the complexity sciences (or are unaware of them) and some have suggested goals for teams, and purposes for businesses, that are too narrow. There are many corporate mission statements in the world expressing ideas such as, “Make money for shareholders”, “Put customers first”, and “Achieve superior financial results” (The Leader’s Guide to Radical Management by Stephen Denning). In each of these cases, the purpose of the organization is (too) narrowly defined as providing value to one type of client or stakeholder.
George Box Articles Available for a Short Time
Posted on May 14, 2014 Comments (0)
George E. P. Box died in March 2013. He was a remarkably creative scientist and his celebrated professional career in statistics was always at the interface of science and statistics. George Box, J. Stuart Hunter and Cuthbert Daniel were instrumental in launching Technometrics in 1959, with Stu Hunter as the initial editor. Many of his articles were published in the journal. Therefore we think it is especially fitting that Technometrics should host this on-line collection with some of his most memorable and influential articles.
They also include articles from Journal of the American Statistical Association and Quality Engineering. Taylor & Francis is offering these articles freely in honor of George Box until December 31st, 2014. It is very sad that closed science and engineering journals block access to the great work created by scientists and engineers and most often paid for by government (while working for state government universities and with grants organizations like the National Science Foundation[NSF]). At least they are making a minor exception to provide the public (that should be unlimited access to these works) a limited access to these articles this year. These scientists and engineers dedicated their careers to using knowledge to improve society not to hide knowledge from society.
Some of the excellent articles make available for a short time:
- A Useful Method For Model-Building by George E.P. Box and William G. Hunter, Technometrics Volume 4 Issue 3 (1962)
- Science and Statistics by George EP Box, Journal of the American Statistical Association (1975)
- An Analysis for Unreplicated Fractional Factorials by George E.P. Box and R. Daniel Meyer, Technometrics (1986)
- Is Your Robust Design Procedure Robust? by George Box and Conrad Fung, Quality Engineering, (1994)
The “virtual issue” includes many more articles.
Interview on PDSA, Deming, Strategy and More
Posted on May 8, 2014 Comments (2)
Bill Fox interviewed me and has posted part one of the interview on his web site: Predicting Results in the Planning Stage:
John: I would say the PDSA improvement cycle and a few key practices in using the PDSA properly like predicting the results in the plan stage—something that a lot of the times people do not do—to determine what would be done based on the results of that prediction.
People discover, especially when they’re new to this stuff, regarding the data that they’re collecting, that maybe even if they got the results they are predicting, they still don’t have enough data to take action. So you figure that even if that number is 30, they would need to know three other things before they make the change. So then, in the plan stage, you can figure that you need to address these other issues, too. At any time that people are collecting data is useful to figure out, for instance: “What do we need to do if the result is 30 or if the result is 3?” And if you don’t have any difference, why are you collecting the data?
Another important piece is the D in Plan, Do, Study, Act. It means “do the experiment”. A lot of times, people get confused into thinking that D means deploy the results or something like that, but thinking of D as ‘doing the experiment’ can be helpful.
A really big key between people that use PDSA successfully and those who don’t is that the ones that do it successfully turn the cycle quickly.
John: I would say that there are a couple. The followers that want to pin everything to Deming tend to overlook the complexities and nuances and other things.
The other problem is that some of the critics latch on to a specific quote from Deming, something like a one-sentence long quote, and then they extrapolate from that one sentence-long quote what that means. And the problem is that Deming has lots of these one-sentence quotes that are very memorable and meaningful and useful, but they don’t capture every nuance and they don’t alone capture what it really means (you need to have the background knowledge to understand it completely).
They are sort of trying to oversimplify the message into these sound bites, and I find that frustrating. Because those individual quotes are wonderful, but they are limited to one little quote out of hours of videotape, books, articles, and when you don’t understand the context in which that resides, that’s a problem.
See the full interview for more details and other topics. I think it is worth reading, of course I am a bit biased.
More Evidence of the Damage Done by Kleptocrat CEO Pay
Posted on April 21, 2014 Comments (1)
I have been writing about the problems of overpaid executives that has lately become so bad that verbiage understand the nature of the problem. Today I see many CEO’s are acting as kleptocrats do – taking food out of others mouths to build their castles. The damage done to everyone else involved is of no concern. Both groups love bankers that flood them with cash for new and larger castles at the expense of the futures of their company (or country).
This paper does a very good job of providing more evidence of the damage done by these kleptocrat CEOs and their apologists.
Are Top Executives Paid Enough? An Evidence-Based Review by Philippe Jacquart and J. Scott Armstrong
Many of the problems with the poor thinking around executive pay stem from the failure to grasp ideas Dr. Deming wrote about decades ago.
The quote from their paper show a failure to understand variation (attributing variation to those near the variation at the time – good marks when the variation is good, bad marks when it is bad). And a failure to understand the organization as a system (the results of any subsystem are greatly influenced by the whole system and the conditions outside the system (the economy, the macro-economic conditions for the industry…). And a failure to understand the theory of knowledge: people should know our brains leap to causation explanations when the evidence doesn’t support it. Then confirmation bias and psychology lead us to accept the data that supports our biases.
You see this just looking at the money heaped onto executives (in addition to the already huge payments taken) in industries whenever those industries (not individual companies, the entire industry) have macro-economic windfalls.
Innovative Thinking at Amazon: Paying Employees $5,000 to Quit
Posted on April 15, 2014 Comments (1)
Amazon continues to be innovative not just in technology but with management thinking. Jeff Bezos has rejected the dictates espoused most vociferously by Wall Street mouthpieces and MBAs that encourage short term thinking and financial gimmicks which harm the long term success of companies.
Most CEOs and executives are too fearful or foolish to ignore what they are told they must do because Wall Street demands it. CEO’s and boards often ratchet up the poor management thinking by tying big bonuses to financial measures which are much more easily achieved by gaming the system than by improving the company (so companies get the games there boards encouraged through their financial extrinsic motivation focus).
Amazon does many good things focused on making Amazon a stronger company year after year. These innovative management practices seem to largely be due to the thinking of the strong willed founder and CEO: Jeff Bezos. Jeff was smart enough to see the great things being done at Zappos by Tony Hsieh and bought Zappos.
Jeff Bezos has added his letter to shareholders to Warren Buffett’s (for Berkshire Hathaway) as letters worth reading each year. In the latest Amazon letter he includes many worthwhile ideas including:
The second program is called Pay to Quit. It was invented by the clever people at Zappos, and the Amazon fulfillment centers have been iterating on it. Pay to Quit is pretty simple. Once a year, we offer to pay our associates to quit. The first year the offer is made, it’s for $2,000. Then it goes up one thousand dollars a year until it reaches $5,000. The headline on the offer is “Please Don’t Take This Offer.” We hope they don’t take the offer; we want them to stay. Why do we make this offer? The goal is to encourage folks to take a moment and think about what they really want. In the long-run, an employee staying somewhere they don’t want to be isn’t healthy for the employee or the company.
A third inward innovation is our Virtual Contact Center. It’s an idea we started a few years back and have continued to grow with terrific results. Under this program, employees provide customer service support for Amazon and Kindle customers while working from home. This flexibility is ideal for many employees who, perhaps because they have young children or for another reason, either cannot or prefer not to work outside the home.
The first point reinforces Dr. Deming’s words encouraging companies to do exactly that – pay for education even if it wasn’t related to the work the employee was doing or would do for the company. Still quite rare decades after Deming’s advice.
Toyota Understands Robots are Best Used to Enhance the Value Employees Provide
Posted on April 8, 2014 Comments (0)
Toyota has always seen robotics as a way to enhance what staff can do. Many USA executives think of robotics as a way to reduce personnel. Toyota wants to use the brainpower of employees to continually improve the organization. Toyota wants to free people for monotonous or dangerous work to let them use their minds.
Humans are taking the place of machines in plants across Japan so workers can develop new skills and figure out ways to improve production lines and the car-building process.
“We cannot simply depend on the machines that only repeat the same task over and over again,” Kawai said. “To be the master of the machine, you have to have the knowledge and the skills to teach the machine.”
Kawai, 65, started with Toyota during the era of Taiichi Ohno, the father of the Toyota Production System envied by the auto industry for decades with its combination of efficiency and quality. That means Kawai has been living most of his life adhering to principles of kaizen, or continuous improvement, and monozukuri, which translates to the art of making things.
“Fully automated machines don’t evolve on their own,” said Takahiro Fujimoto, a professor at the University of Tokyo’s Manufacturing Management Research Center. “Mechanization itself doesn’t harm, but sticking to a specific mechanization may lead to omission of kaizen and improvement.”
We need more companies to learn from the executives at Toyota. They show real respect for people. They are not focused on how much they can extract from the corporate treasury to build themselves castles at the expense of other employees, customers and stockholders as far too many USA executives are.
Toyota has been extremely innovative in investing in robotics as human assistants (partially this is due to the extreme demographic problems Japan faces): Toyota Develops Thought-controlled Wheelchair – Toyota’s Partner Robot – Toyota Winglet – Personal Transportation Assistance.
Steve Jobs on Quality, Business and Joseph Juran
Posted on March 31, 2014 Comments (1)
This webcast shows an interesting interview with Steve Jobs when he was with NeXT computer. He discusses quality, business and the experience of working with Dr. Juran at NeXT computer. The video is likely from around 1991.
We are being out-planned, we are being out-strategized, we are being out-manufactured. It there is nothing that can’t be fixed but we are not going to fix it up here, we are going to fix it by getting back to the basics.
I agree with this thought, and while we have made some progress over the decades since this was recorded there is a long way to go (related: complacency about our contribution the USA has received from science and engineering excellence – when you were as rich as the USA was in the 1950s and 1960s more and more people felt they deserved to be favored with economic gifts without effort (forgetting the basics as Jobs mentioned) – Silicon Valley Shows Power of Global Science and Technology Workforce). After World War II the USA was able to coast on an economic bubble of extreme wealth compared to the rest of the world for several decades (and the economic success built during that period even still provides great advantages to the USA). That allowed wealthy living conditions even without very good management practices in our businesses.
Quality isn’t just the product or service. Its having the right product. Knowing where the market is going and having the most innovative products is just as much a part of quality as the quality of the construction of the product. And I think what we are seeing the quality leaders of today have integrated that quality technology well beyond their manufacturing.
Now going well into their sales and marketing and out as far as they can to touch the customer. And trying to create super efficient processes back from the customer all the way through the delivery of the end product. So they can have the most innovative products, understand the customer needs fastest, etc..
The importance of customer focus is obvious at the companies Jobs led. It wasn’t a weak, mere claim of concern for the customer, it was a deep passionate drive to delight customers.
Analysis Must be Implemented by People to Provide Value
Posted on March 25, 2014 Comments (0)
Guest Post by Bill Scherkenbach
Every time I look at this picture, I think of Dr. Deming’s words to drive out fear and take joy in your work. We were talking in my home office when Sylvester saw a good lap and took it. Our conversation immediately shifted when both Dr. Deming and Sylvester started purring.
The greatest statistical analysis is nothing if it can’t be implemented by people. But people learn in different ways. Some like good stories, others like pictures. Only a few like equations. Dr. Deming always liked a good laugh; and a good purr.
By what method do you get your analyses implemented?
Related: How to Get a New Management Strategy, Tool or Concept Adopted part 1 and part 2 – Getting Known Good Ideas Adopted – Respect People by Creating a Climate for Joy in Work – Playing Dice and Children’s Numeracy
Deming and Software Development
Posted on March 17, 2014 Comments (1)
I am sometimes asked about how use Deming’s ideas on management in a software development context. My belief is Deming’s ideas work extremely well in a software development context. The main issue is often unlearning some assumptions that people might have about what the Deming management system is.
It really is surprising to me how many “knowledge workers” respect Deming ideas but then say his attempts to treat factory workers as thoughtful people who should be respected and involved in improving their processes doesn’t make sense for them because they are “knowledge workers.”
There are many good things being done to improving the software development process. I think many of them are very Deming-like in their approaches (but to me miss out on aspects of the Deming management system that would be helpful). I think Dr. Deming’s approach to software development would focuses on the system of profound knowledge (the 4 inter-related areas below):
- Understanding variation – software development has quite a bit of variation, some probably innate [unique work] and some due to not having good procedures, batching work, not fixing problems right when they are seen, quick fixes that leave the system venerable in the long term (when you make one simple change to the code it has an unanticipated consequence due to poor practices that could have been eliminated), etc.. Many good coding practices are effective strategies to deal with this issue. And building an understanding of variation for managers (and business process owners/product owners) is very helpful to the software development process. The ideas in agile and kanban of focusing on smaller delivery units of work (one piece flow, just in time, cycle time…), customer value, maintainable code, sustainable work conditions, etc. are directly found in a Deming management system.
- Appreciation for the system of software development. Don’t just complain about bugs. Examine the process of development and then put in place mistake proofing efforts (don’t duplicate code, use integrated regression tests, don’t put artificial constraints on that result in system distortions – unrealistic targets…). Use things like kanban, limited work in progress, delivering value to customers quickly, think of success in terms of getting working software to customers (not meeting internal delivery goals), etc. that take into account our experience with systemic software development problems over the decades.
- Theory of knowledge – how do we know what we know? Are estimates reliable? Lets look at what users do, not just what they say (A/B testing…). Software developers often appreciate the value of usability testing, even though they rarely work for organizations willing to invest in usability testing. In my experience when software developers object to usability testing it is normally really an objection to overwork, and the usability testing is just going to give them more work or criticize things they were not allowed to spend the time they needed to do great work. That won’t always be the reason but it is the main one in my experience (I suppose their is also fear and just the psychology of not wanting to hear anything negative about what has been created – even if the usability testing shows tons of great results people will often focus on the negative).
- psychology and respect for people – This pretty much seems like it is the same for software development as everywhere else.