Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 21, Issue 11;   March 17, 2021: Facts, Opinions, Estimates, and Desires

Facts, Opinions, Estimates, and Desires


One reason why resource allocation debates can become so difficult is confusion about the differences among facts, opinions, estimates, and desires. Clarifying their differences can reduce the length and intensity of resource allocation debates.
A U.S. 100-dollar bill made into a jigsaw puzzle

A U.S. 100-dollar bill made into a jigsaw puzzle. It serves nicely as a metaphor for the problem of resource planning in the context of multiple competing projects

In project-oriented organizations, the appetite for new projects can be insatiable. We often seem to have more work to do than we can support with the people, equipment, and financial resources we have. To deal with what's commonly called resource contention we try to determine who and what will be available, when they will be available, and for how long they will be available. Making these projections requires hard data, excellent judgment, some arithmetic, and an understanding of estimation. Using these projections responsibly requires an understanding of the business objectives of the projects in question.

Rarely do we get all this right. That's why an ongoing activity in many project-oriented organizations is resource allocation — a more accurate term is probably resource reallocation. One factor that leads us to mis-allocate resources is confusion about the distinctions among facts, estimates, opinions, and desires. That confusion causes our debates about resource (re)allocation to lead to conclusions that fit our circumstances less well than we need.

A program to avoid these outcomes can begin with understanding these four terms, understanding how they are commonly misused, and understanding the consequences of their misuse.

Facts are bits of data that can be objectively verified. Verification methods vary. They include measurement, observation, and confirmation by trusted sources.
In oppositional debate, fact denial is a tactic often employed to advantage. Usually, the denier states an opinion, representing it as fact, in contradiction to the fact the denier wants to deny. For example, if two advocates of two different projects are in contention for portions of the same resource pool, one of the advocates might contend that a particular technology proved problematic in another recent project because the skill sets required for its use are so rare that the organization was unable to recruit staff with expertise in its use. To deny this fact, the opposing advocate might claim that the recruiter used by the organization was incompetent. Scarcity of qualified individuals is an objective, measurable fact, but assessing the competence of the recruiter is more likely to be based on opinion. Still, the fact denier can prevail if the debaters don't recognize that an opinion is not a fact.
If denying the facts fails, a contender might raise questions about the reliability of verification methods for particular kinds of facts. Indeed, questioning verification methods is a tactic often employed to convert facts into opinions for purposes of the debate at hand. Trusted human sources can be particularly vulnerable. Instead of questioning the fact, the skeptic can attribute nefarious motives to anyone who claims to offer verification of the fact. To limit the effectiveness of this tactic, begin the debate by agreeing on a set of verification methods. For example, when choosing a source for training, start by agreeing on a list of acceptable certifying agencies.
Opinions are statements that cannot be verified (or cannot be verified in the time available) by objective measurement, observation, or trusted sources. For example, personal likes and dislikes are opinions. More to the point for the context of resource allocation in project-oriented organizations, opinions are participants' inclinations or disinclinations based on personal experience or reports of experiences of others. For example, a statement of opinion is, "As a programming language C is beginning to show its age." A statement of fact is, "C was first standardized in 1989 when the American National Standard Institute (ANSI) published the standard known as ANSI X3.159-1989."
Not all opinions are preferences. Some are beliefs. Key phrases that indicate that a statement is an opinion, and not a fact, include, "I think…," "I believe…," "I seem to recall that…," and "I've heard that…."
Among the Fact denial is a tactic often employed to
advantage. In Fact Denial, the denier
states an opinion, representing it as
fact, in contradiction to the fact
the denier wants to deny.
opinions that perhaps present greatest risk to healthy debate are those opinions whose authors believe they are stating facts. Such opinions present risk to the health of debates because the authors of these opinions-as-facts don't allow for the possibility of legitimate but contradictory opinions of others. This attitude can seem to others to be arrogant and disrespectful, which to some is justification for retaliation. Over time, with a repeated pattern of opinion delivered as fact, the strain can grow until people lose control and toxic conflict erupts.
Cultural norms can be helpful in protecting against this pattern. But norms are usually voluntary, and they survive best in an enlightened culture. When everyone understands what a norm provides, they're more likely to abide by it.
Resource planning requires projections of resource needs for activities underway and activities about to be undertaken. Those projections are based on estimates of the kind and scale of the effort required by those projects.
Estimates are neither fact nor opinion. They are a synthesis of both. Those who develop estimates rely on facts such as defined approaches to projects, and experience data from other projects. And they rely on opinions such as subjective assessments of the difficulty of tasks, or the time or effort required for finding the people needed to carry out those tasks.
But because estimates aren't facts, people who are dissatisfied with the implications of a particular estimate sometimes treat that estimate as if it were just another opinion, like the opinion, "I dislike raspberry ice cream." Unlike personal opinions, we dismiss unwelcome estimates at our peril.
A serious estimate is far more than an opinion, for two important reasons. First, if the activity being estimated is eventually undertaken, the actual values of the quantities estimated — financial expenditures and time taken — can be compared to the estimates. No one expects exact agreement between estimates and actuals, but the differences must be within tolerable limits. Because the professional reputations of the people who developed the estimates are at stake, estimators usually take care to make the estimates as realistic as possible.
Second, developing a serious estimate requires research. Portions of the estimate must be based on data from previous efforts and data pertinent to the activity in question. Estimators use that data, after making adjustments for current particulars. They might even employ sophisticated mathematics to make their projections. Except in rare cases, it's foolhardy to imagine that one can find fault with an estimate by simply examining the estimator's results.

