Showing posts with label Kaizen. Show all posts
Showing posts with label Kaizen. Show all posts

May 14, 2018

Happy Just The Way We Are


Great speaker today at the National Institute of Standards and Technology (NIST).

Mike Reiss, producer and writer for the hugely successful Simpson show--the longest-running series on primetime TV with 30 seasons and over 600 episodes!

The topic was "The Science Behind The Simpsons."

Whether the guest was Stephen Hawkings or Leonard Nimoy--there was no shortage of scientists and science in this animated, comedy show that taught us much about life.  

The video clip above was a short capture of the Simpsons singing "We are happy just the way we are."

Incremental change and continuous improvement is so important to our growth and maturation in life.

Yet, there is also a lot to be said for being happy with what you have and who you are. 

There is so much to be grateful for and plenty to enjoy at the moment. 

Many people are on the proverbial roller coaster to nowhere.  

It's nice to get off the roller coaster and finally be somewhere that makes you happy and fulfilled. 

Mary Poppins get hit by the airplane at the end of the skit, and you know what, she's not even missed. ;-)

(Source Video: Andy Blumenthal)
Share/Save/Bookmark

June 26, 2011

How Leaders Can Imitate Art

Mental Floss (July-August 2011) has an article on the awesome art of "Christo and Jeanne-Claude." Their pieces are large, imposing, and environmentally-based. Some examples are:

1) The Umbrella (1991)--Installed 3,100 umbrellas across a 12-mile stretch in California and an 18-mile stretch in Japan."

2) The Gates (2005)--Erected "7,503 steel gates, each with a giant rectangle of orange fabric flowing from it."

3) Surrounded Islands (1983)--"Surrounded 11 uninhabited islands in Biscayne Bay with 700,000 square yards of pink fabric."

4) Wrapped Reichstag (1995)--Wrapped the German parliament in "119,600 square yards of shimmering silver fabric."

What I like about their art is the duality of on one hand, magnitude of the projects--they are huge!--and on the other hand, the utter simplicity of it--such as using a single color fabric to just line up along, spread over, or surround something.

Further, I really like their use of contrasts whether it is the colors of the blue water and green islands with the pink ribbon or the lush green valley with the blue umbrellas--it is in every case dynamic and spell-binding.

Each work even in a microcosm would be beautiful, but when done on a massive scale like with the entire German Parliament building or on multiple continents simultaneously, it takes on an air of magic, almost like Houdini.

Jeanne-Claude passed away in 2009, but together she and Christo created "20 gargantuan works of art, and Christo carries on the "couples's 45 years of collaboration" with new works today.

To me, Christo and Jeanne-Claude are incredibly inspirational:

1) They were highly productive and developed a multitude of magnificent works of art.

2) They defined a sense of beauty in both urban and rural settings that combined the natural surroundings and augmented it with human interventions to complete the creative process.

3) They took on monumental tasks, "funded all the projects themselves," and would obsessively plan all the details to get it right.

4) The were truly collaborative--Christo was the artist and Jeanne-Claude his encouragement and manager, yet they considered each other "equal partners in the creative process."

Their work reminds me of floating in virtual reality like in Second Life, but in this case, it's the real thing. And it's incredibly important because it teaches us that we are partners in the creative process and can do enormously great things in simple and beautiful ways. Similarly, true leadership is about being one with our surroundings, at peace, and yet envisioning how to improve on it and make the good things, spectacular.

(Source Photos of Umbrella and Gates: Wikipedia, and of Islands and Reichstag: here)


Share/Save/Bookmark

March 14, 2011

Watson Can Swim

With IBM's Watson beating the pants off Jennings and Rutter in Jeopardy, a lot of people want to know can computers can really think?

Both sides of this debate have shown up in the last few weeks in some fascinating editorials in the Wall Street Journal.

On one hand, on 23 February 2011, John Searle of the University of California, Berkeley wrote that "IBM invented an ingenious program--not a computer that can think." According to Searle, Watson (or any computer for that matter) is not thinking but is simulating thinking.

In his most passionate expression, Searle exclaims: "Watson did not understand the questions, nor its answers, not that some of its answers were right and some wrong, not that it was playing a game, nor that it won--because it doesn't understand anything."

Today, on 14 March 2011 on the other hand, Stephen Baker, author of "Final Jeopardy--Man vs. Machine and the Quest to Know Everything" took the opposing view and stated: "Watson is an early sighting of a highly disruptive force...one that can handle [information] jobs held by people."

