Search This Blog

Friday, December 05, 2008

Tom Peter's 27 Points to Transform an Organization

The Top 27: Twenty-seven Practical Ideas That Will Transform Every Organization

1. Learn to thrive in unstable times—our lot (and our opportunity) for the foreseeable future.

2. Only putting people first wins in the long haul, good times and especially tough times. (No "cultural differences" on that one! Colombia = Germany = the USA.)

3. MBWA/Managing By Wandering Around. Stay in touch!

4. Call a customer today!

5. Train! Train! Train! (Growing people outperform stagnant people in terms of attitude and output—by a wide margin.)

6. "Putting people first" means making everyone successful at work (and at home).

7. Make "we care" a/the company motto—a moneymaker as well as a source of pride.

8. All around the world, women are an undervalued asset.

9. Diversity is a winning strategy, and not for reasons of social justice: The more different perspectives around the table, the better the thinking.

10. Take a person in another function to lunch; friendships, lots of, are the best antidote to bad cross-functional task accomplishments. (Lousy cross-functional communication stops companies and armies alike.)

11. Transparency in all we do.

12. Create an "Innovation Machine" (even in tough times). (Hint: Trying more stuff than the other guy is Tactic #1.)

13. We always underestimate the Innovation Advantage when 100% of people see themselves as "innovators." (Hint: They are if only you'd bother to ask "What can we do better?")

14. Get the darned Basics right—always Competitive Advantage #1. (Be relentless!)

15. Great Execution beats great strategy—99% of the time. (Make that 100% of the time.)

16. A "bias for action" is a "bias for success." (Great hockey player Wayne Gretzky: "You miss 100% of the shots you don't take.")

17. No mistakes, no progress! (A lot of fast mistakes, a lot of fast progress.) (Australian businessman Phil Daniels: "Reward excellent failures. Punish mediocre successes.")

18. Sometimes "little stuff" is more powerful than "big stuff" when it comes to change.

19. Keep it simple! (Making "it" "simple" is hard work! And pays off!)

20. Remember the "eternal truths" of leadership—constants over the centuries. (They say Nelson Mandela's greatest asset was a great smile—you couldn't say no to him, even his jailors couldn't.)

21. Walk the talk. ("You must be the change you wish to see in the world."—Gandhi)

22. When it comes to leadership, character and people skills beat technical skills. (Emotional Intelligence beats, or at least ties, school intelligence.)

23. It's always "the little things" when it comes to "people stuff." (Learn to say "thank you" with great regularity. Learn to apologize when you're wrong. Learn the Big Four words: "What do you think?" Learn to listen—it can be learned with lots and lots of practice.)

24. The "obvious" may be obvious, but "getting the obvious done" is harder said than done.

25. Time micro-management is the only real "control" variable we have. (You = Your calendar. Calendars never lie.)

26. All managers have a professional obligation to their communities and their country as well as to the company and profit and themselves. (Forgetting this got the Americans into deep trouble.)

27. EXCELLENCE. ALWAYS. (What else?)

See more great stuff at Tom Peter's Website

Friday, November 28, 2008

Weekend Fun

I was out playing golf today and a seven foot gator decided he wanted to watch.

Sunday, November 23, 2008

Project Scope Overload


Always remember to keep your scope manageable. Too much scope when resources are limited can have unpredictable results.

Monday, November 10, 2008

Project Failure

Project Failures are everywhere.  Below is a list of project failures taken from an article that appears on the Lessons-from-History website.  You can read the full article here.


Why are there so many project failures?  My therory is it they are many times a result of a combination of several things:


Weak project management

Poor or non-existent project sponsorship

An organizational culture that severely disfunctional

Incomplete and/or inaccurate requirements


Some Notable Project Failures (from Lessons-from-History.com)

The following list of failures happened within the project itself supporting the Standish claim that close to 50% of projects are seriously challenged:

  • The IRS project on taxpayer compliance took over a decade to complete and cost the country an unanticipated $50 bn.
  • The Oregon DMV conversion to new software took eight years to complete, the budget grew by 146% ($123m) and public outcry eventually killed the entire project.
  • The State of Florida welfare system was plagued with numerous computational errors and $260m in overpayments!
  • August 2008 Unencrypted memory stick lost with names/dates of birth of 84,000 inmates, England 's entire prison population. Home addresses of 33,000 who had six convictions.
  • Feb. 2007 £20bn UK NHS computer system 'doomed to fail‘a senior insider has warned.
  • 2007 laptop with records of 600,000 recruits was stolen from Royal Navy recruiter's car
  • In September 2006 Department of Homeland Security admitted project failure and closed the Emerge2 program $229m (a new financial IT system).
  • In May 2006 the disastrous Seasprite helicopter program for the Australian Navy, with $1bn spent, the helicopters were grounded due to software problems.
  • In April 2005 inter-departmental warfare played a significant role in the failure of a $64m federal IT project.
  • In 2005 British food retailer J Sainsbury had to write off $526m it had invested in an automated supply-chain management system.
  • In 2005 US Justice Department Inspector General report stated $170m FBI Virtual Case File project was a failure, after five years and $104m in expenditures. Over one 18-month period, the FBI gave its contractor nearly 400 requirements changes. 
  • In 2005 the UK Inland Revenue produced tax payment overpayments of $3.45 bn because of software errors. 
  • May 2005 major hybrid car manufacturer installed software fix on 160,000 vehicles. The automobile industry spends $2 to $3 bn per year fixing software problems.
  • July 2004 a new government welfare management system in Canada costing $200m was unable to handle a simple benefits rate increase. The contract allowed for 6 weeks of acceptance testing and never tested the ability to handle a rate increase.
  • In 2004 Avis cancelled an ERP system after $54.5m is spent
  • In 2002 the UK government wasted £698m on Pathway project, smartcards for benefits payments, & £134m overspend on magistrates' courts Libra system.

Mini nuclear plants to power 20,000 homes

From the Guardian

Nuclear power plants smaller than a garden shed and able to power 20,000 homes will be on sale within five years, say scientists at Los Alamos, the US government laboratory which developed the first atomic bomb.

The miniature reactors will be factory-sealed, contain no weapons-grade material, have no moving parts and will be nearly impossible to steal because they will be encased in concrete and buried underground.

The US government has licensed the technology to Hyperion, a New Mexico-based company which said last week that it has taken its first firm orders and plans to start mass production within five years. ‘Our goal is to generate electricity for 10 cents a watt anywhere in the world,’ said John Deal, chief executive of Hyperion. ‘They will cost approximately $25m [£13m] each. For a community with 10,000 households, that is a very affordable $250 per home.’

 Click here for the full article

Monday, November 03, 2008

Quality Improvement – Six Steps to Improving Quality

Step 2 - What is the Objective - To select a problem and set a target for improvement

What key activities should be undertaken?

Collect data on all aspects of the theme (all problems)
Clarify the problems from various viewpoints
Select a problem collected in the previous step
Identify what the customer wants (their requirements)
Write a clear statement of the problem
Utilize data to help establish a target
Present the problem statement to management or your project sponsor

Tools You Can Use:

Checklists
Graphs
Pareto Charts
Control Charts
Histograms
Problem Statement Matrix

Note – Step Three will be coming in the next few days