Laserfiche WebLink
Numbers do have a place in the evalua- <br />tion, even though ~hey are not enough by <br />themselves. Their purpose is less to serve as <br />a basis for drawing conclusions than as an <br />indicator ora need for analysis and to look <br />deeper for causal relationships. For example, <br />in certain cases a dearth of variance requests <br />related to a particular provision may suggest <br />its validity. On the other hand, a weakness in <br />the code may result in easy compliance. This <br />must be weighed against the code provision's <br />purpose and intent. A large volume of vari- <br />ance requests and approvals may suggest <br />that the provision is not working or not practi- <br />cal. 8uc this, too, can be misleading unless <br />each case is reviewed c~refully in terms of <br />context, outside influences, and peculiar cir- <br />cumstances, Sometimes variations, especially <br />in a flexible code format focused on results <br />and performance, are necessary and do not <br />prevent conformance with the code's intent. <br />What may on [he surface be read as a need to <br />amend may prove to be merely the need for <br />minor modifications. <br /> <br />The basic approach to a qualitative evalua- <br />tion ora code can be summed up in two <br />words: ooservation and inquiry, This <br />approach heavily weigh.~ direct observation <br />on the part of the evatuator, interviews with <br />code users, and careful reviews of docu- <br />ments, ~pprova(sl findings, and decisions: <br /> <br />The evaluator may observe significant <br />strfdes in the direction of achieving the pur- <br />pose and goals of the code by noting the <br />quality of submissions, understanding the <br />attitude of applicants and decision makers, <br />and cataloguing the physicai resu4ts of <br />applying the new regulation. For example, <br />we realized that the design focus of our new <br />code had raised the bar with respect to the <br />quality of initial project submissions com- <br />pared to those submitted t~nder the previous <br />ordinance. The turn-of-the-century Lyell <br />building' in the illus,:ration above had been <br />used for commercia[ purposes over the <br />years, but the character of the building had <br />been diminished by facade treatments that <br />complied with the code but were less than <br />appealing. The latest renovation illustrates <br />compliance with the code's design criteria in <br />an as-of-right rehabilitation and reuse. <br />Clearly, both in terms of the quality of the <br />submission and the redevelopment itself, <br />the bar had been raised. <br /> No doubt, the public's extensive involve- <br />ment in drafting the code and significant edu- <br />cation efforts contributed to this. However, <br />such examples have shown that applicants <br />understand what the code is trying co achfeve. <br />Rather than having to "force feed" the new <br />des[§n re§ulations, as some critics had <br />warned, there was a clear reflection of a <br />higher level of awareness with respect to <br />urban design. Applications incorporated the <br /> <br />guidelines and standards before the initial <br />review and comment by staff. This was an <br />observable pattern in many submissions and <br />was a basic indicator of a general level of <br />acceptance, not resistance. This measure of <br />success would be difficult to verify through a <br />purely quantitative approach. <br /> A completed proiect can show the <br />stroh§th of a re§uiation or uncover its weak- <br />ness, and can shed light on how well a theory <br />works in real-world situations. Case studies <br />that focus on readily observable results are <br />particularly useful in'this type of analysis. <br /> Observing the code's processes as they <br />affect these cases can also yield important <br />information. This is real-time, day-to-day <br />observation. It is not just a matter of expedi- <br />ency, but of the quality and depth of review in <br />relation to the particular type of application <br />presented. How fluid is the process? Does it <br />facilitate or is it cumbersome? Does it provide <br />for adequate and timely public participation.7 <br />Is it comprehensi~)e; equitable, and fair? Does <br />it provide the decision makers what they need <br />to assess projects and make determinations in <br />an expeditious yet thorough manner? Is the <br />process properly synchronized with the pur- <br />pose of the regulation? What adiustments <br />need to be made? <br /> tn addition to direct observation, the <br />interview is a very important part of a quali- <br />tative code evaluation. All of the players <br />involved in various applications can be <br /> <br />222 ZONING PRACTICE 7.05 <br /> AMERICAN PLANNING ASSOCIATION <br /> <br /> <br />