Seattle process

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

The Seattle process or Seattle way[1] is a term stemming from the political procedure in Seattle and King County, and to a lesser extent other cities and the Washington state government. The term has no strict definition but refers to the pervasively slow process of dialogue, deliberation, participation, and municipal introspection before making any decision and the time it takes to enact any policy. An early definition came from a 1983 editorial in the Seattle Weekly, "the usual Seattle process of seeking consensus through exhaustion."[2]

Other definitions

"In its positive connotation the Seattle Way values popular participation, transparent process and meaningful debate. More negatively, it has been decried as a culture that values process and debate over results, that bogs down and can't get important things done."—Mark Purcell, Recapturing Democracy.[3]

"The Seattle Way usually is defined as circular consultation reaching indecision. But it also consists of an uninvolved electorate and public decisions taken carelessly, without regard for experience elsewhere and unmindful of consequence."—Ted Van Dyk, contributing columnist to the Seattle Post-Intelligencer[4]

History

Prior to the election of Wes Uhlman as mayor in 1969, civic decision making was relatively quick and powerful groups could influence civic leaders without seeking wide consensus.[1][5]

Proponents of the Seattle process, such as former city councilman Richard Conlin, praised it as a thoughtful method of generating the best results at the expense of time.[6] In return, opponents referred to Conlin in 2005 as the "Duke of Dither" for his devotion to process.[7]

As the Seattle process became more drawn out, it has been criticized, usually by business interests as too slow and dithering. As an example, during the massive redevelopment of the Cascade and South Lake Union neighborhoods in the early 21st century it was criticized by Vulcan Inc. and Fred Hutchinson Cancer Research Center that an in-depth discussion of all of the ideas would wear out the patience of other groups providing financial capital. Meanwhile, neighborhood activists complained that the proposed development ignored the neighborhood plans that were previously, and laboriously, developed in a consensual process.[3] City neighborhood activists generally like the deliberative process.[8][9]

The process has also been criticized for bland results.[8][10]

Methods

The Seattle process as an informal method values study, discussion and civic engagement. It will involve numerous stakeholder groups. It requires the community to present effective data, and for organizers to translate data from different constituencies into useful reports for decision makers.[11] Using process to seek out consensus and hearing all opinions even extends to the corporate boardroom, not just government.[12]

Methods of participation typically include council meetings, neighborhood forums, ballot measures, and marches. Stakeholder groups are all-inclusive and usually include citizens, corporations, non-profits, neighborhood representatives, and identity or issue specific groups.[1]

Despite being called a "process" there is no definitive methodology to the Seattle process; in fact, while writing about Seattle taking four decades to build a light-rail line, The New York Times called it a "mysterious and maddening phenomenon".[13]

Outside of the public meetings and methods open to the public, the Seattle process also causes delay while politicians either tinker with, or obstruct, proposals.[6] Other cities in the area declare their ability to get projects because of the lack of Seattle process.[14]

In politics

The Seattle process, and claimed devotion to it, has been an issue in political races. In the 2001 Mayoral Election candidate Greg Nickels used devotion to Seattle process as an issue against his opponent, city attorney Mark Sidran, who promised a more decisive style.[15] However, eight years later Nickel's style as Mayor would be criticized in a re-election race as top-down, autocratic, and antithetical to the Seattle process.[16]

A sample of projects affected

File:Seattle - old Queen Anne water tower.jpg
Replacing these water towers took 14 years and almost $3 million in planning and development costs

References

  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 4.3 4.4 Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 6.4 6.5 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.