Fleet Logistics: Bridging the Physical-to-Digital Divide

Overview

As the Solo Product Designer & Solution Architect, I led an end-to-end operational overhaul for a major facility management company based in Zagreb. Working within a compact team of one Designer/Developer, two Developers, and one Business Analyst/Project Manager, my core challenge was transforming a fragmented operational "blind spot" of paper logs, physical receipts, and disconnected spreadsheets into a centralized, desktop-driven optimization engine.  

Timeframe & Delivery

Designing a workflow that could survive harsh field operations required deep immersion into the company's daily physical routines:

• Stakeholder Alignment Workshops: I conducted high-level alignment sessions with the Board of Directors to clearly define overarching business goals and pinpoint where untracked financial leaks were occurring.  

• Contextual Inquiries: I paired executive workshops with deep-dive contextual inquiries on the shop floor, shadowing daily operational heads and workers to visually map out true operational friction points.  

• On-Site Human Adoption Strategy: To bridge the digital transition, I authored a highly visual instruction manual that directly mirrored the final application layouts and conducted direct, on-site training sessions with the workforce.  

The What and Why (Operational Constraints)

The organization faced massive, untracked fleet expenditures due to a complete lack of centralized visibility and data infrastructure. However, modernizing the company introduced strict human and structural constraints:  

• The Shared-Terminal Reality: The software was built exclusively for desktop PCs, which operated as single shared terminals inside each department. Multiple workers on different shifts utilized the exact same machine and active profile, exponentially increasing the risk of coordination errors and messy data entry.  

• Low Digital Literacy: The active workforce was highly accustomed to physical clipboards, paper logs, and manual binders. Transitioning to a digital workspace introduced high user anxiety and immediate friction. The UI had to be designed defensively to absorb all user-error risks.  

• Siloed Data Chaos: Critical operational details—including insurance policies, tire tracking, damage logs, lease documents, and fuel bills—lived in completely disconnected physical folders and separate spreadsheets. Fleet managers had to manually cross-reference multiple sources just to check an individual asset's total operational cost.  

Mapping the Operational Transition: From Binders to Automated Triggers

Before structuring the interface, I visually mapped the entire E2E (End-to-End) operational chain to isolate where human bottlenecks occurred. The goal was to transform a high-friction, asynchronous manual loop into a synchronous system state.

The operational blueprint mapping the old paper-trail vulnerabilities against the new automated system triggers.

The Visual Proposal & Redesign: Asset-Centric Information Architecture

Centralizing the Asset Core Around the Vehicle

I restructured the platform's layout by positioning the physical Vehicle as the absolute "Single Source of Truth". In the redesigned layout, all peripheral operational modules—such as monthly route schedules, damage logs, maintenance tracking, leasing terms, and seasonal tire locations—were programmatically parented directly under the specific vehicle profile. This consolidated the scattered files into a single, cohesive desktop view, giving managers instant visibility into a truck's entire maintenance history.  

The Relational Data Schema Behind the UI

Designing for scalability meant ensuring that our no-code database structure could handle complex queries without performance lags. I established a strict hierarchical data logic where the "Core Asset" (Vehicle) acts as the primary parent object, utilizing dynamic junction tables to map multi-variable relations cleanly.

The logical data model showing entity relationships (Many-to-Many) configured to unify disparate spreadsheets under a single relational core.

Error-Defensive User Flows (The Damage Entry System)

To handle tasks like vehicle damage reporting, I translated physical reporting into a foolproof desktop user flow. During data entry, low-literacy users are prone to getting lost if multi-tasking is required.

To safeguard the critical process of uploading vehicle damage photos, I engineered the UI behavior in two distinct ways:  

1. Focused Navigation Strip: The main app navigation is completely hidden during the photo upload stage, locking the user's full focus onto completing the upload and preventing accidental exits.  

2. Zero-Consequence Recovery Paths: If a user accidentally closes the view, there is zero negative consequence or data loss. The system allows them to easily return to the main vehicle profile, select the specific damage entry, and retroactively upload missing photos at any point in time.  

Streamlining Data Ingestion & Fuel Tracking

To tackle the thousands of expenses locked inside paper bills and manual monthly logs, I designed a guided Data Ingestion Flow. Monthly route schedules and fuel receipt entries were broken down into simple, high-contrast guided steps. On top of this data loop, I designed a "One-Click" Reporting Engine with pre-set filter shortcuts for specific cost centers (e.g., separating Fuel costs from active Repairs). This eliminated hours of manual Excel compilation for directors and provided real-time telemetry on total fleet expenditures.  

Key Takeaways & Human-Centric Adoption

Software is Only as Valuable as its Adoption

Forcing a workforce completely dependent on paper logs to adopt a digital platform will fail if user anxiety is ignored. By pairing the desktop rollout with physical, highly visual manuals left directly next to the shared department terminals, we turned a potentially intimidating software mandate into an empowering, stress-free routine.  

Mitigating Risk Natively with Micro-Context

To ensure continuous, clean data entry without constant supervision, I integrated helpful informational (i) pointer tooltips natively onto the interface screens. These tooltips provided instant, plain-language context right where users historically struggled the most—specifically around complex fields like mileage logging and cost reporting. This defensive design execution achieved a smooth rollout with zero operational downtime.