Projects

Blogs

StartUp

Automated Information System "Garage"

Role

Product Designer

Date

2025

Duration

2 months

Overview

AIS Garage is an internal state-owned fleet management platform, not public-facing(!), designed to digitize and automate vehicle operations for 10+ different roles in government transport departments.

The system covers:
– Vehicle status tracking; 

– Digital trip sheets; 

– Maintenance management; 

– Spare parts inventory control;

– Driver status monitoring;

– Automated compliance.

The system completely eliminates paper-based workflows and speeds up processes 2x with automated reporting for government authorities.

Challenge

Design a system for 10+ user roles (ages 20-65) with radically different needs and digital literacy levels and all within just 2 months.


Spoiler: I hit major issues by the second week:)

Process

I conducted interviews with 3 dispatchers and 3 drivers to identify core pain points. And after, due to tight deadlines, I jumped straight into designing basic scenarios for key roles, but hit a crisis in the second week. While designing the 3rd role’s flow, I realized my critical mistake: no unified user flow for all 12 roles. I paused all design work to map the full ecosystem first.

Only after sorting everything out: I designed all roles, consulted with clients, and processed feedback. All feedback was accounted for as I worked to streamline the logic and eliminate redundant actions.

Process

I conducted interviews with 3 dispatchers and 3 drivers to identify core pain points. And after, due to tight deadlines, I jumped straight into designing basic scenarios for key roles, but hit a crisis in the second week. While designing the 3rd role’s flow, I realized my critical mistake: no unified user flow for all 12 roles. I paused all design work to map the full ecosystem first.

Only after sorting everything out: I designed all roles, consulted with clients, and processed feedback. All feedback was accounted for as I worked to streamline the logic and eliminate redundant actions.

Why, What and Who

Why: There is a need for an efficient system to manage the fleet, automate the tracking of vehicles, drivers, and trip logs, reduce errors, and improve transparency.


What: The goal of the system is to provide the best possible fleet management, making it simpler, faster, and more transparent.


Who: The platform is designed for fleet staff, including dispatchers, maintenance, warehouse, accounting, medical officers, drivers, and administrators, with varying levels of digital proficiency.

Screens

Next case study