Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width65%

Fluid Course Administration & Content Management Personas

Overview

The Fluid Course Administration & Content Management Personas are models used to represent the information gathered during the user research done in the Fluid Content Management Research project. They are models of archetypical users in this domain, and are used to inform the design and development process of Fluid Components. Some of these personas are provisional, which means they were not based directly on this user research, but represent user types we know from previous research are important and should be represented. 

These personas will also be useful to communities working on projects in the Course Administration & Content Management domain. We anticipate the need to add additional information to these personas for more focused domains (e.g. Collections Management). 

Column
width35%

Types of Personas

The design of all Fluid Components will be informed directly by the Primary & Secondary personas below. By definition, each primary persona requires their own user interface in a particular application. A secondary persona is one whose needs will be mostly served if the needs of the primary persona is met. There may be small additions to the interface necessary to meet the needs of a secondary persona, but these additions should not negatively affect the experience of the primary persona. (If this were the case, this secondary persona should be another primary persona and have their own interface.)

Auxiliary personas do represent models of users we saw in the field, but we don't believe are different enough from the primary and secondary personas that it is helpful to keep them in mind. However, we are making them available so that they can be used in a particular problem space as necessary. For example, Michael Demsky, the Departmental Support Person, is not that different from Anita Stalmach, who does Departmental Pedagogy Support. However, if there was a use case that involved this person doing a lot of section management, it may be more helpful to use Michael.

Additional personas may also be created based as additional user research is done (or as provisional personas if user research is not an option). This may prove necessary if we realize we don't have enough information on users in a particular problem space. For example, if we are working on a reorderer component in a context/problem space where reordering large collections of images is the primary use case, we may want to have a professor in a media-heavy discipline, such as Art History or Architecture, as a primary persona to inform our design & development process. 

Anchor
primary
primary

Primary Personas

Section
Column
width33%

Catalina De Silva (Faculty - GSI Manager in Spanish)

Excerpt Include
fluid:Catalina De Silva (Faculty - GSI Manager in Spanish)
fluid:Catalina De Silva (Faculty - GSI Manager in Spanish)
nopaneltrue
Column
width33%

Christy Gonzola (Undergraduate Student - Molecular & Cell Biology)

Excerpt Include
fluid:Christy Gonzola (Undergraduate Student - Molecular & Cell Biology)
fluid:Christy Gonzola (Undergraduate Student - Molecular & Cell Biology)
nopaneltrue
Column
width33%

Ashley Myles (Undergraduate Student - Archeology)

Excerpt Include
fluid:Ashley Myles (Undergraduate Student - Archeology)
fluid:Ashley Myles (Undergraduate Student - Archeology)
nopaneltrue

Anchor
secondary
secondary

Secondary Personas

Section
Column
width33%

Stacey Pearson (Graduate Teaching Assistant - Microbiology)

Excerpt Include
fluid:Stacey Pearson (Graduate Teaching Assistant - Microbiology)
fluid:Stacey Pearson (Graduate Teaching Assistant - Microbiology)
nopaneltrue
Column
width33%

Anita Stalmach (Departmental Pedagogy Support - Instructional Designer)

Excerpt Include
fluid:Anita Stalmach (Departmental Pedagogy Support - Instructional Designer)
fluid:Anita Stalmach (Departmental Pedagogy Support - Instructional Designer)
nopaneltrue
Column
width33%

Andy Wright (Graduate Student - Information Studies)

Excerpt Include
fluid:Andy Wright (Graduate Student - Information Studies)
fluid:Andy Wright (Graduate Student - Information Studies)
nopaneltrue

New Provisional student persona - over-acheiver who takes a lot of online classes

Excerpt Include
nopaneltrue
Column
width33%

Anchor
auxiliary
auxiliary

Auxiliary Personas

Section
Column
width33%

Robin McCoy (Faculty - Business School)

Excerpt Include
fluid:Robin McCoy (Faculty - Business School)
fluid:Robin McCoy (Faculty - Business School)
nopaneltrue
Column
width33%

George McFadden (Online Instructor - Journalism)

Excerpt Include
fluid:George McFadden (Online Instructor - Journalism)
fluid:George McFadden (Online Instructor - Journalism)
nopaneltrue
Column
width33%

Ahmad Yousef (Faculty - Tenure-track History)

Excerpt Include
fluid:Ahmad Yousef (Faculty - Tenure-track History)
fluid:Ahmad Yousef (Faculty - Tenure-track History)
nopaneltrue
Section
Column
width33%

Sergio Rossi (Graduate Teaching Assistant - Urban Affairs & Planning)

Excerpt Include
fluid:Sergio Rossi (Graduate Teaching Assistant - Urban Affairs & Planning)
fluid:Sergio Rossi (Graduate Teaching Assistant - Urban Affairs & Planning)
nopaneltrue
Column
width33%

Henry Sibley (Longtime Faculty - Chemistry, Provisional Persona)

Excerpt Include
fluid:Henry Sibley (Longtime Faculty - Chemistry, Provisional Persona)
fluid:Henry Sibley (Longtime Faculty - Chemistry, Provisional Persona)
nopaneltrue
Column
width33%

Shaina Wiseman (Graduate Student - Land Development, Provisional Persona)

Excerpt Include
fluid:Shaina Wiseman (Graduate Student - Land Development, Provisional Persona)
fluid:Shaina Wiseman (Graduate Student - Land Development, Provisional Persona)
nopaneltrue
Section

Michael Demsky (Departmental Support - Biology)

Excerpt Include
fluid:Michael Demsky (Departmental Support - Biology)
fluid:Michael Demsky (Departmental Support - Biology)
nopaneltrue
Column
width35%

Types of Personas

The design of all Fluid Components will be informed directly by the Primary & Secondary personas below. By definition, each primary persona requires their own user interface in a particular application. A secondary persona is one whose needs will be mostly served if the needs of the primary persona is met. There may be small additions to the interface necessary to meet the needs of a secondary persona, but these additions should not negatively affect the experience of the primary persona. (If this were the case, this secondary persona should be another primary persona and have their own interface.)

Auxiliary personas do represent models of users we saw in the field, but we don't believe are different enough from the primary and secondary personas that it is helpful to keep them in mind. However, we are making them available so that they can be used in a particular problem space as necessary. For example, Michael Demsky, the Departmental Support Person, is not that different from Anita Stalmach, who does Departmental Pedagogy Support. However, if there was a use case that involved this person doing a lot of section management, it may be more helpful to use Michael.

Additional personas may also be created based as additional user research is done (or as provisional personas if user research is not an option). This may prove necessary if we realize we don't have enough information on users in a particular problem space. For example, if we are working on a reorderer component in a context/problem space where reordering large collections of images is the primary use case, we may want to have a professor in a media-heavy discipline, such as Art History or Architecture, as a primary persona to inform our design & development process.