Work

About

Approach

Resume

Let's Connect

Work

About

Approach

Resume

Let's Connect

SpeedCloud

Cloud servicing portal to manage all the resources at one place

Beta Published

New

SpeedCloud

Cloud servicing portal to manage all the resources at one place

Beta Published

New

SpeedCloud

Cloud servicing portal to manage all the resources at one place

Beta Published

New

SpeedCloud

Cloud servicing portal to manage all the resources at one place

Beta Published

New

Overview

Overview

Overview

Empowering Indian businesses with secure and truly sovereign cloud

Empowering Indian businesses with secure and truly sovereign cloud

Empowering Indian businesses with secure and truly sovereign cloud

Empowering Indian businesses with secure and truly sovereign cloud

In today’s digital age, data privacy is more important than ever, not just for companies but for entire nation. In India’s growing market, many SaaS companies and digital businesses still rely on foreign cloud providers, resulting in sensitive data often leaving our borders. This is where SpeedCloud steps in, offering Indian businesses a secure, truly sovereign cloud solution that ensures data stays safely within the country.

In today’s digital age, data privacy is more important than ever, not just for companies but for entire nation. In India’s growing market, many SaaS companies and digital businesses still rely on foreign cloud providers, resulting in sensitive data often leaving our borders. This is where SpeedCloud steps in, offering Indian businesses a secure, truly sovereign cloud solution that ensures data stays safely within the country.

In today’s digital age, data privacy is more important than ever, not just for companies but for entire nation. In India’s growing market, many SaaS companies and digital businesses still rely on foreign cloud providers, resulting in sensitive data often leaving our borders. This is where SpeedCloud steps in, offering Indian businesses a secure, truly sovereign cloud solution that ensures data stays safely within the country.

In March 2024, I was given an exciting challenge to design a self-service portal from scratch. The goal was to simplify cloud service usage for customers and drive the company's growth.

In March 2024, I was given an exciting challenge to design a self-service portal from scratch. The goal was to simplify cloud service usage for customers and drive the company's growth.

In March 2024, I was given an exciting challenge to design a self-service portal from scratch. The goal was to simplify cloud service usage for customers and drive the company's growth.

Role

Product Designer

Team

Mohit Shrivastava

Platform

Desktop

Time

24 working days

highlights

highlights

highlights

Glimpses from the project

Glimpses from the project

Glimpses from the project

Glimpses from the project

Context

Context

Context

How it started

How it started

How it started

How it started

The organization is currently providing cloud services to over 900 customers. However, all cloud servers and resources are managed internally, with a dedicated Customer Lifecycle Management (CLM) person assigned to each client. This approach is labor-intensive and requires significant manpower. To scale the business, the company needed a platform that would allow customers to onboard, set up servers, and manage resources independently. This is where we were tasked with delivering a solution.

The organization is currently providing cloud services to over 900 customers. However, all cloud servers and resources are managed internally, with a dedicated Customer Lifecycle Management (CLM) person assigned to each client. This approach is labor-intensive and requires significant manpower. To scale the business, the company needed a platform that would allow customers to onboard, set up servers, and manage resources independently. This is where we were tasked with delivering a solution.

The organization is currently providing cloud services to over 900 customers. However, all cloud servers and resources are managed internally, with a dedicated Customer Lifecycle Management (CLM) person assigned to each client. This approach is labor-intensive and requires significant manpower. To scale the business, the company needed a platform that would allow customers to onboard, set up servers, and manage resources independently. This is where we were tasked with delivering a solution.

Project Goal

Project Goal

Project Goal

Build an MVP platform that streamlines cloud resource and service management, enabling businesses to efficiently monitor, control, and manage their cloud operations from a single centralized hub.

Build an MVP platform that streamlines cloud resource and service management, enabling businesses to efficiently monitor, control, and manage their cloud operations from a single centralized hub.

