As a Product Designer at Nulogy, I was responsible for identifying, analyzing, and communicating user, business and design requirements to all product stakeholders. I lead user research and user testing sessions to inform the creation of project success criteria and the design of workflows, domain models, story maps, sketches, wireframes and prototypes.

As part of the Nulogy Design team I lead the design of Nulogy’s QCloud and GO applications and was one of four designers responsible for the UX and UI design of Nulogy's core application, PackManager. I was also given the opportunity to lead the work creating a unified visual design language that will be applied to Nulogy’s design system.

PackManager is a materials planning, production, inventory and order management application for co-packing operations

Case Study: Enabling a GxP Compliant Workflow

As the packaging and manufacturing landscape evolves, there is an increasing need for customized products within strictly regulated industries. As Nulogy looks to expand its business to these industries, it became clear PackManager (Nulogy’s core application) needed to support workflows in these environments to continue being a world leading contract packaging application.

Market, regulation and customer research needed to be done in order to truly understand how workflows within regulated industries would impact Nulogy's products. As part of this, a charter user group was put together to help the Nulogy team understand user requirements and to provide feedback throughout the design and development process.

Step 1: Research

Understanding customer requirements for this project required many industry visits and calls while simultaneously investigating the diverse and complex regulations, and its applications, in Canada, the United States, and Europe.

I joined a multidisciplinary Nulogy team for an onsite engagement in the UK with one of our biggest customers packaging products in a highly regulated environment. The main purpose of this onsite engagement was to run collaborative workshops with our end users to better understand how these users perform their work. The results of these workshops were crucial in order to set up success criteria for this project.

Step 2: Defining the Problem

To better define the problem we needed to more deeply understand how our research would impact user and regional validation requirements. Understanding each of our user's goals when using the system lead to the creation of personas who interacted with PackManager as well as with themselves throughout the product life cycle.

Step 3: Ideating, Prototyping and Testing

Once every agile team team was aligned and understood the project's requirements and success criteria, we brainstormed ideas of how to  best implement all workflow changes and improvements. Keeping project deadlines in mind was crucial in order to determine an incremental approach in designing and developing solutions to release the most important functionality first; building every workflow into our full vision with every subsequent release. As we hypothesized and prototyped possible solutions, we reached out to users in our charter user group. Throughout this process, the charter user group answered questions and provided feedback for all hypothesis and prototypes as we refined each of our solutions. This process helped the multidisciplinary team maintain an iterative mindset and provided valuable interactions that informed all of our design and development decisions.

Step 4: Implementation

As we (Nulogy) gained increased alignment with our customers on a prioritized implementation plan, we refined all solutions into high fidelity prototypes and wireframes. Each solution was broken up into smaller bodies of work, each of which were then subsequently broken up into user stories containing acceptance criteria and UI/UX requirements. All user stories were then prioritized by each of their respective agile teams, ready to be developed by our development team. We maintained weekly calls with members of our charter user group in order to gather feedback on developed functionality. Always staying agile and making sure we were able to correct and/or iterate on our new functionalities quickly