5 minute read
Pathfinders’ progress against the NMDC – 6. Testing: Adoption and implementation
6. Testing: Adoption and implementation
This section summarises how to test completed codes, to understand how they will be used and how they might be improved. So far there are limited learnings from this phase, as Pathfinders are just beginning to test their design codes following the completion of the programme, implementation of codes, including the importance of training for officers and councillors.
$ Pathfinders are testing their design code with developers, development management officers and local communities to understand:
usability, ensuring it can be used on a day-to-day basis
robustness, ensuring it works in different decision-making scenarios, and whether there are gaps
design and legibility, ensuring it is easy to navigate and read.
Take-aways for future design coders
Test draft codes:
$ Test codes against previous permissions, live planning applications and in pre-application stages.
$ Test codes from various user perspectives, including developers, development management officers and communities.
$ Test both the physical document and any digital assets.
$ Be aware of the interdependencies of any changes made to the code (within the code itself, and in relation to other guidance).
$ Test the document’s useability to ensure it is easy to navigate and follow, and to ensure that its coding is directly reflected in emerging proposals at pre-application and application submission stages, and in decision taking at local level, and/or on appeal/call in/recovery by the Secretary of State.
a. Developing digital codes
$ Pathfinders found that digitising and formatting a design code for websites took longer than anticipated. Some Pathfinders were disappointed by the cost and a lack of available expertise inhouse to support.
Pathfinders also noted that the website or digital platform, when developed, would need periodic updating, and they expressed concerns about who would assume responsibility for keeping the code up-to-date.
$ Introducing digital expertise into planning departments is very important, as Pathfinders found that graphic design and digital teams in-house were unfamiliar with the technical aspects of developing planning documents.
“It’s a real skill: you need to have the planning knowledge to be able to produce something for planning, so just being a graphic designer isn’t enough. I have been in talks about getting us refreshed and trained on these things and getting us access to the software so that we can take it forward ourselves, rather than having to use another department.”
Take-aways for future design coders
Prioritise user experience and functionality over aesthetics:
$ Develop the user journeys at the same time as developing the platform, including:
Identifying the different users and their relationship to the code
Establishing the common entry points and barriers for each type of user
$ Remove barriers through iterative user testing.
$ Be explicit about the actions users are expected to take, when navigating the digital tool (for example, “read this”, “submit an application here”) place other guidance documents together with the code on the digital platform.
$ Identify a site owner to maintain the digital platform.
Work with others to make the digitisation of the code easier
$ Share learning about developing digital codes with other coding teams.
$ Consider jointly commissioning or procuring the development of the digital platform with another local authority.
b. Adoption and implementation
$ Where Pathfinders were using their design codes to expand on an up-to-date, adopted local plan policy by progressing a proposed SPD, this was an easier process than for those where a new, emerging local plan was being prepared, or a local plan review was underway.
“Initially, we’re going to adopt it as a supplementary planning document. Which isn’t ideal in a way that doesn’t have as much weight as a local plan. But it enables us to get it in place reasonably quickly and start using it and testing it.”
“The design code will tie in with the local plan review, so that we can get them on the same cycle and they’ll be kind of brother sister documents together.”
“I think we’re fortunate with the timing of the local plan to be able to put the district wide code in as an appendix.”
c. Training
$ Despite NPPF policies promoting the use and value of design codes, some Pathfinders were concerned that if codes were not accessible and easy to understand they simply would not be used. They believed that a code needed to be accompanied by training for officers and councillors.
“If people aren’t properly trained in how to use and implement it, it’s not going to stick. When we briefed the consultants, two training sessions were built in from the start, which they will deliver. But we have also started thinking about the other support that’s going to be needed for officers within our team.”
Take-aways for future design coders
Support the adoption and implementation of the design code:
$ Training development management officers in using the design code is essential for implementing the code.
$ If planning to combine smaller-scale (site-specific or areaspecific) codes into a larger-scale authority-wide code, then a further piece of work will be necessary, to develop guidance on compatibility.
Define timescales and approach to reviewing the code:
$ Should be reviewed regularly, even if just to check it is still up-to-date.
$ Decide in advance when the code will be updated, and by whom.
