TRAILS Design
Note: As this work is current, many of the artifacts shown are WIP
TRAILS is a nonprofit organization dedicated to teaching school staff how to educate and respond to mental health issues. I was hired as a Product Design contractor to help work out their multi language functionality, but was soon brought on board full time as a Design Engineer to flesh out the design system and operate as a design/dev hybrid.
When I first joined, TRAILS was in the final phases of receiving an updated brand and infosite from an external agency, but the materials were limited to marketing type content and unsuited for general product use. I had to take the updated brand and try to extrapolate and adapt it to fit our dashboard side of the app.
However, it wasn't long before the TRAILS mission and product went through a pivot phase, and with it came an opportunity to iterate on existing styles so that our brand is an extension of product, and not the other way around. Hoping to have a bit more fun with our identity, I began to draft a few "what if" concepts that leaned on my experience as an artist.
Unfortunately, the team was on sharp timeline to deliver the new product MVP, so extensive changes to branding were not in scope given the quantity of materials to update. Given though that we were switching to a new headless UI library (Shadcn), general product-look updates were still on the table. So with that, I got to work drafting up example screens to hash out the overall vibe.
In order to not overly influence the UX iterations of product design squad who were working grayscale on the new MVP, I came up with my own "fake" version of our product to test out theme.
At the time of this writing, I'm working on the frontend to begin adding components and applying this theme. Because of the size and nature of this team, design system source of truth will likely lie in the code and Storybook documentation.
I have much more I could share on all of this work, so if we happen to chat, I can go into my process in much more detail. Aside from that, I can list a few other odds and ends in terms of contribution to the team.
- solo edited sitewide css for brand refresh launch
- component frontend work to create and refactor components
- served as liason between designers and developers, communicating constraints and efficient design
- began a Figma component library, ultimately deprioritized given current team size
- UX work on flows for miscellaneous featuresets and side products