SaaS Asset Management App (Dream™)

Project 1 / 9

I redesigned and prototyped a SaaS asset management and repair ticket app, Dream Asset Management, used by K–12 schools to streamline workflows and improve clarity. As the sole designer on the development team, I collaborated with developers, QA, and the product owner to create a more intuitive, visually organized experience within real-world technical and time constraints.

  1. Context & Collaboration →
  2. Design Execution & Documentation →
  3. Impact & Takeaways →

I enhanced usability by streamlining navigation, adding visual elements like chips and cards to simplify complex data, and documenting design decisions to improve collaboration and handoffs. These updates made it easier for the team to visualize solutions, align on priorities, and deliver a smoother, more effective product experience.

Date

September 2024 - Present

Role

Web Designer (UX/UI)

Tools

Figma, Visual Studio Code, GitHub

Project Type

Vivacity Tech PBC

Context & Collaboration.

Design Within Constraints.

This app was part of a medium-size platform without a true design system. A full redesign wasn't feasible, so I focused on incremental improvements, making layouts cleaner, reducing clutter, and improving flow without distrupting development timelines. Because I worked closely with product and engineering, I learned how to adjust design expectations to fit technical limitations while still advocating for and improving user experience.

Cross-Team Communication.

I ran bi-weekly design meetings with the product owner, developers, and QA to align on priorities, confirm feasibility, and make sure design intent translated correctly into development. These sessions became a key space for feedback and planning, ensuring design was part of every product discussion. When collaborating with other departments, like marketing and leadership, I helped communicate how UX decisions tied into business goals and customer satisfaction.

Design Execution & Documentation.

Improving Usability Through Structure.

As the app grew larger, one of the biggest pain points was navigation complexity. After a UX/UI workshop with the product owner and company CEO, I redesigned the layout by decluttering the left sidebar, moving lower-priority pages to a top navigation bar, and simplifying the overall information hierarchy. Additionally, I introduced chips, card components, and more variety of charts to give data more visual meaning, reducing cognitive load for users who frequenty managed hundreds (or thousands) of assets at once.

Design Documentation for Clarity.

With frequent releases and tight deadlines, I began placing design documentation directly in Figma, explaining design reasoning, usage rules, and fallback recommendations for when features couldn't be fully implemented. This helped developers make informed choices and reduced miscommunication when deadline-influenced decisions had to be made during development.

Notes were left for developers on each Figma frame, explaing design decisions, so they could make informed decisions.

Impact & Takeaways.

Empowering Development Through Design.

Over time, design became a trust part of the process rather an afterthought. Developers and other teammates often said they could hand me a project brief and I'd return with something that made the problem instantly visible and solvable. The clarity of prototypes improved cross-team understanding, allowing new features to be scoped and built faster.

Incremental Improvements That Scaled.

While not all the UI was flashy, it became far more functional. By improving structure and documentation, I helped the team reduce confusion, visualize ideas (and possible constraints) sooner, and keep development aligned with UX intent. Incremental design improvements added up to a smoother user experience and a more maintainable product, proving that thoughful design decisions can make a significant impact even under real-world constraints.

I incrementally improved designs and handoff without disrupting the development workflow.

Explore the Case Studies

Designing for Dream™ meant balancing user needs, technical limits, and business goals, often under tight deadlines. These case studies dive deeper into that process, showing how I solved usability challenges, collaborated with developers, and turned feedback into practical, real-world design improvements.


Previous Project Next Project