Interesting lecture on Statistical Learning as the Ultimate Agile Development Tool by Peter Norvig. The webcast is likely to be of interest to a fairly small segment of readers of this blog. But for geeks it may be interesting. He looks at the advantages of machine learning versus hand programming every case (for example spelling correction).
Google translate does a very good job (for computer based translation) based on machine learning. You can translate any of the pages on this blog into over 30 languages using Google translate (using the widget in the right column).
Personally I believe all 7 of those diseases are still prevalent and causing damage. I do think some progress has been made on longer term thinking but far too many organizations still are extremely short term focused. And I would add two new deadly diseases of management: excessive executive compensation and an outdated intellectual property system.
This lean thinking webcast from India actually does a pretty decent job of providing an overview (for a business TV channel) even if they get some things a bit confused. The discuss TQM in India preceding lean which is an accurate view in my opinion – quality management shared many lean principles. They even talk of lean at Ford doing lean first. But they get the decades for that a bit off. They seem to mash together the “quality is job one” refocus on quality lead by Dr. Deming in the 1980’s with Henry Ford in the early 1900’s.
The webcast includes Jim Womack discussing lean thinking. He mentions the misunderstanding of lean as primarily cost cutting.
Nice webcast by Martin Fowler, Three Years of Real-World Ruby. This talk is probably only of interest to those of you in software development, but for them I think it is an excellent presentation.
At work we have been use Ruby for the last 3 years and have found it to be a powerful language that helps make writing software applications fun. And that is important. By providing a powerful language and a rails framework that takes away much of the drudgery of writing code you can create an environment where develops are happy and productive. We are hiring, by the way.
The talk provides a good background on their experience using ruby to manage projects; and how they manage ruby application development projects.
Unfortunately companies like United have created cultures where people take pride in doing their job poorly. And the continued long term customer hostility companies take shows no sign of letting up. My suggestion is to take Southwest or Jet Blue (or Singapore Airlines or Cathay Pacific).
Unfortunately sometimes you need to travel somewhere that no airline that cares about customer service flies. Then just hope somehow the broken system you must trust to get you someplace somehow doesn’t fail you too badly. Or you can follow the increasingly common trend and publicize the horrible service you were subjected to, in your blog or perhaps your own webcast.
Nice talk on fear of looking foolish. The speakers discuss the idea that visibility is good. Don’t hide. Make everything visible and the benefit from many people’s ideas. The talk focuses on software development but is true for any work.
“criticism is not evil” – Very true. “At Google we are not allowed to submit code until there is code review.” At the bottom line they are repeating Deming’s ideas: improve the system – people are not the problem, bad systems are the problem. Iterate quickly.
Dr. Ackoff is one of two management thinkers that any manager, that is serious about improving management results in their organization, should study (the other is Dr. Deming). There are plenty of others that are also great resources. From part 2 of his talk: “Why-questions, about objects called systems, cannot be answered by the use of analysis… The product of explanation is understanding… The product of analysis is how things work, never why they work the way they do. Explanations always lie outside the system, never inside it.”
Synthesis (thinking about systems) involves 3 steps: 1) what is this system of which this is a part of; 2) understanding the behavior of the containing whole; 3) identify the role of function of the system in question within the containing system. Every system is defined by its role in the larger system.
Joel Spolsky webcast on creating Stack Overflow (with the goal of providing answers to professional programmers) using ideas from anthropology. Once again he provides great information. This is particularly interesting for software development but also just a good presentation for understanding the importance of customer focus and systems thinking.
Various techniques are used to ensure a quality (no red bead) product. There are quality control inspectors, feedback to the workers, merit pay for superior performance, performance appraisals, procedure compliance, posters and quality programs. The foreman, quality control, and the workers all put forth their best efforts to produce a quality product. The experiment allows the demonstration of the effectiveness (or ineffectiveness) of the various methods.