Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
  • Reliability.fm
    • Speaking Of Reliability
    • Rooted in Reliability: The Plant Performance Podcast
    • Quality during Design
    • Way of the Quality Warrior
    • Critical Talks
    • Dare to Know
    • Maintenance Disrupted
    • Metal Conversations
    • The Leadership Connection
    • Practical Reliability Podcast
    • Reliability Matters
    • Reliability it Matters
    • Maintenance Mavericks Podcast
    • Women in Maintenance
    • Accendo Reliability Webinar Series
  • Articles
    • CRE Preparation Notes
    • on Leadership & Career
      • Advanced Engineering Culture
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • AI & Predictive Maintenance
      • Asset Management in the Mining Industry
      • CMMS and Reliability
      • Conscious Asset
      • EAM & CMMS
      • Everyday RCM
      • History of Maintenance Management
      • Life Cycle Asset Management
      • Maintenance and Reliability
      • Maintenance Management
      • Plant Maintenance
      • Process Plant Reliability Engineering
      • ReliabilityXperience
      • RCM Blitz®
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
      • The People Side of Maintenance
      • The Reliability Mindset
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
    • on Risk & Safety
      • CERM® Risk Insights
      • Equipment Risk and Reliability in Downhole Applications
      • Operational Risk Process Safety
    • on Systems Thinking
      • Communicating with FINESSE
      • The RCA
    • on Tools & Techniques
      • Big Data & Analytics
      • Experimental Design for NPD
      • Innovative Thinking in Reliability and Durability
      • Inside and Beyond HALT
      • Inside FMEA
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • R for Engineering
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Feed Forward Publications
    • Openings
    • Books
    • Webinars
    • Journals
    • Higher Education
    • Podcasts
  • Courses
    • 14 Ways to Acquire Reliability Engineering Knowledge
    • Reliability Analysis Methods online course
    • Measurement System Assessment
    • SPC-Process Capability Course
    • Design of Experiments
    • Foundations of RCM online course
    • Quality during Design Journey
    • Reliability Engineering Statistics
    • Quality Engineering Statistics
    • An Introduction to Reliability Engineering
    • Reliability Engineering for Heavy Industry
    • An Introduction to Quality Engineering
    • Process Capability Analysis course
    • Root Cause Analysis and the 8D Corrective Action Process course
    • Return on Investment online course
    • CRE Preparation Online Course
    • Quondam Courses
  • Webinars
    • Upcoming Live Events
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home

by Dianna Deeney Leave a Comment

QDD 040 How to Self-Advocate for More Customer Face Time (and why it’s important)

How to Self-Advocate for More Customer Face Time (and why it’s important)

There are many stories of design successes attributed to the right level of understanding of the customer. Product designers make decisions, daily, about how a product is going to look and perform. So, we need to really understand the customer. And, to really get the customer, engineers need to spend time with them.

Sometimes, the business doesn’t want us to interact with the customer or doesn’t think it would be valuable. Objections include that we’re not prepared for the user’s environment, that we’re too blunt or honest, or that we just overgeneralize what we learn, anyway. Or, there’s a reluctance because of costs. Besides seeing these objections first hand, someone also listed them out in a published book! This shows that this is common across industries.

Is that fair to design engineers? No matter if it’s fair or not. We can prepare ourselves to address those objections. We talk about how we can prepare ourselves to self-advocate for more customer face time.

 

View the Episode Transcript

 

All that’s left to do is to prepare ourselves to talk with customers, and then self-advocate and volunteer for customer-facing opportunities.

  • We can prepare for the environment by asking questions to understand how we’re being invited into someone else’s space: do we need to prepare anything special or wear certain protective gear?
  • We know to get involved in the meeting planning and to understand our role in the meeting and its objective.
    Our approach is of service to the customer, that the customer is always right. And,
  • We’ll make sure we have a download meeting with our team and management with lessons learned from the customer-facing meeting, even if we need to be the ones to set it up.

Citations

Want to know what book listed out some of these objections?

Smith, Preston G., and Donald G. Reinertsen. Developing Products in Half the Time: New Rules, New Tools, 2nd ed. Germany, Wiley, 1998.

Episode Transcript

