Most product leaders inherit a team, a process, and an operating model. They optimize what exists. The harder assignment is building the product organization from scratch inside a company that has been shipping products without one.

I have done this three times. Each time, the company had engineering, sales, and operations. Each time, the company shipped products to customers. Each time, the product operating model was either broken but established, truly nonexistent, or established for legacy products without an operating model for what came next. The common thread: no structured way to decide what to build, and no shared language for discussing tradeoffs.

The pattern that follows is a field-tested operating model built across a global construction technology company shipping to 100+ export-controlled countries, an enterprise data and telematics subsidiary of $44B annual revenue Continental AG, and a $600M manufacturer (Rehrig Pacific Company) serving Fortune 500 accounts across 23 industries.

What do you build first?

The operating model.

The most common mistake I see new product leaders make is hiring before they have defined how the organization will make decisions. They staff up, then discover the company has no product roadmap governance, no intake process for feature requests, no framework for investment prioritization, and no shared language for discussing tradeoffs.

At the construction technology company, I inherited a two-year engineering change order backlog, $7M in accumulated technical debt, and a $40M program that had never been evaluated against market reality. The first thing I established was the product operating model: a prioritization framework, a planning cadence, and the due diligence process that allowed the organization to evaluate its existing commitments with data. That operating model produced the analysis that led to the $40M kill and capital reallocation decision. It also produced the ECO remediation: I hired a program manager and reduced the backlog from two years to two months. The operating model came before any product headcount because the organization needed the decision-making infrastructure before it needed more people making decisions.

Build the decision-making framework first. Who has input. Who has veto. How priorities are ranked. How tradeoffs are communicated. What the cadence looks like: weekly, monthly, quarterly. What artifacts the organization produces and who consumes them. This operating model is the product the product leader ships to the rest of the company. It must work before the team scales.

How do you sequence the team build?

In a company with no product function, the first hire depends on which capability gap is causing the most downstream damage.

At the company, the highest-damage gap was UX. The products worked, but the setup experience took 60 minutes per unit for field operators working underground in GPS-denied environments. Support costs were climbing. Skilled labor shortages meant fewer experienced operators entering the market. I promoted a UX design lead from within the organization and established the user experience design function from zero, including a human-centered design system. We redesigned the setup workflow and cut time-to-value 68%, from 60 minutes to 15 minutes. Support call volume followed the same curve.

At Rehrig Pacific Company, the gap was digital and technology customer intelligence. The company had deep structured understanding of its durable product customers across 23 industries, but no intelligence on digital supply chain needs, modern cloud technology at the edge, or how field operators actually interacted with technology in their daily workflows. The first investment was field research: I personally conducted 41 enterprise customer audits spanning 96,000+ miles annually across agriculture, pharmaceutical, petroleum, classified transport, and logistics. That intelligence layer drove every subsequent digital product investment decision. I improved product initiative accuracy 37% and reduced time-to-value 18% by connecting field observations directly to development priorities.

The sequence is: diagnose the highest-damage gap, hire for that capability, prove the value, then expand. Not the reverse.

What functions belong inside the product organization?

In a mature product org, five functions interact daily: Product Management, UX Design, Business Intelligence, Product Operations, and Go-to-Market. Engineering is not always inside the product organization, but when it is not, it must be treated as if it is. The product operating model fails the moment product and engineering operate as separate entities with separate priorities. In a startup or turnaround, you build these functions over time. The order matters.

Product Management is the core. Strategy, roadmap, prioritization, customer requirements, competitive intelligence. This exists from day one, even if it is just the product leader doing the work personally. At the company, I completely reset the existing Product Management function that had been operating without a structured methodology.

UX Design is the first expansion. In B2B companies selling to field operators, factory workers, and technical users, the UX gap is almost always the largest drag on adoption, retention, and support cost. At the company, I founded the UX Design function from scratch, establishing a named human-centered design system that standardized interaction patterns across the full product portfolio. The system reduced onboarding friction for products shipping to 100+ countries with 40+ regional product localizations.

Business Intelligence is the second expansion. You cannot make data-driven product decisions if no one owns the data. BI builds the dashboards, defines the metrics, and creates the feedback loop between product usage and product investment. I founded BI from scratch at the company because the company had no structured analytics connecting product telemetry to business outcomes.

Product Operations is the third expansion. Process documentation, tooling, release management, cross-functional coordination. Ops becomes essential when the team exceeds 10 people or the product ships to more than 5 markets. Before that, the product leader handles it. I founded Product Ops at the company as the third function from scratch.

Go-to-Market is the fourth. Pricing, packaging, launch coordination, sales enablement. In some organizations this lives in marketing. In product-led organizations, it belongs in or adjacent to the product org because pricing and packaging are product decisions, not marketing decisions. I stood up GTM as a matrixed capability within the product organization at the company. The pricing architecture overhaul I led across the full hardware and software portfolio delivered measurable ASP uplift across all product lines.

At the company, I founded three of these five functions from scratch. UX Design from scratch. Business Intelligence from scratch. Product Operations from scratch. I completely reset Product Management and stood up GTM as a matrixed capability. 20+ people in my direct organization across five departments. Three built from zero. Over 40 additional team members matrixed through GTM. The product operating model I established remains in place years after my departure. That is the test of an org build: does it survive the builder?

How do you operate globally?

Shipping products to 100+ countries adds three layers of complexity: regulatory compliance, localization, and cross-cultural team coordination. I have operated across all three simultaneously.

