Lead the design of the Admin Domain feature for VTS. Requirements sessions were interactive, hands on and other team members were encouraged to grab a marker and express their thoughts.
This feature was to set up the admin domains for VTS. This session was done with Architects, Tech lead, Product Managers. By the end of the session, I had a good understanding of the problem and basic agreement on the flow.
This is how the final design turned out to be. This is the first model that was explored.
This feature provided rich interactions such as drag and drop.
User can connect different gateway groups on the canvas.
This is another feature for VTS that is very close to my heart. Lead the design from requirements, brainstorming, whiteboarding to concepts. This is one of the projects for which a patent has been filed and is currently pending.
In VTS, there Tenant Overlay Networks are represented in tabular data which makes it difficult to comprehend as the context is lost when the user moves to Network, Router, Tenants etc. This feature was discussed, brainstormed with Product Manager and Architect. to mitigate this issue and bring a comprehensive view of the Tenant network.
The following screens show how the actual design turned out to be.
Landing view of the Tenant Overlay Network
Drill down view of a specific network
Ports attached to specific Subnet
Ports spawned on a specific host
This was another challenging feature on VTS. These are advanced device configurations user can configure and save as a template. These templates can be applied to the devices per specific Network, Routers. The challenge was to represent the device model config that we get from NSO was very complex (based on YANG) in a usable form.
One of the goals of this feature was to onBoard the CLI users. I explored few visual concepts before we locked on to a final design.
Explored a visual concept for service extensions comfiguration.
Another visual concept explored. This was meant to be contextual drag and drop with WYSIWYG paradigm.
Final designs for service extensions. This was tested and performed fairly well. The CLI users loved this design and mentioned that they will use this design over CLI.
Worked with another designer to explore concepts for Cisco Evolved Programmable Network Manager (EPNM) project.
Trying to make sense of the dataset
Concept Exploration for EPNM Optical Provisioning Use Case
High Fidelity flow for Circuit provisioning.
High Fidelity flow for Circuit provisioning.
This was one of the special projects lead by the user experience team. There were few key workflows that were used across different products. The goal was to streamline these workflows. All Senior Designers were assigned a flow. I was assigned 'Add Devices' flow. I had a great time doing this project and thoroughly enjoyed the process.
The journey involved working sessions, brainstorming, ideation, sketching, prototyping and testing with users.
To understand the use cases across the products involved lots of working sessions with product managers and subject matter experts. I drafted the flow, reviewed with multiple stakeholders across products.
Once the basic flow was locked, next step was to transform the workflow into interaction models. It involved a lot of sketching. Again the sketches were presented, reviewed and tweaked.
Finally, created an Axure prototype which was tested with multiple users of different products.
Junglee.com - mission statement: "The defacto starting point for all purchase decisions for Indian consumers and a destination for buying anything."
I was responsible for IA, interaction, and user experience.
Several iterations of the ASIN flyouts with different datasets were explored.
It involved seller flows as well. Lot of research happened to find the right set of questions.
We didn't want to use Amazon's customer reviews display so I came up with another way to represent the reviews.
I redesigned the checkout and post transaction flow for Amazon India. It was little challenging as the way payment methods worked in India were little different as from rest of the world. Also, due to legacy systems, the Debit Cards from some banks used to work in a different way from rest of the banks.
The constraint for me was to maintain the sanity of Amazon's checkout but still be able to address the local use cases.
Lots of local banking use cases came into play in the checkout. We were working with a team in India to validate these flows.
The content for these flows took lots and lots of reviews. It was a great learning experience for me.
Re-ordering flow was also re-designed to address few local use cases.
gLike
Interaction Design
This section demonstrates my skills as an Interaction Designer.