Lead designer - user research, end-to-end design process & implementation support.
Design Manager, VP, CTO, Product Manager, Developers, Automation team, UX Designer (me)
9 Months
Netenrich is a SaaS company that focuses on AI ops and cybersecurity. I designed an experience for a self-service portal called Automations that allowed users to use pre-defined templates to automate repetitive tasks.
Unfortunately, due to NDA restrictions, I am unable to share the details of the project. This page contains a brief overview of the project but doesn't reflect everything I worked on— please contact me for the complete portfolio walkthrough :)
If you want to read about the entire project & have the password pleaseClick Here
At the beginning of 2021, I got pulled into a brainstorming session with the design and Automation teams. The initial meetings were filled with words such as Ansible, Yaml, and change management- all of which went over my head. The VP had the vision to create a platform where users could come and automate repetitive tasks thus saving time and reducing manual intervention. Soon I was part of this exciting project of bringing this vision to life.
The manual method of managing different IT services is cumbersome and requires significant time and effort. The tasks and commands for different devices are stored in a spreadsheet linked to a GitHub repository. To perform a task, the user must create a separate script for each task and further create a separate task for each device manufacturer. This process becomes even more tedious as the scripts must be updated every time the device’s OS is updated.
Automations resulted in a 100% task completion rate and allowed our analysts to reduce their time spent in completing these tasks by over 40%. This resulted in overall reduction in the time to resolve a ticket as well.
1. Clearly defining the product roadmap: With multiple PM’s and a changing vision of the product, one of my major learning was that without clarity on the goals, there can be multiple visions. Going forward, I would focus on detailing the use cases and clearly defining the acceptability criteria.
2. A/B testing: For design decisions that were heavily debated, I would use data to drive the decision. Given the opportunity, I would include usability testing for different features to choose a direction based on user data.
Principles like familiarity matter. No matter how ‘good’ a design is, people might stick with an older version if it is not easy enough to learn.
Learning to collaborate and communicate with different team members allowed us to work much more effectively. Through this project, I was able to define processes which were then implemented across the design team and in every project I did later on.