Paradoxical Policies: I

Paradoxical policy is policy that gets in the way of reaching objectives we say we want to reach. With a little thought, we can grasp how counter-productive — in some cases, how dumb — these policies are. But even when we perceive the paradox in a proposed policy, we can have difficulty preventing its deployment. A simple personal example is procrastinating studying for an exam, and then, with the exam approaching, cramming so much that for lack of sleep that we flunk the exam.

For organizations, paradoxical policies are more complicated. An example: To reduce expenses, the company sets a maximum money value for petty cash purchases. But the maximum is so low that the total cost of purchasing a heavy-duty stapler is three times the cost of the stapler, if you include the cost of processing the requisition form necessitated by the new policy.

Here's a collection of paradoxical policies, anonymized to protect the innocent.

• To prevent using company telephones for personal toll calls, everyone is required to review their toll calls for "business relevance" each month. They then pay for nonbusiness calls by check, which in most cases costs more to process than the face amount of the check.
• To control personal toll calls made from conference rooms, conference room telephones are disabled for outgoing toll calls. Therefore, conference calls must be made from personal offices, rendering unusable the electronic whiteboards that were recently installed in conference rooms.
• To reduce Paradoxical policy is policy
  that gets in the way of
  reaching objectives
  we say we want to reachpilfering of laptop computers, laptops are locked to the floor with steel cables, making them no longer portable. If you actually want to take one somewhere, you submit a requisition two business days in advance. This is so inconvenient that most people submit their laptop removal requisitions every two days automatically using an app written by someone in IT who chooses to remain anonymous.
• To create more parking spaces at ground level, visitor parking was eliminated. Visitors must now park in the employee garage, which is access-controlled by a gate. Employees expecting visitors must explain to the visitors that they can park in the "Fire Lane" while they get a visitor pass from Security that enables them to pass through the electric gate into the employee garage. This procedure has not been submitted for approval of the city Fire Department.
• Human Resources has installed a performance management system designed to weed out the "bad employees," which enables tracking the number of employees discharged or reassigned because of substandard performance. Supervisors are therefore required to identify "bad employees." The unintended consequence of this policy is that the new performance management system is deemed successful only if supervisors identify a sufficient number of "bad employees," whether or not there really are any.

Next time we'll look at policies that directly affect projects. Meanwhile, if you've encountered paradoxical policies in your own experience, please send them along. I collect them.   Next 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

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:

The Shape of the Table

Not only was the meeting running over, but it now seemed that the entire far end of the table was having its own meeting. Why are some meetings like this?

The True Costs of Indirectness

Indirect communications are veiled, ambiguous, excessively diplomatic, or conveyed to people other than the actual target. We often use indirectness to avoid confrontation or to avoid dealing with conflict. It can be an expensive practice.

Changing the Subject: I

Whether in small group discussions, large meetings, or chats between friends, changing the subject of the conversation can be constructive, mischievous, frustrating, creative, tension relieving, necessary, devious, or outright malicious. What techniques do we use to change the subject, and how can we cope with them?

The Deck Chairs of the Titanic: Strategy

Much of what we call work is about as effective and relevant as rearranging the deck chairs of the Titanic. We continue our exploration of futile and irrelevant work, this time emphasizing behaviors related to strategy.

Paid-Time-Off Risks

Associated with the trend to a single pool of paid time off from separate categories for vacation, sick time, and personal days are what might be called paid-time-off risks. If your team must meet customer expectations or a schedule of deliverables, managing paid-time-off risks can be important.

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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