I design the systems that turn product innovation into compliant,
scalable consumer products. Connecting enterprise architecture,
regulatory infrastructure, and product development into one
coherent system.
16+ years · Food · Beverage · Personal Care · Regulated Industries
In regulated consumer product companies, the systems that govern product
development are often the least architected. Product knowledge gets lost
between R&D and enterprise platforms. Regulatory and quality requirements
exist in isolation from the data they depend on. Compliance processes that
should enable product launches instead become the bottleneck that delays them.
These are systems architecture problems — and they require leadership that
understands the full lifecycle.
My work sits at the intersection of three domains that most
organizations manage as separate functions.
Enterprise IT Systems
Designing and governing the platforms, workflows, and data
structures that manage product lifecycle information across
the organization.
Regulatory & Quality
Building the compliance, traceability, and quality systems
that ensure products meet regulatory requirements from
development through market.
Research & Development
Ensuring that product development teams can create and
launch new products without being constrained by the
systems meant to support them.
Few professionals operate fluently across all three.
That intersection is where I lead.
If you're building or leading product lifecycle systems
in a regulated industry, I'd welcome the conversation.
I operate at the intersection of product innovation and regulatory reality —
designing and governing the complex enterprise systems that allow consumer
product companies to safely develop and launch new products.
In regulated consumer product companies, enterprise systems, regulatory
infrastructure, and product development are deeply interdependent — but
they're rarely managed that way. My work focuses on designing the systems
architecture that connects them: ensuring product data flows reliably,
compliance is built into the infrastructure, and development teams can
move without friction.
Over sixteen years in enterprise environments — primarily in food, beverage,
and personal care — I've built my career on bringing structure, reliability,
and strategic coherence to these systems. I design the product lifecycle
infrastructure that allows R&D teams to focus on innovation while ensuring
that everything supporting those products remains compliant, scalable,
and audit-ready.
I'm increasingly focused on the next horizon of this work: regulatory
technology strategy, AI-enabled product lifecycle management, and the
evolving role of enterprise knowledge systems in regulated organizations.
Expertise
Three domains define my work — enterprise IT systems, regulatory
and quality infrastructure, and product development. In many
organizations, these operate in silos. I design the connections
between them.
Enterprise IT Systems
What This Means in Practice
Designing and governing the platforms, workflows, and data structures
that manage product lifecycle information across the organization. This
includes PLM platform architecture, enterprise workflow design, system
governance models, and the training and adoption strategies that determine
whether systems actually get used as intended.
When This Breaks
Product data lives in disconnected systems. Teams build workarounds in
spreadsheets. Institutional knowledge exists in people's heads rather
than in governed platforms. The organization can't answer basic questions
about its own products without manual effort.
What I Bring
Over sixteen years of designing and leading enterprise systems programs
in complex organizations — with a focus on building architecture that
serves the business rather than just satisfying IT requirements.
Regulatory & Quality
What This Means in Practice
Building the compliance, traceability, and quality systems that ensure
products meet regulatory requirements from development through market.
This includes compliance documentation systems, audit readiness infrastructure,
quality assurance workflows, and the regulatory data architecture that
supports product safety.
When This Breaks
Regulatory documentation exists apart from the product data it depends on.
Audit preparation becomes a manual scramble. Compliance requirements are
treated as checkpoints rather than embedded in the systems architecture.
The organization discovers gaps only when auditors or regulators find them first.
What I Bring
Deep experience in regulated consumer product environments — food, beverage,
and personal care — where compliance isn't optional and the systems supporting
it must be as rigorous as the science behind the products.
Research & Development
What This Means in Practice
Ensuring that product development teams can create and launch new products
without being constrained by the systems meant to support them. This means
designing lifecycle infrastructure that accelerates innovation rather than
gating it — where R&D teams can focus on formulation and invention while
the surrounding systems handle governance, documentation, and compliance.
When This Breaks
Product development slows to a crawl because every step requires manual
compliance review. R&D knowledge never makes it into enterprise systems.
Product launches are delayed not by scientific or market challenges, but by
infrastructure that wasn't designed to move at the speed of innovation.
What I Bring
A perspective shaped by working directly alongside R&D, regulatory science,
and product development teams — understanding their workflows well enough
to build systems that serve them rather than constrain them.
The Intersection
Most organizations have regulatory specialists, IT architects, and product
development leaders — but few professionals operate fluently across all three
domains. My work lives at the intersection: designing enterprise systems
that are simultaneously architecturally sound, regulatory-ready, and built
to enable product innovation rather than slow it down.
The Operational Flow
The three domains above describe what I bring. The systems map below
shows where that expertise operates — the lifecycle flow that every
regulated consumer product company must manage, and where it most
often breaks down.
Every regulated consumer product moves through these four stages. My role spans all of them.
Systems Thinking in Practice
Enterprise IT Systems × Regulatory & Quality
Translating Regulatory Requirements into Enterprise Systems
The Situation
A new federal regulation required a major consumer products company
to publish laboratory testing results to a public-facing website. The
regulation was complex, the data lived in a LIMS system, and no existing
workflow connected testing data to public reporting infrastructure.
The Approach
Managed the project end-to-end: translated scientific testing concepts
for the IT team, translated IT system requirements back to the regulatory
science team, and built a working prototype that moved data from LIMS
to the public website. The prototype informed the final production implementation.
Enterprise IT Systems × Research & Development
Governing Product Lifecycle Systems at Enterprise Scale
The Situation
A Fortune 100 consumer products organization needed to manage complex
product lifecycle, quality, and regulatory systems across multiple
business units — with an annual program budget of approximately $2.5M
and competing stakeholder priorities.
The Approach
Led systems and program decisions affecting long-term IT strategy,
vendor selection, and organizational infrastructure. Balanced enterprise
architecture requirements with the practical needs of product development,
quality, and regulatory compliance teams.
Cross-Domain Integration
Bridging Technical, Regulatory, and Operational Stakeholders
The Situation
Enterprise systems supporting product development had become fragmented
across departments. Regulatory teams, IT, and product development each
operated in isolation, with manual processes and tribal knowledge bridging
the gaps between them.
The Approach
Served as the bridge between technical teams, regulatory experts, and
operational stakeholders — restructuring workflows, redesigning system
integrations, and establishing governance models that aligned all three
groups around a coherent product lifecycle architecture.
If your organization is navigating enterprise systems challenges
in a regulated industry, I'd welcome the conversation.
I'm open to conversations about leadership opportunities in product
lifecycle systems, strategic collaboration, and industry dialogue
within regulated consumer products.
Professional Inquiries
For leadership opportunities, executive recruiting conversations,
and strategic partnerships.