Build an MVP platform that streamlines cloud resource and service management, enabling businesses to efficiently monitor, control, and manage their cloud operations from a single centralized hub.

The platform should be flexible enough to cater to different target audiences like individual users and enterprise users, by providing customized access and control based on their specific needs, ensuring a personalized and seamless cloud management experience.

The platform should be flexible enough to cater to different target audiences like individual users and enterprise users, by providing customized access and control based on their specific needs, ensuring a personalized and seamless cloud management experience.

The platform should be flexible enough to cater to different target audiences like individual users and enterprise users, by providing customized access and control based on their specific needs, ensuring a personalized and seamless cloud management experience.

challenge

challenge

challenge

How might we

How might we

How might we

How might we

Create a cloud service portal that offers seamless onboarding for different target audiences and user types, each with distinct access controls?

Create a cloud service portal that offers seamless onboarding for different target audiences and user types, each with distinct access controls?

Create a cloud service portal that offers seamless onboarding for different target audiences and user types, each with distinct access controls?

Design a dashboard that includes all necessary features with an intuitive interface to ensure ease of use for users?

Design a dashboard that includes all necessary features with an intuitive interface to ensure ease of use for users?

Design a dashboard that includes all necessary features with an intuitive interface to ensure ease of use for users?

Ensure the design is scalable, allowing future features to be integrated seamlessly without requiring major changes to the existing design?

Ensure the design is scalable, allowing future features to be integrated seamlessly without requiring major changes to the existing design?

Ensure the design is scalable, allowing future features to be integrated seamlessly without requiring major changes to the existing design?

process

process

process

This is how we arrived at the solution

This is how we arrived at the solution

This is how we arrived at the solution

This is how we arrived at the solution

Understanding the problem and scope of the project

Understanding the problem and scope of the project

Understanding the problem and scope of the project

During this stage, we collaborated closely with key stakeholders to gain a deeper understanding of the problem. Our goal was to achieve clarity and alignment around a common objective for the MVP. Through conversations and research we were able to identify core priorities and determine what features made the most sense to build at this stage. This process also provided us with a clear understanding of different user roles and their specific use cases, ensuring the platform would cater to diverse user needs effectively.

During this stage, we collaborated closely with key stakeholders to gain a deeper understanding of the problem. Our goal was to achieve clarity and alignment around a common objective for the MVP. Through conversations and research we were able to identify core priorities and determine what features made the most sense to build at this stage. This process also provided us with a clear understanding of different user roles and their specific use cases, ensuring the platform would cater to diverse user needs effectively.

During this stage, we collaborated closely with key stakeholders to gain a deeper understanding of the problem. Our goal was to achieve clarity and alignment around a common objective for the MVP. Through conversations and research we were able to identify core priorities and determine what features made the most sense to build at this stage. This process also provided us with a clear understanding of different user roles and their specific use cases, ensuring the platform would cater to diverse user needs effectively.

With the stakeholders' deep understanding of the problem and our expertise in product design, we quickly established a clear vision and roadmap for the project. Within just 2 to 3 days, we aligned on key priorities, ensuring a focused and efficient approach for the upcoming development efforts.

With the stakeholders' deep understanding of the problem and our expertise in product design, we quickly established a clear vision and roadmap for the project. Within just 2 to 3 days, we aligned on key priorities, ensuring a focused and efficient approach for the upcoming development efforts.

With the stakeholders' deep understanding of the problem and our expertise in product design, we quickly established a clear vision and roadmap for the project. Within just 2 to 3 days, we aligned on key priorities, ensuring a focused and efficient approach for the upcoming development efforts.

Making information architecture and user flows

Making information architecture and user flows

Making information architecture and user flows

Based on our previous insights, we crafted the core structure and major user flows of the cloud portal, laying the foundation for designing its interface.

Based on our previous insights, we crafted the core structure and major user flows of the cloud portal, laying the foundation for designing its interface.

