Banner.png

Immediately after wrapping up ⚡Flow Builder, our team moved into insights. As with the Flow Builder, I worked as the primary designer and partnered closely with the same group (1 PM and 6 engineers). Because insights and playbook reporting were new to Catalyst, I spent a lot of time researching and validating with customers and collaborating with my PM on scoping the work. This project took about a month and was shipped in early December.

👋🏼 You can play with the early prototypes here (these were used to test ideas)!



Main Problem

Our hypothesis when it came to playbooks was that by nature, they were very "drafty" in the sense that they were never really perfect and would always need to be refined and maintained (much like a design system 😉). However, with our current offering, we were missing the mark on giving users actionable information to help improve their workflows:

  1. Users couldn't know which playbooks were behaving as expected and which weren't. So there was no way of defining success.
  2. Similarly, there was no place for an admin to see an aggregate view of how a specific task or email was performing. Seeing this info per individual action was too repetitive and ineffective.