When I joined Poly, I didn’t know what to expect and it felt a little awkward trying to find my place but it’s a really good team to work with and I’m enjoying trying to figure things out alongside them.

In the beginning, while we were rushing to get things done, the other UX designer and I ended up with so many inconsistencies in our iterations because we didn’t have some sort of temporary design system in place. If we created some sort of component or symbol library from the get-go, I think it would’ve saved us a lot of time. So we came up with a simple design system to help us create flows and prototype faster.

Initially, I was tasked to show through low-fidelity static screens how an admin user might be able to create an event through the desktop app.

After a few static iterations to show potential stakeholders, I was able to create a low-fidelity user flow that demonstrates how an admin user could create an event.

The feedback I received was super helpful. A few of them were:

* An admin user might find it helpful to input reoccurring events all at once.

* If an admin user needs to input reoccurring events, how can that information also be further segmented to different times and different days of the week?

* Can an event be pushed out through social media?

* A way for an admin user to be notified how many people were coming to an event would be super helpful.

Analytics is another feature that Mesh is trying to roll out for potential organizations. Organizations that have shown interest in Mesh inquired about the ability to see the data on how many people came to an event, how they heard about the event, etc.

View the prototype here.

At the time of this writing, Poly was still trying to get buy-in from other organizations and companies. For the time being, I was able to create new static screens and low-fidelity user flows quickly to help Poly have something tangible to share with potential stakeholders.