Shipox DMS
Shipox provides transportation companies an all-in-one solution to track, optimise, and gain actionable insights across their entire fleet operation.
Shipox DMS
Shipox provides transportation companies an all-in-one solution to track, optimise, and gain actionable insights across their entire fleet operation.
Shipox DMS
Shipox provides transportation companies an all-in-one solution to track, optimise, and gain actionable insights across their entire fleet operation.
Shipox DMS
Shipox provides transportation companies an all-in-one solution to track, optimise, and gain actionable insights across their entire fleet operation.
Platform
Desktop (Responsive)
Team
Ali Chandwani (Product Lead)
Gurgen Osipian
Doniyor
Xujanazarov Hasan
Bekhzodkhon Makhkamov
My Role
Project Lead
UX Design
Design System
Overview
Shipox, a B2B SaaS platform, was designed to help businesses in the logistics industry optimize their operations and fleet management. However, when Zip24 acquired Shipox, they found a platform that was poorly built and fragmented. The system lacked integration between its key components: tracking, routing, maintenance, and order management. This fragmentation resulted in significant problems for Shipox's customers, including poor visibility into their operations and inefficient utilization of their resources. The main issues were data silos, lack of visibility, manual work, limited optimization, and difficulty extracting insights.
A transformation of platform into a more unified and intelligent SaaS platform was required. The goal was to create a solution that could optimize end-to-end fleet management while simultaneously improving existing features, simplifying the user interface, and optimizing workflows. This revamped platform would address the current issues and provide customers with a powerful tool to streamline their logistics operations effectively.
Platform
Desktop (Responsive)
Team
Ali Chandwani (Product Lead)
Gurgen Osipian
Doniyor
Xujanazarov Hasan
Bekhzodkhon Makhkamov
My Role
Project Lead
UX Design
Design System
Overview
Shipox, a B2B SaaS platform, was designed to help businesses in the logistics industry optimize their operations and fleet management. However, when Zip24 acquired Shipox, they found a platform that was poorly built and fragmented. The system lacked integration between its key components: tracking, routing, maintenance, and order management. This fragmentation resulted in significant problems for Shipox's customers, including poor visibility into their operations and inefficient utilization of their resources. The main issues were data silos, lack of visibility, manual work, limited optimization, and difficulty extracting insights.
A transformation of platform into a more unified and intelligent SaaS platform was required. The goal was to create a solution that could optimize end-to-end fleet management while simultaneously improving existing features, simplifying the user interface, and optimizing workflows. This revamped platform would address the current issues and provide customers with a powerful tool to streamline their logistics operations effectively.
Platform
Desktop (Responsive)
Team
Ali Chandwani (Product Lead)
Gurgen Osipian
Doniyor
Xujanazarov Hasan
Bekhzodkhon Makhkamov
My Role
Project Lead
UX Design
Design System
Overview
Shipox, a B2B SaaS platform, was designed to help businesses in the logistics industry optimize their operations and fleet management. However, when Zip24 acquired Shipox, they found a platform that was poorly built and fragmented. The system lacked integration between its key components: tracking, routing, maintenance, and order management. This fragmentation resulted in significant problems for Shipox's customers, including poor visibility into their operations and inefficient utilization of their resources. The main issues were data silos, lack of visibility, manual work, limited optimization, and difficulty extracting insights.
A transformation of platform into a more unified and intelligent SaaS platform was required. The goal was to create a solution that could optimize end-to-end fleet management while simultaneously improving existing features, simplifying the user interface, and optimizing workflows. This revamped platform would address the current issues and provide customers with a powerful tool to streamline their logistics operations effectively.
Platform
Desktop (Responsive)
Team
Ali Chandwani (Product Lead)
Gurgen Osipian
Doniyor
Xujanazarov Hasan
Bekhzodkhon Makhkamov
My Role
Project Lead
UX Design
Design System
Overview
Shipox, a B2B SaaS platform, was designed to help businesses in the logistics industry optimize their operations and fleet management. However, when Zip24 acquired Shipox, they found a platform that was poorly built and fragmented. The system lacked integration between its key components: tracking, routing, maintenance, and order management. This fragmentation resulted in significant problems for Shipox's customers, including poor visibility into their operations and inefficient utilization of their resources. The main issues were data silos, lack of visibility, manual work, limited optimization, and difficulty extracting insights.
A transformation of platform into a more unified and intelligent SaaS platform was required. The goal was to create a solution that could optimize end-to-end fleet management while simultaneously improving existing features, simplifying the user interface, and optimizing workflows. This revamped platform would address the current issues and provide customers with a powerful tool to streamline their logistics operations effectively.
DISCOVERING
Challenge
Our challenge was to transform the existing fragmented Shipox platform into an integrated, intelligent SaaS solution that provides complete fleet visibility and optimized end-to-end processes.
Constraints
We faced the constraint of not having access to any end users of Shipox. Instead, we relied on the existing product itself and stakeholder input from the product and engineering teams to understand the capabilities and shortcomings of the platform.
Understanding the landscape
In the initial phase, my team and I studied other fleet management software and SaaS platforms. We analyzed direct competitors and similar solutions, learning about their features and how they differentiate themselves. This provided valuable insights.
Additionally, we spent time analyzing Shipox's existing user reviews, feedback, and issues logged through the support and ticketing systems. Reading direct user feedback helped us understand what customers liked or disliked about the platform and the common issues faced across the board.
DISCOVERING
Challenge
Our challenge was to transform the existing fragmented Shipox platform into an integrated, intelligent SaaS solution that provides complete fleet visibility and optimized end-to-end processes.
Constraints
We faced the constraint of not having access to any end users of Shipox. Instead, we relied on the existing product itself and stakeholder input from the product and engineering teams to understand the capabilities and shortcomings of the platform.
Understanding the landscape
In the initial phase, my team and I studied other fleet management software and SaaS platforms. We analyzed direct competitors and similar solutions, learning about their features and how they differentiate themselves. This provided valuable insights.
Additionally, we spent time analyzing Shipox's existing user reviews, feedback, and issues logged through the support and ticketing systems. Reading direct user feedback helped us understand what customers liked or disliked about the platform and the common issues faced across the board.
DISCOVERING
Challenge
Our challenge was to transform the existing fragmented Shipox platform into an integrated, intelligent SaaS solution that provides complete fleet visibility and optimized end-to-end processes.
Constraints
We faced the constraint of not having access to any end users of Shipox. Instead, we relied on the existing product itself and stakeholder input from the product and engineering teams to understand the capabilities and shortcomings of the platform.
Understanding the landscape
In the initial phase, my team and I studied other fleet management software and SaaS platforms. We analyzed direct competitors and similar solutions, learning about their features and how they differentiate themselves. This provided valuable insights.
Additionally, we spent time analyzing Shipox's existing user reviews, feedback, and issues logged through the support and ticketing systems. Reading direct user feedback helped us understand what customers liked or disliked about the platform and the common issues faced across the board.
DISCOVERING
Challenge
Our challenge was to transform the existing fragmented Shipox platform into an integrated, intelligent SaaS solution that provides complete fleet visibility and optimized end-to-end processes.
Constraints
We faced the constraint of not having access to any end users of Shipox. Instead, we relied on the existing product itself and stakeholder input from the product and engineering teams to understand the capabilities and shortcomings of the platform.
Understanding the landscape
In the initial phase, my team and I studied other fleet management software and SaaS platforms. We analyzed direct competitors and similar solutions, learning about their features and how they differentiate themselves. This provided valuable insights.
Additionally, we spent time analyzing Shipox's existing user reviews, feedback, and issues logged through the support and ticketing systems. Reading direct user feedback helped us understand what customers liked or disliked about the platform and the common issues faced across the board.
DEFINING
How might we help logistics companies operate their vehicle fleets more efficiently to deliver goods and services on time?
Target Audience
Primary Audience
Secondary Audience
Delivery Managers and Drivers
Supply Chain Managers and Logistics Startups
User Interviews
We interviewed drivers and logistics companies who currently use delivery tracking apps to understand their experience and pain points. The interviews revealed that proactive notifications and ETAs are highly valued. Users mentioned frustration over vague ETAs or lack of status updates during delays. Most said they may not constantly track orders, but timely alerts on potential problems or delays allow them to proactively inform customers or adjust plans. There was a clear opportunity to improve user satisfaction by providing more predictive insights and notifications There was a clear opportunity to improve user satisfaction by providing more predictive insights and notifications about delivery changes.
Amanda
29, Fleet Manager
Houston, TX
"Communication bottlenecks with drivers and unexpected breakdowns cause frustrating delivery delays and operational inefficiencies."
About
She manages dispatch and scheduling for a fleet of delivery drivers at a Houston logistics company offering same-day delivery services. Though only 5 years into her career, Amanda quickly demonstrated sharp problem-solving abilities and now oversees coordination for over 50 drivers making deliveries across Texas.
Frustrations
Communication breakdowns between Amanda and drivers causes delivery delays
Inability to accurately predict traffic impacts, and a lack of optimization efforts around driver routing and responsiveness.
Goals
Customizable role-based dashboard visibility
Native communication workflows between drivers and managers
Automated documentation and proof of delivery
Amanda
29, Fleet Manager
Houston, TX
"Communication bottlenecks with drivers and unexpected breakdowns cause frustrating delivery delays and operational inefficiencies."
About
She manages dispatch and scheduling for a fleet of delivery drivers at a Houston logistics company offering same-day delivery services. Though only 5 years into her career, Amanda quickly demonstrated sharp problem-solving abilities and now oversees coordination for over 50 drivers making deliveries across Texas.
Frustrations
Communication breakdowns between Amanda and drivers causes delivery delays
Inability to accurately predict traffic impacts, and a lack of optimization efforts around driver routing and responsiveness.
Goals
Customizable role-based dashboard visibility
Native communication workflows between drivers and managers
Automated documentation and proof of delivery
User Personas
We developed personas representing a driver, an operations manager, and a startup founder to understand the varying needs users have for a delivery management application. We identified a common need for reliable efficiency through predictive insights that provide advanced warnings on delivery delays or changes. Accurate real-time coordination reduces frustrations around uncertainty for all users.
Information Architecture
In collaboration with stakeholders, we generated the information architecture based on the outlined features identified through PRD (Product Requirements Document) and MoSCoW (Must have, Should have, Could have, Won't have) prioritization. These defined flows mapped out the various screens and functionalities that would require wireframing. This helped us group the features and also think of the different ways in which we could improve the overall experience and usability.
Wireframes
Over multiple iterations, from paper to digital, we created wireframes for each flow. These acted as a discussion point for several review sessions with the stakeholders. Once we had achieved clarity on our flows, we started working on the final hi-fi flow and would rotate the screens amongst ourselves and review them collectively. Since each person was working on a different flow and the teams were working remotely, we first created a design system to ensure that there was consistency amongst all the different screens.
DEFINING
How might we help logistics companies operate their vehicle fleets more efficiently to deliver goods and services on time?
Target Audience
Primary Audience
Secondary Audience
Delivery Managers and Drivers
Supply Chain Managers and Logistics Startups
User Interviews
We interviewed drivers and logistics companies who currently use delivery tracking apps to understand their experience and pain points. The interviews revealed that proactive notifications and ETAs are highly valued. Users mentioned frustration over vague ETAs or lack of status updates during delays. Most said they may not constantly track orders, but timely alerts on potential problems or delays allow them to proactively inform customers or adjust plans. There was a clear opportunity to improve user satisfaction by providing more predictive insights and notifications There was a clear opportunity to improve user satisfaction by providing more predictive insights and notifications about delivery changes.
Amanda
29, Fleet Manager
Houston, TX
"Communication bottlenecks with drivers and unexpected breakdowns cause frustrating delivery delays and operational inefficiencies."
About
She manages dispatch and scheduling for a fleet of delivery drivers at a Houston logistics company offering same-day delivery services. Though only 5 years into her career, Amanda quickly demonstrated sharp problem-solving abilities and now oversees coordination for over 50 drivers making deliveries across Texas.
Frustrations
Communication breakdowns between Amanda and drivers causes delivery delays
Inability to accurately predict traffic impacts, and a lack of optimization efforts around driver routing and responsiveness.
Goals
Customizable role-based dashboard visibility
Native communication workflows between drivers and managers
Automated documentation and proof of delivery
Amanda
29, Fleet Manager
Houston, TX
"Communication bottlenecks with drivers and unexpected breakdowns cause frustrating delivery delays and operational inefficiencies."
About
She manages dispatch and scheduling for a fleet of delivery drivers at a Houston logistics company offering same-day delivery services. Though only 5 years into her career, Amanda quickly demonstrated sharp problem-solving abilities and now oversees coordination for over 50 drivers making deliveries across Texas.
Frustrations
Communication breakdowns between Amanda and drivers causes delivery delays
Inability to accurately predict traffic impacts, and a lack of optimization efforts around driver routing and responsiveness.
Goals
Customizable role-based dashboard visibility
Native communication workflows between drivers and managers
Automated documentation and proof of delivery
User Personas
We developed personas representing a driver, an operations manager, and a startup founder to understand the varying needs users have for a delivery management application. We identified a common need for reliable efficiency through predictive insights that provide advanced warnings on delivery delays or changes. Accurate real-time coordination reduces frustrations around uncertainty for all users.
Information Architecture
In collaboration with stakeholders, we generated the information architecture based on the outlined features identified through PRD (Product Requirements Document) and MoSCoW (Must have, Should have, Could have, Won't have) prioritization. These defined flows mapped out the various screens and functionalities that would require wireframing. This helped us group the features and also think of the different ways in which we could improve the overall experience and usability.
Wireframes
Over multiple iterations, from paper to digital, we created wireframes for each flow. These acted as a discussion point for several review sessions with the stakeholders. Once we had achieved clarity on our flows, we started working on the final hi-fi flow and would rotate the screens amongst ourselves and review them collectively. Since each person was working on a different flow and the teams were working remotely, we first created a design system to ensure that there was consistency amongst all the different screens.
DEFINING
How might we help logistics companies operate their vehicle fleets more efficiently to deliver goods and services on time?
Target Audience
Primary Audience
Secondary Audience
Delivery Managers and Drivers
Supply Chain Managers and Logistics Startups
User Interviews
We interviewed drivers and logistics companies who currently use delivery tracking apps to understand their experience and pain points. The interviews revealed that proactive notifications and ETAs are highly valued. Users mentioned frustration over vague ETAs or lack of status updates during delays. Most said they may not constantly track orders, but timely alerts on potential problems or delays allow them to proactively inform customers or adjust plans. There was a clear opportunity to improve user satisfaction by providing more predictive insights and notifications There was a clear opportunity to improve user satisfaction by providing more predictive insights and notifications about delivery changes.
Amanda
29, Fleet Manager
Houston, TX
"Communication bottlenecks with drivers and unexpected breakdowns cause frustrating delivery delays and operational inefficiencies."
About
She manages dispatch and scheduling for a fleet of delivery drivers at a Houston logistics company offering same-day delivery services. Though only 5 years into her career, Amanda quickly demonstrated sharp problem-solving abilities and now oversees coordination for over 50 drivers making deliveries across Texas.
Frustrations
Communication breakdowns between Amanda and drivers causes delivery delays
Inability to accurately predict traffic impacts, and a lack of optimization efforts around driver routing and responsiveness.
Goals
Customizable role-based dashboard visibility
Native communication workflows between drivers and managers
Automated documentation and proof of delivery
Amanda
29, Fleet Manager
Houston, TX
"Communication bottlenecks with drivers and unexpected breakdowns cause frustrating delivery delays and operational inefficiencies."
About
She manages dispatch and scheduling for a fleet of delivery drivers at a Houston logistics company offering same-day delivery services. Though only 5 years into her career, Amanda quickly demonstrated sharp problem-solving abilities and now oversees coordination for over 50 drivers making deliveries across Texas.
Frustrations
Communication breakdowns between Amanda and drivers causes delivery delays
Inability to accurately predict traffic impacts, and a lack of optimization efforts around driver routing and responsiveness.
Goals
Customizable role-based dashboard visibility
Native communication workflows between drivers and managers
Automated documentation and proof of delivery
User Personas
We developed personas representing a driver, an operations manager, and a startup founder to understand the varying needs users have for a delivery management application. We identified a common need for reliable efficiency through predictive insights that provide advanced warnings on delivery delays or changes. Accurate real-time coordination reduces frustrations around uncertainty for all users.
Information Architecture
In collaboration with stakeholders, we generated the information architecture based on the outlined features identified through PRD (Product Requirements Document) and MoSCoW (Must have, Should have, Could have, Won't have) prioritization. These defined flows mapped out the various screens and functionalities that would require wireframing. This helped us group the features and also think of the different ways in which we could improve the overall experience and usability.
Wireframes
Over multiple iterations, from paper to digital, we created wireframes for each flow. These acted as a discussion point for several review sessions with the stakeholders. Once we had achieved clarity on our flows, we started working on the final hi-fi flow and would rotate the screens amongst ourselves and review them collectively. Since each person was working on a different flow and the teams were working remotely, we first created a design system to ensure that there was consistency amongst all the different screens.
DEFINING
How might we help logistics companies operate their vehicle fleets more efficiently to deliver goods and services on time?
Target Audience
Primary Audience
Secondary Audience
Delivery Managers and Drivers
Supply Chain Managers and Logistics Startups
User Interviews
We interviewed drivers and logistics companies who currently use delivery tracking apps to understand their experience and pain points. The interviews revealed that proactive notifications and ETAs are highly valued. Users mentioned frustration over vague ETAs or lack of status updates during delays. Most said they may not constantly track orders, but timely alerts on potential problems or delays allow them to proactively inform customers or adjust plans. There was a clear opportunity to improve user satisfaction by providing more predictive insights and notifications There was a clear opportunity to improve user satisfaction by providing more predictive insights and notifications about delivery changes.
Amanda
29, Fleet Manager
Houston, TX
"Communication bottlenecks with drivers and unexpected breakdowns cause frustrating delivery delays and operational inefficiencies."
About
She manages dispatch and scheduling for a fleet of delivery drivers at a Houston logistics company offering same-day delivery services. Though only 5 years into her career, Amanda quickly demonstrated sharp problem-solving abilities and now oversees coordination for over 50 drivers making deliveries across Texas.
Frustrations
Communication breakdowns between Amanda and drivers causes delivery delays
Inability to accurately predict traffic impacts, and a lack of optimization efforts around driver routing and responsiveness.
Goals
Customizable role-based dashboard visibility
Native communication workflows between drivers and managers
Automated documentation and proof of delivery
Amanda
29, Fleet Manager
Houston, TX
"Communication bottlenecks with drivers and unexpected breakdowns cause frustrating delivery delays and operational inefficiencies."
About
She manages dispatch and scheduling for a fleet of delivery drivers at a Houston logistics company offering same-day delivery services. Though only 5 years into her career, Amanda quickly demonstrated sharp problem-solving abilities and now oversees coordination for over 50 drivers making deliveries across Texas.
Frustrations
Communication breakdowns between Amanda and drivers causes delivery delays
Inability to accurately predict traffic impacts, and a lack of optimization efforts around driver routing and responsiveness.
Goals
Customizable role-based dashboard visibility
Native communication workflows between drivers and managers
Automated documentation and proof of delivery
User Personas
We developed personas representing a driver, an operations manager, and a startup founder to understand the varying needs users have for a delivery management application. We identified a common need for reliable efficiency through predictive insights that provide advanced warnings on delivery delays or changes. Accurate real-time coordination reduces frustrations around uncertainty for all users.
Information Architecture
In collaboration with stakeholders, we generated the information architecture based on the outlined features identified through PRD (Product Requirements Document) and MoSCoW (Must have, Should have, Could have, Won't have) prioritization. These defined flows mapped out the various screens and functionalities that would require wireframing. This helped us group the features and also think of the different ways in which we could improve the overall experience and usability.
Wireframes
Over multiple iterations, from paper to digital, we created wireframes for each flow. These acted as a discussion point for several review sessions with the stakeholders. Once we had achieved clarity on our flows, we started working on the final hi-fi flow and would rotate the screens amongst ourselves and review them collectively. Since each person was working on a different flow and the teams were working remotely, we first created a design system to ensure that there was consistency amongst all the different screens.
DESIGNING
Design System
The aim with the design system was to keep it modern, minimal, and functional. The color palette was derived based on the product's positioning with the primary target audience being managers and drivers, so a balanced palette was created utilizing solids and very minimalistic gradients. The typefaces were chosen based on readability and approachability of the content, as the intention was for the text to seem friendly and trustworthy. An icon set from Iconly was used, as it was felt to be best in line with the positioning of the app to support the visual language.
Roboto
0123456789 !@#$%^&*()_+
abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
DESIGNING
Design System
The aim with the design system was to keep it modern, minimal, and functional. The color palette was derived based on the product's positioning with the primary target audience being managers and drivers, so a balanced palette was created utilizing solids and very minimalistic gradients. The typefaces were chosen based on readability and approachability of the content, as the intention was for the text to seem friendly and trustworthy. An icon set from Iconly was used, as it was felt to be best in line with the positioning of the app to support the visual language.
Roboto
0123456789 !@#$%^&*()_+
abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
DESIGNING
Design System
The aim with the design system was to keep it modern, minimal, and functional. The color palette was derived based on the product's positioning with the primary target audience being managers and drivers, so a balanced palette was created utilizing solids and very minimalistic gradients. The typefaces were chosen based on readability and approachability of the content, as the intention was for the text to seem friendly and trustworthy. An icon set from Iconly was used, as it was felt to be best in line with the positioning of the app to support the visual language.
Roboto
0123456789 !@#$%^&*()_+
abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
DESIGNING
Design System
The aim with the design system was to keep it modern, minimal, and functional. The color palette was derived based on the product's positioning with the primary target audience being managers and drivers, so a balanced palette was created utilizing solids and very minimalistic gradients. The typefaces were chosen based on readability and approachability of the content, as the intention was for the text to seem friendly and trustworthy. An icon set from Iconly was used, as it was felt to be best in line with the positioning of the app to support the visual language.
Roboto
0123456789 !@#$%^&*()_+
abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
REFLECTION
Getting User Input
Getting user input was a significant challenge. The platform was not organized, lacked real data about existing users, and the main input came from stakeholders. Based on this, we first made a Product Requirements Document listing all the features they wanted. My team and I worked hard to explain the importance of research and insights to inform product decisions, and we were able to create a better final product.
Careful Planning
The deadlines were tight, and the stakeholders had high demands. To make sure my team's efforts were well-used, I made and closely followed a Project Plan. It helped me get back on track when timelines changed and allowed my team to successfully deliver the project on time.
Building a Strong Team
As I had recently joined the team and we were working remotely, building a strong team required adjusting and planning. Understanding each person's strengths and interests was the first thing I did. I tried my best to create an open and safe environment for my team, and I wanted them to be excited and challenged throughout so we could be proud of the outcome and celebrate together when finished.
REFLECTION
Getting User Input
Getting user input was a significant challenge. The platform was not organized, lacked real data about existing users, and the main input came from stakeholders. Based on this, we first made a Product Requirements Document listing all the features they wanted. My team and I worked hard to explain the importance of research and insights to inform product decisions, and we were able to create a better final product.
Careful Planning
The deadlines were tight, and the stakeholders had high demands. To make sure my team's efforts were well-used, I made and closely followed a Project Plan. It helped me get back on track when timelines changed and allowed my team to successfully deliver the project on time.
Building a Strong Team
As I had recently joined the team and we were working remotely, building a strong team required adjusting and planning. Understanding each person's strengths and interests was the first thing I did. I tried my best to create an open and safe environment for my team, and I wanted them to be excited and challenged throughout so we could be proud of the outcome and celebrate together when finished.
REFLECTION
Getting User Input
Getting user input was a significant challenge. The platform was not organized, lacked real data about existing users, and the main input came from stakeholders. Based on this, we first made a Product Requirements Document listing all the features they wanted. My team and I worked hard to explain the importance of research and insights to inform product decisions, and we were able to create a better final product.
Careful Planning
The deadlines were tight, and the stakeholders had high demands. To make sure my team's efforts were well-used, I made and closely followed a Project Plan. It helped me get back on track when timelines changed and allowed my team to successfully deliver the project on time.
Building a Strong Team
As I had recently joined the team and we were working remotely, building a strong team required adjusting and planning. Understanding each person's strengths and interests was the first thing I did. I tried my best to create an open and safe environment for my team, and I wanted them to be excited and challenged throughout so we could be proud of the outcome and celebrate together when finished.
REFLECTION
Getting User Input
Getting user input was a significant challenge. The platform was not organized, lacked real data about existing users, and the main input came from stakeholders. Based on this, we first made a Product Requirements Document listing all the features they wanted. My team and I worked hard to explain the importance of research and insights to inform product decisions, and we were able to create a better final product.
Careful Planning
The deadlines were tight, and the stakeholders had high demands. To make sure my team's efforts were well-used, I made and closely followed a Project Plan. It helped me get back on track when timelines changed and allowed my team to successfully deliver the project on time.
Building a Strong Team
As I had recently joined the team and we were working remotely, building a strong team required adjusting and planning. Understanding each person's strengths and interests was the first thing I did. I tried my best to create an open and safe environment for my team, and I wanted them to be excited and challenged throughout so we could be proud of the outcome and celebrate together when finished.
