Water and Watersheds- Unifying Principle for a New Planning Rule?

Guest post by Jim Furnish, former Deputy Chief for National Forest Systems, USDA Forest Service

Why Is Water So Important?

The connection between forests and water has long been recognized, and was at the core of why national forests were created. The Organic Act of 1897 speaks to “favorable conditions of water flow” (which we would articulate differently today), and the strong inference is to both quality and quantity. Forests and their waters were under clear threats from rampant logging, grazing, and mining. Today, although such overt abuses have been stopped, the value of clean abundant water flowing from public land is greater than ever.

Watersheds behave much like a human veinous system, serving every part of the landscape and ushering water out and away through ever larger streams. Water is a direct and inerrant reflection of the health of the landscape — it cannot lie. It is the lifeblood of the landscape, thus, biota is usually bunched and concentrated in and near water. A century of conservation has no doubt served to avert degradation, yet population and commercial pressures continue to impact watershed health.

Is watershed restoration necessary? The underlying question is important — is there anything to restore, and, if yes, how/why did it get that way? On national forests, did the Forest Service play a causal role? The response to these questions draws sharp differences, often breaking along ideological lines. But what does the land say?

Invasive species, degraded fish stocks, threatened species, loss of riparian health — no matter your ideology, all these speak plainly to the reality that things are not as they should be, no matter the cause. What niche should national forests occupy as it relates to reasonable public expectations for watershed health? I would hope the Forest Service would aspire to a high calling. It should be noted that severity varies greatly, and some watersheds remain in great shape, while others are in poor health.

Today, watershed restoration must be an essential unifying principle for land managing agencies — and an important element in an effective and useful planning regulation. Water is a crucial essence for almost all land management considerations.

Trigger Itch

As Sharon writes, I have raised the possibility of using “triggers and thresholds” in some sort of adaptive management framework:  Here is the statement I made at last week’s science forum:

 One possible approach to this problem [how to practice adaptive management in the modern regulatory state] is to consider using some type of pre-negotiated commitments in an adaptive management framework.  These enforceable commitments would specify what actions will be taken by the agency if monitoring information shows X or Y.  In other words, some predetermined decisions, or more general courses of action, are built into the adaptive framework from the beginning (i.e., if this, then what).  Not every possible scenario can be prefigured of course, but having some thresholds or trigger mechanisms built into an adaptive framework might alleviate concerns about the amount of discretion ostensibly needed by agencies to plan and manage adaptively.

In retrospect, perhaps it’s wise to stay away from the term “threshold” because of its scientific usage and debate.  But triggers should still be considered by the agency.  I think the approach might work best in particular management situations, especially those that have an implementation monitoring program in place. 

I don’t think the approach is that uncommon actually.  Consider, for example, a report written by Chuck Quimby of USFS on using adaptive management options within a NEPA process focused on grazing (sorry, don’t have a PDF or link).  He discusses how various adaptive management options can be worked into EIS alternatives. 

Or consider various state wolf management plans whereby states commit to so many packs, and if monitoring shows they drop below some predetermined floor, a different suite of managerial requirements kick-in (more conservative wolf management). 

And to show that such an approach can cut in multiple directions consider the “adaptive timber management strategy” as used by the Tongass NF.  That strategy basically sets various triggers regarding timber harvesting and industrial development in SE Alaska.  If particular objectives are met, then additional roadless areas are opened for more harvesting.  This approach, if I recall correctly, was basically used by the Tongass as a way to more strategically open roadless lands for harvesting—rather than offering multiple sales in multiple roadless areas.  (Of course, conservationists see this as a complete bastardization of the AM approach, but it does demonstrate how adaptive management needs a purpose—it’s a means to an end—and that end needs to be defined by using NEPA). 

