Why Your First Head of Product Should Be a Former Ops Lead
The Trap of the 'Technical' First PM
In the early days of any B2B SaaS startup, the temptation is to hire someone who can 'talk to the engineers.' You want a product manager who speaks code, can write Jira tickets, and understands the stack. I see this move repeatedly in Bengaluru. It is almost always a mistake.
When you are at the zero-to-one stage, your biggest hurdle isn't the architectural debt of your code. It is the friction of your process. You are trying to digitize a messy, manual workflow—like tracking fleet movement across Indian highways or managing procurement paperwork that still relies on faxes and WhatsApp. A developer-turned-PM usually wants to build features. An Ops lead wants to kill inefficiencies.
The Ops Lead Advantage
I have spent years building supply chain visibility at Intugine. We track nearly a million trips a month. If I had built our initial roadmap based solely on what was 'technically interesting' to build, we would have failed. Instead, we leaned into what was operationally broken.
An Ops lead understands the 'why' before the 'how.' They know that a button for an automated report is useless if the warehouse manager can't use it because he is doing data entry on a shaky mobile network at 3:00 AM. They do not care about elegant design; they care about survival metrics like downtime, cycle time, and data accuracy.
The most valuable product feature is often the one that removes the need for human intervention in a broken workflow.
Translating Friction into Logic
Operational leaders are essentially the translators of chaos. When a client complains that their shipments are 'always late,' a typical PM might suggest adding a tracking dashboard. An Ops-minded PM will trace the failure back to the data entry point at the gate pass, identify the bad incentive structure causing the delay, and build a validation rule that prevents the error from occurring in the first place.
They bring specific, hard-won skills to the product function:
- Edge Case Mastery: Ops people live in the edge cases. While a developer is optimizing the happy path, the Ops lead is already planning for the scenario where the server goes down, the client loses internet, and the cargo is stuck at a toll booth.
- Pragmatic Prioritization: They understand that software is just one tool in the kit. If a manual process is faster than an automated one, they won't force automation for the sake of it.
- Client Empathy: They have stood on the factory floor. They know the tone of voice of a customer who is losing money, and they design accordingly.
Hiring for the Long Run
Does this mean you should never hire an engineer as your first PM? No. It means you should prioritize the person who has spent time in the mud of your target market. If you are building for logistics, get someone who has managed a fleet. If you are building for fintech, get someone who has wrestled with reconciliation reports.
Technical debt can be refactored. Operational debt—the cost of building a product that doesn't actually solve the client's day-to-day workflow—is what kills a startup. Build the thing that works in the field, not the thing that looks good in the IDE. Your first Head of Product should be the person who understands the friction better than anyone else in the room.