Laserfiche WebLink
t ration ch e el <br />nditions.for advancl g a► d di <br />�� <br />n>�ns metadaeaonlioveacFl <br />matter is that our staff members worked very <br />hard to overcome the poor processes that <br />were not designed to help them succeed. Our <br />process simply didn't make it easy for them to <br />do the right thing. Often, for the sake of de- <br />livering value in their jobs, our staff members <br />simply operated outside of the process. They <br />would go out of their way to avoid the process <br />so as to prevent the cascade of bad effects <br />that would follow if they kept to their scripts. <br />This was readily apparent in the third stage of <br />the effort: defining, and improving, our flow. <br />Achieving Great Flow <br />The action that best personifies process im- <br />provement is the mapping that comes during <br />the flow stage. Symbolized by the flow charts <br />that show the beginning, middle, and end of <br />an effort, most practitioners can easily sketch <br />the basic flow of any process in accordance <br />to the critical path. But a critical path isn't <br />enough to truly understand how your business <br />is operating when it involves multiple people <br />from multiple groups. The real flow from the <br />start to finish of a process is surprisingly com- <br />plex and full of hidden decisions, conditions, <br />tha �f= a mo a eonm r <br />4ti0� <br />mots: halo <br />and bottlenecks that no single person can <br />identify on their own. And often, it varies from <br />person to person in the existing condition. <br />Mapping the flow, especially as it cur- <br />rently exists, requires significant time and <br />effort. It is, essentially, an audit of the team's <br />work: what they do, how they do it, and when <br />they do it. And like any audit, their involve- <br />ment is critical for success. For a large de- <br />partment such as ours, this meant bringing <br />a staff of more than 20 people to an off -site <br />conference room where they could define ev- <br />ery step of the conceptual review process —as <br />it currently exists and as they currently use <br />it —and map the information on a whiteboard <br />for all to see. The work took several hours, and <br />the visual result wasn't pretty. But it painted a <br />very compelling picture. <br />Within this basic illustration, not only <br />does one find the critical path that serves as <br />the backbone of any process, but also the <br />smaller actions, inputs, and decisions that <br />make it possible. Some of which are inconsis- <br />tent from one participant to another. It is vital <br />that the exercise of mapping the existing flow <br />highlights these inconsistencies. <br />For example, the original process for <br />initiating a conceptual review involved a plan- <br />ner receiving the request from an applicant or, <br />more commonly, informing a would-be <br />applicant that it was required. Sometimes, <br />this occurred after a file had already been <br />created in our case management software. If <br />so, the conceptual review meeting was noted <br />in the case file electronically. But not always. <br />Many cases had no record that a conceptual <br />review meeting had ever been conducted <br />since different users acted in different ways <br />without a process to dictate. <br />Even the simple matter of scheduling <br />the meeting was often different from user <br />to user. Some planners would schedule the <br />meeting themselves in Microsoft Outlook. <br />Others would ask a permit technician to <br />schedule the meeting for them. And again, <br />some would not schedule the meeting at <br />all; they would adhere to the department's <br />standard time for these meetings (Monday <br />afternoons) but hold the meeting in any con- <br />ference room that was available. In the grand <br />scheme, we've hardly scratched the surface <br />on the rest of the process and already find <br />inconsistencies throughout. <br />One important note is that this effort <br />can and should be categorized as a "blame - <br />free autopsy." This is process improvement, <br />ZONINGPRACTICE 5.17 <br />AMERICAN PLANNING ASSOCIATION I page 5 <br />