I joined Chipply's product design team in September 2025. As one of two designers, I've had the chance to take significant ownership—leading projects from discovery to handoff and shaping core parts of the platform.

Several features in varying stages of development are moving us towards our end-to-end vision. While details remain largely confidential, tackling these large user flows have helped me grow in several important ways:

• Systems thinking: it's been critical to address not just the immediate workflows, but also how added functionalities will cascade across the entire lifecycle of an order. We've used these projects to catalyze broader stakeholder conversations around statuses, file management, and traceability on the platform.
• Meeting users in their workflows: our users range from small shops to large operations, with a diversity of workflows and processes. Rather than impose what we deem to be best practice on them, we've sought to design flexible architectures that accommodate a wide range of shop management styles. This has been an exciting challenge, and we've relied heavily on building modularity, rather than a top-down solution.
• Building a foundation: our team has spearheaded several research initiatives to gain knowledge and confidence before entering new domains. From mapping an ecosystem of user personas, to analyzing eCommerce users, we've been able to quickly and resourcefully deepen our understanding of new user groups. These insights have also helped to align teams, like marketing and sales, on the goals of each feature.

As our platform expanded beyond store setup into more complex workflows, it became clear that our existing navigation couldn’t keep up. The old structure reflected early product priorities but struggled to support new features and user pathways. A redesign was essential to enable the platform’s continued growth. Our design team led the initiative, balancing the current product with the future vision, gaining stakeholder buy-in, and collaborating across teams to redefine how users move through the system.

Redesigning the navigation required deep systems thinking. It was essential to balance the familiarity of existing user habits with a forward-looking product vision. We mapped flows, defined page hierarchies, and collaborated closely with stakeholders to create a navigation model that can scale as the platform evolves. Key areas of impact included differentiating between global and store views, and establishing groupings designed to grow over time. The result is a cleaner, more intuitive structure that streamlines current workflows and lays a strong foundation for what's next.

When I first joined Chipply, there wasn't an established design system. I've since led the effort to build a cohesive, cross-platform component library (enterprise & eCommerce), and I continue to maintain and evolve it.

This design system has become a foundation for our entire engineering team, helping us build faster, stay consistent, and elevate our visual language across the platform.

Chipply is a complex platform, with deeply interconnected workflows tracing down to a single item ordered by a customer. Whenever I design a new feature, my first step is mapping the upstream, downstream, and intersecting flows. For example, a change in Purchasing will almost always ripple into Production Management, even if it initially seems unrelated. This mindset has been essential to helping us ship quickly without creating “merge conflicts” in the logic and user experience.

I apply the same systems-level thinking to our design system. Across engineering and design, we’ve made a concerted effort to prioritize and evolve the new system. Despite early growing pains, it's already proving its value dividends as we build more complex features.