Role

Team Lead
UX Designer
UX Researcher

Duration

8 Weeks

The Team

4 UX Designers

Approach

Lean UX

Tools

Figma, Figjam, Discord

The problem

The designer's struggle with color

In the design world today, designers struggle to curate a color palette for their UI-based design projects. Those new to design lack the knowledge of color accessibility guidelines and struggle with ensuring the colors used in their designs are accessible to their end-users. Stipple was designed to solve this problem.

Our approach

Designing with assumptions & a Lean UX mindset

This project was completed as a part of my Interaction Design II course during my senior year Fall semester at KSU. Our team adapted elements of the Lean UX approach to fit with the time constraints of our course timeline. We started off with a set of assumptions about our domain space, the design field, in order to quickly validate and test during a series of two 3-week sprint cycles.

01. Design week 0

Layout out assumptions on the Lean UX canvas

02. Sprint week 1

Building experiments/MVPS, testing, and interviews

03. Sprint week 2

Build new experiments/MVPS,
testing, and follow-up interviews
Kicking off

Sprint one - our initial assumptions

Our team kicked off the process by laying out all our assumptions we had about our problem space. I held a meeting with my team where we had open discussions about any questions we had about the problem space and any clear assumptions we had about the domain.

Since we were working in the design tool space, our team laid out the initial assumption that our users would be designers in tech. We assumed that they needed a tool that could be use as a source of collaboration for their team, and that they currently lacked a resource for learning more about color theory. These were assumptions that we aimed to validate through testing with an MVP, or minimum-viable product.

Building our first test

As a collaborative effort, our team got together and started to put together our first test. Our first test developed in the form of a two-screen lo-fi wireframe where we were testing whether users would utilize a feature that allowed them to share color palettes with their team. Since this was a big assumption we had as team, it was important that we tested this early so we can ensure we were using time and efforts wisely.

Validation through interviews

During our first sprint cycle, my team held interview sessions with 6 participants who fell under our assumptions for our ideal persona, the junior designer with 2-3 years of experience with design.

Major insights we gathered

01. People didn’t need a tool to share color palettes with other designers in their team because they were typically working individually or in a shared work environment such as Figma or Adobe XD.

02. Designers didn’t really need to learn more about the basics of color theory, they wanted resources they could reference about the best accessibility practices when it comes to using color in their UI-based designs.

03. Designers wanted a way to quickly “preview” a color-palette on any design of their choosing.

Revisiting the Lean UX canvas

Sprint two - Revalidating our assumptions

As my team’s leader, I scheduled a meeting with my teammates with a focus on revisiting our initial assumptions we laid out on our Lean UX canvas. I guided our meeting by asking my teammates the following questions: What did we learn from our users? What assumptions can we toss out? What assumptions do we need to add in and further test?

I realized that as a team, we were focusing on creating a product that was too general and broad. Instead of trying to target every and any kind of designer out there, we decided that we would focus on designing for UX and UI designers who would benefit from using a UI-based color palette generator.

Because of the insights gathered during our first round of interviews, our team decided we would focus on further testing having UI-color accessibility resources alongside a color palette generator that focused on generating UI-based color palettes only. Additionally, we would test what previewing a UI-based color palette on a design would look like for our users.

Shifting gears and our new approach

High value, high effort mvp building

As we were nearing the deadline for our project, our team decided to build a more fully-functional mvp that consisted of new features we wanted to test with users based on our previous insights. We decided it was worth the effort of testing out our assumptions we predicted were of higher value to our users. Here, our screens started to become of mid-fidelity and our users gathered a more in-depth look of how our product worked.

01. Design week 0

Layout out assumptions on the Lean UX canvas

02. Sprint week 1

Building experiments/MVPS, testing, and interviews

03. Sprint week 2

Build new experiments/MVPS,
testing, and follow-up interviews
Further validation

Bringing Stipple to life and usability testing

During sprints week one and two, our team was busy bringing Stipple to life in higher-fidelity. As a team leader, I thought it would be beneficial for our team to get at least one week of usability testing in. I found it important to see if our product was usable for our users.

After prototyping our first iteration of Stipple together, we presented our prototype to our interview participants along with a set of tasks we asked for them to complete. Our tasks were centered around two main features of Stipple, generating a color palette and previewing a color palette on a UI.

01. Design week 0

Layout out assumptions on the Lean UX canvas

02. Sprint week 1

Building experiments/MVPS, testing, and interviews

03. Sprint week 2

Build new experiments/MVPS,
testing, and follow-up interviews

Insights we gathered and improvements to our design

01. One of the main takeaways we gained through usability testing with participants is that some of the labels and phrasing we used in the color palette generator didn't make sense to the participant, causing confusion while completing the usability tasks.
02. We followed-up with additional questions about what the user would expect under labels and what they would name labels to better understand the participant's mental model. We then proceeded to update our design to fit the participant’s mental model better.
The end result

Building the prototype and putting it all together

01. Generate UI-focused color palettes

With Stipple, designers can generate color palettes specifically designed to to be used for their UI's that meet web accessibility guidelines.

01. Design week 0

Layout out assumptions on the Lean UX canvas

02. Sprint week 1

Building experiments/MVPS, testing, and interviews

03. Sprint week 2

Build new experiments/MVPS,
testing, and follow-up interviews

02. Preview color palettes on a UI 

Designers may easily preview any of their saved color palettes on a UI template of their choosing.

01. Design week 0

Layout out assumptions on the Lean UX canvas

02. Sprint week 1

Building experiments/MVPS, testing, and interviews

03. Sprint week 2

Build new experiments/MVPS,
testing, and follow-up interviews

03. Gather community inspiration

With a community tab, designers are never more than a click away to view other color palettes used by designers in their field.

01. Design week 0

Layout out assumptions on the Lean UX canvas

02. Sprint week 1

Building experiments/MVPS, testing, and interviews

03. Sprint week 2

Build new experiments/MVPS,
testing, and follow-up interviews

04. Learn more about color and accessibility

UI color accessibility guidelines are available for designers to access and reference whether they are new to learning or need a refresher from time to time.

01. Design week 0

Layout out assumptions on the Lean UX canvas

02. Sprint week 1

Building experiments/MVPS, testing, and interviews

03. Sprint week 2

Build new experiments/MVPS,
testing, and follow-up interviews

👉 Click here to experience the interactive prototype

Reflecting back

Things learned as a first time design leader

01. Figma! I learned so much about Figma as I worked on this project. This project challenged me to not only work within a design system, but build my own design system for our product that my team and I could use to create consistency within our product, as well as, promote a more efficient workflow while building our prototype.

02. Autolayout, components, and variants are your best friends in Figma. I love them and can not imagine designing without them anymore.

03. I learned how to balance out the strengths and weaknesses of each of my team members to ensure everyone was comfortable with their responsibilities with the product, but also made sure to challenge each of my team members to do something new in order to help them build on their skills.

04. As an organized individual, I learned what it was like to have to be organized while working with the schedules and timelines of my team members. I learned so much about the importance of keeping your team members up to date about scheduling, team meetings, weekly check-ins, and project progress throughout the last 8 weeks.

05. I learned… I really love leading a team and leading those I work with. It was such an amazing learning experience working with a team of my peers. Reflections were very important and I found the experience very rewarding. I hope to continue to find opportunities to lead a team of designers in the future.

Meet the team that made it happen, not pictured Graciela Cabrera and Ayo Fagbamiye

Thanks for checking out my work with Stipple

Want to collaborate or chat? I'd love to connect with you. Feel free to email me, send me a message through LinkedIn, or schedule time to meet with me.

back to top