Intranet evolution, best practices, and case studies by Toby Ward.

Add to My Yahoo! Subscribe with Bloglines
Subscribe in NewsGator Online Blog Flux Directory
Subscribe with myFeedster
This Month
January 2007
Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31
Year Archive
Login
User name:
Password:
Remember me 
Web Development & Design Blogs - Blog Top Sites © 2006 Prescient Digital Media. All rights reserved. www.PrescientDigital.com
View Article  Intranet case study: HP

HP has been an innovator for decades. With 150,000 employees in 170 countries supporting thousands of different projects, the intranet has to be solid and a unifying force in such a diverse and disparate company.

 

 

 

@hp is the unifying center of the employee intranet experience – the portal for all employees – with one-stop access to 1,850 intranet applications.

 

Please see the complete article on the Intranet Insider on Communitelligence.com: Intranet case study: HP.

 

Also note the next Intranet Insider World Tour stop is British Airways on February 21st... please see Intranet Insider World Tour: British Airways.

 

 

  Digg this        Post to del.icio.us       Post to Slashdot

View Article  Intranet predictions for 2007

I’m not a big fan of predictions and soothsaying, but I still read those that are well thought.

 

Tony Byrne has developed his Predictions for 2007 which include:

 

  • Google de-googles its appliance
  • AJAX UI backlash
  • Web managers embracing the delete key
  • Falling seat prices
  • Rediscovery of workflow
  • Portal platforms will diversify

I agree with most of Tony’s predictions, but I think there are bigger ones at play. I know I said I don’t do these predictions but since my company is called ‘Prescient’ I feel compelled to become a hypocrite.

 

The year 2007 will see:

 

  • Microsoft crank-up the marketing of Sharepoint leading to more and more customers buying without seriously examining alternative solutions
  • Standalone portal products will continue to be considerably out-done by CMS solutions
  • More vendors delivering a complete all-in-one solution that includes robust content management, search and portal functionality
  • Continued market consolidation with many more CMS vendors being bought, merged or disappearing
  • Dramatic growth in open source implementation and increased profile and functionality for bigger name solutions such as Zope, Alfresco, OpenCMS, and Plone
  • More and more organizations will convert PDF and MS-Word forms to online submission forms with a mixture of in-house and outsourced solutions
  • The search engine market will experience less growth than previous years as more organizations realize their current engine suffices and instead focus on content tagging, categorizing, process and policies
  • Discussion and focus on Knowledge Management (KM) will continue to decline as more organizations instead narrow their attention to specific tools such as Web 2.0 applications
  • More organizations will implement blogs and wikis, but they will still be part of a minority group; social bookmarking and podcasting will still remain little more than a fad on the intranet

Agree? Disagree? What other predictions will come true? Post your comment or question below.

 

  Digg this         Post to del.icio.us       Post to Slashdot

 

For more intranet news visit www.IntranetReport.com

View Article  Intranet as a shopping mall (for ROI)

Intranets don’t deliver good ROI; applications deliver great ROI. Or so we’re told.

 

Why do stores like the Gap, Target, Nordstrom’s, etc. locate in malls? Malls exist because they attract a lot of shoppers and therefore retailers like the Gap are willing to pay a lot of rent to realize the sales and ROI that come from those shoppers. If the shopping mall doesn’t exist, a lot of retailers lose out. The stores don’t get the sales, and they don’t get the ROI.

 

The intranet benefits applications as the mall benefits stores. Intranets drive traffic to applications which reap the big ROI.

 

One of my favorite application ROI examples is the fantastic SuperSleuth sales lead tool on the SodhexoUSA intranet (see Best practices case study: Sodexho USA). SuperSleuth is an intranet application that encourages employees to submit sales leads and prospective clients via the intranet. Successful leads submitted via the SuperSleuth intranet page generate cash rewards of up to $1000 for the person making the submission. Sodexho says it has contributed to a 100% increase in sales leads in the past year and led to US$90 million dollars in managed volume (net client sales including sales by client).

 

 

The Sodexho intranet home, compliments of SodexhoUSA

("Revolutionizing Employee Communication", Angelo Ioffreda, Sodexho USA)

 

SuperSleuth is an intranet based tool that would be no means receive that volume of leads nor generate the dollars it does without the intranet to drive those leads. The intranet home page promotes the tool and generates the traffic that reaps the reward.

 

It’s no longer acceptable for an accountant or techie to tell you that you can’t count the ROI on the employee directory, or online expense form, or sales lead generator as intranet ROI. The intranet begets the tool that delivers the value and as such should be recognized as a successful delivery platform that delivers ROI.

 

While some tools like online benefits enrollment might still generate a high ROI without the foundation that is the intranet, others like SuperSleuth depend on the intranet. It’s fair to say, based on my anecdotal and measured observations, that many applications owe 50% of their value to the intranet.

 

Without the mall, many stores would scramble for customers – many enterprises are without a business model. Like the mall, the intranet ensures the success of its application stores and makes possible a business model that wouldn’t exist without a supporting foundation.

 

To measure and increase the value of your intranet, please dowload the free white paper, Finding ROI.

 

  Digg this         Post to del.icio.us       Post to Slashdot

 

 