The approach could also be used in some restoration plan.  The USFS chooses a plan alternative (using NEPA) that emphasizes restoration.  Within that alternative are embedded a number of adaptive management options.  So, for example, if various restoration objectives are met by some date, then the agency will offer additional stewardship contracts in the following locations. 

 And one more hypothetical:  The USFS chooses a travel management alternative that connects two existing routes for OHV use.  Embedded within that alternative is an adaptive management option:  if an area adjacent to the connected route becomes illegally used and degraded, the new connected route shall be discontinued and decommissioned. 

 Sharon is right, however, because there will be lots of debate about where these trigger points are set.  (This has been a big issue in oil and gas planning and impacts to Grouse in Wyoming).  I imagine in most cases they will simply be politically negotiated, and in others scientists will be given a larger role to play (if used in the wildlife context). 

Martin Nie

When We Just Don’t Know

I have often wondered why Forest Service scientists and managers talk about risk and uncertainty, yet don’t wander into the territory of “novelty, surprise, and ignorance.” My studies in decision-making and economics inform me that risk and uncertainty are the domains of games where probability distributions are well-known. Another realm, the realm of novelty, surprise, and ignorance is where many business and organizational management decisions live. That is why I’m often railing about “wicked problems”, and about how to make sense of the organizational, environmental, and social contexts we dwell in. Today I want to explore the wilds of “organizational ignorance.” In short, I want to take a look at what to do when we just don’t know.

To make my case, I want to examine a little article that I found a few years ago on the subject, titled Managing Organizational Ignorance, by Michael Zack. The only time I mentioned it before on internet chatter, best I can tell, was when the Forest Service was trying to wed Planning with Environmental Management Systems. (my Forest Service EMS/Planning blog chronicles are here). Here is what I said:

[A]s we continue on this EMS journey maybe we ought to spend more time exploring novelty, surprise and ignorance. Study adaptive management, and read in detail books like Panarchy, Supply Side Sustainability, Compass and Gyroscope, Discordant Harmonies, and more. And don’t forget to wander over and read Michael Zack’s Managing Organizational Ignorance—either right now, or later after you’ve worked yourself into a frenzy over EMS and come up short.

Zack begins with one of my favorite quotes, from Neil Postman’s Amusing Ourselves to Death: Public Discourse in the Age of Show Business, “Ignorance is always correctable. But what shall we do if we take ignorance to be knowledge?” [Note: Postman’s book ought to be required reading for everyone in the U.S.—to better understand our current plight w/r/t ignorance]

Zack builds his thesis around four knowledge-processing problems, each describing a unique form of “organizational ignorance”:

  • Uncertainty: not having enough information;
  • Complexity: having to process more information than you can manage or understand;
  • Ambiguity: not having a conceptual framework for interpreting information;
  • Equivocality: having several competing or contradictory conceptual frameworks.

Each problem describes a particular form of organizational ignorance, calling for a particular knowledge-processing capability. Each in some way also represents a fundamental organizational or strategic management problem. Taken together they define the range of knowledge processing capabilities an organization must have to manage its ignorance effectively. These four knowledge problems can be categorized along two axes: 1) the nature of the knowledge being processed, and 2) whether the solution is to acquire more knowledge or to place restrictions on what you have.

Here is Zack’s table, summarizing the relationship between the knowledge problems and information processing (gathering, restricting, analyzing, etc.):

Zack sums up with:

