Launching a successful intranet site

Alex Angas
  • Launching a successful intranet site Alex Angas

    I'm launching a SharePoint intranet site in a couple of weeks time. What can I do to ensure it is successful from Day 1?

    (My role is as SharePoint developer/admin but I will make recommendations to the business sponsor.)

  • There are lots of things that are recommended to make your SharePoint intranet successful. Some are: executive buy-in, training, incremental releases and updates, proper governance/assurance (as you prefer to call it), etc... You know your company's culture best, you will need to look at what has been successful and what has been unsuccessful and try to incorporate what you have learned from those other initiatives with the tips from others. Many refer to Joel Oleson's 10 Steps to Successful SharePoint Deployment (you can find that on sharepointjoel.com in his presentations on the right) but I have found some of Lee Reed's tips on driving adoption very helpful as well. Here's one of his posts that offers some good tips: http://www.sharepointlee.com/Lists/Posts/Post.aspx?ID=7

  • Try focus on next aspects:

    1. Collaboration (team sites)
    2. Portal (company give infos to users)
    3. Search
    4. Users Training and Education

  • 2 weeks is a short time to launch if you haven't done anything yet. However get the buzz out there. I find you need to get some SharePoint champions on your side, individuals in the organzaabion that simply love SharePoint (preferbly not IT) and can offer some support. People that are passionate about the product will take your cause far and lead by example.

    The other thing would be to get on the marketing bandwagon. Nobody hates more than to one day come in and see some new thing IT stood up overnight with no preparation. Go check out the RampUp toolkit. It's a set of documents, resources, and media that you can use to promote SharePoint. You can find it here.

    Finally, be open and there for the users. Once you launch babysit the launch and keep it fresh (with new postings, etc.) and don't let it become a stale tumor in your organization.

  • The technology will not make it "work", that's for sure. Executive buy in is important, but even better, executive behavior. Get them to stop emailing docs and put them in the Intranet, get them to blog, etc. Basically, lead by example. If they don't no one else will do what you want.

    Also look for quick win mini-apps that you can whip out fast. Paid Time Off Requests are (surprisingly) often a winner, and very easy to build. Think about what things everyone in the organization does all the time (and usually hates) and give them a better option.

    Don't let the Intranet stand still. Go for continuous improvement, not big releases. Talk to people a LOT. Find out what is working for them and what isn't.

    So much of all of this depends on the so-called "culture" of the organization. No one knows that better than you if you are in the midst of it.

    M.

  • Success is a hard thing to define. But back when the project was launced, the customer should have defined success criteria for how they would define the intranet as a success.

    Examples could be ROI for management, testers and developers would probably have a success criteria that no bugs is found after launch, IT could have how uptime and that pages are served fast.

    As a developer and architect I would reccommend thorough testing, and test deployments to secure that the site works as designed and that it can actually handle that it becomes a success.

  • Definitely make sure your business sponsor plays an active role as an 'evangelist' in the organization, both above and below their level. I have seen many implementations fail that don't have an engaged business sponsor, just as often as those without a business sponsor.

    Here's another great article from SharePoint Joel as Lori pointed out earlier. http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=23

Related questions and answers
  • We have experienced a strange issue in SharePoint. We backed-up and restored a site collection from WebApp1 to WebApp2 and both the site collections have Publishing Features activated (BLOB CACHE was NOT Enabled) After successful restore , none of the sites were working. Following Exception has occured : Site id <> could not be found OR File not found Solution : In the stack trace there method sitecachesettings(guid id).....Reset the IIS, and booom every thing works fine :) My Question : Where is object cache stored ??? how it works?? point me any links where I can dig in deep

  • on the intranet site. On each individual page, I have setup a Content Query Web Part that displays the documents that have the corresponding Page value set (i.e. if a document Page value has been checked for "HR...My organization is in the process of converting our intranet over to a SharePoint solution. Part of this intranet will be the movement and organization of all our internal documents. Currently, we... items. Does anyone have any ideas as to how I could accomplish this, either via CQWP or by different means? Goals/Requirements of Installation Allow Intranet documents to be maintained

  • I am using SharePoint Server 2007 on Windows Server 2008. I am using Search Center to crawl web data source (i.e. crawl web page from other web sites). My question is related to crawled page counters displayed for the web data source log page of Search Center. My question is, there are 3 crawl counters displayed, successful counter, fail counter and warning counter. For each counter value... stored in Search Center? I am not sure whether there are any duplicated Urls in the 1000 counted pages? BTW: I have this confusion because I set daily incremental page crawl, for example, if http

  • A client is asking for a custom application to be created and deployed within the corporate intranet. Part of the requirements are to publish some of the content also available on the internet site. Both sites are built on SharePoint 2007 but they are on different farms and on different networks. Can the Content Deployment API (and associated tools) handle moving selected content across networks with no direct connectivity? Can we use web services? Has anybody done this sort of thing? If so what approaches have you taken? Thanks, James.

  • I am planning a SharePoint 2010 solution with an intranet / extranet and internet site. The intranet and extranet will probably use different authentication methods. The internet site will probably be in a different domain (DMZ domain) How can I publish an article on one site, and then have it published to the other sites? Is there a way to do this in SharePoint, or should I for example use Biztalk between the sites?

  • I am using SharePoint Server 2007 Enterprise with Windows Server 2008 Enterprise, and I am using publishing portal template. I have created a web application for intranet zone. I want to know how to change the port number of the web application? Could I change it directly in IIS manager (is this way safe)?

  • For the past couple of days I have been setting up a brand new SharePoint Server 2010 running on top of Server 2008. This installation is intended to be used with Active Directory and will be used as an intranet for our organization. Everything installed correctly and the SharePoint install itself went fine. I'm at the point now where I am running the SharePoint 2010 Products Configuration Wizard. The thing that is bothering me is that the configuration wizard runs without me needing to enter any information (Service Accounts, Database Server, Admin Site Port, etc). Should I have done

  • I am working on a new SPS 2010 installation for a client that will be used to replace their intranet. As it stands, the current intranet contains around 1000 documents that are saved amongst various network drives. Part of the client's requirement for the new site is that they want all of these documents in one list so that they can update the metadata and view the site contents from one central location. The issue that I am running into now is that displaying all of these documents as one list causes document list page to slow way down which makes the editing of the document meta data

  • I have a SharePoint intranet site where I need to allow users to upload certain documents. These documents need to be only PDF files for example. What is the simplest way to restrict the document library to only PDF (just checking the extension PDF is fine) ?