Netenrich is a SaaS company that focuses on IT ops and cybersecurity. This project was a redesign of an existing node-based data visualisation tool used for IT asset management and analysing incidents. I focused on improving the overall experience by defining the functions, micro-interactions and visual design.
Lead designer - user research, end-to-end design process & implementation support
Design lead, Product Manager, CTO,
3 Developers, Architect and UX Designer (me)
3 Months
Due to NDA restrictions, I'm unable to share the details of the project. This is just a brief overview. For a complete portfolio walkthrough, feel free to reach out! If you want to read about the entire project & have the password pleaseClick Here →
This was my first project leading the entire design. When this project was first introduced to me, the entire feature seemed intimidating and complex. Asset management and AIOPs require deep subject matter expertise.
So my first step was to gain a basic understanding of what the user’s needs would be and what this feature was to be used for. I aimed to simplify and abstract the concept, so I had enough context to focus on the UX.
Unfortunately due to changes in the priorities of the business roadmap, the feature was used mainly for demos and by some internal users. A more granular version of the graph was recently integrated with the incident resolution solution.
1. Evaluate cross-functionality: While this feature was designed to work as a singular module by itself, it had much potential to be integrated within various other offerings in the platform. I would work with the product team to create more specific user scenarios.
2. Accounting for large-scale networks: For MaSPs the network was of a large scale and thus resulted in data overload. Even with the query builder, only the usage of filtering helped the graph become comprehensible. Testing the graphs with different data sets and de-cluttering the chart by grouping nodes is something I would have focused on.
The product itself is iterative and launch doesn’t mean all features have to be launched at the same time. Old ideas are revisited and features are staged out as and when the need arises.
Although the features are domain-specific, many interaction patterns are often common across different products. One doesn’t need to be a technical expert to advocate for the user.