A question bank feature for a forms management project that helps users store questions and apply edits
TIMELINE
3 months
COMPANY
Springshot
ROLE
I was the solo designer on this project, and worked with the team to refine the use cases and create the designs for all the edge cases in this project.
At a glance
THE PROBLEM
When a single question appeared across hundreds of forms, users had to hunt it down and update each instance manually.
WHAT WE DID
Created a 'question bank' which is a repository of questions that can be used to apply edits across every form
IMPACT
Reduced the time taken to edit and manage forms.
Created a centralized system reducing version drift and error rate
ABOUT THE PROJECT
Springshot’s forms feature helps airline operators support complex operations across various worksites and roles
Springshot manages a robust forms feature that is used by airlines across multiple worksites to manage and track data.
However, with hundreds of forms and multiple users editing the forms it became difficult to track edits. The user had to manually edit every instance of a question across multiple forms.
THE IDEA
Creating a central system to manage questions and track edits
We decided to create a 'question bank' which would act as a repository of questions. Any question stored within the question bank can be used in forms.
Taking inspiration from Figma, we went with the concept of 'components and instances'. When a Question Bank question is edited, the changes are automatically applied to all forms that use that question.
ENTERING THE EXPERIENCE
The question bank page is a subset of the template page
CREATING A NEW QUESTION
There's 2 ways to create a new entry on this list
Start from scratch and create a new question from the templates page
CREATING A NEW QUESTION
Convert an existing question into a question bank question
QUESTION DETAILS
This page shows the full details of a question, including any related or follow-up questions that are triggered by user actions.
It also lists all the forms where the question appears, giving users visibility and control along with the ability to easily unlink it from specific forms.
ANSWER SETS
Paired with the question bank, we created reusable answer sets that could be used across forms. These pre-saved, detailed options helped streamline the form creation process and ensured consistency
ADDING QUESTIONS FROM QUESTION BANK
To keep things simple, we added the question bank to the creation bar as a dropdown. This made it easy for users to find, browse, and reuse existing questions without breaking their flow.
LEARNING
01
Understanding development constraints
Designs don’t exist in a vacuum. I had to understand technical constraints and collaborate with developers early to align on what was possible and where we could flex.
02
The importance of craft
Visual real estate became something I thought about a lot during this project. I had to slow down and really consider what needed to be on the screen, what could be tucked away, and how users would scan and move through the layout.
