Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 2, Issue 4;   January 23, 2002: Start a Project Nursery

Start a Project Nursery

by

In a Project Nursery, professionals from across the entire organization collaborate to conceive of new projects. When all organizational elements help decide which projects to investigate, the menu they develop best suits organizational needs and capabilities.

Do you know how many projects are underway in your organization? Make sure you include those that are still in gestation. If you make a list, you'll likely be surprised at how many there are.

Stuffed bearsYou'll be even more surprised at how many of the early-stage projects — those in gestation — are "off the books" and therefore out of control. Many of these are simply impractical. They aren't bad ideas, necessarily, but they're out of reach of the organization or its customers.

Every project began when someone — or maybe a few people — thought of an idea, talked about it with others for a while, and convinced the organization to back it. While technical organizations, such as IT or Product Development, can usually generate a vast array of ideas for projects, those ideas have a predominantly technical slant. Some ideas are beyond the organization's capacity to exploit. At the same time, other simpler ideas that could truly transform the organization and its markets are overlooked.

A Project Nursery fosters collaborations of professionals from across the organization — technologists, marketers, customer service experts, account executives, senior managers, infrastructure specialists, and administrators. When all organizational elements help decide which projects to investigate, the menu they develop better suits organizational needs and capabilities.

The Project Nursery works, in part, because it provides ready access to three bodies of knowledge.

Every project began
when someone thought of
an idea and convinced
the organization
to back it
Market trends
What customer need will the project satisfy? Will customers care? Will customers understand the offering, or will they need educating? Example: if we eliminate paper forms internally, and move to electronic signatures for internal requisitions, how can we ensure that people will stop printing copies for their files?
Infrastructure trends
What elements of the delivery, usage, or production context are needed for project success? Will they be present? At what cost? Does the customer have all the skills and facilities needed to make use of the output of the project? If not, what do they require? Example: We can put streaming video on our Web site, but do our customers have fast Internet connections?
Organizational trends and capabilities
Is the project in alignment with organizational intentions? If other ideas are competing for organizational resources, can we forge alliances somehow? Are the needed organizational capabilities available? If not, can we acquire them somehow? Example: Before we consider enhancing the Marigold product line with Internet options, are we certain that Customer Support has enough Internet capacity to support the enhancements?

Since all affected constituencies participate in the activities of the Project Nursery, the projects proposed are more likely to take into account the needs of those constituencies. And a project that has received good care in a well-staffed Project Nursery is less likely to later end up in the Project Emergency Room. Go to top Top  Next issue: Become a Tugboat Captain  Next Issue

Rick BrennerThe article you've been reading is an archived issue of Point Lookout, my weekly newsletter. I've been publishing it since January, 2001, free to all subscribers, over the Web, and via RSS. You can help keep it free by donating either as an individual or as an organization. You'll receive in return my sincere thanks — and the comfort of knowing that you've helped to propagate insights and perspectives that can help make our workplaces a little more human-friendly. More

Your comments are welcome

Would you like to see your comments posted here? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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 Project Management:

US Space Shuttle LaunchSome Causes of Scope Creep
When we suddenly realize that our project's scope has expanded far beyond its initial boundaries — when we have that how-did-we-ever-get-here feeling — we're experiencing the downside of scope creep. Preventing scope creep starts with understanding how it happens.
The worldDispersity Adversity
Geographically and culturally dispersed project teams are increasingly common, as we become more travel-averse and more bedazzled by communication technology. But people really do work better together face-to-face. Here are some tips for managing dispersed teams.
Eugene F. Kranz, flight director, at his console on May 30, 1965, in the Control Room in the Mission Control Center at HoustonDesign Errors and Group Biases
Design errors can cause unwanted outcomes, but they can also lead to welcome surprises. The causes of many design errors are fundamental attributes of the way groups function. Here is Part II of our exploration.
Astronauts Musgrave and Hoffman install corrective optics during the Hubble Telescope's Service Mission 1How 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.
Opera house, Sydney, AustraliaLessons Not Learned: I
The planning fallacy is a cognitive bias that causes us to underestimate the cost and effort involved in projects large and small. Mitigating its effects requires understanding how we go wrong when we plan projects by referencing our own past experience.

See also Project Management and Project Management for more related articles.

Forthcoming issues of Point Lookout

A game of Jenga underwayComing September 4: Beating the Layoffs: I
If you work in an organization likely to conduct layoffs soon, keep in mind that exiting voluntarily before the layoffs can carry significant advantages. Here are some that relate to self-esteem, financial anxiety, and future employment. Available here and by RSS on September 4.
A child at a fork in a pathAnd on September 11: Beating the Layoffs: II
If you work in an organization likely to conduct layoffs soon, keep in mind that exiting voluntarily can carry advantages. Here are some advantages that relate to collegial relationships, future interviews, health, and severance packages. Available here and by RSS on September 11.

Coaching services

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

Reprinting this article

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

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
52 Tips for Leaders of Project-Oriented OrganizationsAre your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around.
Reader Comments About My Newsletter
A sampling:
  • Your stuff is brilliant! Thank you!
  • You and Scott Adams both secretly work here, right?
  • I really enjoy my weekly newsletters. I appreciate the quick read.
  • A sort of Dr. Phil for Management!
  • …extremely accurate, inspiring and applicable to day-to-day … invaluable.
  • More
101 Tips for Managing ConflictFed up with tense, explosive meetings? Are you the target of a bully? Learn how to make peace with conflict.
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.
Comprehensive collection of all e-books and e-bookletsSave a bundle and even more important save time! Order the Combo Package and download all ebooks and tips books at once.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!