Finally we come to our fourth item: desires. Those engaged in resource planning debates often have in mind their own preferred outcomes — their own desires. Many have strong attachments to particular projects. They want the available resources to be allocated in such a way that the projects they prefer receive support.

If the resources available aren't sufficient to support every desire of every debate participant, the pressure on all concerned escalates. Participants begin to regard their own opinions as facts. Participants begin to regard an estimate as just one more opinion. And projects that the organization cannot afford to undertake are given a green light with inadequate resources.

Desires therefore can bend the results of these debates away from what is best for the organization. People treat opinions as facts, or they treat estimates as opinions. Watch the resource debates in your organization. If you have an opportunity, you might be able to help others distinguish among facts, opinions, estimates, and desires. Go to top Top  Next issue: Learning-Averse Organizations  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Your comments are welcome

Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Effective Communication at Work:

Cheese and crackersWhen Naming Hurts
One of our great strengths as Humans is our ability to name things. Naming empowers us by helping us think about and communicate complex ideas. But naming has a dark side, too. We use naming to oversimplify, to denigrate, to disempower, and even to dehumanize. When we abuse this tool, we hurt our companies, our colleagues, and ourselves.
Former Illinois Gov. Rod BlagojevichMasked Messages
Sometimes what we say to each other isn't what we really mean. We mask the messages, or we form them into what are usually positive structures, to make them appear to be something less malicious than they are. Here are some examples of masked messages.
Two barnacles affixed to the shell of a green musselGetting Into the Conversation
In well-facilitated meetings, facilitators work hard to ensure that all participants have opportunities to contribute. The story is rather different for many meetings, where getting into the conversation can be challenging for some.
A lightning storm over New York CityComfort Zone Discomfort
The phrase "comfort zone" is a metaphor that can distort how we think about situations in which we feel comfortable and confident. Here are four examples illustrating how the metaphor distorts our thinking.
The mural on the wall of the Cambridge firehouseThe Major Annoyance of Mini-Digressions
Digressions are expensive. They limit progress in meetings. They're most noticeable when they deflect the entire meeting from its stated purpose. There is another kind of digression that's less noticeable, more common, and just as costly.

See also Effective Communication at Work and Workplace Politics for more related articles.

Forthcoming issues of Point Lookout

A well-festooned utility poleComing June 26: Additive bias…or Not: I
When we alter existing systems to enhance them, we tend to favor adding components even when subtracting might be better. This effect has been attributed to a cognitive bias known as additive bias. But other forces more important might be afoot. Available here and by RSS on June 26.
A close-up view of a chipseal road surfaceAnd on July 3: Additive bias…Not: II
Additive bias is a cognitive bias that many believe contributes to bloat of commercial products. When we change products to make them more capable, additive bias might not play a role, because economic considerations sometimes favor additive approaches. Available here and by RSS on July 3.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

Reprinting this article

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.