Watch closely the first 8 or 9 seconds of this video...

...Got it? ...

No rain, no rainbows?

Good. Now, how often as IT are we in that "no rain, no rainbows" guy's shoes? That poor guy went to a lot of planning, time, and effort to make sure that bride had rainbows on her wedding day, and she just didn't get it. We build it and no one comes. We provide the enabling change, and the process changes don't occur. So we turn off the water and figure that's their tough luck.

But did that guy take the time to explain to the bride the intended purpose of the rain?

If benefits are outlined in a cost/benefit analysis to justify a project, are those benefits often seen as a "given" and rarely communicated to the staff that has to utilize product? If the vision was that the staff was supposed to use the product to do new things, do things better, or stop doing things, were they told so?

I really like this guy, my heart goes out to him, but don’t be like this guy.

IT needs a new role of educator and facilitator. IT leaders need to be brave and vocal, driving change and innovation, and promoting IT and business/program integration and coordination. Often this means that your focus needs to change from technology to people and relationship building. And your new role as educator/facilitator, driver of change and innovation, promoter of integration and coordination must continue until your organization has reached the point where IT is not in a box on the organizational chart but a way of thinking that has permeated the organization and everyone understands there needs to be rain to get rainbows.


Post a Comment