|
Elements of Value
<br />Key Performance
<br />Indicators
<br />Benchmark
<br />(Quality) Percentage of staff participation
<br />Comprehensive Comments from all divisions
<br />(Quality) Percentage of comments that
<br />Clear Language provide citation or definition
<br />(Quality) Percentage of comments
<br />Chronological completed with template
<br />Timeliness
<br />Percentage of comments
<br />delivered within 14 days
<br />not process disparagement. When teams get
<br />together to discuss this work, they often feel
<br />a sense of guilt at how convoluted the system
<br />has become. They think it's their fault. But
<br />unveiling all the hidden machinery and small
<br />foibles is vital to understanding how every-
<br />thing can work better. So as the staff members
<br />work to define their process —as it is, not as it
<br />should be —the conference room can start to
<br />feel more like a confessional. But again, as a
<br />"blame -free autopsy," this is a critical step to
<br />everyone's progress as part of a team. Not a
<br />time to point fingers.
<br />When the various actions are defined
<br />and the map is clear, the next step is a
<br />return to the principle of value mapping.
<br />Only, in this case, the value mapping is far
<br />more fine-grained. Here, the team begins to
<br />analyze the dysfunctional process they see
<br />before them. They look at every step and
<br />consider whether it is worth keeping. Like
<br />editors searching for the next unnecessary
<br />adjective, the team becomes ruthless, cut-
<br />ting what isn't needed and keeping only that
<br />which is truly, deeply valuable.
<br />Value in this much smaller sense goes
<br />back to the notion of the critical path. Not
<br />the more simplified version of "the big pic-
<br />ture" but a version that shows how every
<br />step creates an action that gets the client
<br />closer to what they want: the final output. In
<br />our case, the final output is the timely deliv-
<br />ery of a set of complete, consolidated, and
<br />chronological comments. If the team agrees
<br />that a certain step gets them closer to what
<br />the client wants, it is marked with a "Value -
<br />Added" designation.
<br />Processes also have steps that are nec-
<br />essary even if they do not get a client closer
<br />to what they want. Such steps are marked as
<br />i00% on all documents
<br />i00% on all documents
<br />i00% on all documents
<br />z00% of all review cases
<br />"Business Value -Added" in the sense that our
<br />work cannot function without certain actions
<br />taking place. In the instance of conceptual
<br />review, a prime example is the act of inputting
<br />one's comments into our case management
<br />system (Clayton n.d.). This does nothing for
<br />the client (they don't have access), but it is
<br />necessary for the business.
<br />Every other remaining action is marked
<br />with a "Non Value -Added" (NVA) designation.
<br />One of the more satisfying aspects of this
<br />work is looking back at the number of NVA ac-
<br />tions that are found in every original process
<br />map. This is the stuff of red tape bureaucracy
<br />and bad customer service. Each NVA item is
<br />removed from the future process, liberating
<br />staff and clients from things they neverwant-
<br />ed to do in the first place.
<br />Altogether, the value-, business value-,
<br />and non -value-added items are compiled by
<br />percentage so that one can see the overall
<br />picture of what often occurs in a process. It's
<br />not uncommon to find a development review
<br />process that has more than 5o percent of its
<br />actions classified as non -value added. Remov-
<br />ing those items cuts a job's demands in half —
<br />an incredible improvement. In the case of our
<br />conceptual review process, we discovered 44
<br />percent of all actions were unnecessary. On
<br />our other bookend, building permit review,
<br />we eliminated and revised even more steps,
<br />reducing our time line bY7i percent.
<br />What's left is the lean, efficient process
<br />that the team has defined by simple subtrac-
<br />tion. The team is thus a veritable Michelange-
<br />lo, freeing the sculpture from the surrounding
<br />marble. As a result of their collaboration, they
<br />can understand the new process in a deep
<br />way that compels them to use it together in
<br />a consistent manner that imbues great team
<br />spirit. People are often excited to go back to
<br />work and try it. But a process, no matter how
<br />lean, can't be deemed effective until you know
<br />what you're trying to accomplish.
<br />Establishing Pull
<br />The old adage is true: What isn't measured
<br />isn't managed. And if value is determined by
<br />the quality and timeliness of what we deliver,
<br />we need to create measures that can help us
<br />create maximum value. One such measure
<br />should represent the quality element and
<br />another measure should represent timeliness.
<br />Working with your staff to establish these two
<br />measures together, collaboratively, is the key
<br />to creating ownership and buy -in.
<br />In our case, we knew that quality was
<br />best achieved when we delivered com-
<br />ments that were comprehensive, clear, and
<br />chronological. We knew timeliness was best
<br />achieved when comments were delivered
<br />within 1.4 days. The table at left illustrates our
<br />basic KPIs.
<br />Our new process ensures these bench-
<br />marks are met by establishing pull. We've
<br />designed a process that can easily ensure we
<br />"pull" our product through in a timely fashion,
<br />as demanded. But only to a certain extent.
<br />We don't have capacity to meet all possible
<br />demand. If we were to receive, say, io con-
<br />ceptual review meeting requests for a single
<br />week, and these requests were pulled through
<br />the process at the same time, we'd probably
<br />see quality suffer. We simply wouldn't be able
<br />to coordinate in a way that has everyone in the
<br />room consistently for those meetings. So in-
<br />stead, we set a cap based on time and space.
<br />We reserve a single conference room for four
<br />hours a week on Monday afternoons. This typi-
<br />cally serves four such meetings a week. This
<br />allows our staff to coordinate their time, keep
<br />the meetings in a consistent space, and thus
<br />have all the critical elements up front for the
<br />rest of the process to be a success.
<br />In order for applicants to receive the
<br />value we can offer in the time they deserve,
<br />we must adhere to this basic capacity limit.
<br />That's what establishing pull is all about.
<br />Backlogs can happen as a result, but that's a
<br />result of excess demand for the process, not
<br />excess waste within it —a critical difference.
<br />Continuous Improvement
<br />But these capacity limits don't last forever.
<br />The most enjoyable aspect of process im-
<br />provement is that it ingrains a new way of
<br />ZONINGPRACTICE 5.17
<br />AMERICAN PLANNING ASSOCIATION I page 6
<br />
|