When a business utilises Microsoft SharePoint more and more, the solution gradually changes character from an application to an actual enterprise solution. Often, the solution is not upgraded in the business architecture, because the need is not realised before it is too late.

Symptoms such as performance issues, an inadequate backup strategy, slow reaction to changes, unclear decision making processes, and no central prioritising of the transition from application to platform, begin to emerge. 

To help you deal with these issues, we have put together a list of Do’s and Don’ts to help you prepare your SharePoint solution for its new role.

HOW ABOUT...

Strategic alignment?

• DO: Align platform, internal communication, knowledge management, collaboration, and application strategies
• DON't: Just start – you’ll end up with a lot of unanswered questions and resistance from stakeholders

Top management engagement?

• DO: Ensure you have funding and engagement from top management.
• DON’T: Just start – you’ll end with a lot of unanswered questions and resistance from stakeholders

Governance?

• DO: Create clear governance for all four dimensions
• DON’T: Play along

Project management?

• DO: Engage a senior project manager, for example a programme manager, who understands your business, as well as IT
• DON’T: Think this is just an IT project. It is IT and business.

Architecture?

• DO: Be sure to include designs for all types of architecture: information, system, enterprise, topology and business
• DON’T: Under-engineer it.

Ensuring ROI?

• DO: Make it clear that the ROI differs across the various feature areas. Conduct the change management properly
• DON’T: Over-sell it internally. The business case is clear, but usually not tangible in the investment phase

Nurture and control sprawl?

• DO: Acknowledge that SharePoint is a rapidly spreading tool. Embrace it with proper governance and guidance, and use it to back up the business case
• DON’T: Play along. This will lead to clean-up jobs, poor server performance and unnecessary re-active communication

Vendor management?

• DO: Select a vendor who understands the whole life-cycle, can predict the evolution, be proactive, agile, stable and think internationally
• DON’T: Choose a platform vendor that does not suit your basic needs