Sometimes Micro-managing Works

Posted on April 27, 2011  Comments (3)

Sometimes micro-managing works. That doesn’t mean it is a good strategy to replicate. If you benchmark Apple you might decide that you should have a tyrannical obsessive involved CEO who is directly involved in every detail of products and services. After all Apple is now the second most valuable company in the world with a market capitalization of $324 billion (Exxon Mobil is the top at $433 billion) and a huge part of that is Steve Jobs.

Nice quote from How to beat Apple

Apple products & services that Apple does well are the ones that Steve Jobs uses

An interesting point, and really it doesn’t matter if it is completely true it illustrates a point that Steve Jobs is the rare leader that helps by being completely involved in nearly every detail. And at the same time he provides strategic leadership rivaled by very few others. But if you try to benchmark this (simplistically – as most benchmarking is done) you will fail. This works with Steve Jobs and maybe a handful of other people alive today. But with most leaders and organizations it would fail completely.

On another point Jason Kottke makes, I would normally suggest the opposite approach:

Openness and secrecy. Competitors should take a page from Apple’s playbook here and be open about stuff that will give you a competitive advantage and shut the hell up about everything else. Open is not always better.

I think you may well be better off doing the opposite and countering Apple’s secrecy with openness. It would depend on your organization, but, I think you might be better off trying to exploit Apple’s weakness instead of trying to do what they do well. Now things are never this simple but on a cursory level I think that is where I would look.

Google now has a market cap of $171 billion, Apple is almost double that – just 3 years ago Apple first exceeded Google’s value.

Related: Leadership is the act of making others effective in achieving an aimThe CEO is Only One PersonJeff Bezos Spends a Week Working in Amazon’s Kentucky Distribution CenterRespect for PeopleDee Hock on Hiring

Factorial Designed Experiment Aim

Posted on April 25, 2011  Comments (2)

Multivariate experiments are a very powerful management tool to learn and improve performance. Experiments in general, and designed factorial experiments in particular, are dramatically underused by managers. A question on LinkedIn asks?

When doing a DOE we select factors with levels to induce purposely changes in the response variable. Do we want the response variable to move within the specs of the customers? Or it doesn’t matter since we are learning about the process?

The aim needs to consider what you are trying to learn, costs and potential rewards. Weighing the various factors will determine if you want to aim to keep results within specification or can try options that are likely to return results that are outside of specs.

If the effort was looking for breakthrough improvement and costs of running experiments that might produce results outside of spec were low then specs wouldn’t matter much. If the costs of running experiments are very high (compared with expectations of results) then you may well want to try designed experiment values that you anticipate will still produce results within specs.

There are various ways costs come into play. Here I am mainly looking at the costs as (costs – revenue). For example the case where if the results are withing spec and can be used the costs (net costs, including revenue) of the experiment run are substantially lower.
Read more

Management Improvement Carnival #129

Posted on April 20, 2011  Comments (0)

Large rock outcropping along the beach

The beach along Hole in the Wall Trail in Olympic National Park by John Hunter.

The Curious Cat Management Blog Carnival selects recent management blog posts 3 times each month. You may submit a link to the management Reddit to have it considered for inclusion in our carnival

  • Let’s Dance by Ron Pereira – “I am supremely confident injecting a little fun with all the seriousness of life and business will do nothing but help.”
  • How To Hold A Lean Meeting by Matt May – “In one to three sentences, define the overall purpose of the meeting… Goal #5: Develop a preliminary implementation plan. Who does what by when. Closing: Plan next steps. Decide on key follow-up plan.”
  • 5 Wrong Reasons To Apply Kanban – “If you expect that you will replace failed retrospective meetings with a nice and simple ‘stop the line’ rule, you’ll fail, since it is even harder than scheduled regular retrospectives and demands even higher level of self-discipline.”
  • 6 Principles for Rebuilding Industry by Jon Miller – “Principle 3. Remember that goods and services are inseparable… Principle 5. Put the focus back on the people on the gemba…
  • How to get a real education by Scott Adams “The kids in this brainy group are the future professors, scientists, thinkers and engineers who will propel civilization forward. But why do we make B students sit through these same classes? That’s like trying to train your cat to do your taxes—a waste of time and money. Wouldn’t it make more sense to teach B students something useful, like entrepreneurship?”
  • Read more

Problems with Management and Business Books

Posted on April 18, 2011  Comments (9)

We really need to change how we improve the practice of management. Far too often management strategies are just the latest fad from some new book that successfully marketed an idea. The marketing effectiveness of a book, or consultant, has very limited correlation to their ability to improve management, in my experience. It is often true that they make very good keynote speakers, however. So if you want an entertaining keynote speaker looking at the authors of the best selling business books may make sense. But if you want to improve management, I don’t see much value in doing so.

Year after year we have the same basic business books repackaged and marketed. They present a magic bullet to solve all your problems. Except their bullet is far from magic. Usually it does more harm than good.

They amazingly oversimplify things to make their bullet seem magic. This also fails miserably in practice. There are usually not good management options that are simple and easy. Usually the answers for what should be done is a lot of “it depends,” which people don’t seem to like.

