Posts about webcast

Joel Spolsky Webcast on Creating Social Web Resources

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.

What they focused on and did:

  • Voting – Reddit… (see our management Reddit)
  • Tags – lets you see what you want and to block tags you don’t want to see.
  • Editing – letting users edit the questions and responses. For a technical question and answer system this is very useful (based on my experience).
  • Badges – people like to earn “credit” (psychology)
  • Karma – “people are willing to do for free what people are not willing to do for small amounts of money” (psychology)
  • Pre-search – provide quick view of previously answered questions
  • Google is UI – Assumption: “the front page is Google search” – build based on the idea people will search via Google
  • Performance – 16 million pages a month with 2 web servers. They are using the Microsoft stack, not open source.
  • Critical mass – they focused on getting a large user base on day one of the beta site

Related: posts related to Joel SpolskyDell, Reddit and Customer FocusInformation Technology and ManagementWhat Motivates Programmers?

Red Bead Experiment Webcast

Dr. Deming used the red bead experiment to present a view into management practices and his management philosophy. The experiment provides insight into all four aspects of Dr. Deming’s management system: understanding variation, understanding psychology, systems thinking and the theory of knowledge.

Red Bead Experiment by Steve Prevette

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.

Related: Fooled by RandomnessPerformance Measures and Statistics CoursePerformance without AppraisalExploring Deming’s Management IdeasEliminate Slogans

The Importance of Making Problems Visible

Great, short, presentation webcast by Jason Yip showing the importance of making problems visible. Anyone interested in software development should watch this, and it is valuable for everyone else, also. Great visuals.

Related: Future Directions for Agile ManagementAgile Software Development SlideshowLeading Lean: Missed OpportunityInformation Technology and ManagementCurious Cat Micro-financiersposts on project managementToyota Institute for Managers

ER Checklist

The popular ER TV show highlighted the importance of using checklists in surgery yesterday.

Such powerful quality tools, like the checklist, are just waiting to be used. But far too many fail to use these simple improvement tools. And in health care those failures are potentially critical.

Related: Checklists Save LivesThe Power of a Checklistmanagement improvement dictionaryArticles on Improving the Health Care System

Applying Disruptive Thinking to the Healthcare Crisis

The Innovator’s Prescription: A Disruptive Solution to the Healthcare Crisis

Christensen spies symptoms of such disruptions bubbling up in the healthcare industry, such as molecular diagnostics, imaging technologies and high bandwidth telecom, and business model innovations. Integrated health systems like Kaiser Permanente have a leg up in deploying and optimizing these disruptive technologies.

The push for widespread healthcare reform must come from employers, who in spite of their declared intent to cut healthcare costs also know “they profit when their employees are healthy and productive.” Affordable healthcare, he concludes, “doesn’t come by expecting high end, expensive institutions or expensive caregivers to become cheap, but by bringing technology to lower cost providers and venues of care, so they can become more capable.”

Clayton Christensen is the rare management thinker that I feel real provides profound insights into thinking about management. There are many other good management thinkers that offer valuable idea, just most of them (in my opinion) really are presenting material in ways that offer managers a good way to take action on all the long known good management ideas that we fail to adopt successful for decades.
Continue reading

Management Improvement Carnival #54

In the webcast, Corey Ladas discusses lean thinking in software development, Deming and quality, customer pull vs Kano model and gemba.

  • 7 Practical Ways to Respect People by Ron Pereira – “Some think that to be respectful you can never disagree. This is ridiculous. My old boss at Nokia used to tell his management team that if all 8 of us agreed he had 7 too many people in the room. So true.”
  • Is Brainstorming a Waste of Time? by Mark McGuinness – “For Sutton, the problem isn’t with the technique but the way it’s applied: ‘when brainstorming sessions are managed right and skillfully linked to other work practices, they can promote remarkable innovation.’”
  • The Remarkable Chief Engineer by John Shook – “So the Chief Engineer has no choice but to lead by the soft skills of true leadership. By soft skills, I am referring to the suite of skills written of in books about leadership or management books and taught in leadership training – characteristics such as ‘leading through influence’ or ‘servant leadership’ or ‘win-win negotiating’.”
  • Yet another form of muda by Dan Markovitz – “You’ll learn, among other things, that making an ironclad commitment to spend 15 or 20 minutes each day with your assistant is essential. Your assistant is there to extend your reach and capability to effect change in the organization.”
  • Continue reading

