• News
  • Events
  • Handbook

News, Blog, & Resources

Case Studies

All Site

Build Better Handbook: Table of Contents
  •   

    Start Here

    • Introduction to the Build Better Handbook

    • Manufacturing Term Glossary

  •   

    Getting Culture Right

    • Jeff Lutz: Team Culture Drives Product Performancepopular

    • Scrappy Ways to Execute Like Applepopular

    • Building a Culture of Quality

      • Building the World's Most Reliable Products: Insights from Medical and Defense Leaders
      • Fear Management
  •   

    NPI: A How To Guide for Engineers & Their Leaders

    • Leading from the Front

      • Marcel Tremblay: The Olympic Mindset & Engineering Leadership
      • Anurag Gupta: Framework to Accelerate NPI
      • Kyle Wiens on Why Design Repairability is Good for Business
      • Nathan Ackerman on NPI: Do The Hard Thing First
      • JDM Operational Excellence in NPI
    • Building the Team

      • Quality is Set in Development & Maintained in Production
      • 3 Lessons from Tesla’s Former NPI Leader
      • Maik Duwensee: The Future of Hardware Integrity & Reliability
      • Reject Fake NPI Schedules to Ship on Time
      • Leadership Guidance for Failure to Meet Exit Criteria
    • Screws & Glue: Getting Stuff Done

      • Choosing the best CAD software for product design
      • Screws vs Glues in Design, Assembly, & Repair
      • Best Practices for Glue in Electronics
      • A Practical Guide to Magnets
      • Inspection 101: Measurements
      • OK2Fly Checklists
      • Developing Your Reliability Test Suite
      • Guide to DOEs (Design of Experiments)
      • Ten Chinese phrases for your next build
    • NPI Processes & Workflows

      • EVT, DVT, PVT Stage Gate Definitions
      • Hardware Schedules are Driven by Iteration
      • The Shedletsky Test: 12 Requirements for NPI Programs
      • 4 Best Practices for Generational Knowledge Building
  •   

    Production: A Primer for Operations, Quality, & Their Leaders

    • Behind the Pins: How We Built a Smarter Way to Inspect Connectors

    • Former Apple Executive Bryan Roos on Leading Teams in China and Managing Up

    • Responding to Rare-Earth Supply Chain Risks: A Quick Guide for Manufacturers

    • Logitech’s Approach to Collaboration with Manufacturing Data

    • Leading for Scale

      • Navigating Factory Moves and Scaling Production in an Era of Uncertainty with PRG's Wayne Miller
      • Steven Nickel on How Google Designs for Repair
      • Petcube’s Alex Neskin Embraces Imperfection to Deliver Innovation
      • Proven Strategies for Collaborating with Contract Manufacturers
      • Greg Reichow’s Manufacturing Process Performance Quadrants
      • 8D Problem Solving: Sam Bowen Describes the Power of Stopping
      • Cut Costs by Getting Your Engineers in the Field
      • Garrett Bastable on Building Your Own Factory
      • Oracle Supply Chain Leader Mitigates Risk with Better Relationships
      • Brendan Green on Working with Manufacturers
      • Surviving Disaster: A Lesson in Quality from Marcy Alstott
    • Ship It!

      • Serialization for Electronics Manufacturing
      • Tactics to Derisk Ramp
      • E-Commerce Ratings Make Product Quality a Competitive Edge
    • Production Processes & Workflows

      • Failure Analysis Methods for Product Design Engineers: Finding Sources of Error
      • Failure Analysis Methods for Product Design Engineers: Tools and Techniques
      • How to Improve First Pass Yield with Instrumental
      • How to Identify Dark Yield
      • JDM Operational Excellence in Production
  •   

    Thinking Ahead: How to Evaluate New Technologies

    • How to Buy Software (for Hardware Leaders who Usually Don’t)

    • Adopting AI in the Aerospace and Defense Electronics Space

    • Build vs Buy: A Guide to Implementing Smart Manufacturing Technology

    • Leonel Leal on How Engineers Should Frame a Business Case for Innovation

    • Saw through the Buzzwordspopular

      • Managed Cloud vs Self-Hosted Cloud vs On-Premises for Manufacturing Data
      • AOI, Smart AOI, & Beyond: Keyence vs Cognex vs Instrumentalpopular
      • Visual Inspection AI: AWS Lookout, Landing AI, & Instrumental
      • Manual Inspection vs. AI Inspection with Instrumentalpopular
      • Electronics Assembly Automation Tipping Points
      • CTO of ASUS: Systems Integrators for Manufacturing Automation Don't Scale
    • ROI-Driven Business Cases & Realized Value

      • Building a Buying Committee
      • How to Buy Software (for Those Who Usually Don't)
  •   

    Webinars and Live Event Recordings

    • Overcoming the Three-Body Problem in Electronics Manufacturing

    • The Frontier of Trust - Build Better 2025

    • Outsourced: Industry Perils of Delegating Too Much of Product Innovation and Ownership | Build Better 2025

    • The Frontier of Electronics Complexity: The Many Bottlenecks of AI Compute Infrastructure

    • Limitless Acceleration: The Frontier of Schedule Velocity in NPI and Production

    • The Apple-China Symbiosis and What it Means for the Future of Electronics with Patrick McGee

    • Get Me Outta Here! Racing to Full Production Somewhere Else

    • Tariff Talk for Electronics Brands: Policies Reactions, Reciprocal Tariffs, and more.

    • Materials Planning: The Hidden Challenges of Factory Transitions

    • Build Better 2024 Sessions On Demand

      • Superpowers for Engineers: Leveraging AI to Accelerate NPI | Build Better 2024
      • The Motorola Way, the Apple Way, and the Next Way | Build Better 2024
      • The Future of Functional Test: Fast, Scalable, Simple | Build Better 2024
      • Build Better 2024 Keynote | The Next Way
      • Principles for a Modern Manufacturing Technology Stack for Defense | Build Better 2024
      • What's Next for America's Critical Supply Chains | Build Better 2024
      • Innovating in Refurbishment, Repair, and Remanufacturing | Build Better 2024
      • Leading from the Front: The Missing Chapter for Hardware Executives | Build Better 2024
      • The Next Way for Reducing NPI Cycles | Build Better 2024
      • Scaling Manufacturing: How Zero-to-One Lessons Unlock New Opportunities in Existing Operations | Build Better 2024
    • Build Better Fireside Chats

      • Aerospace and Defense: Headwinds & Tailwinds for Electronics Manufacturing in 2025
      • From Counterfeits to Sanctions: Securing Your Supply Chain in an Era of Conflict
      • Design for Instrumental - Simple Design Ideas for Engineers to Get the Most from AI in NPI
      • Webinar | Shining Light on the Shadow Factory
      • Tactics in Failure Analysis : A fireside chat with Dr. Steven Murray
    • Preparing for Tariffs in 2025: Resources for Electronics Manufacturers

      • How to Prepare for Tariffs in 2025: Leaders Share Lessons and Strategies
      • Tariff Talk for Electronics Brands
      • Talking Trade Compliance with Gabrielle Griffith
      • GUIDE: Moving Your Factory
  1. Build Better Handbook
  2. Old Content
  3. Logitech’s Approach to Collaboration with Manufacturing Data

Logitech’s Approach to Collaboration with Manufacturing Data

Estimated reading time: · copy link

Before he ever walked a production line in Beijing, Martin Hess Pedersen spent nearly twenty years inside Nokia writing and leading software. Then a simple obsession changed his path: what are our consumers actually telling us, and how fast can we learn from them? That question carried him from software quality into the full stack of hardware, testing, and manufacturing, and eventually into a 12-year stint in Asia.

This story is for leaders who want to transform messy signals from factory data, field feedback, and human judgment into repeatable excellence grounded in trust.

Martin Hess Pedersen on the Great Wall of China.

Nokia’s Foundation for Data and Trust

When Martin Hess Pedersen talks about his years at Nokia, there’s no hesitation in his admiration.
“If Nokia were still alive and thriving today,” he says with a smile, “I’d probably still be there.”

Those were the years that shaped him, two decades spent at the heart of one of the most admired engineering organizations in the world. He began in software, leading teams and managing development programs, but his curiosity quickly grew beyond code. He wanted to understand how products lived once they left the lab. What did consumers experience? What could their feedback teach engineers about design, quality, and manufacturing?

That question led him into the factory. “We built five million phones a month out of a single plant,” Martin recalls. “The supply chain was extraordinary, world-class in efficiency and precision.”

At Nokia, the concept of data-driven quality was ingrained in the company's culture. Even in the early 2010s, “we’d combine component and finished-goods data, track every KPI, and move quickly to the right part of the supply chain the moment something started to drift.”

Nokia’s structure — owning most of its factories and keeping suppliers close — created a culture of transparency.

“When you own both the process and the data,” Martin says, “trust is the default.”

Across Cultures: Microsoft and Foxconn

After nearly twenty years at Nokia, the next chapters of his career would expose Martin to entirely different cultures of hardware engineering and manufacturing execution.

When Microsoft acquired Nokia in 2014, Martin continued to lead manufacturing quality. If “Nokia’s Way” was data-driven quality and world-class efficiency, he describes “Microsoft’s Way” as deep specialization and process discipline.

“It was a huge learning curve,” he remembers. “Nokia was flat and fast; Microsoft was structured and siloed. Neither was wrong — they just moved differently.”

In 2016, still in Beijing, Martin joined Foxconn when the company purchased Nokia’s mobile assets and sought to relaunch a licensed Nokia brand under its umbrella. Martin initially hesitated. “Foxconn’s culture was unlike anything I’d experienced — very hierarchical, very top-down,” he says. “But I also saw the potential to blend what I’d learned at Nokia about quality and trust into a new system built on a massive scale.”

While at Foxconn, he and a small team built an end-to-end mobile phone division — design, development, manufacturing, and supply chain — inside Foxconn.

At Foxconn, there’s only one voice — Terry Guo’s. You don’t bring bad news. But when you’ve seen what openness can accomplish, you realize how much that transparency enables both speed and quality.”

The three experiences — Nokia’s collaborative precision, Microsoft’s structure, and Foxconn’s command hierarchy — have provided Martin with a strong perspective on the importance of transparency and data in building great products.

Why Data Transparency Isn’t the Default in Contract Manufacturing Relationships

Even today, with AI systems on every roadmap, leaders at electronics brands both large and small still struggle to get raw manufacturing data from their contract partners. Martin knows both sides of that tension — and the psychology behind it.

“Eighty to ninety percent of the time,” he says, “when something goes wrong, the supplier’s first thought is liability. They ask, ‘What am I going to be held accountable for?’”

Fear, not technology, is the barrier. Suppliers hesitate because data can expose risk — or margin. And when every percentage point matters, some suppliers might be tempted at various times to fudge the numbers – rework not reported, yield numbers “smoothed,” only sharing incomplete test data.

Martin doesn’t demonize it. He understands it. “Margins are narrow, and brands push for cost-down every year. Suppliers look for little buffers to survive. If full transparency means losing those buffers, hesitation is human.”

But he’s clear about the fix: trust through shared accountability. “It takes two to tango. If the brand dictates the process — from SOPs to test limits — then the brand owns part of the result. Contracts should reflect that.” Unfortunately, by the time many leaders – on engineering, or quality, or even automation teams – get involved with their suppliers, procurement has already stamped a contract that will drive behavior. Shared accountability needs to be built in up front, so that liability and fear are not a barrier to sharing the information that enables high-quality execution at rapid speeds.

The “Logitech Way”: Partners, Not Suppliers

When Martin joined Logitech, that idea became doctrine. “We don’t have suppliers; we have partners. We grow together and learn together.”

The principle sounds simple, but it plays out in deliberate ways:

  1. Shared Risk. Logitech’s manufacturing contracts explicitly balance responsibility. Brands accept part of the operational risk when they drive design and process decisions.
  2. Presence and the Personal Touch. During new site ramps, Martin’s team sends people to “walk the line” — observing, testing, and debugging shoulder-to-shoulder with factory teams. “We don’t push the big green button until we’re confident,” he says.
  3. Transparency as Learning. When a partner shares early issues, they’re rewarded with support, not penalties.

Owned factories and contract sites both feed into Logitech’s data lake, but their data looks different. Owned sites are automated and structured; manufacturing partners require translation. Instead of forcing uniformity, Martin’s team invests in infrastructure to normalize diverse data sets and achieve consistent insights regardless of source.

“We treat our manufacturing partners as extensions of our own operations,” he explains. That includes sharing learnings. Manufacturing partners are often eager to learn from their customers – but many customers are reluctant to share information from their sales channels or market data.

“They want to know the happiness of the consumer, star ratings, return rates, reviews,” he says. “That’s their achievement, too.”

They also want to see what’s ahead: roadmap visibility, early access to innovation plans, and how they rank against their peers. Logitech shares anonymized performance comparisons, not as punishment, but as motivation.

“When a supplier knows they’re outperforming the average, it builds pride. When they’re not, it builds focus. Either way, it drives improvement.”

The Future: AI, Blended Data, and Closed-Loop Quality

Martin’s excitement about AI isn’t theoretical — it’s grounded in years of working with messy, real-world data. “AI is already helping us mine call transcripts, repair logs, and manufacturing records for root causes,” he says. “You can get to an 80 or 90 percent correct hypothesis in minutes. That’s game-changing.”

The next step is even more ambitious: blending consumer data with factory data to build predictive quality systems.  “Imagine connecting every test station, every yield report, every customer review,” he says. “You could see a pattern forming before the first return hits the field.”

To get there, data governance matters. “Without structured lineage and disciplined data ownership, the models can’t learn correctly. But when they do, they’ll give us insights we can’t even imagine today.” Building these systems will be what’s next for top-tier electronics brands and manufacturers.

Views: 47
  • Log In
  • Speak to an Expert
  • Twitter_Logo_Blue

Change Notice

Get notified when we update the handbook

Please fill out a valid email!

Thanks for your subscription!

© 2026 Instrumental. Privacy Policy

We use cookies to improve your experience, analyze traffic, and personalize content.
By clicking “Accept”, you agree to our use of cookies. You can manage your preferences at any time.

Instrumental
Powered by  GDPR Cookie Compliance
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.