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:

Have a Program, Not Just an Agenda

In the modern organization, it's common to have meetings in which some people have never met — and some never will. For these meetings, which are often telemeetings, an agenda isn't enough. You need a program.

Coping with Layoff Survival

Your company has just done another round of layoffs, and you survived yet again. This time was the most difficult, because your best pal was laid off, and you're even more fearful for your own job security. How can you cope with survival?

The Ups and Downs of American Handshakes: I

In much of the world, the handshake is a customary business greeting. It seems so simple, but its nuances can send signals we don't intend. Here are some of the details of handshakes in the USA.

Workplace Memes

Some patterns of workplace society reduce organizational effectiveness in ways that often escape our notice. Here are five examples.

Entry Intimidation

Feeling intimidated about entering a new work situation can affect performance for both the new entrant and for the group as a whole. Four trouble patterns related to entry intimidation are inadvertent subversion, bullying, hat hanging, and defenses and sabotage.

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

Forthcoming issues of Point Lookout

Coming January 29: Higher-Velocity Problem Definition

Typical approaches to shortening time-to-market for new products usually involve accelerating problem solving. Accelerating problem definition can also help. Available here and by RSS on January 29.

And on February 5: Unrecognized Bullying: I

Much workplace bullying goes unrecognized. Three reasons: (a) conventional definitions of bullying exclude much actual bullying; (b) perpetrators cleverly evade detection; and (c) cognitive biases skew our perceptions so we don't see bullying as bullying. Available here and by RSS on February 5.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 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 June 29, 2017, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.