Authors fail to place their book (or their trademarked strategy they hope turns into a movement/fad) in the appropriate context. Most books just take a few good ideas from decades old practices add a new name and leave off all references to the deep meaning that originally was there. I guess quite often the authors don’t even know enough about management history to know this is the case; I guess they really think their minor tweak to a portion of business process re-engineering is actually new. This also would make it hard for them to place their ideas within a management philosophy.

On a related note, I find it interesting how different the lean manufacturing and six sigma communities are online (and this has been going on for more than a decade). One of the problems with six sigma is there is so little open, building on the practices of six sigma. Everyone is so concerned with their marketing gimmick for six sigma that that don’t move forward a common body of work. This is a serious problem for six sigma. Lean manufacturing benefits hugely from the huge community of those building openly on the body of knowledge and practice of lean. You can find 10 great lean manufacturing blogs without trouble. You will have difficulty finding 3 good six sigma blogs (and even those spend most of the time on other areas – often lean thinking).
Read more

Engage in Improving the Management System

Posted on April 14, 2011  Comments (0)

To actually improve management you need to engage in continual improvement of your management systems. This requires doing the hard work of challenging complacency. The job of those improving the practice of management is not to make everyone happy and just ignore that the words about improvement are not actually carrying through to changes in behavior.

Do Executives “Get It?”

So many times executives spout the importance of new initiatives like wellness programs, safety programs, or improvement projects like Lean, Six Sigma, etc. They talk about how great they are and how everyone should embrace them so the company can improve, but when push comes to shove, their actions indicate they really don’t believe in them.

If you are trying to bring about change you need in-process indications of actual success at improving the management system. Instead it seems to me, most of the time, the focus is on spinning what is being done to convince others that what is being done is good. This is not helpful and not useful.

Without in-process indications of how the movement to a better management system is performing the pattern is all too common. People want to show they are doing a good job (which often includes not being too negative – because if they criticize results they can be branded as negative). So instead we end up with actions that would be used if one assumed that while we had problems with the last 4 management fads we implemented, now we have this wonderful new idea it will avoid all the problems.

So we start our new process, and write up reports and presentations for meetings talking about our successes. We are careful to ignore any warning signs. Then, after 1, 2… years (in a good economy this can last quite a bit longer), the boss says the results are not improving, this isn’t working. Everyone quickly agrees and the improvement effort is dropped. Usually there will be a period of time taken until and a new fad is found that everyone agrees is wonderful for 2-5 years until they then all agree was a failure. Repeat for the rest of your career.

To break this cycle and actually continually improve we can’t go along with the in-process indications that the management improvement system is not really working. We need to seek out indications that it is not working and address those issues and build a strong continually improving management system.

Related: Management Advice Failuresflavors of management improvement effortsmanage what you can’t measureFederal Government Chief Performance Officer (a specific example of the repeated failure to improve), just pretending the failures in the past didn’t exist doesn’t help the current effort

Why Lean is Different

Posted on April 12, 2011  Comments (0)


Why Lean is different by Operae_Partners

Short webcast by Michael Ballé discusses what makes lean manufacturing different: going to where the work is done, standardize processes (from the gemba view), practice respect for people and continually improve. Lean thinking focuses on achieving better results and through that process improves trust and teamwork internally, as well as better supplier and customer relationships.

Related: Non-technical Control Chart WebcastMihaly Csikszentmihalyi: Creativity, Fulfillment and Flowlean management, books, articles…

Management Improvement Carnival #128

Posted on April 10, 2011  Comments (2)

The management blog carnival is published 3 times a month with select recent management blog posts. I also collect management improvement articles through Curious Cat Management Articles, you can subscribe via RSS to new article additions.

  • Resist your machine thinking! by Jeff Liker – “To maintain consistent output, one must continually adjust the system to changing environmental conditions. This is called dynamic homeostasis in systems thinking, or running to stay in place. … Maintenance comes from having clearly defined standards, observing carefully for deviations from those standards, and then developing and implementing countermeasures to eliminate the deviations.”
  • 5 lessons from an Information Architecture career by Martin Belam – “Over the years I’ve learned that pragmatic UX that gets software shipped is more valuable than perfecting your pre-build documentation.
    This lesson is very much tied up with the ideas of progressive iterations, and improving things from the base of a ‘minimum viable product’… There is nothing less compelling than shipping nothing at all.”
  • Pop quiz: Lean-ify this iPad case by Kathleen Fasanella – “Here is a summary of the specific items you mentioned: Having the work piece, waste can, tools and equipment arranged optimally. Component placement was (mostly) eyeballed, several suggested jigs or templates for layout. David suggested notching for more efficient placement. The fabric covers should have been cut with rounded covers to eliminate the messy and wasteful step of hand trimming.”
  • Demystifying the Product Owner by – the product owner leads product discovery: “to help identify and describe requirements, and to ensure that the product backlog is ready for the next sprint planning meeting. It also means that the product owner has to engage in product planning, visioning and product road mapping…”

  • Gary Hamel at Dell: How can IT organizations adapt?

  • Working in the cracks in the system by Wally Bock – “Use the situation as an opportunity for conversation. Talk to John in private. Tell him you’ve noticed that he’s been coming in late and tell him why that matters to you and to the team. After you say that, wait for John to speak next.”
  • Read more