The four knowledge-problems framework provides a powerful lens for viewing information processing, communication, and knowledge management in organizations. It suggests several prescriptions and conclusions.

  • Organizations must be open to novelty and anomaly. Only by acknowledging its ignorance can an organization put itself on the road to learning. Organizations must recognize and accept that there are events that may be difficult to explain because no one understands them well enough. …
  • Knowledge management today focuses primarily on solving problems of complexity and uncertainty. It aims to share and exploit what is known within well-defined circumstances and contexts, and is dominated by information technology. Expert systems apply codifiable but highly complex sets of rules; best practice databases attempt to share less structured but well-documented expertise; point of sale systems attempt to provide rapid feedback for managing market uncertainty, while e-mail and discussion databases do the same for internal uncertainty. Much less effort has been spent worrying about the ambiguous and equivocal situations resulting from more profound forms of organizational ignorance. To truly manage knowledge and expertise, however, organizations must make sure that their members work toward building a shared fundamental understanding of the situations and problems they face. Meetings and teams, as well as informal opportunities for engaging in sense-making conversations that raise good questions, challenge the status quo, and directly deal with ambiguity and equivocality are all essential. Solving convergent, well-defined problems requires having a shared understanding in place first. It is therefore critical for organizations to be aware of and to solve problems of ambiguity and equivocality before diving into the more structured problems of uncertainty and complexity.
  • Information technology can play an important role in managing information and knowledge, when it is appropriately applied. This requires diagnosing the nature of the knowledge problem beings solved. Information technology makes sense in cases of uncertainty and complexity, but much less so for dealing with ambiguity and equivocality
  • Organizations need to go beyond their own boundaries to find the knowledge they need to help them make sense of the world. Where the organization is relatively ignorant…, it should include [constituents] in the sense-making process. In doing so, the organization will also develop a shared understanding and basis for ongoing communication with its [constituents]. As ambiguity and equivocality give way to uncertainty and complexity, the organization can more easily migrate to more structured technologies to communicate and coordinate with its external partners. … Organizations may use information technology to exchange data and information, but they will need to use social interaction to exchange knowledge in building a shared understanding about their commercial relationships.
  • Senior executives and managers must interact freely with those at lower levels of the organization in sensemaking and problem-solving processes to discover what the organization as a whole truly knows. It is not enough for managers merely to catalog organizational knowledge by creating a “knowledge map.” Rather, they must sense the organization’s knowledge and ignorance by engaging all organizational levels in the process of resolving the four knowledge problems.
  • Like managing knowledge, managing organizational ignorance requires an appropriate culture. In general, the organization must create an environment in which it is acceptable to publicly admit that one does not know something. Multinational organizations I have observed find this to be particularly problematic in certain national cultures. Managing complexity requires a culture in which it is acceptable to identify and support experts and seek their advice. Resolving uncertainty requires a culture supportive of open, clear and extensive cross-boundary communication, and a willingness and ability to bridge various languages (both professional and national) in use across the organization. Resolving ambiguity requires the ability to confess ignorance and confusion. Managing equivocality requires an environment in which it is acceptable to disagree about interpretations and which accepts diversity of views as well as useful and productive consensus.
  • Each of the four knowledge problems suggests a different set of processes, roles, information technologies, and organizational structures for their resolution. … Often … problems are intertwined. [An organization] must be flexible enough to modify itself dynamically to deal with the knowledge problem at hand. …
  • Even the non-routine or unpredictable aspects of the four problems can be managed, or at least anticipated, in a routine fashion. Where ambiguity or equivocality routinely arises, organizations should create standing mechanisms to address them. Provisions must be made for face-to-face conversations to occur among those most relevant to resolving ambiguity or equivocality. Those responsible for executing the resulting interpretations must also be involved so that those interpretations can be meaningfully communicated. Uncertainty can be routinely handled by anticipatory mechanisms for exchanging information; complexity can be handled by anticipatory mechanisms for locating knowledge.
  • The four problems suggest a framework for managing organizational learning. Ambiguous and equivocal problems often represent non-routine events about which the organization lacks sufficient knowledge. The process of resolving ambiguity and equivocality, however, is the stuff of which organizational learning is made. Ambiguous and equivocal events, if encountered enough times, eventually become familiar enough to be migrated to more routine processes. Organizations must have the ability to evaluate events to determine if they are interpretable or not, route them to the appropriate resolution process, and eventually migrate those that become familiar to routine processes, thereby reserving the organization’s capacity to continually handle novelty and confusion. [Emphasis (bold) added by Iverson]

Is the Forest Service ready to deal with Zack’s four knowledge-processing problems? Do they help make better sense of “ignorance problems” than traditional rhetoric of “risk and uncertainty”? Have Forest Service managers/scientists/staffers already been dealing with these problems albeit in different frames? In short, what do you think?