<?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 Jordan Moore on Medium]]></title>
        <description><![CDATA[Stories by Jordan Moore on Medium]]></description>
        <link>https://medium.com/@jordanmoore?source=rss-519cd1c351d7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1onv3p0Z3M5dBhGuAuGFiw.png</url>
            <title>Stories by Jordan Moore on Medium</title>
            <link>https://medium.com/@jordanmoore?source=rss-519cd1c351d7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:03:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jordanmoore/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[Working Backwards from Magic]]></title>
            <link>https://medium.com/dawsonandrews/working-backwards-from-magic-7c4c3b60aaa8?source=rss-519cd1c351d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c4c3b60aaa8</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jordan Moore]]></dc:creator>
            <pubDate>Tue, 20 Sep 2022 16:24:46 GMT</pubDate>
            <atom:updated>2022-09-21T08:52:09.021Z</atom:updated>
            <content:encoded><![CDATA[<p>As an industry (and I’d perhaps extend this towards society as a whole) I believe that we are sleepwalking into a level of comfort where big, bold, radical thinking has made way for safe, tried and tested systems and processes that produce reliably similar results and more of what the world already has. The industry seems as though it is short on new ideas and bravery, and big on conventional thinking and mass-producing more of the same. It’s tilting towards anti-progress. It is my hope that working backwards from magic is the pushback against this mode of thinking.</p><h4>What is Working Backwards from Magic?</h4><p>Put simply: working backwards from magic is an approach to creative problems by using the suspension of belief and any limiting factors to unlock new value.</p><p>It is a tool that can be turned towards design and development problems, product ideas and/or improvements, essentially anything that would benefit from thinking from new directions and perspectives. It’s an incredibly simple process to describe and, in my opinion, easier to apply than the prescribed templates of conventional creative processes and approaches.</p><h4>Step 1: Identify the Problem</h4><p>In order to know where we’re going, we need to understand the problem we’re trying to solve. How deeply you understand it doesn’t necessarily matter, this is more about having something to aim at rather than nothing.</p><h4>Step 2: Remove all limitations</h4><p>Leave conventional thinking at the door. It’s of no use to us in this process. Removes all limitations from the problem, all assumptions, all technical restrictions, all preconceived notions and concepts, get all of that out of the way and start from this point because by default, you’re making something new and therefore more valuable. What you won’t want to do is see how others are solving the problem — this gets you back into conventional thinking and solving problems with existing solutions.</p><p>Let’s look at the problem Uber were faced with. It didn’t require any deeper definition other than “how do we get people from A to B?”</p><p>If Uber looked at what everyone else was doing (reasoning by analogy/conventional thinking using preexisting ideas) they would just have a shinier interface on top of a regular taxi firm website offering a contact form and/or a phone number to call a taxi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*emz8QHG8ZMTAiKOht6Gajw.jpeg" /></figure><p>Instead, Uber decided to work backwards from magic and started from impossible. How could you get someone from A to B if this worked like magic? “Teleportation!” Obviously that’s not doable, yet at least, so if not teleportation then what? You would have a personal driver to take you from A to B. You wouldn’t need to be somewhere in particular, this service would know where you are, and you would know how long it would be until your driver gets here — etc etc, and so Uber is born.</p><p>By moving all of the limitations out of the way (current understanding of how taxis work, technical limitations, society’s expectations of what a taxi does), Uber was able to create something new and of significantly greater value than the existing solutions to the problem.</p><p><strong>The world is full of secrets like this left to discover.</strong> We’re lucky we are in software because most of the hardware secrets have been discovered. The web is just getting started and there are millions of life-changing ideas in waiting.</p><h4>Step 3: Introduce Reality and Meet Magic in the Middle</h4><p>As we’ve just discussed in the Uber example, it’s not enough to start from magic and leave it at that. There is a need to get real which involves remaining disciplined about keeping conventional thinking at arm’s length.</p><p>Working backwards from magic requires you to start from impossible and slowly introduce just enough reality until your solution is as close to magic as possible.</p><p>Before Apple took over the world, the old saying was “nobody gets fired for choosing IBM”. Risk-averse people and conformists get left for dust in the long run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*vcADTeAssViyeL63yjb7sw@2x.jpeg" /><figcaption>A young Steve Jobs sticking the middle finger up to conventional thinking</figcaption></figure><h4>Conventional Thinking vs Working Backwards From Magic</h4><p>My intention isn’t to encourage a complete rejection of conventional thinking altogether. Tried and tested solutions have their time and place, but at a time where design is self-commoditising in software I can’t help but feel that the industry is declaring “mission complete” and systemising too soon.</p><p>Conventional thinking in digital design adopts the generic process of discovery through to completion by passing through all the usual stops along the way: user stories, competitive analysis, personas, wireframes and so on. Such processes are rapidly becoming checklists, or worse — ass-covering exercises so that the designer can blame the process if their work doesn’t quite return on the investment.</p><p>The issue with conventional thinking is that it often involves an abundance of rules and processes that rarely produce the insanely valuable outcomes. The possibility space is artificially limited from the start. Ideas that create companies like Uber are left for other daring adventurers and the conventional thinker can only watch from the sidelines and wait for ideas to become mainstream before integrating them.</p><p>Working backwards from magic starts from a completely different and grander possibility space. It begins with the simple question:</p><blockquote>“if this worked like magic, what would that look like?”</blockquote><h4>“It’ll never work”</h4><p>For this approach to work, it needs to live in a culture that is open to risk, making mistakes, and learning from failure quickly. We are taught from an early age that mistakes are bad and that learning to repeat answers from books is how to progress in life — in essence: do what everybody else is doing, DON’T think different. I can’t help but think that this leads to the type of ass-covering through a plethora of rules, conventions and processes that have become the norm in creative work.</p><p>I have found that, in my experience, working backwards from magic democratises design more than existing approaches which seem to revel in the authority of a UX leader type bringing the timid, naive client and others through the dangerous world of design. In contrast, asking a client “if this worked like magic, what would that look like?” brings them to the table without the need to jump through hoops, or worry about saying the right technical terms or have concerns about whether something can or can’t be achieved.</p><p>I have also started to become comfortable with the idea that “it’ll never work” is a good indication that I’m on the right track towards creating new value. “It’ll never work” simply means that it doesn’t exist (yet) and you’re firmly in working backwards from magic territory. Your possibility space is infinitely bigger.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c4c3b60aaa8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dawsonandrews/working-backwards-from-magic-7c4c3b60aaa8">Working Backwards from Magic</a> was originally published in <a href="https://medium.com/dawsonandrews">Dawson Andrews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Craft CMS vs WordPress: a side-by-side review]]></title>
            <link>https://medium.com/dawsonandrews/when-we-engage-with-new-clients-one-of-the-common-themes-during-early-conversations-is-choosing-4e1be3be3acd?source=rss-519cd1c351d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e1be3be3acd</guid>
            <category><![CDATA[craft]]></category>
            <category><![CDATA[craft-cms]]></category>
            <category><![CDATA[content-management]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[cms]]></category>
            <dc:creator><![CDATA[Jordan Moore]]></dc:creator>
            <pubDate>Fri, 26 Jun 2020 11:13:02 GMT</pubDate>
            <atom:updated>2020-06-26T11:18:40.496Z</atom:updated>
            <content:encoded><![CDATA[<p>When we engage with new clients, one of the common themes during early conversations is choosing the right content management system (CMS) for the project — and with good reason. A content management system is the bridge between our code and our client, and therefore the bridge between our client and their customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cw3BAVh4umHGqEBVFKwSHQ.png" /><figcaption>The underlying chain in every digital project</figcaption></figure><p>A bad CMS can compromise this chain at any point, even from the very beginning, for example, it may impose stringent coding or design restrictions which then affects our client’s ability to give their customers what they want which affects the customer experience.</p><p>It’s no understatement to say that choosing a CMS is one of the most important decisions in a digital project.</p><p>In this article, we’re going to walk through the key requirements of a modern content management system by comparing two of the biggest names in this space: WordPress and <a href="https://craftcms.com/">Craft CMS</a>.</p><h3>What is a CMS?</h3><p>To begin, we should answer the obvious question: “<strong>What is a CMS?</strong>”</p><p>A content management system is a tool for creating, editing, and managing digital content such as publishing pages, articles, site structures, as well as digital media including images and videos. Content is published through the CMS interface so users can access it through web pages and/or apps.</p><p>The CMS market is crowded with a lot of choice including the recent rise of headless content management systems like Contentful and Prismic (back-end only systems delivering structured content via a RESTful API). To make sense of this crowded market, you will need to consider a CMS product with <strong>longevity</strong> and <strong>cadence</strong>, that is to say how long it has been in existence which will demonstrate experience and trust amongst its users, and how frequently it is updated and maintained which will demonstrate how secure the platform is and whether you will find support should you encounter issues.</p><p>With that in mind, Craft CMS and WordPress meets both of our key criteria.</p><h3>Background</h3><p><strong>WordPress</strong> is the world’s most popular tool for publishing blogs and has added content management capabilities over time to become a CMS. With that comes a lot of legacy baggage where WordPress tries to be all things to all people including hobbyists, bloggers, and people who trust it as a more fully-fledged CMS. This baggage mainly manifests in the busy user interface, arcane plugin ecosystem and performance issues from a back-end and front-end experience.</p><p><strong>Craft CMS</strong> is a commercial content management system including premium brands such as Netflix, Apple and Microsoft. It is by far the younger of the two systems, however it still has many years under its belt. It is developed and maintained by a team of developers and an active open-source community. Where WordPress tends to rely on themes for designers and developers to get started, Craft provides a blank canvas so user experiences are built from the ground up(see the Flexibility for more details).</p><h3>Security</h3><p>WordPress the more widely used CMS of the two competitors, which is part of the reason it is a target for frequent attacks, and because many WordPress sites run poorly maintained plugins leaving a door wide open for attackers to gain access.</p><p>This security concern isn’t something to be taken lightly. In 2016, the Panama Papers breach that saw approximately 2.6 terabytes of data (somewhere in the region of 11.5 million files) was leaked from Mossack Fonesca, the Panama-based law firm, all because of a vulnerability in a WordPress plugin called Revolution Slider — a plugin to display a carousel of images. WordPress relies on plugins like Revolution Slider to achieve core functionality available in other content management systems such as Craft.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_s94w2667b6Zcue_.jpg" /></figure><p>Craft CMS doesn’t have as wide an array of plugins as WordPress, mostly because it doesn’t need plugins to achieve either a) built-in functionality, and therefore, more secure or b) the desired functionality is achievable in code because Craft is more flexible and customisable from a development perspective.</p><p>One of our frustrations as a business is the feeling of dread when receiving an email from a hosting provider indicating that a security exploit has been identified on one of the plugins in a WordPress install. It is then a race against time to track down the site, log in, update the plugins (assuming there is an update, otherwise it’s a straight up removal of the plugin which potentially breaks functionality), then syncing the changes across all environments.</p><p>Thankfully, Craft CMS has no major exploits. The Craft Plugin Store is similar to Apple’s App Store in that they keep a close eye on plugins submitted to the store ensuring that the likelihood of any major security breach is low (particularlycompared to the 1,500+ documented exploits in WordPress).</p><p><strong>Winner: Craft CMS</strong></p><h3>SEO</h3><p>Wordpress is known for having one of the best SEO plugins in Yoast SEO, which has long given it an advantage in this category. Ask any content editor who has used WordPress in the past and the chances are they have used Yoast alongside it when publishing pages and sending links to social media.</p><p>However, Craft CMS has not just caught up in the SEO game, you could even argue that it has surpassed WordPress with its own elite SEO plugin, SEOmatic.</p><p>SEOmatic provides more than just common SEO tools, like alt attributes and link title attribute fields. It goes further to automatically render metadata and create sitemaps for Google, all while providing a range of advanced SEO options. SEOmatic strikes the balance between providing the ease of use of Yoast SEO but its advanced features give it the slight edge that even Moz.com, the go-to resource for SEO experts, enthusiastically uses Craft CMS and SEOmatic over WordPress and Yoast SEO.</p><p>SEOmatic provides the ability to automatically generate structured data/JSON-LD to ensure pages such as products, events, recipes, showtime listings, AMP pages, and any other content types that Google may pre-format in search result displays which has been proven to boost conversion rates for end-users.</p><p><strong>Winner: Draw</strong></p><h3>Speed and Performance</h3><p>If you recall the chain diagram from earlier, the speed and performance occurs at the code level which is where most content management systems impose their will on the design and developer behind the user experience at the end of the chain. The question is how much code is required from the CMS to function correctly and what is the performance impact?</p><p>WordPress is bloated from the core up. Especially once you start adding plugins to achieve the essential functionality you need on top of what it gives you out of the box. Craft CMS, on the other hand, has many of the desired functionality items out of the box that would otherwise require plugins in WordPress.</p><p>Moreover, in order to bypass limitations in the core product, a lot of the plugins popular WordPress plugins such as Jetpack, use extensive Javascript overrides to customise core behaviour. This adds bulk to each page load and puts pressure on users’ browsers. This adds considerable weight to a page and negatively impacts performance all before the developer has even had a chance to implement any of the design into the experience.</p><p>Craft on the other had is incredibly lightweight. It doesn’t come with legacy code libraries to appease the earlier users who intend to use it as a blog rather than a CMS, rather Craft gets out of the way for the developer. So much so that it is easy to use Craft as a headless CMS if necessary so that only structured data is loaded into the page rather than any expensive PHP or database calls.</p><p><strong>Winner: Craft CMS</strong></p><h3>Design and Development Flexibility</h3><p>Which brings us on to the next key requirement. Although this sounds more like a concern at the code side of the chain, it ultimately affects the user at the other end most of all.</p><p>WordPress was built as a blogging platform, and in that area, it excels. However, when it comes to designing unique pages, ambitious and immersive experiences, WordPress falls very short of the mark. Sure, you technically can achieve some degree of unique and ambitions design in WordPress but it usually involves complex workarounds, manual hard-coding of pages directly from the admin panel, and other hacks — all of which adds up to expensive resources in all definitions of the word — design time, development time, the content administrator’s time, support time, and page performance. Employing such workarounds also introduces design and code fragility meaning people usually become adverse to making any necessary changes or potential improvements in case it all comes crumbling down.</p><p>WordPress has been described as “like starting with a Pollock painting and applying paint remover until you have something you can draw on, instead of just starting with a blank sheet of paper in the first place”. WordPress imposes code and design bloat out of the box rather than Craft’s blank sheet of paper where you start with the user and business needs.</p><p>Craft CMS has no design restrictions. It doesn’t impose its way of doing things on top of you. There is no such thing as the Craft CMS equivalent of “site that looks like a WordPress site”. It’s easy to see why two of the industry leaders in immersive user experiences, Netflix and Nike, have chosen Craft as their CMS of choice. It buys them the creative freedom to design and build something unique and engaging for users whilst being easy to use and flexible for content administrators to publish those experiences to their audience.</p><p><strong>Winner: Craft CMS</strong></p><h3>Ease of Use for Content Administrators</h3><p>WordPress certainly enjoys some familiarity among content administrators and marketing teams who have had previous exposure to the CMS, and anecdotally speaking, we’ve noticed some client’s reluctance to replatform to Craft and other content management systems as a result.</p><p>However, the good news is, Craft’s user interface and functionality is almost like-for-like with WordPress with the only immediate notable difference being that Craft’s interface is easier to use and navigate than WordPress. We have several of our clients who were former WordPress users who now use Craft CMS and found it far easier to use — some of which picked it up so quickly that they didn’t need our training!</p><p>It has been described by some of our customers as “WordPress with a major design upgrade”, or “a more modern, easier to use WordPress”. Craft CMS has unlocked marketing teams potential allowing them to easily share pages and posts on social media, run effective campaigns and boost user engagement and conversion rates.</p><p>Although that on first glance both the WordPress and Craft CMS admin panels look identical and function the same, Craft CMS does a better job of simplifying the interface and administrative tasks, showing relevant information for content and marketing teams such as page performance, user engagement and campaign success, as well as being built for speed and performance from the backend to frontend.</p><p>Craft has a built-in <strong>Live Preview</strong> feature so content editors can see the content change in realtime as they type. In this safe draft mode, it means they can test things like content length, layout and media before they publish the page to the public. WordPress has a preview function also, but it doesn’t work in realtime and requires the editor to stop working, generate a preview URL (which usually takes some time) and then review.</p><p>One of the most powerful features of Craft CMS from a content administrator’s perspective is the ability to save draft versions of pages and send them to other members of their team for sign-off before publishing to the public. The great thing about these sign-off URLs is that they are unique links that can be viewed privately without the need to log into the CMS.</p><p>There are many other features we could mention to make marketing team’s lives easier, but we’ll end this section on one of the common complaints of many content management systems: <strong>image editing</strong>.</p><p>If you have any past experience of working with a CMS, you have probably experienced the pain of uploading images fit for purpose for the end-user. Sometimes this will likely have involved you having to stick to stringent image dimensions, file types and optimisations — you may have even had to pick up some new Photoshop skills along the way to make that happen. Thankfully, Craft CMS handles all of this automatically.</p><p>Craft CMS can be set up to handle automatic image resizing, cropping (with a focal point tool to make sure nobody loses a head when automatic cropping happens!), and optimisation to make sure pages stay performant and lightweight for users. You can still manually crop if you wish, and as we mentioned before with the Live Preview feature, you’ll be able to see what things look like before they go live.</p><p><strong>Winner: Craft CMS</strong></p><h3>Multiple Sites and Multiple Languages</h3><p>It is becoming increasingly common for digital experiences to have multiple domains and subdomains managed from the same content management system. Some may even choose to manage iPhone and Android app content from the same content management system.</p><p>Craft CMS has multi-site capabilities by default out of the box, once again without the need to add any additional plugins. It assumes your current site is site 1 of of many even if you only ever choose to have one site.</p><p>You might choose to have a multi-site setup if you want to have a website as a section within your CMS and an accompanying app as a separate section — you might even want to have a mixture of shared and unique content for each. Or you might potentially want to have multiple languages on multiple domains but powered by one CMS cleanly categorised by language. In any of these scenarios, you may want to grant access for all content editors, or maybe only show them relevant parts of the overall CMS — whatever the setup, Craft is flexible and will scale its security, performance, users and permissions levels accordingly.</p><p>WordPress, as you might have guessed by now, requires additional plugins to achieve something similar. It doesn’t have the clean user permissions view that Craft gives you where you can easily see who can access what part of the CMS. WordPress users will need to be duplicated across different sites, account details recreated, and of course, new passwords generated and changed.</p><p><strong>Winner: Craft CMS</strong></p><h3>Price</h3><p>This can often be a stumbling block if we’re trying to convince a client to move to Craft CMS. WordPress is free — it’s used by 30% of websites on the web and is a great way for people to get started with a web presence, however, we have found that the old saying of “You get what you pay for” holds true in this area.</p><p>A Craft CMS licence costs $299 which includes one year of updates, then $59 per year for updates after that. The difficulty is trying to quantify the <strong>true cost of WordPress</strong> considering that to achieve so many of Craft’s core features in WordPress requires additional development time, installing additional plugins — some of which may cost extra such as Jetpack at £250 per year, the time invested in fighting performance issues and stripping out bloated code, difficulty syncing between environments — all of which adds up to a cost that can be hard to calculate, and that’s assuming there are no security issues and exploits to deal with along the way.</p><p>It’s worth noting that when compared to other enterprise-level CMS platforms such as Adobe Experience Manager(anywhere from $250,000 to $1,000,000), Craft’s offering seems a lot more reasonable. A followup question might be,“Why is Craft so cheap compared to Adobe Experience Manager?” You have to consider Craft’s market position to answer that question — where WordPress tries to be all things to all people at its free price point, and AEM prices itself at an enterprise level, Craft positions itself out of the hobbyist market of WordPress and leaves the door open for businesses and enterprise at this price point.</p><p>On paper, WordPress wins in the price category, but in practice it’s not as easy as pointing to each platform’s pricing page and assuming that what you see is what you get. There is certainly a hidden cost below the surface with WordPress which is worth considering when taking price into consideration.</p><p><strong>Winner: Draw</strong></p><h3>Support</h3><p>Because of its popularity, WordPress has amassed a large user base with a large amount of plugin developers looking to capitalise on its market share. This means that WordPress has a large community support network where questions will be answered quickly, and there are rarely any scenarios that haven’t been encountered by a developer or content administrator before.</p><p>Craft on the other hand has a smaller, but very active community on live forums like Discord and Slack. One of the benefits of Craft’s price tag is the fact that you will have access to support direct from the development team if you should come across any bugs or the need for general help and support.</p><p>Again, this is a category that could go either way, but due to WordPress being in the game a lot longer than Craft, by that measure it has accumulated copious amounts of Google searches with help questions down the years so there are very few situations where a problem is encountered without an answer a Google search away.</p><p><strong>Winner: WordPress</strong></p><h3>Conclusion</h3><p>Choosing a CMS is a massive decision that shouldn’t be taken lightly. As we can see, it is a decision that has a direct impact on the 3 parties involved with any digital project: the agency, the client, and the customers.</p><p>Users demand more from a modern digital experience. Their expectations are higher than ever. They expect Netflix to make the decision for them as to what series they should binge watch next, they expect Spotify to introduce them to new genres and artists, they expect rich, fulfilling digital experiences that make a lasting impression.</p><p>With WordPress, we believe it is stuck in the digital past and walking a difficult line between catering for the hobbyist bloggers who elevated the platform to where it is today, and companies who have adopted it as a means of getting on the web with customisable themes.</p><p>But that just doesn’t cut it for the modern user. With conversion rates affected by each millisecond of a page load, the modern content management system needs to prioritise performance <strong>and</strong> empower agencies and content editors alike to create awe-inspiring digital experiences to engage and retain the attention of the modern user.</p><p>That’s why we choose Craft. It is a fit for the ambitious organisations we work with who come with a passionate user base who demand and deserve world-class digital experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e1be3be3acd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dawsonandrews/when-we-engage-with-new-clients-one-of-the-common-themes-during-early-conversations-is-choosing-4e1be3be3acd">Craft CMS vs WordPress: a side-by-side review</a> was originally published in <a href="https://medium.com/dawsonandrews">Dawson Andrews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intentional and Emergent Design Systems II]]></title>
            <link>https://medium.com/dawsonandrews/intentional-and-emergent-design-systems-ii-9ef59a1d0e1b?source=rss-519cd1c351d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ef59a1d0e1b</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[css]]></category>
            <dc:creator><![CDATA[Jordan Moore]]></dc:creator>
            <pubDate>Mon, 10 Feb 2020 14:58:44 GMT</pubDate>
            <atom:updated>2020-02-10T21:28:05.956Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iH8AGgwF-gM315ZnifBpJQ.jpeg" /></figure><p>I believe Robin Rendle’s <a href="https://www.robinrendle.com/essays/systems-mistakes-and-the-sea">Systems, Mistakes, and the Sea</a> was a catalyst for several enjoyable articles on design systems since the beginning of the year. Notably Jeremy Keith’s <a href="https://adactio.com/journal/16342">Web standards, dictionaries, and design systems</a>, Frank Chimero’s <a href="https://frankchimero.com/blog/2020/gardening-vs-architecture/">Gardening vs Architecture</a>, a subsequent, deeper dive in Jeremy’s <a href="https://adactio.com/journal/16369">Architects, gardeners, and design systems</a>, and Dave Rupert’s <a href="https://daverupert.com/2020/01/the-web-is-industrialized-and-i-helped-industrialize-it/">The Web is Industrialized and I helped industrialize it</a>.</p><p>What follows is a contribution to this discussion. I’m still unpacking it but it feels timely to push some thoughts out into the open whether they’re ready or not.</p><p>I believe that we are collectively tapping into something important within the design system discourse. Something felt, but difficult to uncover and put into words. However, it is gaining shape with some common themes around the role of humans and machines, order and chaos, industry and liberty.</p><p>I’m going to dive deeper into the conversation through the framing I believe helps me most by elaborating on <a href="http://jordanm.co.uk/2019/07/30/intentional-and-emergent-design-systems.html">Intentional and Emergent Design Systems</a>.</p><h3>Recapping Intentional and Emergent Design Systems</h3><p>It helps to read <a href="http://jordanm.co.uk/2019/07/30/intentional-and-emergent-design-systems.html">the original, short article first</a>, but as a brief summary:</p><p>Intentional design systems are the typical approach to building design systems: design system first → design/build solutions from the system, i.e intentionally designing a system regardless of the solution.</p><p>Emergent design systems start from solutions and work backwards to find emerging, reusable patterns for the system.</p><h3>The Reach &amp; Scope of Design Systems</h3><p>As far as I am aware, there is no collective understanding of the desirable reach of a design system. The intentional camp believes that everything must come from the system. By default, the system permeates the entire product.</p><p>In an intentional design system, there is no room for chaos. Only order. If something doesn’t fit the system it doesn’t belong in the system. If something cannot be born out of the system, it will not belong in the system. Intentional systems are authoritarian by nature.</p><p>Their liberal counterpart, the emergent design system, begins with creativity and chaos deriving patterns for the system later. Decisions start from user outcomes (the sum of all parts) and work backwards to find reusable parts. It’s hard to quantify the reach of emergent systems. It may cover a small amount of the product, and it may cover a lot of the product. It’s not all-encompassing. There is likely a correlation between the number of unique user problems encountered and the overall coverage of the system.</p><p>The scope of an intentional design system is large by default and requires some degree of conjectural bloat (code for scenarios that have yet to occur). When components are front-loaded into the process you get wastage as a byproduct. Guesswork and assumptions are part of the product’s DNA. I don’t blame anyone in thinking that this approach is the sensible direction. We’ve been conditioned to believe the next new thing should come first in the chain of events, whether it’s mobile-first, content first, users first — when it comes to building products in design and code, you can be forgiven for adopting a design system first approach.</p><p>Although not a like-for-like comparison, it’s interesting to see that the same voices who would bemoan libraries such as jQuery and Bootstrap — two libraries full to the brim of conjectural bloat — haven’t noticed the hypocrisy in advocating for design system first approaches before building up to more complex components. The same voices who evangelise for accessibility damning jQuery for adverse effects on performance and page weight are happy to tax users for a speculative design system<a href="http://jordanm.co.uk/#fn:1">1</a>.</p><p>In contrast, emergent design systems require only accepting evidence-based patterns and components into its system. It flips everything on its head asking the parts to prove themselves to be replicable and have sufficient utility. They need <a href="https://frankchimero.com/blog/2020/gardening-vs-architecture/">the gardeners Frank Chimero alluded to</a>.</p><p>A useful lens for drawing that difficult line around the scope and reach of a design system might be around the value of tasks the UI components will provide to users. Low-value tasks (the type that provides limited utility such as a terms and conditions page) are perfect for design systems to do the heavy lifting — if not all of the lifting. High-value tasks (such as a search box on an e-commerce product) should require more human attention and deservedly so. Think of a pilot flying a plane full of passengers — the most critical (and therefore high-value) parts of a flight are: taxiing, takeoff, and landing. Autopilot can take care of the rest. You want your pilot at his or her sharpest for those key moments. Your design system is no different.</p><h3>The Sunk Cost Fallacy of Design Systems</h3><p>An intentional design system assumes that your design work is done. You can maintain it, of course, but making changes to the system becomes a bureaucratic process.</p><blockquote>We’ve industrialized design and are relegated to squeezing efficiencies out of it through our design systems. All CSS changes must now have a business value and user story ticket attached to it.</blockquote><blockquote>Dave Rupert — <a href="https://daverupert.com/2020/01/the-web-is-industrialized-and-i-helped-industrialize-it/">The Web is Industrialized and I helped industrialize it</a></blockquote><p>I remember coming up against design bureaucracy during my time working as part of a large scale product team. We were faced with many new user problems in need of solutions. The team were hellbent on shaping the solution to the problem out of the prebuilt pieces of the design system. Reasoning by analogy. The method of thinking rarely leads to new solutions for new problems. First-principles reasoning was deemed too expensive.</p><p>I was met with arguments like “That means we’re going to have to create a new rule for this component, we’ll have to get internal sign-off, the developers will have to invest extra effort, it’ll need to go through testing, do you seriously want to go through all those steps?”</p><p>It was clear that we had been designed into a corner by our design system or at least our organisation’s ideology. What if our initial assumptions were wrong? What if we didn’t have the pieces to address these new problems?</p><p>I noticed a pattern. If a problem could be easily solved, low-effort, low value, or if it had already been solved — defer to the system. Watch out for when the system pushes back. If the design system pushes back, it’s time for human intervention and invention.</p><p>Individuals commit the sunk cost fallacy when they continue a behaviour or endeavour as a result of previously invested resources (time, money or effort) (Arkes &amp; Blumer, 1985). The same is true for design systems that grow in scope beyond a team’s ability to become dynamic to the system and its user’s needs. Decisions are deferred to the system by default, and anything that requires the system to change is met with often insurmountable objections because of the time, money, and/or effort to change the system.</p><p>Useful questions to ask when the system pushes back:</p><ul><li>Do we need to amend the system?</li><li>Is it a unique case that should sit outside the system?</li><li>Is it likely to reoccur in different variations?</li><li>Is it something that should be governed by a design system?</li><li>Does the system bake in more assumptions than a different approach? (Occam’s Razor is a good guide for software decisions)</li><li>Does building the best thing involve building it out of the things we’ve already built? Or does it require building something new?</li></ul><p>You can tell what type of design system you’re working with if it biases solutions towards pre-existing components or if the system gives you the freedom to invent.</p><h3>Leaving Room for Creativity</h3><p>The majority of systems I hear people advocate for <em>appear</em> to subscribe to intentional design systems. Because of this, one of my overriding fears is that design systems are designing designers out of the picture. For years we’ve pushed against the idea of design as a commodity, yet here we are commoditising design down to atomic levels.</p><blockquote>“Sometimes you load up a show on Netflix or a song on Spotify and you can feel the algorithm in it.”</blockquote><blockquote>Frank Chimero — <a href="https://frankchimero.com/blog/2020/gardening-vs-architecture/">Gardening vs Architecture</a></blockquote><p>I used to poke fun at the websites of the early 2010s claiming to be “handcrafted”. Now I’m thinking they were on to something. Perhaps “handcrafted” was the wrong adjective, but I think they were trying to describe something else. Something made through more effort, deliberateness, craft, and creativity. These experiences placed more of an emphasis on the importance of aesthetics, they spoke to human ideals such as affordance, familiarity, and metaphor. Flat design lends itself towards low-effort commoditisation and malleability in a design system — perhaps leading to the ideology of “everything that can be systemised, will be systemised”.</p><p>There is a certain coldness in the algorithms. You can feel the algorithm in a rigid design system that spans every corner of a product. You don’t want a design system that feels “automated” — well, you might but your users certainly don’t. Your users would rather a product designed with care (dare I say, “handcrafted?”).</p><p>The benchmark must surely be what resonates with users — and if that is an amalgamation of predefined components and rules that must work because the system says so, then fine, so be it. I firmly believe that it makes much more sense to start from resonance and work backwards treating users first and systems second.</p><p>If I could give an artificial intelligence the keys to fully automating modern design, I’d point it towards an intentional design system. An emergent approach leaves room for mystery, chaos, intuition, creativity and expression — the unpredictable, unique, innately human elements.</p><p>Do design systems limit creativity? The answer rests on what type of system you subscribe to.</p><p>The worst incarnation of a design system designs designers out of the picture. If I were building an AI tool to displace designers, I’d point them towards an all-encompassing, intentional design system. I fear that we’re blindly running towards automation and we’re giving the algorithms the template our jobs. It’s not hard to imagine a world where No Code technology complements No Design. By contrast, the best incarnation of a design system leaves room for creativity, invention, the human elements.</p><p>And my argument is exactly that — we should safeguard the human elements of the design process. There will always be a need for human intervention, the kind of which requires a human eye to correct for optical alignment when the machines produce rounding errors, or perhaps it is our all too human flaws that produce the rounding errors, either way, the goal should be to prioritise people over rules, algorithms, and automation. Ultimately you want to design systems that liberate creative teams rather than systems that constrain creative teams.</p><p>Jeremy Keith recently added colour to the idea of intentional and emergent design systems drawing ideological comparisons with language prescriptivists and language descriptivists.</p><blockquote>Language prescriptivists attempt to define rules about what’s right or right or wrong in a language. Rules like “never end a sentence with a preposition.” Prescriptivists are generally fighting a losing battle and spend most of their time bemoaning the decline of their language because people aren’t following the rules.</blockquote><blockquote>Language descriptivists work the exact opposite way. They see their job as documenting existing language usage instead of defining it. Lexicographers — like Merriam-Webster or the Oxford English Dictionary — receive complaints from angry prescriptivists when dictionaries document usage like “literally” meaning “figuratively”.</blockquote><blockquote>Jeremy Keith — <a href="https://adactio.com/journal/16342">Web standards, dictionaries, and design systems</a></blockquote><p>When I first read the article, I quietly took issue with where Jeremy’s interpretation landed. The reasoning up until the ending resonated, but I believed his conclusion put intentional design systems on the side of beauty at odds with the emergent design systems — accurate but not beautiful.</p><blockquote>I think we can learn from the worlds of web standards and dictionaries here. A prescriptive approach might give you a beautiful design system, but if it doesn’t reflect the actual product, it’s fiction. A descriptive approach might give a design system with imperfections and annoying flaws, but at least it will be accurate.</blockquote><blockquote>I think it’s more important for a design system to be accurate than beautiful.</blockquote><blockquote>Jeremy Keith — <a href="https://adactio.com/journal/16342">Web standards, dictionaries, and design systems</a></blockquote><p>How can front-loaded design systems result in more beautiful products than design systems that begin with the end in mind and work backwards?</p><p>Then I realised the flaw in my thinking. Jeremy was describing the design system <em>itself</em>, not the fruits of the system. (The irony of my flawed thinking further highlights my own biases towards the emergent end of the spectrum!)</p><p>I feel that one further elaboration is required: an intentional design system can create beautiful design systems, an emergent design system can be created from beautiful products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ef59a1d0e1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dawsonandrews/intentional-and-emergent-design-systems-ii-9ef59a1d0e1b">Intentional and Emergent Design Systems II</a> was originally published in <a href="https://medium.com/dawsonandrews">Dawson Andrews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intentional and Emergent Design Systems]]></title>
            <link>https://medium.com/@jordanmoore/intentional-and-emergent-design-systems-474d37af8b82?source=rss-519cd1c351d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/474d37af8b82</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[css]]></category>
            <dc:creator><![CDATA[Jordan Moore]]></dc:creator>
            <pubDate>Tue, 30 Jul 2019 11:34:05 GMT</pubDate>
            <atom:updated>2019-07-30T11:34:05.182Z</atom:updated>
            <content:encoded><![CDATA[<p>There appears to be two competing approaches in designing design systems. I’m going to call these approaches <em>intentional</em> design systems and <em>emergent</em> design systems to create a clear distinction between both.</p><h4>An intentional design system</h4><p>This appears to be the default methodology in design circles. The flavour and framework may vary, but the approach generally consists of: design system first → design/build solutions.</p><p>I have a few concerns with this way of working with design systems. Front-loading design and/or build with the pieces you believe you’ll eventually need to arrive at a solution creates a limited set of outcomes. Any attempt to create more pieces in anticipation of generating a greater number of outcomes results in <strong>conjectural bloat</strong> – a cost offset to the user paid for in unnecessary data and time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gVAlk_2yedT0k9jKuyzWFA@2x.jpeg" /><figcaption>Simplified flow of an intentional design system (building blocks first)</figcaption></figure><p>Assuming the pieces will arrange themselves into answers means that you begin by painting yourself into a corner with something yet to prove its worth. This variety of design systems thinking usually finds its authors and gatekeepers consulting with the system over answers rather than thinking from first principles. Intentional design system advocates focus primarily on the <em>what</em> and <em>how</em> rather than the <em>why</em>.</p><h4>An emergent design system</h4><p>Then there is the opposing approach, the unashamedly cart before horse way of looking at design systems.</p><p>This approach is much closer to the user needs end of the scale by beginning with creative solutions <strong>before</strong> deriving patterns and systems (i.e the system emerges from real, coded scenarios).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uCVxFgm4fOrbe9jMUOQsEw@2x.jpeg" /><figcaption>Simplified flow of an emergent design system (solution first, derive systems)</figcaption></figure><p>Emergent design systems are typically more liberal and agnostic to predefined ideas and pieces. The rules are written <em>as</em> the game is played, not before, which opens up more creative possibilities. The rules committed to code have been proven in the wild and earned their place in the system.</p><p>The fundamental difference between the two competing methods is <strong>the point at which design decisions become codified as part of a design system</strong>. This may seem like a minor point to get stuck on but it touches on an old CSS problem: it’s hard to remove CSS <em>after</em> the fact because it isn’t clear where certain style rules are used or perhaps never used. Front-loading a design system with granular, variable-like CSS rules is as good as saying those rules are immovable and any attempt to move them will have unintended consequences up the design system chain from granular to fully formed components and patterns.</p><p>Waiting for systems to emerge, through a continuous process of building and deconstructing, goes some way towards remedying the assumptions of the alternative technique.</p><p><em>No, “intentional” and “emergent” isn’t an attempt to find another new name for things. It’s simply a useful and distinctive illustrative label that does a better job of helping me describe the problem than the oversimplified “design system first” and “design system last”.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=474d37af8b82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unpacking Design Problems]]></title>
            <link>https://medium.com/dawsonandrews/unpacking-design-problems-c57ae73a67aa?source=rss-519cd1c351d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c57ae73a67aa</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jordan Moore]]></dc:creator>
            <pubDate>Fri, 02 Nov 2018 10:45:43 GMT</pubDate>
            <atom:updated>2018-11-02T10:45:43.743Z</atom:updated>
            <content:encoded><![CDATA[<p>The best puzzles are the ones that demand more of you. When the answer appears obvious, but you second guess yourself. When you know there’s more to it than meets the eye.</p><p>Nob Yoshigahara’s infamous number tree puzzle is certainly one of my personal favourites for just these reasons. It gives you a set of information and asks, What do you make of this?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rdH5Oa4OoV3vREVQIMVVzg.png" /><figcaption>The answer is at the bottom of the article</figcaption></figure><p>Puzzles are a great tool for strengthening mental muscles that can help unpack design problems. They push you to adopt a different mindset and perspective, challenge assumptions, study intently, and look closely. Like a puzzle, difficult design problems evoke that same moment of epiphany when you peel back the layers to find hidden truths.</p><p>But design challenges are not quite as easy as puzzles, which have the answers hidden in plain sight. With puzzles, all the pieces are available to you: You just need to put it together. With design problems, you need to find the pieces first, then put everything together.</p><p>This can be daunting, but there are methods, tactics, and techniques you can reach for to help facilitate these discoveries.</p><h3>First principles</h3><p>Although used heavily in the field of physics, Aristotle’s method of reasoning known as “first principles” originated as a means for organic reasoning (as opposed to looking at analogies, which are often riddled with errors).</p><p>When applied to design problems, you start with an observation, such as a requirement in a project brief. Then you ask why until you arrive at the most basic understanding of the truth of the problem. This provides a solid foundation to build upon.</p><p>First principles force you to look at the problem without using other people’s preconceived ideas and attempts on how to solve it. When you use this approach, you automatically generate new value. It’s certainly cognitively more intense, but in my experience it produces more original and valuable results.</p><p>What happens if you arrive at the same conclusion others have already reached? Is this method a waste of time?</p><p>Mike Bithell, an independent game developer, sums this up nicely:</p><blockquote>“Oftentimes, when trying to reinvent the wheel, you end up with a wheel. But there is a nice moment of ‘huh, I guess that’s why people just use wheels’… that process of justifying the standard is satisfying, if massively wasteful. Still. Cool wheel.”</blockquote><p>For a good example of first principles in action, try this Wikipedia experiment. Click on the first non-parenthesized link in any random article and follow the chain. It will lead you down a path toward the most basic understanding of any concept. Strangely, approximately 80% of articles deconstructed in this manner bring you back to the Wikipedia article about philosophy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xd6cCBkwfUngOBb0mHJcPg.png" /><figcaption>Click the first non-parenthesized link in any article on Wikipedia and see where the trail takes you</figcaption></figure><h3>Question everything</h3><blockquote>“Judge a man by his questions rather than by his answers.” <br>–Voltaire</blockquote><p>A design problem is only as difficult as the questions you ask of it.</p><p>Good questions don’t necessarily lead to definitive answers, but rather further questions. The amount of additional questions tends to correlate with the value hidden within the problem. If a question is easily snuffed out and the conversation cut short, it might not be as provocative as you originally suspected.</p><p>Some good starting points for exploratory questioning are:</p><ul><li>Why is this a problem?</li><li>What makes you believe this is true?</li><li>What is your biggest challenge?</li><li>Who does this well?</li><li>What question did I not ask that would be valuable to know?</li></ul><p>Feel free to use why liberally. Why is like a jackhammer for drilling through a problem’s layers. Why is flexible enough to get to the basic fundamentals (see: first principles), but can also be used to dig deeper into the problem you’re facing.</p><p>Sometimes, the best follow-up question is no question at all. A tactical silence can encourage your client to fill in the gap and reveal additional knowledge that might have otherwise been overlooked.</p><h3>Collaborative understanding</h3><p>Your strength as a product designer is determined by your ability to provide valuable solutions that address your client’s business goals and objectives. This can only be achieved if you deeply understand the original problem.</p><p>I find it beneficial to collaborate intensely with the client to define the problem(s) you’re going to address. Don’t take the version defined in the brief as the be all, end all. Explore it completely, break it down to first principles, build it back up, and communicate the problem back to the client.</p><p>This demonstrates your understanding of your client’s problems, your ability to grapple with problems, and your client’s understanding of their own problems. It creates a good starting point, and it’s the perfect time to demonstrate exactly how you’re going to test assumptions and measure success.</p><blockquote>“A design lives and dies by its designer’s understanding of the problem. Understand the problem.” <br>–<a href="https://twitter.com/erondu/status/987354283883446272">Jared Erondu</a></blockquote><h3>A few more back-pocket methods</h3><p>There are always more ways to test your solutions.</p><p>For example, Occam’s Razor is a mental model that suggests that the simplest solution — the path of least resistance — tends to be the right one. Although it isn’t always indicative of the truth, it’s a good technique to help avoid assumptions and analogies.</p><p>It’s also worth implementing techniques that help remove biases and ensure objectivity. One of my particular favourites is “<a href="https://en.wikipedia.org/wiki/Straw_man#Steelmanning">steelmanning</a>,” or building the strongest possible counter-argument to your solution. Adopting both for- and against-mindsets as you pursue a solution is hugely valuable; it not only produces a better solution, but arms you with a defence against the alternative.</p><p>The path to delivering value in product design isn’t through shiny user interfaces. Like a good puzzle, it lies in your ability to approach the problem from an inquisitive perspective, assemble the pieces of information you need, explore fundamentals and truths, and build back up to the definitive solution.</p><p>No one said it would be easy.</p><p><em>Answer: 12</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c57ae73a67aa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dawsonandrews/unpacking-design-problems-c57ae73a67aa">Unpacking Design Problems</a> was originally published in <a href="https://medium.com/dawsonandrews">Dawson Andrews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mapping User Experiences to Individuals using the Big 5 OCEAN]]></title>
            <link>https://medium.com/dawsonandrews/mapping-user-experiences-to-individuals-using-the-big-5-ocean-eb03806a038b?source=rss-519cd1c351d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb03806a038b</guid>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Jordan Moore]]></dc:creator>
            <pubDate>Wed, 06 Jun 2018 18:17:22 GMT</pubDate>
            <atom:updated>2018-06-06T18:17:22.072Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mapping User Experiences to Individuals Using the Big 5 OCEAN Personality Traits</h3><p>The Big Five Personality Traits, sometimes referred to as the five factor model (FFM), is a model commonly used by psychologists to describe individual personalities. The original model was constructed by Ernest Tupes and Raymond Christal in 1961 but it didn’t reach mainstream academic audiences until the 1980s and early 90s.</p><p>Multiple sets of independent researchers on human personality arrived at the same conclusion in naming the five factors that generally predict and explain behaviour which indicates the factors are valid as far as we know today.</p><p>Each of the five factors (O,C,E,A,N) are scored between 1–100 according to the individual ranked against average scores after completing a series of questions (<a href="https://openpsychometrics.org/tests/IPIP-BFFM/">try it out for yourself</a>).</p><p>The five factors are:</p><ul><li><strong>Openness</strong> — this trait describes someone’s appreciation for art, adventure, inventiveness, creativity, sensitivity to beauty, likely to hold unconventional beliefs — things of an abstract nature. I personally sit on the 95th percentile for openness which seems abnormally high, but most people in the design industry tend to rank quite highly in this factor</li><li><strong>Conscientiousness</strong> — a sense of self-discipline, desire for achievement, tendency to defy measures impeding the route to success, orderly, attention to detail</li><li><strong>Extraversion</strong> — mostly describes what kind of social animal you are, the ability to start conversations, talking to a variety of people at a party, ability to assert themselves, extraverts rather than introverts</li><li><strong>Agreeableness</strong> — sensitivity towards others, empathy for the emotions of others, interested in people and the desire to make people feel at ease, giving up time for others, kind, generous, trusting, optimistic about the intentions of others</li><li><strong>Neuroticism</strong> — negative emotions such as anger, anxiety, depression, easily stressed and irritated, worrying, prone to mood swings</li></ul><p>Every person maps differently to each of the OCEAN personality traits, and having an understanding of how others around you correlate is beneficial to your interactions with them. Not everybody is comfortable being open about the specific scores on each of the factors, particularly as some indicate socially negative traits such as anxiety and depression. Before co-founding our product design studio, each of the directors took the Big Five Personality test as a means to a) see how aligned/unaligned we were in our own individual personalities and b) as a means of empathising with each other in recognising our strengths and supporting our weaknesses. I understand that not everybody would be comfortable sharing something that is so personal to the individual, but we found this exercise has eradicated any talk of <em>“I don’t understand [person]’s point of view”</em> and <em>“I don’t get where [person] coming from”</em>.</p><h4>So why is this important in UX?</h4><p>For me, the tools and methodologies within the field of user experience are flawed in that they do not address concerns beneath a user group level. A truly meaningful experience would speak to the <strong>individual</strong> rather than taking a one-size-fits-all blanket approach.</p><p>We are great at understanding the needs and desires of groups of people, but even personas — the UX tool designed to help empathise with specific users — always bring us back into solutions that scale up to cater for groups based on the assumed needs of a single user. Designing an experience for Sarah, a junior shop assistant who likes long walks, often leads that the majority of users become Sarah and her intended experience is their experience. Job Stories are a relatively new entry into this space where they fix the problem of personas splitting audiences, getting in the way of shared goals. Job Stories are a good means of orienting towards tasks and for that reason remain compatible with an OCEAN approach to UX where Job Stories address universal functional requirements. It leaves room for a presentational layer and certain functional elements catered for individuals.</p><h4>Practical Applications</h4><p>Applications could adapt their interfaces to individuals. Let’s imagine a fitness app with a audio guided run feature. Users in the upper percentiles of conscientiousness may benefit from the orderly, disciplined commands of a drill sergeant and from an app that stretches their goals slightly beyond their comfort zone pushing the user to compete at their best. For people on the other end of the conscientiousness scale, a softer approach would be necessary along with positive reinforcement to help them be the best that they can be without pushing them into territory that alienates them or makes them feel inadequate.</p><p>The same could apply for language and labels used within interfaces. Perhaps some colours appeal to certain personalities? Maybe there are images that intimidate people that inspire other sets of people?</p><p>Looking at the differences between individuals along OCEAN factors studies have shown that individuals high in agreeableness (people who give up time for others, make people feel at ease) are less likely to negotiate salary increases within their company. Perhaps we can create applications that help people move towards desired outcomes in adjusting elements in their personality that may be impeding on particular life goals.</p><h4>Potential dangers and opportunities</h4><p>One of the biggest challenges in pursuing this untapped area of UX is gathering the data required to determine a person’s scores along the Big Five Personality Traits. It’s not exactly ideal to have users answer a full personality test under the promise of a better user experience on the other side of this unique onboarding experience, and it’s certainly not ideal to gather this data in any way that negatively affects a user’s privacy. Maybe it’s something that happens over time where certain actions can produce a score against the OCEAN factors, or games, puzzles and quizzes may unlock this type of information. There is work to be done and design problems to figure out here.</p><p>Then there’s the question of how you store this information and what exactly you do with it. I don’t believe it is necessary to store this data on servers or let any company see a user’s scores. That is for the individual to know and for the product experience to react to it. It is potentially dangerous territory, but then again, so is everything we do:</p><blockquote>If ethics is about the question of how to act, and designers help to shape how technologies mediate action, designing should be considered ‘ethics by other means.’ Every technological artefact that is used will mediate human actions, and every act of design, therefore, helps to constitute moral practices.</blockquote><blockquote>P. P. Verbeek, What Things Do, 2009</blockquote><p>In other words, every design decision you make is loaded with your intent and bias. We’re already knee deep in the danger game whether you have realised this sobering fact already or not. Another one of the major challenges is engineering objectivity into this process, and whether this field is explored further or not, we should look to engineer objectivity into our work regardless.</p><h4>What next?</h4><p>I’m at the mystery stage of the knowledge funnel as described by Roger Martin in his 2009 book The Design of Business. I have identified that this is an area with great potential and the next steps are to build heuristics to see if we can mine the mystery for insights with the eventual hope of turning the research into a reliable, replicable algorithm give us the capability to create and resonate with the people who use the things we make.</p><p><strong>References</strong></p><ol><li><a href="https://en.wikipedia.org/wiki/Big_Five_personality_traits">https://en.wikipedia.org/wiki/Big_Five_personality_traits</a></li><li>P. P. Verbeek, What Things Do, 2009 (Page 69)</li><li>R. Martin, The Design of Business, 2009</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb03806a038b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dawsonandrews/mapping-user-experiences-to-individuals-using-the-big-5-ocean-eb03806a038b">Mapping User Experiences to Individuals using the Big 5 OCEAN</a> was originally published in <a href="https://medium.com/dawsonandrews">Dawson Andrews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts on human vs AI narration]]></title>
            <link>https://medium.com/dawsonandrews/thoughts-on-human-vs-ai-narration-27b0a2e94d40?source=rss-519cd1c351d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/27b0a2e94d40</guid>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Jordan Moore]]></dc:creator>
            <pubDate>Sun, 04 Jun 2017 12:12:16 GMT</pubDate>
            <atom:updated>2017-06-04T12:13:49.795Z</atom:updated>
            <content:encoded><![CDATA[<p>My Instapaper feed looks a lot like my Steam account. I have gathered many items with the good intention of making use of them on a rainy day, but they eventually gather dust on their virtual shelves.</p><p>Occasionally I’ll try and blast through a set of articles that I considered at one point to have potential value to me. When I’m strapped for time I’ll try Instapaper’s “speak” feature, which is effectively a shortcut to iOS’ dictation feature. I usually end up cancelling the dictation after it reads a few paragraphs. Perhaps I forget how bad it is or maybe I’m expecting some advances in the technology since I last used it that make it sound more natural and human-like.</p><p>With AI being applied to more and more tasks, fields and entire industries I notice how far it falls short of key human traits such as empathy and storytelling, and empathy within storytelling for that matter. We have thousands of years of experience on the robots when it comes to communicating oral wisdom from campfires and passing ideas down through generations.</p><p>AI narration is improving, however, services like <a href="http://narro.co/">Narro</a> offer bots with various dialects that have fairly accurate speech patterns and rhythm. But ultimately the narration ends up having a passive effect as AI hasn’t managed to emulate the human capability of captivating an audience to deliver a message. Robots rely on punctuation like a musical score to inform the pace at which they communicate text, though we lack punctuation for instinctive human storytelling tools like drama and the pause to allow certain ideas to simmer in the minds of the listener. This is why uninteresting speakers often fail to communicate their idea — the audience becomes disengaged from the message.</p><p>On a relevant note, another key human trait in storytelling is context. With a contextual understanding of the topic, humans know when to employ the storytelling tools mentioned previously. Consider this example from a recent opinion piece in the New York Times about the dangers of relying on Google rather than investing in deep understanding:</p><blockquote>Google is good at finding information, but the brain beats it in two essential ways. Champions of Google underestimate how much the meaning of words and sentences changes with context. Consider vocabulary. Every teacher knows that a sixth grader, armed with a thesaurus, will often submit a paper studded with words used in not-quite-correct ways, like the student who looked up “meticulous,” saw it meant “very careful,” and wrote “I was meticulous when I fell off the cliff.”</blockquote><blockquote>From <a href="https://www.nytimes.com/2017/05/19/opinion/sunday/you-still-need-your-brain.html"><strong>You Still Need Your Brain</strong></a> by Daniel T. Willingham</blockquote><p>A classic example of schoolchildren discovering a tool like a thesaurus and employing the technology incorrectly. With AI dictation we are cutting out the middleman leaving it open for potential missteps like this not necessarily with words, but the in the power of those words.</p><p>P.S If you are looking for a startup idea, please feel free to design a subscription service with great human storytellers willing to read my Instapaper feed for me, thanks!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27b0a2e94d40" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dawsonandrews/thoughts-on-human-vs-ai-narration-27b0a2e94d40">Thoughts on human vs AI narration</a> was originally published in <a href="https://medium.com/dawsonandrews">Dawson Andrews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The power of awkward silence in user testing sessions]]></title>
            <link>https://medium.com/dawsonandrews/the-power-of-awkward-silence-in-user-testing-sessions-375d1360d1c9?source=rss-519cd1c351d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/375d1360d1c9</guid>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Jordan Moore]]></dc:creator>
            <pubDate>Fri, 26 May 2017 09:07:39 GMT</pubDate>
            <atom:updated>2017-05-26T09:07:39.959Z</atom:updated>
            <content:encoded><![CDATA[<p>Looking back over the vast majority of user testing sessions I have conducted, I noticed a pattern in where I felt I got the most value from each individual session.</p><p>I’m talking about the moment where the room is silent and there’s that awkward pause where the user is struggling and everything in your being is telling you to help them. It’s the moment in the session when they’ve been struck by genuine confusion that causes a gap in the person articulating thoughts back to you as they move through the prototype. If you cave and give into your inherent human desire to help then you risk losing highly valuable insights. You’ll know that moment is happening because you’ll feel it in your gut. You’ll see the obvious on screen where the person sees something else. You’ll see it in their eyes and you’ll want to help by telling them the answer or even ask them something like “What did you expect to happen here?”</p><p>Exercise restraint and give that moment time to breathe.</p><p>Wait for the silence to become uncomfortable and then keep waiting. If you speak first, you lose. Whatever they say first will be an insight. Even if it’s simply “I’m stuck…” or an “I don’t know what to do here…” that gives you a foundation upon which to build a line of questioning to dig deeper. Or they’ll tell you the answer and it will be gold.</p><p>Another thing that I’ve noticed is that after that moment in the session it’s generally the point at which the person loosens up a bit more and talks more candidly about their thought process and becomes more openly critical about your work. For me, <em>this</em> is what defines a useful user testing session versus a session resulting in a blank page with a lack of insights. Otherwise, we could end up going through the motions in a session where you both know the person isn’t being entirely honest because they don’t want to offend people and you end up receiving low-quality feedback, or some of the feedback simply isn’t communicated because that barrier hasn’t been removed.</p><p>I believe it’s still important to lay the groundwork in making them feel at ease, like reassuring them that you didn’t design this thing and that it was the team back in the office (even though you totally designed it), and the fact that you’re helping us make this thing better (which is true) — it’s in that moment of awkwardness where they struggle and you exercise restraint — that’s where the real value lies.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=375d1360d1c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dawsonandrews/the-power-of-awkward-silence-in-user-testing-sessions-375d1360d1c9">The power of awkward silence in user testing sessions</a> was originally published in <a href="https://medium.com/dawsonandrews">Dawson Andrews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Responding to environmental light levels with CSS Media Queries Level 5]]></title>
            <link>https://medium.com/dawsonandrews/responding-to-environmental-light-levels-with-css-media-queries-level-5-f3e0beb78c88?source=rss-519cd1c351d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3e0beb78c88</guid>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Jordan Moore]]></dc:creator>
            <pubDate>Thu, 02 Mar 2017 10:26:30 GMT</pubDate>
            <atom:updated>2017-03-02T13:02:48.435Z</atom:updated>
            <content:encoded><![CDATA[<p>Media Queries Level 5 is a future specification for CSS media queries that intends to build upon the <a href="http://www.w3.org/TR/css3-mediaqueries/">existing media queries spec</a> that many of us use when we build responsive designs today as well as the <a href="https://drafts.csswg.org/mediaqueries-4/">CSS Media Queries Level 4 specification</a>.</p><p>It may seem strange that I want to talk about a theoretical specification beyond CSS Media Queries Level 4 but the powers that be <a href="https://developer.mozilla.org/en/docs/Web/CSS/@media/light-level#specifications">have deferred</a> one of the most exciting media features — the light-level media feature (formerly known as the luminosity)—to the Media Queries Level 5 spec. So obviously the specification has yet to be implemented in any browser at the time of writing, but that shouldn’t stop us from exploring the potential use cases.</p><p>The light-level media feature has garnered interest from the web community, it will allow developers to make CSS adjustments based on changes in the ambient lighting in which the device is used. The user’s device must be equipped with a light sensor to trigger this new media feature.</p><p>One of the most obvious use cases for the light-level media feature is to adapt a design depending on whether the user is reading the page during the day where ambient lighting is brighter or during the night where ambient lighting is darker. We already see this behaviour in a few native apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Nh5R9pKgFQqDwiOoBqhI-A.png" /><figcaption><a href="http://digg.com/reader">Digg Reader</a> on iOS can change its theme depending on the brightness of the environmental lighting</figcaption></figure><p>The thing about designing for the web is we don’t have the same prior knowledge of the destination device that designers for native apps do. The light sensor’s sensitivity on an iOS device might be different than an Android device, and the light sensor’s sensitivity on an Android device might be different to the light sensor of <em>another</em> Android device, so we would need to be careful with the degree of change we make as it could be jarring to devices that have an overly keen light sensor.</p><p>The code will look something like this:</p><pre>@media (light-level: normal) {<br>    body {<br>        background: #f5f5f5;<br>        color: #262626;<br>    }<br>}<br>@media (light-level: dim) {<br>    body {<br>        background: #e9e4e3;<br>    }<br>}<br>@media (light-level: washed) {<br>    body {<br>        background: #ffffff;<br>    }<br>}</pre><p>A <strong>normal</strong> light level represents the screen being viewed in ideal lighting conditions. I would recommend working from this level as your default — and rather than wrapping those styles in a media query targeted for normal light levels it would probably be best to leave those styles unwrapped so browsers and devices that haven’t got the capability of seeing the light media feature can see the page in its ideal condition. You can then use the <strong>dim</strong> value to make adjustments for darker environments and <strong>washed</strong> to adjust styles for brighter environments leaving the default styles accessible to all devices whether they are equipped with a light sensor or not.</p><p>I mentioned earlier about the potential differences in the light sensor hardware sensitivity — I think this is a key reason not to go over the top with the changes we make within light-level media queries. Can we definitively say that a cloud passing in front of the sun will not trigger the <strong>dim</strong> light-level media feature? The last thing I’d imagine the user wants is a harsh change between a light and dark design on a threshold that is too easily triggered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*OaKlPdIh3gShD7KzCJd8lw.jpeg" /><figcaption>Potential stylesheet changes from dark to light environments (left to right). Subtle changes in contrast are key for avoiding a jarring user experience when environmental changes occur</figcaption></figure><p>As with other facets of web design, we should strive to stay out of the user’s way when they are trying to enjoy our design. The light-level media feature has the potential to be the most annoying media query at our disposal, it could be responsible for ushering in a new era of glow in the dark websites — let’s just be careful with it when it eventually arrives.</p><p><em>This article was originally published on my old blog in November 2013, updated in 2014 and this version today in March 2017 to align with changes in CSS draft specifications.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3e0beb78c88" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dawsonandrews/responding-to-environmental-light-levels-with-css-media-queries-level-5-f3e0beb78c88">Responding to environmental light levels with CSS Media Queries Level 5</a> was originally published in <a href="https://medium.com/dawsonandrews">Dawson Andrews</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Tomacco Methodology for Ideas]]></title>
            <link>https://medium.com/theuxblog/the-tomacco-methodology-for-ideas-b8c9207e9dec?source=rss-519cd1c351d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8c9207e9dec</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ideas]]></category>
            <dc:creator><![CDATA[Jordan Moore]]></dc:creator>
            <pubDate>Mon, 27 Feb 2017 12:02:22 GMT</pubDate>
            <atom:updated>2017-05-24T10:40:32.845Z</atom:updated>
            <content:encoded><![CDATA[<p>I am happiest at work when I am in front of our whiteboard wall, marker in my right hand (coffee in the other) and surrounded by people armed with the same tools.</p><p>Workshops at <a href="https://dawsonandrews.com/">Dawson &amp; Andrews</a> are an experience and I want to share some of that secret sauce with you.</p><p>We pour a lot of emotion into ideas. Ideas are held in such high esteem that we dedicate approximately 20% of our time every month to sessions where we gather around our big whiteboard wall and fill it with whatever thoughts, side projects or design problems that have been on our minds.</p><p>By giving ideas an environment to thrive, we increase the chances of turning something that was previously a collection of messages between neurones in an individual’s mind, then visualised in a concept on a whiteboard which is, in turn, collaborated and improved upon before becoming a meaningful thing that delivers value to people.</p><h3>The Tomacco™ Approach</h3><p>As we’re a young studio, everything is still in its infancy and is prone to evolving into something else. Our current approach to ideas is much like Homer Simpson’s approach to growing tomatoes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2g5ccQl_eEUcVviPW2m-oQ.jpeg" /><figcaption>Image courtesy of FX Networks</figcaption></figure><p><em>In case you haven’t seen the Simpsons episode “E-I-E-I-(Annoyed Grunt) I’ll briefly recap. The Simpsons leave Springfield as a result of another one of Homer’s trademark gaffes which left him running from a Southern colonel in search of a temporary home for his family. They arrive at Grampa Simpson’s old farmhouse with lots of poor fertile land. After frustrations growing crops, Homer decides to spray his tomato crops with plutonium to give them a bit of encouragement. The tomato seeds then mutate overnight with tobacco seeds (which Homer mistakenly scattered with his tomato seeds) and the fruits of Homer’s accidental alchemy are born as “Tomacco” — a highly addictive fruit worth millions to tobacco companies vying to take it from Homer.</em></p><p>I see comparisons between Homer’s nuclear approach and the fuel we give to ideas internally in the studio. It’s important not to shoot ideas down when they manifest, but rather let them grow even if they become ridiculous and far-fetched. <strong>Absurdity is fuel for ideas</strong>. You should allow room for the absurd. Doing so will give you fertile ground as a foundation from which to start. By allowing yourselves to get carried away and to remove the baggage of prior knowledge and preconceptions everyone loosens up and ideas start to flow. And it’s remarkable how many times we’ve laughed and thrown a far-fetched idea into the mix only to say “Well, actually… we could do something like that…”. Of course, there will be a point on the path where we’ll need to get real but if we didn’t leave room for the absurd, so many ideas that we have built upon would have remained in the ether.</p><p>Whilst I’m running with this Tomacco analogy, it turns out a great way to validate ideas it to <strong>let them rest and grow</strong>. I generally feel checking in on an idea in a week is a healthy validation window to see if it still makes sense and is worth acting upon.</p><h3>Equipment</h3><p>I’m a subscriber to <a href="https://www.tonyrobbins.com/podcast/3-steps-breakthrough/">Tony Robbin’s “State→Story→Strategy”</a> mode of getting things done. Before we can establish stories and strategies we need to establish a good state. Although state priming is mainly an inward, personal exercise, I believe your environment and equipment are an important part of state setting.</p><p>I recommend the following tools:</p><h4>1. A big whiteboard</h4><p>We’re lucky to have a 6m × 2.5m wall coated in whiteboard paint to leave room to dream big.</p><h4>2. Whiteboard markers</h4><p>For the big whiteboard.</p><h4>3. Idea generating substances (optional)</h4><p>Unless you’re making a follow-up to Sgt Peppers’, I find coffee (of the bulletproof variety) and espressos work wonders. Our communal Chemex gets us in a bit of a tribal mood and probably has some team-working benefits on a subconscious level or something — whatever — I find it helps in setting a good state.</p><h4>4. People!</h4><p>My worst ideas are ones that I’ve grabbed like a rugby ball and tried to run the length of the field by myself. I might get there in the end, but the idea will be knackered and worn out <strong><em>if</em></strong> I make it across the line. With people behind the idea, everyone can take it further. This has been a personal revelation for me. I’ve been putting Paul Arden’s advice of “Don’t covet your ideas… more will come back to you” into practice. Previously ego would have prevented me from giving up an idea and watching someone else carry it. I would have felt like I’d no longer have a chance to be a part of it. However what I’ve learned is that you’ve still got a hand on it, but the more hands around it, the more of a chance you’ve got with the idea. Let someone else carry it, pass it back, come at it from a new angle, introduce new perspectives and carry it over the line with fresh energy.</p><p>Ideas by nature are almost mystical in that they appear out of thin air. Being true to their nature, we don’t schedule in some sort of contrived “idea time”, instead they mostly happen organically. It shouldn’t be a forced situation where we have to think of ideas at gunpoint although that in itself might be a great vessel for experimental thinking.</p><p><em>(The idea for this post was conceived on a whiteboard)</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F313fd4%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F313fd4%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/53a9af75c49c28b205353de3ad566277/href">https://medium.com/media/53a9af75c49c28b205353de3ad566277/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8c9207e9dec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/theuxblog/the-tomacco-methodology-for-ideas-b8c9207e9dec">The Tomacco Methodology for Ideas</a> was originally published in <a href="https://medium.com/theuxblog">theuxblog.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>