MITE/Leadership

Leadership

 * identify chain of command in the organization, to ensure guiding principles -- evolve into multiple information architectures
 * identify designers - who understand information design and 'architecture'
 * focus on the information architecture
 * Ruth - will inform everyone - Brian, Nancy, Terri and Dani, and keep Gary in the loop
 * Keep Gary & Ruth in the loop for design
 * After Info Architecture is developed, then we can sit down with the Communications Team, to decide what content is to be developed
 * Be more precise in the development of the HippoCampus (Individual) and NROC (Institutional) values
 * Future conversation - strategic messaging (Teri, Dani, Jonathan); reflective of other groups (look at it more broadly) - deeper messaging with Ruth, and Nancy)

Project History
...when you go to NROC Network.org, you will go to this area - three tabs MITE with org information, NROC, about NROC information, member services and networking opportunities, and then another tab Research and Policy with MacArthur/DML and OER information.
 * re: features and functionality: Ruth
 * Brian had set up an installation at NexLearn; then had Phil at Nexlearn took Corporate MITE content and NROC content was recreated in Drupal...
 * now we have a Drupal installation that has converted all of that content on the site.
 * we are rethinking the Network Community stuff, focused on Member Services...and integrating all of our information and member sites in one drupal site, based upon Brian's recommendation...
 * regardless of URL, you can get to the right place, with one click of the tab...
 * mainly focused on what they need in the NROC tab - for support, marketing, implementation tab, and resources for members - much easier and clearly displayed organization that's available to our members.
 * redesign and expansion and online and staff meeting... where we are now...?
 * not changing the URLs we have - if someone puts montereyinstitute.org they get to MITE org info, nrocnetwork.org goes to NROC tab.
 * got to be a single decision-maker - as an entity that has a final decision-maker, that there has a final decision maker (i.e., Brian, Nancy & Jeff and Ruth) - final feedback... sharing design proposals, iteratively... so there is the opportunity to get feedback from the team...
 * cut down on people's busywork, and thinking through workflow...
 * sharing feedback, and getting things done iteratively...
 * constituency - that we're messaging..


 * Gary:
 * website : communicates with new members; and folks already members
 * 1. info is tiered, and you find out more about as you move down
 * 2. a bit different


 * architecture is navigable; layering of the architecture has to be mindful of that; and then add to that a sales tool for Terri and Dani,
 * reasonable navigation - trying to find an architecture that is transparency and allows all of the constituencies that need to be developed
 * Information architecture for new folks, and IA for existing members. (Sam)


 * a place for existing members to find stuff
 * Teri and Dani connecting with members and providing consultory services


 * Ruth - coordinating redevelopment with Salesforce (a priority, but not 1st.; automating things to be automated...


 * Gary:
 * members have different needs...but so far they have talked about "wants'
 * now it's what people 'need'
 * two information architectures blend together, which are useful to different audiences


 * rapid prototyping - get feedback - put it out there, and what folks are looking at it: Brian (History), Nancy (Customer), Terri and Dani (looking for it as a tool); then put it into customers...
 * bring our existing customers into this


 * iterative development will help us forge multiple information architectures... (Sam)


 * Gary: the architecture should be entirely separate from design; then bring in the designer - standard tufty applied to different interface
 * info design is the starting point, and then made more attractive and transparent into this navigable form, that it's hierarchically built that way, and brings you visually into it.
 * Step I - get the information architecture done (as driving principle), and then bring in visual design


 * now we have a laundry list of expectations; now, get our group of respondents... now to just a couple of folks... (Brian, everything who went before); Nancy )new users; and Dani (and then we'll get what we want)
 * Gary: Ruth and I will focus on design - and Gary wants to be kept informed about the design


 * User Permissions set up - Brian wanted to transfer all of our content in the Drupal; we can edit everything... we can set up restrictions, but everyone

OERs

 * what is the positioning of OERs as related to our work
 * i.e., under Research and Policy tab (OERs)
 * OER is central to everything we do, it's a cornerstone
 * individuals: OER is the lead issue, it's how we couch everthing - high quality, multi-media based education
 * institutional value proposition - it's less about OER; OER is a feature of what we're offering... (not necessarily a decision-making lever); but the high value, works with different configurations, works with diff. CMS, modifiable;
 * OERs are incredibly useful tools for attacking standard problem issues...
 * messaging - fabulous educational tools for solving problems, and btw: they're OERs


 * Messaging is very different, has got to be part of this architecture...
 * Hippocampus - that materials are available at HippoCampus Member Services area is really focused on getting prospective members to participate...
 * we have to be more precise in the values for institution (there's a whole set of institutional values that shouldn't be anywhere near Hippocampus.
 * Drive deeper usage - NROC; usage and feedback from community colleges; Ministry of Education, etc. - formerly focused on research
 * consultory services in how to implement OERs - this will continue to grow
 * formed a relationship with Petersons.com (geotargeting advertising with colleges and universities), on HippoCampus (advertising for enriching the content)
 * OERs - federal funding over the next 10 years...and providing consultory services, and then facilitate partnerships.
 * WikiEducator, and Creative Commons - broader reach than NROC, etc. - promote OER Quality Guidelines