Pegasus: Media Buying Platform (SaaS)

Pegasus is a self service product where client users can build and buy ads through Kargo’s network that transacts on a cost per completed view metric (CPCV). This means that Kargo would guarantee that all billed clicks on a client’s ad were intentional clicks by the consumer. To measure this, the consumer would need to remain 5 seconds or longer on the advertisers landing page for it to be counted. I worked on a team of designers, product managers, and engineers to help build this product. My role was to integrate our Composer Ad Builder product into Pegasus so that we can enable ad building as feature of the platform. Since Composer was a more mature product, we chose to repurpose it and use its technology for Pegasus. However, we needed to update Composer to match our new design system as well as follow the correct requirements needed for Pegasus.

Methods applied:

  1. High-Fidelity Designs

  2. Usability Testing

  3. Affinity Mapping

  4. Stakeholder Feedback


High Fidelity Designs



Usability Testing

GOAL

Validate our proposed design solution when integrating the Composer Ad Builder into the Pegasus platform.

METHODOLOGY

Held 5 usability tests with internal users. Created a testing script so the team can align on all the tasks and questions being asked to the participants.

Affinity Mapping

GOAL

Analyze and synthesize the data gathered during the user interviews.

METHODOLOGY

Transferred notes from all user interviews over to FigJam. Color coded notes by user. Worked with Product Manager and other team stakeholders to sort the notes into themes across all users that were interviewed. Identified reoccurring themes.

FigJam Board

results

The Composer portion of the flow tested perfectly. All users felt that the integration of Composer into the pegasus platform made sense. They had some feedback regarding features within the pegasus campaign set up, but as far as my involvement, we validated the work and we were good to move forward to development.




Final Designs / Flows

This was the final figma file that was shared with the development team so that they can understand all flows and use cases with the integration.