Joining ZF Group: Product Management Inside a Giant

My first week at ZF Group, I tried to push a change to the product roadmap. In a startup, that takes a conversation and a whiteboard. At ZF, it took a slide deck, three alignment meetings, a steering committee review, and a sign-off chain that included someone in Friedrichshafen whose title I still can’t pronounce correctly.

I’d gone from a company where I was the CEO, CTO, and occasionally the person fixing the printer, to a company with 150,000 employees that makes transmissions for half the trucks in Europe. The culture shock was real.

Why I did it

The honest answer: I was tired. Three years of running AutoPlan had drained me in ways I didn’t fully appreciate until I stopped. I wanted a salary. I wanted to not check my bank balance every morning. I wanted someone else to worry about payroll.

The strategic answer: ZF was building a new digital products division from scratch. They wanted people who could “think like a startup” inside enterprise. I’d done a startup. I’d failed at a startup. Apparently that qualified me.

The role was Senior Product Manager for a new SaaS platform targeting commercial fleet operators. I’d be building 0-to-1 inside a company that had been building gearboxes since 1915. The irony was not lost on me.

The “accidental fleet owners” insight

Here’s the thing that made the product interesting. When most people hear “fleet management,” they think of DHL or FedEx, massive operations with hundreds of trucks and dedicated logistics teams. But ZF’s aftermarket data showed something different.

The bones of 70% of commercial vehicles in Europe are owned by companies with fewer than 20 vehicles. These aren’t logistics companies. They’re plumbers. Bakers. Construction firms. Landscapers. They own vans and trucks because they need to get their people and equipment to job sites. Fleet management is not their business; it’s an inconvenience that comes with running their actual business.

I started calling them “accidental fleet owners.” They don’t have fleet managers. The person tracking vehicle maintenance is usually whoever sits nearest the filing cabinet. Their systems are a mix of Excel, sticky notes, and hoping the MOT reminder letter arrives before the deadline.

These people don’t want fleet management software. They want to not think about their vehicles at all. That distinction (between selling a tool and removing a headache) became the foundation of everything we built.

(Tangent: I spent a day riding along with a plumbing company in Stuttgart that had 11 vans. The owner, Thomas, showed me his “fleet management system.” It was a cork board with vehicle keys hanging on hooks, and a WhatsApp group where drivers reported problems. When I asked how he tracked maintenance schedules, he laughed and said “I wait until something breaks.” His annual repair costs were €47,000. He had no idea that number was roughly double what it should have been.)

The startup-inside-enterprise dance

Building a new product inside a company like ZF is a peculiar exercise. You have resources that a startup founder would weep for: engineers, data, existing customer relationships, brand credibility. But you also have constraints that would make a startup founder throw a chair.

Everything takes longer. Not because people are slow, but because the stakes are different. When ZF puts its name on a product, 150,000 employees’ reputations are attached to it. The quality bar is higher. The compliance requirements are real. The procurement process for a third-party API integration involves a security review that takes six weeks minimum.

I learned to translate between two languages: startup urgency and enterprise governance. “We need to ship this fast” becomes “we’re proposing an accelerated timeline to capture the Q3 market window.” Same energy, different vocabulary.

The trick is finding the spaces where you can move fast without triggering the antibodies. Internal tools? Ship whatever you want. Customer-facing features behind a beta flag? Surprisingly easy to get approved. Changing the pricing model? That’s a board-level conversation, don’t even try.

What I wish I’d known

The biggest adjustment wasn’t process or politics, it was feedback loops. In a startup, you ship something on Monday and you know by Wednesday if anyone cares. At ZF, the feedback loop from “feature shipped” to “customer actually using it” could be three months because the enterprise sales cycle is that long.

I compensated by building a direct line to about fifteen customers who’d agreed to weekly check-ins. My manager thought I was spending too much time on customer calls. I thought I was spending exactly the right amount. We agreed to disagree.

Eight months in, I can say this: I’m learning things about product management at scale that I couldn’t have learned any other way. My lead engineer has been patient enough to explain why things that took me ten minutes in a startup take ten days here, and our UX designer has a gift for translating enterprise complexity into screens that Thomas the plumber would actually use. The startup years taught me how to build from zero. ZF is teaching me how to build from zero when zero is surrounded by a hundred years of something.

Whether that’s a skill I’ll use inside enterprise forever or take back to the startup world, I genuinely don’t know yet. Ask me in a year.




Enjoy Reading This Article?

Here are some more articles you might like to read next:

  • Google Gemini updates: Flash 1.5, Gemma 2 and Project Astra
  • Displaying External Posts on Your al-folio Blog
  • The AI Product Factory: Using Claude Code as a Game Development Studio
  • Building a Brewery Sim in Godot with AI Pair Programming
  • Leading AI Transformation: What the Role Actually Looks Like