Based on our previous insights, we crafted the core structure and major user flows of the cloud portal, laying the foundation for designing its interface.

To ensure accuracy and practicality in our approach, we also conducted multiple interviews with Engineers and DevOps teams. This helped us gain a deeper understanding of backend processes, especially for highly technical flows that we were initially unfamiliar with.

To ensure accuracy and practicality in our approach, we also conducted multiple interviews with Engineers and DevOps teams. This helped us gain a deeper understanding of backend processes, especially for highly technical flows that we were initially unfamiliar with.

To ensure accuracy and practicality in our approach, we also conducted multiple interviews with Engineers and DevOps teams. This helped us gain a deeper understanding of backend processes, especially for highly technical flows that we were initially unfamiliar with.

Competitor analysis

Competitor analysis

Competitor analysis

Once we had a clear understanding of the base structure and defined what needed to be built, we shifted our focus to competitive analysis. Our aim was to explore how industry leaders approached cloud management and identify ways to enhance the user experience on our platform.

Once we had a clear understanding of the base structure and defined what needed to be built, we shifted our focus to competitive analysis. Our aim was to explore how industry leaders approached cloud management and identify ways to enhance the user experience on our platform.

Once we had a clear understanding of the base structure and defined what needed to be built, we shifted our focus to competitive analysis. Our aim was to explore how industry leaders approached cloud management and identify ways to enhance the user experience on our platform.

We analyzed three major competitors, Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. The goal was to adopt familiar design patterns to ensure easy adaptability for users transitioning from these platforms while also introducing improvements that could differentiate our platform.

We analyzed three major competitors, Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. The goal was to adopt familiar design patterns to ensure easy adaptability for users transitioning from these platforms while also introducing improvements that could differentiate our platform.

We analyzed three major competitors, Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. The goal was to adopt familiar design patterns to ensure easy adaptability for users transitioning from these platforms while also introducing improvements that could differentiate our platform.

Making wireframes

Making wireframes

Making wireframes

Once we had a clear direction on designing the portal, we began creating wireframes to visualize the structure of the platform. This step helped us gain better clarity on how different components would come together and allowed us to identify any structural gaps early on.

Once we had a clear direction on designing the portal, we began creating wireframes to visualize the structure of the platform. This step helped us gain better clarity on how different components would come together and allowed us to identify any structural gaps early on.

Once we had a clear direction on designing the portal, we began creating wireframes to visualize the structure of the platform. This step helped us gain better clarity on how different components would come together and allowed us to identify any structural gaps early on.

We also review these wireframes with stakeholders to ensure alignment and gather early feedback. This helped us validate the structure before investing time in designing the final user interface, ensuring that we were moving in the right direction.

We also review these wireframes with stakeholders to ensure alignment and gather early feedback. This helped us validate the structure before investing time in designing the final user interface, ensuring that we were moving in the right direction.

We also review these wireframes with stakeholders to ensure alignment and gather early feedback. This helped us validate the structure before investing time in designing the final user interface, ensuring that we were moving in the right direction.

Designing Hi-Fi prototype

Designing Hi-Fi prototype

Designing Hi-Fi prototype

After reviewing the wireframes with stakeholders and incorporating necessary changes, we moved on to designing the Hi-Fi wireframes to give a realistic look and feel of the platform.

After reviewing the wireframes with stakeholders and incorporating necessary changes, we moved on to designing the Hi-Fi wireframes to give a realistic look and feel of the platform.

After reviewing the wireframes with stakeholders and incorporating necessary changes, we moved on to designing the Hi-Fi wireframes to give a realistic look and feel of the platform.

Simultaneously, we began building a design system to streamline the design process and ensure consistency across the platform. This helped us accelerate the design workflow, making it easier to scale the design as the platform evolved.

Simultaneously, we began building a design system to streamline the design process and ensure consistency across the platform. This helped us accelerate the design workflow, making it easier to scale the design as the platform evolved.

