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 127 Understanding Cross-Functional Collaboration

Understanding Cross-Functional Collaboration

Are you prepared to untap the potential of cross-functional collaboration in product design?

On this episode of Quality during Design, we pull back the curtains on the dynamics of cross-functional teams in product design. Dianna Deeney, your host and seasoned quality professional, shares her insights on navigating the complex world of cross-functional teams, addressing common misconceptions, and maximizing brainstorming through structure.

We’re about to take a deep dive into the power of diverse perspectives in shaping a holistic vision for a product. Hear about the concept of internal customers in product design, the process of gathering design inputs, and unlocking the potential of directed co-work. This episode is a must-listen for anyone aiming for cross-functional co-work for design inputs.

 

View the Episode Transcript

During concept development, our goal as a product designer is to give our cross-functional team opportunities to talk together and with us so that we can gather design inputs. That’s really what we want are the design inputs against which we can create a great design.

If we approach collaboration:

  • in a structured way,
  • with questions already formed,
  • and a way to communicate and facilitate a meeting with design inputs as the goal,

we’re going to have more success with getting the design inputs that we need, and we’ll have a more successful design because of that.

 

We’re collecting our design inputs with our cross-functional team in a collaborative co-work meeting.

  • Work toward a common goal, something that is not so big as the project goal, but something smaller and more focused that can be achievable within one working session.
  • Focus on the user. We’re designing and developing something for them, for them to be able to use it.
  • Have a starting point. We don’t just show up with a cross-functional collaboration meeting with nothing. We do want to do some homework and not show up empty-handed.
  • Follow a “roadmap” that includes a general direction that we’re taking, the group prompted questions, scenarios within which groups can be creative, etc…

How can we do this? With quality tools…Quality during Design.


Below are some articles about cross-functional team dynamics and ways to manage and build them up for success. I promised I would like to these in the podcast, so here they are!

75% of Cross-Functional Teams Are Dysfunctional by Benham Trabezi. He proposes a Portfolio Governance Team which uses end-to-end accountable leaders for each function and for the project.

Solver Teams — Hyper Agile & Well Oiled Execution by Ajay Shrivastava. He takes a perspective from a software developer role and recommends a Solver Team approach where every team member is accountable together and they each lead their respective stages of development.

Working With Cross Functional Teams: Master Effective Collaboration in the Workplace by Vinita Bansal. She reviews four common pitfalls with cross-functional teams, but then proposes six best practices, one of which is to establish a process for the team to make decisions, up-front.


Brainstorming quotes are from:

Boyd, Drew and Jacob Goldenberg. Inside the Box: A Proven System of Creativity and Breakthrough Results. Simon & Schuster, 2013.

Schirr, Gary. “Flawed Tools; The Efficacy of Group Research Methods to Generate Customer Ideas.” Journal of Product Innovation Management, vol. 29, 2012.

 

Collaborative risk management quote from:

Lindholm, C. and M. Host, “Risk identification by physicians and developers – differences investigated in a controlled experiment,” 2009 ICSE Workshop on Software Engineering in Health Care, Vancouver, BC, Canada, 2009, pp. 53-61, doi: 10.1109/SEHC.2009.5069606.

“Involving multiple roles, for example users and developers in the risk identification process, will result in a more complete set of identified risks than if only one role is included in the process.”

 


Episode Transcript

Let’s talk about cross-functional collaboration in product design, the challenges and how we can overcome some of those challenges and the reasons we would want to. Let’s talk more about it after this brief introduction.

Hello and welcome to Quality During Design, the place to use quality thinking to create products others love for and less. Each week we talk about ways to use quality during design and product development. I’m your host, Dianna Deeney. I’m a senior level quality professional and engineer with over 20 years of experience in manufacturing and design. I consult with businesses and coach individuals on how to apply quality during design to their processes. Listen in and then join us. Visit QualityDuringDesigncom.

Cross-functional collaboration. First, let’s talk about what a cross-functional team is. They are people that are assigned to a project to represent a certain function of the organization. They usually have decision-making capabilities when it comes to the project decisions and decisions about the product itself. Cross-functional team members may be representing the production and manufacturing facilities, marketing, reliability, quality and I would even consider project management as part of that cross-functional team. All of these different functions bring a different perspective of the project and the product when it comes to product development.

There are some challenges when working in a cross-functional team and I bet if you’ve been in product design, you’ve probably seen some of these challenges. For one, there’s a perception that too many voices just get in the way of productivity. I just need to know what I need to know so that I can design something already and we can move on with the project. And there is something to say about just lolling in a project and not making progress on it. And if you have too many cooks in the kitchen, so to speak, that does make it more challenging.

Another challenge with cross-functional teams is how do you work together? A lot of times, teams get together and do brainstorming sessions, and I mean true brainstorming sessions. I think we’ve all had some bad experiences with brainstorming, but there is a place for it. When brainstorming was introduced about 50 years ago, it was the thing to do, it was easy to set up and a way for people to talk together. Also, during those 50 years, people experienced a lot of difficulty with getting productive brainstorming sessions or having results of a brainstorming session that they could actually use. And there were lots of studies done on brainstorming and how brainstorming groups work. Some of the quotes from some of the research is, there’s no advantage to brainstorming group over a group of the same number of individuals working alone, or the brainstorming group came up with fewer ideas than the individuals, or just the quality and creativity of the ideas generated was actually lower. So some of our experiences with brainstorming may give us a negative viewpoint of cross-functional development.

