<?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 Tom Harrison on Medium]]></title>
        <description><![CDATA[Stories by Tom Harrison on Medium]]></description>
        <link>https://medium.com/@trinovantum?source=rss-6a1175754fc3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Tom Harrison on Medium</title>
            <link>https://medium.com/@trinovantum?source=rss-6a1175754fc3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:29:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@trinovantum/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[Buckinghamshire Council Website: weeknotes w/c 30/11/20]]></title>
            <link>https://medium.com/buckinghamshire-digital-service/buckinghamshire-council-website-weeknotes-w-c-30-11-20-f6be9d16b34d?source=rss-6a1175754fc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6be9d16b34d</guid>
            <category><![CDATA[localgov]]></category>
            <category><![CDATA[local-government]]></category>
            <category><![CDATA[buckinghamshire]]></category>
            <category><![CDATA[localgovdigital]]></category>
            <dc:creator><![CDATA[Tom Harrison]]></dc:creator>
            <pubDate>Sun, 06 Dec 2020 23:24:30 GMT</pubDate>
            <atom:updated>2020-12-06T23:24:30.406Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s been a lot of change at Bucks over the last few months. The main news:</p><ul><li>Our Product Owner, and Head of Digital, Ben Unsworth took up a new job in Essex.</li><li>Our Lead Designer, Boris Divjak, took up a new job in Australia.</li><li>We now have a new PO and Head of Digital, Pete Parfitt, moving across from a previous role in the council.</li><li>We now have a new Designer, Sarah Morice, who is also new to us at Unboxed.</li></ul><p>In amongst all this, weeknotes got lost in the shuffle a bit, but videos of our show and tells are all up on YouTube. The most recent ones being:</p><ul><li><a href="https://youtu.be/Uf7B0Rs2eSM">Sprint 21</a></li><li><a href="https://youtu.be/VcfjMP5vY0k">Sprint 22</a></li><li><a href="https://youtu.be/AJl0M8Q3heA">Sprint 23</a></li></ul><p>Over the autumn we made some decisions on how we were going to use agency time for the remainder of the budget. As a result of this we made a couple of changes to improve our focus, as the team felt we were getting spread a little too thin between all of the things we wanted to do. Over the last few months we have been working on:</p><p><strong>Improving our search results</strong></p><p>User satisfaction for search has been quite poor with pages not being returned that people would expect, and lots of search terms leading to no results at all. We’ve done quite a bit of work to improve this, with the biggest change being the implementation of elastic search and our tests are giving much more accurate search results. You can find out more about how this works <a href="https://youtu.be/AJl0M8Q3heA?t=891">in one of our show and tell videos</a>.</p><p><strong>Progressing our work around long form content</strong></p><p>Like most council sites we will be required to publish lots of policies, strategies etc. It’s hard to keep these accessible and very often they become pdf’s. We’ve been working with a couple of teams across the council to design page templates to better support this content. As part of this, we’re also developing new Word templates with the relevant styling implemented so that people creating long form content can get a better idea of how it will look once published. This should also make it a lot easier for site content editors to upload policies as it will have been written with the site format in mind.</p><p><strong>Updating content for the Family Information Service</strong></p><p>This deserves a blog of its own, but we are continuing our work to update and rewrite content for the Family Information Service. It hasn’t always been smooth sailing as we’ve had to build bridges with the service team who are understandably both passionate and protective about their existing content. Progress has been good however and we’ve created some additional page templates to take into account some specifics about their content. Next up — reduce content duplication elsewhere by linking towards the Family Information Service content.</p><p><strong>Prioritising remaining content for migration</strong></p><p>For the most part, content will be migrated from the old sites to the new in line with the wider service improvement work being done across the council. For some content it makes sense for it to be bumped up the priority order a bit, e.g. for specific user journeys within a service, like checking bin collection dates. We did some analysis of site stats and contact centre call volumes to feed into this and as a result will be prioritising. <a href="https://youtu.be/VcfjMP5vY0k?t=781">We spoke more about our methodology at one of our recent show and tells</a>.</p><p><strong>Schema.org tagging</strong></p><p>A final note is that we’re continuing with our work to implement schema.org tags across the site. Our most recent additions are organisation details and jobs tags, meaning that details of jobs from our recruitment site now appear in search results.</p><figure><img alt="A screenshot showing how job listings display on the Google search results page" src="https://cdn-images-1.medium.com/max/1024/0*qXLc8fjbazNfQYjA" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6be9d16b34d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/buckinghamshire-digital-service/buckinghamshire-council-website-weeknotes-w-c-30-11-20-f6be9d16b34d">Buckinghamshire Council Website: weeknotes w/c 30/11/20</a> was originally published in <a href="https://medium.com/buckinghamshire-digital-service">Buckinghamshire Digital Service</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BoPS: Sprint notes 6 and 7]]></title>
            <link>https://medium.com/ubxd/bops-sprint-notes-6-and-7-bceb7488ef4e?source=rss-6a1175754fc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/bceb7488ef4e</guid>
            <category><![CDATA[localgovdigital]]></category>
            <category><![CDATA[fixtheplumbing]]></category>
            <category><![CDATA[local-government]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[plantech]]></category>
            <dc:creator><![CDATA[Tom Harrison]]></dc:creator>
            <pubDate>Mon, 20 Jul 2020 17:59:49 GMT</pubDate>
            <atom:updated>2020-07-20T17:59:49.517Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>16/6/20 to 13/7/20</strong></p><p>Due to holidays and a few other things we missed a sprint note, so here’s combined notes for the last four weeks:</p><ul><li>Updated the landing page. Previously it showed all open applications by default. Based on user feedback it now only includes applications assigned to that user, or that are unassigned.</li><li>Built document management functionality. We’re trying to keep this as simple as possible for as long possible as it has the potential to get very complex and we really don’t want to end up building a document management system inside our development management system.</li><li>Started work on full householder applications, beginning with research around consultation, site visits and the conditions that are assigned to householder approvals.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/435/0*oTF3DATqP4gxfE_c" /><figcaption>Prototypes of site visit functionality</figcaption></figure><ul><li>Had BOPS penetration tested by our security partner. No serious vulnerabilities were found but it identified a few bits of housekeeping for us to complete.</li><li>Discussed the data we could get from Planning Portal if we were to integrate with it in future, and the data that the London Development Database (LDD) would like to be able to collect from BOPS which will help inform future API development.</li><li>Finished building out our Terraform infrastructure, which makes deploying changes and spinning up new environments much much quicker and has made our developers very happy.</li><li>Integrated with Gov.UK Notify.</li></ul><p><a href="https://docs.google.com/presentation/d/1DFgvcIFU1bA-Lx01jUDX8BHkMnljfAkr0vWww3XQNrA/edit#slide=id.g4f68b8219a_0_3">Show and Tell 6 slide deck</a></p><p><a href="https://www.youtube.com/watch?v=Df9y0w65AL0">Show and Tell 6 video</a></p><p><a href="https://docs.google.com/presentation/d/1AL64d1QLtuyVnsbFscSGEeUSsLueBDFzfNooEnZaWPo/edit#slide=id.g89c50a2a61_2_16">Show and Tell 7 slide deck</a></p><p><a href="https://www.youtube.com/watch?v=Yq6ZD9jbOS8">Show and Tell 7 video</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bceb7488ef4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ubxd/bops-sprint-notes-6-and-7-bceb7488ef4e">BoPS: Sprint notes 6 and 7</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: Sprint Note 5]]></title>
            <link>https://medium.com/ubxd/bops-sprint-note-5-cb660ca61eed?source=rss-6a1175754fc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb660ca61eed</guid>
            <category><![CDATA[fixtheplumbing]]></category>
            <category><![CDATA[plantech]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[localgovdigital]]></category>
            <category><![CDATA[local-government]]></category>
            <dc:creator><![CDATA[Tom Harrison]]></dc:creator>
            <pubDate>Wed, 17 Jun 2020 17:02:52 GMT</pubDate>
            <atom:updated>2020-06-17T17:02:52.524Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>2/6/20 to 15/6/20</strong></p><p>This sprint we:</p><ul><li>Created a basic API to make decisions data available to Planning Registers, the London Development Database or anything else that might need it. We need to add UPRNs, and we have a longer term aim to do some user research with potential users of planning data to find out what we need to expose through it.</li><li>To test the API we asked two developers who have recently joined us from Flatiron School, Anastasia and Melissa, to create a simple one page planning register to display the dummy data we’ve been working with, which looks pretty neat:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8CvMvVwHB3AO8e94" /><figcaption>Our dummy planning register with dummy data.</figcaption></figure><ul><li>Started laying the foundations for document management functionality in BoPS. This involved a couple of conversations with Open Systems Lab as we’ll be dependent on files and info coming through from their Reduce Invalid Planning Applications service. We can’t make any assumptions about how documents will be provided, sometimes all plans come in together in one document, others might submit them each separately. To work with this we’ll be taking an approach where documents are tagged with the document type(s) as required.</li><li>Discussed unique IDs and application numbers, which are currently generated by individual planning authorities. Typically this will follow a syntax set by the system they’re using, perhaps with some customisation so it makes a bit more sense internally. Theoretically, that means that there are multiple planning applications in different parts of the country with the same ID number which might be problematic if a national planning register is created. For now we’re going to include the local authority code of the planning authority, but the idea of a working group to decide a standard syntax for codes in BoPS was raised at our show and tell by Peter Forest at Buckinghamshire Council and is worth exploring.</li><li>Conducted user testing around how managers ask for corrections and officers upload documents. We tested with three officers and three managers from Southwark, Croydon, Coventry, Buckinghamshire and Luton councils.</li><li>Started looking at how we’ll scale BoPS to work with multiple councils. For MVP we’re not building a multi-tenanted application but once we start deploying multiple councils that will become problematic quite quickly. We’re now reviewing what aspects of the application we would want to be configurable in an admin panel, and looking at what we’d need to do behind the scenes to iterate the architecture.</li></ul><p><a href="https://docs.google.com/presentation/d/1n-qdZtEXo20ncunZas7mDSWgBrc4YrhBNcZxtizO5nI/edit?usp=sharing">Show and tell slide deck</a></p><p><a href="https://www.youtube.com/watch?v=IXCZQrUhL8o">Full show and tell video</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb660ca61eed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ubxd/bops-sprint-note-5-cb660ca61eed">BoPS: Sprint Note 5</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: Sprint note 4]]></title>
            <link>https://medium.com/ubxd/bops-sprint-note-4-ead3fea50172?source=rss-6a1175754fc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ead3fea50172</guid>
            <category><![CDATA[local-government]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[plantech]]></category>
            <category><![CDATA[fixtheplumbing]]></category>
            <category><![CDATA[localgovdigital]]></category>
            <dc:creator><![CDATA[Tom Harrison]]></dc:creator>
            <pubDate>Fri, 05 Jun 2020 16:32:23 GMT</pubDate>
            <atom:updated>2020-06-05T16:32:23.299Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>19/5/20 to 1/6/20</strong></p><p>This sprint we:</p><ul><li>Mapped the planning application data we would receive from <a href="https://ripa.digital/">RIPA</a> into BoPS. We’ve also started looking in more detail at what an API from RIPA would look like. Continued thanks to Alastair and the team at Open Systems Lab who have been great to collaborate with on this.</li><li>This mapping then fed into an iteration of the main assessment screen for officers that moves away from asking them multiple yes / no questions about applications. Answers to questions are now pulled from the application data provided by RIPA and displayed inline, with a single yes / no question at the bottom.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*W75r64nWN0fsAoLXfp8-Jw.png" /><figcaption>Image showing the old, multi-question prototype and the newer version with inline answers.</figcaption></figure><ul><li>As a note to the above, BoPS will work with other products than RIPA, e.g. Planning Portal, if they can provide data in the required format.</li><li>Tested the latest version of the Permitted Development prototype with officers at LB Southwark and LB Lambeth. This included the review of automatically generated decision notices and the flow used by planning managers to request amendments.</li><li>Started prototyping how document management might work. There’s a few unknowns around how plans will be sent through, how often they’ll be updated, the best way to categorise them etc. We’re not attempting to do anything complicated as there are already systems such as DigEPlan that can handle things like annotations, analysis, etc, but some basic functionality for receiving and updating documents is needed.</li><li>Delivered a lot of user stories for both officers and managers, which can best be explained by <a href="https://youtu.be/IRPA5tYqcpg?t=679">watching the demo from our show and tell</a>.</li><li>Sent out our systems and processes survey to councils.</li></ul><p><a href="https://docs.google.com/presentation/d/1EceaCxt4AdHrS_4PgjEQABodvqoXYoyyVuBfKzCeLMY/edit?usp=sharing">Show and tell slide deck</a></p><p><a href="https://www.youtube.com/watch?v=IRPA5tYqcpg">Full show and tell video</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ead3fea50172" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ubxd/bops-sprint-note-4-ead3fea50172">BoPS: Sprint note 4</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: Sprint note 3]]></title>
            <link>https://medium.com/ubxd/bops-sprint-note-3-202fb3e6f0f1?source=rss-6a1175754fc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/202fb3e6f0f1</guid>
            <category><![CDATA[localgovdigital]]></category>
            <category><![CDATA[localgov]]></category>
            <category><![CDATA[fixtheplumbing]]></category>
            <category><![CDATA[plantech]]></category>
            <dc:creator><![CDATA[Tom Harrison]]></dc:creator>
            <pubDate>Fri, 22 May 2020 16:08:10 GMT</pubDate>
            <atom:updated>2020-05-22T16:08:10.792Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>5/5/20 to 18/5/20</strong></p><p>This sprint we:</p><ul><li>Agreed what we’ll do after sprint 4. Our options at the beginning of the project were to either continue looking at Permitted Development or start work on full householder applications. After discussing with MHCLG we’ve decided to focus a bit further on Permitted Development with the aim of having an MVP that can integrate with <a href="https://www.ripa.digital/">Reduce Invalid Planning Applications</a> (RIPA). This will enable us to solve a whole problem around processing one type of application, whilst hopefully minimising the amount of integration required with legacy systems to encourage adoption.</li><li>Delivered the first pass of functionality for officers to assess applications and make recommendations, and for managers to make determinations.</li><li>Started working with a dummy API from RIPA, complete with canned responses. This will enable us to restrict the questions displayed to Planning Officers to only the ones relevant to that application.</li><li>Tested v4 of the Certificate of Lawfulness prototype with officers and managers at four councils. As a result we’ve been able to remove a step from the workflow by auto-generating the decision notice, based on the officer’s answer to policy questions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*9gvr2Fgw1OsrGP8J3ca6fA.png" /><figcaption>An image showing mapping from policy questions to decision notice</figcaption></figure><ul><li>We also learned that although managers need to understand how an officer made a decision they don’t necessarily need a full report, which gives us some more opportunities to streamline things.</li><li>Finally, we started looking at how managers would request amendments on applications.</li></ul><p><a href="https://docs.google.com/presentation/d/15hrcQZ3E6h4qGgi2AcSupvheluYQqcwbis0xSarEd34/edit?usp=sharing">Show and Tell slides are here</a></p><p><a href="https://www.youtube.com/watch?v=ID-taA2l_xY">Show and Tell video with Q&amp;A is here</a></p><p><strong>Prototype:</strong> <br><a href="https://beta-bops-design-prototype.herokuapp.com/">https://beta-bops-design-prototype.herokuapp.com</a></p><p>Username: unboxed <br>Password: magic</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=202fb3e6f0f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ubxd/bops-sprint-note-3-202fb3e6f0f1">BoPS: Sprint note 3</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: Sprint note 2]]></title>
            <link>https://medium.com/ubxd/bops-sprint-note-2-8afcbf008b44?source=rss-6a1175754fc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8afcbf008b44</guid>
            <dc:creator><![CDATA[Tom Harrison]]></dc:creator>
            <pubDate>Sun, 10 May 2020 21:59:36 GMT</pubDate>
            <atom:updated>2020-05-11T10:24:06.599Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>21/4/20 to 4/5/20</strong></p><p>This sprint we:</p><ul><li>Presented our ways of working at the Connected Places Catapult “PlanTech in the era of Covid-19” webinar. <a href="https://youtu.be/1XqjGpMcoWU?t=1970">The webinar is available here.</a></li><li>Iterated on our prototype. A big focus was the language used to describe steps in the process to match the language used by Planners on a day-to-day basis. We were also able to remove a process step. The link and password are at the foot of the page.</li><li>Continued testing with people at LB Lambeth, LB Croydon, LB Southwark, Surrey Heath Council and Buckinghamshire Council. We did some information sorting to understand the best way to present</li><li>Looked more closely at the relevance of information at different stages. As a result more of the generic information about applications is hidden behind accordions to reduce scrolling.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0JWSH_NV5nVMixCGByphsw.png" /></figure><ul><li>Saw some inconsistencies in process between different councils, for example whether they work to complete assessment by “fast track” dates or statutory dates. We need to create an application that is flexible enough to work for everyone, but whereas some details can be abstracted away others (like target dates) are a bit more difficult. We’ll be doing a broad survey of as many councils as possible to get an idea of what variances we might need to accommodate. If you’d like to be involved <a href="/service/mailto:tom.harrison@unboxed.co">please get in touch with us</a>.</li><li>Delivered two more features, the work list for officers and the overview screen officers first see when assessing applications.</li><li>Finished, for the time being, our work on the AWS infrastructure. We spent more time on this than we originally envisioned but now we’re confident we’ve got this right, we can ramp up on delivery of features.</li><li>Continued our investigation into what data we could expect to be coming into BoPS from application submission services, e.g. built using <a href="https://www.ripa.digital/">Open Systems Lab’s RIPA</a>. We also continued looking at requirements for exporting documents such as schematics into other systems, but this is potentially much simpler.</li></ul><p><a href="https://beta-bops-design-prototype.herokuapp.com/"><strong>Prototype is available here</strong><br></a>Username: unboxed <br>Password: magic</p><p><a href="https://docs.google.com/presentation/d/1u3Uv0Uvo56BfDFXHt0YIol66kFN3mORATCvHn8jH7UQ/edit?usp=sharing"><strong>Show and tell slide deck is available here</strong></a></p><p><a href="https://vimeo.com/415116040"><strong>Show and tell video is available here</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8afcbf008b44" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ubxd/bops-sprint-note-2-8afcbf008b44">BoPS: Sprint note 2</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: Sprint note 1]]></title>
            <link>https://medium.com/ubxd/bops-sprint-note-1-a33c9f2b6bab?source=rss-6a1175754fc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/a33c9f2b6bab</guid>
            <category><![CDATA[plantech]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[localgovdigital]]></category>
            <category><![CDATA[fixtheplumbing]]></category>
            <category><![CDATA[localgov]]></category>
            <dc:creator><![CDATA[Tom Harrison]]></dc:creator>
            <pubDate>Fri, 24 Apr 2020 17:39:29 GMT</pubDate>
            <atom:updated>2020-04-24T17:39:29.237Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>07/4/20 to 20/4/20</strong></p><p>This sprint we:</p><ul><li>Had our project kick-off. We typically do these over a one day alignment workshop, but having &gt;10 people on a video call for 7 hours sounded awful, so we broke it up into smaller sessions.</li><li>Defined our scope. Originally we were planning to look at full householder applications but we decided instead to first look at Permitted Development (PDs). The advantage of PDs is that the policy that underpins them is national, so theoretically this will be easier to design for multiple councils. Once we’ve got this working we can then make a decision to expand to looking at full householder applications, or continue to iterate on PDs.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-NsUfJwLGT-IGQdnH9kuHw.png" /></figure><ul><li>Iterated on the prototypes that we developed in alpha and tested them with Planning Officers at Coventry, Southwark and North West Leicestershire councils. <a href="https://drive.google.com/file/d/1r7DSCztAS5sPeHdabcmCWoEfcm_t3kae/view?usp=sharing">The playback from our designers to the rest of the team is available to view</a>. Things we learned include that Planners tend to identify applications by the first part of the address rather than their number, so that info needs to be on listing screens. We also got some good pointers on use of language for different tabs and how certain words might be interpreted.</li><li>Created our infrastructure on AWS. Our product will need to scale across potentially hundred of councils so we decided AWS would be more suitable than Heroku, which we’ve used a lot previously. AWS does take a bit longer to set up than Heroku does and there was a bit of discussion as to whether we should deploy there initially and then migrate to AWS later. It’s an interesting question, on the one hand going with Heroku first enables us to deliver value faster. On the other hand it would mean that we leave a very risky assumption around getting AWS set up towards the end of the project.</li><li>Shipped our first bit of working code! We now have a login screen with different tiers of access for Planning Officers, Planning Managers and Admins. AWS set-up took a bit longer than we thought so we didn’t get as much built as we hoped, but it’s a good start (and proves the value of testing riskiest assumptions first).</li><li>Had some conversations with Open Systems Lab and DigEplan, who are also working on systems around planning. Open Systems Lab are working on Reducing Invalid Planning Applications (RIPA), who’s alpha was recently concluded. BoPS of course needs to get application data in from <em>somewhere</em>, so we’ve been discussing what an API between an application system and a management system might look like.</li><li>DigEplan have a toolset that allows planners to easily compare plans and annotate them so that applicants can understand what needs to change. Integrating this with existing products has been quite challenging, so in a similar vein we’ve begun discussions with them around what an API that provided access to planning documents might look like.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a33c9f2b6bab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ubxd/bops-sprint-note-1-a33c9f2b6bab">BoPS: Sprint note 1</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[Buckinghamshire Council Website: Weeknote #19]]></title>
            <link>https://medium.com/buckinghamshire-digital-service/buckinghamshire-council-website-weeknote-19-436a6c4063f1?source=rss-6a1175754fc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/436a6c4063f1</guid>
            <category><![CDATA[local-government]]></category>
            <category><![CDATA[buckinghamshire]]></category>
            <category><![CDATA[fixtheplumbing]]></category>
            <category><![CDATA[localgovdigital]]></category>
            <dc:creator><![CDATA[Tom Harrison]]></dc:creator>
            <pubDate>Fri, 06 Mar 2020 17:31:10 GMT</pubDate>
            <atom:updated>2020-03-06T17:31:10.310Z</atom:updated>
            <content:encoded><![CDATA[<p>w/c 2nd March</p><p>This week we:</p><ul><li>Had our ninth(!) show and tell. <a href="https://docs.google.com/presentation/d/18bmJe__w6oj6dQ5MaloV4b8QpOZ9kNZW4d8ewT0L35s/edit?usp=sharing">Slides are available to view</a>, the video will be up shortly as soon as I’ve uploaded it from my phone (Ben and Boris were both at Service Design in Government this week and we didn’t have our normal camera so we had to get creative).</li><li>Started work on designing the forms for complaints. We’re still investigating the feasibility of different approaches so have two prototypes, a <a href="https://marvelapp.com/54bde29/screen/66843849">multi-step</a> approach enabling <a href="https://www.gov.uk/service-manual/design/form-structure#start-with-one-thing-per-page">one thing per page</a>, and a fall back option of a <a href="https://marvelapp.com/4cj55fi/screen/66843707">single page</a> for day one if this proves too fiddly to create in the time we have available.</li><li>Gave our Libraries content to the service for final sign-off before publication. The end-to-end process of updating this content has taken longer than we hoped but underlines the <strong>importance of integrating content design, user journeys and development.</strong> It’s definitely harder to do, but the results are a lot better than trying to tackle those things sequentially.</li><li>Finished up the majority of the back end work for our “find and apply for a job” service. We’ve now got search alerts working, so just need to add the ability to download files associated with a job. We’re a bit behind on our front end work but should be powering through that in the next sprint to get everything live before vesting day.</li><li>Started looking at the mammoth find and replace task we have removing references to the existing county and district councils on legacy sites. For example over a thousand on the county council site and over 700 on the Wycombe DC site.</li><li>Started going through the final list of about 200 links we’ll need to have back to content on the existing county council site until we’ve finished migrating content.</li><li>Continued adding to our design guidelines, <a href="https://zeroheight.com/5ef2b1a81/p/25b1f1-buckinghamshire-council-digital-design-guidelines">viewable at Zero Height</a>, latest additions include buttons, tables and progressive disclosure options. The latter will be very important when publishing</li></ul><p><strong>What we’re thinking about</strong></p><p>How we can make the site easily accessible for other project teams. Not all of the new digital services for Buckinghamshire Council will be delivered by this project team, <a href="https://medium.com/buckinghamshire-digital-service/building-a-better-digital-family-information-service-sprintnotes-01-1e1e292b41f4">for example the new Family Information Service site</a>. We need to work out how we can best support those teams in:</p><ul><li>deciding which bits of their service can be best implemented via the main site CMS</li><li>making the handover to the other site as seamless as possible</li></ul><p><strong>Next week</strong></p><ul><li>Planning for our penultimate sprint before vesting day</li><li>Publishing Libraries content</li><li>Penetration testing</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=436a6c4063f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/buckinghamshire-digital-service/buckinghamshire-council-website-weeknote-19-436a6c4063f1">Buckinghamshire Council Website: Weeknote #19</a> was originally published in <a href="https://medium.com/buckinghamshire-digital-service">Buckinghamshire Digital Service</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Buckinghamshire Council Website: Weeknote #18]]></title>
            <link>https://medium.com/buckinghamshire-digital-service/buckinghamshire-council-website-weeknote-18-f42e976577d7?source=rss-6a1175754fc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f42e976577d7</guid>
            <category><![CDATA[content-design]]></category>
            <category><![CDATA[localgov]]></category>
            <category><![CDATA[localgovdigital]]></category>
            <category><![CDATA[buckinghamshire]]></category>
            <dc:creator><![CDATA[Tom Harrison]]></dc:creator>
            <pubDate>Fri, 28 Feb 2020 17:20:35 GMT</pubDate>
            <atom:updated>2020-02-28T17:20:35.582Z</atom:updated>
            <content:encoded><![CDATA[<p>w/c 24th February</p><p>This week we:</p><ul><li>Had sprint planning. We have 2.5 sprints left until vesting day and are zooming in on the final must haves and working out how much more development we can squeeze in, which will impact on how we present some content.</li><li>Started looking at creating forms for complaints, FOIs and SARs and how they will integrate with the councils new management system, Respond.</li><li>Made some further tweaks to our libraries content, which we’ll hopefully be releasing next sprint.</li><li>Looked at the migration of content from staging to production. We didn’t think this would be an issue originally, but in doing the Libraries work we’ve found it quite useful to prototype and iterate content and user journeys in the staging environment. Currently we’d have to manually copy this to production which is a bit of a faff and increases the likelihood of someone making a mistake along the way. Fortunately, Wagtail has a new migration feature that we can use for this.</li><li>Did some content co-design for “find and apply for a job” with the recruitment team. As ever, they were really engaged and open to new ways of doing things (<a href="https://medium.com/buckinghamshire-digital-service/find-and-apply-for-a-job-a-design-sprint-665508536cc1">they previously did a design sprint with us</a>).</li><li>Dug into the filtering behaviour of “find and apply for a job”. Typically on a job site the first view you get is unfiltered, and you then apply progressively more filters to narrow it down. For us however the majority of the jobs we list are teaching jobs that most visitors aren’t qualified for, so that pattern doesn’t work as well. If a job seeker wanted to quickly skim all jobs across all areas on our site they would need to tick all but one filter boxes. As an alternative we’re experimenting with flipping this around, so that filters for all jobs are ticked by default and visitors un-tick areas they’re not interested in.</li></ul><p><strong>What we’re thinking about</strong></p><p>What things look like after vesting day. To meet the deadline we’re doing a few things in ways that are quick and easy, but incur a bit of technical debt. We’re going to spend a few sprints in April and May resolving these, then pause development of further platform features to concentrate on content migration through the spring. In the summer we’ll then start looking at bigger pieces of work we could do to best support the council’s wider improvement agenda.</p><p><strong>Next week</strong></p><ul><li>Show and tell</li><li>Address lookup, so people can check which area of the council they’re in (this will impact on delivery of some services until they’ve been brought into alignment)</li><li>Arranging user testing for people with specific access needs — for example someone who navigates the website without a mouse or with a screenreader</li><li>Hopefully publishing Libraries content</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f42e976577d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/buckinghamshire-digital-service/buckinghamshire-council-website-weeknote-18-f42e976577d7">Buckinghamshire Council Website: Weeknote #18</a> was originally published in <a href="https://medium.com/buckinghamshire-digital-service">Buckinghamshire Digital Service</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Buckinghamshire Council Website: Weeknote #17]]></title>
            <link>https://medium.com/buckinghamshire-digital-service/buckinghamshire-council-website-weeknote-17-68ac0f820352?source=rss-6a1175754fc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/68ac0f820352</guid>
            <category><![CDATA[buckinghamshire]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[localgov]]></category>
            <category><![CDATA[fixtheplumbing]]></category>
            <category><![CDATA[localgovdigital]]></category>
            <dc:creator><![CDATA[Tom Harrison]]></dc:creator>
            <pubDate>Fri, 21 Feb 2020 13:09:22 GMT</pubDate>
            <atom:updated>2020-02-21T13:09:22.091Z</atom:updated>
            <content:encoded><![CDATA[<p>w/c 17th February</p><p><strong>This week we:</strong></p><ul><li>Had our eighth show and tell. The <a href="https://docs.google.com/presentation/d/11By6NEydtWVv0cjKXOae6ppMvBHMaZ6k-rnl8wz0rnM/edit#slide=id.g6e9e89568a_0_41">slides are available online</a> and the <a href="https://www.youtube.com/watch?v=crXm_Acg7VE&amp;feature=youtu.be">video is also up</a>. Libraries are the first service whose content is being migrated in full during the project and the service manager, Zoe, joined us to talk about her experience working with the team. The key messages were to keep an open mind and remember that users see services differently to those that work within it, which is a great sentiment to convey to future service areas we work with. Thanks Zoe!</li></ul><figure><img alt="An image showing a summary update from the show and tell deck." src="https://cdn-images-1.medium.com/max/1024/1*BJkKUIfCKf_X9xjNQMLUpw.png" /><figcaption>Update from our show and tell deck.</figcaption></figure><ul><li>Did some user testing on our new Libraries content and structure, including a card sorting exercise to polish the navigation structure. We also ran some tests on <a href="https://maze.design/">Maze</a> asking them to complete certain actions such as finding and reserving books. We found that some of the language used needs tweaking, for example “borrowing” didn’t feel right when accessing a digital copy of a magazine, and that we shouldn’t refer to a digital assets as an “online reference resource”.</li><li>Implemented search functionality on our “find and apply for a job” service. Job seekers can now search the free text of the job title or job description, or use filtering options. When using filtering options they can set up an email job alert. We also worked on job categories and have implemented functionality allowing the recruitment teams to collate multiple job types into a “supergroup”, e.g listing all adult social care and children’s social care jobs under “social care”.</li><li>Continued our work with various suppliers on rebranding legacy sites. We also have some internal systems with public facing elements, such as Firmstep, that we need to update ourselves.</li><li>Made some additions to the design system, working on tables, buttons and form elements.</li></ul><p><strong>Next week:</strong></p><ul><li>Sprint planning, 2.5 sprints left…</li><li>More testing of “find and apply for a job”</li><li>Address / postcode look-up</li><li>Making policy documents accessible</li></ul><p><strong>What we’re thinking about</strong></p><p>Analytics and privacy. The use of citizen’s personal data by local government has been in the news recently. In short, Google provides incredibly powerful analytics tools to website owners for free, but these can (of not managed very carefully) then contribute to the tracking of people’s web usage by advertisers. It’s unclear whether local government needs the granularity of insight offered by Google Analytics, and it typically doesn’t have the skills required to make maximum use of the data collected. As a consequence sites are hoovering up a lot of data for little purpose. This is somewhat counter to a ‘privacy by design’ approach.</p><p>To avoid falling into this trap, we’re piloting <a href="https://usefathom.com/">Fathom</a> for use on the new site. Fathom is a privacy centered analytics platform, which means that it doesn’t collect personal data about users or require cookies to run. The consequence is the data collected is not as rich as we would get from Google. The question for our pilot then is whether the data from Fathom is <em>rich enough</em> for us to optimise our site to the required quality for users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68ac0f820352" width="1" height="1" alt=""><hr><p><a href="https://medium.com/buckinghamshire-digital-service/buckinghamshire-council-website-weeknote-17-68ac0f820352">Buckinghamshire Council Website: Weeknote #17</a> was originally published in <a href="https://medium.com/buckinghamshire-digital-service">Buckinghamshire Digital Service</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>