---
title: "ZF SCALAR: design system to product ownership"
description: "Five roles at ZF SCALAR: building the Velocity design system, leading the UI Platform team, owning EVO Touch, now Global Product Owner for Driver Experience."
canonical: "https://mladenruzicic.com/work/zf-scalar"
last_modified: "2026-11-13"
author: "Mladen Ružičić"
language: "en"
---

# ZF SCALAR

> From individual contributor to engineering manager of the platform team, to product owner of several products.

By [Mladen Ružičić](https://mladenruzicic.com). Joined as a senior engineer on a platform migration, noticed the UI tooling was the real bottleneck, and built the proof of concept that became Velocity, the SCALAR design system. Led the team that shipped it and drove adoption across product teams, then owned EVO Touch as Global Product Owner until September 2026. Since October 2026 Global Product Owner for the Driver Experience team.

- **When**: October 2023 to now
- **Role**: Global Product Owner, Driver Experience team (previously Global Product Owner for EVO Touch, and engineering manager, UI Platform)
- **Company**: ZF SCALAR

_Public surfaces only. Employed work: role, domain and the shape of the contribution are described; private metrics, internal screenshots and system details are omitted._

## In numbers

- 50%: of 300 engineers on Velocity at handover

## Summary

I joined ZF SCALAR in October 2023 as a senior engineer and have moved upstream since: from feature work, to the technical foundation of a design system, to leading the team that built it, to owning a product. Since October 2026 I am Global Product Owner for the Driver Experience team.

## Role and scope

Five roles in three years: senior software engineer, UI platform engineer, engineering manager for the UI Platform team, Global Product Owner for EVO Touch (ZF's multi-platform application for commercial vehicle drivers) until September 2026, and now Global Product Owner for the Driver Experience team, where I work with existing customers on what their drivers need and what the law asks of them.

## Context

SCALAR is a large organisation with many product teams building on shared web technology. That structure produces a specific failure mode: every team solves the same interface problems slightly differently, and the differences compound into inconsistency for users and duplicated work for engineers.

## Problem

Arriving on a complex platform migration, the migration itself was not the hard part. The hard part was that UI development workflow and internal tooling made straightforward work slow, and inconsistently so across teams. Nobody owned it, because it was not anyone's feature.

## Decisions

I wrote up the inefficiencies concretely instead of complaining about them, with proposed developer-experience improvements attached. That got the room and the mandate to build a proof of concept.

The design system, Velocity, was built as a product rather than a library. That meant treating adoption as the actual deliverable: talking to product teams before writing components, shipping the pieces they needed next rather than the ones that were interesting to build, and accepting that a component nobody uses is a liability. Accessibility went into the primitives rather than into a checklist, because it is far cheaper there.

I stayed roughly half hands-on as lead engineer while managing the team. On a small platform team serving many consumers, distance from the code makes the prioritisation worse, not better.

## Contribution

Built the proof of concept and the technical foundation. Championed the initiative across the organisation and secured the team and the mandate to pursue it. Acted as technical lead and de facto product owner in the first phase, then as engineering manager: architecture, component API design, roadmap, cross-team communication and adoption work. Then handed it over cleanly and moved into product ownership, first for EVO Touch.

## Outcome

Velocity moved from an unofficial experiment to the go-to UI solution inside SCALAR and became the standard for new development. By the time I handed it over, about half of the 300 engineers were building with it. I have since moved off the platform project, and adoption has kept growing without me, which is the outcome you want from a platform. The clearest outcome, though, was organisational: platform work done as product work created the product-ownership roles I have held since.

## Learnings

Design systems do not fail on component quality. They fail on adoption strategy, which is a product problem wearing an engineering costume. The teams that had to migrate needed a reason that was true for them this quarter, not an argument about long-term consistency.

Developer experience is product work. It has users, a roadmap, competitors (the copy-pasted local component) and a retention problem. Framing it that way is what made it fundable.

## On the page

From individual contributor on a product team, to engineering manager of the platform team, to product owner of several products.

2023 to now · Global Product Owner, Driver Experience

- **50%** of 300 engineers on Velocity at handover
- **2023** joined

### Roles

#### Senior software engineer

Oct 2023 to Jan 2024

**What happened.** I arrived in the middle of a large platform migration. The migration was not the hard part. Everyday interface work was slow and uneven between teams, and nobody owned that.

**How I moved on.** I researched it and proposed concrete fixes. Management gave me the room to pursue them.

#### UI platform engineer

Jan to Jun 2024

**What happened.** I built the proof of concept and the foundation of Velocity, a design system the product teams could share, and made the case for it across the organisation until the team's focus moved to it.

**How I moved on.** I was its technical lead and product owner in all but name. The promotion to engineering manager followed.

#### Engineering manager, UI Platform team

Jun 2024 to May 2025

**What happened.** I led the platform team building Velocity and stayed about half hands-on. We treated adoption as the thing we delivered: about half of the 300 engineers were building with it when I handed it over.

**How I moved on.** Velocity became the default design system proposed for new work, and that opened the product owner role.

#### Global Product Owner, Multi-platform team

May 2025 to Sep 2026

**What happened.** I owned the vision, the roadmap and the delivery of EVO Touch, the app commercial-vehicle drivers work in, and kept three mobile apps in the group pulling in one direction.

**How I moved on.** EVO Touch was stable and a strong team took it over. I moved to where I fit better: several new projects that need their foundations laid and a delivery date kept.

#### Global Product Owner, Driver Experience (now)

Since Oct 2026

**What I do now.** Several new projects, where I help lay the foundations and make sure they ship on time. I work with existing customers to understand what their drivers need and what the law asks of them, and I research the sector, for example the European rules on eco-driving.

Links:

- [zf-scalar.com](https://zf-scalar.com)

### The pictures

- SCALAR, ZF's platform for truck fleets and their drivers. (Clip: The zf-scalar.com home page scrolling: trucks, a cab tablet, fleet dashboards and phone screens.) Source: zf-scalar.com, © ZF Friedrichshafen AG
- EVO Touch, the on-board computer and its driver app. I owned the product until September 2026. (Picture: The SCALAR EVO Touch card on the zf-scalar.com Connectivity page: a 7-inch tablet showing a driver's driving and service times in front of the fleet office app, beside four points: an IoT on-board computer with a touch interface, rich vehicle and driving data, a gateway between office and road, and SCALAR Cargo, ZF's driver app.) Source: zf-scalar.com, © ZF Friedrichshafen AG
- The driver app in the cab: a driver sees their own score. (Picture: The "Driver engagement and transparency" section of the ECO Performance page: a line on GDPR-aligned consent and the SCALAR Cargo App, above a photo of a phone in a windscreen mount showing a trip's details, an average score of 69% and the grade B.) Source: zf-scalar.com, © ZF Friedrichshafen AG
- ECO Performance grades every driver, trip and fleet from A to F. Driver-facing work like this is what I am on now. (Clip: The ECO Performance page on zf-scalar.com scrolling through its scoring, dashboards and driver app.) Source: zf-scalar.com, © ZF Friedrichshafen AG
- How a grade is made: seven measures of driving, one letter. (Picture: Three rows of the ECO Performance page: a blue ZF truck on a country road tagged "Fuel Consumed: Excellent A" beside the text on seven key performance indicators; a driver's graded scores for coasting, cruise control, fuel and idling above a trend chart; and a phone in a cab showing a trip's scores.) Source: zf-scalar.com, © ZF Friedrichshafen AG
- A cab screen next to the road it is used on. (Picture: The zf-scalar.com home page: "Backed by 35+ years of experience", "Built for cargo logistics" and "Powered by ZF", then two trucks on a motorway at sunset with the EVO Touch tablet in front of them, its screen showing driving-time dials, beside the heading "Everything connected, everything optimized".) Source: zf-scalar.com, © ZF Friedrichshafen AG

## Images

![The zf-scalar.com home page scrolling: trucks, a cab tablet, fleet dashboards and phone screens.](https://mladenruzicic.com/static/work/zf-scalar/home-glide-square-poster.webp)
![The SCALAR EVO Touch card on the zf-scalar.com Connectivity page: a 7-inch tablet showing a driver's driving and service times in front of the fleet office app, beside four points: an IoT on-board computer with a touch interface, rich vehicle and driving data, a gateway between office and road, and SCALAR Cargo, ZF's driver app.](https://mladenruzicic.com/static/work/zf-scalar/sq-evo-touch.webp)
![The "Driver engagement and transparency" section of the ECO Performance page: a line on GDPR-aligned consent and the SCALAR Cargo App, above a photo of a phone in a windscreen mount showing a trip's details, an average score of 69% and the grade B.](https://mladenruzicic.com/static/work/zf-scalar/sq-eco-driver-app.webp)
![The ECO Performance page on zf-scalar.com scrolling through its scoring, dashboards and driver app.](https://mladenruzicic.com/static/work/zf-scalar/eco-glide-square-poster.webp)
![Three rows of the ECO Performance page: a blue ZF truck on a country road tagged "Fuel Consumed: Excellent A" beside the text on seven key performance indicators; a driver's graded scores for coasting, cruise control, fuel and idling above a trend chart; and a phone in a cab showing a trip's scores.](https://mladenruzicic.com/static/work/zf-scalar/sq-eco-how-it-works.webp)
![The zf-scalar.com home page: "Backed by 35+ years of experience", "Built for cargo logistics" and "Powered by ZF", then two trucks on a motorway at sunset with the EVO Touch tablet in front of them, its screen showing driving-time dials, beside the heading "Everything connected, everything optimized".](https://mladenruzicic.com/static/work/zf-scalar/sq-home-cab-screen.webp)

## More case studies

- [TenderLift](https://mladenruzicic.com/work/tenderlift): Swiss public-procurement intelligence for supplier-side SMEs: find, assess and win relevant tenders.
- [studenti.rs](https://mladenruzicic.com/work/studenti-rs): Serbian student platform, running since 2008. Built it at my first job, bought it back in 2022.
- [FontAlternatives](https://mladenruzicic.com/work/fontalternatives): Find free alternatives to expensive typefaces. An experiment that grew into steady organic traffic.
- [Zarez](https://mladenruzicic.com/work/zarez): A spelling checker for Serbian, in Latin and Cyrillic.
- [Panciona](https://mladenruzicic.com/work/panciona): A white-label app for coaches, trainers and nutritionists to give to their own clients, on their own domain.
- [Shopify](https://mladenruzicic.com/work/shopify): Shop Minis from zero: mini React Native apps inside Shop.app, plus the SDK and partner ecosystem.
- [HEGIAS](https://mladenruzicic.com/work/hegias): Moving an AR/VR MVP toward production: 3D pipelines, microservices on AWS, in-app voice.
- [WolkAbout](https://mladenruzicic.com/work/wolkabout): Junior to senior in three years: Angular frontends for an IoT platform moving large volumes of live data.
- [Work he has put real time into](https://mladenruzicic.com/work)
