A hummingbird feeding on the nectar of a flower. Nectar is a fluid rich in sugars, secreted by plants. It serves little purpose to the plant itself, except to attract pollinators, such as hummingbirds and insects, which consume it as fuel. Most plants are very particular — specific plant species often attract only one or a few different pollinating species. Pollination by traveling pollinators is one method plants use to gain access to pollen of other members of their own species. In effect, plants use nectar to acquire genes from other individuals of their own species — genes that might offer their offspring competitive advantage. In flowering plants, nectar is the incentive for animal species to provide transportation for those genes. Indeed, one way to look at sexual reproduction generally is that it provides a mechanism for rapid propagation of genetic innovation.
Encouraging cross-functional contributions within an organization can serve a similar function — it can make that organization more competitive, more quickly, and more cheaply than hiring consultants or acquiring competitors. Photo courtesy Natural Resources Conservation Service, U.S. Department of Agriculture.
In large projects or small, the need for the big idea is the same: one project, one big idea. That's one reason why organizations that tackle large projects have disproportionately smaller needs for new or big ideas.
Since large projects are more accessible to large organizations, those that tackle large projects tend to have more people, many of whom are very capable and creative. In large organizations, we find more people with new ideas that have more trouble finding truly receptive listeners. That causes some of them to try harder, further annoying the people whose jobs are to generate and champion ideas. Tensions develop, and frustration builds. Sometimes, good people leave.
There is a better way. It begins with the recognition that capable, creative people have good ideas — lots of them — and those ideas often apply to parts of the company other than their own. Here are some tips for crafting a large organization that can deal with unsolicited cross-functional contributions.
- Assign process and problem owners a responsibility to listen
- Sometimes people who "own" a particular process or problem can feel that contributions from others are infringements on that ownership.
- Make clear to everyone that responsibility for a process or problem includes responsibility to listen to and evaluate ideas from elsewhere in the organization.
- Make originality a pre-requisite
- Devise measures to control repetition and redundant suggestions. Deprecate rehashing of settled debates. One possibility: make previous contributions available to anyone contemplating making a contribution. Make the history anonymous if necessary.
- Requiring originality dramatically reduces the load on recipients. By assigning contributors responsibility for determining that their contributions aren't redundant or repetitive, we reduce the flow of contributions and improve their quality.
- Recognize that for new ideas, "not your job" is a toxic concept
- Recognize that for new
ideas, "not your job"
is a toxic concept - When we tell people, either explicitly or otherwise, that thinking about a particular process or innovation isn't their job, we're creating frustration and tension, and discouraging initiative.
- Sometimes, only the internal customers of a process can really see where it can be improved. And sometimes only people far enough away from a problem can see the solution. Contributions from afar are often critical to success.
- Provide nonbureaucratic, responsive contribution channels
- Since great people are always thinking, give them a way to pass their thoughts along. It can be as simple as an email address or a wiki. Or it can be an actual appointment with a person.
- Whatever you do, be certain that people feel heard. Automated responses are ineffective. Mechanisms that just listen without evidence of active consideration fool nobody.
Unless you own the idea-management process of your organization, beware. If you offer these ideas — or anything like them — they'll likely be received as unsolicited contributions. Tread lightly. 
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
Would you like to see your comments posted here? rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.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.
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:
Own Your Space- Since we spend so much of our waking lives in our offices, it's surprising how few of us take control
of our immediate surroundings. If you do — if you make your space uniquely yours — you'll
feel better about the time you spend at work.
Coping and Hard Lessons- Ever have the feeling of "Uh-oh, I've made this mistake before"? Some of these oft-repeated
mistakes happen not because of obstinacy, or stupidity, or foolishness, but because the learning required
to avoid them is just plain difficult. Here are some examples of hard lessons.
Wacky Words of Wisdom: III- Adages are so elegantly stated that we have difficulty doubting them. Here's Part III of a collection
of often-misapplied adages.
The Utility Pole Antipattern: I- Organizational processes can get so complicated that nobody actually knows how they work. If getting
something done takes too long, the organization can't lead its markets, or even catch up to the leaders.
Why does this happen?
Six Traps in Email or Text: II- Collaboration requires communication. For many, communicating often takes place in email and text message
systems. But much of the effort expended in communication is dedicated to resolving confusions that
we created for ourselves. Here are four examples.
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
Coming May 14: Working with the Overconfident- A cognitive bias known as the Overconfidence Effect causes us to overestimate the reliability of our judgments. Decisions we make based on those judgments are therefore suspect. But there are steps we can take to make our confidence levels more realistic, and thus make our decisions more reliable. Available here and by RSS on May 14.
And on May 21: Mismanaging Project Managers- Most organizations hold project managers accountable for project performance. But they don't grant those project managers control of needed resources. Nor do they hold project sponsors or other senior managers accountable for the consequences of their actions when they interfere with project work. Here's a catalog of behaviors worth looking at. Available here and by RSS on May 21.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
My 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!
Bad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we
love the work but not the job.Learn how to make your virtual global team sing.Are you managing a change effort that faces rampant cynicism, passive non-cooperation, or
maybe even outright revolt?Learn how to make meetings more productive — and more rare.