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 103 What to do for Effective and Efficient Working Meetings

What to do for Effective and Efficient Working Meetings

We all like effective and efficient working meetings.

What do we do to plan them, or how do we improve our recurring ones?

Are we prepared to do things differently? If so, we can collect information so we know what we want to improve and by how much.

We talk about best practices of meeting evaluations for those that we plan and facilitate and those recurring team meetings.

 

 

View the Episode Transcript

 


What about your meetings now? Do you think WHAT you do (its effectiveness) needs to be improved? Or HOW you do it (its efficiency) could be better? What statement would you first put on your evaluation form?

Example Efficiency Statements

  • good time management
  • good meeting pace
  • having clear purpose
  • having and following agenda
  • full participation of all attendees
  • staying on topic
  • good communication between attendees
  • staying on schedule with project plan

Example Effectiveness Statements

  • working on the right things
  • accomplishing assigned work
  • focusing on work processes and system issues
  • looking for root causes
  • using data
  • involving the right people

These examples were taken from: Tague, Nancy R. The Quality Toolbox, 2nd ed. ASQ Quality Press. 2005. pp. 347-348.


Other Quality during Design podcast episodes you might like:

Use Meetings to Add Productivity

Get Clarity on Goals with a Continuum


Episode Transcript

We all like to be part of meetings that are effective and efficient, right? Some meetings are opportunities to get alignment and make decisions. Some are working meetings all involve our time and we’re all really busy, so we want our time spent in meetings to be useful. As an attendee, what would you think about being able to give your feedback on that, on how effective and efficient the meeting was? Would you appreciate the opportunity? Would you be more engaged the next time? Especially if you saw changes to make it better? Would you look forward to joining this person again? Because you know they’re not just trying to get through stuff. They want you to be involved that your opinion matters. Let’s turn it around. What about when you are the meeting host? Now it’s another level of scary because you are asking for a feedback and are expected to change because of it, but when we do it, it will have the same effect on our teammates that we just talked about. They’ll be more engaged, you’ll get more out of it and you’ll get better at it. Let’s talk more about the steps we can take for effective and efficient working meetings after the brief introduction.

Hello and welcome to Quality During Design, the place to use quality thinking to create products, others love for less. Each week we talk about ways to use quality during design, engineering, and product development. My name is Dianna Deeney. I’m a senior level quality professional and engineer with over 20 years of experience in manufacturing and design. Listen in and then join us. Visit quality during design.com.

Do you know what 12 things you should have before a design concept makes it to the engineering drawing board where you’re setting specifications. I’ve got a free checklist for you and you can do some assessments of your own. Where do you stack up with the checklist? You can log into a learning portal to access the checklist and an introduction to more information about how to get those 12 things. To get this free information, just sign up@qualityduringdesign.com. On the homepage, there’s a link in the middle of the page. Just click it and say, I want it.

Part of quality during design is facilitating discussions with the cross-functional team, getting their input in work time toward design inputs, which is what we want for designs, and then checking in during development for buy-in and approval of how the design is being engineered and the results of tests, things like that. A good meeting takes planning. As part of the planning, we think ahead about what feedback we want from our attendees and when we’re going to ask it. Oh, I know it might seem cringey like you’re entering into a popularity contest or looking to bolster your confidence or an even more uncomfortable thought that everyone is secretly your enemy and wants you to feel bad and give you really low ratings. Here’s the thing. You are in control of what you ask, how you ask it and what you do with the information, especially if you’re the one facilitating the meeting.

Your mindset is a big part of having the confidence to even just ask. So take a growth mindset. It’s an opportunity to learn and do better and yes, be prepared to be surprised. The important parts are to ask, review the feedback and change your approach the next time if you need to or if you get glowing reviews. Keep doing what you’re doing. So how do we go about doing this? Are we just supposed to pleasantly surprise our team with a feedback form at the next meeting? Well, this depends. If this is a routine team meeting that we’re talking about, then you should approach your team with this idea. I mean, the rule of thumb here is that the team is in charge of the team meetings. Part of the idea of a meeting evaluation is giving the team members some power or say into what’s covered in the meeting and how it’s covered.

Creating a meeting evaluation, discussing the answers and deciding on changes can be a team activity. It would just be part of the agenda. As you do them, you’ll get better at them or decide you don’t need to do them so often. On the other hand, if this is a meeting or a series of meetings that you’re putting together, you’re planning it, setting the agenda and facilitating it, then just make it part of your meeting agenda. You plan for a meeting evaluation ahead of time and you work it into your meeting. When does a meeting evaluation fit into the meeting? Is it at the end of the meeting? Well, really we wanna ask ourselves when do we wanna act on the results of it? Remember that feedback is a gift. So what are you going to do with this gift? You’ll want to adjust what and how you do things with this feedback.