There are many stories of design successes attributed to the right level of understanding of the customer. Product designers make decisions, daily, about how a product is going to look and perform. So, we need to really understand the customer. And, to really get the customer, engineers need to spend time with them. Sometimes, the business doesn’t want us to interact with the customer or doesn’t think it would be valuable. Let’s talk about how we can prepare ourselves to self-advocate for more customer face time.

Hello and welcome to quality during design, the place to use quality thinking to create products others love, for less. My name is Dianna. I’m a senior level quality professional and engineer with over 20 years of experience in manufacturing and design. Listen in and then join the conversation at QualityDuringDesign.com.

I always found talking with customers a valuable experience. I would talk to customers about risks of using a potential product, at conferences and trade shows, and would meet them in their place, where they would use a product. It’s important for product designers to get face time with customers. Time and again, it’s shown that understanding our customers gives us the insight we need to design FOR them. Instead of trying to design for a faceless subset of a population with some statistics that someone has given us, designing for customers that we’ve spent an hour or more with helps us really get into who we’re designing for and why. And, that helps us step from what the customer wants into what the customer needs, then we can step into the technical requirements that we mostly design against.

I’ve also moved forward with projects where marketing or field operations handed me a document. Maybe it was results from an off-site meeting, complete with a Kano model (that’s where we map product features against customer delight). Or, notes about customer wants versus customer needs. The information was certainly helpful. But it didn’t come even close to having that information AND getting a chance to sit at a roundtable with customers. Face time with customers is best.

When should we talk to customers? If we wait until we have a prototype, that’s too late. We want to talk to customers before our product design even hits the paper. Customers can tell us what they want. We need to talk with customers to figure out what they need. And, we have to do this before we start getting into any designs. We should also talk to customers throughout the design process. Maybe their involvement will taper off the farther into the design we get. So, developing a designing relationship with our customers would be a valuable thing to do.

We’ve now talked about why it’s important for design engineers to talk with customers. And, that we want to be able to talk with them routinely throughout product development. Our marketing and field operations departments have the contact list. How do we better prepare ourselves to talk with customers, and encourage our marketing departments to let us do so?

Other functions of the business have objections to inviting engineers to speak with customers, and a lot of it has to do with maintaining a positive business image. I’ve experienced them. And, I was reminded of some other objections while I was doing some reading. Is that fair to design engineers? No matter if it’s fair or not. We can prepare ourselves to address those objections.

One objection is that we’re ill-prepared for the customer’s environment. I had opportunities to speak with surgeons in their office, interviewing them to understand the risks of a product. It was a valuable exercise for the company, and the surgeon thought so, too. Then, for a different project, I was invited to talk to a different surgeon, again. Like before, I traded my steel-toed shoes and khaki pants for a nicer suit and dress shoes. When I showed up at work, the marketing manager that had set-up the site visit clicked her tongue, shook her head, sighed, and then chuckled. “This is why I don’t invite engineers to site visits.” This time, I was being invited into a surgical suite, and I was not dressed appropriately for that type of environment. Was it the marketing manager’s fault? No, it was my fault. I assumed what a site visit would mean based on my other project. I failed to get the details about the day so I could prepare myself appropriately.

So, we jump into a customer’s environment that is foreign to our environment, and don’t fit in well or are not prepared for it. This is why visiting customers is a valuable design tool! This objection by other departments is also easy to address: we ask in advance what type of site it is to understand if there are any safety measures or dress codes that we need to account for. Understanding the customer’s environment is one aspect. Understanding how we’re being invited into someone else’s space is another. Asking in advance is being responsible for ourselves. It’s not showing that we don’t understand them. It’s a sign that we respect them.

Another objection is that engineers are too blunt or honest with customers. This is not my story, but I think it’s a good one. A customer was trying a nearly completed design. They were given the product and the instructions and were being asked to use it in their environment, where they work. The design team was meant to observe, only. The customers were having troubles using the product. The engineer that was invited to observe got frustrated watching the customer try to fiddle with the product, so he intervened and said, “You’re using it wrong! You’re supposed to do it THIS way!” Was it really that the customer was using it wrong? Or, was it that the engineer designed the wrong thing? The product wasn’t intuitive to use, which is a design problem. The engineer was more worried about it being technically right, and less concerned about how the customer used it and what they thought about it. This outburst of the engineer was damaging to the business-customer relationship. And it also ruined a validation study.