Regulatory compliance is a product requirement, not a legal afterthought. FCC, CE, UKCA, CCC for hardware certification. ITAR for export-controlled technology. GDPR and CCPA for data privacy. HIPAA for healthcare applications. Each market has constraints that affect what the product can do, what data it can collect, where that data can be stored, and how the product is certified. At the company, products required FCC and CE certification for every market entry. At Zonar, I led the initial CCPA compliance effort because of the overlap with GDPR and my role as the bridge between Zonar and Continental AG on all overlapping product and compliance activities. Compliance must be embedded in the product development process from day one.

Localization is competitive localization. Translation is table stakes. Real localization requires a deep understanding of cultural norms that affect how the product is used, sold, and supported in each market. At the company, I created and owned a Competitive Localization Program across 14 market groups with 40+ product localizations. The same physical product configured differently for different regulatory environments, measurement standards, and operational practices. But the program went beyond technical compliance. Denmark and the Netherlands have workplace ergonomics and repetitive stress regulations that affect how operators are allowed to use field equipment. Break requirements differ. Product hold positions matter. These are not engineering constraints. They are cultural and regulatory realities that product teams miss when they treat localization as a translation exercise. The program charter I authored defined what varies by market and what stays constant globally, covering not just product configuration but pricing, marketing, communications, and customer engagement adapted to each market’s norms. Pricing localization was a critical market entry lever: willingness to pay, competitive price points, and purchasing norms vary by region, and a global price list applied uniformly across 14 markets leaves revenue on the table in some and blocks entry in others.

Cross-cultural coordination is a leadership skill, not a process. At Zonar, I led 50+ matrixed engineers and product managers across the United States, Romania, France, India, and Asia, coordinating through Continental AG’s matrixed structure. At the company, I managed a development team in India alongside 14 international market groups. The lesson goes deeper than tooling or time zones. Every culture has a different relationship with authority, disagreement, and deadlines. A German engineering team pushes back directly and expects you to have the data ready. An Indian development team signals concern through silence and indirection. A Japanese headquarters makes decisions through consensus that takes longer than Western product cycles expect. I managed approximately 90% schedule adherence across international teams during COVID, measured against annual sprint velocity targets. The product leader’s job is to build a communication cadence that respects these differences while maintaining shared accountability for outcomes.

What does the product operating model look like after 12 months?

If the build is working, after 12 months the organization has:

A roadmap governance process that leadership trusts. At the company, the executive committee transitioned from ad hoc product decisions to a structured quarterly review within my first year.

A prioritization framework that engineering respects. At Zonar, I built an 11-dimension investment scoring framework for the vocational market segment that identified $5.9M in lost and at-risk revenue from portfolio gaps. Engineering engaged because the framework was data-driven, not opinion-driven.

A design system that new products inherit. The human-centered design system I established standardized interaction patterns so that the new flagship platform could ship consistent UX across 100+ markets without per-market design rework.

A metrics layer that connects product usage to business outcomes. The BI function I built created the first dashboards connecting product telemetry to the business metrics the executive team actually used for decision-making.

A release cadence that customers and internal stakeholders can predict.

A team that can operate without the product leader in the room.

That last point is the one that matters most. The product operating model must outlast the person who built it. If it depends on a single leader’s presence to function, it is a personality, and personalities leave.

The flagship product launched at the industry’s largest trade show one month after my departure. Unveiled by the company’s second-generation leadership. The product operating model, the team, and the roadmap governance I established are still in place. The innovation lab I built at Rehrig Pacific Company outlasted my tenure. Renamed the Rehrig Innovation Showcase Experience. At Zonar, the PLG platform my team built survived Continental AG’s sale of the company to a PE acquirer in 2024. The acquirer disposed of their own competing product and kept mine.

Three organizations. Three operating models. Three that outlasted the builder. Build the model. Build the team. Build the cadence. Then build the products.

Technologies and standards referenced

  • FCC Part 15 (US wireless device certification)
  • CE Marking (EU product conformity)
  • UKCA (UK product conformity)
  • CCC (China Compulsory Certification)
  • GDPR (EU General Data Protection Regulation)
  • CCPA (California Consumer Privacy Act)
  • ITAR (International Traffic in Arms Regulations)
  • HIPAA (Health Insurance Portability and Accountability Act)
  • Microsoft Azure, AWS, Google Cloud (cloud platforms)
  • Agile / Scrum (product development methodology)

About the author

Product executive. 15+ years building industrial AI platforms, B2B SaaS products, and connected smart device ecosystems in regulated industries across 100+ countries. Three portfolio turnarounds. Three org builds. Three times the methodology transferred, only the industries changed.

Nick builds at the hardware-software-data intersection. Industrial AI. Edge-to-cloud platforms. Workflow automation systems making 8,000+ decisions per workflow with zero cloud dependency. The career pattern: enter complex regulated environments, find the kill decisions others avoid, and redirect capital from legacy programs to products that ship and outlast him. The acquiring company kept his product. Threw away their own.

Most recently Head of Product at Digital Control Incorporated. Global product portfolio. Turnaround-to-growth. Previously at Zonar Systems, a subsidiary of $44B annual revenue Continental AG, leading a $70M connected device platform across three continents, and at Rehrig Pacific Company building an innovation function from scratch.

Leading global products and global teams as a Chief Product Officer, Head of Product, VP of Product for B2B and B2B2C companies for digital transformation and product growth leadership.

More about Nick →