Better value, better solutions, and improved customer satisfaction are some of the benefits realized when projects are managed and delivered using a CSS framework. As more organizations apply CSS principles, evidence continues to grow that measurable benefits result from this broadly informed and flexible approach to all phases of transportation decision-making. Involving stakeholders in decision-making yields transportation solutions that balance environmental, engineering, community, mobility, funding, and safety needs with the minimum of delay and controversy.
CSS processes deliver better value in the form of reduced costs or more cost effective projects, on-time delivery, or – perhaps most importantly – improved community relationships. Direct cost savings relate to right sizing of facilities, avoidance actions (reducing the environmental clearance from an EIS to an EA/FONSI), and avoidance of opposition, which can lead to costly litigation and delays. Finally, CSS processes provide opportunities to leverage a wider range of funding options, including non-traditional funding sources or cost-sharing approaches.
Many senior executives of state departments of transportation (DOTs) recognize that applying CSS principles to their project delivery systems will save time and resources and better ensure delivery of projects as planned.
An agency’s design manuals, standards, and criteria will generally produce proven solutions to typical problems. The challenge for designers is to recognize when the standard solution may not “fit” or perhaps not work, and a unique approach is required. A CSS mindset can help a designer know when to apply a tailored approach. Being context sensitive means that designers look for solutions that avoid or minimize impacts while operating safely and efficiently. Ultimately, this results in better—even optimal—solutions, which are in alignment with the environment and community.
The process requires flexibility and creativity. To be flexible, designers must first have thorough knowledge of how and why specific design criteria are applied, and keep key issues and values in mind. Designers who are “context sensitive” understand that the design process is not one of applying mandates by rote, but rather of carefully exercising choices involving these design controls and roadway elements:
Design choices are influenced by the context: topography, location, functional classification of the facility, adjacent land use, and presence and nature of environmental features, including built elements. Designers exercise judgment about design controls, and look for creative solutions that balance stakeholder needs while preserving operational safety and efficiency. Designers might, for example, suggest asymmetric designs or policy or operational changes that will make possible a solution that performs optimally within the project’s unique context.
CSS projects are not only acceptable to stakeholders; they can become a community rallying point and source of civic pride. An agency-wide commitment to CSS approaches can increase agency credibility and lead to more productive relationships between the agency and its “customers,” the community.
A context sensitive process does not cost more than a traditional project development process. These processes are scalable and do not necessarily require an extensive (expensive) public involvement process. A CSS process does require taking the time to listen to stakeholders early on and develop solutions that reflect stakeholder values; but developing solutions with stakeholders is less expensive than redesigning a project.
By gaining an understanding of stakeholder issues early, teams who use CSS approaches can shorten the project development process and reduce the likelihood of redesign and litigation later on.
Benefits can include:
Resources:
