My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
5.2. SR 07-24-2000
ElkRiver
>
City Government
>
City Council
>
Council Agenda Packets
>
2000 - 2010
>
2000
>
07/24/2000
>
5.2. SR 07-24-2000
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/21/2008 8:33:49 AM
Creation date
6/28/2004 1:21:40 PM
Metadata
Fields
Template:
City Government
type
SR
date
7/24/2000
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
118
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).
View images
View plain text
Unfortunately, the town meeting was scheduled during the week that I was on a family <br />vacation, a poor choice of dates. Lacking the continuity of city staff, the meeting did not <br />achieve any sense of consensus building. In fact, the division between opposing <br />viewpoints deteriorated back to their original positions. A month of hard work on <br />teambuilding was destroyed. Two members of the task force submitted their <br />resignations and the project was on the verge of collapse. Fortunately, time healed <br />most wounds, resignations were withdrawn, a joint meeting with the City Council was <br />held and we were back on course. The moral of the story - a polarized task force will <br />require constant and considerate staff continuity. <br /> <br />Specific stakeholders were invited to a subsequent meeting. These included police and <br />fire departments, ambulance service, refuse collection, post office, city transit, school <br />district transit and the bicycle commuters club. A representative of each group <br />described their access needs through the neighborhood and answered many excellent <br />questions form the task force. This meeting was a watershed event for the task force. <br />Many members had preconceived options based on inaccurate assumptions. The <br />information provided by these stakeholders began the process where polarized <br />viewpoints began to meet in the middle. <br /> <br />Moving Towards Consensus <br /> <br />The task force decided that the study area was much too large to evaluate at one time. <br />Therefore they broke it up into three geographical sub-areas. This accomplished the <br />following: <br /> <br />· The neighborhood with the easiest problems was tackled first. <br />· Quick "victories" were obtained and the task force realized they could <br /> cooperated and work together <br />· Staff could keep up with the task force in the preparation of maps, <br /> exhibits and studies <br />· Common problems of speeding or congestion could be solved <br /> separately <br /> <br />Using the Hot Spots map, the task force began their evaluation. First, they determined <br />whether the perceived problems required fixing or just public education. Once it was <br />decided to fix a problem, staff was asked to suggest methods form the "tool box." The <br />task force still found it difficult to independently sort for the proper tool. Occasionally, a <br />member would suggest "Let's put in stop signs everywhere" or "Let's just post every city <br />street for 25 mph." Over time, the task force itself would tell the member the error of his <br />ways. Staff became less of a teacher and more of a moderator and resource. <br /> <br />After solutions were identified for each location, the task force looked for continuity over <br />the entire sub-area. Network problems, such as trip diversion or emergency access, <br />were identified and the solutions were reconsidered. When all of the sub-areas were <br />completely analyzed, the entire study area was reevaluated for network problems. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.