My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD04787
CWCB
>
Floodplain Documents
>
Backfile
>
4001-5000
>
FLOOD04787
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/25/2010 6:47:15 PM
Creation date
10/5/2006 12:59:32 AM
Metadata
Fields
Template:
Floodplain Documents
County
Statewide
Basin
Statewide
Title
Colorado Association of Storm Water and Floodplain Managers 8th annual Conference
Date
9/22/1997
Prepared For
State of Colorado
Prepared By
CASFM
Floodplain - Doc Type
Educational/Technical/Reference Information
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
181
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br />. <br /> <br />Acknowledging everyone's input (prove that you are listening). <br />Separate the input process from the decision process, i.e., don't criticize or judge <br />anyone's idea when it is presented. Just wrIte it down and tell them it will be <br />considered. <br />State the "givens" up front. Let everyone know what is negotiable and what <br />isn't. Make sure everyone understands ane, agrees to these at the beginning of the <br />process, <br />Document the process, Write do\\n everyone's comments and keep them visible <br />throughout the process. When decisions are made, return to these conmlents and <br />show how you have responded to each item, <br />Be honest, sincere and realistic. You cannot meet eve'yone' s needs 100%, Be <br />honest about this from the beginning, What you can do is hear evervone equally. <br />and sincerely consider their concerns, <br />Remain objective. This can be difficult if you are the project manager. It often <br />helps to enlist a separate facilitator, whose main stake in the project is to obtain <br />consensus. This person can deflect melyou or us-vs, -them situations. <br /> <br />. <br /> <br />. <br /> <br />. <br /> <br />. <br /> <br />. <br /> <br />. Following Tlte Steps, By defIning clear steps for each part of the process. you can move <br />fommd one srep at a time and avoid being sidetracked, Typical steps might include: <br /> <br />. <br /> <br />State the problem. This includes the needs, the goals, and the "givens" for the <br />project. <br />Solicit input. Listen objectively and witholt criticism. Carefully record the input, <br />Develop alternatives. This can often include a hands-on work session. where <br />everyone is invited to help generate solutions, This allows people to understand <br />that the problem is more complex than their own smgle issue. and that other <br />people have ,ssues that must be addressed as well. <br />Finalize the plan. This is usually best done by the design team, after considering <br />all of the input. <br />Present the plan. Invite everyone to see the finished plan, Give everyone credit <br />for the,r mput. Make this a fun event. <br /> <br />. <br /> <br />. <br /> <br />. <br /> <br />. <br /> <br />2 <br /> <br />. <br /> <br />. <br /> <br />. <br />
The URL can be used to link to this page
Your browser does not support the video tag.