Qualitative user research was conducted in January-March of 2018 to better understand how community members experience IT at Stanford. The findings from this research are intended to inform strategic planning and service improvement projects.
This report contains qualitative findings from user research conducted January–March of 2018 by the University IT Service Design team as part of the inaugural Campus IT Plan program.
The findings from this research are intended to inform future strategic planning and service improvement projects by technical and business owners of IT systems across Stanford. The objective of this qualitative research was to understand how various audiences experience IT at Stanford. Specific goals were to:
Learn how key technology services, tools, and systems are experienced
Learn what’s working well and what can be improved
Understand how each audience obtains IT support and what their experience is when they receive it
Identify gaps in IT provided by Stanford
Identify future IT needs
Qualitative research is primarily exploratory and used to gain understanding of underlying reasons, opinions, and motivations. It helps us develop understanding of a problem space, build empathy with users, and collect evidence to expose potential patterns. Where quantitative research uses larger datasets to generalize results representing a larger population, qualitative research focuses on going deeper with a smaller sample size to uncover meaningful human stories to use as provocations for new designs, service improvements, and innovations.
Quantitative data can often answer “What? When? Where? How many?” while qualitative data focuses mainly on “Why? How?”. For this reason, qualitative data should be verified with quantitative data if the purpose is to extrapolate out broader trends in a population, and quantitative data can benefit from qualitative data for deeper understanding of how the data points connect and why.
When reading the findings in this report, please keep in mind that we are reporting on what we heard from the participants in the study and that the sample sizes and breakdown of audiences who participated should be understood in order to effectively interpret the findings (these are listed below). Through these reports, we are communicating the rich human narratives that can help build empathy and understanding with our community.
This report captures what we believe to be useful insights, not necessarily statistically significant findings. We hope these findings may be useful in understanding the people in our community and capture unique perspectives that may deepen our understanding of various problem spaces that IT services address.
The Executive Research Report (below) summarizes key findings from the research. Additional detailed findings by topic area are available below. Full participant breakdown and research protocol are documented in the Appendix as a separate document on this page.
These insights are not an end in themselves but meant to be provocations to lead to further discovery, ideation, and design work.
Some of the findings in this report may be specific and tactical feedback related to a particular service. Others might be more general or strategic.
When reading the findings, consider the following:
What are the implications of these findings to my service, area, or organization?
Where could we benefit from additional, deeper research (either qualitative or quantitative) to better understand context or validate these findings with a larger population?
How might we use these findings to inspire creative thinking and innovation in our team or organization?
You can provide feedback or ask follow-up questions to the Service Design team directly at servicedesignteam@lists.stanford.edu. If you are interested in having a member of the team come to present findings to your group or lead your team through an ideation workshop related to relevant findings, please reach out to discuss with us. We would be happy to partner with your group to conduct further secondary research, facilitate ideation workshops, or partner on design improvement projects coming out of this work.
Below are a sample of the questions used when interviewing research participants. All participants were prompted with a similar set of questions. The below questions were used for graduate students and postdocs.
To learn more about the research protocols, please refer to the Appendix.
Read the executive summary of findings, including general insights that cross all categories, summaries of topic area findings, and key audiences insights (undergraduate, graduate, staff, and faculty).
The following reports highlight detailed findings in ten topic areas that reflect significant feedback gathered from participants during the user research. Review the summary of contents below to discover which reports may be of interest to your group(s).
Length: 14 pages
Contents:
Length: 41 pages
Contents:
Length: 44 pages
Contents:
Length: 55 pages
Contents:
Length: 17 pages
Contents:
Length: 42 pages
Contents:
Length: 13 pages
Contents:
Length: 7 pages
Contents:
Length: 9 pages
Contents:
Length: 41 pages
Contents:
Download four "persona" posters for undergraduate students, graduate students (and TAs), researchers (faculty, grad, and postdoc), and staff. Posters are 11"x17" and meant to create quick, scannable views of audiences highlights based on role/affiliation.
View a full participant breakdown by organization and role, and all research protocols (including interview approach, outreach tactics, interview scripts, and handouts).
If you have questions, concerns, or feedback regarding the findings presented in the above reports, please contact the Service Design team at servicedesignteam@lists.stanford.edu