Veritas Cloud

Challenge Customers were providing feedback to Veritas that they were not feeling heard and that the Veritas cloud strategy was not well aligned with theirs. As a result, Product Management VP level leadership asked the CX team to assist in creating the Cloud Strategy for Veritas.

Solution Ran co-design workshops with customers, used feedback to create concepts for short and long term strategy, created designs for product release, validated with customers along the way.

Role Created and ran Design thinking workshops, Design Lead (for 3 designers), and Designer (3rd party integrations with Cloud Service Providers).

 

Background

Up until the CX org was involved, customer conversations had mostly followed an inside-out approach and focused on product use cases instead of jobs to be done, user pain-points, needs, etc.

Design and Research worked together (with support from Product Management) to create a Cloud Design Partner Program to involve customers in the design of upcoming data protection capabilities for the public cloud, including self-service, long-term retention from on-prem to cloud, disaster recovery for cloud workloads and continuous data protection for point in time recovery​.

process.png

Customer Interviews

The researcher interviewed 13 customers with roles spanning Data Protection, Infrastructure, and Cloud (including Cloud Architects). Some of the customers interviewed were Starbucks, Expedia, Qualcomm, and Southern California Edison.

Recommendations:

  • Create a simple and flexible data protection framework for service delivery across hybrid environments

  • Explore Cloud native and self-service tools that allow end users to execute use cases efficiently and autonomously instead of depending on their IT admins

  • Explore one-pane-of-glass visibility to meet compliance, cost, and efficiency-management requirements​

Design thinking workshop with customers

Using data from the interviews, I spent time with the researcher and product managers to understand the customers’ cloud data protection journey, future strategy and challenges and created some problem statements. We wanted to validate these problem statements with the customers and involve them in the concepting phase for an outside-in approach focused on user’s needs. We wanted a collaborative brainstorming process based on common practices used by Google Design Sprints, IDEO, Lean Development, RDL (Rapid Design Lab), etc. The process’ core belief is that the user’s presence is essential in the creative process as the users provide insight into what is valuable to them.

Screen Shot 2021-08-27 at 3.18.36 PM.png

I worked with the researcher to create a design workshop with these exercises:

  1. Problem definition validation - Spend time with the audience talking about the problem definition. Interestingly enough, this took up more time than we anticipated but revealed important insights and points of mis-alignment

  2. Hopes and Fears - Audience brainstorms on post-it notes their fears today and their hopes for this solution

  3. Problem Mapping - Group organizes post-its into groups and create an affinity map. They then vote on themes of interest

  4. Crazy 8s - Group starts ideating by noting/drawing down the first things that came to their mind when they though of theme. Speed is critical here

  5. Storyboarding - Picking one of these ideas, folks create flows of how the idea might work

  6. Share - Everyone shares their storyboards, group responds, provides feedback and discuss. They then vote on ideas of interest

73be1670-008a-4c74-a9b7-73f3dc75e098.jpeg

Challenge: Audience Hesitancy to ideate. Veritas makes products for highly technical users. So when we conduct such participatory design workshops, our audiences tend to be technical folks - IT admins, Backup admins, Engineers, Cloud architects, etc. They do not necessarily think of themselves as “creative” types and often are intimidated or reluctant to participate fully in the Crazy 8 process. I once had to help run a workshop on another project where the engineer put down their pen during the Crazy 8 part, folded their hands and did not participate! I wanted to avoid that with this audience and make them comfortable enough to let their guard down and let the ideas flow.

Approach:

  • I spent some time breaking through this barrier and talking about “creativity” means. It can be about brainstorming, whiteboarding and trying to figure out new ways to solve problems. A crazy 8 exercise is not about drawing pretty pictures and in fact, perfection is the enemy of speed (and hence progress) for this exercise. This exercise is about quieting the inner critic and giving our creative impulses space to flourish. It could go in any direction you want. The idea might seem weird, impossible and impractical but that’s okay. These ideas often give way to truly inspired ones.

  • I gave a live demo using an example (finding a restaurant to eat at) and talked out loud about what I was thinking and doing.

Outcome:

  • I was able to successfully make them comfortable enough to fully participate. There was lively and engaged discussion and debate when they were sharing their crazy 8s and storyboards!

  • Validation and clarification of Problem Statement

  • Outside-in approach helped reset & clarify assumptions, including from an architectural standpoint

