Comments on: IT and the Corporate Immune Mechanism – the "Mother Hen" reflex http://www.cleverworkarounds.com/2008/07/26/it-and-the-corporate-immune-mechanism-the-mother-hen-reflex/ After much frustration, it seems DEFAULT is the way to go... Tue, 27 Jul 2010 11:20:51 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: IT Support London http://www.cleverworkarounds.com/2008/07/26/it-and-the-corporate-immune-mechanism-the-mother-hen-reflex/comment-page-1/#comment-18402 IT Support London Tue, 24 Nov 2009 13:22:54 +0000 http://www.cleverworkarounds.com/2008/07/26/it-and-the-corporate-immune-mechanism-the-mother-hen-reflex/#comment-18402 Thats why it's important that you have a decent IT Support company or in house IT expert to help you out * the right way * Thats why it’s important that you have a decent IT Support company or in house IT expert to help you out * the right way *

]]> By: The One Best Practice to Rule Them All: Part 6 | End User SharePoint http://www.cleverworkarounds.com/2008/07/26/it-and-the-corporate-immune-mechanism-the-mother-hen-reflex/comment-page-1/#comment-8629 The One Best Practice to Rule Them All: Part 6 | End User SharePoint Mon, 13 Apr 2009 14:59:21 +0000 http://www.cleverworkarounds.com/2008/07/26/it-and-the-corporate-immune-mechanism-the-mother-hen-reflex/#comment-8629 [...] they are always the ones who have to deal with the after-effects of bad customizations (See the “mother hen reflex” post for how that has come to be). But through mapping this issue out, I was able to make some [...] [...] they are always the ones who have to deal with the after-effects of bad customizations (See the “mother hen reflex” post for how that has come to be). But through mapping this issue out, I was able to make some [...]

]]> By: CleverWorkarounds » The one best practice to rule them all – Part 6 http://www.cleverworkarounds.com/2008/07/26/it-and-the-corporate-immune-mechanism-the-mother-hen-reflex/comment-page-1/#comment-7154 CleverWorkarounds » The one best practice to rule them all – Part 6 Thu, 19 Mar 2009 18:00:06 +0000 http://www.cleverworkarounds.com/2008/07/26/it-and-the-corporate-immune-mechanism-the-mother-hen-reflex/#comment-7154 [...] they are always the ones who have to deal with the after-effects of bad customisations (See the “mother hen reflex” post for how that has come to be). But through mapping this issue out, I was able to make some [...] [...] they are always the ones who have to deal with the after-effects of bad customisations (See the “mother hen reflex” post for how that has come to be). But through mapping this issue out, I was able to make some [...]

]]> By: SharePoint Daily for July 28, 2008 - SharePoint Daily http://www.cleverworkarounds.com/2008/07/26/it-and-the-corporate-immune-mechanism-the-mother-hen-reflex/comment-page-1/#comment-1409 SharePoint Daily for July 28, 2008 - SharePoint Daily Mon, 28 Jul 2008 13:31:20 +0000 http://www.cleverworkarounds.com/2008/07/26/it-and-the-corporate-immune-mechanism-the-mother-hen-reflex/#comment-1409 [...] IT and the Corporate Immune Mechanism - the "Mother Hen" Reflex (Clever Workarounds)Recently, I came across the blog of Dux Raymond, a Project Manager, forthcoming author and trainer who looks at SharePoint from a project management perspective. Being rather interested in that area myself, I read his "Empowered by SharePoint" post. [...] [...] IT and the Corporate Immune Mechanism – the "Mother Hen" Reflex (Clever Workarounds)Recently, I came across the blog of Dux Raymond, a Project Manager, forthcoming author and trainer who looks at SharePoint from a project management perspective. Being rather interested in that area myself, I read his "Empowered by SharePoint" post. [...]

]]> By: Dux http://www.cleverworkarounds.com/2008/07/26/it-and-the-corporate-immune-mechanism-the-mother-hen-reflex/comment-page-1/#comment-1400 Dux Sat, 26 Jul 2008 17:37:12 +0000 http://www.cleverworkarounds.com/2008/07/26/it-and-the-corporate-immune-mechanism-the-mother-hen-reflex/#comment-1400 Hi, Paul - Great post. First off, I appreciate you referencing my blog post. I fully agree with you that SharePoint empowerment can only be guaranteed if: 1. There is complete support and buy-In from powers that be (upper management). 2. IT shifts its mindset. The typical problem I see today with SharePoint implementations is that there is a lack of understanding of the true benefits of SharePoint. In fact, IT is NOT giving up control or power if users are empowered to do enable collaborative tools themselves. I see this as mundane tasks being taken off of IT's back (I loathed the days when I was working as an IT support staff and in comes a request to update the newsletter on the intranet). IT can then focus on more complex issues and challenges. In addition, the user community will not see IT as a bottleneck nor even worse, a necessary evil. With this being said, I have met a lot of folks with the IT/IS group (sys admins, developers) not wanting to have anything to do with SharePoint. It's not that they have limited opportunities to gain sound understanding of SharePoint, but their pure underestimation of the technology and arrogant perspective that SharePoint is yet another end user toy with no organizational benefits. SharePoint cannot be compared to existing technologies. It shifts the paradigm of collaborative computing and data integrity management. We have to rethink how information is organized, how people will be grouped and how technology is an enabler not only to the highly skilled technogeek, but to the greater majority as well. Lastly, sound planning and having a SharePoint governance plan in place jointly developed by upper management, IT and the user community is necessary for empowerment to truly flourish. Empowered by SharePoint, Dux Hi, Paul -

Great post. First off, I appreciate you referencing my blog post. I fully agree with you that SharePoint empowerment can only be guaranteed if:

1. There is complete support and buy-In from powers that be (upper management).
2. IT shifts its mindset.

The typical problem I see today with SharePoint implementations is that there is a lack of understanding of the true benefits of SharePoint. In fact, IT is NOT giving up control or power if users are empowered to do enable collaborative tools themselves. I see this as mundane tasks being taken off of IT’s back (I loathed the days when I was working as an IT support staff and in comes a request to update the newsletter on the intranet). IT can then focus on more complex issues and challenges. In addition, the user community will not see IT as a bottleneck nor even worse, a necessary evil.

With this being said, I have met a lot of folks with the IT/IS group (sys admins, developers) not wanting to have anything to do with SharePoint. It’s not that they have limited opportunities to gain sound understanding of SharePoint, but their pure underestimation of the technology and arrogant perspective that SharePoint is yet another end user toy with no organizational benefits.

SharePoint cannot be compared to existing technologies. It shifts the paradigm of collaborative computing and data integrity management. We have to rethink how information is organized, how people will be grouped and how technology is an enabler not only to the highly skilled technogeek, but to the greater majority as well.

Lastly, sound planning and having a SharePoint governance plan in place jointly developed by upper management, IT and the user community is necessary for empowerment to truly flourish.

Empowered by SharePoint,
Dux

]]>