Silos Happen? Part 1

http://behindbricks.wordpress.com/2011/01/11/a-new-silo-a-new-obstacle/

Been a while since I posted about the competition. One reason is the competition has changed. It is no longer about this vendor versus that vendor but more insidious. It is now about Silos vs Openness.

In the past I may have painted a picture of a Silo company to look like many things but usually referred to them as Microsoft companies. Usually because Microsoft promoted the individual over the network and as an after thought provided a way to share the data. In contrast to Lotus which from the ground up was about sharing data and has been for over 20 years.

While I may have vented against the Silo companies and the people that thrive on that culture, think an evil pointy haired boss instead of just incompetent, there may be companies that have become Silo organizations purely by accident and have no idea they did it.

I was on a conference call today that sparked a number of questions and one which I am pondering in this post....can you become a Silo organization by accident?

The simple answer is of course, no. Someone or something puts other wheels in motion and before long the car is roaring down the highway with the dog's tongue hanging out the window.

As David Byrne once said, "Well, how did I get here?" This is the question. For if we can figure out this question properly, we can unravel possibly years of bad corporate culture and set you on a course of social enlightenment, beauty and enjoyment.

Most of the Social Media experts of course point out the benefits of a social enterprise. That is easy. They will tell you write a blog, post here, do this do that, but none of this will change a culture, let alone an executives mind set. Examples abound, best practices are in White Papers, but yet it does not hit home because in some cases it happened by accident over time.

To borrow a common idea, if you spent 10,000 hours being a Silo, how many hours will it take to reverse course? And if it was all by accident, now what?

Sales people will spend hours in meetings trying to gauge why an organization needs their product or will try to transform the enterprise but what if they get it wrong or are missing one key point.

Purpose.

No one wants to hear they are wrong or doing something seemingly proper only to find out they have been promoting a closed culture. Look around you at the businesses you frequent, the non-profits you assist, the schools your children attend. You can see the dichotomy and yet if you try to raise this awareness you may be pushed out or ignored. The reason is because management does not like to admit when they made a mistake and worse, if they are not sure how to get out of it, hate the messenger. This isn't about making the executive look bad, although usually their ego's are what makes them feel this way, when in fact they could be appreciative that someone has raised a potential problem of monumental meaning. It is about providing reasonable doubt that the companies efforts may be what is blocking their ability to embrace the cultural shift to openness.

In order to find that purpose again and revisit it, you need to ask some important questions. I suggest starting at the outer, peripheral items and work your way backwards. It is not a top down approach, but putting the executive in their own seat of a situation and having them see and feel the experience in a whole new way while trying to understand what the real purpose is behind the effort.

Walking in someone else's shoes is just the tip of the iceberg.

Firewalls Suck Time

Some days you just can't argue with simplicity. Duplicity is another story.

Junior admins remember, all is not as it appears.

While knocking off a number of issues at a client site upgrade it was reported a server was not accessible from the Domino Administration client. Funny thing is, the servers were replicating with it, no problem at all. But no clients could connect to it.

I asked the usual questions, have you verified DNS names, server document references, TCPIP references, etc.

All looked good they say. At a certain point it impedes my efforts so off I go to troubleshoot this one. Here is what I find:

1)  Server document security page has no one allowed to access the server. Similarly the admin group and server group were not listed. Security settings were all default too. I know we set them, some box has an old copy that replicated, fine, changed, still nothing.

2) Can access the server via RDP and map a drive to it, which led me to  #3

3) Windows 2008 Firewall. Damn, that was it. Although we set all the new servers to the exact same settings, this box did not have the clients cleared to be able to access the server.

REALLY!  Having been on site at some government facilities that lock down every port, protocol and driver I should have checked it first, but you know you start with the larger focus and spiral down to smaller and smaller till you nail it.

Nailed it, now on to other things.