What can we do about this objection: that we’re too blunt or honest with customers? First, we’re clear about the objective of this meeting. Then we show up as part of the plan for the meeting. We make sure we have a role to play in the meeting, we’re not just a tag-a-long. It’s alright to take marketing’s lead, and to let them know that we’re taking their lead. After all, its marketing, sales, or field ops that are the ones that have built a relationship with a customer. It makes sense that they’d want to protect that relationship. So, we’ll show up, but we’re okay with taking a back seat and to not control the meeting. We do want to make sure that we gain the knowledge and customer’s perspective that we need, so we don’t want to leave with unanswered questions. We take notes, we jot down questions, and we check-in with the meeting facilitator (namely the marketing person).

At these meetings, the customer is always right. It’s an old saying, but it directly applies in this situation. There’s no sense to argue with the customer over how they like to do things, or how they understand or expect their world and environment to work. We might learn something that makes our design job difficult or inconvenient, but that’s not the customer’s fault. We’re providing a service to the customer by designing a product for them to use. They’re taking time out of their day to help us learn how we can be of better service to them.

Now we’re prepared for the environment, we have a role in the meeting, and we’re approaching it as “the customer is always right”. We attend the meeting and walk away with new found insight into our customers. There’s another hurdle we need to address, and that is the complaint that engineers overgeneralize. I think this just comes with how we think: we’ve learned something, so now how can we use it? To prevent the overgeneralization, we can depend on our marketing people to help. After we’ve met with the customer, we meet with our team (including marketing) as soon as we can. We download what we’ve learned and share our take-aways with the rest of our team after meeting with the customer. This gives the entire team (including marketing) a chance to get on the same page with respect to the product design.

The last objection to engineers talking with customers has to do with the cost of doing so. Managers may say, “We have a marketing team doing market research. Why do we need to send engineers away from the design house, and pay for their travel?” This kind of objection can only be won-over with management’s understanding of the value of designers talking directly with customers. We may need to present a value-proposition. We can go back to the plan for the meeting, and its objectives. And involving management in the download meetings, where we’re sharing notes and making decisions about the design, will demonstrate the value of designers talking with customers. It might cost a little to send an engineer to talk with a customer. It costs a whole lot more to redesign a nearly-finished prototype because we didn’t get the customer needs correct.

What is today’s insight to action?

All that’s left to do is to prepare ourselves to talk with customers, and then self-advocate and volunteer for customer-facing opportunities. We can prepare for the environment by asking questions to understand how we’re being invited into someone else’s space: do we need to prepare anything special, or wear certain protective gear? We know to get involved in the meeting planning and to understand our role in the meeting and its objective. Our approach is of service to the customer, that the customer is always right. And, we’ll make sure we have a download meeting with our team and management, even if we need to be the ones to set it up.

Input from the customer is so important to successful design. This might go beyond what we’re doing now, but it’s shown time and again and published in many sources: designers design better products when they’ve had face-time with customers. It’s a technique that us and our counterparts just need to get comfortable with doing.

Please go to my website at QualityDuringDesign.com. You can visit me there, and it also has a catalog of resources, including all the podcasts and their transcripts. Use the subscribe forms to join the weekly newsletter, where I share more insights and links. In your podcast app, make sure you subscribe or follow Quality During Design to get all the episodes and get notified when new ones are posted. This has been a production of Deeney Enterprises. Thanks for listening!

Filed Under: Quality during Design, The Reliability FM network

About Dianna Deeney

Dianna is a senior-level Quality Professional and an experienced engineer. She has worked over 20 years in product manufacturing and design and is active in learning about the latest techniques in business.

Dianna promotes strategic use of quality tools and techniques throughout the design process.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Quality during Design podcast logo

Tips for using quality tools and methods to help you design products others love, for less.


by Dianna Deeney
Quality during Design,
Hosted on Buzzsprout.com
Subscribe and enjoy every episode
Google
Apple
Spotify

Recent Episodes

QDD 128 Leveraging Proven Frameworks or Concept Development

QDD 127 Understanding Cross-Functional Collaboration

QDD 126 Exploring the Problem Space: A Key Principle for Robust Product Design and Project Success

QDD 125 Exploring Product Development and AI Through Literature

QDD 124 Design for User Tasks using an Urgent/Important Matrix