To the question of whether machine thinking is "real" thinking? Baker quotes David Ferrucci, IBM's chief scientist who when asked if Watson can think, responded "Can a submarine swim?"

The analogy is a very good one.

Just because a submarine doesn't swim like a fish or a person, doesn't mean it can't swim. In fact and in a sense, for the very reason that it doesn't swim exactly like a fish or person, it actually can swim better.

So too with computers, just because they don't "think" like humans doesn't mean they don't think. They just think differently and again in sense, maybe for the very same reason, in certain ways they can think better.

How can a computer sometimes think better than a person? Well here are just some possible examples (non-exhaustive):

- Computers can evaluate options purely based on facts (and not get "bogged down" in emotions, conflict, ego, and so forth like human beings).

- Computers can add processing power and storage at the push of button, like in cloud computing (people have the gray matter between their ears that G-d gave them, period).

- Computers do not tire by a problem--they will literally mechanically keep attacking it until solved (like cracking a password).

- Computers can be upgraded over time with new hardware, software, and operating systems (unlike people who age and pass).
At the same time, it is important to note that people still trump computers in a number of facets:

- We can evaluate things based on our conscience and think in terms of good and evil, and faith in a higher power (a topic of a prior blog).

- We can care for one another--especially children and the needy--in a altruistic way that is not based on information or facts, but on love.

- We can work together like ants in a colony or bees in a hive or crowdsourcing on- or off-line to get large jobs done with diversity and empowerment.

- We are motivated to better ourselves and our world--to advance ourselves, families, and society through continuous improvement.
Perhaps, like the submarine and the fish, both of which can "swim" in their own ways, so too both computers and people can "think"--each in their own capacity. Together, computers and people can augment the other--being stronger and more effective in carrying out the great tasks and challenges that confront us and await.

Share/Save/Bookmark

March 13, 2011

Essential Leadership Do’s and Don’ts

Below is a list of my top 15 recommended leadership attributes and the do’s and don’t for these.

For example, in managing people—do empower them; don’t micromanage. For supporting people—do back them; don’t undermine them. In terms of availability-do be approachable; don’t be disengaged. And so on…


While the list is not comprehensive, I believe it does give a good starting point for leaders to guide themselves with.

Overall, a good rule of thumb is to be the type of leader to your staff that you want your supervisor to be to you.

Common sense yes, but too often we expect (no, we demand) more from others than we do from ourselves.

This is counter-intuitive, because we need to start by working and improving on ourselves, where we can have the most immediate and true impact.

Now is a perfect time to start to lead by example and in a 360-degree fashion—because leadership is not a one-way street, but affects those above, below, and horizontal to us.

If we are great leaders, we can impact people from the trenches to the boardroom and all the customers and stakeholders concerned. That’s what ultimately makes it so important for us to focus on leadership and continually strive to improve in this.

Share/Save/Bookmark

November 30, 2009

Leadership: Fight or Flight

When we are confronted with difficult situations, people tend to two different responses: fight or flight.

Generally, people will stand and fight when they are either cornered and have no other option, when they will suffer undue harm if they just try and “let it go”, or when the issue is something that they really believe strongly in (like a principle or value such as equity, justice, righteousness, etc. that they feel is being violated).

In contrast, people typically will flee when they feel that they can get out of a bad situation mostly unscathed and their principles will not be violated (such that they can live with their personal and professional dignity intact). Often, people consider fleeing or a change of venue preferable to “getting into it” when it’s possible to avoid the problems that more direct confrontation can bring.

There is also a third option not typically addressed and that is just “taking it,” and letting it pass. In the martial arts, this is akin to taking someone’s best shot and just absorbing it—and you’re still standing. You go with the flow and let it go. This is sometimes feasible as a less dramatic response and one that produces perhaps less severe consequences (i.e. you avoid a fight and you still yield no ground).