Quality is Made in the Board Room

Posted on April 8, 2011  Comments (1)

Dr. Deming stated “Quality is made in the board room,” page 202 Dr. Deming: the American who taught the Japanese about quality. I believe, once the board and executive leadership has put in place the right management system (one that respects people, continual improves using a standardized improvement process (that itself is being improved), practices evidence based management, focuses on customer value, improves processes rather than blames people, builds the capacity of the organization over time…) then quality is everyone’s responsibility.

Executive leadership can’t do it themselves. Making it everyone’s responsibility after the system allows everyone to participate effectively is sensible. That does not, in any way, excuse blaming those stuck in a bad system for failures they didn’t heroically overcome.

Continuing from the quote from Deming above:

A worker can deliver lower quality, but she cannot deliver quality better than the system allows…
Exhortations not only have no long-term effect, but eventually they backfire

Related: The Two Pillar of the Toyota Way: continuous improvement and respect for peopleDr. Deming on ManagementBooks on Applying Deming’s ideas

Finding, and Keeping, Good IT People

Posted on April 6, 2011  Comments (3)

Finding good IT people, wherever you located globally, is hard. Waiting for the good IT people to apply for positions, is not likely to gain enough good candidates.

To get really good IT people you need to actually manage your current IT staff properly. Then word will get out that your organization is not run by pointy haired bosses (phb) and good IT people will be open to joining. This obviously is not a quick fix. But this practice is the key. This is just respect for people with a eye on the special needs of creative IT people.

If you do this you will also reduce turnover. That doesn’t help in recruiting people, but it solves the underlying problem recruiting is meant to deal with – having staff to do the work. Making your environment tech employee friendly has the benefits mentioned above and will reduce turnover.

Like many issues when examined systemically the most important factors to deal with the recruiting problem are often not directly looking at the problem at hand. Now there are sensible actions to improve the recruiting process. Take a fundamental look at the hiring process and think about some real changes – how about trying people out first, not determining staffing primarily on judgments based on how well then interview. Don’t have silly prerequisites. Why do you need a college degree for an IT job? Or why require specific degrees, like a computer science degree, and exclude others, for example, an online IT degree. Might specific college experience be helpful? Yes. Might someone without it be a great employee? Yes.
Read more

Toyota Kata Song – The Times They Are Changing

Posted on April 4, 2011  Comments (2)

Very well done song, Toyota Kata – Managing by Means, by Doug Hendren – to the music of “The Times They are A-changing” by Bob Dylan. Doug sounds impressively similar to Dylan and the words are actually wonderful.

Managing by results, it don’t work anymore. Don’t stand in your office, go to the shop floor

to really improve you must iterate, see our problems as treasures before its too late, and eliminate waste, whether little or great. Take baby steps up to your dreams. And gradually reach a more flexible state if we want to manage by means.

Via: Lean Blog

Related: Toyota Kata (book)Learn Lean by Doing LeanThey Will Know We are Christians By Our LoveIf Your Staff Doesn’t Bring You Problems That is a Bad Sign

Management Improvement Carnival #127

Posted on April 2, 2011  Comments (1)

photo of Cliff Palace at Mesa Verde

Photo of Cliff Palace at Mesa Verde by John Hunter.

The Curious Cat Management blog carnival highlights recent management blog posts 3 times each month. The posts generally focus on the areas I have focused on in the Curious Cat Management Guide since 1996 (Deming, agile software development, systems thinking, lean manufacturing, customer focus…).

  • Jim Womack, lean blog podcast #116 – Great, as you would expect. Includes a great explanation of the problems that have made adopting lean ideas in medicine, which somewhat counter-intuitively includes the reluctance to use the scientific method/pdsa to examine results.
  • What Larry Page really needs to do to return Google to its startup roots – “If your company has to have ‘No meetings Thursday’ then you’re doing it wrong. How about ‘No meetings except for Thursday’… Having to launch a simple service in multiple datacenters around the world, and having to deal with near-weekly datacenter maintenance shutdowns is unacceptable for an agile startup. Startups need to focus on product, not process and infrastructure.”
  • Don’t forget what it’s like to be 10 by Richard G Russell – Your job isn’t telling them what to do. 80% of your job is understanding what your team does, and what they need to accomplish their job; then helping them do it.
  • Relationship between Process and Innovation by Jeffrey Phillips – “Let’s distinguish between effective processes that accelerate innovation and those failed processes that either weren’t meant to accelerate innovation or weren’t the right processes for innovative ideas to begin with.” [Curious cat 2007 post: Process Improvement and Innovation
  • Surfacing Problems Daily by Jamie Flinchbaugh – “When it comes to building a problem-solving culture, one of the most important traits is being able to surface problems quickly and face them honestly.”
  • How to start a movement in your company – by David Choe – “So, here I am to tell the tale and advocate for good leadership, clear vision, constancy of purpose, and true empowerment.”
  • Read more

  • Recent Trackbacks

  • Comments