Proposed Agenda

MEETING OBJECTIVE: Decide what new processes we feel would be valuable to implement within the community related to "instructional visioning".  Once these are identified we should surface them within the larger community and get feedback, particular from the product council and product manager.

  1. Process for Implementing Design Investigations
    1. Proposal: Based on what is learned from the Sakai 3 design efforts currently underway (particular the Samigo and Sakaibrary groups), a community-wide practice would be established which would:
      1. Create a Sakai Community Guide for Implementing Design Investigations#### This would be a broad overview of the investigation phase of the design process that would be posted in Confluence for developers and those new to the approach.
      2. Establish a proposal process by which projects could request assistance from the T&L and UX group in developing and implementing a Design Investigation
        1. This might include things like: Definition of the target audience, user attributes to cover, interview recruitment plan, interview protocol and contextual inquiry guide, etc.
      3. The proposal would be sent to the UX and T&L groups to review and comment on (this might end up becoming part of the product development process).  If accepted, the UX and T&L groups would assist in implementing the design investigation.
        1. This would not require that the T&L/UX groups do all the work but would allow developers, etc. to tap into their knowledge and expertise during the design phase.  It would also provide the T&L and UX groups with direct input into the development process (which I see as being valuable and thus worth some of my time).
    2. Timeline: October - December 2009: engage in current design investigations; January - June: Document process and present it at 2010 conference.
  2. Publish a Sakai Instructional Technology Trend Report
    1. Proposal: This report would research and identify important trends in the instructional technology domain that have implications for Sakai in the 2-3 year window.  This would be a high-level report who's objective would be to get important trends on the radar of the community and those institutions and groups who are engaged in development work.  It may also be used by groups, such as the product council, to push developers to factor trends into new development projects or when tools/functions are re-designed.
    2. Report Format - I'm imagining a relatively brief document posted in Confluence (20-25 pages).  It would be "refreshed" once a year with new trends being added and those that don't look likely to take hold removed.
    3. Work Plan - The first version of this report may take some effort to research and assemble but once it was created the "refreshes" would not take as long.  My guess is that with a large enough group (10-15) contributing that it could be created in 3-4 months.  It might be useful to consider establishing some informal relationships with groups such as ELI and the New Media Consortium (who work on the Horizon's Report) as part of this effort.

DISCUSSION TOPIC: Instructional "Metaphor" for Sakai 3
With the plan to move away from a tool-centric design in Sakai 3, many of us are struggling to understand what the vision or metaphor for what the user experience will be when faculty, students, researchers, etc. enter into the new environment.  There is also the concept allowing for multiple metaphors that could be designed for different purposes.  For example, the metaphor that works for a course may be different then for a project site.

NEED: We need to flesh this issue out more so that we can begin to understand how we might address it.

Meeting Minutes and Notes