<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Michelle Ann Isme on Medium]]></title>
        <description><![CDATA[Stories by Michelle Ann Isme on Medium]]></description>
        <link>https://medium.com/@misme?source=rss-b9bdab77545f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TfwmN34Cz5EE30IDVQL4Sg.jpeg</url>
            <title>Stories by Michelle Ann Isme on Medium</title>
            <link>https://medium.com/@misme?source=rss-b9bdab77545f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:50:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@misme/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[BoPS sprint notes (22.12.20)]]></title>
            <link>https://medium.com/ubxd/bops-sprint-notes-22-12-20-29856303b105?source=rss-b9bdab77545f------2</link>
            <guid isPermaLink="false">https://medium.com/p/29856303b105</guid>
            <category><![CDATA[digital-planning]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Michelle Ann Isme]]></dc:creator>
            <pubDate>Tue, 22 Dec 2020 18:06:10 GMT</pubDate>
            <atom:updated>2020-12-23T23:36:14.898Z</atom:updated>
            <content:encoded><![CDATA[<p>We are well into the second sprint for the private beta phase of BoPS — building a user centred and more efficient Back-office Planning System.</p><p>Since picking up BoPS again, in late November, we’ve implemented the infrastructure that will allow different planning authorities to receive applications (see our <a href="https://medium.com/ubxd/bops-is-back-sprint-notes-2e020425d9ea">previous sprint notes</a>), prototyped new validation features (in collaboration with a planner in Buckinghamshire), and had our first Show and Tell.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fw_IdagexlAI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dw_IdagexlAI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fw_IdagexlAI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/856cd15d3f5aae057a1755ca2baf7314/href">https://medium.com/media/856cd15d3f5aae057a1755ca2baf7314/href</a></iframe><p>We have also developed a beta version of a production ready <a href="https://southwark.preview.bops.services/api-docs/index.html">documented API</a>, that any applicant facing service can use to submit certificates of lawful development applications to us. This means that we are effectively ready to begin beta testing as soon as we receive application data - bring on 2021! :)</p><p>In the current sprint we’ve also developed a couple of new features that will:</p><ul><li>make it easier for planners to manage and edit the documents that are submitted with applications e.g adding and removing tags, so it’s easier to identify which drawing is which.</li><li>make it quicker to check the validity of applications e.g displaying a payment reference and whether the application is for proposed or existing work.</li></ul><p>You can keep an eye on what else we’re up to by checking out our public backlog: <a href="https://trello.com/b/KQqYJd7W">https://trello.com/b/KQqYJd7W</a></p><p>We really welcome any thoughts and feedback on our work — please add a comment below.</p><figure><img alt="Photo, from above, of residential area in London" src="https://cdn-images-1.medium.com/max/1024/1*7mdvhAWNn5HD5iTt5J0oeA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@writtenmirror?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jay Mullings</a> on <a href="https://unsplash.com/s/photos/houses-winter-uk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>We’d also love to hear from any planning teams who are interested in finding out more about BoPS and /or getting involved in helping us to design or user test further functionality in the future. Get in touch with our Product Owner, Tom, at: tom.buttrick@southwark.gov.uk</p><p>We’re really looking forward to getting BoPS into the hands of planners in early 2021 — see you then!</p><p><em>P.S. If it’s not in your diary already, our </em><strong><em>next Show and Tell will be on Thursday, 7 January at 10.30am</em></strong><em> (as always we’ll be streaming to YouTube and you’ll be able to tune in at: </em><a href="https://rebrand.ly/bops-show-and-tell"><em>https://rebrand.ly/bops-show-and-tell</em></a><em>)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29856303b105" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ubxd/bops-sprint-notes-22-12-20-29856303b105">BoPS sprint notes (22.12.20)</a> was originally published in <a href="https://medium.com/ubxd">Unboxed</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BoPS is back! (sprint notes)]]></title>
            <link>https://medium.com/ubxd/bops-is-back-sprint-notes-2e020425d9ea?source=rss-b9bdab77545f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e020425d9ea</guid>
            <category><![CDATA[urban-planning]]></category>
            <category><![CDATA[digital-planning]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[local-digital]]></category>
            <dc:creator><![CDATA[Michelle Ann Isme]]></dc:creator>
            <pubDate>Tue, 01 Dec 2020 11:02:32 GMT</pubDate>
            <atom:updated>2020-12-01T11:02:32.946Z</atom:updated>
            <content:encoded><![CDATA[<p>We’re excited to announce that development on BoPS — the catchier way to say ‘Back-office Planning System’ — has kicked off again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V--j1iGs6sKHWhkK3Y7Kew.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@nicolebaster?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Nicole Baster</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>Quick recap:</strong> earlier this year we built a minimum viable product (MVP) that will make it quicker and easier for council planning teams to assess applications for householder permitted development… in a nutshell, it will help councils to provide a better service whereby applicants receive a quicker decision on their application. It does this through clean and intuitive design (backed up with lots of research and testing with planning officers) that makes it easier for planners to find what they need to make an assessment, and by receiving applications as “data” (rather than PDF application forms) which makes it easier to surface or re-use that data elsewhere.</p><h4>So, what’s next?</h4><p><a href="https://www.southwark.gov.uk/innovate/collabrative-project/planning-back-office">Southwark Council</a>, the lead partner on the BoPS project, is working with Unboxed and other council partners, with support from MHCLG’s <a href="https://localdigital.gov.uk/fund/">Local Digital Fund</a>, to move the MVP into beta testing over the next few months.</p><figure><img alt="Screenshot of GDS project phase posters (discovery, alpha, beta, live) with a line indicating we’re between beta and live" src="https://cdn-images-1.medium.com/max/1024/1*MZLc_gTGRf8jvYnDtKZvGA.png" /></figure><p>We will publish more blog posts about this as we progress through the project but, to begin with, we plan to beta test with one planning officer in each of our partner councils. We’ll start in Southwark, Lambeth and Buckinghamshire councils with Camden Council coming onboard later on. The planning officers involved in beta testing will use BoPS to assess applications for householder permitted development only — potentially starting testing with historical applications and then using it with new applications. You can <a href="https://www.gov.uk/service-manual/agile-delivery/how-the-beta-phase-works">find out more about how the beta phase works here</a>.</p><p>We are also engaging with other councils who are interested in being involved — <strong>please get in touch</strong> if you would like to find out more about the project (detail below)!</p><p>While our immediate focus is on moving the BoPS MVP into beta testing — so we can monitor and learn from how it’s being used and iterate accordingly — the medium-longer term vision is to expand BoPS so that it can be used to assess all types of a planning applications (non-householder permitted development through to major planning projects). Again, watch this space for further blog posts about this.</p><h4>Development roadmap…</h4><p>Our development roadmap is focussed on four key areas that will enable us to move into best testing with the councils mentioned above:</p><ul><li><strong>Developing the API to receive application data:</strong> from applicant facing services — starting with taking data from RIPA.</li><li><strong>Multi-council tenancy:</strong> infrastructure to ensure that planning authorities, and the officers in them, only see the applications submitted to their authority.</li><li><strong>Validation features:</strong> approving documents, displaying a payment reference, stating whether it is proposed or existing development, adding the ability to withdraw applications.</li><li><strong>Making data available:</strong> building on the API that was developed in the previous phase of the project so that planning data can be shared on a planning register and for reporting purposes, providing the ability to not publish certain documents (containing personal data).</li></ul><h4>Sprint notes:</h4><p>We kicked off this phase of the project with an alignment workshop with attendees from the partner councils mentioned above, Coventry Council and MHCLG. This gave us the wider team an opportunity to discuss their hopes and fears for the project, discuss potential risks (and how we can mitigate them), share the roadmap for this phase of work, and discuss how we can work together collaboratively.</p><figure><img alt="Project hopes workshop activity. Main hopes: quicker decisions, more councils involved, &amp; move into beta testing in 6 sprints" src="https://cdn-images-1.medium.com/max/1024/1*jqcvZXi2ItHWmgI8IGBTzA.png" /><figcaption>Screenshot from ‘Hopes and Fear’s activity in the project alignment workshop.</figcaption></figure><p>This was followed by a “sprint zero” — a short, one week sprint to allow newer members of the development team to explore and understand what has already been built and investigate how to approach some of the “big ticket” items, set up our agile meetings, and start re-kindling the relationships developed with other councils in earlier stages of the project (following a few months break since the last phase).</p><p>During our ‘sprint zero’ the team:</p><ul><li>researched and decided on the infrastructure required for supporting multi-council use of the product</li><li>had several meetings with RIPA’s development team</li><li>begun work on the API — a “spike” (ahem, that’s a technical investigation) to identify the best way to receive application data</li><li>started prototyping validation features — collaboration and co-design with a planning officer in Buckinghamshire Council (thanks Emily!)</li><li>demoed BoPS to Greenwich Council and Camden Council.</li></ul><p>We are now in our first full two-week sprint and you can see what we’re up to here, on our public backlog: <a href="https://trello.com/b/KQqYJd7W">https://trello.com/b/KQqYJd7W</a></p><p>We will share what we achieve in this sprint at out <strong>first Show and Tell </strong>on <strong>8th December at 11:30am </strong>(tune in at <a href="https://rebrand.ly/bops-show-and-tell">https://rebrand.ly/bops-show-and-tell</a>) and in our next sprint notes!</p><p>If you are interested in being involved in this project or have any questions please get in touch with Tom Buttrick, our product owner, at tom.buttrick@southwark.gov.uk or post a comment below.</p><p>You can also find the latest updates on Twitter at <a href="https://twitter.com/BoPs_Digital">@BoPs_Digital</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e020425d9ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ubxd/bops-is-back-sprint-notes-2e020425d9ea">BoPS is back! (sprint notes)</a> was originally published in <a href="https://medium.com/ubxd">Unboxed</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some ideas for what an alternative planning register could look like…]]></title>
            <link>https://medium.com/ubxd/some-ideas-for-what-an-alternative-planning-register-could-look-like-695332683c34?source=rss-b9bdab77545f------2</link>
            <guid isPermaLink="false">https://medium.com/p/695332683c34</guid>
            <category><![CDATA[plantech]]></category>
            <category><![CDATA[urban-planning]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[digital-planning]]></category>
            <dc:creator><![CDATA[Michelle Ann Isme]]></dc:creator>
            <pubDate>Thu, 09 Jul 2020 17:10:54 GMT</pubDate>
            <atom:updated>2020-07-09T19:03:53.340Z</atom:updated>
            <content:encoded><![CDATA[<h3>Some ideas for what a user centred planning register could look like…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GO8TbwoX9zj5TqrwKSlUhw.jpeg" /></figure><p>Yesterday, I published a <a href="https://medium.com/ubxd/is-now-the-time-to-build-a-national-planning-register-d95a869439f4">blog post</a> that questioned whether now is the time to pull local planning register data together onto a national platform. I also shared some of the feedback we’d heard, from planning officers, about the problems with some legacy planning registers... So, today, I’m going to share some ideas for what an alternative planning register could look like.</p><p>The reason we’re thinking about this is because we are in the middle of building a new back office planning system (<a href="https://bops.digital/">BoPS</a>), and will likely also need to develop some sort of planning register so that councils can fulfil their legislative duties, to publish planning applications and decisions… We also need to find a way for the main users of BoPS (planning officers) to obtain and review feedback from the public, something that is often done through the council’s planning register.</p><p>To tackle this we have several options:</p><ul><li><strong>Ask planning officers to upload applications to their existing registers</strong> (where existing software allows this). However, this will provide an additional admin burden that is not present now because existing back office systems integrate with their own registers.</li><li><strong>We can create a user-centred local planning register</strong> for each council which just shows the planning applications in their authority (same as now but, ideally, underpinned with plenty of user research, particularly with members of the public).</li><li><strong>We could also provide an api </strong>for the above local register, so that data can be fed into a separate, national platform in the future.</li></ul><h3>So, what could a planning register look like?</h3><p>My colleague, <a href="https://twitter.com/borisdivjak">Boris Divjak</a>, and I recently took what Unboxed calls an “innovation day” where we’re able to spend some time learning or working on something that interests us. As we’ve both been involved throughout the BoPs project, we’ve both caught the planning bug and wanted to have a go at mocking up some ideas for an alternative planning register.</p><p>You can see our ideas, below, but there’s a couple of caveats…</p><p>The biggie is that our prototypes are largely based around the needs of internal users (council planning teams) and hearing about some of the problems they face when assessing applications. However, lots of research and testing needs to be done with the users who need to look at planning registers and, in some cases, provide feedback on applications — namely the public.</p><p>We’ve also considered some of the potential opportunities a national register could provide, with an eye on the <a href="https://digital-land.github.io/project/single-register-of-planning/discovery/">research conducted by MySociety and MHCLG</a> and the thought provoking articles ( <a href="https://futurecities.catapult.org.uk/2019/05/10/building-a-21st-century-digital-planning-system-a-quick-start-guide/">here’s one of many</a>) published by Future Cities Catapult.</p><p>However, we’re bound to have made a few assumptions, too, that would need to be validated (or not).</p><p>Lastly, our prototypes are based on householder planning applications (i.e adding an extension to an existing house rather than developing a whole new building) because this is what our BoPS project is focussing on, but we think there’s potential to include other types of developments in the future.</p><p>Caveats out of the way.. <a href="https://www.figma.com/proto/8G5PxbJUUEUg8S0VPwAKA9/Planning-register?node-id=1065%3A2&amp;scaling=scale-down"><strong>Check out the prototype here.</strong></a></p><h4>Planning register homepage:</h4><p>A clean, simple homepage to make it easy to search planning applications. This could also provide a starting point to share high level stats and data too.</p><figure><img alt="Screenshot from prototype showing a search page to search planning applications in the UK" src="https://cdn-images-1.medium.com/max/1024/0*BxJy00TNdxekTS6H.png" /></figure><p><strong>Research required:</strong></p><ul><li>How do different types of users need to search a planning register?</li><li>Which data points are useful to share?</li><li>Should we provide stats on the planning register or would this be better surfaced in a separate standalone service, perhaps pulling data from the register?</li></ul><h4>Search results page:</h4><p>A page displaying a list of planning applications, highlighting key information such as the application type and its status. Over time the register could also group together multiple applications that relate to the same site.</p><figure><img alt="Screenshot of the search results page in our prototype, which includes options to filter results." src="https://cdn-images-1.medium.com/max/1024/0*lPiZaJ9jjqUw8vm7.png" /></figure><p>Research required:</p><ul><li>How do users need to be able to filter results?</li><li>What key information should be presented on this page?</li></ul><p>Known challenges:</p><ul><li>It will not be possible to display existing, historical applications unless data can be extracted from the various back office planning systems and registers that councils currently use.</li></ul><h4>Application page:</h4><p><a href="http://www.legislation.gov.uk/uksi/2010/2184/article/36/made">Planning legislation</a> states that local planning authorities must publish applications with any accompanying plans and drawings, the reference number, decision and the date of the decision. We took these requirements as a starting point but have also thought about the kind of information that might be useful for someone who wants to find out about and understand a proposal.</p><p>Currently, application documents are published on registers as downloadable PDF forms but if data is supplied in a structured format, to systems like BoPS, it can be displayed directly on the application page. We have also experimented with how different steps of the assessment process could be displayed to enable users to quickly grasp at what stage an application is at. This could, potentially, also be useful for applicants when they want to check on the progress of their application.</p><figure><img alt="Prototype page showing information about a planning application including details about the proposal, drawings, map &amp; status" src="https://cdn-images-1.medium.com/max/1024/0*8DE2uJQ9kdETnD12.png" /><figcaption>Note: The image shows a prototype page for an application for householder planning permission. You can also see a prototype for a simpler application, for a certificate for <a href="https://www.figma.com/proto/8G5PxbJUUEUg8S0VPwAKA9/Planning-register?node-id=1065%3A91&amp;scaling=scale-down">lawfulful development</a>.</figcaption></figure><p>Research required:</p><ul><li>What’s the most important information to different types of users?</li><li>Content — can people who have had little or no prior exposure to the planning process understand what the application is for? Is this the best format and order to display information about the application?</li><li>Should the planning register be used to update applicants on the status of their application or would this need be better served through automatic updates emailed from the back office planning system, or by the applicant logging in to the system they used to apply in the first place?</li><li>Some developments will have a lot of plans and documents — what’s the best way to display these to users?</li></ul><p>Known challenges:</p><ul><li>At the moment plans and drawings, for householder development, are generally provided in PDF format which may not be very accessible and could also create challenges when trying to open and view them. However, there is also potential to scale up functionality in future, potentially taking advantage of other “Plan Tech” products on the market such as <a href="https://vu.city/">VU.City’s</a> 3D maps.</li><li>Maps! There are whole blog posts just about this but, in a nutshell, there might be problems with licensing that mean displaying a map on a page, with the site boundary around a property, could be a lot trickier than it looks. The team behind the <a href="https://www.ripa.digital/">RIPA projec</a>t have recently started to delve into some of this so I’ll direct you to <a href="https://medium.com/@digitalplanning/maps-4e4a68458176">their blog post</a>…</li><li>To present applications in this way also requires data, generated by applicants when they first apply and by the back office systems used to assess them, to be provided in a structured format.</li></ul><h3><strong>What about consultation…?</strong></h3><p>It’s tricky to know where to start on this.</p><p>We’re aware of some problems (discussed in <a href="https://medium.com/ubxd/is-now-the-time-to-build-a-national-planning-register-d95a869439f4">yesterday’s blog post</a>) based on what planning officers have told us but we’ve only really got one side of the story so, again, we’d really love to do some user research with:</p><ul><li>Members of the public who need to be able to comment on local and neighbouring developments</li><li>Community groups and organisations that comment on particular types of development e.g developments in their area.</li><li>Statutory consultees that are regularly asked to comment on developments, based on their expertise. This could be the authority’s own design or transport teams but it might also include regional or national organisations such as Transport for London or the Environment Agency. You can see a <a href="https://www.gov.uk/guidance/consultation-and-pre-decision-matters#Statutory-consultees-on-applications">list of national consultees here</a>.</li></ul><p>The <a href="https://blogs.hackney.gov.uk/hackit/hackneys-drive-for-a-digital-submit-my-planning-application-service-2">Submit My Planning Application</a> project, led by Snook and Hackney council, did plenty of user research with the public but their main focus was on applicants. However, we did find a quote from a member of the public that had provided consultation feedback on planning applications:</p><blockquote>“You don’t get much info on why your objection isn’t valid. The letter does not address specific comments you might have submitted. It’s very generic.”</blockquote><p>We’d like to explore this further with more research.</p><p>We have also had a quick look at some of the <a href="https://www.gov.uk/guidance/consultation-and-pre-decision-matters">legislative requirements for planning consultation</a>. However, there are still gaps in our knowledge and we’d like to find out:</p><ul><li><strong>Are councils required to make all consultation feedback public?</strong> — does statutory and public consultation feedback have to be published? And, if so, how long does it need to be available for and what are the GDPR implications?</li><li><strong>Does the council have to respond to consultees?</strong> Do they need to respond to all of them or just those that object? And, again, do the responses also have to be publicly available?</li><li><strong>Does consultation have to take place on the register?</strong> We don’t think it does (see below) but it’s not 100% clear. Most registers do provide a very basic feedback form but is this largely based on convenience, as the application and drawings are already on the register?</li></ul><p>We also considered what we have learnt from our BoPS user research with planning officers, who need to review consultation feedback. From this point of view it would be helpful if:</p><ul><li><strong>consultation feedback is easy for planning officers to find</strong> and refer to during their assessments</li><li><strong>planning officers can see high-level stats about consultation</strong>, such as the number of comments received and how many of these comments are objections — this helps officers to estimate how much time may be required to complete their assessments.</li><li><strong>feedback can be filtered by objections, neutral and supportive comments</strong> i.e so planning officers can prioritise reviewing objections</li><li><strong>feedback can be filtered based on the type of user that has provided it</strong> — different types of feedback is useful during different points of a planner’s assessment e.g it is helpful to refer to any objections from neighbours when assessing the impact the proposal will have on neighbouring properties.</li><li><strong>public feedback is structured around planning policy</strong> — we’ve heard that some of the feedback provided by public consultees isn’t always a material consideration under planning policy… <strong>would it be helpful to guide public consultees</strong> by asking them to provide feedback on specific things?</li></ul><p>With some of these things in mind we started <a href="https://www.figma.com/proto/8G5PxbJUUEUg8S0VPwAKA9/Planning-register?node-id=1019%3A217&amp;scaling=scale-down">prototyping a structured form</a> for gathering consultation feedback. Our prototype for this is incomplete as more time needs to be spent on researching what kind of guidance, if any, public consultees need.</p><p>Here are some screenshots:</p><figure><img alt="Prototype shows the a consultation form, asking users to choose the capacity in which capacity they’re commenting" src="https://cdn-images-1.medium.com/max/1024/0*tfS3uPfhItTsrBeU.png" /></figure><figure><img alt="Prototype of a consultation feedback form, asking users whether they are objecting, supporting or neutral about the proposal" src="https://cdn-images-1.medium.com/max/1024/0*k6U47Nd3e9JLwqo2.png" /></figure><p>This is one approach but we know that other platforms exist, or are being developed, that might be better placed to facilitate consultation — such as <a href="https://www.commonplace.is/">Commonplace</a> or <a href="http://www.civicvoice.org.uk/">Civic Voice</a> (who, by the way, we presented alongside at a <a href="https://youtu.be/1XqjGpMcoWU">Connected Places webinar</a> earlier this year).</p><p>Although planning legislation is clear on the need to consult for different types of applications it also states that:</p><blockquote>“Local planning authorities have discretion about how they inform communities and other interested parties about planning applications.”</blockquote><p>Further investigation is required but this might mean that consultation doesn’t need to take place on the planning register itself. However, any alternative options for facilitating planning consultation will ideally collect feedback in some of the ways mentioned above.</p><p>As I’m sure I’ve drummed on about enough, already, we really need to do more research and testing with users as well as exploring what technology is already available.</p><p>And we created these prototypes largely to take what we’ve been learning, from planning officers, and turn it into something tangible that we could share and get feedback on.</p><p>So, we would like to hear any thoughts you have on our prototypes (don’t worry, we expect them to be flawed and we’re not precious about them!) and any of the points raised in this or <a href="https://medium.com/ubxd/is-now-the-time-to-build-a-national-planning-register-d95a869439f4">yesterday’s blog post</a>.</p><p>Share your thoughts below or on twitter with <a href="https://twitter.com/icoo">@icoo</a> :)</p><p><em>Originally published at </em><a href="https://unboxed.co/blog/some-ideas-for-what-an-alternative-planning-register-could-look-like/"><em>https://unboxed.co</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=695332683c34" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ubxd/some-ideas-for-what-an-alternative-planning-register-could-look-like-695332683c34">Some ideas for what an alternative planning register could look like…</a> was originally published in <a href="https://medium.com/ubxd">Unboxed</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is now the time to build a national planning register?]]></title>
            <link>https://medium.com/ubxd/is-now-the-time-to-build-a-national-planning-register-d95a869439f4?source=rss-b9bdab77545f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d95a869439f4</guid>
            <category><![CDATA[digital-planning]]></category>
            <category><![CDATA[plantech]]></category>
            <category><![CDATA[local-digital]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[urban-planning]]></category>
            <dc:creator><![CDATA[Michelle Ann Isme]]></dc:creator>
            <pubDate>Wed, 08 Jul 2020 19:00:17 GMT</pubDate>
            <atom:updated>2020-11-30T20:03:15.195Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="A gif showing a map of the UK, zooming out from a pin on one property in London to show map pins across the whole of the UK." src="https://cdn-images-1.medium.com/max/1024/0*vud7TgMOtl_khBlQ.gif" /></figure><p><strong>Quick answer:</strong> we think it might be!</p><p>We’re currently building a new back office system (<a href="https://bops.digital/">BoPS</a>) for council planners to more easily assess planning applications from householders.</p><p>However, when an application comes into the council it doesn’t just need to appear in the back office system — the council is also required to publish planning applications, as outlined by <a href="http://www.legislation.gov.uk/uksi/2010/2184/article/36/made">planning legislation</a>.</p><p>And this is where planning registers come in.</p><p>Each local authority has its own planning register where it publishes planning applications and decisions. With this in mind, we’ve developed a simple api to allow data about applications to flow through and out of BoPS i.e onto a register.</p><p>The problem, however, is that planning registers are currently provided by existing back office planning systems and they are generally not open to allow alternative systems to push data to them.</p><p>We’re certainly <a href="https://digital-land.github.io/blog-post/a-short-history-of-planning-application-data-projects/">not the first to mull over this problem</a> but it’s not something we can ignore now that we’re developing an alternative back office system.</p><p>As well as providing a public audit trail of planning decisions, planning registers also provide a vehicle for getting feedback on applications.</p><p>We began the BoPS project by focussing on <a href="https://medium.com/ubxd/how-were-making-it-easier-to-assess-planning-applications-and-why-we-re-starting-with-permitted-b06d5462bf55">permitted development applications</a> and these generally don’t require consultation.</p><p>Now that we are about to move onto handling the assessment of applications for full householder planning permission, we will need to find a way to facilitate consultation… And to do that we need to enable members of the public to easily find and see applications.</p><p>The way it works at the moment is largely like this (give or take a few discrepancies between different systems):</p><ol><li>An application is received by the back office system and validated.</li><li>The planning officer can now start assessing the application in their back office system. At the same time, the application is published onto the planning register.</li><li>The application’s page on the planning register will include links to the application form, drawings and any other documents the applicant submitted. If the proposal requires consultation, there will also be a feedback form that anybody can complete to state whether they support or object to the proposal and why.</li><li>The council also alerts any neighbours to this page by sending them a letter or an email and the majority of councils also stick a notice to a lamp post near the property.</li></ol><figure><img alt="Planning application notice on a lamp post" src="https://cdn-images-1.medium.com/max/480/0*K45haQjl_egFc4Q4.jpeg" /><figcaption><em>Planning notices on lampposts — </em><a href="https://mhclgdigital.blog.gov.uk/2020/05/28/start-treating-planning-applications-as-data-rather-than-documents/"><em>this isn’t necessarily the way forward!</em></a></figcaption></figure><p>The most immediate problem, for BoPS, is that we need to facilitate a way for councils to meet the legislative requirements to publish planning applications (the legislation specifies <a href="http://www.legislation.gov.uk/uksi/2010/2184/article/36/made">what has to be on the register</a>) and allow for consultation.</p><p>If they can’t do this it will likely prove to be a blocker for councils to use the BoPS system.</p><p>However, it shouldn’t just be a case of replicating what’s available now because after speaking with over 60 planning staff in different councils, throughout the duration of the BoPS project, we’ve heard about some of the problems that already exist in relation to planning consultations.</p><p>These include:</p><ul><li><strong>It can be difficult to find and refer to consultation feedback during assessments</strong> — some officers have told us that they receive an email when a new comment has been submitted on the register. One officer told us that every bit of consultation feedback is turned into a PDF and uploaded to their back-office planning system, which can be difficult to sort through and review during their assessment particularly when there has been a lot of feedback.</li><li><strong>Feedback from public consultations can be long and time-consuming to assess</strong> — this alone is not the problem. The issue is when objections are raised that don’t pertain to planning policy (material considerations), where the planning officer can do very little about it.</li><li><strong>Planning staff have to “redact” consultation comments</strong> — comments are submitted via an application’s page on the planning register and then later published onto that page. However, some back office systems require council staff to review and redact personal information before the comment can be published… can some of this be automated?</li></ul><p>What we don’t have, and would really need, is research with people who use planning registers and need to provide consultation feedback. However, we have had a look at some of the research others have done, such as Snook’s work on the <a href="https://research.localgov.digital/projects/planning-applications/">Submit My Planning Application service</a> with Hackney Council, and made some assumptions (that would need to be tested):</p><ul><li><strong>Planning registers are difficult for people that don’t have any planning knowledge to understand</strong>. Looking at existing planning registers, we felt it was difficult to quickly grasp what a proposal was for and wondered whether the technical and planning-specific content on some registers is understood by the public.</li><li><strong>The public need more guidance about what they can and can’t object to</strong><em> </em>- some consultation forms are centred around an open text box and provide very little guidance to applicants. We wondered whether this might be a contributing factor to some of the problems planning officers face when reviewing feedback (as outlined above).</li></ul><p>Arguably the above problems could be solved by injecting a dollop of user centred design into the process of building a new local planning register.</p><p>However, publishing local planning data onto a national platform could also help to tackle a few other problems:</p><ul><li><strong>there’s a lack of consistency across registers</strong> that are provided by different suppliers, which makes it hard to analyse and compare data across different authorities, unless they happen to use the same system. And if legislation is changed each system will need to be updated.</li><li><strong>councils can end up with multiple planning registers</strong> when they change their back office systems — unless they are able to migrate data from their old register into the new one (and it’s often not possible to do that) their residents will be required to search through both registers which, as mentioned above, may also look different.</li><li><strong>it is difficult to get an up-to-date picture of planning on a national scale</strong> — although MHCLG publishes <a href="https://www.gov.uk/government/collections/planning-applications-statistics">national planning statistics</a> these are done on a quarterly basis, and are drawn from the <a href="https://www.gov.uk/government/publications/district-planning-matters-return-ps1-and-ps2">PS1 and PS2 reports</a> that each council has to collate and send to them.</li></ul><p>The last point is particularly problematic for projects like BoPS.</p><p>Planning officers often need to check the planning history of a site when assessing a new proposal. For example, if an applicant wants to extend their property by 3 metres at the back, and this is permitted under planning legislation, the officer needs to make sure the property hasn’t already been extended before. To do that, now, the officer will check whether there are any previous applications associated with a site in the back office system.</p><figure><img alt="Sketches showing how the same property has had 3 planning applications to extend different parts of it over 10 years" src="https://cdn-images-1.medium.com/max/1024/0*dneCNhEzQC_dMwik.jpg" /></figure><p>If there was a national platform which pulled data from local planning registers, the officer could simply look up the property on there instead, which would make it easier to start using a new back office system like BoPS. Alternatively, and in an ideal world, that platform might even provide an api so projects like BoPS could pull in planning history and display it to users when they need it!</p><p>To understand more about the problems with obtaining planning data, I strongly recommend you take a look at this <a href="https://digital-land.github.io/project/single-register-of-planning/discovery/">extensive research</a> by MySociety.</p><p>While developing the api, to share data from BoPS, we have also developed a proof of concept planning register that simply lists the outcome of applications — basically whether they were granted or refused.</p><figure><img alt="Screenshot of our proof of concept register which lists all of the householder planning applications and the decisions" src="https://cdn-images-1.medium.com/max/1024/0*G837eipuJvbd2yzv.jpg" /></figure><p>This is not an MVP planning register because although it’s minimal, it isn’t really viable, as it currently only lists the decision of applications and not the detail of them e.g drawings.</p><p>The reason we haven’t developed an MVP is because the users of BoPS (planning officers and managers) are not the primary users of planning registers, and to know what needs to be built we would need to do some more user research.</p><p>So, who are the users?</p><p>As we haven’t done the research this probably isn’t an exhaustive list but here are the users we know about:</p><ul><li><strong>Neighbours and local residents </strong>who want to provide feedback on a nearby development e.g the house next door that wants to add an extra storey to their home.</li><li><strong>Local community groups</strong> that want to stay aware of (and when required) respond to developments in their area. For example, this might be a neighbourhood group that is opposing a major development.</li><li><strong>Statutory bodies</strong> that also need to provide feedback during consultation. These may include teams based in the council, such as the council’s highways team, but could also be staff working in national bodies that are consulted for their expertise.</li><li><strong>Planning staff</strong><em> </em>- planning officers sometimes use their council’s public register to search for data as it is easier than looking for it in their current back office system.</li><li><strong>Other council staff </strong>—<strong> </strong>enforcement teams, legal teams etc…</li></ul><p>We also suspect that applicants could use planning registers to:</p><ul><li><strong>Keep updated on progress</strong> — planning officers have told us that applicants call up to ask what stage their application is at. Automatically pushing more updates, and perhaps more specific statuses, to a register might be a way to keep applicants in the loop. However, this problem might also be better solved through the software applicants use to submit their applications.</li><li><strong>Read consultation feedback</strong> e.g from neighbours</li><li><strong>Do research before submitting an application</strong><em> </em>- has anybody else in the neighbourhood submitted a similar proposal? Were they granted permission? Which architects did they use?</li></ul><p>And if we think about a national platform that pulls data from local registers, it’s likely that it could be beneficial to other users too, including:</p><ul><li><strong>Central government</strong> — instead of collating data from each individual council, could they just go and get it directly from a national platform? Could that platform even do some of the number crunching for them?</li><li><strong>Developers and architects</strong><em> </em>- perhaps to identify planning trends in particular areas.</li><li><strong>PlanTech companies</strong> — if a national platform existed and provided an api this might be of use to companies operating in the “plan tech” space.</li><li><strong>Number-crunchers and commentators</strong> — I don’t know really what to call these users and they might be any of the people I’ve mentioned above. They might be economists, journalists, market analysts, urban planning gurus. They might write reports with titles like, “20% increase in demand to extend houses, over the last fives years, will push the average house price up by £X”</li><li>And maybe, one day, <strong>historians</strong> that want to understand how an area has changed over time!</li></ul><p>Again, for more information about the users of planning data check out the <a href="https://digital-land.github.io/project/single-register-of-planning/discovery/">excellent research</a> that MySociety have done in partnership with MHCLG’s Digital Land team.</p><p>-</p><p>So, that’s why planning registers are important, who uses them, and the benefits that could come from bringing planning data together onto a national platform. Tomorrow, I’ll share some ideas we’ve prototyped for what an alternative planning register could look like…</p><p>If you have any thoughts or comments please share them below — planning can be a minefield so please let me know if I’ve missed anything! :)</p><p><em>Originally published at </em><a href="https://unboxed.co/blog/is-now-the-time-to-build-a-national-planning-register/"><em>https://unboxed.co</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d95a869439f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ubxd/is-now-the-time-to-build-a-national-planning-register-d95a869439f4">Is now the time to build a national planning register?</a> was originally published in <a href="https://medium.com/ubxd">Unboxed</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we’re making it easier to assess planning applications and why we’re starting with permitted…]]></title>
            <link>https://medium.com/ubxd/how-were-making-it-easier-to-assess-planning-applications-and-why-we-re-starting-with-permitted-b06d5462bf55?source=rss-b9bdab77545f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b06d5462bf55</guid>
            <category><![CDATA[govdesign]]></category>
            <category><![CDATA[urban-planning]]></category>
            <category><![CDATA[plantech]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Michelle Ann Isme]]></dc:creator>
            <pubDate>Fri, 24 Apr 2020 14:10:37 GMT</pubDate>
            <atom:updated>2020-04-25T08:08:37.572Z</atom:updated>
            <content:encoded><![CDATA[<h3>How we’re making it easier to assess planning applications and why we’re starting with permitted development</h3><figure><img alt="Photo of post-it notes with hand-drawn images of floor plans, houses and trees — from an activity in a workshop with partners" src="https://cdn-images-1.medium.com/max/1024/1*AjN3a8l0GXh1JTwOQRFmPg.jpeg" /></figure><p><em>Written in collaboration with Jack Ricketts, Southwark Council.</em></p><p>When it comes to the UK planning system there are many problems to solve.</p><p>It’s fair to say that very few people, possibly nobody, enjoys applying for planning permission. Navigating a myriad of guidance to determine whether or not you need to apply in the first place, pulling together everything that’s needed to submit an application, and then completing the application itself, are not fun tasks.</p><p>The process is confusing, labour intensive and frustrating which is why many applications arrive invalid. However, there are <a href="https://sites.google.com/hackney.gov.uk/submit-my-planning-application/home">other projects</a> that are looking to improve the process for applicants.</p><p>We’re interested in what happens next.</p><p>Specifically, how we can build a back office planning system that makes it as easy as possible for planning teams to assess applications.</p><h4><strong>The problems to solve…</strong></h4><p>Our recent <a href="https://unboxed.co/blog/the-future-planning-system-for-local-authorities/">blog post</a> detailed the problems we’re looking to solve — <em>with </em><a href="https://www.southwark.gov.uk/innovate/collabrative-project/planning-back-office"><em>Southwark Council</em></a><em>, </em><a href="https://localdigital.gov.uk/funded-projects-round-1/user-centred-back-office-planning-system-to-unlock-transformation/"><em>MHCLG</em></a><em>, and partners</em> — but here’s a quick re-cap of some of the biggest challenges planning teams face with existing processes and systems:</p><ul><li><strong>They are hard to use</strong> — they’re inaccessible, poorly designed and disjointed, which makes it difficult for planners to easily find the information they need to assess applications. In addition, many existing systems have not been designed for use on tablets or mobiles, so the notes and photographs planners make whilst on site visits have to be emailed and uploaded to the back-office system later.</li><li><strong>They rely on manual workarounds</strong> — planning officers have to copy and paste the address that the application refers to into external systems to view maps and identify local constraints. Email integration is often poor or non-existent which makes it harder to record the interactions between planning teams, applicants and their agents.</li><li><strong>They lock in data</strong> — information generated by the planning officer during the assessment process is created and stored inside documents e.g launching a Word document that the planner has to fill in. This results in a lack of structured data that makes it harder, for instance, to automatically push out more frequent updates to applicants. It also makes it harder to export data for strategic reporting purposes.</li><li><strong>They block innovation</strong> — many legacy systems do not allow for integration with other tools that will aid planning teams.</li></ul><h4><strong>Why we’re focussing on householder applications</strong></h4><p>Householder applications consume about 50% of officers’ time so our initial focus is to build a better system for assessing applications from residents e.g a roof extension to a house.</p><figure><img alt="A screenshot from a prototype we are testing with planning teams. It shows a list of the new applications that have come in." src="https://cdn-images-1.medium.com/max/1024/1*fiLmoC33TwMoRBdmNHm3TA.jpeg" /><figcaption>Planners’ work list — one of the screens that our designer, <a href="https://medium.com/@claudia.i.hopkins">Claudia Hopkins</a>, has been prototyping and testing with planning teams.</figcaption></figure><p>However, even within that narrowed scope there are a few different types of householder application, such as:</p><ul><li><strong>Certificates of lawfulness (CoL) for permitted developmen</strong>t <strong>(PD)</strong> — national legislation allows homeowners to make some simple alterations to their property without having to apply for full planning permission. This is known as ‘permitted development’ and residents can apply for a ‘certificate of lawfulness’ to prove that the alterations they have made, or propose to make in the future, are inline with national legislation. A resident may apply for a certificate of lawfulness in order to show potential buyers, when they’re selling their home.</li><li><strong>Prior approvals</strong> — this is still for permitted development but is for certain types of alterations to larger properties, and therefore requires a little more scrutiny and a degree of consultation.</li><li><strong>Full planning permission</strong> — for applicants who are proposing to make alterations that are not covered under permitted development legislation. This may be because, for instance, the applicant wants to significantly extend their property, or permitted development rights have been removed on that property.</li></ul><p>Each of these types of application have different assessment needs.</p><p>When a planning officer is assessing an application for a certificate of lawfulness, they are ultimately checking that what the applicant is proposing to do meets the conditions set out in the <a href="http://www.legislation.gov.uk/uksi/2018/343/made">General Permitted Development Order</a>.</p><p>It’s a technical assessment, of a binary nature.</p><p>The same applies to prior approvals but there is an additional requirement to consult with neighbours.</p><p>If no valid objections are received during consultation and the proposal meets the requirements for permitted development, it will be considered to have prior approval and the applicant will be granted a certificate of lawfulness. If valid objections are received the applicant has the option to either make changes to their proposal or apply for full planning permission.</p><p>With applications for full planning permission an officer is not only checking proposed plans against a raft of planning policy, they are also taking into consideration the impact on neighbours and how the alterations may affect local design and heritage.</p><p>To do this they often make a site visit and consult with neighbours as well as any relevant statutory bodies such as the highways authority.</p><h4><strong>Getting started with Permitted Development</strong></h4><p>In one sense, Permitted Development (applications for certificates of lawfulness) are already very much the MVP of householder applications because:</p><ul><li>it’s a technical assessment</li><li>it’s based around national legislation</li><li>it doesn’t require consultation or site visits</li></ul><p>Kicking off our beta project by focussing on permitted development will also ensure we can deliver a standalone service quickly and start adding value to users sooner.</p><figure><img alt="Image of a drawing showing a computer in the system with data feeding out of it and into different systems." src="https://cdn-images-1.medium.com/max/1024/1*KQDoINiPiVFenW1b_T-Mrg.jpeg" /><figcaption>Sketch from an early ‘ideation’ workshop with project partners</figcaption></figure><p>It also makes sense from a software development perspective as many of the elements of building a service for assessing PD applications can be reused, but added to, to assess more complex applications later, including:</p><ul><li><strong>Getting the right infrastructure in place</strong> so we can ensure that our system doesn’t recreate the same problems that exist now, including making it easier to pull in and export relevant data.</li><li><strong>Providing a way for users to log in</strong> and access the functionality they need to do their jobs.</li><li><strong>Displaying relevant planning policy</strong> <strong>and legislation </strong>to guide planners in their assessments — this will be particularly helpful for junior planning officers.</li><li><strong>Present a clear overview of an application</strong> so planners can quickly understand what the applicant is proposing, including a way to easily view plans and drawings.</li><li><strong>Making a recommendation</strong> — enabling planning officers to make a recommendation and for planning managers to make a final determination.</li><li><strong>Inform applicants of the decision</strong>.</li></ul><p>In addition the <a href="https://www.ripa.digital/">RIPA project</a> (reducing invalid planning applications) — that is also being funded by MHCLG — is concentrating on PD first and we are keen to join forces and work together to tackle problems, in the spirit of <a href="https://localdigital.gov.uk/about/">local digital collaboration</a>.</p><h4><strong>Scaling up later…</strong></h4><p>Although, during the first half of the project, we will concentrate on developing a minimum viable product that allows planners to assess permitted development applications, we know there’s room to add a lot more value by tackling householder applications for full planning permission.</p><p>That’s why — half way in — we will take stock and, following discussion with our partners and stakeholders, likely pivot to scale what we’ve already built to incorporate the additional elements required to assess the other application types.</p><p>The research that our design team is doing now will also feed into the additional functionality that will be required later, such as how to handle consultation.</p><figure><img alt="Photo of a user research session: Martyn Evans at Unboxed discusses a prototype with a planner from Coventry Council" src="https://cdn-images-1.medium.com/max/1024/1*9n2VBsz4Aycq8dOoTJmezg.jpeg" /><figcaption>User research we undertook earlier in the project (we’re now testing our new prototypes with users).</figcaption></figure><p>So, that’s our current ‘plan’ but as with all agile projects, things may change as we learn more from user testing.</p><p>We’d love your feedback — please leave a comment or email us (info below).</p><p>We’re also looking at what data is available now so we can use it to benchmark against and measure how our system is adding value. For instance, the data councils submit to feed into national <a href="https://www.gov.uk/government/collections/planning-applications-statistics">planning application statistics</a>.</p><p>If anyone is aware of other data sources that it might be useful for us to have a look at, we’d love to hear from you!</p><p>Get in touch:</p><ul><li>jack.ricketts@southwark.gov.uk</li><li>michelle.isme@unboxedconsulting.com</li></ul><p><em>To follow our progress look out for more blog posts and weeknotes, from the team, on the </em><a href="https://medium.com/@ubxd"><em>Unboxed Medium blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b06d5462bf55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ubxd/how-were-making-it-easier-to-assess-planning-applications-and-why-we-re-starting-with-permitted-b06d5462bf55">How we’re making it easier to assess planning applications and why we’re starting with permitted…</a> was originally published in <a href="https://medium.com/ubxd">Unboxed</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why knowing what I won’t negotiate on helps me be a better product manager]]></title>
            <link>https://misme.medium.com/why-knowing-what-i-wont-negotiate-on-helps-me-be-a-better-product-manager-f016a0d01df7?source=rss-b9bdab77545f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f016a0d01df7</guid>
            <category><![CDATA[resilience]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Michelle Ann Isme]]></dc:creator>
            <pubDate>Thu, 06 Dec 2018 00:17:45 GMT</pubDate>
            <atom:updated>2018-12-06T00:17:45.257Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g36UzGO5hNDJEJXNgadd2g.jpeg" /></figure><p>In product management saying ‘no’ is just a part of the job.</p><p>Everyone has ideas for features — some good, others less so — but even the great ones are often not backed up by much more than just a hunch. And, when they are, they still might not be the right thing to build right now so you are going to have to say no, at least temporarily.</p><p>Then there’s that invaluable piece of user feedback, which you’d love to address ASAP (because who doesn’t want to make things better for users?), but you’ve only got two developers and they’re going to be busy for a while building something that another set of users also desperately need. Again, time for another ‘temporary no’ (aka. “we really appreciate your feedback and have added it to our backlog”).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl41YkuOX4AP61mvle%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fwarnerarchive-warner-archive-strange-brew-l41YkuOX4AP61mvle&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl41YkuOX4AP61mvle%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/f33a93ec2c7604426dc5981f239e7350/href">https://medium.com/media/f33a93ec2c7604426dc5981f239e7350/href</a></iframe><p>And then there are the good old-fashioned no’s you have to dole out when someone else — often driven by good intentions — has promised your product will deliver something you know will add little to zero value.</p><p>Or the undeliverable deadlines you’ve inherited… In this case saying no early on is not only a way to avoid setting the team up for failure — it’s also just the right thing to do... I’ve found it’s far better to be honest and upfront with stakeholders about things like this, even if it’s uncomfortable in the short-term, to avoid burning bridges in the long-run. More importantly, saying no to impossible demands early on provides an opportunity to explore the possibilities that are, erm, possible.</p><p>But while saying no is frankly just part of a product manager’s job, it doesn’t mean it’s enjoyable.</p><p>To be a good PM you have to be ok with being ‘bad cop’ (saying no), ‘stupid cop’ (asking the really obvious questions), and ‘disappointing cop’ (prioritisation means that not everyone’s needs can be met first). To be ok with playing these roles you need not only to leave your ego at the door but you also need a degree of resilience.</p><p>Saying no, sometimes several times to the same group of people, can be absolutely draining and without resilience you might find yourself giving in where you shouldn’t and, worse, doubting your own decisions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3o72wGp7QlJdaZNFYc%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fhappy-smile-sad-3o72wGp7QlJdaZNFYc&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3o72wGp7QlJdaZNFYc%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="200" frameborder="0" scrolling="no"><a href="https://medium.com/media/4c01b1cb42c53b9d0b5eb63e0bef5bef/href">https://medium.com/media/4c01b1cb42c53b9d0b5eb63e0bef5bef/href</a></iframe><p>I’ve built up resilience as I’ve got older and had more experiences (including plenty of fails!) and through overcoming a lot of personal difficulties (but that’s for another blog post).</p><p>However, I’ve also learnt what ‘my product management principles’ are… Basically, what I’ll fight tooth and nail for and what I’m willing to relinquish or meet halfway on (because sometimes that’s also the right thing to do).</p><p>Most importantly, I know what my ‘non-negotiables’ are — the things I would be willing to walk away for.</p><p>They are:</p><p>1. I will not create digital products or services that will knowingly* harm a user(s) or put them at risk of harm.<br>2. I won’t create digital products or services that purposefully mislead users e.g manipulating them to sign up for things / take actions they probably don’t want.</p><p>Of course, there are plenty of other things I push back on such as building features that nobody needs; sacrificing good design over good technology and vice versa; building digital products without any plan for how they will be maintained or growing a mountain of future technical debt. At the same time I know that things don’t and can’t always go to plan — a lesson drummed into me when I was working in a fast (and chaotic) start-up for two years — and being a purist in such situations often isn’t helpful.</p><p>However knowing that, no matter what, I will not choose to work on products or prioritise features that will knowingly cause (a risk of or) harm or mislead people is what helps me stay focused and not lose confidence when my ‘no’ is taking a little while to be heard.</p><p>To identify your own ‘non-negotiables’ think about what you drives you, why you chose to be a PM in the first place, what you love about your job. For me, coming at it from a design and user experience background, what I love most about being a PM is building stuff that can make somebody’s life a little bit easier in some way — whether that’s making it easier for someone to check their bank balance or making it easier for a farmer to assess whether a <a href="https://data.blog.gov.uk/2017/03/20/creating-a-register-for-managing-water-levels/">plot of land is suitable</a> for growing crops. And the opposite of that is making people’s lives a little bit harder in some way, such as by causing harm.</p><p>Happy non-negotiating!</p><p>—</p><p><em>It goes without saying that there are good and bad ways to tell people ‘no’ but I’m assuming anyone reading this knows all about, and practices, respect at work! And, in my experience, a no is often better received when delivered with a clear set of reasons why and, where possible, when you’ve got an alternative option or two up your sleeve.</em></p><p><em>I also believe it is possible to build features that eventually turn out to be harmful but that there was no way of knowing that at the time. Justin Rosenstein, who created the Facebook ‘like’ button sums it up in </em><a href="https://www.theguardian.com/technology/2017/oct/05/smartphone-addiction-silicon-valley-dystopia?CMP=aff_1432&amp;awc=5795_1544053393_be04279cb31582d1601f9fe906b64713"><em>this Guardian article</em></a><em> when he says: “It is very common for humans to develop things with the best of intentions and for them to have unintended, negative consequences.”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f016a0d01df7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dear service design, what are you?]]></title>
            <link>https://misme.medium.com/dear-service-design-what-are-you-e196612d0c84?source=rss-b9bdab77545f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e196612d0c84</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[service-designer]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Michelle Ann Isme]]></dc:creator>
            <pubDate>Wed, 20 Sep 2017 12:31:05 GMT</pubDate>
            <atom:updated>2017-09-20T22:53:34.718Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*6HRWbS0m4zXfr9AIxuSg0A.jpeg" /><figcaption>Just because you can be a dinosaur, doesn’t mean you have to be.</figcaption></figure><p>The service design industry — just like many growing industries today — is having a bit of an identity crisis. Is it about user research? User centred design? Business design? Workshop facilitation? Even a bit of, dare I say it, good old fashioned project management?</p><p>These were some of the questions jotted on the post-its — from here on referred to as ‘squares-of-woe’ — that clung to the wall of the <a href="http://www.sd-ldf.com/events-of-2017/industry-issues">first event</a> at this year’s <a href="http://www.sd-ldf.com/">Service Design Fringe Festival</a> in London, this weekend.</p><p>It’s fair to say we got off to a negative start…</p><p>But that was the plan (honest!)</p><p>Participants were asked to bring their woes with them so, collectively, we could take a service design approach — because, obviously — to tackling them…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ih9wkCoTk2RInAL4ABwZWQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AuX2lCTeM0xWP2-DTc9SzA.jpeg" /><figcaption>Katie Baggs, co-facilitator and service designer, leads the first session with a little inspiration from “Master collaborator” David Bowie.</figcaption></figure><p>The woes came in thick and fast. In summary, those little neon squares-of-woe pondered:</p><ul><li>How can we persuade people of the value of service design?</li><li>How do we measure and demonstrate what we do?</li><li>How can we justify the cost, time and resources?</li><li>How can we increase employment?</li><li>What makes service designers distinct from other roles, particularly in an agile organisation (ok, that one was mine).</li><li>How can we distinguish ourselves?</li></ul><p>All of which stem, in some way, back to one core issue:</p><p>The need for a clear and consistent definition of what service design is and what service designers actually do.</p><h3><strong>So, what is service design?</strong></h3><p>If we can’t explain what service design is and what service designers do how can we persuade anyone else of the value of it? And what hope is there of distinguishing ourselves?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gMoph1CPK_PxXaWX1sCUQw.jpeg" /><figcaption>Brainstorming ideas about what service design is</figcaption></figure><p>So, Sharpies at the ready, we scribbled down our thoughts on what service design is. And this is what we wrote:</p><ul><li>stakeholder management</li><li>facilitation and negotiation</li><li>identifying opportunities</li><li>problem solving</li><li>creating value for customers and businesses</li><li>managing interests</li><li>understanding user needs</li><li>producing stories, personas and journey maps</li></ul><p>Great! Service designers do everything! That clears it up :-/</p><p>But, wait a minute…</p><h3><strong>How is service design different from other disciplines?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6KHJLpi3V2kuXQA6cBIOiw.jpeg" /><figcaption>Are you a cat or a dog?</figcaption></figure><p>Disclaimer: I’m a product manager.</p><p>Before that I was a UX designer and before that I worked in a variety of digital communications roles.</p><p>I’ll be honest, one of the reasons I’m attending — and volunteering for — the Service Design Fringe Festival is to get a better understanding of the difference between a product manager and a service designer, so I can figure out where I want to take my career.</p><p>The ideas about what service design is, listed above, are all valid points but I couldn’t help but look at them and think, “yeah, me too”.</p><p>For instance, in my last interview I was asked to identify a poor user journey and make recommendations for how I’d improve it. To meet the challenge, I mapped out the as-is user journey to identify pain points and problems. I surveyed over 80 users to create personas and stories. Then I used all of this to identify opportunities to improve the experience and add value.</p><p>And I got the job… as a product manager.</p><p>So, what exactly makes service design different to other roles? To help move things along, and coming from the North where we like a good moan, I suggested the group identify:</p><h3>What service design is not…</h3><p>We often have stronger, more concrete ideas about what we don’t do or like. For instance, I‘m not a huge fan of beetroot but when it’s in a smoothie with a bunch of stuff I do like, I’ll happily tolerate it… And when it’s baked into a delicious <a href="http://www.jamieoliver.com/recipes/chocolate-recipes/epic-chocolate-and-beetroot-cake/">chocolate and beetroot</a> cake, I pity any poor soul that stands between us. But mushy peas? No. ABSOLUTELY NOT. Never, ever gonna happen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R-kqgcMxIyC0tpOV-MclsA.jpeg" /><figcaption>Mushy peas / peas turned into mush — why?</figcaption></figure><p>So, we repeated the exercise — mushy pea style — with the group listing all the things service design is not. And these things aren’t service design:</p><ul><li>marketing</li><li>brand strategy</li><li>change management</li></ul><p>This seems to suggest that service design is commonly mistaken for these three industries. With more time, I think it would have been useful for the group to dig a bit deeper into each of these — why do people think service design means marketing or change management? Is there overlap with these industries and what is it? Is the language we use to describe service design too similar to the language used by these other industries? Or is it simply that as humans we have a tendency to link what we don’t know to something we do know about, in order to help us understand it?</p><h3>What isn’t a service designer?</h3><p>Interestingly, most of the suggestions from the above exercise were about what a service designer is not — rather than the broader service design industry — and they all happen to be other roles…</p><ul><li><strong>Graphic/product/UI designer</strong> — some service designers may have a background in one of those disciplines and be visual thinkers but when, for example, was the last time you heard of a graphic designer designing a way to make it easier to live with dementia?</li><li><strong>HR consultant</strong> — employee experience is a part of service design but it’s not the job of a service designer to hire or fire people. The result of a service designer’s work may, however, lead to a change that makes it easier for an employee to carry out a set of tasks and therefore improve employee satisfaction.</li><li><strong>Service analyst</strong> — service designers look at <strong>all</strong> the ways a person comes into contact with a service whereas a service analyst may focus specifically on improving customer service or the operation of services.</li><li><strong>Domain expert</strong> — having some domain knowledge doesn’t hurt but unless you’re working in-house it’s unlikely you’ll be an expert in all the domains you encounter. Service designers look at a service from end-to-end and speak to as many people as possible that are involved along the way — this helps them understand the problems and opportunities facing the service rather than just the domain.</li><li><strong>Web developer</strong> — service designers might identify technology as an opportunity to improve a service but it is not their job to build it, just like a supermarket doesn’t grow, process and package every item it sells.</li><li>…and my favourite: a <strong>powerpoint designer </strong>— see below picture.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ci6-WuP5unA846QnsbBQHQ.jpeg" /><figcaption>Did someone just say service designers are powerpoint designers? Co-facilitator and curator Christopher French.</figcaption></figure><p>I’m going to take a wild guess that the participants in the room have had to explain, at one point or another, why what they do is different to one of the roles listed above. And I can empathise because I’ve lost count of how many times I’ve had to explain the difference between a project manager and a product manager (more on that below).</p><p>However, it also makes me wonder if the problem of defining what we do is not limited to just those working in new or digital careers. After all, if a <a href="https://www.wired.com/2017/02/robots-will-soon-taxes-bye-bye-accounting-jobs/">robot files our tax returns</a> how do we define the work of an accountant, let alone describe where they add value?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m3vlxneAo50hBQYOZbT_ug.jpeg" /></figure><p><strong>So, what makes a service designer different to a product manager?</strong></p><p>Product management is about the product. Good product managers champion their users — they understand their needs and who they are (including when they’re offline)—and they do this to identify and prioritise features that solve problems… <strong>Through their product</strong>.</p><p>Service designers look at the whole organisation, from customer and employee experiences to technology and operational functions, to identify opportunities to solve problems and add value. Product might be a part of that but it’s not the whole story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*-Q-gkRYNVmE6Aufq5ExHfA.jpeg" /></figure><p>As one participant put it:</p><blockquote>“Having a holistic view of everything that’s happening is one our greatest strengths!</blockquote><p>For example, a digital product that offers a quick and easy experience for booking or changing a hospital appointment won’t help the patient when they’re met by grumpy staff or a dirty ward. In this case, a service designer might look at why the staff are grumpy — is it because they‘re overworked? Are they overworked because they never receive a finalised list of patients in time to allocate the right amount of staff to a ward? Is the lack of staff the reason the ward is dirty? For more (and real) examples of service design check out <a href="https://www.designweek.co.uk/issues/12-18-january-2015/what-is-the-best-example-of-using-service-design-in-the-public-sector/">this Design Week article</a>.</p><p><strong>As for project management?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*741elI2bjSrxvQAuoKAsvw.jpeg" /></figure><p>Project management, generally speaking, is about completing a project on time and to budget. There is a start and end date for a defined piece of work. But both service design and product management are iterative. They don’t have a clear finishing line, they keep evolving as the needs of their stakeholders and the industries they operate in changes.</p><h3>In conclusion?</h3><p>Service design and the work of service designers is hard to define and this leaves room for assumptions and comparison with other industries and disciplines.</p><p>Listing all the tasks service design does or could include doesn’t make things clearer. Neither does explaining how a service designer is different to, for example, a project manager or UI designer — that’s useful for people doing those jobs but offers little insight for people who don’t really know what a project manager or UI designer do.</p><p>So, setting some boundaries and being able to offer a definition — even if it changes over time — can only help people better understand the service design industry.</p><p>Here’s an example definition you can use, taken from the Service Design Fringe Festival <a href="http://www.sd-ldf.com/what-is-service-design/">website</a>:</p><blockquote>Service design is a set of principles and methods used to create services. Service designers work directly with the users of a service, designing with them in a process which includes user research, idea generation, prototyping &amp; testing.</blockquote><p>If you don’t like it, there are plenty more definitions scattered across the internet including these <a href="https://blog.practicalservicedesign.com/what-is-a-service-experience-explained-through-drawings-e3f2bef8f6bc">excellent drawings!</a></p><p>But definitions only go so far.</p><p>Real examples of service design in practice is the best way to show how the industry adds value. One participant summed this up when they said:</p><blockquote>We must break down the silos in the service design industry — blogging, being open about what we’re working on, what we’re learning, running show &amp; tells... All of these things will help people to really ‘get’ what we do.</blockquote><p>For inspiration, take a look at how <a href="https://medium.com/newham-digital/newham-digital-3405fb2d9f1c">Newham Council are using Medium</a> to blog about what they’re up to.</p><p>But as technology continues to <a href="https://www.theguardian.com/society/2015/nov/29/five-ways-work-will-change-future-of-workplace-ai-cloud-retirement-remote">change the world of work</a> (← a couple of years old but still worth a read!) and the boundaries of many jobs become ever more fluid, it’s much harder to pin down a definition for the role of a service designer.</p><p>This is largely because the role of a service designer changes, depending on the evolving needs of an organisation and all the people who interact with it… This flexibility is part of a service designer’s value.</p><p>As one participant put it:</p><blockquote>“As <a href="https://twitter.com/hashtag/servicedesigners?src=hash">service designers</a> we are strategists but we go beyond just strategy. We’re also makers. We’re the umbrella across customer experience, user research, product and operations. ”</blockquote><p>The role of a service designer also depends on the service designer that is doing it. As the exercises highlighted in this article show, a service designer needs to have a multitude of skills but — like all good <a href="https://medium.com/@laurenholliday_/the-world-is-run-by-t-shaped-people-1bf60f642633">T-shaped people</a> — they will excel in some areas more than others.</p><p>So, knowing what you — as a service designer — are not and what you don’t do is perhaps more valuable than trying to define exactly what you do do.</p><p>The service design community should also learn from the mistakes of the product management community and avoid <a href="https://medium.com/@bfgmartin/product-managers-you-are-not-the-ceo-3441cb3914e4">grandiose definitions</a> of what they do — product managers are not CEOs and service designers aren’t saving the world (sorry!).</p><p>But one thing is clear — service designers are definitely not powerpoint designers.</p><p><em>The Service Design Fringe Festival runs from 16–24 September 2017 with </em><a href="http://www.sd-ldf.com/events-of-2017/"><em>over 30 events taking place</em></a><em> across London. Thanks to Katie Baggs, Service Designer at </em><a href="https://rainmaker.solutions/"><em>Rainmaker</em></a><em>, and Curator Chris French for facilitating the event described in this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e196612d0c84" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>