Zeus externo

Role: UX/UI Designer

Time Line: 30 weeks

Setting: Two designers UX/UI

Overview

Zeus began as an application designed to help a large conglomerate manage daily and occasional work activities. With over 100 customizable tools, it quickly became a vital resource for more than 150,000 employees. Recognizing its potential, the goal was set to distribute Zeus to other companies outside the conglomerate. However, one significant challenge stood in the way: the existing administrator interface wasn’t user-friendly, making it difficult for companies to customize Zeus according to their specific needs.

Problem Statement

To successfully commercialize Zeus externally, our team needed to overcome several challenges. The most pressing was the usability of the current administrator interface, which required extensive training due to its complexity. We aimed to create an intuitive onboarding process that wouldn’t require prior training, making Zeus accessible to any user. This involved redesigning existing functionalities to enhance usability based on feedback from usability tests. Additionally, we needed to introduce new functionalities that stakeholders had previously managed through the backend, ensuring the administrator could handle these tasks smoothly.

User & Audience

One of the biggest challenges was identifying the primary users of the new administrator. Since the product was targeted at various types of companies, the person making the purchase decision was unlikely to be the one using the administrator daily. After analyzing previous Zeus users and the target audience for the MVP, we concluded that the primary users would be administrative staff, particularly those in Human Resources.

Scope & Constraints

I was involved in this project for seven months, during which I handled everything from the conceptualization of the new administrator to the research and development of various modules required for the MVP. The absence of a defined business plan at the beginning led to multiple iterations throughout the project. Our task was to carefully define every element of the onboarding process to eliminate the need for user training and ensure the functionality modules within Zeus met the needs of its users.

Process & Methodology

Phase 1: Analysis of the Existing Administrator

My initial responsibility was to redesign the existing administrator, which had been used in a previous attempt to commercialize Zeus. To improve the user experience without compromising the previous development, we conducted multiple meetings to craft a balanced proposal.

Phase 2: Business Model Change
As the project progressed, the business model underwent a significant shift, which allowed us to start fresh with a proposal based on the administrator used internally within the organization. We began with an in-depth investigation of the current administrator’s issues, focusing on critical modules like “Communications” and “Tasks to Do.” This phase included interviews with current users and a benchmark analysis of other content management platforms such as Facebook Ads, Instagram, and Google.

mockuuups,-free-macbook-pro-with-female-professional.jpeg

Phase 3: Design and Development

With clear pain points and a solid design foundation, we developed the UI proposal for the new administrator, covering:

Onboarding
Configuration
Employee management
Notification center

MVP Modules:

Communications: Upload images and videos that all employees will see in the app.
Tasks to Do: Create surveys or forms for employees.
Zeus Box: Upload documents for employees to review or download within a specified time.
Mission and Vision: Access the company's mission and vision at any time.
Document Requests: Manage routine documentation requests from employees, such as employer letters.
Training: Surveys or forms that employees complete, which include a grade upon completion.
Zeus Chat: Internal company chat.

mockuuups-macbook-pro-space-gray-mockup-on-the-wooden-table.jpeg

Outcomes & Lessons Learned

Initially, my role was to provide support until a specialized team was brought in to take over the project. During this transitional period, the project went through numerous changes and adjustments, which we managed effectively to meet all deadlines. Despite the initial lack of a defined guide and the multiple shifts in business rules, we succeeded in delivering a functional product that met the stakeholders' expectations.

Outcomes:

Successful Delivery: The project was completed on time despite tight deadlines and numerous changes, meeting all the set objectives.
Significant Improvements: The redesigned administrator proved to be more intuitive and user-friendly, eliminating the need for prior training.
Stakeholder Satisfaction: The enhancements and new functionalities were well-received, demonstrating the quality and effort put into the project.

Lessons Learned:

Adaptability: Being able to quickly adjust to changes in the business model was crucial for the project’s success. This adaptability allowed us to respond effectively to new demands and deliver a high-quality product.
Effective Communication: Maintaining clear and consistent communication with stakeholders was key to aligning expectations and meeting deadlines. This ensured everyone was informed and engaged throughout the project.
Teamwork: Collaboration with other designers and mutual support were essential in overcoming the challenges we faced. The teamwork fostered an exchange of ideas that enriched the final outcome.