Multi - Cloud SaaS Platform
Multi - Cloud SaaS Platform
Multi - Cloud SaaS Platform
IBM SaaS Platform is a console aimed to make it easy for customers to find and try out IBM Automation SaaS products on the AWS Marketplace. Our primary objective was to provide users with a centralized and cohesive experience through the IBM SaaS Management Console. We aimed to streamline and simplify the user journey by offering a unified interface that seamlessly integrates all the IBM products.
IBM SaaS Platform is a console aimed to make it easy for customers to find and try out IBM Automation SaaS products on the AWS Marketplace. Our primary objective was to provide users with a centralized and cohesive experience through the IBM SaaS Management Console. We aimed to streamline and simplify the user journey by offering a unified interface that seamlessly integrates all the IBM products.
My role in MCSP
My role in MCSP
In this project, my responsibility involved understanding the requirements, elaborating on the needs, and generating comprehensive workflows for the product. I collaborated with product management, engineers, and a compact group of designers throughout the process. The timeline of this project is about 28 months. Additionally I also worked on side projects during this time read more about them at the end of the projects.
In this project, my responsibility involved understanding the requirements, elaborating on the needs, and generating comprehensive workflows for the product. I collaborated with product management, engineers, and a compact group of designers throughout the process. The timeline of this project is about 28 months. Additionally I also worked on side projects during this time read more about them at the end of the projects.
Design process
Design process
We practised IBM design thinking in this project. It has a user-centric, iterative approach. It emphasizes empathy, cognitive diversity, and rapid iteration. The process involves observing user needs, reflecting on insights, making prototypes, and iterating based on feedback.
We practised IBM design thinking in this project. It has a user-centric, iterative approach. It emphasizes empathy, cognitive diversity, and rapid iteration. The process involves observing user needs, reflecting on insights, making prototypes, and iterating based on feedback.
Problem identification
Problem identification
Customers find themselves navigating up to 8 distinct systems to purchase and oversee IBM SaaS subscriptions and software licenses. Frequently, these systems exhibit redundant features. This leads to a disjointed, inconsistent, and confusing experience for customers. Simultaneously, IBM incurs duplicated operational expenses and misses out on potential sales opportunities due to this inefficiency.
Customers find themselves navigating up to 8 distinct systems to purchase and oversee IBM SaaS subscriptions and software licenses. Frequently, these systems exhibit redundant features. This leads to a disjointed, inconsistent, and confusing experience for customers. Simultaneously, IBM incurs duplicated operational expenses and misses out on potential sales opportunities due to this inefficiency.
Customer journey map
Customer journey map
Ofcourse this is vast, Let me summarise this. In this map the customers journey from the discovery phase to the usage phase including the help and support is mentioned. This map also has plotted points where the 8 different personas interact and work together. Using this map pain points of those 8 personas were identified and then classified accordingly.
Ofcourse this is vast, Let me summarise this. In this map the customers journey from the discovery phase to the usage phase including the help and support is mentioned. This map also has plotted points where the 8 different personas interact and work together. Using this map pain points of those 8 personas were identified and then classified accordingly.
Pain points
Pain points
Fragmented Monitoring Overload: Without a SaaS console, teams face the daunting task of juggling multiple monitoring platforms for each SaaS product. This fragmented approach leads to inefficiencies.
Incomplete Performance Picture: The absence of a unified SaaS console deprives teams of holistic insights into performance metrics across various SaaS applications.
Security and Compliance Blind Spots: Securing multiple SaaS products without a dedicated console leaves teams vulnerable to breaches and compliance issues due to decentralized monitoring.
Cost Chaos and Overspending: Managing multiple SaaS subscriptions without consolidation leads to overspending and budget strain due to lack of visibility and optimization.
Fragmented Monitoring Overload: Without a SaaS console, teams face the daunting task of juggling multiple monitoring platforms for each SaaS product. This fragmented approach leads to inefficiencies.
Incomplete Performance Picture: The absence of a unified SaaS console deprives teams of holistic insights into performance metrics across various SaaS applications.
Security and Compliance Blind Spots: Securing multiple SaaS products without a dedicated console leaves teams vulnerable to breaches and compliance issues due to decentralized monitoring.
Cost Chaos and Overspending: Managing multiple SaaS subscriptions without consolidation leads to overspending and budget strain due to lack of visibility and optimization.
Solution
Solution
A centralized control hub for seamless management of IBM product subscriptions across multiple cloud providers. Empowering users with simplified subscription oversight, efficient user and tenant management, and a dynamic Status Dashboard for real-time insights. Elevating the security with seamless Identity Provider (IDP) management.
A centralized control hub for seamless management of IBM product subscriptions across multiple cloud providers. Empowering users with simplified subscription oversight, efficient user and tenant management, and a dynamic Status Dashboard for real-time insights. Elevating the security with seamless Identity Provider (IDP) management.
Information architechture
Information architechture
Exploratory designs
Exploratory designs
Feature maping
Feature maping
Design reivew
Design reivew
I kickstarted a design review forum called DDR (Design Desk Review) a great initiative of our team, in which the whole studio joins in to discuss and critique the designs which are being worked on irrespective of the team. A friendly session to learn and share knowledge.
I kickstarted a design review forum called DDR (Design Desk Review) a great initiative of our team, in which the whole studio joins in to discuss and critique the designs which are being worked on irrespective of the team. A friendly session to learn and share knowledge.
Back to the sketch board
Back to the sketch board
This review was very crucial for the designs and the people around to understand various complications that are impacting the other products which will eventually onboard MCSP. We not only had to think about our end users but also our secondary users/ stakeholders which are IBM products themselves. Due to DDR we got a wider perspective from various products point of view. This made us reiterate the flows and think them through. As some parts of our console were to be used again by the product teams we created a Design Library which was supposed to be used by the product teams for any components needed.
This review was very crucial for the designs and the people around to understand various complications that are impacting the other products which will eventually onboard MCSP. We not only had to think about our end users but also our secondary users/ stakeholders which are IBM products themselves. Due to DDR we got a wider perspective from various products point of view. This made us reiterate the flows and think them through. As some parts of our console were to be used again by the product teams we created a Design Library which was supposed to be used by the product teams for any components needed.
Adopting a new strategy
Adopting a new strategy
The team wanted to make a SaaS offering not only to AWS but also to other hyper-scalers. This shift happened in Q4 2022. So the strategy shifted from focusing on making the software AWS compliant to a uniform flow which can be adopted by all the hyper-scalers.
This new strategy focused on adopting many more products and resulted in a Multi-Cloud approach. The change of strategy and the refurbishing of the console led to a widening of the team with more designers to work on and to collaborate. I collaborated with 15 designers, 7 Developers, 3 PMs, 1 User researcher and 1 Content designer this team was based from 7 different timezones.The strategy led product change gave rise to the name Multi Cloud Saas Platform
The team wanted to make a SaaS offering not only to AWS but also to other hyper-scalers. This shift happened in Q4 2022. So the strategy shifted from focusing on making the software AWS compliant to a uniform flow which can be adopted by all the hyper-scalers.
This new strategy focused on adopting many more products and resulted in a Multi-Cloud approach. The change of strategy and the refurbishing of the console led to a widening of the team with more designers to work on and to collaborate. I collaborated with 15 designers, 7 Developers, 3 PMs, 1 User researcher and 1 Content designer this team was based from 7 different timezones.The strategy led product change gave rise to the name Multi Cloud Saas Platform
Outcomes
Outcomes
Testimonials
Testimonials
“With IBM SaaS console development time has reduced by 50%-60%”
~ Travis Hayes
AWS Strategy Account Representative
“With IBM SaaS console development time has reduced by 50%-60%”
~ Travis Hayes
AWS Strategy Account Representative
“Without IBM SaaS console, it would have taken us over a year to launch”
~ Parisa Lotfi
Product Manager, IBM API Connect
“Without IBM SaaS console, it would have taken us over a year to launch”
~ Parisa Lotfi
Product Manager, IBM API Connect
©2024 PALASHBAKRE
GO BACK TO TOP
©2024 PALASHBAKRE
GO BACK TO TOP
©2024 PALASHBAKRE
GO BACK TO TOP