1 — Role
“What is your role?”
Content/Product designer, Frontend engineer (platforms are separate options as they have different experiences), Other (for any scallywags).
2 — Tenure
“How long have you been at TravelNest?”
Having different options for this will give us an insight into whether new hires have very different opinions in comparison to those who have been here longer. What are your assumptions within your own company? At the time of running this survey I had only started initiatives around educating new hires across our Tech org, so expected the results to vary.
3 — Quality
“Our design systems make it easier for me to build a high-quality UI.”
Ratings-based answer Quality is a staple and widely-understood benefit of a design system, thus it should be included.
4 — Speed
“Our design systems help me implement or design features faster.”
Ratings-based answer Much like quality, speed is a staple and widely-understood benefit of a design system, thus it should be included.
5 — Confidence
“I feel confident in using our design systems.”
Ratings-based answerIt is important that people feel they are armed with the right information and are getting the most out of our design systems. I feel the word confidence captures this well. We know from previous insights that there are a lot of uncertainties around many things so for us it was imperative to include this and monitor it going forward. Remember our vitals? I feel like this is an opportunity for a pun, but I can’t lose all credibility just yet.
6 — Contributing Back: Ease
“I can contribute back to our design systems with ease.”
Ratings-based answerThis is broken out from Speed based on the insights from our own research. Our insights signal that different platforms have trouble contributing back, which can be either Ease or Speed related or even both.
7 — Contributing Back: Speed
“I can contribute back to our design systems with speed.”
Ratings-based answerThe same rationale behind number 6.
8 — Completeness: Availability
“I find myself using something that is outside of our design systems.”
Frequency-based answerOne of our main insights is around the disparity between what is available in our design tool libraries vs. our code-based component libraries. There is a different percentage of components available in each platform and there will be some cases where:
- What they require is in Figma but not code (yet)
- There is something similar available but does not fit their needs
- There is nothing similar available
So it’s something that our team should definitely include.
9 — Completeness: UI Coverage
“Design systems covers at least 80% of my use cases when building a UI.”
Yes/No answerOur design system will not cover 100% of use cases, which is totally fine. 80% is based on the Pareto principle (80/20 rule). I believe this is a realistic number for us to be aiming for in terms of adoption across each application. Those 100%-ers are living in a pipe dream. For now, doing this through a survey is a good place to start until we can properly quantify how much is actually covered in each application.
“I know about the latest updates in our design systems.”
Ratings-based answerI don’t need to say anything here, do I?