Failure: Honda’s Secret to Success

Related: Honda has Never had Layoffs and has been Profitable Every YearInside Honda’s BrainCurious Cat Engineering Blog

Management Improvement Carnival #48

Nicole Radziwill is hosting the Management Improvement Carnival #48 on the Quality and Innovation blog, highlights include:

  • With so much focus on Mumbai this week, Joe Munte’s post on the dabbawallas of Mumbai focuses on a illuminating and positive aspect of the dynamic city that provides lessons for effective management…
  • Keep it simple! Checklists and Change Programs by Crossderry is a couple months old – but I still like it. It provides a “useful reminder to avoid a common error made when PMOs first implement processes and controls – over-engineering”…
  • John Hunter reflects on Management at Google, and features a video of Schmidt and Hamel chatting. I am a big fan of Google because they skillfully implement effective, agile quality systems in an environment highly conducive to innovation…

This edition of the carnival is the first on our new schedule: we will now be publishing 3 times a month. Submit your nominations for management posts to include in future editions. The Quality and Innovation blog is the 6th blog to host the carnival, the others are: Evolving Excellence, Lean Blog, Lean Six Sigma Academy, Capable Blog and our own Curious Cat Management Improvement Blog.

Eric Schmidt on Management at Google

   
Eric Schmidt speaks at the Management Lab Summit on May 29, 2008 in Half Moon Bay, California. Conversation with Professor Gary Hamel.

  • “The culture can be thought of as a ship and iterate culture with transparency for what people are doing. And that model scales pretty well.”
  • “I have two jobs, two roles. The first is to make sure every issue that is important is really debated to find, not the common outcome, but the best decision… second thing is to put pressure to make it happen quick.”
  • “it [managing better] starts with listening, it has to do with curiosity
  • “everything has to be based on some fact”
  • “It’s only about the people.” [respect for people is critical, Google really acts as though the people are their most important asset - John].
  • “What is the number 1 goal of the company? It is end user happiness with search. What is the number 2 goal? It’s end user happiness with advertising. What is the number 3 goal? The construction of the Google network of partners to effectuate the first two. What is the number 4 goal? To grow and scale the business… You will eventually get extraordinary returns for your shareholders and maximize advertiser happiness if all those things happen… There are a lot of business executives that get confused on what the goal is and they think that shareholder value is the goal. Shareholder value is a consequence of the goal.”

Related: Eric Schmidt Podcast on Google Innovation and EntrepreneurshipInterview with Google CEO Eric SchmidtInnovation at GoogleGoogle: Experiment Quickly and OftenMarissa Mayer Webcast on Google InnovationGoogle Management by Gary HamelLarry Page and Sergey Brin Interview Webcast

Ford’s Camaçari Plant in Brazil

photo of Fords' Camacari plant in Brazil

Brazil’s Camaçari plant is model for the future

This state-of-the-art manufacturing complex in the northeastern Brazilian state of Bahia is not only the centerpiece of Ford’s Brazilian turnaround plan, it is also one of the most advanced automobile plants in the world. It is more automated than many of Ford’s U.S. factories, and leaner and more flexible than any other Ford facility. It can produce five different vehicle platforms at the same time and on the same line.

At Camaçari, more than two dozen suppliers operate right inside the Ford complex, in many cases producing components alongside Ford’s main production line. Having those supplier operations on-site allows Ford to take the concept of just-in-time manufacturing to a whole new level. Inventories are kept to a bare minimum, or dispensed with entirely. Components such as dashboard assemblies flow directly into the main Ford assembly line at the precise point and time they are needed.

