Monday, August 10, 2009

A Success Story at Cal Poly Pomona

“With Word, the documents were not very searchable, and we had limited ability to share these documents at the same time. We tried to use a CMS system to create internal web pages, but it wasn’t set up to manage dynamic pages with multiple contributors at multiple times. It was unwieldy and simply not friendly for collaboration.”

This is a direct quote from a wiki user and probably has more weight than when I toot my company's horn about strengths of wikis over word and CMS systems.

I promise I didn’t make it up. Kevin Morningstar, executive director of Student Affairs Information & Technology Services (SAITS) within the Division of Student Affairs at California State Polytechnic University Pomona (Cal Poly Pomona), said it.

There’s a new case study on the SAITS experiences and successes to-date with SamePage. In it, Kevin explains how, for the first few years of its operation, SAITS was charged with (and employees struggled with) finding ways to create and share effective user and technical documentation. They tried and discarded other solutions before determining a wiki was the best fit.

Kevin explains that when his team found SamePage: “We jumped on it. SamePage came pre-packaged; it was already executable to be immediately up and running,” he noted. “And we had it up and running in 24 hours with one staff member taking care of the set up.”

“I can’t imagine we could have made a better choice,” he said. Read the rest of the case study.

No comments: