SlideShare a Scribd company logo
1 of 20
Usability Testing

           Solution Overview and Testing
                     Roadmap



3/6/2012            Copyrights 2012, Cadence9   1
Administration
• Introductions and backgrounders
• Robert Half
      – log time, etc.
• Cadence9
      – estimate 8 hours per week
      – 1 orientation (today)
      – 3 weeks in duration
      – debriefing meetings (here, Friday, time TBD )

3/6/2012                 Copyrights 2012, Cadence9      2
Participant Experience
 • have your own computer with internet
   access
 • familiar with social media destinations
 • using Google Docs to access needed
   documentation




3/6/2012           Copyrights 2012, Cadence9   3
Agenda
•   what is Cadence9?
•   demonstration
•   usability testing process
•   getting started
•   Q&A




3/6/2012             Copyrights 2012, Cadence9   4
What is Cadence9?
 • hosted web-based content marketing and
   social media platform
 • build for marketing teams
 • manage, publish, engage and measure from
   one place
 • supports all major social media channels
 • integrates with custom or proprietary
   channels

3/6/2012          Copyrights 2012, Cadence9   5
Demonstration
• solution tour
• key items
      – user roles
      – channels
      – templates
      – tasks
      – publishing events
           • Primary Channels (see content topics doc)
      – engagements

3/6/2012                     Copyrights 2012, Cadence9   6
Testing
• goal
      – usability feedback based on 3 roles
• teams
      – 2 teams of 4 people
      – 3 roles
      – role change each week
• activities
      – intensive lifecycle modeling

3/6/2012                 Copyrights 2012, Cadence9   7
Process Overview
• 1st week example
    Person     Admin   Author   Engager   Comments
     Jeremy      X
     Yvonne              X
   Emmanuel                       X
       David             X
        Abe      X
       Tony              X
      Albert                      X
      Martin             X
Process Overview (Continued)
• admin setup users, channels, templates, and
  then removes (at start of next test period)
• content ideas are supplied
  – various types, media, template, timing, routings,
    role
• admin and authors publish create/author
  content
• engagers … monitor and reply to engagement
  – C9 team members will be “engagees”
Admin Role
• setup temporary users, channels and
  templates
• create publishing tasks in editorial calendar
  – for Tue, Wed and Thu create 10/day for authors
    and admin
• everyone publish your own items (5/day)
• monitor assignments and publish
  – approve / reroute events written by authors
  – routing suggestions
Authors
• author 10 pieces per day and route
  – based on task assignments from admin
• monitor task assignments
  – watch for task assignment in email
  – can come from either manager or other author
  – complete task and route to author or manager
Engagers
• monitor engagement activity
  – from engagees
• reply and act with in Cadence9
All Team Members
• review applicable reports for accuracy
• complete online survey form at end of each
  day for your role
• use Feedback option to report bugs/issues
• watch for daily emails from the C9 team
• call Mike for any help … 714 904 6352
• be critical!

3/6/2012          Copyrights 2012, Cadence9    13
Friday’s Debriefing
•   review survey input
•   review any Feedback submittals
•   update process documentation as required
•   other comments and feedback
•   prepare for following week
Content
• topic “prompter” approach
  – experiences based on your car
  – e.g. “what’s the gas mileage?”
• responses
  – ranging from less than 140 characters to 100
    words
  – have FUN!
• use content guide (online)
  – types, media, template, timing, routings, role
  – media library provided
Content Types and Media
•   status updates
•   blog text
•   curation
•   files
•   PPTs
•   images
•   video
•   … what else?
Getting Started
 • test site
       – qa.amplephi.com
       – user name - email account
       – password -
       – look for daily notes
 • Google Docs
       – user name - c9testgroup@gmail.com
       – password - c9Testing


3/6/2012                Copyrights 2012, Cadence9   17
Available at Google Docs
 • C9 Solution Overview for Testing Teams (PPT)
 • Test Participants Rooster (needed by Admins)
 • Destination access information (needed by
   Admins)
 • Template descriptions (needed by Admins)
 • Admin, author and engager role
   documentation
 • Content topics

3/6/2012           Copyrights 2012, Cadence9      18
Other Notes
• if you see the word “Amplephi” ... ignore
• Feedback comments (top right in application)
      – goes to several people
      – Ken will respond if issue
      – will be addressed at debriefing




3/6/2012                 Copyrights 2012, Cadence9   19
Q&A
• questions, comments
• call or contact immediate help
      – Mike
      – 714 904 6352
      – michael@vdr.com




3/6/2012              Copyrights 2012, Cadence9   20

More Related Content

Similar to How does your _____ car handle in the rain?

Implimenting and Mitigating Change with all of this Newfangled Technology
Implimenting and Mitigating Change with all of this Newfangled TechnologyImplimenting and Mitigating Change with all of this Newfangled Technology
Implimenting and Mitigating Change with all of this Newfangled TechnologyIndiana Online Users Group
 
Communicating Design
Communicating DesignCommunicating Design
Communicating Design悠識學院
 
Design Studio Methodology: A quick why and how
Design Studio Methodology: A quick why and howDesign Studio Methodology: A quick why and how
Design Studio Methodology: A quick why and howDaniel Naumann
 