Simultaneously, we began building a design system to streamline the design process and ensure consistency across the platform. This helped us accelerate the design workflow, making it easier to scale the design as the platform evolved.

Review with stakeholders and get feedback

Review with stakeholders and get feedback

Review with stakeholders and get feedback

Given the limited time for the portal design, we couldn't afford to rely solely on our own hypotheses. So, simultaneously during the design process, we conducted countless interviews with stakeholders to ensure our thinking was correctly aligned with their expectations.

Given the limited time for the portal design, we couldn't afford to rely solely on our own hypotheses. So, simultaneously during the design process, we conducted countless interviews with stakeholders to ensure our thinking was correctly aligned with their expectations.

Given the limited time for the portal design, we couldn't afford to rely solely on our own hypotheses. So, simultaneously during the design process, we conducted countless interviews with stakeholders to ensure our thinking was correctly aligned with their expectations.

During these sessions, we also brainstormed potential blockers and feature implementations to ensure that our designs would seamlessly align with backend complexities.

During these sessions, we also brainstormed potential blockers and feature implementations to ensure that our designs would seamlessly align with backend complexities.

During these sessions, we also brainstormed potential blockers and feature implementations to ensure that our designs would seamlessly align with backend complexities.

Since we had no prior knowledge of the technical side, these meetings turned out to be extremely valuable in shaping the product and preventing any major roadblocks later.

Since we had no prior knowledge of the technical side, these meetings turned out to be extremely valuable in shaping the product and preventing any major roadblocks later.

Since we had no prior knowledge of the technical side, these meetings turned out to be extremely valuable in shaping the product and preventing any major roadblocks later.

Implement necessary changes based on the feedback

Implement necessary changes based on the feedback

Implement necessary changes based on the feedback

After gathering extensive feedback, we identified key improvements needed for the portal. Several new feature and flow suggestions emerged, which were initially out of scope due to time constraints. However, once we finalized the existing scope, we were asked to incorporate these additional features into the design.

After gathering extensive feedback, we identified key improvements needed for the portal. Several new feature and flow suggestions emerged, which were initially out of scope due to time constraints. However, once we finalized the existing scope, we were asked to incorporate these additional features into the design.

After gathering extensive feedback, we identified key improvements needed for the portal. Several new feature and flow suggestions emerged, which were initially out of scope due to time constraints. However, once we finalized the existing scope, we were asked to incorporate these additional features into the design.

This led to major enhancements in multiple user flows, UX refinements across the portal, and updates to various screens, ultimately making the platform more intuitive and efficient for users.

This led to major enhancements in multiple user flows, UX refinements across the portal, and updates to various screens, ultimately making the platform more intuitive and efficient for users.

This led to major enhancements in multiple user flows, UX refinements across the portal, and updates to various screens, ultimately making the platform more intuitive and efficient for users.

Output

Output

Output

Final solution proposed

Final solution proposed

Final solution proposed

Final solution proposed

Design system

Design system

Design system

Design style for dashboard

Design style for dashboard

Design style for dashboard

Design style for dashboard

decisions

decisions

decisions

Critical decisions taken during the project

Critical decisions taken during the project

Critical decisions taken during the project

Critical decisions taken during the project

Different dashboards for different types of users

Different dashboards for different types of users

Different dashboards for different types of users

As we discovered that the dashboard would cater to multiple types of users with distinct use cases, we decided to categorize users based on their access levels and responsibilities. This led us to identify two primary user groups:

As we discovered that the dashboard would cater to multiple types of users with distinct use cases, we decided to categorize users based on their access levels and responsibilities. This led us to identify two primary user groups:

As we discovered that the dashboard would cater to multiple types of users with distinct use cases, we decided to categorize users based on their access levels and responsibilities. This led us to identify two primary user groups:

  1. Org Level Users (Tenant Admin, Billing Manager) – Their primary role was to manage and monitor resources and activities at an organizational level.

  1. Org Level Users (Tenant Admin, Billing Manager) – Their primary role was to manage and monitor resources and activities at an organizational level.

  1. Org Level Users (Tenant Admin, Billing Manager) – Their primary role was to manage and monitor resources and activities at an organizational level.

  1. Project Level Users (Project Admin, Project User) – Their focus was to manage and monitor resources within specific projects.

  1. Project Level Users (Project Admin, Project User) – Their focus was to manage and monitor resources within specific projects.

  1. Project Level Users (Project Admin, Project User) – Their focus was to manage and monitor resources within specific projects.

Given the difference in features and functionalities based on these roles, we chose to design two separate dashboards tailored to their respective needs. However, we ensured that both dashboards remained interconnected, allowing Org Level Users to seamlessly manage and monitor Project Level activities without switching platforms.

Given the difference in features and functionalities based on these roles, we chose to design two separate dashboards tailored to their respective needs. However, we ensured that both dashboards remained interconnected, allowing Org Level Users to seamlessly manage and monitor Project Level activities without switching platforms.

Given the difference in features and functionalities based on these roles, we chose to design two separate dashboards tailored to their respective needs. However, we ensured that both dashboards remained interconnected, allowing Org Level Users to seamlessly manage and monitor Project Level activities without switching platforms.

Separate Instance spinning flows for Individual and Enterprise user

Separate Instance spinning flows for Individual and Enterprise user

Separate Instance spinning flows for Individual and Enterprise user

At an enterprise level, managing cloud infrastructure is more organized and complex due to multiple projects, resources, IPV, SSH Keys, and Networks spread across different locations. To maintain full control, we designed a detailed and controlled flow for enterprises.

At an enterprise level, managing cloud infrastructure is more organized and complex due to multiple projects, resources, IPV, SSH Keys, and Networks spread across different locations. To maintain full control, we designed a detailed and controlled flow for enterprises.

At an enterprise level, managing cloud infrastructure is more organized and complex due to multiple projects, resources, IPV, SSH Keys, and Networks spread across different locations. To maintain full control, we designed a detailed and controlled flow for enterprises.

For individual users, where the goal is to launch applications quickly, we introduced an express flow that allows them to spin instances within a few clicks. This helped us balance control and speed, catering to both enterprise and individual users efficiently.

For individual users, where the goal is to launch applications quickly, we introduced an express flow that allows them to spin instances within a few clicks. This helped us balance control and speed, catering to both enterprise and individual users efficiently.

For individual users, where the goal is to launch applications quickly, we introduced an express flow that allows them to spin instances within a few clicks. This helped us balance control and speed, catering to both enterprise and individual users efficiently.

By differentiating the user flows, we were able to balance control and speed, catering to the diverse needs of enterprise and individual users.

By differentiating the user flows, we were able to balance control and speed, catering to the diverse needs of enterprise and individual users.

By differentiating the user flows, we were able to balance control and speed, catering to the diverse needs of enterprise and individual users.

Creating a separate page for subscription

Creating a separate page for subscription

Creating a separate page for subscription

SpeedCloud by NxtGen is a cloud service provider, but a significant portion of its revenue comes from managed services offered as add-ons for each VM. To increase visibility and adoption, we designed a dedicated Add-ons page displaying both active and available add-ons for each VM. This ensures users are aware of their current add-on status, while also encouraging them to explore and activate additional services.

SpeedCloud by NxtGen is a cloud service provider, but a significant portion of its revenue comes from managed services offered as add-ons for each VM. To increase visibility and adoption, we designed a dedicated Add-ons page displaying both active and available add-ons for each VM. This ensures users are aware of their current add-on status, while also encouraging them to explore and activate additional services.

SpeedCloud by NxtGen is a cloud service provider, but a significant portion of its revenue comes from managed services offered as add-ons for each VM. To increase visibility and adoption, we designed a dedicated Add-ons page displaying both active and available add-ons for each VM. This ensures users are aware of their current add-on status, while also encouraging them to explore and activate additional services.