Unlike many U.S. auto plants, where workers’ responsibilities are strictly limited to specific job classifications, workers like Silva dos Santos are encouraged to learn as many different skills as possible.

Here is an interesting video on the plant. It is sad how poor management at GM, Ford and Chrysler has created such a bad situation for those working at those companies, their suppliers, the communities that support their production… GM and Ford had the advice they needed to succeed from Deming in the 1980′s but they chose to focus on the short term, large executive payments, accounting gimmicks instead of continual improvement…

They each have improved over the years, but the standard is not just improving but doing so effectively and enough and they failed at that. The UAW shares some responsibility for failing to successfully lead their workers to a promising future but management is much more responsible for the failure in my opinion (the video and article try to say Ford wants to be innovative in the USA but the UAW won’t let them). It is management’s jobs to focus the organization on cooperation and success for all stakeholders. When management is more concerned with getting themselves huge payoffs (from the pockets of the other stakeholders) and then try to blame one of those other stakeholders for fighting management is disingenuous. Executive’s contempt for other stakeholders leads to the other stakeholders feeling that they should be just as greedy as management.

Related: Ford’s Wrong TurnFord and Managing the Supplier RelationshipGlobal Manufacturing Data 2007Toyota’s New Texas PlantWomack Podcast on GMVW Phaeton Manufacturing plant
Continue reading

Webcast on the Toyota Development Process

Kenji Hiranabe talks about Toyota’s development process (webcast). Kenji shares a presentation he attended earlier this year by Nobuaki Katayama, a former Chief Engineer at Toyota, and the lessons he learned from him.

