The field of vision of a horse. View a larger image. Horses have blind spots, front and rear. In their natural habitat of open range, they manage quite well, but in human-dominated environments, such as cities and villages, their blind spots leave them vulnerable. This vulnerability has given them a reputation for startling easily — a reputation that is likely undeserved, because it's probably due to the mismatch between the human environment and their natural habitat.
In the organizational environment, managers who choose to withhold from their subordinates information regarding reviews can, in effect, create blind spots for their subordinates. Those blind spots make their subordinates vulnerable, and once the pattern is evident, their subordinates can become skittish, exhibiting signs of stress arising from an acute sense of vulnerability. Performance declines are then inevitable. Image courtesy U.S. Federal Highway Administration.
A vignette common during performance review season goes like this. Michelle Manager visits Sam Subordinate's cube and says, "Morning Sam, come to my office and we'll do your review." Sam is taken by surprise. Arriving together in Michelle's office, Michelle says to Sam, "Have a seat," and hands him a two- or three-page document that he's seeing for the first time. "Have a look," she says. "Tell me what you think."
Sam reads eagerly at first, but slowly realizes that, far from singing his praises, this document is an indictment. It's a list of grievances he's never heard before. Many are gross distortions and some are just plain false. His emotions take over. He feels accused, hurt, and angry.
"There's a space at the end for your signature," says Michelle. "Signing doesn't mean you agree with every little thing, it just means you've read it." Defeated, Sam signs. The document enters his personnel folder.
Sam has been blindsided. Feeling helpless, he has surrendered. His personnel record now contains yet another review filled with falsehoods and distortions.
Blindsiding was once much more common than it is today, because law is developing regarding employee rights. The law is in a primitive state, and civil suits are still the main deterrent to performance review abuses. But a consensus is emerging about appropriate processes for conducting performance reviews. Here are the basics:
- Regular scheduling
- Reviews of employees in good standing occur at regular intervals — quarterly, semi-annually, or, at a minimum, annually. Employees who are on notice for performance issues might be reviewed more frequently.
- Fair notice
- The subordinate receives fair notice of review meetings. Subordinates with heavy travel schedules are reasonably accommodated.
- Written documentation
- Everything of significance is captured in writing, and signed by supervisor and subordinate to indicate not agreement, but acknowledgement that the document was presented. The two parties can negotiate the content, but each can also append their own views without editing by the other.
- Opportunity to prepare
- The subordinate receives a A consensus is emerging about
appropriate processes for conducting
performance reviewsdraft of the document far enough in advance to allow for preparation of rebuttals or appendices. The subordinate can prepare for the review on company time, at full compensation. - No hidden standards
- The review can fault the employee for failing to perform to standards only if those standards were previously documented. If a standard is revised between reviews, the employee is informed of the change, and has time to adapt to the new standard. At the next review, that revised standard applies only to employee performance during the period the standard was active.
- Fairness
- All standards are fairly applied to all subordinates equally, without discrimination as to race, sex, age, religion, ethnicity, or any other demographic factor.
How did you conduct you last review? Was it fair? Were any of these guidelines violated? 
First issue in this series 
Top 
Next Issue
Are 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? rbrenfHlRlTgqCIXkUHBTner@ChacrEuHRQPYVKkOucGfoCanyon.comSend me your comments by email, or by Web form.About Point Lookout
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 Personal, Team, and Organizational Effectiveness:
Shooting Ourselves in the Feet- When you give a demo to a small audience, there's a danger of overwhelming them in a behavior I call
"swarming." Here are some tips for terrific demos to small audiences.
Virtual Communications: II- Participating in or managing a virtual team presents special communications challenges. Here's Part
II of some guidelines for communicating with members of virtual teams.
Coping and Hard Lessons- Ever have the feeling of "Uh-oh, I've made this mistake before"? Some of these oft-repeated
mistakes happen not because of obstinacy, or stupidity, or foolishness, but because the learning required
to avoid them is just plain difficult. Here are some examples of hard lessons.
Communication Refactoring in Organizations- Inadequate communication between units of large organizations is one factor that maintains the dysfunction
of "silo" structures in large organizations, limiting their ability to act coherently. Communication
refactoring can help large organizations to see themselves as wholes.
Meeting Troubles: Collaboration- In some meetings, we collaborate not in reaching objectives, but in preventing our doing so. Here are
three examples of this pattern.
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
Coming April 30: On Planning in Plan-Hostile Environments: II- When we finally execute plans, we encounter obstacles. So we find workarounds or adjust the plans. But there are times when nothing we try gets us back on track. When this happens for nearly every plan, we might be working in a plan-hostile environment. Available here and by RSS on April 30.
And on May 7: Subject Matter Bullying- Most workplace bullying tactics have analogs in the schoolyard — isolation, physical attacks, name-calling, and rumor-mongering are common examples. Subject matter bullying might be an exception, because it requires expertise in a sophisticated knowledge domain. And that's where trouble begins. Available here and by RSS on May 7.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenfHlRlTgqCIXkUHBTner@ChacrEuHRQPYVKkOucGfoCanyon.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:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
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
Recommend this issue to a friend
Send an email message to a friend
rbrenfHlRlTgqCIXkUHBTner@ChacrEuHRQPYVKkOucGfoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
My 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!
Bad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we
love the work but not the job.Learn how to make your virtual global team sing.Are you managing a change effort that faces rampant cynicism, passive non-cooperation, or
maybe even outright revolt?Learn how to make meetings more productive — and more rare.