Random Thoughts on Instructional Design
Dr. Kimball did a wonderful job of presenting how the Lake Washington School District (LWS) implemented of the Sharepoint portal platform.
The district needed a way to integrate their data to address accountability pressures, support increased requirements with fewer resources, and support fiscal responsibilities. They also wanted a way to provide real time information to stakeholders — when and how they wanted it, and to capitalize upon student skills, interests, and ability to multitask.
The purpose of the LWS portal project was to create a customized user experience that allowed for a variety of user roles. They also wanted to provide a common user interface that provided connections to datasets, used a single sign on, and to provided client notifications services.
Some of the challenges LWS faced in selecting and implementing a portal system were:
Once a portal or series of portals are selected it is imperative to nurture vendor partnerships, and assure that the tool(s) are easy for teachers and staff to use.
LWS used a three passed approach to implementing their portal system.
Microsoft Sharepoint was selected as the platform and both HP/Microsoft collaborated on the implementation. The district decided to use an Australian code set instead of implementing an â€œout of the boxâ€ version of the product. This decision turned out to be a disaster. The code was non-standard and required a great deal of customization.
Some of the other issues that they ran into in this phase are that the product was not as mature as they had hoped, and that providing different tools sets for different users introduced new levels of complexity.
LWS decided to retrench and implement Sharepoint out of the box functionality. They also decided to implement the easy function first then move onto the more difficult and items that would be transparent to the users in subsequent phases.
The product was implemented throughout the district on a per request basis and little training was provided. All authors were allowed to customize their pages and decide on what data they wanted posted and were it should be posted. Allowing the authors this type of freedom acted as a catalyst for a grassroots movement among the faculty and staff could really push the envelope. Some of the schools have even replaced their traditional websites with the portal. Juanita High School was the first school to replace their website http://publicportal.lwsd.org/schools/JuanitaHigh/default.aspx.
In the next phase of their implementation LWS plans on adopting a new calendaring application, provide home access, address back end data integration, and continue partner development.