Tips from the Trenches: SharePoint early adopters speak out

“Get the business involved from the beginning and ensure it does not become an IT project. Give yourself twice as much time as you expect to migrate content.” - Knowledge Manager, Australian water utility

“SharePoint offers teams in diverse locations to collaborate in real time and the means to unilaterally upload content, data and information, while relying on a separate web team to fit their requests into workflows.

“SharePoint backed database grows exponential as more teams and staff accept the challenge to participate and collaborate. The difficulty is the ongoing maintenance and relevant content both in terms of business use and time based correctness as staff and business restructures move ownership around. This eventually leads to content degeneration and relevance.

“Seriously think of business requirements, ICT capabilities, records management requirements within the relevant sector (public or private) and the ongoing maintenance costs.” - Director, Knowledge and Records Management, Australian federal government department

“We have used SharePoint since 2001 so each version has allowed us to move closer to web only platform.

“Design the platform with a view that it will constantly change if you want to meet evolving business needs. Each solution you deliver to the business will evolve, so design the solution with a view to constant easy change....not traditional long redevelopment lifecycles otherwise the staff will go back to spreadsheets and file shares when you can't deliver.” - Enterprise Architect, Local government.

"Ensure that a new installation is phased and is driven by strategy and governance, and is underpinned by good information management practices, training, support and change management.

"Ensure that you start with clearly defining business requirements, engage users from the outset to ensure that you understand their needs, which should feed into business requirements." - Advisor, Knowledge Management at GS1 Australia