<?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 Matt Tyas on Medium]]></title>
        <description><![CDATA[Stories by Matt Tyas on Medium]]></description>
        <link>https://medium.com/@matttyas?source=rss-34cea8622334------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Bce5Rh2kYl0aHNajOe0l2g.png</url>
            <title>Stories by Matt Tyas on Medium</title>
            <link>https://medium.com/@matttyas?source=rss-34cea8622334------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:48:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@matttyas/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[Design system team weeknotes issue 6]]></title>
            <link>https://matttyas.medium.com/design-system-team-weeknotes-issue-6-8947e1fa42c5?source=rss-34cea8622334------2</link>
            <guid isPermaLink="false">https://medium.com/p/8947e1fa42c5</guid>
            <category><![CDATA[co-op]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Matt Tyas]]></dc:creator>
            <pubDate>Fri, 30 Oct 2020 14:31:32 GMT</pubDate>
            <atom:updated>2020-10-30T14:31:32.254Z</atom:updated>
            <content:encoded><![CDATA[<p>The design system team is part of one web following our overarching vision of:</p><blockquote><strong>Coherent and cost-effective user experiences for Co-op.</strong></blockquote><p>The design system team provide the solid foundational tools, resources and standards to enable other teams to work fast — with quality baked in from the start.</p><h3><strong>Design system meet-up</strong></h3><p>We hold design pattern meet ups every 3 weeks. In this session we <a href="https://miro.com/app/board/o9J_kxRLSUw=/">ran an exercise to map the process designers would ideally use to contribute</a>. <br> <br>From experience, I know there are numerous elements and components used across digital products and services that aren’t in the Design System due to lots of different reasons.</p><p>This session was held to increase our understanding of how we can encourage and help designers contribute new components or raise awareness of the need to iterate an existing component. <br> <br>It’s early but the insights from the session will certainly help inform our direction and priorities. <br> <br>We’ll start small and quick by reviewing and updating the Component lounge Miro board and what it is. We’ll let the design team know when this is done. We also have 1 of 2 new pages that will be published on the Design System website that explain how to contribute and link to the updated Component lounge Miro board.</p><figure><img alt="image  of an online whiteboard showing the flow of contribution designers suggested" src="https://cdn-images-1.medium.com/max/757/1*d4Xe9Z-InQGjVr0-QvMW3g.png" /></figure><figure><img alt="Live soon will be a page to show people how to contribute." src="https://cdn-images-1.medium.com/max/1024/1*lnsOjL5mvHMTYKN8udguFQ.png" /><figcaption><em>Live soon will be a page to show people how to contribute.</em></figcaption></figure><figure><img alt="We also want to be open about what we’re working on and why it’s important." src="https://cdn-images-1.medium.com/max/1024/1*yvO3WEXWrAeeSVaYPacTAg.png" /><figcaption><em>We also want to be open about what we’re working on and why it’s important.</em></figcaption></figure><h3><strong>User journey (Level 2) accessibility testing framework</strong></h3><p>We have been grouping key accessibility issues into levels based on how likely they are to prevent someone from using something we have made.</p><p>Now we are working to put these things into a logical order and a format that we can provide to product teams. The goal is to provide a framework that makes it easy to test for those issues that make our products and services less accessible and even completely inaccessible.</p><h3><strong>Fixing accessibility issues in the design system components</strong></h3><p>We’ve also begun to fix some of the accessibility issues raised in our first round of component testing. This week we’ve:</p><h3><strong>Tweaked our button colours so they are fully compliant to our colour contrast guidelines.</strong></h3><p>Previously the hover states did not have enough contrast.</p><p>We’ve changed them from this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/249/1*rBgSdckm65UT3vKNnIo_yg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/213/1*LC6j2Z5grVEKZzv84E3JhQ.png" /></figure><p>To this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*ilZiyxU4YpOyPIhpYmRqkw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*kHgAsZc3x_ApzW6Zz-AemA.png" /></figure><p><em>Images show hovered button states. Text sizes and any weird formatting are due to embedding of these images in email.</em></p><p>The foundations-buttons component is now at <a href="https://www.npmjs.com/package/@coopdigital/foundations-buttons">v2.3.0</a> and the CSS foundations (that the buttons are included in) are now at v<a href="https://www.npmjs.com/package/@coopdigital/css-foundations">6.2.1</a>.</p><h3><strong>Fixed colour contrast issues on the skip navigation</strong></h3><p>Skip navigation is used by people who use the keyboard to navigate quickly move to areas of the page avoiding large blocks of links they may otherwise have to manually tab through.</p><p>We fixed the colour contrast of this component to make it compliant with our accessibility guidelines.</p><p>We changed it from this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/351/1*Y6VaQdAJsaVmOciDUxlHow.png" /></figure><p>To this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/288/1*IhWcElRxr_6_1PgmXfebKQ.png" /></figure><p>The skip navigation component is now at <a href="https://www.npmjs.com/package/@coopdigital/component-skipnav">v2.2.1</a>.</p><h3><strong>We increased the tappable areas of the logo — without changing its size</strong></h3><p>Tap or click areas of interactive elements must be at least 44x44px in most scenarios. Previously the logo was just under at 38x41px.</p><figure><img alt="The red border illustrates the new tappable size." src="https://cdn-images-1.medium.com/max/219/1*nRyH60qKNL6q3wUiD94eNA.png" /><figcaption><em>The red border illustrates the new tappable size.</em></figcaption></figure><p>The foundations-global component is now at <a href="https://www.npmjs.com/package/@coopdigital/foundations-global">v3.2.0</a> and the CSS foundations (that the global logo styles are included in) are now at v<a href="https://www.npmjs.com/package/@coopdigital/css-foundations">6.2.1</a>.</p><h3><strong>Researching the developer experience and the structure of our front-end</strong></h3><p>As the team is looking at some of the current issues flagged by the accessibility audit, we’re also starting to think more longer term to try and shape what the future of the design system looks like.</p><p>We’ve identified a few conversations that need to happen with folk in other teams, as well as trying to identify where/when/how the current design system is, and isn’t, being used.</p><p>We’re also trying to hone the contribution process to make it easier for designers to suggest new components or enhancements to existing components, as well as looking at standards/guidelines for developers.</p><h3><strong>What’s next</strong></h3><p>We’ll be continuing:</p><ul><li>with our work on accessibility</li><li>working on the structure of our front-end</li><li>tidying up our design files</li></ul><h3><strong>Our roadmap and walls</strong></h3><p>We’ve revamped <a href="https://miro.com/app/board/o9J_ku70qU8=/">our web team walls</a> so you can easily see our strategy, goals and roadmaps for the web platform teams in once place.</p><h3><strong>Contribution and support</strong></h3><p>If you need support using the design system, we have a public slack channel #designsystem-support</p><p>And if you find any <a href="https://github.com/coopdigital/coop-frontend/issues">issues or improvements in the coop-frontend you can raise them on Github</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8947e1fa42c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design system team weeknotes issue 5]]></title>
            <link>https://matttyas.medium.com/design-system-team-weeknotes-issue-5-127bfa0a7019?source=rss-34cea8622334------2</link>
            <guid isPermaLink="false">https://medium.com/p/127bfa0a7019</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[co-op]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Matt Tyas]]></dc:creator>
            <pubDate>Fri, 23 Oct 2020 15:52:11 GMT</pubDate>
            <atom:updated>2020-10-23T15:53:35.377Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Design system team weeknotes: Issue 5</strong></h3><p>The design system team is part of one web following our overarching vision of:</p><blockquote><strong>Coherent and cost-effective user experiences for Co-op.</strong></blockquote><p>The design system team provide the solid foundational tools, resources and standards to enable other teams to work fast — with quality baked in from the start.</p><h4><strong>Show and tell</strong></h4><p>We’ve not done an external show and tell yet, but we do record the ‘no prep’ show and tells. We felt this show and tell was such a good update (and felt prepped) that we should start inviting external people. In the meantime <a href="https://web.microsoftstream.com/video/4d7e4e58-44fe-4a52-9cb5-e5ca1da8a072?referrer=https:%2F%2Fco-op-digital.atlassian.net%2F">you can watch the web team show and tell here</a> — same content as the weeknotes, but including Coherence and Efficiency. The Design system update is first lasting about 14 minutes.</p><h4><strong>We’re almost ready to test our user journey (level 2) accessibility testing framework</strong></h4><p>We’ve previously written about the levelled approach to accessibility testing we’re developing so far we’ve developed 2 levels, these are:</p><ul><li>level 1 — that assesses the components in the design system — currently 515/548 tests pass giving us a 94% pass rate</li><li>level 2 — the user journey level testing we’re developing now</li></ul><p>The goal of the level 2 framework is to make accessibility testing in key user journeys as simple as possible for product teams. We’ll also begin to assess how well we’re doing as an organisation with regards to digital accessibility.</p><p>This is something we can then report on and improve over time.</p><h4><strong>What we’ve done</strong></h4><p>This week we began to further filter the areas we need to test. The problem we were solving here was trying to get the issues that must be tested (and fixed if issues are uncovered) down to a manageable amount for teams.</p><p>We did this with the team and the Dave Cunningham (leading the accessibility work across digital) by working through our Miro board of issue areas and ranking them by:</p><ol><li>Critical issues — things that will stop someone from using our products or services.</li><li>Major issues — things that will make it very difficult for somebody to use our products and services.</li><li>Minor issues — things that will make it frustrating for somebody to use our products or services.</li></ol><figure><img alt="Minor and Critical accessibility issues on an online whiteboard" src="https://cdn-images-1.medium.com/max/1024/1*ScZKXKT3hx-546McstQ3eQ.png" /></figure><p>We also introduced a horizontal line. Below the line are the issues that anecdotally we rarely see in Co-op products or are likely to be handled by the component (level 1) testing — assuming they pass.</p><p>This left us with 7 critical issues every team should spend time testing. These are:</p><ul><li>making all functionality available from a keyboard</li><li>allowing people to resize the content</li><li>making sure videos can be understood with no sound</li><li>checking that all the parts of each form have text labels</li><li>not using hovers to reveal extra information</li><li>if something changes on a page, it must be described to screen reader users</li><li>the use of semantics, ARIA landmarks and roles</li></ul><p>The last one — HTML mark-up semantics is a big topic. It means using the right HTML tags and attributes to describe the content of the page to machines — the browser or screenreader. Further work is required to break this one down into things that are absolute requirements and things that are less important, as well as ways to easily test.</p><p>From this we’ll create a spreadsheet similar to the component (level 1) testing framework but grouped according to our filtered issues.</p><figure><img alt="The testing framework level 2 spreadsheet" src="https://cdn-images-1.medium.com/max/1024/1*cRAxmE8wTFbRTRRW5XSpGg.png" /></figure><p>Along side this framework we’ll include information on how to test as well as a plain English guide to what standards we support and what they mean for users.</p><h4><strong>Making component development easier and better documented</strong></h4><p>Alongside all of the accessibility work running in the design system team, we’ve also got a functional spike of Storybook up and running — massive thanks to Jiebin Su for all the work he’d done in his own time on starting this up — this allows us to provide an a single repository where anyone can see components and interact with them, change properties etc. and see how they react.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ATKHYMapzcA_wbMtRvUNQ.gif" /></figure><p>This will also give us a place to host internal documentation — rather than relying on adding too much technical information to the design system website — which we expect to become more user friendly for a range of colleagues.</p><p>It’s really, really early on its lifecycle, but it’s an exciting starting point for the journey ahead… watch this space!</p><h4><strong>What’s next</strong></h4><p>We need to finish off our framework spreadsheet and research some of the critical issues further. We’ll then test this framework with the Food digital team in the near future.</p><h4><strong>Our roadmap and walls</strong></h4><p>We’ve revamped <a href="https://miro.com/app/board/o9J_ku70qU8=/">our web team walls</a> so you can easily see our strategy, goals and roadmaps for the web platform teams in once place.</p><p>Onward and upward.</p><p>The design system team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=127bfa0a7019" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design system team weeknotes issue 4]]></title>
            <link>https://matttyas.medium.com/design-system-team-weeknotes-issue-4-60975d22622c?source=rss-34cea8622334------2</link>
            <guid isPermaLink="false">https://medium.com/p/60975d22622c</guid>
            <category><![CDATA[co-op]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Matt Tyas]]></dc:creator>
            <pubDate>Fri, 23 Oct 2020 15:44:04 GMT</pubDate>
            <atom:updated>2020-10-23T15:53:23.152Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Design system team weeknotes: Issue 4</strong></h3><p>The design system team is part of one web and contributes to the overarching vision of:</p><blockquote><strong>Coherent and cost-effective user experiences for Co-op.</strong></blockquote><p>The design system team provide the solid foundational tools, resources and standards to enable other teams to work fast — with quality baked in from the start.</p><h3><strong>Accessibility in our user journeys</strong></h3><p>With Dave Cunningham’s help we’ve been looking at how we scale accessibility testing into product teams.</p><p>We want to make it part of everyone’s routine to test accessibility as well as making it easy to understand common issues that can arise.</p><h3><strong>What we did</strong></h3><p>We began by collating everything we would test in a user journey within a spreadsheet. This gave us a sense of the scale of the challenge and quickly realised it would need breaking down.</p><p>We tried a quick spike on an automated tool to test websites. Inspired by a piece of work by the BBC this tool could automate some tests and guide a user through manual tests — producing a report at the end. Although it seems very powerful, we ultimately decided it’s too much of a risk to work on further until we have learnt more about how teams will want to test — and have the skills in the team to deliver it.</p><figure><img alt="Automated testing running on coop.co.uk" src="https://cdn-images-1.medium.com/max/1024/1*56VPWzOyBUSdznRrNo_bUg.png" /><figcaption><em>On the left: Terminal output of the automated tests. On the right the guided manual tests (question and answer at the bottom).</em></figcaption></figure><p>After a regroup Dave did some thinking and started to help us break the tests down by severity to the user. For example. If a website is not navigable via the keyboard it will be totally unusable to a section of our audience.</p><figure><img alt="Minor to critical accessibility issues on an online whiteboard" src="https://cdn-images-1.medium.com/max/1024/1*EGzAF8kFhHBwT7p_BgOR8g.png" /></figure><p>On the other hand using justified text might not be a design decision we’d favour since it can make text harder to read for some users — it won’t stop anyone using our products.</p><h3><strong>What’s next</strong></h3><p>We need to flesh out these severity levels further and decide how we group and test them with a product team to see how it works in practice.</p><h3><strong>Our roadmap</strong></h3><p>We’ve also done some work fleshing out our roadmap. At a high level this now looks like:</p><p><strong>Now:</strong></p><p>Accessibility. Goals:</p><ol><li>100% pass rate for components in the design system.</li><li>A first pass accessibility framework being used by a product team.</li><li>New accessibility documentation in the design system.</li></ol><p>Developer experience. Goals:</p><ol><li>Making working with our components and front-end easier by creating better documentation.</li><li>Making development of new components easier.</li></ol><p><strong>Next:</strong></p><p>Design system website. Research goals:</p><ol><li>Understand users, content and direction for the main design system website</li><li>Understand the tech approach for the future</li><li>Understand adoption of the current design system with 3rd parties/agencies to identify potential pain points we can fix in future versions</li><li>Understand the contribution model of the design system and how we can simplify it in the future, whilst still upholding our high standards</li></ol><p><strong>Ongoing:</strong></p><p>Maintenance and community. Goals:</p><ol><li>Fix accessibility test fails.</li><li>Maintain community input and create backlog of future work.</li></ol><p>Onward and upward.</p><p>The design system team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60975d22622c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design system team weeknotes issue 3: 9 Oct 2020]]></title>
            <link>https://matttyas.medium.com/design-system-team-weeknotes-issue-3-9-oct-2020-81ab28de899d?source=rss-34cea8622334------2</link>
            <guid isPermaLink="false">https://medium.com/p/81ab28de899d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[co-op]]></category>
            <dc:creator><![CDATA[Matt Tyas]]></dc:creator>
            <pubDate>Wed, 14 Oct 2020 09:29:14 GMT</pubDate>
            <atom:updated>2020-10-14T09:40:28.439Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Design system team weeknotes: Issue 3</strong></h3><p>The design system team is part of one web following our overarching vision of:</p><blockquote><strong>Coherent and cost-effective user experiences for Co-op.</strong></blockquote><p>The design system team provide the solid foundational tools, resources and standards to enable other teams to work fast — with quality baked in from the start.</p><h3><strong>We presented at the digital All hands.</strong></h3><p>This week the Online business area presented at the digital all hands. We outlined the vision and goals for the Co-op online business area that consists of the web platform and enabling teams.</p><figure><img alt="Graphic showing the structure of the online business area." src="https://cdn-images-1.medium.com/max/1024/1*ELOi0WS6Ovqnn5DfPor2Sw.png" /></figure><h3><strong>Accessible content, inclusive language</strong></h3><p>Along with Jo Schofield and Dave Cunningham we’ve been working on a plain English guide to which AAA Web Content Accessibility Guidelines we will cover. We’re also going to be working with Jo on a guide to inclusive language. These pieces of work will inform and feed into the content design guidelines and style guide within the design system.</p><h3><strong>Content style guide</strong></h3><p>We have started working on more comprehensive guidelines for content design and how we do content at Co-op. The vision is to have an entry for each element, pattern or point of style we need to consider. Each one will have examples and evidence for why we do things a certain way.</p><h3><strong>Addressing the components that failed</strong></h3><p>Based on the work we carried out to test all of our components and foundations against accessibility criteria, we now have tickets and tasks in Jira ready to work through. Once these have been addressed and fixed, our pass % for our current set of components will be close to 100%. Just to repeat — this is just the start.</p><h3><strong>Component meet up!</strong></h3><p>We held an open session for anyone that wanted to take part — we asked for everyone to have their frustrations and questions ready for all things related to components, foundations, support, process and anything else related to the Design System.</p><p>In total there were 35 issues/questions highlighted. We were able to answer some of these directly in the session, others will help inform our roadmap and there were 2 broad themes that came out:</p><p>1. Awareness — how should we communicate changes and updates so that those that want to know, know.</p><p>2. Guidance — people want examples and guidance on usage of components.</p><h3><strong>What’s next?</strong></h3><p>Next up we’re zeroing in on the fixes for the failing components and getting them pushed out. We’re also starting to plan how we can make the design system more visible for <em>everyone, </em>and looking at firming up the contribution process — watch this space</p><h3><strong>Contribution and support</strong></h3><p>And if you find any <a href="https://github.com/coopdigital/coop-frontend/issues">issues or improvements in the coop-frontend you can raise them on Github</a>.</p><p><em>Thank you as well to </em><a href="https://twitter.com/_gbbns?lang=en"><em>Chris Gibbons</em></a><em>, </em><a href="https://twitter.com/ciaran_greene"><em>Ciaran Greene</em></a><em> and Alex hall for compiling these weeknotes.</em></p><p>Another great week.</p><p>The design system team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81ab28de899d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Co-op design system team weeknotes: Issue 2]]></title>
            <link>https://matttyas.medium.com/co-op-design-system-team-weeknotes-issue-2-16f079c3988a?source=rss-34cea8622334------2</link>
            <guid isPermaLink="false">https://medium.com/p/16f079c3988a</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[co-op]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Matt Tyas]]></dc:creator>
            <pubDate>Mon, 05 Oct 2020 08:53:45 GMT</pubDate>
            <atom:updated>2020-10-05T08:53:45.519Z</atom:updated>
            <content:encoded><![CDATA[<p>The design system team is part of one web following our overarching vision of:</p><blockquote><strong>Coherent and cost-effective user experiences for Co-op.</strong></blockquote><p>The design system team provide the solid foundational tools, resources and standards to enable other teams to work fast — with quality baked in from the start.</p><h3><strong>Continuing with our work on accessibility</strong></h3><p>This week we continued with our work on creating an accessibility testing framework.</p><h4><strong>Why is it important?</strong></h4><p>You can <a href="https://medium.com/@MattTyas/co-op-design-system-team-weeknotes-issue-1-86a1ff493694">read about why we’re focusing on accessibility here</a>.</p><h4><strong>What we’ve done</strong></h4><p>We’ve now tested 38/42 components across 16 categories. The framework is a work in progress so we found we could only run 548 out of a possible 693 tests.</p><p>The remaining tests either:</p><ul><li>need further discussion on the pass/fail criteria or on how we actually test them — and to what standards</li><li>couldn’t be tested as the component is not surfaced in the design system as yet</li><li>are not applicable to a component. For example the colour palette is not rated against using the correct HTML elements — we count these as passes to get a simpler metric.</li></ul><p>Of the tests we’ve been able to run so far, we ran:</p><p><strong>548 tests run on 38 components across 16 categories</strong></p><p><strong>515 Passing tests (94%)</strong></p><p><strong>33 Failures (6%)</strong></p><h4><strong>What’s next?</strong></h4><p>It’s a pretty good start, but only part of the story. These are component level tests done in isolation. We know that (in One Web anyway) many accessibility errors occur when components are used in the content management system, integrated into websites or are to do with larger bespoke functionality.</p><p>We also need to make sure things are tested with real users of mixed abilities.</p><p>Therefore our next steps are:</p><ul><li>taking the failed tests and creating a backlog of things to fix</li><li>looking into how we can automate some testing in the design system and web platform tenants</li><li>beginning to create a user journey level testing framework that we’ll test with product teams</li><li>Working with Dave Cunningham on the above and getting his help in more clearly defining what pass/fail really means in relation to the WCAG AA/AAA guidelines</li><li>planning more content design-led work as we welcome Alex Hall into the team after his sterling work on Membership</li></ul><p>We’re also:</p><ul><li>Starting design pattern meet-ups from next week</li><li>Having 2 days per fortnight of maintenance — to allow us to fix the accessibility errors we’ve found</li></ul><h4><strong>Last weeks survey</strong></h4><p>Last week we added a short survey asking if you had read our weeknotes and if the email format worked for you as an update.</p><p>We had 24 responses with a range of communication channels mentioned. These were email, Yammer and Slack. All of which we already use each week to publicise the work that is going on — so we’ll keep doing it this way.</p><p>There was also feedback that teams would like to be briefed on changes that are upcoming and what they need to do to accommodate them.</p><p>This is entirely understandable and something we plan to begin doing in the future, as we look at our operating model and the agreement we have with teams around Co-op. Watch this space.</p><h3><strong>Contribution and support</strong></h3><p>We’re looking at designing a clear, regular contribution to live process — that will start soon — watch this space. We’ll also be starting to understand how we work with and support product teams.</p><p>Another great week.</p><p>The design system team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16f079c3988a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Co-op design system team weeknotes: Issue 1]]></title>
            <link>https://matttyas.medium.com/co-op-design-system-team-weeknotes-issue-1-86a1ff493694?source=rss-34cea8622334------2</link>
            <guid isPermaLink="false">https://medium.com/p/86a1ff493694</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[co-op]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Matt Tyas]]></dc:creator>
            <pubDate>Mon, 05 Oct 2020 08:46:25 GMT</pubDate>
            <atom:updated>2020-10-05T08:46:25.133Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to the first official weeknotes from the newly formed design system team!</p><p>The design system team is part of one web following our overarching vision of:</p><p><strong>Coherent and cost-effective user experiences for Co-op.</strong></p><p>The design system team will provide the solid foundational tools, resources and standards to enable other teams to work fast – with quality baked in from the start.</p><p>We’ll be working with all of Co-op to make sure we’re doing the right things for our colleagues and customers.</p><p>We are a small (but mighty) team made up of:</p><ul><li>Chris Gibbons (Front-end Engineer)</li><li>Ciaran Greene (Interaction Design)</li><li>Matt Tyas (Product and One Web Principal)</li><li>Molly Whitehead-Jones (Content Design)</li><li>Alex Hall (Content Design)</li><li>Gaynor May (QA)</li><li>Tom Walker (User research)</li></ul><p>I’ve added job titles – but we’ll all be pitching in in all areas and helping people upskill where ever possible.</p><h3><strong>Our first focus: Accessibility and standards</strong></h3><p>Week 1 began with a planning session and the team unanimously decided to focus on the theme of accessibility and standards.</p><p>We know that trust is key to the design system. The design components we distribute must be high quality and help product teams move quickly knowing they are starting with a well tested baseline.</p><p>Since accessibility is the cornerstone of usability this is a valuable place to start – but why?</p><h3>Helping Co-op achieve its vision: Co-operating for a fairer world</h3><p>Our Co-op vision gives us clear direction that this is a thing we should focus on. If we truly believe in this vision – creating user experiences for everyone is an inherently Co-operative thing to do.</p><p>Aside from this – it is the right thing to do.</p><p>Dave Cunningham (who has been at the forefront of setting up an accessibility champions network in Co-op) recently refreshed our accessibility policy.</p><p>This outlines our commitment to creating accessible products and services and gives clear guidance on how, by:</p><ul><li>meeting the <a href="https://www.w3.org/TR/WCAG21/">Web Content Accessibility Guidelines (WCAG) 2.1</a>, Level AA as a minimum and Level AAA wherever possible</li><li>respecting the <a href="https://www.legislation.gov.uk/ukpga/2010/15/section/29">Equality Act 2010</a></li></ul><p>You can <a href="https://digitalblog.coop.co.uk/2020/08/20/introducing-our-accessibility-policy-for-co-op-products-and-services/">read about the accessibility policy in Dave’s blog post</a>.</p><p>The design team have also long held the principle:</p><p><a href="https://coop-design-system.herokuapp.com/principles.html#we-design-for-everyone"><strong>We design for everyone</strong></a></p><p>If that weren’t reason enough, it just makes good business sense to have Co-op’s services open and available to the anyone that wants to use them.</p><h3>What we’ve done</h3><p>We began by creating a draft accessibility framework based on the outputs of a workshop held the week before on accessibility testing. Roughly we decided we might need 3 levels on which to test our products:</p><ul><li>Level 1: Component level – the testing the design system team (and anyone else building for the design system) will do to ensure components reach the right standards from a design, front-end and content design perspective</li><li>Level 2a: CMS level – less defined right now, but is about ensuring when integrated into Contentful the standards are still met and content editors know they need to enter (things like) meaningful alt tags to images</li><li>Level 2b: Product level testing. Will be a framework and tools to help product teams test their own bespoke products.</li><li>Level 3: Components and products tested with real people of all abilities and cause them no issues in completing tasks. This is the ultimate aim as we can be most confident we’ve removed any able bodied bias by finding out how people really use our products.</li></ul><p>We’ve only begun to define level 1 right now and it takes the form of a spreadsheet.</p><figure><img alt="accessibility framework spreadsheet" src="https://cdn-images-1.medium.com/max/1024/1*ZQCb5NodlyQmevVsyEBQ_Q.png" /></figure><p>In an update I gave recently on the design system I said it was not the ‘cool project’ as it had a very important mission – this spreadsheet proves that I think.</p><p>We’ve defined categories to test against as well as begun to test components in the system right now in order to define the best tools and how much can be automated vs how much will be manual.</p><h3>What’s next</h3><p>We’ll be continuing with this work both creating the framework and finding issues in the design system that need to be fixed.</p><h3>Our roadmap</h3><p>We’ve also spent time on a rough and ready roadmap. There’s more work to be done on the ‘when’ and ‘how’ of the items in it but right now it looks like this:</p><figure><img alt="Post-it notes showing high level design system roadmap" src="https://cdn-images-1.medium.com/max/1024/1*EX7C2L6w6F0QIv3tRhLKqw.png" /></figure><h3>Contribution and support</h3><p>We are also looking at designing a clear, regular contribution to live process – that will start soon – watch this space.</p><p>It has been a great start and we’re excited about the future.</p><p>The design system team</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86a1ff493694" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I caused a mini Twitter storm – because of some job adverts I posted]]></title>
            <link>https://matttyas.medium.com/i-caused-a-mini-twitter-storm-because-of-some-job-adverts-i-posted-2e48fe1e451?source=rss-34cea8622334------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e48fe1e451</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[design-leadership]]></category>
            <dc:creator><![CDATA[Matt Tyas]]></dc:creator>
            <pubDate>Wed, 12 Feb 2020 20:11:19 GMT</pubDate>
            <atom:updated>2020-02-12T20:18:42.646Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s taken me a few weeks to get round to writing this. I wanted to make sure I wasn’t angry or upset and I had had enough time to reflect and weigh up all the facts.</p><p>I understand what happened fully now and, why people were upset.</p><p>But it was a misunderstanding.</p><p>A caveat before we get going (although I think it’s okay) I’m in no way saying my employer had anything to do with the mistakes made.</p><p>This makes it all sound very serious – it really isn’t.</p><h3>What happened?</h3><p>On a Monday morning a few weeks ago I tweeted out 4 roles I am recruiting at Co-op. 2 Lead front-end Engineers and 2 Front-end Engineers.</p><p>I went about my day.</p><p>Later when I got back to my desk I saw this tweet – and the resulting fallout.</p><p>This is normally where I’d embed the tweet. But I won’t be doing that. It feels fair to concentrate on what happened without calling anyone out.</p><p>Let’s carry on.</p><p>My stomach turned. What awful mistake had I made? I went completely into flight mode so I couldn’t really think straight. I sent a few initial tweets then stopped – as I wasn’t really answering the questions properly. I needed time to think, take a breath and decide what to do.</p><h3>The problem I had caused</h3><p>I had posted two different levels of role. A Front-end Engineer and a Lead Front-end engineer.</p><p>The Engineering department had posted one role level open – called ‘Software Engineer’.</p><p>The tweet was comparing the ‘Front-end Engineer’ to ‘Software Engineer’ and pointing out a huge pay discrepancy. A totally fair point except the comparison was incorrect.</p><p>I don’t blame anyone. It’s very easy to see why this was confusing.</p><h3>Why the comparison was not correct – but was understandable</h3><p>Front-end Engineer roles are actually grade E roles – junior to mid level. The Software Engineer roles are grade D – a mid to senior level.</p><p>The correct comparison would have been the Lead Front-end Engineer and Software Engineer. Both grade D with almost identical pay. There is no pay discrepancy there.</p><p>I completely understand why this is confusing. Why aren’t things named similarly? Why didn’t you check what other roles were open before you put them live? Trust me – I’ve asked myself all these questions.</p><p>I was a Front-end dev for years and never understood why it was not valued as highly as engineering in the past. I am glad we’re past all that these days and I’m glad to work at a place that values everyone’s skills equally.</p><p>That’s why I’m taking the time to write this down.</p><p>I care about what happened. Sometimes organisational, historical context and simple oversight can happen – and it’s best to learn from it.</p><h3>What went wrong?</h3><p>What I began to realise as the day wore on was that a lot of small differences in the adverts and the way our departments are organised had built up to create a huge looking problem.</p><h3>I was trying to target my adverts</h3><p>Engineering have a lot of roles open all the time – so they have a generic advert. It makes sense. The advert is always live waiting for applications. Not having this would cause a lot of extra work for them.</p><p>That works for them.</p><p>I’ve never had much luck with generic adverts in the past. Maybe I’ve written them badly. I’m not sure. I thought I’d try to target my adverts. I’ve had feedback in the past that people want to know what they’ll be working on. That meant creating adverts targeted to the team they’d be on and the role level.</p><h3>The structure of design and engineering is different</h3><p>Here’s a thing we need to tackle internally. Front-end falls under design at Co-op Engineering is a different area run by different people. There’s reasons for this – and it’s contextual to our organisation.</p><p>The reality is that once someone works here all divisions between job titles fall away.</p><h3>What we do need to do is rationalise our job titles</h3><p>In Engineering there is no Lead. Just a sliding scale from mid to senior. All with the same title. In Design we have ‘Designer’, ‘Lead Designer’, and ‘Principal Designer’ (me). People have different specialisms within that like User researcher or Front-end engineer’. The reason for that is that we want everyone to have some knowledge, appreciation and maybe do a bit of – each thing.</p><p>Front-end is in design because they are in many ways the closest link to the product and the customer so it is hugely important (in my opinion) that they have a user centred approach. Not that software engineers don’t by the way – it’s just a bit different.</p><h3>There was not prefix on the Front-end engineer advert</h3><p>Rightly that meant that the Front-end engineer advert looked comparable to the Software engineering advert.</p><h3>I didn’t look what other jobs were advertised</h3><p>Had I done that. I might have spotted what the rest of Twitter had. That – comparatively – looked bad.</p><h3>I live and learn</h3><p>Things like this make you better. They make you want to be better.</p><p>I hope this blog post goes some way to explaining what happened.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e48fe1e451" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m a Principal Designer – what do I do?]]></title>
            <link>https://matttyas.medium.com/im-a-principal-designer-what-do-i-do-137be7009428?source=rss-34cea8622334------2</link>
            <guid isPermaLink="false">https://medium.com/p/137be7009428</guid>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[principal-designer]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[Matt Tyas]]></dc:creator>
            <pubDate>Mon, 13 Jan 2020 22:17:12 GMT</pubDate>
            <atom:updated>2020-01-14T10:24:35.336Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m a Principal Designer at Co-op digital.</p><p>I work in the web platform team. Our mission is to create a consistent web experience for both users of the platform (digital teams and content publishers) and give Co-op customers a seamless user centred experience online.</p><p>As a new year started we had 2 team days to reset our vision, team goals and revisit things like our ways of working.</p><p>Toward the end of the second day we had a session on roles and responsibilities where each member of the team wrote down what they did. Then the group was asked to explain what that person did before they themselves stuck the post-its and explained them.</p><p>When it came to me there were some answers – but more silence.</p><p>At that moment I got a bit worried.</p><p>Am I not contributing as I should? Is the work I do not actually helpful to the team and our goals?</p><p>Luckily someone pointed something very helpful out to me.</p><p>To paraphrase, “you have a more behind the scenes role now, more enabling – so we don’t always see what you do”.</p><p>In that moment another blog post formed.</p><h3>What does a Principal designer do?</h3><p>The image below is what I wrote on the day as the answer to what I do.</p><figure><img alt="The post-it notes I wrote to explain what i do as a Principal Designer" src="https://cdn-images-1.medium.com/max/1024/1*SZo0PfsBE43NXs2kEK52ag@2x.jpeg" /></figure><p>Let’s break each post-it down.</p><h3>Clearly repeat why we’re doing this work</h3><p>Clearly – because it’s my job to help our stakeholders and the rest of digital understand why this is the right thing for our users. Sometimes that’s slides, blog posts like this one or generally telling people in the street how great we are.</p><p>Seriously – this is important. Especially the repeat bit. It’s easy to loose sight of good work and the context that work was delivered in. Repetition is a well worn propaganda technique. Propaganda is not always bad.</p><h3>Make sure user and business needs are met across products on the platform.</h3><p>I help to ensure we’re doing the right work for the right reasons by asking:</p><ul><li>does this solve a user’s problem?</li><li>does it align to our strategy and that of the wider Co-op?</li><li>is it helping the business deliver something (within the bounds of the first 2) in a cost effective and iterative way?</li><li>is this actually being designed and built in a best practice, scalable and flexible way?</li></ul><p>If it isn’t – it’s my job to question why, and give evidence as to why we should do something differently.</p><p>Let’s get real though – if you have any kind of job – you’ll know that’s not what always happens. That doesn’t mean we should stop trying. See: repetition.</p><h3>Understanding what our users say and do</h3><p>It’s important I know what our users think of our services through face to face, remote usability research and our analytics. If I’m asked about how people use and want to use our service. I should know the answer.</p><p>If I don’t. I’ll be honest and try to find out. There’s a pretty cracking team around me who will know.</p><h3>I help to form the strategy and vision of the web platform</h3><p>As with everything here, I’m not the only one involved in these things. I help to set a direction along with our head of online, product manager and others. We also get input from our whole team and secondary stakeholders like the head of digital and head of design.</p><p>We’re currently tweaking our strategy which is something I’m excited to talk about the detail of in a future post.</p><h3>I facilitate workshops, project kick-offs and weekly design critiques (crits) — and encourage others to do it too</h3><p>I’ve split these activities up as I tend to see them slightly differently.</p><p>Workshops can take many forms and consist of a range of design related activities with aim of trying generate ideas to solve a problem. These ideas can then be researched. Often the people invited are subject matter experts in a totally different area to ours and may not feel comfortable identifying as having design skills. I can then tailor activities to help generate ideas without making people feel out of their depth.</p><p>Kick-offs happen at the beginning of a piece of work. They’re about a group of people getting a shared understanding of particular problem we’re trying to solve and the boundaries in which we are going to try to solve it.</p><p>“We have learnt that users want to do X so we’re going to build Y. But we have technical limitation Z”.</p><p>Design crits give the whole team the opportunity to feedback on whether they think the solutions put forward are best to achieve the goals we’ve set. <a href="https://digitalblog.coop.co.uk/2018/03/28/how-to-run-a-design-crit-and-why-theyre-important/">It’s and open safe space that has rules</a>. Everyone’s opinion is important and useful and is an important activity for any multidisciplinary team.</p><p>Equally these are not things I exclusively should run. If someone else is better placed or just wants to get experience they should do it and I will help them if they need it.</p><p>Which leads me too…</p><h3>Line management, mentoring and pairing</h3><p>Each Principal designer covers a specialism in design – interaction design, user research, content design and front-end – my area. A principal must have a good grasp of all these disciplines.</p><p>It’s matrix management so I manage the permanent front-end colleagues and contractors across digital but within my project team I’m responsible for all the disciplines in design.</p><p>Line management is hard and every book you read tells you it is something few people take too naturally. I certainly didn’t – but I think I’m getting there.</p><p>I can’t tell you what it is and it isn’t. I’m still finding out for myself as each new person has different needs and goals I try to help them with. For me that’s the key. Find out what they want now and for the future. Find out what makes them happiest at work and attempt to create the conditions where they have that.</p><p>Mentoring is part of line management but I pull it out because it’s a big part of what I do every day within the web platform team. It tends to be quick conversations about direction or to sense check something.</p><p>I used to find managing people really hard and it made me super anxious.</p><p>These days I actually enjoy it.</p><p>I literally never thought I’d say that.</p><h3>I am responsible for the front-end discipline</h3><p>At the moment this is the hardest bit of the job.</p><p>Keeping up to date when you’re not in the code everyday is hard. Side projects help – but working on the same stack as the team is more important. It’s not just to feel on a similar level. Actually it’s more about understanding the challenges people might face with our set-up and being able to usefully input in technical discussions.</p><p>Plus it’s fun and pretty therapeutic just building something once in a while.</p><p>To be honest the same can be said for design – although most of the design I do now are sketches to quickly get ideas across when mentoring.</p><p>I also:</p><ul><li>I try to recruit the (not hire) the right people into the right teams with the right skills</li><li>run the front-end community of practice</li><li>help to set the direction of our shared front-end tools</li></ul><p>There’s enough to say in these three bullets that they may warrant their own blog post at some point in the future.</p><h3>In summary</h3><p>It really is a lot of activities around ‘the work’ whilst also doing a bit of the work as well.</p><p>Ultimately my goal is that either my direct product team or those I manage have the safety, freedom and back-up they need to do their job to their full potential.</p><p>It’s a tough gig – but I wouldn’t have it any other way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=137be7009428" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writing is for clever people with thoughtful opinions — not silly people like me]]></title>
            <link>https://matttyas.medium.com/writing-is-for-clever-people-with-thoughtful-opinions-not-silly-people-like-me-806974d7e7b1?source=rss-34cea8622334------2</link>
            <guid isPermaLink="false">https://medium.com/p/806974d7e7b1</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Matt Tyas]]></dc:creator>
            <pubDate>Mon, 06 Jan 2020 10:58:23 GMT</pubDate>
            <atom:updated>2020-01-06T18:45:32.493Z</atom:updated>
            <content:encoded><![CDATA[<h3>Writing is for clever people with thoughtful opinions — not silly people like me</h3><p>That’s a crap title. Or maybe it’s a good title? I don’t know. Already, I want to give up.</p><p>It’s hard to writing things down.</p><p>Especially if you’re surrounded by peers who do an excellent job of writing. That’s really intimidating.</p><p>Especially when you’ve been treading water professionally for a year or so. I have no real excuse, I have a daughter now — but I was never that prolific at writing before then — let’s be honest.</p><p>Especially when you’re an anxious person underneath it. If you know me personally — don’t laugh — it’s true :)</p><p>I’m the joker. That’s how I cover the anxiety up. It means maybe when I have something serious to say it has less impact because I’ve set myself up as this fun loving character.</p><p>I feel like I have nothing to add to the conversation. No real insight or revelation that will change the way anyone thinks about designing or building a product or service and most things I think to write about have already been done. This topic in-itself is exactly that — the ‘writing about how you can’t write’ blog post. Immediately has sent my inner monologue into “shut-up Matthew — nobody cares” overdrive.</p><p>I also write really long sentences sometime and I think Content Designers will tut under their breath at me.</p><p>All these things have made me stagnate a bit over the last year or so. A busy home life has given me the perfect opportunity to ignore writing and thinking. I know I can. I have done it now and again. I can tell a good tale, I can stand up and talk in front of people as well.</p><p>I do manage sometimes especially on the <a href="https://digitalblog.coop.co.uk/author/mtyascoop/">Co-op digital blog</a>, but it’s different — it’s not thought so much, or interesting opinion. It’s just what we’ve done.</p><p>I want to do more thinking and opinioning (opinioning?!). I think writing whatever’s there in my head down will help me face this fear of not knowing what to write about.</p><p>I’ve just tapped this out on my phone.</p><p>It only took a few minutes — and it’s a start.</p><p>It’s not felt healthy for me to have unused thoughts rattling round in my brain. So I will begin in some small way to write them down.</p><h3>I’m going to try to write a blog post a month in 2020</h3><p>This probably seems really over the top when all I want to do is write 12 blog posts. However I get bored quickly and find it very easy to dart to the next thing. So this will be a challenge for me.</p><p>Coupled with the problems of writing I have above. It will be an easy one for me to give up on.</p><p>I’d like to build a useful habit and break down my own insecurity by facing up to my fear of putting my thoughts down.</p><h3>This is not a New Years resolution</h3><p>I’m going to be kind to myself. A resolution sets me up to fail. So with that in mind I’m doing this on my terms that I can refer back to if it begins to get me down.</p><ol><li>The last thing I need is more stuff to do — this has to feel useful or I will stop — and that’s okay.</li><li>I am not in competition with anyone else.</li><li>I’m not going to get angry at myself if I don’t manage to keep the quality up or some of my sentences are a bit long.</li><li>It’s fine to write and publish on my phone — it needs to be easy or I won’t do it</li></ol><p>I will try to write a blog post a month in 2020.</p><p>I will try to write a blog post a month in 2020.</p><p>I will try to write a blog post a month in 2020.</p><p>Consider January ticked off.</p><p>Also — the Candyman just appeared.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=806974d7e7b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Balance]]></title>
            <link>https://matttyas.medium.com/balance-b14631d201d3?source=rss-34cea8622334------2</link>
            <guid isPermaLink="false">https://medium.com/p/b14631d201d3</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Matt Tyas]]></dc:creator>
            <pubDate>Tue, 11 Oct 2016 07:18:32 GMT</pubDate>
            <atom:updated>2016-10-25T15:31:46.364Z</atom:updated>
            <content:encoded><![CDATA[<p>The universe hands out balance pretty rarely. Although, and this is the important bit - that rarity is based on your personal perspective.</p><p>We live on Earth. A planet that to us, has balance. Sat in the ‘Goldilocks zone’, we live in that that lovely area where everything is just right. Just right for life (as we know it) to form and ultimately allow me to write, and you dear reader, to read.</p><p>When I was a kid there was this bit in E.T. that always struck me. A bit of interaction you rarely see when one world meets the next. When E.T. first meets Elliot, he (the supposed alien) is scared. Elliot is not part of E.T’s goldilocks zone, so E.T, shrieks in fright just as loud as the human boy.</p><p>If we are E.T. and Elliot is our stakeholder (we sometimes come from what seem to be other worlds) then the service we are designing is something else again. It inhabits it’s own goldilocks zone with a Venn diagram of external forces acting on it that in some cases can resemble a Spirograph (another 80s reference…) a series of interlinking spheres of influence some that are more important, some less, than others. Users, politics, technology, fact, opinion, money, time, ego (I’m sure you can think of some more) all play a factor and all, might to a greater or lesser extent be important to your service’s Goldilocks zone. We all know which ones we want to entertain, but all MUST be tackled — at least in part.</p><p>Design (I told you to bare with me) is about balance. That balance sometimes comes by tackling issues you might not think are in your realm to tackle but these, may be the ones to go for. That doesn’t mean going head on to your next meeting and telling people they’re wrong left right and centre. It means that the goldilocks zone of your service might need pulling a little more away from one circle and closer to the next. What’s in each external factor’s Goldilocks zone, how does it relate to your service’s goldilocks zone and most importantly the zone of your users? This is a fancy way of saying you should use empathy — empathy for everything.</p><p>You are not alone though. The idea of facing all these external pressures seems hard. But for all the circles pulling away there are often more pushing in. You are not E.T. stranded on a distant world. You have allies everywhere. You might not know it (you might not know that they’re your allies at all yet) but these other E.T’s can help you nudge your service towards it’s very own Goldilocks zone.</p><p>Unlike the Earth (that is at the mercy of the external factors that have dealt it it’s hand) you can adapt you can empathise and with that help others get the right amount of what they need into your service.</p><p>In turn, they’ll empower you and you’ll feel confident to push away when you need too and you’ll know which E.T. to ask for help next time. Talk to the other E.Ts, see what makes them tick.</p><p>What am I saying with all these metaphors and 80s references? Listen, listen to everything and everyone even if you don’t think it is important, someone else does. Then, do your best to filter it down into something that fits your users needs.</p><p>Should have just written that paragraph shouldn’t I?</p><p>Matt</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b14631d201d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>