Using a survey to understand digital design tool usage across the University (as part of the Figma design component library project)
This year, as part of the Figma component library project, we researched how colleagues across the University use digital design tools in their work. This post explores how we approached the research, from designing and distributing the survey through to analysing the responses and identifying emerging themes.
In a previous blog post, intern Kaile Liu introduced the wider Figma project, and its aims and objectives:
What I am working on as a Digital Developer Intern (Figma)
Request access to the project brief for more details:
We needed to understand how digital design work happens across the University
To begin with, we needed to understand how staff across the University design, collaborate and deliver digital work.
There are a wide range of tools, workflows and practices currently in use. Understanding these existing ways of working would help us explore where Figma fits within the wider digital landscape, rather than looking at Figma in isolation. It also supports the work we are doing to improve our Figma component design library.
To hear from colleagues across a wide range of roles and disciplines, we chose a survey as the main method for this research.
Five questions framed our research
As well as understanding what tools people use, we wanted to find out how those tools support their work and where there may be opportunities to improve existing ways of working.
Our research was underpinned by five key questions:
- What tools are people using day-to-day?
- How do those tools support their work?
- Where do people experience challenges or inefficiencies?
- How do teams collaborate when creating digital content and services?
- Where are there opportunities to provide better support, guidance and training?
These questions helped us build a broader picture of digital working practices across the University. Additionally, working this way allowed us to look beyond any individual or singular tool.
Hearing from more than just traditional design roles was important
Design work happens across many different roles at the University, including roles not traditionally associated with design or that do not have ‘design’ in the job title. For example, a communications officer creating digital content, a developer sketching a wireframe, a UX practitioner co-creating a prototype or a learning technologist building online resources may all be making design decisions as part of their work.
This meant looking beyond traditional design roles and hearing from colleagues who use digital design tools in different ways.
Initial conversations helped us shape the research
Before designing the survey, we carried out an initial set of user interviews with staff from across the University. We also drew on existing University communities and communities of practice to understand the different roles involved in digital design work. These conversations gave us an early view of how colleagues use and collaborate through digital tools. They helped us identify the groups we wanted to hear from and shape the questions we wanted to ask in the survey.
Adapting our survey to broaden our understanding of ways of working
Based on these interviews, we recognised that a single set of questions would not capture the differences between roles particularly well. Instead, we adapted the survey so that respondents would answer shared questions and then be filtered to questions relevant to their role and ways of working.
This, in essence, would give us a more consistent set of responses while still allowing us to explore some of the differences between roles.
Role categories allowed us to tailor the survey
We created a filter with seven options:
- Marketing and Communications
- UX and Human-centred Design
- Graphic and UI Design
- Developer
- Project or product manager
- Research
- Other (for participants who did not feel represented by the other groups)
Participants selected the options that best reflected their work, determining which role-specific questions they were shown. They also provided their job title.
The survey combined common and role-specific questions
The survey consisted of three main sections. The questions included a mixture of multiple-choice and open-ended responses. This allowed us to identify broader patterns while also giving colleagues opportunities to explain their experiences in more detail.
The opening section included five common questions about participants’ roles, the types of digital design work they do and the tools they use, including tools for collaboration, diagramming and presentations.
The middle section included around four to six role-specific questions, depending on the participant’s selected group. These explored aspects of digital working relevant to each group. For example, marketing and communications colleagues were asked about the tools they use when designing marketing materials, while developers were asked about the tools and approaches they use during the design phase of projects.
The closing section included 15 common questions focused on colleagues’ experiences and expectations of digital design tools, including Figma. We asked which tools colleagues would be likely to use, whether they experienced challenges with their current tools and how their work might be affected if they lost access to Figma.
We wanted the survey to reach as many colleagues as possible
We distributed the survey primarily through existing Teams channels and University communities, which helped us reach a wide range of roles. These included groups focused on marketing and communications, human-centred design and digital development, as well as distribution via heads of IT.
The survey received 55 responses
We heard from 55 staff across a range of roles. Based on the categories participants selected when completing the survey, these were as follows:
- Marketing and Communications: 20
- Developers: 10
- UX and Human-Centred Design: 6
- Graphic and UI Design: 3
- Project or product manager: 2
- Other: 14
Although seven categories were available in the survey, no participants selected ‘Research’ as their primary category, so it is not shown in the breakdown.
The ‘Other’ category included colleagues working in areas such as product and project management, learning technology and academic support.
We refined the groups when analysing the responses
The survey categories gave us a useful starting point, but participants did not always recognise themselves within the roles specified (even when their job title directly reflected one of the options). For example, a participant selected themselves as ‘Other’, but their job title indicated that their work was within graphic design.
In order to evaluate the responses effectively, we revisited participants’ selected categories alongside their job titles and descriptions of their work.
This helped us six create groups that gave us a more useful basis for comparing responses:
- Developers and technical specialists
- UX practitioners
- UI and graphic designers
- Marketing and communications staff
- Product and project managers
- Learning technology and academic support staff
Some of these groups needed to be created on the back of this, as we had not identified those specific roles. For example, Learning Technologist was not an option for participants to select, but emerged as a useful category based on the number of respondents who had this as their job title.
After this assessment, we were in a better place to begin analysis, as these groups gave us a more useful basis for comparing responses while still reflecting the range of roles represented.
Analysing the survey results required two approaches
The survey produced both quantitative and qualitative responses, and we used different approaches depending on the type of question and response.
For the role-specific questions, we used FigJam (Figma’s whiteboard for online collaboration) to review and compare responses across the different groups. This included both quantitative and qualitative responses, allowing us to look at the detail within each role as well as compare responses across the wider dataset. We used Power BI, a data visualisation platform, to explore the common quantitative questions, which gave us a consistent set of responses across all participants.
We used FigJam to explore the role-specific responses
We created a large collaborative FigJam board to organise the responses. FigJam supported discussion within the project team, allowing us to work in tandem and analyse the data as a group (in person and asynchronously).
We read through responses from each group, compared them across different roles, and identified recurring patterns and themes. FigJam also allowed us to consider the quantitative responses alongside the more detailed qualitative answers, giving us a fuller picture of ways of working.

Section of our analysis on the FigJam board
Power BI helped us explore the common quantitative responses
Power BI allowed us to visualise responses across the opening and closing questions. We wanted to do this as they were common questions asked of all participants. Power BI allowed us to bring our data to life by presenting the data in a more visual way, highlighting the common patterns and themes more easily.

Section of our Power BI visualisations for the project.
Grouping responses helped us identify recurring themes
The open-ended questions in the role specific sections had more detailed responses. This required us to compare responses across the different role groups and group similar comments together to identify recurring themes.
As we worked through the responses, we also noted areas where a follow-up conversation with a participant could provide more context.
We also captured key quotations that illustrated what participants were telling us in their own words. These will be useful for when we playback findings to colleagues and complete a written report.
The research will inform the next stage of the project
The research highlighted both the diversity of digital working practices across the University and common themes across different roles.
The next stage will bring these findings together into a report. It will highlight where Figma currently supports existing workflows and where its integration will provide more consistent, unified delivery of digital practices across the University.
