├── README.md ├── _config.yml ├── accessibility-acceptance-criteria.md ├── assets ├── css │ └── style.scss ├── project-summary-cards.pdf └── questions_and_suggestions.docx ├── case-studies.md ├── community.md ├── design-crits.md ├── design.md ├── package-lock.json ├── service-teams.md ├── specialist-publisher.md ├── standards.md └── tools-and-resources.md /README.md: -------------------------------------------------------------------------------- 1 | 12 | 13 | 18 | 19 | # Interaction design at Defra 20 | 21 | Interaction designers are essential parts of service teams that work to meet user needs, design standards and accessibility legislation. They also make sure all work is aligned to the service vision and that it adds value for users. They work closely with the entire project team, especially user researchers, service designers, content designers and software developers. 22 | 23 | Interaction designers lead teams to design accessible public and staff-facing digital products that are simple enough for everyone to use and that work across multiple channels, devices, browsers and platforms. When solving complex problems, the role of interaction design is to see the bigger picture as well as the fine detail, how things currently work and how they could work. They know how to remove complexity from services and are able to explain ideas in a way that other people understand. They will measure recently released product features to establish benchmarks and to identify potential areas of improvement. One of the key responsibilities of interaction design is to lead on the direction of new interaction patterns, standards and consistency in how products are designed. Interaction design's core aim is to help government transform the way it delivers services so that they're more efficient, simpler, faster and easier to use. 24 | 25 | ### What is interaction design? 26 | 27 | A design practice that works out the best way to let users interact with a product or sub-service. This is done to make sure we create inclusive and accessible products that can be used by all people. 28 | 29 | ### Why do it? 30 | 31 | Interaction design removes the risk of developing systems that don't meet user needs by: 32 | 33 | * testing assumptions, hypothesis, and designs early and often 34 | * ensuring the product is inclusive and accessible 35 | 36 | Interaction design along with other disciplines helps us create products that: 37 | 38 | * meet the [Government service standard](https://www.gov.uk/service-manual/service-standard) 39 | * meet Government accessibility regulations 40 | * meet current web standards 41 | * meet user and organisational needs 42 | * are simple and intuitive to use 43 | * work in a way that is familiar 44 | * require the minimum possible steps to complete 45 | * are consistent throughout 46 | * are usable by everyone, equally 47 | 48 | ### When to do it 49 | 50 | Interaction design is applicable throughout the agile delivery phases: Discovery, Alpha, Beta and Live (as defined by GDS). In addition, Interaction designers work on upgrading legacy applications and rolling out changes to ensure Defra’s web estate is consistent and meets current standards and regulations. 51 | 52 | ### Benefits 53 | 54 | Interaction design supports digital delivery to ensure benefits can be realised: 55 | 56 | * reduces risk, development and maintenance costs by testing assumptions and hypothesis 57 | * improves outcomes by facilitating design sessions to ensure a wide range of possibilities are considered 58 | * improves performance and reduces the number of user errors 59 | * increases user satisfaction and trust in both the service and Defra 60 | * improves efficiency through consistency and familiarity 61 | 62 | ## Service design in Defra 63 | 64 | Service designers work across a programme of work to design the interactions and building blocks that ensure a new or existing service works. They may also support multiple product teams to provide insight on how to achieve desired outcomes in a measurable way. 65 | 66 | Service designers work closely with all members of a multi-functional team to measure good services and good service design. They will work closely with user researchers, interaction designers, content designers, business analysts and product and service owners to identify and facilitate a shared understanding of the problem that needs to be solved. This might involve doing user research, understanding the current system and articulating the vision and then synthesising the learnings from that research and distilling and describing the problem in a concise way. 67 | 68 | The key principles of being a service designer are: 69 | 70 | * identify what the real problem is 71 | * map and visualise the journey of users 72 | * facilitate a shared understanding within and outside of the team 73 | * spot opportunities for reducing cost and complexity 74 | * help define the scope of the service 75 | * explore and prototype various solutions to the problem 76 | * design the service end to end, from backstage to front, in all channels 77 | 78 | ## What is service design? 79 | 80 | To help us understand what we mean by service design and end-to-end services in government, Scott Colfer’s [Product Management Handbook](http://scottcolfer.com/product-management-handbook/) highlights three principles from two key blog posts by Louise Downe [Good Services are Verbs](https://designnotes.blog.gov.uk/2015/06/22/good-services-are-verbs-2/) and Kate Tarling [A Common Language to Describe Services](https://hodigital.blog.gov.uk/2016/12/21/creating-a-common-language-to-describe-services/). 81 | 82 | ### A service helps a user to do something that needs to be done 83 | 84 | The way a user approaches getting something done isn't always the same as how government would like a user to interact with it. Government doesn't necessarily operate in 'services' but more through a series of transactions – ie 'Statutory Off Road Vehicle Notification (SORN)' or 'Tax your vehicle'. Users mostly think in services: "I want to learn to drive", "I need to renew my passport", "I want to become a childminder", "I need legal aid". 85 | 86 | ## A service name starts with a verb 87 | 88 | When we design something we want it to be of maximum value to the end user, and we want to be judged by this delivery of value, not by the costs of a project or the way it was delivered. Services like "learning to drive" or "needing legal aid" focus the attention on the value to the user. When something begins with a noun such as 'Statutory Off Road Vehicle Notification (SORN)' or 'Tax your vehicle' then the focus is on the transaction. It describes the thing the government wants you to transact and the value isn't necessarily focused on the user. 89 | 90 | ## Use the term 'service' accurately and sparingly 91 | 92 | A service helps a user to do something that needs to be done. It also helps government achieve policy intent on behalf of its citizens with whom it has a social contract. Services are verbs, eg "Visit the UK", rather than nouns, eg 'Biometric Residence Permit'. 93 | 94 | By taking these principles we ensure that we understand exactly what are 'services' and then the elements that make up a 'service', commonly referred to as the 'features', 'capabilities', 'activities' and 'technologies'. 95 | 96 | ### Examples of services: 97 | 98 | * visit the UK 99 | * learn to drive 100 | * i want to become a childminder 101 | * i need to renew a passport 102 | * i need legal aid 103 | 104 | ### Examples of features (one step or transaction in a service): 105 | 106 | * applying for a visa 107 | * applying for a licence 108 | * granting or refusing permission 109 | 110 | ### Example of capability - appointment booking, which requires: 111 | 112 | * an appointment booking system, which may be a technical capability 113 | * physical locations or phone support to host the appointments 114 | * a process for changing or cancelling appointments 115 | 116 | ### Examples of activities: 117 | 118 | * finding out how something works 119 | * calling people for help 120 | * applying for something 121 | 122 | ### Technology: 123 | 124 | ‘Technology’ means the digital systems, products, tools, hardware and applications we build, maintain and buy. Technology exists to support activities and capabilities – and enables us to deliver faster, clearer, simpler services. 125 | 126 | ### Example 127 | 128 | “For example, judged from a pure interaction design practice point-of-view, Uber is clearly an exemplary user experience. Yet judged from a wider urban design point-of-view, its impact appears to be hugely damaging, with vast numbers of vehicles incentivised to drive into the middle of cities, apparently leading to increased congestion and reduced public transport use. Seeing like a system, it looks like a product designed to get drivers onto the road, at the expense of more sustainable options. Needless to say, this is literally the opposite of what most city governments are trying to achieve at this point. In effect, Uber works for the individual – a car is always within range – precisely because it does not work for the city, as the streets are deliberately congested with drivers.” 129 | 130 | From [The City is My Homescreen](https://medium.com/dark-matter-and-trojan-horses/the-city-is-my-homescreen-317673e0f57a) 131 | 132 | ### Why do it? 133 | 134 | By working across organisational boundaries, Service Design helps users complete their goals by solving problems that sit outside the normal remit of Interaction and Content Design. 135 | 136 | ### Service design 137 | 138 | * builds context and understanding of end users lives 139 | * brings visibility to customer journeys and the pain points that limit service use 140 | * highlights organisational/ structural issues that prevent good service outcomes 141 | 142 | ### Service design along with other disciplines will help us create services that: 143 | 144 | * are easy to find 145 | * clearly explain the purpose of the service 146 | * set expectations a user has of the service 147 | * enable each user to complete the outcome they set out to do 148 | * work in a way that is familiar 149 | * require no prior knowledge to use 150 | * are agnostic of organisational structures 151 | * require the minimum possible steps to complete 152 | * are consistent throughout 153 | * have no dead ends 154 | * are usable by everyone, equally 155 | * encourage the right behaviours from users and service providers 156 | * respond to change quickly 157 | * clearly explain why a decision has been made 158 | * make it easy to get human assistance 159 | 160 | ### When to do it 161 | 162 | Service Design is applicable throughout the agile delivery phases Discovery, Alpha, Beta and Live (as defined by GDS). In addition it is valuable to use Service design approaches in pre-discovery in order to diagnose and scope out the problems that need to be addressed. Often requests are made to build defined things i.e. an app, a page, a service which presuppose a solution, working pre discovery allows stakeholders to avoid this issue with good problem definition. 163 | 164 | ### Benefits 165 | 166 | Service design supports digital design to ensure benefits can be realised 167 | 168 | * reduces risk by ensuring the right problem is solved 169 | * creates efficiencies by identifying service siloes, duplication and proliferation 170 | * ensures user and stakeholder outcomes are designed into the service 171 | -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | remote_theme: defra-design/govuk-jekyll-theme 2 | -------------------------------------------------------------------------------- /accessibility-acceptance-criteria.md: -------------------------------------------------------------------------------- 1 | 11 | 12 | # Accessibility acceptance criteria 13 | 14 | Ensuring a service is accessible is often something that a team decides to do either prior to a service assessment or when it deems the service is ready for release. A better way to do it is to make it part of the acceptance criteria for every sprint. This not only ensures that the team doesn’t get any nasty surprises but is a way for a team to work effectively together by ensuring the acceptance criteria by which they deliver code is aligned with accessibility requirements. 15 | 16 | Using the latest version of the GOV.UK Design System ensures a lot of things are baked in, but sometimes there are different patterns and components especially with internal and case management system. 17 | 18 | ### General 19 | 20 | * Actionable with keyboard or touch or mouse or voice 21 | * Check using assistive technologies. Tested with at least one screen reader 22 | * Zoom page to 200%, then 400% - is content still legible? Test on all major browsers 23 | * Try without css – does content make sense and appear in a logical order? 24 | * Test without javascript – does content make sense and appear in a logical order? 25 | * View on variety of screen sizes 26 | * Used with high contrast mode 27 | * Invert colours (eg white on black) 28 | * Test with voice dictation (eg Voiceover on Mac) 29 | * Appearance changes on interaction 30 | * Links should look like links 31 | * Suitable vertical spacing between lines and paragraphs 32 | * Avoid italics, block capitals or justified text 33 | * Text can be resized 34 | * Check html mark-up is valid 35 | * Check in a range of browsers and devices 36 | 37 | ### Specific 38 | 39 | * Check that headings and lists are used correctly 40 | * Use the https://accessibility-bookmarklets.org/install.html to verify that all content is in a landmark and that the correct landmarks are used in the correct places. 41 | * Use bookmarklet to ensure text spacing meets WCAG 1.4.12 42 | * Colour contrast testing. Perhaps not a full test, but focusing on colour combinations that look suspect. This needs to include hover and focus states and needs to be done on all various responsive layouts (a colour contrast of at least 4.5:1 between text and the background) 43 | * Where there is a service that includes images, test the service without images being displayed. This is not a WCAG requirement, but it is a GDS requirement. Many techniques that provide alternate text for assistive technologies (such as aria-label attributes and hidden text) do not provide visible text for sighted users when images are not displayed 44 | * For each page built or updated as part of the sprint, use the HTML validator at https://validator.w3.org/nu/ and use https://dotjay.github.io/wcag-parsing-filter/bookmarklet/ to filter the results so that only WCAG non-compliances are shown 45 | * No timeout unless as a security precaution 46 | * Download links labels include file format and size 47 | * Only use tables to present data 48 | * Don’t communicate using colour alone 49 | * All form inputs have labels 50 | 51 | ### Content 52 | 53 | * Using plain English 54 | * Explain unusual words and jargon 55 | * Most important information at the start 56 | * Logically structured, using sub-heads, bullets and short sentences 57 | * Consistent use of formatting (eg H1/H2 etc) 58 | * Each page has unique, descriptive h1 and page title 59 | * Content written in a task focused way 60 | * Default text size that is comfortable to read 61 | * Headings, links and button text must be unique and descriptive 62 | * Alt tags, captions and image descriptions for images 63 | * Link text that is descriptive (eg: Read our [Privacy Policy]) 64 | * (Where relevant) transcripts for any audio and/or video content 65 | * If there are documents as attachments ensure they are accessible (eg PDFs to be accessible – https://www.gov.uk/guidance/how-to-publish-on-gov-uk/accessible-pdfs) 66 | * Where relevant, think about provision of alternative formats (eg easy read format) 67 | * Error messages suggest ways to fix error 68 | * Error messages should show a summary of errors above the h1 and move focus to it 69 | * Error message summary should include an h1 message that tells the screen reader user there is a problem, and gives a list of descriptive errors with links to the relevant fields 70 | 71 | ### Reference and furhter reading 72 | 73 | * Unsorted collection of accessibility acceptance criteria https://alphagov.github.io/a11y-dev-workshop/criteria 74 | * ARIA documentation: https://w3c.github.io/using-aria/#ariachecklist 75 | * Paciello Group: https://developer.paciellogroup.com/blog/2014/09/web-components-punch-list/ 76 | * Improving accessibility with accessibility acceptance criteria https://insidegovuk.blog.gov.uk/2018/01/24/improving-accessibility-with-accessibility-acceptance-criteria/ 77 | -------------------------------------------------------------------------------- /assets/css/style.scss: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /assets/project-summary-cards.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/defra-design/design/c36ae456ea9ac99f041c1397cf63e6c0edc1e355/assets/project-summary-cards.pdf -------------------------------------------------------------------------------- /assets/questions_and_suggestions.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/defra-design/design/c36ae456ea9ac99f041c1397cf63e6c0edc1e355/assets/questions_and_suggestions.docx -------------------------------------------------------------------------------- /case-studies.md: -------------------------------------------------------------------------------- 1 | 11 | 12 | # Case studies and examples 13 | 14 | Below we have started collecting relevant case studies of the work we do 15 | 16 | ## Design history 17 | 18 | * [A directory of design histories](https://x-govuk.github.io/govuk-design-history/directory/) 19 | * [Design history template](https://x-govuk.github.io/govuk-design-history/) 20 | * [Design history example - Submit social housing lettings and sales data (CORE)](https://core-design-history.herokuapp.com/) 21 | * [Design history example - Becoming a teacher](https://bat-design-history.netlify.app/) 22 | -------------------------------------------------------------------------------- /community.md: -------------------------------------------------------------------------------- 1 | 2 | 12 | 13 | # Defra Design community 14 | 15 | We are a team of interaction designers and service designers working from across the UK on projects, services and programmes here at Defra. We are based around Bristol, York, Warrington, Newcastle and London. 16 | 17 | ## Community of practice (CoP) 18 | 19 | * Defra - Design community of practice, first three Wednesdays of every month - [Agenda](https://trello.com/b/sdPUAgzZ/defra-design-team-meetings) 20 | * Defra - UCD Show & Tell [Agenda](https://defra.sharepoint.com/:x:/r/teams/Team1340/UCDLeadershipTemp/UCD%20Monthly%20Show%20and%20Tell%20Line%20up.xlsx?d=wfeb651a1cd7645cfbfc900008ff12c68&csf=1&web=1&e=sZk6GO) 21 | * Defra - User centered design meet-up, quarterly 22 | 23 | ### Slack 24 | 25 | Sign up to Slack using '_defra' at the end of your name. 26 | 27 | * [Defra digital Slack Workspace](https://defra-digital.slack.com/?redir=%2Fmessages%2Fdesign%2F) 28 | * [Cross Gov digital Slack Workspace](https://ukgovernmentdigital.slack.com) 29 | 30 | #### Recommended channels 31 | 32 | * Defra - design 33 | * Defra - ucd 34 | * Defra - user research 35 | * Defra - accessibility 36 | * Defra - flood-ucd (Warrington) 37 | * Defra - bristol_ucd (Bristol) 38 | * Gov - design 39 | * Gov - prototype-kit 40 | * Gov - govuk-design-system 41 | * Gov - accessibility 42 | * Gov - user-research 43 | 44 | ### Mailing lists 45 | 46 | * [Digital designers mailing list](https://groups.google.com/a/digital.cabinet-office.gov.uk/forum/?hl=en-GB#!forum/digital-service-designers) 47 | 48 | ### Useful Blogs 49 | 50 | * [https://defradigital.blog.gov.uk/](https://defradigital.blog.gov.uk/) 51 | * [https://gds.blog.gov.uk/](https://gds.blog.gov.uk/) 52 | * [https://accessibility.blog.gov.uk/](https://accessibility.blog.gov.uk/) 53 | -------------------------------------------------------------------------------- /design-crits.md: -------------------------------------------------------------------------------- 1 | 2 | 12 | 13 | 14 | # Design crits 15 | 16 | A design crit is a critique, or detailed analysis of something (not a criticism) in order to improve its design. Design crits can be done at any stage in the design process and help improve our services. 17 | 18 | We have a [#design-crits](https://defra-digital.slack.com/archives/C01REPJH9V5) slack channel that allows you to submit your work for immediate feedback. 19 | 20 | We also offer design crits to anyone who is interested in having them. You can request a design crit session via [our request form](https://forms.gle/nQrFQYzd5sdLjuBK6). 21 | 22 | 23 | ## Why we do design crits 24 | 25 | Design crits are about: 26 | 27 | * lifting the standard and consistency of design practice across Defra 28 | * creating a sense of collective responsibility for everything that goes out the door in our name 29 | * developing our critical skills as designers: evaluating work and lending a helping hand to our colleagues to improve it 30 | * thinking hard beyond design patterns, about user needs and coherent end-to-end service experiences 31 | * sharing what we learn with the design team and government more widely 32 | 33 | 34 | ## Proposed ground rules for running a design crit 35 | 36 | Design crits can be, when badly run, bruising affairs so we propose to follow six important ground rules to make sure it’s all about the work and not the individual. These are proposals and nothing here is fixed in stone - we’ll continue to experiment and find what works best for us as a design team. 37 | 38 | 1. **Crits are always moderated** 39 | 40 | 2. **Everything is about the work, never about the individual.** A good critique should be honest and to the point, but never personal. 41 | 42 | As Sarah Richards puts it, we start from the assumption that: *“everyone did the best job they could with the information they had at the time”* 43 | 44 | 3. **It’s a conversation and not a court.** Crits are a place to start conversations, not to aggressively challenge or criticise people for ‘doing it wrong’. 45 | 46 | 4. **Be in listening, not defensive mode.** As a designer sharing work, show the work as it is, don’t pre-emptively interpret/explain/defend on its behalf. 47 | 48 | 5. **Take notes, lots of them.** Someone must take responsibility for capturing the conversation and sharing it. 49 | 50 | 6. **We don’t have to agree.** Others might say/suggest things that the designer doesn’t agree with or cannot action, but they do have a responsibility to manage expectations and be clear about what they intend to do in response (see 5). 51 | 52 | 53 | ## Tips for getting and giving feedback 54 | 55 | 56 | ### Getting feedback 57 | 58 | 59 | #### 1. Set the context 60 | 61 | * who are the users? 62 | * what do they need? 63 | * what stage is the project at? 64 | * what are our current assumptions? 65 | 66 | You can use the [project summary cards](https://github.com/DEFRA/design/raw/master/assets/project-summary-cards.pdf) to help set the context for a crit. 67 | 68 | 69 | #### 2. Say what kind of feedback you want 70 | 71 | * graphic design 72 | * interaction design 73 | * service design 74 | * content design 75 | 76 | 77 | #### 3. Let the team review the work 78 | 79 | * don’t give a demo 80 | * don’t talk too much 81 | * don’t get defensive 82 | * do take notes 83 | * do listen 84 | 85 | 86 | ### Giving feedback 87 | 88 | 89 | #### 1. Listen to the context 90 | 91 | * ask questions if you need to 92 | 93 | 94 | #### 2. Give the right kind of feedback 95 | 96 | * avoid personal opinions 97 | * avoid absolute statements 98 | * ask open questions 99 | * be kind 100 | * explore ideas and suggest alternatives 101 | 102 | 103 | Instead of: 104 | 105 | *“I don’t like X”* 106 | *“Y never works”* 107 | 108 | Ask: 109 | 110 | *“What happens if...”* 111 | *“Have you tried...”* 112 | 113 | 114 | You can use the [questions and suggestions form](https://github.com/DEFRA/design/raw/master/assets/questions_and_suggestions.docx) to help provide feedback at a crit. 115 | -------------------------------------------------------------------------------- /design.md: -------------------------------------------------------------------------------- 1 | 2 | 12 | 13 | # Interaction Design 14 | 15 | In the Interaction Design Profession at Defra, we are generally agnostic about the tools interaction designers use to get the job done, but when it comes to designing products and services that both citizens and staff use on a day-to-day basis, we prioritise designing in the browser to ensure what we are designing is as close to what we are delivering (and has a very good chance of meeting, where relevant, the [service standard](https://www.gov.uk/service-manual/service-standard) and the [Technology Code of Practise](https://www.gov.uk/guidance/the-technology-code-of-practice). Plus, it goes a long way to ensuring what we design meets the [accessibility regulations](https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps) that ultimately will impact everything we design. 16 | 17 | The regulations aren't there to make our lives difficult, they are there to help us build better products and services. 18 | 19 | HTML prototyping is central to how we deliver our design work. Depending on the structure and the way a team is set up, sometimes the design and prototyping workflow will be slightly different and more of the prototyping will be done by a front end developer. Ultimately, it is what is most suitable for the individual team. However, a designer will always be more empowered if they can communicate their ideas through HTML. 20 | 21 | [Full list of what interaction designers in government do and the skills required to do the job](https://www.gov.uk/guidance/interaction-designer) 22 | 23 | Below are some of the activities carried out by Interaction and Service designers in Defra. 24 | 25 | ### Discovery 26 | 27 | How interaction designers support discovery: 28 | 29 | * Build knowledge of the subject and understanding of the policy intent (work with stakeholders, policy and subject matter experts) 30 | * Understand how users interact with any current service 31 | * Understand user needs and track interactions across departmental and organisational boundaries 32 | * Help the team to identify and investigate pain points or problems with any existing service 33 | * Capture, document and present holistic user journeys in a clear, engaging way 34 | * Make plans for Alpha ('How might we statements', hypotheses and assumptions to test) 35 | * Work with team and stakeholders to capture the entire perspective of a service, help to set the vision and build a roadmap for the future 36 | 37 | ### Alpha 38 | 39 | How interaction designers support the alpha phase: 40 | 41 | * Prioritise assumptions identified in discovery for testing 42 | * Facilitate design and mapping workshops with the team 43 | * Design and test multiple solutions to make sure we build the right thing 44 | * Decide on high-level to be user journeys (online, offline etc) 45 | * Iterate and test assumptions through prototyping 46 | * Identify and create reusable patterns and components that can be rolled out across Defra and across government services 47 | * Make sure the service is inclusive and accessible 48 | * Know how to use data and research to influence design thinking 49 | 50 | ### Beta 51 | 52 | How interaction designers support the beta phase: 53 | 54 | * Prototype detailed interactions, components, screens 55 | * Iterate designs based on user research, data, analysis and feedback 56 | * Iterate and refine existing design patterns where needed 57 | * Create new design patterns where needed and share with wider Defra and cross government design communities 58 | * Make sure the service can be used by everyone 59 | * Help the team test the service with assistive technology 60 | * Help the team to create a plan for assisted digital users 61 | * Utilise, iterate and introduce interaction patterns and standards that scale 62 | 63 | ### Live 64 | 65 | How interaction designers support live: 66 | 67 | * Use feedback, analytics, and call centre data to identify areas for product improvement 68 | * Continue to address any constraints identified in beta 69 | * Work with other organisations that provide services that are part of the same service journey in order to iterate towards solving a whole problem for users 70 | * Iterate and test designs with users 71 | 72 | ### New features 73 | 74 | What is it? - An interaction designer makes sure any additional features are designed to meet user needs, design standards and accessibility legislation. They also make sure new features are aligned to the service vision and add value for users. 75 | 76 | An interaction designer will: 77 | 78 | * understand how users interact with and are affected by any new feature 79 | * design and test prototypes to make sure new features are usable and inclusive 80 | * create reusable patterns and components that can be rolled out across Defra 81 | 82 | ### External changes 83 | 84 | What is it? - An interaction designer updates products in response to changes in external components, legislation or services that the application depends on. 85 | 86 | An interaction designer will: 87 | 88 | * understand how changes will impact users 89 | * design and test prototypes to make sure new features are usable and inclusive 90 | 91 | ### Legacy products/sub-services 92 | 93 | What is it? - An interaction designer works on legacy applications making sure products are inline with current design standards and accessibility legislation. 94 | 95 | An interaction designer will: 96 | 97 | * work with existing product users to improve usability and efficiency 98 | * create designs to test with users working within legacy technology constraints 99 | * help the teams to understand and meet accessibility legislation 100 | 101 | # Service Design 102 | 103 | Service designers help to define the scope of the service whether it is a minimal viable product (MVP), a minimal viable service (MVS) or a minimal marketable service (MMS). Together with the product or service manager they will reflect on the identified user needs and figure out what the smallest useful version of the service can be. 104 | 105 | And when the time comes, service designers facilitate the design of the service from end to end across all channels both online and offline, from backstage processes and activities to front user-facing products and tasks. This facilitation allows the whole team to be involved and to ensure the best solution is reached. 106 | 107 | When mapping a users' journey, a service designer will include a view of an entire system with all of its stakeholders and all of its pain points to ensure they are spotting all opportunities for reducing cost, reducing complexity and reducing the steps for a user to achieve their goal. In the Discovery phase, 90% of a service designer's work is archaeology. 108 | 109 | ### Discovery 110 | 111 | How service designers support discovery: 112 | 113 | * Question the scope of the discovery – broaden it, rescope it (and if necessary initiate further discovery) 114 | * Keep the team on track for an appropriately wide discovery 115 | * Understand who the users and user groups of the service/system/thing are (primary users, secondary users, internal users) 116 | * Investigate users’ contexts, needs, potential gains, pain points 117 | * Synthesise user research data and share findings back to the wider team and key stakeholders 118 | * Sift through quantitative data and link it to qualitative findings, potentially initiate more 119 | * Research and describe underlying support systems and technologies 120 | * Analyse dependencies (contractual, legal, technological, ethical) 121 | * Map the as-is state of the service offered today 122 | * Map all stakeholders involved in the provision of the service to end users 123 | * Capture what the provision of service in different channels looks like 124 | * Research how much the service costs to operate, who funds it and how and how it is funded today and how it expensive its provision is 125 | * Read policy documents, laws, standards, regulations and question today’s 126 | * Summarise major pain points of users and opportunities for service (re)-development / improvements 127 | * Help the team agree scope and boundaries and decide when is the right time to move into Alpha 128 | * Articulate the vision for the service (with product manager/service owner) 129 | 130 | ### Alpha 131 | 132 | How service designers support the alpha phase: 133 | 134 | * Understand and respond to the users of a service and the context they are in 135 | * Identify what the real problem is 136 | * Develop a strategic vision for the service (final destination, not just the plan for beta) 137 | * With the product manager, hold the vision for the team 138 | * Work with team to develop a scaffolded approach to delivering the vision 139 | * Help define problems for interaction designers to explore 140 | * Map and visualise the journey of users 141 | * Facilitate a shared understanding within and outside of the team 142 | * Spot opportunities for reducing cost and complexity 143 | * Help define the scope of the service 144 | * What are the feasible and useful fixes you can do - low hanging fruit where change is feasible, easy and beneficial for the user, and what is harder to do 145 | * Explore and prototype various solutions to the problem 146 | 147 | ### Beta 148 | 149 | How service designers support the beta phase: 150 | 151 | * Keep track of user needs as the service is used and help prioritise into fixes, new features and functionality 152 | * Help the service to understand and decide what new usage, contexts and features should be incorporated into digital channels or built into other channels and support systems 153 | * Find and implement improvements to the service in all channels 154 | * Work with caseworkers and support teams to make sure that user’s needs and problems are represented in the development teams, and incorporate feedback that will help caseworkers do their jobs better 155 | 156 | ### Live 157 | 158 | How service designers support live: 159 | 160 | * Identify areas for automation or improvement to make internal processes simpler and more efficient 161 | * Identify customer and user behaviours and process for continuously provide feedback to product and service teams 162 | * Provide a holistic view, from digital and physical channels and human interactions and ongoing identification of metrics and opportunities 163 | 164 | ### Scoping/shaping 165 | 166 | Working with the business and policy upfront to understand what we have, what we might need to do and why. This stage is about establishing the problem/costs/issues that you want to look at. Including the people and skills you are likely to need for discovery. At this stage we need to define the problem(s) and the desired outcome(s). 167 | 168 | Questions to answer: 169 | 170 | * Who are the users and stakeholders? 171 | * Do we understand their needs? 172 | * What underlying challenges do we need to address? 173 | * What already exists internally/ externally? 174 | * What do we want to achieve? 175 | * How might this link to the wider digital strategy? 176 | * What areas might we need to look into in more detail? 177 | * What is the scope we want to explore in discovery? 178 | 179 | ### Workshops 180 | 181 | A Service Designer will: 182 | 183 | * Facilitate sessions involving key stakeholders/ users 184 | * Understand and frame the problems you want to solve 185 | * Help you sketch out a vision 186 | * Create an agreed set of outcomes 187 | 188 | ### Design sprints / UCD policy design 189 | 190 | Understand the policy intent and the needs of users to help design the policy and generate ideas for how it might be enacted. 191 | 192 | A Service Designer will: 193 | 194 | * Conduct initial stakeholder/ user exploration 195 | * Document insights 196 | * Facilitate idea generation 197 | * Run co-design sessions to test and build on hypotheses 198 | * Create prototypes to test policy 199 | 200 | ### Exploration 201 | 202 | Working alongside policy, business analysis and architecture to understand the main business drivers, problems to be solved and desired outcomes before moving to Discovery. 203 | 204 | A Service Designer will: 205 | 206 | * Identify the main business drivers 207 | * Gather existing insight about the users of any current service and high level pain points 208 | * Gather existing insight about user needs 209 | * Identify subject matter experts and key stakeholders 210 | * Align proposed work to strategy and programme vision 211 | * Work with Policy to define the problems we are trying to solve 212 | * Work with Policy to define the outcomes we want to deliver 213 | * Work alongside a Business Analyst to understanding the people, processes and data involved in any as is process 214 | * Analyse failure within services and identify root causes for that failure. Identify opportunities for cost reduction and improvement within an existing service. 215 | * Create as is user journeys, highlighting pain points, dependencies, areas for improvements and hypothesis to test 216 | * Create service prototypes, and design touchpoints 217 | * Work with the team to provide recommendations for how to take the work forward 218 | * Frame and create problem statements for discovery 219 | 220 | ### New programmes of work 221 | 222 | Services as end users would know them transcend delivery or product teams. Service designers work across a programme of work to design the interactions and building blocks that make a new service. The service designer may support multiple product teams to provide insight on how to achieve desired outcomes in a measurable way. 223 | 224 | A Service Designer will: 225 | 226 | * Identify the main business drivers 227 | * Work with the team to define the problems we are trying to solve 228 | * Work with Policy to define the outcomes we want to deliver 229 | * Create as is user journeys, highlighting pain points, dependencies, areas for improvements and hypothesis to test 230 | * Develop a strategic vision for the service 231 | * Design the interactions and building blocks that make up the service 232 | * Create service prototypes to test ideas and assumptions 233 | * Influence performance reporting so we measure and target improvements to things that matter to users 234 | * Lead on ensuring that interactions and user journeys across the programme are rational and consistent 235 | 236 | ### Existing programmes of work 237 | 238 | Service designers work with existing programmes to help connect discrete digital projects to deliver a joined up service vision, provide cost efficiencies, and increase the effectiveness with which end-user benefits are delivered. 239 | 240 | A Service Designer will: 241 | 242 | * Align and lead communication with service managers, product owners and policy colleagues to define user journeys and articulate the vision for products and services 243 | * Visualise/map existing products and processes, highlighting inconsistencies, inefficiencies, dependencies, pain points and dead ends. 244 | * Visualise/map relationships between different products or sub services 245 | * Identify opportunities for service improvement and cost reduction 246 | * Identify opportunities to align internal processes 247 | * Identify opportunities to align our services with user journeys and tasks 248 | * Lead on ensuring that interactions and user journeys across the programme are rational and consistent 249 | * Understand user needs and track interactions across departmental and organisational boundaries 250 | * Influence performance reporting so we measure and target improvements to things that 251 | -------------------------------------------------------------------------------- /package-lock.json: -------------------------------------------------------------------------------- 1 | { 2 | "lockfileVersion": 1 3 | } 4 | -------------------------------------------------------------------------------- /service-teams.md: -------------------------------------------------------------------------------- 1 | 11 | 12 | 13 | # Services we're working on 14 | 15 | 16 | ## Animal and Plant Health 17 | 18 | 19 | - Pig Syndromics 20 | - Plant Health Risk Register 21 | - Proficiency Testing Laboratory Information Management System (PT LIMS) 22 | 23 | 24 | ## Borders, Biosecurity and Trade 25 | 26 | - API Developer Portal 27 | - Apply for an exemption from avian influenza disease control restrictions 28 | - CITES 29 | - Comply with UK REACH (Chemicals) 30 | - eCerts 31 | - ECHO 32 | - Electronic application for phytosanitary certification (EAPC) 33 | - Fish Export Service (FES) 34 | - IPAFFS 35 | - PHES 36 | - Risk Engine 37 | - Trade Platform 38 | - Veterinary medicine 39 | - Wood packaging material for import and export 40 | 41 | 42 | ## Flood Services 43 | 44 | - Check for Flooding 45 | - Flood Maps for Planning 46 | - Improving Access 47 | - Next Generation Warning System 48 | - Reservoir Act Compliance Enforcement (RACE2 49 | 50 | 51 | ## Future Farming 52 | 53 | - Advice Common Area 54 | - Local Nature Recovery 55 | - Making Payment Data Public 56 | - Slurry 57 | - Sustainable Farming Incentive 58 | - Vet Visits 59 | 60 | 61 | ## Natural England 62 | 63 | - Biodiversity Net Gain 64 | - Conservation Management Service 65 | - Natural England Architecture 66 | - Sustainable Development Digital Service 67 | 68 | 69 | ## New Initiatives 70 | 71 | - Air Quality and Industrial Emissions 72 | - Common Platforms and Customer ID 73 | - Forest Risk Commodities 74 | - Natural Capital Ecosystem Assessment 75 | - Science Capability for Animal Health (SCAH) 76 | 77 | 78 | ## Regulatory Services 79 | 80 | - Fishing Rod Licenses 81 | - Ruby Waste 82 | - Water Abstraction 83 | 84 | 85 | ## Waste Reforms 86 | 87 | - Collection and Packaging Reforms 88 | - Waste Exemptions 89 | - Waste Tracking 90 | -------------------------------------------------------------------------------- /specialist-publisher.md: -------------------------------------------------------------------------------- 1 | 2 | 12 | 13 | # What is Specialist Publisher 14 | 15 | The guide will presume you or someone in your team already have access to Whitehall Publisher or the Whitehall staging environment, Whitehall Integration. 16 | 17 | ### Overview 18 | 19 | The publishing platform for mainstream content on GOV.UK is Whitehall Publisher. However, there are other publishing tools for types of content that cannot best be served by Whitehall Publisher. One of these is Specialist Publisher. Like Whitehall Publisher, Specialist Publisher is hosted on publishing.service.gov.uk. If you or someone in your team currently have access to either Whitehall Integration or Whitehall Publisher, you access Specialist Integration or Specialist Publisher in the same way. 20 | 21 | Specialist Publisher allows teams to publish to GOV.UK in much the same way as in Whitehall Publisher but where content and documents are presented in a ‘finder’ functionality. This allows the published content to be filtered according to an agreed filter set including a set of specified metadata. A schema is then built for the agreed filter set. This can either be done by your team or the Specialist Publisher team at Government Digital Service (GDS) (examples of schemas). For each piece of content, metadata is presented in a blue box at the top of the content as well as in the listing in the filtered list (examples of live Specialist Finders below). The best user case for implementing a Finder is that users need to be able to find content by the way of specific meta data and filtered views. 22 | 23 | The way that Specialist Publisher manages published content (eg research reports) is more limited than Whitehall Publisher. There is one template and when publishing content, attachments, links and images have to be added manually in the Markdown. Make sure this isn’t a problem for anyone who is going to be publishing any content in the future. 24 | Only content published via Specialist Publisher can be displayed in the Specialist Finder. For example, if content is currently published via Whitehall Publisher, it can’t be displayed in a Specialist Finder. It would need to be republished via Specialist Publisher and then to avoid duplication the version on Whitehall Publisher would need to be deleted. The team at GDS can support with forwarding. However, any content published via Specialist Publisher does appear in GOV.UK search and can be displayed as featured content if the instance of the Specialist Finder is implemented in conjunction with a type of organisation page published via Whitehall Publisher or as linked content within a Guidance page. 25 | The default unfiltered view of content in a Specialist Finder list is most recently published at the top of the list. In Specialist Publisher there is no functionality to select a date of publication (past or future) so if your team is planning to publish existing content as part of the set up of an instance of the Specialist Finder, you need to publish it in order of oldest first to ensure it displays in the correct order. 26 | 27 | The implementation of a Specialist Finder requires the support of a specific team in GDS. Details below. Before talking to GDS, discuss your team’s requirements with the Head of Content in DDTS, Lucy Hartley, to establish that Specialist Publisher is the correct solution for your project. 28 | 29 | If you have a need for volume publishing, discuss with the GDS team. They have done this before. 30 | 31 | There is no cost to Defra to use the service. 32 | 33 | The length of time required to deploy the service needs to be discussed with the team at GDS. Timelines can be impacted by higher priority work (eg COVID or Brexit) 34 | 35 | ### Reference 36 | 37 | * Notes on GitHub https://github.com/alphagov/specialist-publisher 38 | * Examples of schemas which are stored in a JSON format https://github.com/alphagov/specialist-publisher/tree/master/lib/documents/schemas 39 | * Overview of publishing tools on GOV.UK 40 | * Example of a prototype used on the FCERM project which could be used to get you started https://github.com/matthewsolle/FCERM-Specialist-Publisher 41 | 42 | ### Specialist Publisher team at GDS 43 | 44 | Thomas Leese, Lead Developer thomas.leese@digital.cabinet-office.gov.uk 45 | Jonathan Nichols, Product Manager jonathan.nichols@digital.cabinet-office.gov.uk 46 | 47 | ### Examples 48 | 49 | https://www.gov.uk/raib-reports 50 | https://www.gov.uk/maib-reports 51 | https://www.gov.uk/drug-device-alerts 52 | https://www.gov.uk/international-development-funding 53 | https://www.gov.uk/european-structural-investment-funds 54 | https://www.gov.uk/drug-safety-update 55 | https://www.gov.uk/dfid-research-outputs/analysis-of-health-needs-and-health-system-response-in-the-coastal-districts-of-bangladesh 56 | https://www.gov.uk/countryside-stewardship-grants 57 | https://www.gov.uk/cma-cases 58 | https://www.gov.uk/business-finance-support 59 | https://www.gov.uk/aaib-reports 60 | 61 | ### Tips for adding content to the Markdown 62 | 63 | #### Adding an attachment 64 | 65 | You need to create a draft of the content you want to publish before you are able to add an attachment: 66 | 67 | 1. Add a draft of the content 68 | 2. Open it again to edit it 69 | 3. Add attachment 70 | 4. Add reference to the attachment in the Markdown at the point you want it to appear using the following code: 71 | 72 | [InlineAttachment:file_name.filetype] 73 | eg [InlineAttachment:A_method_for_monetising_the_mental_health_costs_of_flooding.pdf] 74 | 75 | NB the reference needs to be the exact name of the attachment 76 | 77 | #### Adding an image 78 | 79 | You need to create a draft of the content you want to publish before you are able to add an image as an attachment: 80 | 81 | 1. Add a draft of the content 82 | 2. Open it again to edit it 83 | 3. Add the image you want to use as an attachemnt (it needs to be saved with the dimensions of 960x640) 84 | 4. Add reference to the attachment in the Markdown at the point you want it to appear using the following code: 85 | 86 | ![InlineAttachment:image_name.filetype] 87 | eg ![InlineAttachment:KarinaC_StarboardWalkwayShowingStackOfHatchCoversAndGantryCrane.jpg] 88 | 89 | NB the ! at the beginning makes it show up as an image and the reference needs to be the exact name of the attachment 90 | 91 | #### Adding grey box 92 | 93 | Add $CTA before and after the text you want to appear in a grey box 94 | Example here https://www.gov.uk/maib-reports/crush-incident-on-general-cargo-vessel-karina-c-with-loss-of-1-life 95 | 96 | ### Other functionality 97 | 98 | #### Adding email alerts for content published and displayed in your Specialist Publisher Finder 99 | 100 | When your Finder is live, ask the GDS team to set up alerts based on the filters in your Finder. 101 | 102 | Example can be seen here when selecting ‘Get emails’ https://www.gov.uk/raib-reports 103 | 104 | #### Link from your Specialist Publisher to another page on GOV.UK 105 | 106 | If you are linking to your Finder from another page on GOV.UK (say an Organisation page) you might want users to be able to return to that page from the Finder. Once your Finder is live, ask the GDS team to add the link to your Finder. 107 | 108 | eg https://www.gov.uk/raib-reports with the link ‘From Rail Accident Investigation Branch’) 109 | -------------------------------------------------------------------------------- /standards.md: -------------------------------------------------------------------------------- 1 | 2 | 12 | 13 | ## Defra Design standards & guidance 14 | 15 | All Defra's online services must: 16 | 17 | - Be designed to meet the Government [service standard](https://www.gov.uk/service-manual/service-standard) 18 | - Meet the [government accessibility requirements](https://www.gov.uk/service-manual/helping-people-to-use-your-service/making-your-service-accessible-an-introduction#meeting-government-accessibility-requirements) 19 | - Be designed based on user needs 20 | 21 | Go to the [Defra design standards repo](https://github.com/DEFRA/design-standards) 22 | -------------------------------------------------------------------------------- /tools-and-resources.md: -------------------------------------------------------------------------------- 1 | 2 | 12 | 13 | # Tools and resources 14 | 15 | ## GOV.UK Prototype kit 16 | 17 | There is a very well supported design system and front end prototyping kit. The [GOV.UK Design System](https://design-system.service.gov.uk/) provides a well-supported way to make interactive prototypes that look like pages on GOV.UK. These prototypes can be used to show ideas to people you work with, do user research and quickly iterate ideas. They can also help you build fully fledged interactive prototypes that look to solve complicated problem as simply as possible. It also provides a good platform for developing staff-facing products and services. In this list of cross government design systems, predominately supporting staff-facing tools, there are other examples of how designers across government are solving problems and provide other sources of solutions and direction. [Gov Design Systems](https://github.com/ctdesign/gov-design-systems-list) 18 | 19 | Also, you will find that there is great support and experience of prototyping throughout the design team and we try to run workshops on how to use the prototyping kit. 20 | 21 | ### Getting set up 22 | 23 | The GOV.UK Prototype Kit cannot be installed on a networked Defra PC laptop. If you are a contractor or a supplier you will have to use your own unnetworked machine to run it. If you are a permanent civil servant member of the design team (or the UCD team) you should already have an off network MacBook on which it can be installed and run successfully. If you don't have one, request one from your line manager or UCD Operations. 24 | 25 | [Get started](https://design-system.service.gov.uk/get-started/) on GOV.UK Design System 26 | 27 | ### Github 28 | 29 | Get a Github account. To get an account you must set up [two factor authentication](https://help.github.com/en/articles/configuring-two-factor-authentication). 30 | 31 | Use the Defra [GitHub account](https://github.com/defra-design) to host the code for your prototype. Ask to be added as a member of the team and then either set up the repo yourself or ask to have one set up up by the UCD Operations team or your line manager. Make sure you name the repo so everyone understands what it is and please include the details of the project in the read me file. Please also include a design history in your prototype so it is easy for other people to understand what you have been doing and what you have achieved. [GOV.UK Design History Template](https://github.com/x-govuk/govuk-design-history-template). All prototype repo's must be named with an _proto and be managed by the design team. 32 | 33 | ### Heroku 34 | 35 | [Get a Heroku account](https://www.heroku.com) 36 | To get your prototype online. It’s simple and fast to deploy new versions as you work and to allow people to view and test quickly. 37 | 38 | Get your app set up on the central Heroku account. Design Leads and Design Ops will help with this (and if you haven't used Heroku before, ask them for some help) 39 | 40 | Further guidance [Heroku](https://govuk-prototype-kit.herokuapp.com/docs/publishing-on-heroku) for hosting your password protected prototypes. 41 | 42 | ### Components and patterns 43 | 44 | Design patterns solve the common problems so teams can focus on the things unique to their service and it’s users. 45 | 46 | Check the [GOV.UK Design System](https://design-system.service.gov.uk/) to see if the component or pattern you need is already being used across government. 47 | 48 | If you cannot find what you need in the GOV.UK Design System you can: 49 | 50 | * [see if it is being worked on by other teams across government and add your findings](https://design-system.service.gov.uk/community/backlog/) 51 | * [see if it is being worked on by someone in Defra](https://github.com/DEFRA/design-discussions/issues) and add your findings 52 | * [propose a new pattern in the Defra backlog](https://github.com/DEFRA/design-discussions/issues) 53 | * [propose a new pattern in the GOV.UK Design System](https://design-system.service.gov.uk/community/propose-a-component-or-pattern/). All patterns must be [useful and unique](https://design-system.service.gov.uk/community/contribution-criteria/#new-proposals). 54 | 55 | * Check x-govuk for [design patterns and design resources] from other government departments (https://x-govuk.github.io/) 56 | 57 | ### Extensions 58 | 59 | These are node modules that can be install to add functionality to the prototype kit 60 | 61 | * [Custom filters that help to solve common prototyping challenges](https://github.com/defra-design/extra-filters) 62 | * [Defra page template for internal services](https://www.npmjs.com/package/defra-template) 63 | * [Defra page template for showing flood warnings](https://www.npmjs.com/package/flood-banner) 64 | 65 | ### GOV.UK Prototype kit blog posts 66 | 67 | * Read [tips on working with the Gov.uk prototype kit](https://medium.com/@onebc/five-tips-from-five-weeks-using-the-gov-uk-prototyping-kit-b63f5592cc14) 68 | * [More efficient prototyping with the GOV.UK prototype kit: step by step](https://medium.com/gov-design/more-efficient-prototyping-with-the-gov-uk-prototype-kit-step-by-step-84ea2832549a) 69 | * [Validation for prototypes](http://www.craigabbott.co.uk/validation-for-prototypes) 70 | 71 | ### Documentation 72 | 73 | * [GOV.UK Eleventy plugin](https://x-govuk.github.io/govuk-eleventy-plugin/) 74 | * [GOV.UK Design History](https://design-history.herokuapp.com/) 75 | 76 | ## Wireframing 77 | 78 | Our default wireframing tool for the Defra Design Team is Figma. If you are a permanent civil servant member of the team, request to be added to the team Figma account. Ask your line manager or UCD Operations. If you are a contractor or a supplier, you will need to provide your own licence but can be added to shared work files as required that sit in the Defra Design Team Figma account. 79 | 80 | Open source kits are available for wireframing: 81 | 82 | * [Google draw wireframing kit](https://docs.google.com/drawings/d/1d10Rl4X0_quNgLk8oPlgbXK4sfDU09OvpUsIn8Azsv8/edit) 83 | * [Sketch wireframing kit](https://github.com/abbott567/sketch_wireframing_kit) 84 | * [Balsamiq wireframing kit](https://github.com/enoranidi/govuk-design-system-balsamiq) 85 | * [Figma wireframing kit](https://www.figma.com/file/NWuFffKvPQhl3aJ9nKU0p3/GOV.UK-Design-System?node-id=23%3A233) 86 | 87 | ## Accessibility 88 | 89 | [Defra accessibility resources](https://defra-design.github.io/accessibility/) 90 | 91 | ## User flows 92 | 93 | The supported and approved whiteboarding tool in the Defra Design Team is Mural. UPDATE TO FOLLOW ON ROLL OUT OF MURAL AS THE DEFAULT TOOL IN FEBRUARY 2023. In the meantime, please use your own free Mural account or the existing Defra Design Team Miro account. 94 | 95 | Open source kits are available for producing flow diagrams: 96 | 97 | * [Sketch flow kit](https://github.com/charlesrt/gov-flow) 98 | * [Google draw flow kit](https://www.beatnic.co.uk/2019/10/04/google-drawing-template-gov-flow-kit/) 99 | 100 | ## Defra branding and print template 101 | 102 | Style guide, templates and brand assests 103 | 104 | * [Corporate document templates](https://intranet.defra.gov.uk/forms/corporate-document-templates/) 105 | * [Branding](https://intranet.defra.gov.uk/how-to/correspondence/branding-corporate-templates/) 106 | 107 | ## Training 108 | 109 | Chris Barrett and Gareth Thomas in the Defra Design Team run regular prototype training for the Defra User-Centred Design Community. 110 | 111 | ## Workshops and meetings 112 | 113 | * [Workshop Tactics for product teams](https://www.workshoptactics.com/pages/tactics) 114 | * [Quick icebreakers for online meetings, (that don’t suck)](https://emilywebber.co.uk/quick-icebreakers-for-online-meetings-that-dont-suck/) 115 | * [Cards for humanity](https://cardsforhumanity.idean.com/) 116 | * [Tarot cards of tech](http://tarotcardsoftech.artefactgroup.com/) 117 | * [Good Service Scale](https://docs.google.com/spreadsheets/d/1z6_WN7XYngyJd-kKSHcmKxSKVFpf4dV8RbUofUdTQ9c/edit?usp=sharing) 118 | 119 | ## Capability 120 | 121 | Share the [Service and Interaction Design Capability Trello board](https://trello.com/b/Xcx5TBr1/service-and-interaction-design-capability) with people in your team to help them understand what you do. 122 | --------------------------------------------------------------------------------