Paradoxical Policies: II

The tension between the inherent uniqueness of projects, and the need to formulate policy that applies to all projects, makes governance of project-oriented organizations challenging. For every policy proposed, it's easy to construct rare but potentially expensive scenarios in which compliance with policy leads to consequences that conflict with policy objectives. Here are four such scenarios, actually captured in the wild.

• A fast-moving desktop application software company with a fairly formal software development process acquires a smaller, entrepreneurial company with a hot product for mobile devices and a very informal development process. The acquired product team is directed to follow the acquiring company's formal process. It must develop a test plan, but it lacks the staff to do the work, and its request to hire three additional testing professionals has been rejected. To ensure compliance with the mandate, the acquiring company then assigns someone who knows little about testing mobile device software to write the test plan. The result is as horrendous as it is predictable.

• The project hasFor every policy proposed, it's
  easy to construct rare but
  potentially expensive scenarios
  in which compliance with policy
  leads to consequences that
  conflict with policy objectives been slipping, and another slip seems likely, but not inevitable. To avoid being forced to announce another slip, on Wednesday afternoon Management orders an emergency project status review (EPSR) to be held at an all-day Saturday meeting. All work halts immediately, as everyone fires up PowerPoint to prepare slides for the EPSR. The loss of three days of work makes another project slip inevitable.

• To monitor project health, bi-weekly status reports are required for all projects that are approved for spending against a budget. This includes some projects in which little activity occurs because they're waiting for some other effort's deliverables to arrive. In fact, the only activity that occurs in these projects is writing the bi-weekly status reports, which only adds to the data blizzard that buries the people who must review the reports, making it more difficult for them to monitor the health of projects.
• To reduce expenses, the company decides to run "lean and mean." It tracks skills utilization data to ensure that people with skills that are in high demand — and who are therefore compensated at rates above market — are actually using those skills in the projects to which they're assigned. Consequently, people with high-value skills are usually allocated to several projects. Those project managers must then coordinate schedules to avoid over-allocating people with high-value skills. But projects rarely keep to schedule, because, um, they're projects. When schedules change abruptly, the people with high-value skills become bottlenecks, and project schedule chaos ripples through the organization. These delays can cause significant lost revenue opportunities, vastly larger than the savings that were supposed to come from running "lean and mean."

Finding these situations is easier than avoiding them when we devise policy. Simulations can help. First 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.

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:

Tactics for Asking for Volunteers: I

CEOs, board chairs, department heads and team leads of all kinds sometimes seek people to handle specific, time-limited tasks. Asking the group for volunteers works fine — usually. There are alternatives.

Fill in the Blanks

When we conceal information about ourselves and our areas of responsibility, we make room for others to speculate. Speculation is rarely helpful. It's wise to fill in the blanks.

Reactance and Decision-Making

Some decisions are easy. Some are difficult. Some decisions that we think will be easy turn out to be very, very difficult. What makes decisions difficult?

Down in the Weeds: II

To be "down in the weeds," in one of its senses, is to be lost in discussion at a level of detail inappropriate to the current situation. Here's Part II of our exploration of methods for dealing with this frustrating pattern so common in group discussions.

The Goal Is Not the Path

Sometimes, when reaching a goal is more difficult than we thought at first, instead of searching for another way to get there, we adjust the goal. There are alternatives.

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

Forthcoming issues of Point Lookout

Coming May 29: Newtonian Blind Alleys: II

Some of our decisions don't turn out well. The nature of our errors does vary, but a common class of errors is due to applying concepts from physics originated by Isaac Newton. One of these is the concept of spectrum. Available here and by RSS on May 29.

And on June 5: I Could Be Wrong About That

Before we make joint decisions at work, we usually debate the options. We come together to share views, and then a debate ensues. Some of these debates turn out well, but too many do not. Allowing for the fact that "I could be wrong" improves outcomes. Available here and by RSS on June 5.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrennQDSufuHTcysJErCner@ChacWNJSrnsiavdWeiXToCanyon.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, USD 11.95)
• Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
• Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
• Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)

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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Power Affect: How We Express Our Personal Power

Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.

• A recording of a program presented 6:00 PM June 29 (Eastern Time), Monthly Webinar, Technobility Webinar Series. You can earn 1.0 Category 'A' PDU by viewing this program. View this program now.