QDD 123 Information Development in Design, with Scott Abel – Part 2 (A Chat with Cross-Functional Experts)

QDD 122 Information Development in Design, with Scott Abel – Part 1 (A Chat with Cross-Functional Experts)

QDD 121 Crafting Effective Technical Documents for the Engineering Field

QDD 120 How to use FMEA for Complaint Investigation

QDD 119 Results-Driven Decisions, Faster: Accelerated Stress Testing as a Reliability Life Test

QDD 118 Journey from Production to Consumption: Enhancing Product Reliability

QDD 117 QDD Redux: Choose Reliability Goals for Modules

QDD 116 Reliability Engineering during Design, with Adam Bahret (A Chat with Cross-Functional Experts)

QDD 115 QDD Redux: 5 Options to Manage Risks during Product Engineering

QDD 114 The Instant Glory of Projects

QDD 113 What to do about Virtual Meetings

QDD 112 QDD Redux: How to self-advocate for more customer face time (and why it’s important)

QDD 111 Engineering with Receptivity, with Sol Rosenbaum (A Chat with Cross-Functional Experts)

QDD 110 Don’t Wish for Cross-Functional Buy-in on Product Designs – Plan to Get It!

QDD 109 Before You Start Engineering Solutions, Do This

QDD 108 QDD Redux Ep. 4: Statistical vs. Practical Significance

QDD 107 QDD Redux Ep. 3: When it’s Not Normal: How to Choose from a Library of Distributions

QDD 106 QDD Redux Ep. 2: How to Handle Competing Failure Modes

QDD 105 QDD Redux Ep. 1: How Many Do We Need to Test?

QDD 104 The Fundamental Thing to Know from Statistics for Design Engineering

QDD 103 What to do for Effective and Efficient Working Meetings

QDD 102 Get Design Inputs with Flowcharts

QDD 101 Quality Tools are Legos of Development (and Their 7 Uses)

QDD 100 Lessons Learned from Coffee Pod Stories

QDD 099 Crucial Conversations in Engineering, with Shere Tuckey (A Chat with Cross-Functional Experts)

QDD 098 Challenges Getting Team Input in Concept Development

QDD 097 Brainstorming within Design Sprints

QDD 096 After the ‘Storm: Compare and Prioritize Ideas

QDD 095 After the ‘Storm: Pareto Voting and Screening Methods

QDD 094 After the ‘Storm: Group and Explore Ideas

QDD 093 Product Design with Brainstorming, with Emily Haidemenos (A Chat with Cross Functional Experts)

QDD 092 Ways to Gather Ideas with a Team

QDD 091 The Spirits of Technical Writing Past, Present, and Future

QDD 090 The Gifts Others Bring

QDD 089 Next Steps after Surprising Test Results

QDD 088 Choose Reliability Goals for Modules

QDD 087 Start a System Architecture Diagram Early

QDD 086 Why Yield Quality in the Front-End of Product Development

QDD 085 Book Cast

QDD 084 Engineering in the Color Economy

QDD 083 Getting to Great Designs

QDD 082 Get Clarity on Goals with a Continuum

QDD 081 Variable Relationships: Correlation and Causation

QDD 080 Use Meetings to Add Productivity

QDD 079 Ways to Partner with Test Engineers

QDD 078 What do We do with FMEA Early in Design Concept?

QDD 077 A Severity Scale based on Quality Dimensions

QDD 076 Use Force Field Analysis to Understand Nuances

QDD 075 Getting Use Information without a Prototype

QDD 074 Finite Element Analysis (FEA) Supplements Test

QDD 073 2 Lessons about Remote Work for Design Engineers

QDD 072 Always Plot the Data

QDD 071 Supplier Control Plans and Design Specs

QDD 070 Use FMEA to Design for In-Process Testing

QDD 069 Use FMEA to Choose Critical Design Features

QDD 068 Get Unstuck: Expand and Contract Our Problem

QDD 067 Get Unstuck: Reframe our Problem

QDD 066 5 Options to Manage Risks during Product Engineering

QDD 065 Prioritizing Technical Requirements with a House of Quality

QDD 064 Gemba for Product Design Engineering

QDD 063 Product Design from a Data Professional Viewpoint, with Gabor Szabo (A Chat with Cross Functional Experts)

QDD 062 How Does Reliability Engineering Affect (Not Just Assess) Design?