The webcast takes awhile to get going. If you are impatient you might want to start at the 6 minute mark. Some thoughts from the talk:

  • Voice of the Customer is diffuse. A strong concept (for a project – new car for example) is very important to focus thought, listening to voice of the customer is important but must use strong concept to avoid losing focus (due to diffuse customer feedback).
  • Honest face to face communication is important. Bad news first – present bad news first [don't try to hide bad news - my thoughts in brackets, John Hunter].
  • Everyone must think about cost reduction, many efforts add up to big impact [the importance of reducing waste everywhere].
  • benchmark, not to copy others, but to learn from what others do well.

The webcast includes a nice (though short) discussion of agile management in software development and lean manufacturing (the different situation of manufacturing versus software development). Kenji Hiranabe has also translated several agile and lean books into Japanese including Implementing Lean Software Development.

Related: Kenji Hiranabe’s blogMarissa Mayer Webcast on Google InnovationArticles and webcasts by Mary PoppendieckFuture Directions for Agile ManagementInterview with Toyota President

Hiring the Right Person

Malcolm Gladwell presented at the New Yorker conference on the Challenge of Hiring in the Modern World. As usually, he provides some great thoughts. I wrote on Hiring the Right Workers

The job market is an inefficient market. There are many reasons for this including relying on specification (this job requires a BS in Computer Science – no Bill Gates you don’t meet the spec) instead of understanding the system. Insisting on managing by the numbers even when the most important figures are unknown and maybe unknowable. Using HR to find the right person to work in a process they don’t understand (which reinforces the desire to focus on specifications instead of a more nuanced approach). The inflexibility of companies: so if a great person wants to work 32 hours a week – too bad we can’t hire them. And on and on.

Malcolm Gladwell doesn’t use the same language but I think he says many of the same ideas: “Insisting on managing by the numbers even when the most important figures are unknown and maybe unknowable.” etc. This idea he frames as a mismatch problem.

Related: Hiring: Silicon Valley StylePeople are Our Most Important AssetMalcolm Gladwell SynchronicityHiring, Does College Matter?Interviewing and Hiring ProgrammersGladwell (and Drucker) on Pensions

Future Directions for Agile Management

Agile management (agile software development specifically) is something that makes a big difference in my work life. David Anderson consistently provides great ideas on agile management and he does so again in this 90 minute presentation on the future directions for agile. As I learned about agile software development, what I saw was a great implementation of management improvement practices focused on software development that was very compatible with Deming’s management philosophy and lean thinking practices. The Agile manifesto:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

The first line can seem to be at odds, but I think in practice it is not – though I admit it may seem that way based on the importance placed on process by Deming (I think you have to read on agile to understand why this is the case). For my use of agile software develop, a highlight of the most important ideas is:

  • Deliver working systems quickly (with limited features, add features based on user needs) – [management improvement practice: PDSA, pilot ideas on a small scale, go to the gemba (don't sit in conference rooms talking about what might be an issue for the computer application you want to see in 6 months, create working systems and then continually improve it)]
  • Build systems that cope well with uncertainty and allow for constant continuous improvement of processes (with IT systems that can adjust as needed to changing business conditions and desires) – [continual improvement - what is good enough today is not good enough next year]

Important concepts addressed by agile management: highly collaborative, risk tolerance, systems thinking, customer interaction, craftsmanship ethic [joy in work], eliminate waste. Great quote from the webcast:

What we know about knowledge work, and software engineering, is that coordination cost grow non-linearly with batch size. We’ve known this since Greg Brooks published the Mythical Man Month, probably longer than that. So that is a key difference with manufacturing, coordination costs do not grow with batch size in manufacturing.

Related: Kanban In Software EngineeringManagement Science for Software EngineeringImproving Communicationwebcast of David Anderson talking about applying Agile and Deming’s ideas at MicrosoftWhat is Agile Software Development?

Engineering Innovation

In the webcast Dean Kamen discusses his latest innovation: robotic arms for people (amazing stuff). Once again he is doing great stuff. It is great what engineers can do (many worked together to get the progress so far) when given the opportunity. We need many more such efforts.

The research was funded by DARPA. DARPA, for those that don’t know, also made reading this blog possible. They funded the development of the internet. I was giving a talk, while I was working for the Office of Secretary of Defense Quality Management Office, on Using Quality to Develop an Internet Resource (back before blogs, but after the web, in 1999). I was trimming things as I spoke and cut the tidbit about DARPA and the internet because I figured everyone already knew that (and I had to trim as I was speaking). In discussions afterwards I found many didn’t know DARPA’s involvement.

Related: Better and DifferentWater and Electricity for AllGoogle Innovation

Dean Kamen Lends a Hand, or Two (August 2007):
Continue reading

Bezos on Internet Boom

The webcast shows Jeff Bezos, Amazon.com founder and CEO, speaking at TED on the internet boom. He compares the boom to the gold rush highlighting the similarities. But then he compares the internet to the development of industry around electricity. I think he is exactly right on the internet: “there’s more innovation ahead of us than behind us.”

Related: Bezos on Lean ThinkingAmazon InnovationAmazon’s Amazing AchievementInnovation Thinking with Christensenmanagement webcasts

Webcast on 2-Bin Systems

Illustration of how 2-Bin Systems work, by Bill Hanover.

Related: Overall Equipment Effectiveness (OEE) video by Bill HanoverMessiness is BadDrum-Buffer-Rope Examplelean manufacturing resources

Lean, Toyota and Deming for Software Development

Mary Poppendieck on The Role of Leadership in Software Development, very nice 90 minute webcast:

In this 90-minute talk from the Agile2007 conference, Lean software thought leader Mary Poppendieck reviewed 20th century management theories, including Toyota and Deming, and went on to talk about “the matrix problem”, alignment, waste cutting, planning and standards. She closed by addressing the role of measurement: “cash flow thinking” over “balance sheet thinking”.

via, Leadership is not Obsolete for Self-Organizing Teams!

Once again Mary provides a great resource. This is a great overview. Lean Software Development by Mary Poppendieck and Tom Poppendieck is an excellent book on these topics.

Related: articles and webcasts by Mary Poppendieckposts on software developmentmore management webcasts

  • Recent Trackbacks

  • Comments