Design thinking workshop with internal stakeholders

We conducted 2 similar workshops with internal stakeholders to explore these two problem statements:

AppOwnerPersona.png

Design Workshop 1 : As an App owner (with apps in Cloud), I need access to services that get my app data back in the manner and time that was promised to me in order to 1)optimally restore services as soon as I can 2) meet compliance requirements in a way that is simple, flexible and easy to use.

ITManager_Tim.jpg

Design Workshop 2: As an IT Organization, we need to easily deploy (setup and configure) the fundamentals of the solution in the cloud (with minimal Configuration steps) so that app owners can consume it

We included stakeholders from Product Management, Engineering, Design and Research. Instead of the Hopes and Fears section, we used How Might We statements to get everyone brainstorming. We also added a Competitive Research section. At this point, I began to include some other designers on the project and I asked them to conduct some research on partial or direct competitors and included that as part of the workshop (Cohesity, Rubrik, AWS, Nutanix, Cisco Meraki, etc. )

Workshop outcome:

  • Strong alignment of cross functional stakeholders around a common clearly communicated vision (Product Management, Engineering, Architecture, CX, Partner Services)

  • Validation and alignment of Problem Statements / Use Cases

  • Informed the prioritization of cloud use cases for initial design work

  • Input into “Jobs to be done” customer survey

  • Early ideation

Group generated How Might Wes and as a group we organized them by theme

Group generated How Might Wes and as a group we organized them by theme

Storyboards from the first workshop

Storyboards from the first workshop

Challenge : Create a successful online format for co-creative workshop. After the first workshop, the office went to working fully remote due to COVID restrictions, all participants were remote. So we had to figure out a way to keep brainstorming productive, not exhausting and keep everyone engaged.

Approach: We split it up over two days. We used tools such as Trello to share our ideas and do the affinity mapping. We used post-its and pictures and sharing tools to idea and sharing our ideas with one another

Outcome: We were able to successfully create and validate as a group a variety of promising ideas, concepts and a list of desired outcomes (example: how might we make it easy to try, how might we offer automatic recommendations on deployment patterns based on scanning the user’s environment) categorized across various themes such as Operational Efficiency, Ease of Use, Buying/Evaluate, etc.

We used Trello to organize into themes and discuss the How Might Wes we brainstormed

We used Trello to organize into themes and discuss the How Might Wes we brainstormed

We brainstormed Crazy 8s and storyboards and shared them on Webex

We brainstormed Crazy 8s and storyboards and shared them on Webex

Output from Design Labs

Ideation

The workshops revealed a wide variety of use cases we could explore. I worked closely with Research and Product Management to prioritize which ones to focus on. We also used data from a “Jobs to be done” survey the researcher conducted to help figure out which use cases are important to our users but are not being solved for today.

With this prioritized list of use cases, the designers and I started working on various concepts. I divided up the project into the following workstreams

  • NetBackup based : One designer designed concepts for flows launched from Veritas’ flagship Data Protection product (NetBackup).

  • Standalone Cloud product : Another designer designed concepts launched from an independent stand-alone product for Cloud protection. This independent product had not been build yet, but we wanted to fully explore this direction as well in order to think blue sky. If it was a powerful concept, we might be able to get executive buy-in to build it. Or it might help determine creative ways to solve the problem even if it ended up being within NetBackup.

  • Cloud Service Partner (CSP) Integration concepts for Deploy phase of customer journey

  • CSP Integration for other journey phases: I worked on these concepts. I also reviewed the other designers’ work, gave them feedback and design direction, coached and mentored them on various topics (handling ambiguity in this phase of the project, collaborating with stakeholders, etc.)

Competitive analysis and product research

We performed competitive analysis on the Cloud flows for these products and studied various products that were part of the user’s journey

Traditional On Prem competitors adapting to the Cloud

  • Rubrik

  • Cohesity

  • Veeam

Cloud Native Protection competitors

  • Clumio

  • Druva

  • Kasten

Indirect Competitors

  • Cisco Meraki

  • Nutanix

Automation frameworks (for Deployment phase of customer journey)

  • Terraform

  • Jenkins