To enhance accessibility, we placed the Add-ons page in the side navigation bar, making it easily reachable for users at any time.

To enhance accessibility, we placed the Add-ons page in the side navigation bar, making it easily reachable for users at any time.

To enhance accessibility, we placed the Add-ons page in the side navigation bar, making it easily reachable for users at any time.

Adding little relief for new enterprise users

Adding little relief for new enterprise users

Adding little relief for new enterprise users

Since the manual enterprise flow involves a lengthy process where users need to buy quotas first and then set up their VDC (Virtual Data Center), we aimed to speed up the process. To achieve this, we added an info notification on top of the widgets, allowing users to quickly navigate and buy and set up their VDC in one go, reducing the overall setup time and improving the user experience.

Since the manual enterprise flow involves a lengthy process where users need to buy quotas first and then set up their VDC (Virtual Data Center), we aimed to speed up the process. To achieve this, we added an info notification on top of the widgets, allowing users to quickly navigate and buy and set up their VDC in one go, reducing the overall setup time and improving the user experience.

Since the manual enterprise flow involves a lengthy process where users need to buy quotas first and then set up their VDC (Virtual Data Center), we aimed to speed up the process. To achieve this, we added an info notification on top of the widgets, allowing users to quickly navigate and buy and set up their VDC in one go, reducing the overall setup time and improving the user experience.

Easy access of the activity log

Easy access of the activity log

Easy access of the activity log

Through discussions with stakeholders and users, we discovered that the activity log is highly important for critical users like Tenant Admins and Project Admins, as they frequently monitor resource changes and user activities.

Through discussions with stakeholders and users, we discovered that the activity log is highly important for critical users like Tenant Admins and Project Admins, as they frequently monitor resource changes and user activities.

Through discussions with stakeholders and users, we discovered that the activity log is highly important for critical users like Tenant Admins and Project Admins, as they frequently monitor resource changes and user activities.

To enhance accessibility, we integrated the activity log directly on the homepage, ensuring it dynamically adapts based on whether the user is viewing the project dashboard or the main dashboard, providing a seamless and efficient user experience.

To enhance accessibility, we integrated the activity log directly on the homepage, ensuring it dynamically adapts based on whether the user is viewing the project dashboard or the main dashboard, providing a seamless and efficient user experience.

To enhance accessibility, we integrated the activity log directly on the homepage, ensuring it dynamically adapts based on whether the user is viewing the project dashboard or the main dashboard, providing a seamless and efficient user experience.

Future scope

Future scope

Future scope

Future planning for this portal

Future planning for this portal

Future planning for this portal

Future planning for this portal

Include major features like Cluster Creation, Edit VM Resources, Build Project with AI, Manage Subscription, Network Topology, Console Access, and many more to enhance platform capabilities.

Include major features like Cluster Creation, Edit VM Resources, Build Project with AI, Manage Subscription, Network Topology, Console Access, and many more to enhance platform capabilities.

Include major features like Cluster Creation, Edit VM Resources, Build Project with AI, Manage Subscription, Network Topology, Console Access, and many more to enhance platform capabilities.

We also plan to introduce AI-driven automation to simplify resource management, along with advanced telemetry analytics for deeper business insights. Expanding integrations with CRM tools will further streamline monitoring and management.

We also plan to introduce AI-driven automation to simplify resource management, along with advanced telemetry analytics for deeper business insights. Expanding integrations with CRM tools will further streamline monitoring and management.

We also plan to introduce AI-driven automation to simplify resource management, along with advanced telemetry analytics for deeper business insights. Expanding integrations with CRM tools will further streamline monitoring and management.

Additionally, we will remain agile to accommodate potential improvements based on user feedback and evolving business needs.

Additionally, we will remain agile to accommodate potential improvements based on user feedback and evolving business needs.

