Skip to main content

Toyo...duh!

Last week's blog entry seemed to resonate with the precious few readers that I have. In addition to the lone comment that was posted, I received a number of emails that said how "spot on" the message was.

To re-emphasize the need to take responsibility for one's actions, it should be noted that there is now a shareholder lawsuit that has been filed. In the article on MSNBC.com, it was reported that this is a response to the recalls and the seemingly deliberate, misstated reasons for the safety issues in the first place. To put it another way, Toyota is accused of knowing full well that the reasons they initially gave for the cause of the problem were nowhere near what they were saying internally. To quote the article:

"...top Toyota executives have known for nearly a decade that faulty electronic throttle controls caused vehicles to sometimes careen wildly out of control but covered it up to protect the company's reputation for safety — and its stock price."

This lawsuit should not be a surprise to anyone unless you've had your head in the sand during the past month or so. Reading the hemming and hawing by Toyota to the American public and Congress quickly left me with the impression that either they were hiding something or were incompetent. But you don't have the top selling mid-sized sedan for 8 years if you're incompetent so you do the math.

If you're Toyota, it's easy to understand why you would want to hide the scope of the problem. But in the end you have a moral obligation to do what's right, namely: a) disclose everything that you know and b) devote every possible resource to the task of figuring out the problem. Apologizing for not doing this after the fact does not resurrect the San Diego Patrol Officer whose Lexus accelerated on its own and eventually killed him and three family members.

Instead, they fret and fear about public reaction if their weaknesses were made public. And they aren't alone either. This past week, a Chinese graduate student in Engineering found out he's a target in the scope of Congress. His offense? He published a paper that discussed the vulnerabilities of the American electrical infrastructure and how a terrorist could possibly take out the entire electric grid for the U.S.

Here's a hint to Congress: if you're so damned worried about publications that describe infrastructure vulnerabilities then fix the vulnerabilities so that there is no risk in the first place. Let's take some of the bank bailout money and put it to good use instead of allowing the larger financial institutions to take a slap on the wrist without actually affecting the standard of living of their highest officers. Alan Greenspan noted this (the link goes to the NY Times article reporting on his recently released 48-page analysis on the financial meltdown) when he said the following:

"To be sure, the senior officers of Bear Stearns and Lehman Brothers lost hundreds of millions of dollars from the collapse of their stocks...But none to my knowledge filed for personal bankruptcy and their remaining wealth allowed them to maintain much of their previous standards of living."

If you aren't going to use TARP to fix the vulnerabilities in the financial system, use it to fix them in the electrical infrastructure. (Or maybe we should address the continued gouging of the American public by the oil companies. Don't even get me started on that topic...)

And if you do fix the big problems looming in a variety of areas, be sure they are fixed instead of deluding yourself into thinking the problem will go away simply because you click your heels together three times while repeating, "There's no place like home." Stock traders seem to be doing this right now by saying that
, "steadying home prices are good enough for now."

Wake up people. You're starting to sound like Mary Meeker during the Dot Com bubble in the late 90's. Home prices are not good enough for now. They aren't even close and won't be until the backlog of foreclosures that have been intentionally stalled by the banks themselves gets cleared.

Let's recap, then: be upfront about what you know; fix the problems; and then be sure they are fixed before declaring victory. Toyota is finally learning this lesson the hard way. Maybe, then, we can avoid looking like idiots (as I reported last week) for simply observing the errors of others instead of looking at ourselves in the mirror to ensure that we aren't guilty of the same problems.

Popular posts from this blog

Time to Level Up!

With the recent news out of Salesforce and Oracle, it’s easy to understand why folks affected by layoffs might feel discouraged. Not only are they leaving companies they may have called home for years, but they’re also facing the daunting prospect of job hunting while headlines scream about “AI taking over human jobs.” Not long ago, another company I follow - let’s call it Acme  - went through a similar round of layoffs. Two employees in particular (we’ll call them Jim and John) showed how mindset can make all the difference. Jim had been at Acme for over 20 years. He was reliable, steady, and well-liked, but not exactly the standout type. When he was laid off, he decided to take some time off before even thinking about his next move. After all, he had a severance package. Didn’t he deserve a break after two decades of hard work? John’s story was different. Though he hadn’t been at Acme as long, he’d built a strong reputation and had both technical and leadership skills. Instead of...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...

COSMIC Insights

Consider the following scenario:  you're a mid-level manager and find out that a layoff is coming.  You're about too lose one of your best direct reports, but you have no ability to influence the decision to lay them off. Oy! My head hurts! What do you do? Oftentimes, I find that people - when presented with situations where they feel compelled to act but have no ability to change the outcome - enter a state of mental lethargy.  They don't know exactly what it is they should do but, "gosh darnit!", something has  to be done.  When they realize how helpless they actually are, they start lamenting about the situation, how they are backed into a corner, etc. In a very real sense, they go through the five stages of grief . I'd like to offer the following alternative way of approaching these and other situations:  I call it the COSMIC method, not only because it sounds cool but also because I like science fiction (" Lisan al Gaib! "). COSMIC is an acronym...