Contribution in the Drupal community
Contribution in the Drupal communityContribution in the Drupal community
Contribution in the Drupal communityKálmán Hosszu
 
Introduction To Agile Refresh Savannah July20 2010 V1 4
Introduction To Agile Refresh Savannah July20 2010 V1 4Introduction To Agile Refresh Savannah July20 2010 V1 4
Introduction To Agile Refresh Savannah July20 2010 V1 4Marvin Heery
 
Engineering Design Process
Engineering Design ProcessEngineering Design Process
Engineering Design ProcessM.T.H Group
 
Prototyping - the what, why and how at the University of Edinburgh
Prototyping - the what, why and how at the University of EdinburghPrototyping - the what, why and how at the University of Edinburgh
Prototyping - the what, why and how at the University of EdinburghNeil Allison
 
Agile Methods - An Overview - Marc Bless - 2009
Agile Methods - An Overview - Marc Bless - 2009Agile Methods - An Overview - Marc Bless - 2009
Agile Methods - An Overview - Marc Bless - 2009Marc Bless
 
From Project Manager to Scrum Master
From Project Manager to Scrum MasterFrom Project Manager to Scrum Master
From Project Manager to Scrum MasterLitheSpeed
 
Learning from Learnings: Anatomy of Three Incidents
Learning from Learnings: Anatomy of Three IncidentsLearning from Learnings: Anatomy of Three Incidents
Learning from Learnings: Anatomy of Three IncidentsRandy Shoup
 
Reliability Maintenance Engineering 2 - 4 Purpose and Equipment
Reliability Maintenance Engineering 2 - 4 Purpose and EquipmentReliability Maintenance Engineering 2 - 4 Purpose and Equipment
Reliability Maintenance Engineering 2 - 4 Purpose and EquipmentAccendo Reliability
 
Agile 2008 Retrospective
Agile 2008 RetrospectiveAgile 2008 Retrospective
Agile 2008 RetrospectiveCraig Smith
 
Ux and strategy design
Ux and strategy designUx and strategy design
Ux and strategy designLMarine
 
Csun presentation 2015 final v2
Csun presentation 2015 final v2Csun presentation 2015 final v2
Csun presentation 2015 final v2LizNWEA
 
Intro to Scrum - Heidi Araya
Intro to Scrum  - Heidi ArayaIntro to Scrum  - Heidi Araya
Intro to Scrum - Heidi Arayaagilemaine
 
2012 bad camp-project management tools and organization-v4
2012 bad camp-project management tools and organization-v42012 bad camp-project management tools and organization-v4
2012 bad camp-project management tools and organization-v4Andy Kucharski
 

Similar to How does your _____ car handle in the rain? (20)

Implimenting and Mitigating Change with all of this Newfangled Technology
Implimenting and Mitigating Change with all of this Newfangled TechnologyImplimenting and Mitigating Change with all of this Newfangled Technology
Implimenting and Mitigating Change with all of this Newfangled Technology
 
Communicating Design
Communicating DesignCommunicating Design
Communicating Design
 
Design Studio Methodology: A quick why and how
Design Studio Methodology: A quick why and howDesign Studio Methodology: A quick why and how
Design Studio Methodology: A quick why and how
 
Contribution in the Drupal community
Contribution in the Drupal communityContribution in the Drupal community
Contribution in the Drupal community
 
Introduction To Agile Refresh Savannah July20 2010 V1 4
Introduction To Agile Refresh Savannah July20 2010 V1 4Introduction To Agile Refresh Savannah July20 2010 V1 4
Introduction To Agile Refresh Savannah July20 2010 V1 4
 
Engineering Design Process
Engineering Design ProcessEngineering Design Process
Engineering Design Process
 
Prototyping - the what, why and how at the University of Edinburgh
Prototyping - the what, why and how at the University of EdinburghPrototyping - the what, why and how at the University of Edinburgh
Prototyping - the what, why and how at the University of Edinburgh
 
Agile Methods - An Overview - Marc Bless - 2009
Agile Methods - An Overview - Marc Bless - 2009Agile Methods - An Overview - Marc Bless - 2009
Agile Methods - An Overview - Marc Bless - 2009
 
From Project Manager to Scrum Master
From Project Manager to Scrum MasterFrom Project Manager to Scrum Master
From Project Manager to Scrum Master
 
1-intro.ppt
1-intro.ppt1-intro.ppt
1-intro.ppt
 
1-intro.ppt
1-intro.ppt1-intro.ppt
1-intro.ppt
 
Afganistan Culture Shock
Afganistan Culture ShockAfganistan Culture Shock
Afganistan Culture Shock
 
Learning from Learnings: Anatomy of Three Incidents
Learning from Learnings: Anatomy of Three IncidentsLearning from Learnings: Anatomy of Three Incidents
Learning from Learnings: Anatomy of Three Incidents
 
Scrum intro
Scrum intro Scrum intro
Scrum intro
 
