Team
Product designer
Product manager
Technical documentation
Back end engineers
Front end development
Make a feature be a network troubleshooting tool it was intended to be instead of the data visual tool it is behaving as.
When a website experiences a slowdown or an error the immediate thing to check is if it is dealing with a network issue.
Pulsar helps companies keep their websites performing well by automatically steering their website traffic to the best servers at the right time. Companies can see the results of the automatic solution but not why. I need to make
Pulsar is not just a data tool but it needs to be tool that gets users to the next steps in understanding why an error might be occurring
In this feature build I solved for…
Pulsar automation solution behaving as a blackbox. I found a way to show clarity and data for a solution that doesn’t have clear data backing its results and decisions
Transitioning to a new design system while making one of the largest updates to the feature so I had to make fast decisions and updates to the designs when a blocker occurred with both back end and front end development
I designed with ambiguity as I had to work in parallel with back end as they did not know what was and was not possible
Design process
Defined requirements with Product in discovery
User interviews with low fi prototypes
User interviews with mid fi prototypes
Hi fidelity hand off with development
Design iterations based of development limitations
Big wins
Largest feature update for the product that was successfully released and it caused a +73.1% spike in customers on the page.
Portfolio 2024
United States