QDD 061 How to use FMEA for Complaint Investigation

QDD 060 3 Tips for Planning Design Reviews

QDD 059 Product Design from a Marketing Viewpoint, with Laura Krick (A Chat with Cross Functional Experts)

QDD 058 UFMEA vs. DFMEA

QDD 057 Design Input & Specs vs. Test & Measure Capability

QDD 056 ALT vs. HALT

QDD 055 Quality as a Strategic Asset vs. Quality as a Control

QDD 054 Design Specs vs. Process Control, Capability, and SPC

QDD 053 Internal Customers vs. External Customers

QDD 052 Discrete Data vs. Continuous Data

QDD 051 Prevention Controls vs. Detection Controls

QDD 050 Try this Method to Help with Complex Decisions (DMRCS)

QDD 049 Overlapping Ideas: Quality, Reliability, and Safety

QDD 048 Using SIPOC to Get Started

QDD 047 Risk Barriers as Swiss Cheese?

QDD 046 Environmental Stress Testing for Robust Designs

QDD 045 Choosing a Confidence Level for Test using FMEA

QDD 044 Getting Started with FMEA – It All Begins with a Plan

QDD 043 How can 8D help Solve my Recurring Problem?

QDD 042 Mistake-Proofing – The Poka-Yoke of Usability

QDD 041 Getting Comfortable with using Reliability Results

QDD 040 How to Self-Advocate for More Customer Face Time (and why it’s important)

QDD 039 Choosing Quality Tools (Mind Map vs. Flowchart vs. Spaghetti Diagram)

QDD 038 The DFE Part of DFX (Design For Environment and eXcellence)

QDD 037 Results-Driven Decisions, Faster: Accelerated Stress Testing as a Reliability Life Test

QDD 036 When to use DOE (Design of Experiments)?

QDD 035 Design for User Tasks using an Urgent/Important Matrix

QDD 034 Statistical vs. Practical Significance

QDD 033 How Many Do We Need To Test?

QDD 032 Life Cycle Costing for Product Design Choices

QDD 031 5 Aspects of Good Reliability Goals and Requirements

QDD 030 Using Failure Rate Functions to Drive Early Design Decisions

QDD 029 Types of Design Analyses possible with User Process Flowcharts

QDD 028 Design Tolerances Based on Economics (Using the Taguchi Loss Function)

QDD 027 How Many Controls do we Need to Reduce Risk?

QDD 026 Solving Symptoms Instead of Causes?

QDD 025 Do you have SMART ACORN objectives?

QDD 024 Why Look to Standards

QDD 023 Getting the Voice of the Customer

QDD 022 The Way We Test Matters

QDD 021 Designing Specs for QA

QDD 020 Every Failure is a Gift

QDD 019 Understanding the Purposes behind Kaizen

QDD 018 Fishbone Diagram: A Supertool to Understand Problems, Potential Solutions, and Goals

QDD 017 What is ‘Production Equivalent’ and Why Does it Matter?

QDD 016 About Visual Quality Standards

QDD 015 Using the Pareto Principle and Avoiding Common Pitfalls

QDD 014 The Who’s Who of your Quality Team

QDD 013 When it’s Not Normal: How to Choose from a Library of Distributions

QDD 012 What are TQM, QFD, Six Sigma, and Lean?

QDD 011 The Designer’s Important Influence on Monitoring After Launch

QDD 010 How to Handle Competing Failure Modes

QDD 009 About Using Slide Decks for Technical Design Reviews

QDD 008 Remaking Risk-Based Decisions: Allowing Ourselves to Change our Minds.

QDD 007 Need to innovate? Stop brainstorming and try a systematic approach.

QDD 006 HALT! Watch out for that weakest link

QDD 005 The Designer’s Risk Analysis affects Business, Projects, and Suppliers

QDD 004 A big failure and too many causes? Try this analysis.

QDD 003 Why Your Design Inputs Need to Include Quality & Reliability

QDD 002 My product works. Why don’t they want it?

QDD 001 How to Choose the Right Improvement Model

Join Accendo

Receive information and updates about articles and many other resources offered by Accendo Reliability by becoming a member.

It’s free and only takes a minute.

Join Today

© 2025 FMS Reliability · Privacy Policy · Terms of Service · Cookies Policy