Reliability Maintenance Engineering 2 - 4 Purpose and Equipment
Reliability Maintenance Engineering 2 - 4 Purpose and EquipmentReliability Maintenance Engineering 2 - 4 Purpose and Equipment
Reliability Maintenance Engineering 2 - 4 Purpose and Equipment
 
Agile 2008 Retrospective
Agile 2008 RetrospectiveAgile 2008 Retrospective
Agile 2008 Retrospective
 
Ux and strategy design
Ux and strategy designUx and strategy design
Ux and strategy design
 
Csun presentation 2015 final v2
Csun presentation 2015 final v2Csun presentation 2015 final v2
Csun presentation 2015 final v2
 
Intro to Scrum - Heidi Araya
Intro to Scrum  - Heidi ArayaIntro to Scrum  - Heidi Araya
Intro to Scrum - Heidi Araya
 
2012 bad camp-project management tools and organization-v4
2012 bad camp-project management tools and organization-v42012 bad camp-project management tools and organization-v4
2012 bad camp-project management tools and organization-v4
 

How does your _____ car handle in the rain?

  • 1. Usability Testing Solution Overview and Testing Roadmap 3/6/2012 Copyrights 2012, Cadence9 1
  • 2. Administration • Introductions and backgrounders • Robert Half – log time, etc. • Cadence9 – estimate 8 hours per week – 1 orientation (today) – 3 weeks in duration – debriefing meetings (here, Friday, time TBD ) 3/6/2012 Copyrights 2012, Cadence9 2
  • 3. Participant Experience • have your own computer with internet access • familiar with social media destinations • using Google Docs to access needed documentation 3/6/2012 Copyrights 2012, Cadence9 3
  • 4. Agenda • what is Cadence9? • demonstration • usability testing process • getting started • Q&A 3/6/2012 Copyrights 2012, Cadence9 4
  • 5. What is Cadence9? • hosted web-based content marketing and social media platform • build for marketing teams • manage, publish, engage and measure from one place • supports all major social media channels • integrates with custom or proprietary channels 3/6/2012 Copyrights 2012, Cadence9 5
  • 6. Demonstration • solution tour • key items – user roles – channels – templates – tasks – publishing events • Primary Channels (see content topics doc) – engagements 3/6/2012 Copyrights 2012, Cadence9 6
  • 7. Testing • goal – usability feedback based on 3 roles • teams – 2 teams of 4 people – 3 roles – role change each week • activities – intensive lifecycle modeling 3/6/2012 Copyrights 2012, Cadence9 7
  • 8. Process Overview • 1st week example Person Admin Author Engager Comments Jeremy X Yvonne X Emmanuel X David X Abe X Tony X Albert X Martin X
  • 9. Process Overview (Continued) • admin setup users, channels, templates, and then removes (at start of next test period) • content ideas are supplied – various types, media, template, timing, routings, role • admin and authors publish create/author content • engagers … monitor and reply to engagement – C9 team members will be “engagees”
  • 10. Admin Role • setup temporary users, channels and templates • create publishing tasks in editorial calendar – for Tue, Wed and Thu create 10/day for authors and admin • everyone publish your own items (5/day) • monitor assignments and publish – approve / reroute events written by authors – routing suggestions
  • 11. Authors • author 10 pieces per day and route – based on task assignments from admin • monitor task assignments – watch for task assignment in email – can come from either manager or other author – complete task and route to author or manager
  • 12. Engagers • monitor engagement activity – from engagees • reply and act with in Cadence9
  • 13. All Team Members • review applicable reports for accuracy • complete online survey form at end of each day for your role • use Feedback option to report bugs/issues • watch for daily emails from the C9 team • call Mike for any help … 714 904 6352 • be critical! 3/6/2012 Copyrights 2012, Cadence9 13
  • 14. Friday’s Debriefing • review survey input • review any Feedback submittals • update process documentation as required • other comments and feedback • prepare for following week
  • 15. Content • topic “prompter” approach – experiences based on your car – e.g. “what’s the gas mileage?” • responses – ranging from less than 140 characters to 100 words – have FUN! • use content guide (online) – types, media, template, timing, routings, role – media library provided
  • 16. Content Types and Media • status updates • blog text • curation • files • PPTs • images • video • … what else?
  • 17. Getting Started • test site – qa.amplephi.com – user name - email account – password - – look for daily notes • Google Docs – user name - c9testgroup@gmail.com – password - c9Testing 3/6/2012 Copyrights 2012, Cadence9 17
  • 18. Available at Google Docs • C9 Solution Overview for Testing Teams (PPT) • Test Participants Rooster (needed by Admins) • Destination access information (needed by Admins) • Template descriptions (needed by Admins) • Admin, author and engager role documentation • Content topics 3/6/2012 Copyrights 2012, Cadence9 18
  • 19. Other Notes • if you see the word “Amplephi” ... ignore • Feedback comments (top right in application) – goes to several people – Ken will respond if issue – will be addressed at debriefing 3/6/2012 Copyrights 2012, Cadence9 19
  • 20. Q&A • questions, comments • call or contact immediate help – Mike – 714 904 6352 – michael@vdr.com 3/6/2012 Copyrights 2012, Cadence9 20

Editor's Notes

  1. reach out to family, friend, employees, etc to engagemturks to engage