Trying a product
Open source enterprise software
When marketing enterprise software, we have requirements to allow users to test the products out. Selling open source enterprise software makes the process of giving the user what they need even more challenging. The goal of the business is to connect with the user, finding ways to make sure they’re enabled to understand how the product can fit in their stack. So we had to find clever ways to make sure the user understands the value of starting a trial for complex technology.
One of the ways I enabled designers to understand how users may be interacting with our product trials was through user journeys and flows. This helped to identify roadblocks, opportunities, new pathways, organic strategies, amongst others needs of our design process. As part of the product trial work, we used our existing personas to identify how they may interact with our trials.
This wasn’t always research-backed from the start or tried and true, but it gave everyone a general understanding of what’s trying to be solved from both the business and user lens.
Templating & enablement
Once the methods for the correct product flow are designed and tested, it’s crucial that there’s consistency in the way users interact with the company’s portfolio.
I created guidelines for developers to understand what needed to be templated and what was flexible, and what needed to be dynamically driven by the CMS. This also helped to ensure efficiency when a new product trial was spun up, or a new feature needed to be enabled across all products.