The last challenge that I’ll mention is sort of an obvious one: is conflicts. Whenever people are working together, there’s going to be conflicts. From my experience and from other people’s experiences, those challenges center around not being aligned with the same priorities, there’s no end-to-end project leadership and not having a system that everyone worked within together. I’ll link to some articles in the podcast blog about these kind of challenges.

So why do we even bother doing cross-functional product design or getting together with our cross-functional teams for product design? Because, despite its challenges, which we can overcome, there are a lot of benefits that we don’t want to ignore.

For one, talking with people from different perspectives gives us a more complete picture, especially of the use space. Now, I’m a fan of cross-functional team collaboration, which is why I’m doing what I do. My main reason is that the different perspectives that each person brings from their respective areas of the business and also their independent individual experiences, helps create a more complete vision of a product and performance, both for the user and the risks it could introduce. People have studied this, too, involving multiple roles. For example, “Users and developers in the risk identification process will result in a more complete set of identified risks than if only one role is included in the process.”

Cross-functional collaboration also gives us clarity. Now, I’ve seen time and again the power of bringing people together to get a better understanding, greater alignment and improved designs, just to name a few of those benefits. With cross-functional collaboration, you’re communicating, interacting and talking with other people, so you have that space and that opportunity to get clarity on what it is you’re trying to do and your own goals and the goals of the greater project.

The last benefit of cross-functional collaboration that I’ll talk about in this episode is that, as a product designer, you have lots of internal customers. You might be responsible for the design aspect and making decisions about how it’s going to look, how it’s going to be made and the materials that it’s made from, but we all know that it takes a team of people to make a design idea a reality where someone is using and interacting with their product. In the field, product designers have many internal customers to their design contribution, meaning that the decisions that designers make affect many other people, including all of the people on the cross-functional team.

We know that team building, creation and management take skill and there’s a lot of methods and techniques for managing that. But you may be thinking, “Dianna, I’m not managing a team. I’m not the one who decides who’s on it. I’m assigned to a cross-functional team and I’m the product designer on the team.” Even still, we need to build something together with our cross-functional team.

I encourage you to facilitate meetings with a cross-functional team, so we need a way to work with our team on design decisions and design inputs. The challenge for product designers is in getting design inputs and their priorities based on things that matter. We’re talking about product design concepts. At this point in our project, we’ve identified a need. There’s a gap in the market, a potential new product, and we don’t have anything developed yet. This is really when we need to get clear on design inputs before we start the designing process.

What we can do with our cross-functional team is to collaborate using directed co-work. We work toward a common goal, something that is not so big as the project goal, but something smaller and more focused that can be achievable within one working session.
And we want to focus on the user. We’re designing and developing something for them, for them to be able to use it.
We’ll have a starting point. We don’t just show up with a cross-functional collaboration meeting with nothing. We do want to do some homework and not show up empty-handed.
And then have a roadmap to follow – a general direction that we’re taking, the group prompted questions, scenarios within which groups can be creative…

We’re really collecting our design inputs with our cross-functional team in a collaborative co-work meeting.

What I’m not talking about is I’m not talking about design sprints, whether the agile kind or the sprints product development kind, where you develop something in a week. I’m not talking about designing something together with a team. I am talking about exploring the use space and the concept space with our team for design inputs. The other thing I’m not talking about is I’m not talking about that typical brainstorming session that we mentioned earlier. There are elements of creativity and some brainstorming techniques, but it’s within a structure. Having structured working meetings is much better than sharing reports where marketing creates a market needs analysis, writes it up in a report and then throws it over the wall to the engineering and design department.

Because our structured meetings are going to give us an opportunity to talk with and better understand the perspectives of our cross-functional teammates. That is going to give us easier buy-in on our design ideas that we’re going to be making later, because we made them part of the design process. We’re also going to avoid surprises because we’ve verified and checked and left room to explore interpretations and hidden problems in the use space, things that alone we wouldn’t have noticed, but together we figured out.

As much as the members of our cross-functional team is part of the project, they do have their particular goals and they focus on their own particular part of the project or product. We just need to recognize that.

Our goal as a product designer is to give them opportunities to talk together and with us so that we can gather design inputs. And that’s really what we want are the design inputs against which we can create a great design.

That may seem selfish that we’re gathering our design inputs and identifying more opportunities for design options, but it really isn’t selfish because the rest of the team is also getting the inputs they need. Manufacturing production is getting more information about what they may need for their manufacturing plan. Marketing is getting more clarity for their marketing plans. Reliability is gaining an understanding of some of the use space and use environment and limitations. Quality is getting an idea of what quality measures may be important for the user, and project management is getting an understanding of where there could be project risks.

As a product designer, it’s really our responsibility to ask our cross-functional team for these inputs, because they are the internal customers or they represent our end users, which are our external customers.

So what’s today’s insight to action? If you approach collaboration in a structured way, with questions already formed and a way to communicate and facilitate your meeting so that you get the design inputs that you need, you’re going to have more success with getting the design input that you need and you’ll have a more successful design because of that.

Next week, we’re going to be talking about leveraging proven frameworks for concept development, so we’re going to be getting into some of these different frameworks and structured meetings that you’ll be able to use in working with your cross-functional team.

At QualityDuringDesigncom, under training, there is a free lesson “Engineering Products from a Concept Space”. It’s a video introduction to the use space and some of these frameworks that we’ll be talking about next week. You get access to an online portal where you’ll be able to log in time and again to view the video, read the transcript or get the downloads. I look forward to meeting you here next week. This has been a production of Deeney Enterprises. Thanks for listening.

Filed Under: Quality during Design

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