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
    • 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
    • Asset Reliability @ Work
  • 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
      • 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
    • 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?
      • 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
    • 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 025 Do you have SMART ACORN objectives?

Do you have SMART ACORN objectives?

Objectives are goalposts of what it is we’re trying to accomplish. Though they’re only a part of planning a project, if we don’t have well-defined and clear objectives, it could lead to us not having the stellar project results we want. Our objective should be a SMART ACORN.  We review these two, complementing acronyms as ways to check that we’re setting up our project for success.

 

View the Episode Transcript

Use SMART to ensure we know how to define our tasks toward getting things done.

SMART: Specific, Measurable, Achievable, Relevant, Time-bound

Use ACORN to consider how a project objective will be measured and if it aligns properly with your group.

ACORN: Accomplishment, Control, Only Objective, Reconciliation, Numbers

A – Accomplishment – Does the goal describe results that can be verified (not behaviors)?

C – Control – Is the goal’s accomplishment within the group’s control?

O – Only Objective – Would we accomplish success if this were the only goal? Ensure goals are main goals; identify sub-goals separately.

R – Reconciliation – Will this goal interfere with another group, or is someone else already working on this?

N – Numbers – Can the goal be measured?

Citations

The ACORN test is published in this book: Tague, Nancy R. “ACORN Test.” Quality Toolbox. ASQ, 2005, pp. 93-95.

 

 

Episode Transcript

Are you getting started with a project? It could be a new design, a new test method, or continuous improvement. If so, you gotta have an objective, a definition of what it is you’re trying to accomplish. If it’s not defined…well, it could lead to getting results you weren’t aiming for or missing the results of what you’re trying to do. There is a check we should do with our objectives to make sure they’re set up to be the best they can be. Our objective should be a SMART ACORN. I’ll talk to you more about these two acronyms after this brief introduction.

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

Objectives are goal posts of what it is we’re trying to do. Though they are only a part of planning a project, if we don’t have well-defined and clear objectives, it could lead us to not having a stellar project. There are two checks to ensure objectives are set up properly, and they’re both acronyms: SMART and ACORN. I’ve found SMART in lots of places, but I’ve only seen ACORN in one. I like to combine them because they cover slightly different viewpoints of what a good objective should be. They don’t conflict; they complement each other. Let’s talk about both.

START is the one that you’re probably familiar with. Its acronym letters mean specific, measurable, achievable, relevant, and time specific or time bound. Let’s review each of these.

Specific. We need to get specific in our objectives in order to be able to plan and move ahead. Getting specific allows us to create tasks, assign people to them, and start setting target completion dates.

Measurable, our goals need to be measured. We need to major in our project to make sure we’re on the right path and so we know when we’ve reached success.

Achievable. Yeah, it’s great to set big goals. But since we need to break those big goals into little steps in order to achieve them or we need other groups to get there.

Relevant. Does our goal line up with our long-term objectives? Or, are we not on our way to where we need to be?

Time-based. Part of our goal needs to include a timeline for when we’re going to get it done. It needs to be realistic, but also a little aggressive. We want to get things done! Setting an end date keeps us motivated.

SMART is an acronym that most people are familiar with, and I bet you’ve probably heard of it before also.

ACORN is another measure of our objectives. It’s another acronym that stands for accomplishment control, only objective, reconciliation, and numbers. What’s different about ACORN (versus SMART) is it considers how a project objective will be measured and if it aligns properly with our group. The only place I’ve found ACORN published was in Nancy Tague’s Quality Toolbox book. I’ll include a citation about her book in the podcast blog. Let’s go over each letter of ACORN and talk about what it means for setting our objectives.

Accomplishment. Does the goal describe results that can be verified? We want goals where we can gather data, not have to rely on someone monitoring how people are acting or behaving. People are not a root cause and pointing fingers doesn’t help anyone.

Control. Is the goal’s accomplishment within the group’s control? Sometimes we can develop lofty long- term goals that are aligned with our company’s overall objectives. But if our project goals are outside of our control, then we’re going to have a tough time getting any project to a completion. If this is the case, we need to either shift our goal, or expand the project to include and get buy-in (and commitment) from the other groups that are needed. Because we will need their support to get it done.

Only objective. Would we accomplish success if this were the only goal? We need to check that our goal is a main goal: that if we meet this goal, we will consider it a success. If we must have subgoals, then we need to be sure to identify those separately.

Reconciliation. Will this goal interfere with another group, or is someone else already working on this? There may be a problem we’re trying to solve that could have several root causes spread or shared by different groups or departments. If one group is trying to solve their root cause and we start trying to solve our root cause, we could be undoing each other’s work or making our respective projects more difficult to complete. We may just need to be aware that we have to reconcile our project with another group’s project to get the best results.

Numbers. Can the goal be measured? This aligns a lot with SMART goals, doesn’t it? If it’s specific, measurable, actionable, realistic, and time based, we can measure it.

We can evaluate almost anyone’s objectives against the SMART objectives. We need to know more about our particular project to understand how well our objectives meet the ACORN acronym.

So, here’s a phrase we can remember: “Our objectives should be a SMART ACORN.” Before we finalize our objectives, we’ll run them through these two tests. If we do, we’re likely to be better set on a path towards success.

Please visit this podcast blog and others at qualityduringdesign.com. Subscribe to the weekly newsletter to keep in touch. If you like this podcast or have a suggestion for an upcoming episode, let me know. You can find me at qualityduringdesign.com on Linked-In, or you could leave me a voicemail at 484-341-0238. This has been a production of Denney Enterprises. Thanks for listening!

Filed Under: Quality during Design, The Reliability FM network

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 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

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

This site uses cookies to give you a better experience, analyze site traffic, and gain insight to products or offers that may interest you. By continuing, you consent to the use of cookies. Learn how we use cookies, how they work, and how to set your browser preferences by reading our Cookies Policy.