Laserfiche WebLink
<br />40 <br /> <br />agency obviously had its mind made up on which alternative it wanted before it started! Couple these <br />perceptions with the fact that within anyone river basin or forest there may be three, four, or even ten such EIS <br />processes underway, all in various stages of completion, and it is little wonder the public becomes disenchanted. <br />To complicate matters, when the agencies do attempt to make a good-faith effort to convene a group of <br />concerned citizens with diverse viewpoints to work together, they are inhibited by conservative interpretations of <br />the Federal Advisory Committees Act (F ACA ) which makes it impractical and extremely difficult to assemble <br />public task forces. <br /> <br />Ideas / Solutions <br /> <br />We need to recognize that we can't expect to get the public involved if they can't understand what we are talking <br />about. We need to avoid using jargon and acronyms. They may mean a lot to us, but 90% of the public are only <br />familiar with the most common terms. We should be speaking in plain English, that everyone can understand. <br />Doing this will communicate that we do care about them and want to hear what they have to say. <br /> <br />To work within FACA restrictions we can do a couple of things. First, we can separate citizen work groups <br />from the technical or formal decision making process. We can also use workshops (totally open meetings with <br />open participation) instead of Task Forces or Workgroups (with closed membership). <br /> <br />We should begin to view public involvement as a dynamic tool which can aid us in determining our <br />management agenda. For instance, we can use public involvement to get a better pulse on whether or not a <br />particular action is likely to raise substantive issues that will need to enter the NEPA process. <br /> <br />Work Group Results <br /> <br />Work Group Issues: <br />1. Agency interpretations of regulations. <br />2. Upper level management jurisdiction battles (fIsh, water). <br />3. Regulations that change with the political administration. <br />4. Technical advisory groups can become political through appointments. <br />5. Inflexible time frames of regulations and policies. <br />6. Public's misunderstanding of regulations. <br />7. Publics who withhold infonnation for later appeals. <br />8. How do you select stakeholders to be on advisory groups and get the right people to come? <br />9. Cultural differences. <br />10. Different agendas and priorities of agencies. <br /> <br />Work Group Ideas / Solutions: <br /> <br />. Create an interagency strategy team which meets bi-monthly. It would need to be jointly funded and <br />must cover the per diem and travel of its members. In general, try to combine or share meetings. <br /> <br />· Need to involve tribal representatives early. Need to understand tribal dynamics -- Who can speak? <br />A void intertribal councils which send one spokesperson. Actively recruit / develop a liaison <br />person. Report back to the tribes on decisions, even if they don't attend meetings. Be culturally <br />sensitive and know tribal mores about how to approach problems. <br /> <br />· Be realistic but flexible in the time frame. Don't cut off or shorten the process too soon. Setting <br />objectives, shared visions etc. takes as many meetings as it takes. <br /> <br />· "Partners afloat/astride" type programs are extremely valuable. They give agencies the chance to get <br />out in the fIeld with each other and with key members of the public. These give the opportunity to <br />role play, in which participants can reverse the roles they normally play. The trips should last 2 or <br />3 days and should involve decision makers that may be involved in jurisdictional battles. <br /> <br />· Ecosystem management may mean that no one agency has the lead role. It would be best to have a <br />community-based organization or independent group facilitate the process. <br /> <br />American River Management Society <br />