For more intranet news visit www.IntranetReport.com

 

© 2006 Toby Ward - Prescient Digital Media

View Article  Why you should or shouldn’t choose Microsoft Sharepoint

I receive many, many questions about different content management systems and portal products and asked for my opinions on one product or vendor versus another. My response, in short, is: who cares!!

 

Okay usually I’m a little more polite than that, and I try not to foam at the mouth or have a hissy fit (hey, I’m only a product of my environment and I have two young daughters). My long response is a little more intelligent: it doesn’t matter what a product has or can do, what is more important is what it can do for you. More specifically, how does it meet your organization’s specific user, business and functional requirements?

 

 

Sharepoint promotional slide (Microsoft.com) with the requisite

stock photo to make me want to buy... she's cute but...

 

The number one vendor I’m questioned about is Microsoft, particularly Sharepoint. I know some friends and colleagues at Microsoft will give me a tough time on this, but I am completely technology neutral. Neither my company Prescient nor I have any technology partnerships or reseller (VAR) agreements with any vendor. That makes me and Prescient a very rare breed. The vast majority of even the small web design shops have partnerships with one or several vendors like Microsoft; making those firms bias. I am not and have no axe to grind with MS. In fact, I like Microsoft, I admire the Sharepoint team, and I like Microsoft’s own corporate portal (MSWeb).

 

However… I am not yet intimately familiar with the latest version of Sharepoint. But I am not a fan of the previous version, and I do not like the Microsoft CMS. The previous version of Sharepoint and CMS were very simplistic and limited; fine for very simple document management, but in my opinion, not very good for an enterprise intranet. Sharepoint is a fine product for some organizations, but wouldn’t be a good fit for many others.

 

Here’s the crux of my point: what works for one organization is sure not to work for yours. Everyone organization is unique with unique needs. This is not just true for Microsoft, but for ALL vendors and products. We’re working with a client that uses Plumtree. And frankly, this implementation, like most of the Plumtree implementations that I’ve seen, is brutal. However, I’ve also seen a very good Plumtree implementation for GlaxoSmithKline (I’ll be doing a case study article in the coming weeks).

 

But forget about what I have to say about Sharepoint, or what IT says, or any other company (including Microsoft). Best spend your time determining what you need to do, and then match those needs to the available solutions.

 

If you’re planning a new intranet – or extranet or website – take a few weeks to really thoroughly document your user, business and functional requirements for a CMS or intranet platform and then match them to several different vendor offerings. There are thousands of potential solutions to power your intranet. Take the time to thoroughly understand and document your needs and a few of these vendors.

 

The best way to find the best solution for your organization’s needs is through a *detailed* RFP. Get the vendors working for your business… don’t just look at the product offerings of a couple and make a decision. It might be that Sharepoint or Plumtree works for you in the end, but why not make certain. It’s just too expensive and complex a decision not to spend a few weeks gathering requirements and evaluating a few vendors accordingly.

 

NOTE TO VENDORS: Please don’t spam me with your sales pitches on why Sharepoint or your solution is the cat’s meow. This is not a critique of Sharepoint, Plumtree or any other solution. It’s a recommendation for following a *process* to choose Sharepoint, Plumtree or another solution. I’m not above being bribed thoug; but I’ll still remain technology neutral  Good case studies are always welcome though and frequently featured here.

 

About the author: Toby Ward is an intranet consultant (Internet consultant too) and the founder of Prescient Digital Media. He has worked with and improved many, many company intranets including Amgen, HSBC, Mastercard, Manulife, PepsiCo, Royal Bank, etc. Toby and his company are consultants for hire and can help improve your intranet… if given the right amount of time and motivation J Toby is also available to watch or play just about any sport – including the culinary sports J You may contact this intranet consultant directly.

 

 

  Digg this         Post to del.icio.us       Post to Slashdot

 

 

For more intranet news visit www.IntranetReport.com

 

© 2006 Toby Ward - Prescient Digital Media

 

View Article  Open source myths

My colleague Seth Gottlieb from Optaros knows open source very well. In fact, he’s probably the most knowledgeable guy on the planet when it comes to open source content management systems (CMSs) I say this of course with no hesitation despite the fact that he is a die-hard Red Sox fan, and therefore by definition, a sworn enemy of a lifelong Blue Jays fan (we won’t hold it against him though since he probably doesn’t know any better J).

 

 

Coming to know open source as well as he does, Seth is well versed in all the mythology and hearsay about open source. Let’s face it, most of us know little about open source (or at least until recently) and yet most have some very definitive, pre-conceived notions about open source. But thanks to Seth and some of his colleagues I know a lot more about open source now then I did at New Year’s last year.

 

Here’s perhaps the most valuable education you can get on open source solutions, and more bang-for-the-buck then any book or course: Seth Gottlieb’s top 8 myths about open source – myths for both the critics (anti) and supporters (pro). I’ve paraphrased some and added my own opinion in places and analysis, but this is almost all Seth’s work.

 

Anti-open source myth #1: Open source will cost more than commercial.

 

Read the full article Open source myths