A couple of weeks ago, me and a customer of mine gave a lecture about social intranets and key factors for a successfull implementation.
Since we had been working together with an implementation of a social intranet for almost a year, we had some experiences that we wanted to share.
There have been a lot of articles published in the last decade, showing that the majority of IT projects tend to fail in one perspective or the other. The main reasons for failure seams to be:
- The budget wasn’t held
- Not delivered within promised time frame
- The product owner didn’t get what he/she wanted
There are some things that I believe will reduce the risk of failure. I’ll try to share the most important ones in this post.
Prestudy
Make sure that you make a thorough prestudy that answers the questions “What do I, as an employee, need (not what I would like) to do my daily work. This could result in a prioritised list that could be used as a starting point for the product backlog. Choose the top 10 from this list for the implementation project. Save the rest for after the project is done.
Implementation
- Use an agile method, preferrably scrum, when implementing this.
- Make sure that the requirements answers the questions [Someone] would like to do [Something] because [Business need]. This will make sure that the developers understands the specific requirement and therefore can decide on the best solution for implementing it.
- Try to work with small prototypes and reqular meetings with the product owner. This will make the gap between business and IT smaller and decrease the risk of failure.
- Make sure that you plan for how this application should be maintained after the project is done. If possible, make one of the developers from this phase join the project from the start.
- Make sure that the product owner understands SharePoint’s potential and that a lot of requirements can be met at 80% with very little effort.
Launch
It’s important that you make a thorough launch plan for the intranet. Try to create a curioisity in the organisation before the launch so that the employees knows that something is up. In this case, the customer took inspiration from Google+ and Facebook launches by creating a reference group that had access early on. There were also serveral ambassadeurs that could spread the word.
On the morning of the launch, members of the project handed out breakfast bags to everyone with a little note that told the employee to sit down, eat the breakfast and take a look at the new intranet. This became a success and about 25% of all the employees wrote a micro blog post on the intranet at this day.
There are a lot of other factors to think about other than those I’ve mentioned. Depending on the organization you will be faced with challenages on many levels, both organizational and technical. The risk of failure will be reduced if the mentioned steps are followed.
What do you think?
Are there any other important factors that I haven’t mentioned?