Cloud Service Providers

  • Azure

  • Amazon Web Services

  • Google Cloud Platform

Flowcharts

The designers reviewed their concepts with me and I would give them feedback and direction. They would then revise and review with the stakeholders (Product Management, Engineering and Research). We also started creating some flowcharts for the concepts to help explain the bigger story of the entire user flow or use case.

Storyboards

The plan was that we would iterate a couple of times and then once folks felt comfortable that we had a good handle on the flows, we would move on to refined concepts for concept testing. However, in this project, some of the stakeholders had a challenging time visualizing the user flows.

So I thought it would be good to add an intermediary step to add some fidelity to the flowcharts and help with the visualization. This indeed helped move the discussion and internal validation along and we then moved into the refined concepting phase.

Screen Shot 2021-08-27 at 5.16.38 PM.png

Refined concepts for concept testing (Role: Design Lead)

Once we had a good handle on the flowcharts and the storyboards, we started refining the concepts. Here are a few of the interesting ones that I gave design direction on.

Storage Lifecycle

Here is one example of my design direction that evolved the design over time. The use case was to provide the user with a simple way to set up storage tiering during the setup process. We need to design an intuitive and straightforward experience that would give user information on where the data was currently stored, predictive insights into how much this would approximately cost and recommend changes they can make to bring down the cost.

Cloud Service Provider Integration (My role: Designer)

We explored concepts around integration with Cloud Service Providers (CSPs) such as Azure, AWS and GCP. Research had shown that the user personas (App Admin, Department Admin, etc.) spend most of their days in the CSP apps and would like a Cloud native app experience around protection and recovery. They do not want to leave the CSP app experience and go to NetBackup to perform tasks related to backup, recovery, etc. We focused on Azure first

Direction 1 - Light Integration. The first round of concepts was around light integration of the NetBackup product and CSPs. So the user(s) would need to execute flows using both products.

Direction 2 - Deep integration with CSP, get inside the fabric of the CSP

After we started working on the concepts, it quickly became evident that this would be a problematic user experience as the user would have to execute pieces of the flows in two different products, so the experience would appear broken. Even if we were to use SSO so that once users logged into NBU, they would not have to log into the CSP and vice-versa, it would still be a less than ideal experience for the user. Product Management and Architecture started discussing conversations that they could have with the CSPs to explore deeper integrations for Veritas features (such as backup and recovery) within the CSP products. In order to facilitate these conversations with the CSPs, we created some concepts to help illustrate the value of the Veritas data protection and recovery features within the CSP and the extreme ease-of-use for the user.

Wireframes for NetBackup SaaS Protection (Release: December 2021)

The concepts we created helped inform the Veritas Cloud Strategy in the long term and short term (focus on SaaS app protection - Office 365, Salesforce, Dynamics 365 and G Suite). These Office 365 app protection and recovery features were referred to as NetBackup Saas Protection (NSP). Released in Dec 2021.

Final Designs (Release: December 2021)

Here are some screenshots from the final product - NetBackup Saas Protection (NSP). Released in Dec 2021.

Outcome

  • Outside-in design workshops captured customer POV and helped reset & clarify assumptions, including from an architectural standpoint

  • The concepts we created helped inform the Veritas Cloud long term strategy and short term releases for Netback Saas Protection and Recovery Vault

  • We produced over 30 concepts and 150 concept wireframes, 10 flows spanning 7 phases of the Customers Cloud Journey (Evalulate, Buy, Deploy, Configure, Operate, Monitor, and Report).

  • Growth of designers, including 3 promotions

IMG-2527.jpg
Picture2.png
 

“Manisha is a highly experienced designer and leader that is equally dedicated to the product and the team. I have had the pleasure of working with and learning from Manisha in multiple contexts over the last few years. She has been a great collaborator and teammate for projects which we worked on together, always offering a unique perspective and thorough consideration for the user. She has also been an amazing manager: I was constantly met with support, understanding, and encouragement, and I appreciate that she was always mindful of providing growth opportunities. She maintained a balance of support and independence, stepping in if and when needed, which has helped my development as a designer tremendously. She has been excellent both as a fellow designer and manager, and I would highly recommend her.”

rglicrop3.png

Rachel Goldman, UX Designer, MSc Digital Design Student at Hogeschool van Amsterdam