Phase I
From ETS
Completed Milestones
- Site Audit
- Completed Director interviews
- Completed Card Sorting
- User Profiling
- New content collection
- Wireframing
- Paper-prototyping
- Navigation
- Creating templates and features in Plone (WebLion)
- LAUNCH (Aug 21, 2008)
Team access to Milestones and To Do lists are in BaseCamp
Design Brief for Phase I
TLT Web Site Redesign 2008, 05/27/2008
Project Overview
Overall Goals
Revise the information architecture, visual design, content, and functionality of the Teaching and Learning with Technology Web site (http://tlt.its.psu.edu/), so that it better meets the needs of users and of TLT.
Vision
- Users find the Web site easy to use, informative, and useful.
- The Web site supports the TLT mission and strategic plan.
- Content authors can keep content relevant to users and up-to-date easily.
- The site simplifies the user experience and creates a compelling and engaging experience.
Perception/Tone/Guidelines
The target audience (faculty) feels that TLT is a credible resource. They know TLT via work relationship and through TLT symposium and other conference sessions. They do not come to the TLT Web site for this information (in general). If they go to a Web site, they go directly to the service site. They are generally most interested in getting options for accomplishing a specific task. They are very interested in personal consulting.
Communication Strategy
The communication strategy is how we will convey the overall message. Based on the director interviews, some of the messages TLT wishes to convey through the Web site are:
- Providing best practices in pedagogy
- Helpful (Consulting)
- Informative (Credible)
- Friendly, hip, inviting
- Engaging
- “Living the brand”
We will convey the message of credibility and helpfulness by simplifying the experience and create a compelling, intuitive experience. We will display testimonials liberally to illustrate practical application of services and practices to cultivate a culture of technology and engagement. Related content will have the ability to be built from different sources and be distributed through the use of content aggregation (RSS/XML). Content creation will be simplified so that content authors and users alike can post easily via a content management system. Messaging and action items will be clear throughout the site, and the visual design and concept will make people remember TLT as a reliable resource.
Target Audience
Using the information gathered from users during the card-sorting sessions and from the director surveys, we got a sense of who the site visitors are, why they are coming to the site, and what tasks they are likely to perform. We are in the process of detailing user personas of TLT’s various audiences. They will include characteristics, education, language, computer expertise, domain experience, motivation, and/or expectations.
Audiences
Faculty (teaching + research) Faculty/Student Faculty/Staff Instructional Designer Student Staff Outside Universities
Initiatives
This project includes concept development, design and layout, production, and programming for the TLT Web site. The structure and hierarchy of the site will be based on user-centered design (from card sorting and paper-prototyping usability sessions). Production of the site includes content creation, writing, and editing, and the creation and optimization of all files/images. The site will be created using the Plone content management system. This project is scheduled and estimated to complete its first iteration on August 15, 2008. Factors that increase or decrease the production schedule (for example, late content or additional features added) may affect the schedule. These factors may be rolled into the next iteration phase.
Initiatives for August 2008 Launch
- Reorganize content
- Migrate critical content into a content management system
- Create multiple pathways for users to find content
- Create a flat information architecture structure
- Use “gallery” pages to provide multiple gateways into information
- Create “springboard” pages for services that have multiple related Web sites
- New content: user testimonials
- Increase usability
- Optimize for accessibility
Future Initiatives
- Create a TLT-wide style guide
- Plan for cross-TLT Web site link-backs and aggregation
- Improve search to includes all TLT sites
- Increase copyright and accessibility awareness in relation with each service
Usability Testing
Wireframes
- Springboard Page (draft)
- Home Page and Faculty Profiles (draft)
Committee Meeting Notes
Meeting Notes for Jan 15, 2008
Kick-off meeting
Attendees Audrey, Allan, Catherine, Dana, Derick, Erik, Mary, Tara
Goals for this meeting
- Introductions
- Discussion of the group's goals and first steps
- Selection of a committee chair (short-term, rotating appointment)
- Overview of the steps of site redesign process
- Planning next actions
Results of the meeting
Step 1: the design plan The first goal of this committee will be outlining a website design plan including an estimated timeline to present to John Harwood by February 1, 2008. Audrey has been honing a redesign strategy for this first step, which largely consists of defining the project. This step involves...
- identifying our audience by creating user profiles and conducting user and stakeholder interviews. We have already identified the audience as mainly faculty across the entire university as well as some student-oriented services. [added from email discussion:] The TLT audience served by Training (and CLC?) is predominantly staff, as well as faculty and graduate students. Special Projects' audience is also mostly staff: technical and managerial.
- planning via identifying who else should join or assist our team and what the resources are
- planning for iterative usability testing
- setting up a communication staging area where the team can all stay on the same page
The result of this step will be a document clarifying the high-level goals and initiatives of this phase of the redesign (and goals for subsequent iterations), while balancing the users' expectations and needs with the stakeholders' strategic vision and goals, looking at the organization as a whole. It will outline...
- how long things are going to take
- why we're doing things the way we are
- what elements are important
This document will serve to get buy-in and get everyone on the same page. Audrey will work with Catherine this week to edit the plan and finalize it in our next committee meeting, scheduled for next week.
Housekeeping Audrey Romano will chair the committee.
A communication staging area to facilitate feedback and collaboration will be set up.
Miscellany Organize around the things that we do and not how we're structured. Amen!—Erik Rose
To do Another thing we can do immediately is make a note on the current TLT site's homepage that gives notice that a redesign is in the works and solicit volunteers for user interview and get general feedback and suggestions.
In the next meeting we will outline the process of conducting user interviews and creating user personas.
Meeting Notes for Jan 24, 2008
Redesign Overview Plan Drafting/Time Assessment
Attendees: Audrey, Allan, Catherine, Derick, Mary, Tara
Goals for this meeting:
- Overview the more detailed steps of the ReDesign Workflow Plan. Get team endorsement.
- Review estimated time scales for DEFINE and STRUCTURE processes. Get team endorsement.
- Process Plan Completion:
How should this be delivered to JTH? What level of detail? Does he need a physical document or direct him to the Intranet Project Profile. Is this document enough or should an executive summary be created with this outline as an appendix? Catherine and Audrey will complete this stage and alert team of its completion for final team approval and delivery to JTH.
- In the DEFINE > Plan stage, do we accomplish this as a team or have one person assess and present a draft for team to endorse?
- Next actions:
- Begin auditing current site(s): main TLT (and unit sites). Who gets assigned, when can this be completed?
- Communication Staging Area: Project Profile page on the intranet exists for all of TLT to see an overview of the purpose, process, and progress of the project. However, for the team, a more project management focused tool may be necessary (e.g. Basecamp). Project Definition vs Project Management (outbound communication (PR), team communication and versioning, todo lists, milestones, push vs pull, feeds, is this basebamp + intranet? Or wiki?)
Results of the meeting:
The Redesign Workflow Overview Plan will include a short paragraph summary with key points in how the goals and objectives of the project will be defined and give a basic time estimate for the first two major processes (DEFINE AND STRUCTURE) and a ballpark end date for possible scope scenarios (July 08-min to Sept 08-max). Catherine and Audrey will meet next week to create this and it will then be sent to team members to revise and finalize. It will also undergo a review by Cole Camplese.
Specify in the document also that Unit Directors will be interviewed one-on-one by one to two team members. One to lead the interview and the other to record. Request permission to tape record. Contact JTH to set up the first Director interview.
For next meeting, Audrey will provide a draft interview questions which will be discussed and finalized by the team. The team will decide who will conduct the interviews for each of the Directors and will schedule them within the next week, if possible.
The difference between an audit and an inventory is that an audit will cover the main sections of the site (skeleton) and who currently is responsible (maintains) for the pages. For next meeting, Audrey will provide a process for auditing websites. The team will determine if we can accomplish this task each on our own or if we need help from the team or from others within our unit. How long do we need to accomplish this process?
Meeting Notes for Feb 11, 2008
Director Surveys, Site Auditing Tactics
Attendees: Audrey, Mary, Tara, Allan, Catherine,
Announcements: John Harwood has reviewed and responded positively to the Redesign Process.
Goals for the meeting:
- create director interview survey
- identify who will interview which directors
- discuss user interviews
- discuss how to approach site audit
Results of the meeting: In order for the interviewers to be prepared to conduct the Director interviews, we want to be a little more knowledgeable about the TLT site content and usage. We decided that a cursory site audit will help us have a better sense of the content and functionality of the current site.
Previous to this meeting, Audrey met with Christian Vinten-Johansen (Special Projects) to follow-up on site auditing tools. Web stats for the TLT website is available here on the staff intranet under the book Web Statistics. The web statistics for various ETS web servers are analyzed using an open source program called AWStats. More details on that later...
The Google Sitemap Generator was suggested as a tool that will "create Sitemaps from URL lists, web server directories, or from access logs". This could help us get an idea of general site sections, as a site map does not currently exist. The site index, which does exist, does not show architecture or relationships between the content. Audrey sent an email to Jason Heffner (ETS) immediately following the meeting to request use of the Google Sitemap Generator as well as asked for recommendations on other site auditing tools.
Consult with other unit staff that has experience with site logs, search keywords, audience...
Directors(Managers) to Interview and Interviewers:
- John Harwood (TLT): Catherine & Audrey
- Lisa Lacomb (Training Services): Allan & Elizabeth
- Cole Camplese (ETS): Audrey & Catherine
- Mike Halm (Special Projects): Mary & Tara
- Dave Hollen (CLC): Frank & Allan
- Mary Ramsey: Frank & Elizabeth
Purpose of Director Surveys:
- Gather Info
- Audience: Current/Desired, Know-Feel-Do
- Content: Owners
- Identifying Initiatives
- Successful Sites
- Business Objectives (Internal Discovery)
Process:
- Interviews will be held face-to-face by one to two committee members
- Interviews will aim for 1 hour in length (15 min general, 45 min for interview)
- Ask for permission to record interviews
- Directors will be contacted and given general interview topics (ID audience, content owners, successful sites, web objectives)
- Directors will not be given exact interview questions as this will be more of a discussion environment
- Questions will be open and the interviewer should be sure to capture the reasoning behind answers by leading interviewer to explain.
- Can mention other interviewer answers to aid discussion
- Visual design will not be addressed at this point. This aspect will evolve and be tested as the design phase begins, being led by user data and designer recommendations.
- Don't overwhelm with too many extra questions.
Customizing the Interview Questions:
A book page will be created for committee members to edit and comment on. Consider the survey purposes. Consider what questions are critical. Edit into the language and organization-specific. Questions can be eliminated, generalized, and more in-depth questions added.
Initial Suggested User Interviews: Committee members Elizabeth Pyatt (ID-ETS) Barb Smith (ETS)
Meeting Notes for Feb 17, 2008
Discuss Process and Delegate Site Audit, Finalize Director Surveys
Attendees: Audrey, Allan, Catherine, Derick, Elizabeth, Mary, Tara
Goals:
- how do we accomplish getting current site data and analysis before the director interviews?
- i asked jason about google site map, but he has not responded with feedback
- we have awstats. how can we analyze this data to give us userful information
- we have the last report that came from the WebXM product scans. Only a small percentage of the data from WebXM was included in the report.
- complete editing down of survey questions
- complete assigning of interviewers and -ees
- schedule interviews (create an email notice)
- identify users for profiling
- assign interviewers for user profiling
- project planning (can anyone tackle some of this)
Next Tasks:
- Assign sections of the TLT site to committee for auditing (to be completed by Friday, February 22)
- Provide questions to be answered for the audit
- Complete director interview questions
- in addition to the audit, create a report of AWSTATS of the TLT site (Audrey & Elizabeth).
Background info: From "Communicating Design" by Dan M Brown "With an inventory, the intent is to capture and describe every piece of content on the site. A content audit captures and describes less, focusing perhaps on the main content areas of the site... An audit establishes a boundary around the scope of the investigation."
Meeting Notes for Feb 25, 2008
Complete Site Audit, Finalize and Schedule Director Surveys
Attendees: Audrey, Allan, Catherine, Elizabeth, Mary, Tara
Completed Tasks: Received site audit results from Audrey, Allan, Elizabeth, Catherine, Tara, Frank and Mary. Finalization of interview questions.
Results of the meeting: Discussion on what the site auditing has revealed about the committee's understanding of the current state of the TLT site architecture and content. Our focus at this point is on the architecture and audience, and not about visual design. We want to know what is working and what isn't, what the director's think about their unit's services and its representation on the TLT site with the audience in mind (not the organization structure). and especially, Why.
General Observations from the Site Audit:
- Many of the section pages are lists of links that take the user to a site (homepage) outside of TLT.
- The context of the sections are not clear. This creates doubt around the links that are listed and their relationship and usefulness.<//li>
- There are various site designs and content/navigation structures just within the TLT site itself, mostly in the Suggestions area. This is mainly due to the fact that a user may typically be entering this section of the site directly than through the TLT homepage. The suggestions area also seems to be the largest content area on the TLT site.
- The TLT header text does is not a link taking back to the homepage of TLT
- Breadcrumbs are sometimes present, and sometimes functional, but are typically only present 1-2 pages in. The deeper you get into the site, the less likely or helpful the breadcrumbs are.
- There are definitely services, as well as staff intranet, that have no representation on the TLT site, at least from the homepage.
- Ownership of the pages and sections is difficult to assess given that a few of us are not as familiar with the TLT site or the organization's structure and purpose behind the web presence.
- We would like to enable links to services outside of TLT to provide the best usefulness for the users. Unit and Organization structure are not necessarily the best way to organize the architecture if that isn't how the users get to the content.
- We can look to the site stats report to see which parts of the site users are mostly accessing and keywords they use when searching to find the content. If they actually find what they are looking for is one aspect that we can not know. This might be something we can add to pages in the new CMS to harvest this data.
Next Tasks:
- Contact committee members not in attendance to confirm resources and participation.
- Schedule director interviews to complete by March 10, 2008. Don't wait on the site audit for the director interviews.
- Make sure you have access or make arrangements to equip yourselves with audio recorders for the interviews and to ask permission to record.
- Create Basecamp project and provide access for members to have a document sharing space, task lists, milestones and enable consolidated communication/assignments tracking
- Reassign any outstanding site sections to members for auditing
- Complete site audit in digital form and share.
- Complete current site architecture in digital form and share
- Each member should study the list of questions for interviews and consider how they will conduct the interviews to enable a discussion rather than a Q&A. Advise to think over what your answers might be.
Interviewee and Interviewer Assignments:
- John Harwood (TLT): Catherine & Audrey (contact Deb Dixon to schedule)
- Lisa Lacomb (Training Services): Allan & Elizabeth (contact ? to schedule)
- Cole Camplese (ETS): Audrey & Catherine (contact Jane Houlihan to schedule)
- Mike Halm (Special Projects): Mary & Tara (contact Rebecca McCloskey to schedule)
- Dave Hollen (CLC): Frank & Allan (contact Hope to schedule)
- Mary Ramsey: Frank & Elizabeth (contact directly to schedule)
Meeting Notes for March 31, 2008
Attendees: Audrey, Allan, Catherine, Elizabeth, Erik, Derick, Mary, Tara
We succeeded in getting 11 volunteers for the card-sorting session from the TLT Symposium signup/flyer.
We conducted 2 card-sorting sessions among our team.
- Group 1: Mary, Tara, Derick, Audrey
- Group 2: Allan, Elizabeth, Erik, Catherine
Discussed what is needed for conducting the session with faculty/staff/students signups from the Symposium:
- Schedule dates and rooms for next week on everyone's schedule.
- For the off-UP campus signups, they should be sent the cards file to print and cut out. A video conferencing call should be arranged to simulate the same experience.
- Create an introduction (it is like concept mapping, but prompted)
- Generate a script.
- Prompts (little/big)
- Create a pre-questionnaire.
- Create a take away sheet with references and URLs.
- Get different color index cards for categories.
What the users role is in the card-sorting session:
- Working in pairs
- Thinking out loud
What our role is in the card-sorting session:
- Ask questions about background, teaching, use of the web, web use environment, bookmarks
- Audio recording
- Take a photo during and at the end of sorting process.
Prompts:
- You can change the names of cards or eliminate cards
- You can use sentences to explain instead of names (Ask them how they would describe it)
- Start with what you know
- What are the key selling points that would make you choose that service?
- If a user asks "I don't know what this card is", tell them to put it into a pile to address later
- If a user has an enormous category, ask "How would you further break it down?" "What is the meaning of all these things" "Are there other groupings that might emerge from this?"
- If a user isn't sure if a card should go in one pile or another, prompt to make multiple cards and put them in both.
- Why did you put things in this pile and why is it different from another pile?
Sites to conduct in:
- 202K Rider
- 315 Rider
- Irvings
- Panera (reserve back room)
- Willard conference room
- Weblion conference room
- 510 Miller Lab
Focus on UP signups for first run:
- 11am to noon
Meeting Notes for April 07, 2008
Attendees: Audrey, Catherine, Mary, Tara, Erik
- Announce Dates - who can attend, what role (prompter, observer, food)
- Review Cards
- Review Hand Out
- Review Script
- More participants
- 4/7 - Audrey, Tara, Mary, Erik
- 4/9 - Audrey, Mary, Elizabeth
- 4/11 - Audrey, Catherine, (Mary)
- 4/23 - Audrey, ...
Meeting Notes for April 21, 2008
Drafting Architecture, Navigation and Wireframes
Attendees: Audrey, Catherine, Mary, Frank
Goals for this meeting:
- Report on results of new card sorting sessions
- Begin conceptualizing draft pages and architecture pathways
Results of the meeting:
- Assigned Audrey to draft possible page structure for "low hanging fruit areas" (services).
- Get meeting frequency and length rescheduled to allow for more "working" sessions
Next meeting:
- Audrey will meet with several service managers to get their feedback on the draft wireframe
- Elizabeth will bring a list of faculty tasks
Meeting Notes for April 28, 2008
Drafting Architecture, Navigation and Wireframes
Attendees: Audrey, Frank, Catherine, Mary, Elizabeth, Derick
Goals for this meeting:
- Report the feedback from Blogs, Podcasts, and Digital Commons managers on the wireframes
- Discuss the wireframe, what works, what doesn't
- See what faculty tasks Elizabeth put together and use that to create a draft "gallery" page
Results of the meeting:
- Assigned people to draft possible page structure for "low hanging fruit areas" (services/content topics).
- A very draft "gallery" page was mocked up from the faculty tasks perspective
- Revised service-specific draft wireframe
Assignments:
- ANGEL (Mary)
- Digital Commons (Audrey)
- Blogs (Audrey)
- Podcasts (Audrey)
- Video Conferencing (Derick)
- Copyright and Plagiarism (Elizabeth)
- Classroom Technology (Frank)
- Educational Gaming (Elizabeth)
Next meeting:
- Review drafts and identify the common themes and differences.
- Assess what extent the redesign will cover * what is doable by the due date * what needs to be retained on the TLT site vs what exists on an outside site.
- Plan usability testing (paper-prototyping)
Meeting Notes for May 12, 2008
Attendees: Audrey, Allan, Elizabeth, Erik, Catherine
meeting goals:
- Review drafts and identify the common themes and differences.
- Assess what extent the redesign will cover - what is doable by the due date - what needs to be retained on the TLT site vs what exists on an outside site.
- Plan usability testing (paper-prototyping)
next goals:
- recruit 3-4 faculty
- create a design brief
paper-prototyping
- 3 team members to one faculty. 1 faculty test at a time.
- 1st approach: pre-discussion (interest)
- 2nd approach: specific task
- half hour length
- held at wherever
- show examples of sites (weblion, educause site, apple)
to do:
- audrey + allan work on design brief, committee reviews
- make a list of faculty candidates for paper-prototyping
- audrey draws up paper-prototypes
- next meeting have a dry run with committee members
- following week conduct faculty testing (small snack bribe)
- catherine and audrey start building in plone
Meeting Notes for June 2, 2008
Attendees: Tara, Derick, Elizabeth, Catherine, Audrey, Erik
Tasks to accomplish:
- Review paper-prototypes
- Decide on alternate home page design layout elements
Paper-Prototyping Session details:
- 3-4 faculty (late to middle adopters), outside TLT circles
- 4 tasks (2 per design)
- Food (if we do a snack like doughnuts we can have more than one session per day)
- Session time: ~45min
Next tasks:
- Finish edits on paper-prototypes
- Create paper-prototype page for an information-springboard page vs service-springboard (e.g. copyright and plagiarism)
- Recruit 3-4 faculty (late to middle adopters)
- Define paper-prototyping tasks (4) in Basecamp
- Set dates for sessions
Meeting Notes for June 16, 2008
Attendees: Audrey, Catherine, Mary
Meeting tasks:
- Define paper-prototyping tasks (4)
- Review paper-prototypes and make edits
- Volunteers for the sessions
- Recruitment (Catherine will ask faculty she knows)
Meeting Notes for June 30, 2008
Attendees: Audrey, Catherine, Frank, Mary, Tara
Tasks:
- Brief results of paper-prototyping (more specific task-based section, shorten links list, rethink some springboard info)
- Nail down gallery links container
- Revisioning info on springboard pages, Assign pages that haven't been addressed
- Meeting with Cole tomorrow to talk about Feature section and tasks relating to technology and pedagogy
Next Tasks:
- Work on navigation in a writeboard (incl links)
- Add "Quick start" list for each service (look thru the sites, contact project managers)
- Start prototyping in Plone (meet with Rob/Catherine)