Harvard Business Review (December 2009) in an article called “How to Pick a Good Fight” provides some guidelines on when as a professional you should consider standing up and fighting, as follows:

  1. “Make it Material”—Fight for something you really believe in, something that can create real value, noticeable and sustainable improvement.
  2. Focus on the Future”—Don’t dwell on the past or on things that cannot be changed. Spend most of your time “looking at the road ahead, not in the rearview mirror.”[This is actually the opposite of what 85% of leaders do, which is trying to figure out what went wrong and who to blame.”
  3. Pursue a Noble Purpose”—Make the fight about improving people’s lives or changing the world for the better.” I’d put it this way: stay away from selfish or egotistical fights, turf battles, empire building, and general mud slinging.

“The biggest predictor of poor company performance is complacency.” So leaders need to focus “the good fight” on what’s possible, what’s compelling, and what’s high impact. Great leaders shake things up when the fight is right and create an environment of continuous improvement. Leaders create the vision, inspire the troops, and together move the organization forward to greater and greater heights.

As for fleeing or “turning the other cheek” those venues are best left for issues of lesser consequence, for keeping the peace, or for times when you are simply better off taking up the good fight another day.


Share/Save/Bookmark

September 7, 2008

Toyota and Enterprise Architecture

MSNBC on 24 April 2007 reported: through a shrewd combination of investing in environment-friendly vehicles, offering sharp new models and wooing drivers with brand power, Toyota has toppled GM from the top global sales spot for the first time ever.”

Harvard Business Review, June 2008, reports on “Contradictions that Drive Toyota’s Success.” (by Hirotaka Tekeuchi, Emi Osono, and Norihiko Shimizu) Toyota Motor Corporation has become one of the world’s greatest companies because of Toyota Production System (TPS)…enables the Japanese giant to make the planet’s best automobiles at the lowest cost and to develop new products quickly.”

What is Toyota’s secret?

Reaching for the stars—Toyota sets “near-unattainable goals.” For example, “consider the company’s strategy: Meet every customer need and provide a full line in every market.” This runs counter to Michael Porter’s strategy of “choosing what not to do.” Additionally, Toyota’s goals are “purposely vague” to force exploration, innovation, and collaboration to meet them.

Consider the goals stated by Toyota’s president, Katsuaki Watanabe:

“Build a car that makes the air clean [not just less dirty], prevents accidents [not just reduces accident’s], makes people healthier and happier when they drive it [not just a car that gets you from place to place], and gets you from coast to coast on one task of gas [not just incrementally improving gas mileage].”

Have you ever seen anything like these goals in your organization’s strategic plans?

I highly doubt it. But imagine how your enterprise would change culturally and competitively overnight if you did!

Of course, Toyota’s strategy of Kaizen—continuous improvement—is part of their unending desire to succeed and not be satisfied. They view improvement as not something you achieve, but as something you continuously strive for.

We can apply Toyota’s reach goals and Kaizen philosophy to making enterprise architecture planning more effective too. We need to stop conveniently “planning” on things we are working on now or for which we have a head-up that are just around the corner. Sure it’s easy to plan with 20-20 hindsight and it helps us to achieve our unit and individual performance plans and gets inappropriately recognized and rewarded, but this is really a short term outlook and not one that will drive organizational success. Instead, like Toyota, we need to set goals that are stretch goals for the organization, and which make us go beyond our comfort zones, so that we can truly work to break out of the box and differentiate ourselves and our organization from the status quo and the limits of our imagination. Setting the bar truly high and then not settling for anything less than continual improvement is a long term strategy for success and one that needs to be genuinely encouraged and rewarded.

Here’s another important aspect of Toyota’s success:

Employees are highly valued— “Toyota views employees not just as pairs of hands, but as knowledge workers.” Ideas are welcome from everyone up and down the organization. “Employees have to operate in a culture where they constantly grapple with challenges and problems and must come up with fresh ideas…when people grapple with opposing insights, they understand and come up with effective solutions.” In fact, at Toyota, “employees feel safe, even empowered to voice contrary opinions and contradict superiors.” There is a culture of open communications, and a tremendous value is placed on personal relationships and networking. Additionally, value is placed not on results, but for “how much trust and respect the manager has earned from others,” and “refusing to listen to others is a serious offense.”

This concept of valuing employees and listening to them can shed light on how we need to develop effective enterprise architecture and sound governance; whereby, we provide all major stakeholders a voice at the table--to participate in and influence planning, decision making, and innovation. This is the way to achieve higher returns and lower risks. We need to stop planning and making decisions on the whims of the few or based on gut, intuition, and politics. We must cultivate information sharing, collaboration, and elevate people as the quintessential element of our enterprise’s success.

“Toyota’s culture…places humans, not machines, at the center of the company. As such, the company will be imperfect, and there will always be room for improvement.”

People are flawed, but our endeavors make us great!


Share/Save/Bookmark

February 5, 2008

Organizational Blues and Enterprise Architecture

Organizations are like people, they have ups and downs. They have a beginning and an end (even as they transition or morph into something else). And somewhere in the middle or in numerous little points along the way, the organization/person experiences questioning, doubts, reevaluation or mere generally speaking, “the blues.”

The Wall Street Journal, 2-3 February 2008, has an editorial that describes “a massive American-British study of some two million souls throughout 80 counties confirming, empirically, that middle age immiserates us all without regard to income, culture, gender, marital status, or previous experience.”

The study demonstrates the “mood swing of life” with a “U-curve, in which mental stability and happiness bottoms out in our 40s and into our 50s. We then get more cheerful as we round the curve into the final stretch.”

What happens in mid-life crisis?

“Mid-life is a time when the mirage of life’s perfectibility and symmetry, as envisioned in one’s youth, come back to trouble you like a conscience…one might call it a last chance at happiness, or of “getting it right…the last opportunity to shape your fate before you have to accept it; a phase when you are suddenly taunted by the lives unlived.”

Not only people, but organizations go through mid-life crisis:

The stock market swoon of company’s stocks (representing their market values) is one gauge of their oft meteoric rise and death-defying falls. Just some recent examples of companies in the news today: Technology titans, Microsoft with an intraday low of $0.80 in 1986 and a high of $53.97 in 1999, and Yahoo $0.65 in 1996 and $125.031 in 2000, and both are slightly above or below $30 today. Another example, Starbucks has been off nearly 50% in the past year.

The rise and fall of enterprises is a reflection of their even changing environment. Life is not status quo. We are all tested, all the time. It is how we respond to those tests that determine where we go next.

How do we respond?

Some people respond to mid-life crisis by changing themselves, their jobs, careers, and even partners (some opt for the flashy red convertible sport car deluxe!). People are trying to remake themselves—for better or worse. Organizations do the same thing; they seek transformation, reengineering, and strategic change, and hence they undertake initiatives like Six Sigma, Total Quality Management, The Baldridge Award, Kaizen, and other varied change management endeavors (even enterprise architecture to an extent). We as people and organizations look in the mirror and realize that we cannot continue as we are if we are to survive and thrive to fight another day.


Share/Save/Bookmark

January 8, 2008

Unmanned Vehicles and Enterprise Architecture

Cars that drive themselves, fiction or a soon to be reality?

General Motors believe that new technology enabling unmanned vehicles is the key to their business future; so GM is setting their sights on this as their target architecture for their turnaround.

The Wall Street Journal, 7 January 2008, reports that GM’s new target architecture is to develop unmanned vehicles by 2018.

Chairman and Chief Executive of GM, Rick Wagoner’s “vision of he not-too-distant future, vehicles crammed with cameras, sensors, and radar and navigation technology will be able to brake and accelerate on their own, avoid accidents, and spot congestion.”

Larry Burns, Chief Technologist at GM states “we see vehicles going from being largely mechanical o becoming more and more electronic.”

“Pushing the technological envelope is a key element of Mr. Wagoner’s strategy for turning GM around and positioning the company to compete with Toyota Motor Corp. in the long term. He is convinced being the first with game-changing innovations is the solutions to one of GM’s fundamental problems—battered image.”

While GM’s quality problems have mostly been addressed, consumers still perceive GM to be a stodgy company and have not come back to buy.

Mark LaNeve, GM’s U.S. sales and marketing chief said that “GM believes it must challenge Toyota on technology leadership in order to reverse the negative perceptions of GM and to win back customers who have defected to foreign brands…Toyota right now clearly has a leadership position on reputation, financial results, and many other measures.”

Will this new architecture strategy work for GM?

I wouldn’t bet on it for a number of reasons:

  • Toyota is not standing still while GM retools; in fact, Toyota is already on the leading edge with the Prius gas-electic hybrid, and the Lexus luxury sedan that can parallel park itself.
  • If GM doesn’t deliver on this technology promise, they will have shot themselves in the foot; it’s one thing to be perceived as behind the 8 ball and it’s another thing to prove that you can’t deliver on your commitments.
  • GM has not clearly articulated the business requirement for unmanned vehicles in the consumer market; we are not dealing with the need for unmanned aerial vehicles in fighting the enemy in Iraq.
  • GM’s strategy, as presented, is not coherent; they talk about getting ahead with technology, but have not addressed their inferior position on other issues such as financial results and other measures that GM’s Mark LaNeve acknowledged.

From a User-centric EA perspective, GM has still not caught on to the essence of the Japanese concept of Kaizen—continuous improvement and user-centricity. GM is looking at trying to steal the technology mantle from Toyota instead of incremental and evolutionary improvement time and time again. It’s a philosophy you live by, not one that you steal.


Share/Save/Bookmark

November 4, 2007

Six Sigma and Enterprise Architecture

Six Sigma is a set of practices originally developed by Motorola to systematically improve processes by eliminating defects. A defect is defined as nonconformity of a product or service to its specifications.

While the particulars of the methodology were originally formulated by Bill Smith at Motorola in 1986, Six Sigma was heavily inspired by six preceding decades of quality improvement methodologies such as quality control, TQM, and Zero Defects. Like its predecessors, Six Sigma asserts the following:

  • Continuous efforts to reduce variation in process outputs is key to business success
  • Manufacturing and business processes can be measured, analyzed, improved and controlled
  • Succeeding at achieving sustained quality improvement requires commitment from the entire organization, particularly from top-level management

The term "Six Sigma" refers to the ability of highly capable processes to produce output within specification. In particular, processes that operate with six sigma quality produce at defect levels below 3.4 defects per (one) million opportunities (DPMO). Six Sigma's implicit goal is to improve all processes to that level of quality or better.

Six Sigma is a registered service mark and trademark of Motorola, Inc. Motorola has reported over US$17 billion in savings from Six Sigma as of 2006. (Wikipedia).

Is Enterprise Architecture another offshoot of Six Sigma, Total Quality Management, Kaizen, and so on or is it different?

First what are the similarities between EA and Six Sigma?

  1. Business process improvement—both seek to improve business processes to enhance efficiency and effectiveness and improve enterprise “quality”.
  2. Performance measurement— both believe in measuring and managing results of operations and in driving toward improved performance and mission execution.
  3. Alignment to strategy—both seek to align outputs to strategic goals

What are the differences between EA and Six Sigma?

  1. Technology versus design Focus—EA focuses on technology enhancing business performance; Six Sigma emphasizes design for defect-free performance (or zero defects).
  2. Use of Information for improved decision-making versus process optimization—EA captures business and technical information to improve IT planning, governance, and decision-making (such as new IT investments); while Six Sigma captures and measures information on performance to optimize business processes.
  3. Information- versus industrial-based economy—EA aligns technology solutions with the information requirements of the business and its foundation is in the information economy; while Six Sigma’s defect-free processes are based on an industrial, engineering, and product-based economy.
  4. Information-centric versus process centric initiative—EA is an information-centric initiative that addresses information requirements, information technology solutions, information security, information access, information archival, information privacy, information sharing, and so on; Six Sigma is a process-centric initiative that addresses process inputs, outputs, controls, and mechanisms and works through process definition, measurement, analysis, improvement, and control (DMAIC).

So EA and Six Sigma share some important facets such as business process improvement, performance measurement, and alignment to strategy; however, EA is an information-centric initiative geared toward the information age, as such it takes Six Sigma into the 21st century.


Share/Save/Bookmark

August 14, 2007

Kaizen and Enterprise Architecture

User-Centric Enterprise Architecture and Kaizen are blood brothers — both are dedicated to improvement.

I love Kaizen! Kaizen is the Japanese philosophy of continuous improvement. Kaizen seeks “change for the better” and has been adopted by many companies in Japan as their equivalent of Six Sigma or Total Quality Management (TQM). Toyota is one of the best known and often cited examples of successfully implementing Kaizen; they have made kaizen part and parcel of their auto production process. Kaizen is an enterprise-wide endeavor. In a kaizen environment, the organization experiments to find better ways of doing things and then when these superior ways are found, they become the new standard throughout the organization.

In user-centric EA, there is also a focus on standards, integration, and process improvement. In EA, these are facilitated by the EA knowledge base of business and technical information, the analysis of problem areas and identification of gaps, redundancies, inefficiencies, and opportunities, and the institutionalization of regular and meaningful planning and good governance for maximizing the value of investments to the enterprise.

While kaizen is often associated with improvement to production systems including quality control, testing, and assurance, it is also a way of approaching work, education, relationships, and life — it’s when one is constantly asking “how can I do better” and actually following through (not like the typical New Year’s resolutions).

To me, EA is similar to kaizen in that it seeks to capture information, analyze it, and find ways to improve things. In EA, this search for continual improvement manifests itself by filling information gaps for users, eliminating organizational stovepipes, delivering IT solutions that meet requirements, consolidating redundant systems, and facilitating business process reengineering or improvement.

Do you view EA as a form of kaizen? How do you use EA to improve organizational processes and functions?
Share/Save/Bookmark