Additionally, we will remain agile to accommodate potential improvements based on user feedback and evolving business needs.

Takeaways

Takeaways

Takeaways

Key learnings got from the project

Key learnings got from the project

Key learnings got from the project

Key learnings got from the project

Balancing User Needs

Balancing User Needs

Balancing User Needs

Designing for both individual and enterprise users taught me the significance of building flexible, role-based solutions that can seamlessly adapt to diverse user needs while maintaining a consistent user experience.

Designing for both individual and enterprise users taught me the significance of building flexible, role-based solutions that can seamlessly adapt to diverse user needs while maintaining a consistent user experience.

Designing for both individual and enterprise users taught me the significance of building flexible, role-based solutions that can seamlessly adapt to diverse user needs while maintaining a consistent user experience.

Overcoming Time Constraint

Overcoming Time Constraint

Overcoming Time Constraint

Smart and strategic planning from the beginning of the project played a crucial role in overcoming the tight delivery timeline, allowing us to stay aligned with goals and deliver the product on time without compromising quality.

Smart and strategic planning from the beginning of the project played a crucial role in overcoming the tight delivery timeline, allowing us to stay aligned with goals and deliver the product on time without compromising quality.

Smart and strategic planning from the beginning of the project played a crucial role in overcoming the tight delivery timeline, allowing us to stay aligned with goals and deliver the product on time without compromising quality.

Collaboration with Teams

Collaboration with Teams

Collaboration with Teams

Close collaboration with developers throughout the process helped bridge the gap between design and technical feasibility, ensuring that design decisions were practical, achievable, and easier to implement, ultimately leading to a smoother development process.

Close collaboration with developers throughout the process helped bridge the gap between design and technical feasibility, ensuring that design decisions were practical, achievable, and easier to implement, ultimately leading to a smoother development process.

Close collaboration with developers throughout the process helped bridge the gap between design and technical feasibility, ensuring that design decisions were practical, achievable, and easier to implement, ultimately leading to a smoother development process.

Designing for Scale

Designing for Scale

Designing for Scale

This project emphasized the importance of scalability, not only in building a product that can handle growing user demands but also in designing processes that can easily adapt to future enhancements and evolving business needs.

This project emphasized the importance of scalability, not only in building a product that can handle growing user demands but also in designing processes that can easily adapt to future enhancements and evolving business needs.

This project emphasized the importance of scalability, not only in building a product that can handle growing user demands but also in designing processes that can easily adapt to future enhancements and evolving business needs.

Importance of design system

Importance of design system

Importance of design system

A consistent design system ensured scalability and a seamless user experience while streamlining collaboration between designers and developers.

A consistent design system ensured scalability and a seamless user experience while streamlining collaboration between designers and developers.

A consistent design system ensured scalability and a seamless user experience while streamlining collaboration between designers and developers.

Value of Iteration

Value of Iteration

Value of Iteration

Early usability tests provided crucial insights that helped refine the design and enhance the overall user experience.

Early usability tests provided crucial insights that helped refine the design and enhance the overall user experience.

Early usability tests provided crucial insights that helped refine the design and enhance the overall user experience.

  • * Let’s connect!

  • * Let’s connect!

Feel free to drop

me an email

Works

About

Approach

suvopaul79@gmail.com

Resume

LinkedIn

Behance

© 2025 Sushavon Paul

Made with love in Framer

Feel free to drop

me an email

Works

About

Approach

suvopaul79@gmail.com

Resume

LinkedIn

Behance

© 2025 Sushavon Paul

Made with love in Framer

Feel free to drop

me an email

Works

About

Approach

suvopaul79@gmail.com

Resume

LinkedIn

Behance

© 2025 Sushavon Paul

Made with love in Framer

Feel free to drop

me an email

Works

About

Approach

suvopaul79@gmail.com

Resume

LinkedIn

Behance

© 2025 Sushavon Paul

Made with love in Framer