Customers often struggle to choose the right printer for their needs due to the wide variety of options available in the market. They need a user-friendly desktop application that guides them through the selection process based on their specific requirements.
Goal
Develop a desktop application that assists customers in choosing the most suitable printer based on their needs, preferences, and budget.
User Interview
Conducted interviews with potential users to understand their pain points and needs when it comes to buying a printer. Common issues included confusion about different printer types, specifications, and compatibility with devices.
Competitive Analysis
Analyzed existing printer selection tools and applications to identify gaps and opportunities for improvement.
Persona
Developed a persona named “Tech-Savvy Tom” who represents our target audience—a tech-savvy individual looking for a printer for both personal and professional use.
User Stories
As Ajay, I want an application that helps me understand the differences between various printer types (inkjet, laser, etc.).
As Ajay, I want to input my budget and receive printer recommendations within that range.
As Ajay, I want to compare printer specifications side by side.
Information Architecture
Created a sitemap to outline the application’s structure and navigation flow.
Wireframes
Designed wireframes for key screens, including the home screen, printer comparison page, and budget input page.
Usability Testing
Conducted usability tests with colleges within the organization and then tested with a few of my friends who are planning to purchase a printer user to gather feedback on the prototype’s design and functionality.
Learnings
As this was my first project where I tried including most of the UX process in designing the web and mobile application, there were many challenges faced
Learning to do user interviews by asking open-ended questions to gather maximum information
Convincing stakeholders the importance of the process and how it will increase productivity and decrease in re-work.
HPE OneSphere was a cloud management platform offered by Hewlett Packard Enterprise (HPE). It was designed to simplify the management of hybrid cloud environments, which typically involve a combination of on-premises infrastructure and resources hosted in public and private clouds.
What are the Goals of the App
I have worked on many features in OneSphere. But here I am showcasing the feature, onboarding Kubernetes on bare-metal. Easily onboard Kubernetes on bare-metal and manage the clusters from OneSphere.
The problem
Deploying Kubernetes on bare metal servers presents challenges related to hardware compatibility, provisioning complexity, and security, highlighting the need for streamlined solutions and expertise to ensure a successful and secure deployment. And also consider the time consumed to onboard.
The Solution
Streamline the process of attaching nodes and automate the process of creating a master node. Reduce the manual intervention
Building Persona
Task flow
Competitive Analysis
Company Name
Product Offering
Unique Value Proposition
Features
Hewlett Packard Enterprise (HPE)
HPE OneSphere (Cloud Management)
Simplified hybrid cloud management and Kubernetes orchestration.
Multi-cloud management
Unified interface
Cost management
Resource provisioning
Analytics and insights
Security and compliance
VMware
VMware Tanzu (Kubernetes Platform)
Comprehensive Kubernetes management and development platform.
Kubernetes cluster provisioning
Application deployment and scaling
Monitoring and logging
CI/CD integration
Multi-cloud support
Red Hat (now part of IBM)
OpenShift (Kubernetes Platform)
OpenShift (Kubernetes Platform)
Kubernetes orchestration
Developer tools and APIs
Security and compliance
CI/CD pipeline integration
Extensive partner ecosystem
Google Cloud
Google Kubernetes Engine (GKE)
Managed Kubernetes service on Google Cloud Platform.
Automated cluster management
Seamless integration with GCP services
Scalability and high availability
Kubernetes Engine Marketplace
Microsoft
Azure Kubernetes Service (AKS)
Managed Kubernetes container orchestration service on Azure.
Integrated with Azure DevOps
Monitoring and diagnostics
Enterprise-grade security
Serverless Kubernetes with Azure Functions
Amazon Web Services (AWS)
Amazon Elastic Kubernetes Service (EKS)
Managed Kubernetes service on AWS.
Automatic updates and patching
Integration with AWS services
Scalable and highly available
AWS Marketplace for Kubernetes applications
Wire Frames
User Testing
Conducted multiple rounds of user testing
First, we did preference testing to understand which design is better than the other designs
Made some modifications based on the feedback received from stakeholders
Conducted moderated user testing on the new design to understand what can be made better and whether users are able to relate to the work they perform
Finally we developed both the options and did a AB testing.
Following are some of the findings from these tests
0
Users tested
0
Users felt its the easiest method
0
Users unable to find which nodes were master nodes
0
mintes to complete the task
Few Verbatiums from the test
Attaching nodes was relatively quick and easy. I had no issues with figuring out how to go about doing this.
I believe that this would be the absolute easiest way to attach nodes, It is quicker and much more efficient than the previous method.
I believe all three nodes were attached as a master node to the cluster. I could be wrong but this is what I can recall
Even though the process was easy for the users, 2 users were unable to understand which node was attached as the master node. So we went back to the drawing board and made some changes to address that and tested it again.