Turning the car key in the door lock, Marian was relieved that they'd finally agreed to get out for lunch, because she wanted a change of scene for the conversation she and Kevin and James were about to have. The door locks all clicked open, and the three of them hopped in.
"Where to," she said.
Kevin answered from the back seat: "You have to ask?"
Marian looked up at Kevin in the rear-view mirror. "Just trying to give you an opportunity for input," she replied. At the end of the loop road, she turned left towards Mike's, where they always went for lunch when projects were in trouble.
James began immediately. "I wish we'd found out about the Georgetown products before we did the Pyramid modules — we wouldn't be here now. But how could we have known?"
Kevin, of course, had the answer. "They could've told us," he said dryly. Marian and James laughed weakly.
"Yeah, there is that," Marian said. "But they've done this to us before. You'd think we would have learned by now."
Projects are full
of surprises — that's
them projectsIndeed. Projects are full of surprises — that's what makes them projects. Still, we can reduce the incidence of surprises by cleverly sequencing the project's tasks. Here are some tips for using schedule to manage risk.
- Avoid the logical-order trap
- Some projects impose a logical order on task sequence. A building, for example, has to have its foundation in place before the first structural elements go up. But unless the laws of physics intervene, keep an open mind about the order of things.
- Exploit leverage
- Give preference to tasks that reduce costs, either because they spin off tools you can use, or because you can learn something valuable, or because they provide a morale boost.
- Delay creating what you don't need
- Building or designing something before it's needed creates constraints through commitment. Delaying preserves flexibility.
- If you think something might be difficult, find out early
- Schedule the solutions to unsolved problems so that bad news arrives early, when you have time to sort out alternate approaches, and before other elements impose constraints.
- Use reconnaissance teams
- Designate teams to perform reconnaissance in force, looking for traps before the main body of the project reaches them. Give these teams enough budget to run tests that reveal weaknesses before you've made major commitments.
- Avoid resource optimization
- Shortening the critical path by optimizing resource allocation is a risky strategy. Most development projects aren't predictable enough for this kind of fine-tuning.
- Get comfortable with placeholders
- We use placeholders when scheduling requires them, especially in the critical path. But building placeholders is a wonderful way to reconnoiter — to find out about trouble early. Use them more often.
You can do the same things when you read. Sometimes reading the end first gives you a useful mental framework for the beginning and middle. If you're doing that right now, I hope you enjoy reading the beginning and the middle of this article. 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 welcomeWould you like to see your comments posted here? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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.
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 Project Management:
- Make a Project Family Album
- Like a traditional family album, a project family album has pictures of people, places, and events.
It builds connections, helps tie the team together, and it can be as much fun to look through as it
is to create.
- Design Errors and Groupthink
- Design errors cause losses, lost opportunities, accidents, and injuries. Not all design errors are one-offs,
because their causes can be fundamental. Here's a first installment of an exploration of some fundamental
causes of design errors.
- Unnecessary Boring Work: I
- Work can be boring. Some of us must endure the occasional boring task, but for many, everything about
work is boring. It doesn't have to be this way.
- False Summits: I
- Mountaineers often experience "false summits," when just as they thought they were nearing
the summit, it turns out that there is much more climbing to do. So it is in project work.
- How We Waste Time: I
- Time is the one workplace resource that's evenly distributed. Everyone gets exactly the same share,
but some use it more wisely than others. Here's Part I of a little catalog of ways we waste time.
See also Project Management for more related articles.
Forthcoming issues of Point Lookout
- Coming June 26: Appearance Antipatterns: I
- Appearances can be deceiving. Just as we can misinterpret the actions and motivations of others, others can misinterpret our own actions and motivations. But we can take steps to limit these effects. Available here and by RSS on June 26.
- And on July 3: Appearance Antipatterns: II
- When we make decisions based on appearance we risk making errors. We create hostile work environments, disappoint our customers, and create inefficient processes. Maintaining congruence between the appearance and the substance of things can help. Available here and by RSS on July 3.
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, 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
- 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.