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.
Research Goals
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
What is qualitative vs. quantitative research?
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.
How to interpret this report
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.
Report structure
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.
How you might use this report
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?
How to provide feedback, ask questions, or request further discovery
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.
Sample interview questions
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.
- What comes to mind when you think about Information Technology at Stanford?
- What core technologies, systems, or apps do you use most regularly here at Stanford to support you as a grad student / postdoc?
- Thinking about your typical quarter, what are your biggest pain points associated with technology, and how technology supports you as a grad student/postdoc? What works really well?
- Where do you go when you want or need to figure out how to achieve something with technology at Stanford?
- How do you get support for technology issues, and what are your pain points about getting IT support? (tell me about a recent experience)
- Are there any gaps in what Stanford offers as central or departmental technology services/support, that you feel you have to seek from outside the university? If so, what are those gaps?
- What are three things that technology could do better to support you as a grad student/postdoc?
- What is a technology (here at Stanford or outside of Stanford) that you are really excited about, and would be excited to have more access to?
- What technology do you think will be important to your studies/work in the next 3-5 years?
To learn more about the research protocols, please refer to the Appendix.
