🔍 > Lean Terms Directory

Objective vs. Subjective

Last updated by Jeff Hajek on December 21, 2020

Being able to recognize objective vs. subjective information is an important skill for individuals in Lean companies.

Objective vs. Subjective Definitions

  • Objective: Information or data that is based in fact. Often numerical. Can be verified by an independent third party. Example: Math tests.
  • Subjective: Information or opinions that are open to interpretation. Generally filtered through the eyes of the person collecting or presenting it. Example: Literature essay tests.
Lean Terms Videos

Lean Terms Discussion

As a general rule, objective facts are much better than subjective information for decision making in continuous improvement efforts. Objective facts are indisputable. The time a process takes, the frequency of stock outs, and a part’s diameter can all be measured. Any trained person can take the same measurement and come up with the same result.

That measurability and repeatability makes the information extremely useful when changing processes. The before and after metrics can be measured, and there is objective proof of which is better.

More importantly, objective facts are more likely to have an absolute right and wrong than subjective opinions. Most people accept that higher quality is better than lower quality, all else being equal.

Subjective opinions, on the other hand, can lead to problems. While opinions are necessary in some situations, especially in interpersonal relationships and when deciding on high-level things like mission statements and values, in most cases, subjective thinking is a problem-solving handicap.

Opinions (subjective) tend to have a significant amount of bias, and are generally formed instinctively. Certainly, instincts can be honed and might frequently be accurate. Sometimes, though, they are at odds with what facts and data tell us. And the big problem is that we probably won’t know how accurate our instincts are until it is too late.

Problems with Subjective Thinking

Morgan D. Jones, a former CIA analyst, lists several reasons why subjective reasoning can be flawed (paraphrased from The Thinkers Toolkit):

  1. Emotions influence thoughts. Our mood can change the facts for us.
  2. We take mental shortcuts which skip facts.
  3. We overuse patterns. We assume that because something happened before, it will again.
  4. We make assumptions and are influenced by bias. Previous opinions of things influence what we are currently looking at.
  5. We create explanations where there are none. We don’t like vacuums. We fit explanations in, even if there is contradiction, because we don’t like that void.
  6. We weigh evidence we like more than that which we don’t. If something supports our belief, we will put more stock in that. This happens often in kaizen. If there is a glitch, it is weighed much more heavily than the successes by those that don’t want the change.
  7. We support our beliefs, even if others consider opposing evidence to be overwhelming. If we believe something in our hearts, we will not change, even with evidence against it. This is extremely common when trying to convince people to reduce lot sizes.

Of course, we do have to make some decisions based on subjective opinions. Hiring decisions, for example, while rooted in objective facts, ultimately come down to being a subjective choice about which candidate will best fill the job. We may score people, and try to apply a rigid system of evaluation, but a numerical decision laid on top of a series of opinions doesn’t magically become an objective fact.

Lean Terms Next Steps

Train yourself to use objective facts vs. subjective opinions when making decisions. There is certainly a place for subjective evaluations in personal relationships, but with most decisions, you will be well served to stick with facts and data.


2 Comments

Carol Dekkers · January 19, 2011 at 1:25 pm

Great post. So often, software developers complain about (the business) management making decisions formulated mostly on opinion which as you point out can be fraught with error.

However, it is commonly a situation where “data” is presented to this same management without any indication of causality – which forces management to interpret as best they can. We in software development have an obligation to present information (objectively analyzed data showing causality) so that management can make objective rather than subjective decisions.

I’m going to use (with your permission and attribution) excerpts of your posting in my presentation to the ASQ Software Division next month where I will present about how to really show results of software quality.

Thanks for the post!

    Jeff Hajek · January 19, 2011 at 7:52 pm

    Carol,
    Thanks for the comment. You made me realize a major oversight in the term. I didn’t address the problem of subjective opinions being presented as fact. I’ll have to add that in at some point (though, in truth, I can’t remember the last time I actually did something ‘at some point’).

    Yes–feel free to use the excerpts. Nice to be able to help out a great group. (A plug is always appreciated!)

    By the way, I took a quick look at your blog. Can’t spend much time on it right now with a few client deadlines coming up, but the first impression was great. If anyone else wants to check it out, just click on Carol’s name above.

    Thanks again for the comment.
    Jeff

Leave a Reply

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