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."
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 welcomeWould you like to see your comments posted here? rbrenogMhuqCxAnbfLvzbner@ChacigAthhhYwzZDgxshoCanyon.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.
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.
More articles on Personal, Team, and Organizational Effectiveness:
- Favors, Payback, and Thoughtlessness
- Someone at work who isn't particularly a friend or foe has asked you for a favor. What happens if you
say no? Do you grant the favor? How do you decide what to do?
- Finding Work in Tough Times: Strategy
- If you're out of work and discouraged — or getting there — you're in great company.
Better than ever before. Getting back to work starts with getting to work on finding work. Here's a
collection of strategies for the job of finding work.
- Clueless on the Concept
- When a team member seems not to understand something basic and important, setting him or her straight
risks embarrassment and humiliation. It's even worse when the person attempting the "straightening"
is wrong, too. How can we deal with people we believe are clueless on the concept?
- Contextual Causes of Conflict: II
- Too often we assume that the causes of destructive conflict lie in the behavior or personalities of
the people directly participating in the conflict. Here's Part II of an exploration of causes that lie
- How to Get Out of Firefighting Mode: I
- When new problems pop up one after the other, we describe our response as "firefighting."
We move from fire to fire, putting out flames. How can we end the madness?
Forthcoming issues of Point Lookout
- Coming December 13: Contrary Indicators of Psychological Safety: I
- To take the risks that learning and practicing new ways require, we all need a sense that trial-and-error approaches are safe. Organizations seeking to improve processes would do well to begin by assessing their level of psychological safety. Available here and by RSS on December 13.
- And on December 20: Contrary Indicators of Psychological Safety: II
- When we begin using new tools or processes, we make mistakes. Practice is the cure, but practice can be scary if the grace period for early mistakes is too short. For teams adopting new methods, psychological safety is a fundamental component of success. Available here and by RSS on December 20.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenogMhuqCxAnbfLvzbner@ChacigAthhhYwzZDgxshoCanyon.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