for Information Management Blogs
MAR 4, 2011 12:33pm ET

Blogroll

What Happens in Vegas … Is Disruptive Change

Print
Reprints
Email

I firmly believe that what happens in Vegas should stay in Vegas — which is why I will NOT be blogging about what happened at Pure Nightclub after Tuesday night’s poker tournament at TDWI Las Vegas. However I thought I’d share a point or two from my Monday keynote.

In my presentation on building your enterprise data strategy I listed organizational and cultural dysfunctions that could sabotage a data strategy. One of these is the so-called “Culture of No.” I explained that “no” is way easier than “yes.” Anyone can come up with a good reason not to do something. After all, they might be held accountable if they say yes. No is the safe answer, the acceptable answer, and fewer people second-guess it. (Not coincidentally I also talked about Passive-Aggressive Resistance.)

Some companies consistently err on the side of what I call “organizational homeostasis.” I came up with the term after watching an infomercial where a diet doctor was discussing how the mechanisms that control appetite and burn energy are intricately balanced. “Our bodies like to remain at whatever weight they’re used to,” said the diet doctor. My personal experience affirms both the doctor’s claim — don’t get me started — and the cultural tendency of companies to stay where they are. Chase causes discomfort, be it in the form of severe hunger pangs or new ways of working.

My favorite clients not only embrace change, they kiss it on the lips. They use their change readiness to invite improvements or to open up new opportunities. The word “disruptive” is tossed around not like a hot potato, but rather like a fabulous pair of new glasses that everyone wants to try on. And it turns out they look good on everyone.

Someone in my keynote asked me for a prediction. My prediction is that as business picks up and executives look for new ways to improve corporate performance, they’ll welcome change. This means people will be more likely to experiment with new products and services, revisit entrenched business processes, and extend offers to employees and partners they wouldn’t have considered during the bad old days of homeostasis.

My company is about to go through a disruptive-yet-exciting change. It’s also creative, forward-thinking, timely, and strategic. It will be good for our employees, our partners, and our clients. It will let us create new products and improve existing ones. It will help us hire more people and leverage the awesome team we currently have. Needless to say, I’m excited about it.

Can you apply this description to an idea at your company? Can you get excited about it? Good. Now go make it happen! And if it happens in Vegas, you don’t have to tell.

Read the Press Release announcing Baseline Consulting’s acquisition by DataFlux here.

 

Advertisement

Comments (2)
For decades we have been told that the reasons organizations don't change is because people are resistant to change or that "no" is an easier answer than "yes". Those in IT seem to assume that "no" doesn't mean "no" so they keep flogging the same old products and theories with new marketing hyperbole.

Customer data integration morphed into master data management. Outsourcing has become cloud computing. Data entry errors and data quality problems can now all be solved by data profiling and data management best practices have become data governance. It's "no" wonder organizations are saying "no". What happened to SOA and SaaS? Are they DOA?

When asked about the ROI or impacts of these technologies on the business the responses are anecdotes or how these changes are a journey.

These organizations now "know" that many of the technology promises of the past have not resulted in measurable improvements to the business yet required significant resources to deploy and maintain. They have come to realize that technology isn't as much of a competitive advantage as in the past. Chasing the latest buzz word is no longer acceptable.

Now that they "know" they are saying "no".

Posted by Richard O | Wednesday, March 09 2011 at 12:06PM ET
I agree that we should "welcome change," but with the caveat that we should fail quickly when reversing bad change is necessary.

I think there is a small typo in "Chase causes discomfort...." I think "Chase" should be "Change".

Posted by Alan M | Wednesday, March 09 2011 at 2:13PM ET
Add Your Comments:
You must be registered to post a comment.
Not Registered?
You must be registered to post a comment. Click here to register.
Already registered? Log in here
Please note you must now log in with your email address and password.

Blog Archive for Jill Dyché

Designing Your BI Competency Center
You Need to Get Out More
Anti-Predictions for 2011
Offering Up Your (Data) Dowry: A Cautionary Tale
The Unique and Special Purpose of Business Intelligence

More from Jill Dyché »

Blog Index »

Twitter
Facebook
LinkedIn
Login  |  My Account  |  White Papers  |  Web Seminars  |  Events |  Newsletters |  eBooks
FOLLOW US
Please note you must now log in with your email address and password.