Let’s say you’re planning for a long working meeting with a break for lunch. Then you may wanna consider doing a meeting evaluation just before break. You can review them to see where you have low scores or scores where they’re widely different. Some are a one and some are a five. If you want. When everyone gets back from lunch, you can share some of the results and let them know what you plan to change in the next half of the meeting. You can also ask for suggestions. What are some of your ideas for how we could do things differently to make this meeting more effective and efficient? Remember, this isn’t a show, it’s a working meeting for collaboration. Beyond having the right mindset and an idea of how we want to act on its results, what are some good guidelines for a meeting evaluation? We’re going to have a rating scale and a short list of statements to look at it.

It looks really simple, but it does take a little bit of intentional action and thoughtfulness on our part to really put together a good evaluation form. Well, first about the scale. We have a scale for agree up to disagree. One to five is typical. It doesn’t matter which under the scale is agree in which is disagree. Just be consistent. I tend to rank good things higher. We want something other than a yes or a no because we’re talking about working meetings and team dynamics and planning. We want those shades of gray so we can do more with a scale of one to five, then we can with the black and white. The scale affects how we word our statements too, which is the other thing that we need for our evaluation form. We wanna write these evaluation statements so the most agreeable response is on the same end of the scale or if you’re a pessimist, the most disagreeable response is on the same end of the scale.

For example, say we have two statements. The first statement is state on topic with an agree or disagree, and the other statement was pace was too slow with an agree or disagree. These won’t really work together on the same evaluation form cuz it’s making it hard for ourselves. If we got state on topic and we got all agrees, that means it was a good thing. If we asked if pace was too slow and we got all agrees, that means it’s a bad thing. They both get a high rating, but one is great and the other one is not so great. So that’s what I mean by writing them so that the most agreeable response is on the same end of the scale. In this example, we could use stay on topic and then change the second one to good meeting pace. If our attendees rate both of these as agree, that means that they’re both a good thing and what type of questions do we wanna ask?

Well, we really want to know the team effectiveness and efficiency. Effectiveness is what was done and the efficiency is how it was done. Here are some examples of good efficiency questions for a meeting evaluation form, good time management, good meeting pace, having a clear purpose, having and following an agenda. Full participation of all attendees, staying on topic, good communication between attendees and staying on schedule with the project plan. Examples of effectiveness statements could be working on the right things, accomplishing assigned work, focusing on work processes and system issues. Look for root causes, using data involving the right people. Those are some examples of the statements we could list on our meeting evaluation form. How many statements do we ask our attendees to rate? Cuz I rattled off a pretty long list of statements there. You have to think about what do you wanna know or what are you willing to act on right now?

If your team decided to do meeting evaluations, then you all might wanna choose one or two aspects of what you think would make a better team meeting. Take baby steps with a mind of continuous improvement. If someone says, our meetings always run over, then you can stick to an efficiency evaluation, like good time management. If someone says, I don’t even know why we’re meeting so often, that might translate to an effectiveness statement, like focusing on work processes and system issues. In a team setting, we’re setting team goals. It’s not any one person’s problem to fix. Do the two question evaluation, review the low score or the statements that have widely different results or compare it to the last meeting. Are we doing better? If not, what can we do better? Still get the team’s input and share in the responsibility of the effectiveness and efficiency of their meeting.

For example, we did our evaluation and we decide that we still don’t have good time management. We don’t wanna point a finger and tell any individual team member to do better. For example, we don’t wanna blame Susie, the project manager. Instead, we suggest a time limit on each agenda topic that everyone targets and then we could nominate a timekeeper or invite someone else to the meeting to be a timekeeper. Are we still having trouble focusing on work processes and system issues during the meeting? Don’t blame or point fingers again, instead, suggest a parking lot for issues that get off topic. Anyone can say, I think we’re getting off topic and write something in the parking lot. This is why it’s a good idea to involve the team about meeting evaluations when and how to do them and the evaluation criteria. After a while, you may have mastered these two things that you wanted to improve about the meetings.

What are two more things you think you can work on to improve? In this case, keep the evaluation, but change the statements. Refocus what it is you want to make improvements on. What if this meeting evaluation is for your own series of workshops? The same questions apply. What do you want to know or what are you willing to act on right now? Consider that, then plan your meeting evaluation, what you’ll ask, when you’ll ask it and what you’ll do with the information.

What’s today’s insight to action? Effective and efficient teamwork is a target for most people, attendees and facilitators alike. Part of engineering a product is cross-functional teamwork and part of quality during design is to facilitate some of those meetings. If we want better meetings, we need to understand what we want to improve and how much we need to improve it, and meeting evaluation is a way to set targets and collect data so we can do better.

If you like this topic or the content in this episode, there’s much more on our website including information about how to join our signature coaching program, the quality during design journey. Consistency is important, so subscribe to the weekly newsletter. 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