<?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 Paul Aston on Medium]]></title>
        <description><![CDATA[Stories by Paul Aston on Medium]]></description>
        <link>https://medium.com/@paul.aston?source=rss-6b8ed8648e36------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*rI3apxCt0qieQG1P.</url>
            <title>Stories by Paul Aston on Medium</title>
            <link>https://medium.com/@paul.aston?source=rss-6b8ed8648e36------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:24:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@paul.aston/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[The EU Data Act: What It Means for OEMs and the Future of Connected Vehicles]]></title>
            <link>https://medium.com/@paul.aston/the-eu-data-act-what-it-means-for-oems-and-the-future-of-connected-vehicles-af2c9b9e8a52?source=rss-6b8ed8648e36------2</link>
            <guid isPermaLink="false">https://medium.com/p/af2c9b9e8a52</guid>
            <category><![CDATA[automotive]]></category>
            <category><![CDATA[eu-data-act]]></category>
            <category><![CDATA[oem-manufacturers]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Paul Aston]]></dc:creator>
            <pubDate>Fri, 31 Jan 2025 11:50:06 GMT</pubDate>
            <atom:updated>2025-01-31T11:50:06.894Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zUErJZ9SZmTQaCFnvb6cWg.png" /></figure><p>Now that the automotive industry has embraced the shift toward connectivity and being software driven, data has become one of its most valuable assets. For Car Manufacturers (OEMs), the ability to collect, manage, and analyse vehicle data is critical — not just for delivering quality products and fostering innovation but also for maintaining a competitive edge. However, with the introduction of the EU Data Act (EUDA), the rules governing data access, sharing, and ownership will change significantly.</p><p>We are at the brink of a new data economy.</p><h3>Understanding the EU Data Act</h3><p>The aim of the <a href="https://digital-strategy.ec.europa.eu/en/policies/data-act">EU Data Act</a> is to create a more competitive and transparent data economy by enabling fair access and use of the data generated by connected vehicles.</p><p>The EU Data Act seeks to foster a more competitive and transparent data ecosystem by ensuring fair access to, and use of, industrial data, including that generated by connected vehicles. The legislation gives users greater control, allowing them to view, download, and share their data. Third parties can also access this data for commercial purposes, provided they have explicit user consent. This shift challenges traditional OEM business models, which have historically treated vehicle data as proprietary.</p><p>Key provisions include:</p><ul><li><strong>User Empowerment:</strong> Vehicle owners and users will have the right to access and share data generated by their cars with third-party service providers, not just the OEM.</li><li><strong>Fair Access Obligations:</strong> OEMs must provide non-discriminatory access to vehicle data, ensuring that independent service providers — such as service centres, insurers, and charging network operators — can compete on an equal footing.</li><li><strong>Interoperability Requirements:</strong> The Act promotes standardised data formats and interfaces, reducing fragmentation and ensuring seamless data exchange across the ecosystem.</li><li><strong>Obligations for Data Sharing Agreements:</strong> Businesses will need to enter into clear agreements governing data access and use, ensuring transparency and compliance with fair market practices.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TiOnzloUPoUPHhXdaMrcPg.png" /><figcaption>The Data Flow of the EU Data Act</figcaption></figure><h3>Impact on OEMs: Challenges and Opportunities</h3><p>Whilst the EUDA does present some challenges, forward-thinking OEMs will recognise it as an open door to new and exciting possibilities.</p><h3>Challenges:</h3><ol><li><strong>Loss of Exclusive Control:</strong> OEMs will no longer have a monopoly over in-vehicle data, potentially impacting revenue streams derived from proprietary data platforms or data powered products.</li><li><strong>Compliance Complexity:</strong> Meeting new legal requirements will require investments in vehicle platforms, infrastructure, data sharing platforms, governance frameworks, and legal expertise.</li><li><strong>Increased Competition:</strong> Greater access to data for third parties means heightened competition from independent service providers, particularly in after-sales, energy, maintenance, and mobility services.</li></ol><h3>Opportunities:</h3><ol><li><strong>New Business Models:</strong> With data-sharing mandates in place, OEMs can develop new revenue streams by offering premium data services or subscription-based access to business critical signals or remote functions.</li><li><strong>Stronger Customer Relationships:</strong> Giving users control over their data enhances transparency and trust, leading to deeper customer loyalty and more personalised experiences.</li><li><strong>Ecosystem Collaboration:</strong> Standardisation and interoperability encourage stronger relationships with third-party developers, leading to enhanced service offerings and greater innovation, it will also allow OEMs to collaborate with startups, software developers, and mobility service providers to co-create groundbreaking solutions.</li><li><strong>Competitive Edge:</strong> By delivering a premium response, rather than simple compliance, OEMs can provide a compelling and engaging experience that brings value to users, builds engagement and drives retention. Failure to do so risks losing out to competitors who prioritise this.</li></ol><h3>How OEMs Should Prepare</h3><ol><li><strong>Explore New Business Models:</strong> OEMs need to reassess their data strategies — especially the mindset shift from proprietary to shared. This may involve restructuring existing data services and exploring new business models.</li><li><strong>Invest in Interoperability:</strong> Ensuring that vehicle data systems align with standardised formats and APIs will be crucial for scaleable deliveries and ease of use within the new data economy.</li><li><strong>Strengthen Data Governance:</strong> Establishing robust compliance mechanisms, transparent data-sharing agreements at scale, and user-friendly consent management systems will be essential.</li><li><strong>Reassess Competitive Edge:</strong> Determine how open data access reshapes market positioning and influences differentiation from competitors.</li></ol><h3>The Road Ahead</h3><p>The EU Data Act is a paradigm shift in the automotive data ecosystem, that challenges the traditional data silos of OEMs, both internally and externally.</p><p>In theory this could foster greater transparency and competitiveness for those who embrace this change proactively and they will be best positioned to thrive in this evolving landscape.</p><p>The EU Data Act is not simply a new piece of compliance — it’s a catalyst for transformation. OEMs that embrace this new era of user empowerment will emerge as the frontrunners of a smarter, more connected automotive world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af2c9b9e8a52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Do I Use Medium?]]></title>
            <link>https://medium.com/@paul.aston/how-do-i-use-medium-c4747cb06e9d?source=rss-6b8ed8648e36------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4747cb06e9d</guid>
            <category><![CDATA[blogging]]></category>
            <dc:creator><![CDATA[Paul Aston]]></dc:creator>
            <pubDate>Tue, 06 Sep 2022 11:36:47 GMT</pubDate>
            <atom:updated>2022-09-06T12:21:55.610Z</atom:updated>
            <content:encoded><![CDATA[<p>I should try and remember the basic rules to make it accessible!</p><ol><li>Remove the post from the paywall</li><li>Make it open to everyone (not just members)</li><li>Follow the instructions: <a href="https://www.notion.so/volvocars/Publishing-to-the-Volvo-Cars-Engineering-blog-dfe7035adc1b48148ac2620efb79acfc">https://www.notion.so/volvocars/Publishing-to-the-Volvo-Cars-Engineering-blog-dfe7035adc1b48148ac2620efb79acfc</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4747cb06e9d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Thinking for Devs]]></title>
            <link>https://medium.com/wearehumblebee/design-thinking-for-devs-14d86134e124?source=rss-6b8ed8648e36------2</link>
            <guid isPermaLink="false">https://medium.com/p/14d86134e124</guid>
            <category><![CDATA[technical-design]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[humblebee-stories]]></category>
            <dc:creator><![CDATA[Paul Aston]]></dc:creator>
            <pubDate>Tue, 19 Jun 2018 13:58:23 GMT</pubDate>
            <atom:updated>2022-09-06T11:26:54.934Z</atom:updated>
            <content:encoded><![CDATA[<h4>What is it, and why should you care?</h4><p>In my previous article I talked about <a href="https://blog.prototypr.io/why-developers-should-be-in-your-design-sprints-127a385507c9">why developers should be in design sprints</a>, and it’s been nice to hear that there are devs out there who agree with me. The one question that keeps cropping up though, is: “What exactly is a design sprint”?</p><p>So trying to keep it to simple words and nothing too ‘design-y’, here is a brief introduction to design thinking.</p><p>First things first, what the f**k is it?</p><p>The best answer I have found is: “Tackling ill-defined problems in a human-centric way” — You put yourself in your user’s shoes</p><p>It’s a process made up of 5 stages. To begin with, you move through them, working towards a solution to your problem.</p><ol><li><em>Empathise</em></li><li><em>Define</em></li><li><em>Ideate</em></li><li><em>Prototype</em></li><li><em>Test</em></li></ol><p>Which is all well and good, but what does that actually mean? Let’s take an example. First of all we get our ill-defined problem.</p><blockquote>“Our new webshop isn’t getting as many sales as we thought it would”</blockquote><h4>Empathise</h4><p>With that problem as clear as mud, we can move onto the first stage in the design sprint, <strong>Empathise<br></strong>Understand from a user’s perspective what it’s like to use the site. Try it yourself, run user testing, benchmark against industry leaders. Basically, use it, poke and prod at it, listen to what people are saying.</p><p>So let’s take a look at our example site (with all due apologies to <a href="http://arngren.net/">arngren.net</a>):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o4zhS2PIlyMPGifJn2frsQ.png" /><figcaption>Landing Page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9YKEoYQZoUgwC27dyfyBUg.png" /><figcaption>Product Page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*owFSoGpKz-1A4N-s8ri-jA.png" /><figcaption>Checkout</figcaption></figure><h4>Define</h4><p><em>The horror, the horror! </em>Right? But now we’ve tested the site, we’ve got some feedback and we’ve interviewed some actual users. So now we can move on to <strong>Define. </strong>What exactly is the problem that we’re solving? Why are they not converting site visits to sales?</p><p>Let’s look at some real(ish) feedback:</p><ul><li>It should be set on fire and s**t into space! (<strong><em>dev</em></strong>)</li><li>Poor use of white space, there’s no flow (<strong><em>UX</em></strong>)</li><li>It’s takes, like, a minute to load! (<strong><em>dev</em></strong>)</li><li>The Accessibility is all wrong (<strong><em>UX</em></strong>)</li><li>Are those bugs or features? (<strong><em>dev</em></strong>)</li><li>The baseline isn’t good (<strong><em>UX</em></strong>)</li><li>I think it’s fun, but I don’t trust the checkout (<strong><em>actual user</em></strong>)</li></ul><p>These are some pretty typical bits of feedback and you can see the different perspectives coming through (which is why you really should have a mixed team in a sprint). But let’s address that last bit of feedback from an normal user of the site:</p><blockquote>“I think it’s fun, but I don’t trust the checkout”</blockquote><p>That comment cuts through our ‘expert’ diagnosis and actually gives us a nice piece of insight. I think we can safely say we’ve defined our problem — Users actually like the site, but they have no confidence in the checkout.</p><h4>Ideation</h4><p>With a clear problem to solve “Users don’t trust the checkout”, we can move on to <strong>Ideation. </strong>This is the bit where we get all clever and stuff, and come up with ways to fix the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/1*mi8-ND9asMpfifUma0_IBg.gif" /></figure><p>Now there are two important things to remember here:</p><ol><li>There are a <a href="https://www.cleverism.com/18-best-idea-generation-techniques/">ridiculous number of techniques</a> people use for ideation, but they are nothing to be scared off. A good workshop facilitator will only use them to help unstick the nuggets of genius up there in your head.</li><li>THERE IS NO SUCH THING AS A BAD IDEA. This is important. At this stage, just throw up everything. You’d be surprised how many times a truly batshit idea spawns some real brilliance.</li></ol><p>So bearing these two things in mind, we’ll have dived into extracting all that brilliance and will have produced a veritable flood of post-its. They’ll be all over the walls, like technicolour unicorn vomit. This is the scene that people seem to always conjure when they picture ‘creativity’. In truth, it’s just a convenient way to get those ideas out and up in a people-readable way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*O1tu1zu6UtypJIe5cYU5fA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*RgPTv5UL8NahCRUfdnzBJw.png" /></figure><p>Now we have our ideas, we have to choose the best ones to go forward with. Again there are a number of ways of doing this, from rock-paper-scissors (seriously), to all kinds of sticky dot related voting malarky.</p><p>The important thing is that we choose <em>something </em>and proceed to the next stage.</p><h4>Prototyping</h4><p>As a dev your first instinct is to break out the boilerplate and start building some kind of MVP. Cool your jets, hotshot! Go as low tech as you can to start with, nothing wrong with good old pen and paper if it does the job. The designers may be rushing off to Invision or Flinto if they want something a little more substantial, but if you’re just testing the concept and not the UI, quick and dirty is the way forwards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9nzxEdJuJ-ruJHPKfl6DYw.png" /></figure><p>NB: Whilst this can be a nice opportunity to put your feet up with a cuppa and let your ultra-hip design colleagues do the work, it is worth at least sticking around for the beginning and making sure they understand exactly what you meant about the tech on that hastily scribbled post-it.</p><p>Once the prototype has been cobbled together, it’s time to put it in front of some unsuspecting innocents.</p><h4>Testing</h4><p>Simply, grab some users. Make them use your prototype. Designers have ways of making them talk.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FZWIKzjfnnUCKQ%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FZWIKzjfnnUCKQ%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FZWIKzjfnnUCKQ%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="179" frameborder="0" scrolling="no"><a href="https://medium.com/media/1d98187244516a075e3108dc4badd375/href">https://medium.com/media/1d98187244516a075e3108dc4badd375/href</a></iframe><p>Seriously, they do. There are even dedicated UX Researchers out there who get worryingly phycological at people. <br>The aim of this testing is to get <em>insights, </em>which basically translates to: “do people like our idea?”</p><p>From this there are only really two ways to go:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fd3mmkM7o2qC78iZ2%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fd3mmkM7o2qC78iZ2%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fd3mmkM7o2qC78iZ2%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="245" frameborder="0" scrolling="no"><a href="https://medium.com/media/ba531d8e59cc5d325b127d56b19f7d89/href">https://medium.com/media/ba531d8e59cc5d325b127d56b19f7d89/href</a></iframe><p>It’s a success. Now it’s time to fire up your tools, atomic batteries to power, turbines to speed and <em>get building.</em></p><p>Or, more likely…</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3ohzdOTQloNHvuDFGE%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3ohzdOTQloNHvuDFGE%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExcDl0NjdwM3ZnZjZ5bTFhMm5sdHFmeWc3Z3R5Z2N0MnZhaHlxZ2g5cCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2F3ohzdOTQloNHvuDFGE%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="289" frameborder="0" scrolling="no"><a href="https://medium.com/media/5ccfceefa300ea57ea6dba032af4513b/href">https://medium.com/media/5ccfceefa300ea57ea6dba032af4513b/href</a></iframe><p>It’s back to the drawing board — You see, this is the thing with design thinking, it’s not really a step-by-step recipe, it’s more of a set of modes in an iterative process.</p><p>You’ve taken a good stab at solving the problem. Maybe the users didn’t like your solution, maybe they didn’t agree with your definition of the problem, but at least now you have a better idea of where to look and you didn’t waste a load of resources to get there.</p><p>Quick testing and validation lead to great solutions with minimal overhead and a better chance of success.</p><p>As the team puts it: “Be fast to fail”</p><p>Personally, I like to think of it as: “Failing with style”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14d86134e124" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wearehumblebee/design-thinking-for-devs-14d86134e124">Design Thinking for Devs</a> was originally published in <a href="https://medium.com/wearehumblebee">Humblebee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Developers should be in your design sprints.]]></title>
            <link>https://blog.prototypr.io/why-developers-should-be-in-your-design-sprints-127a385507c9?source=rss-6b8ed8648e36------2</link>
            <guid isPermaLink="false">https://medium.com/p/127a385507c9</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[technical-design]]></category>
            <dc:creator><![CDATA[Paul Aston]]></dc:creator>
            <pubDate>Fri, 08 Jun 2018 07:11:15 GMT</pubDate>
            <atom:updated>2018-06-12T06:42:15.921Z</atom:updated>
            <content:encoded><![CDATA[<h4>AKA: The Rise of Technical Designers</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B0hHUJ5enXrPBNPmc39vqA.jpeg" /></figure><p>Interestingly, if you google “Technical Designer”, the main result is for those talented types in the fashion industry who construct the garments based on an illustrator’s drawings. Recently though, that’s a title I’m hearing more and more in digital, mainly around devs who’ve gone over to The Dark Side.</p><p>The parallels are there, traditionally developers are the people who weave code out of the pretty pictures given to them by their stylish and enigmatic designer colleagues. They are the people who bring the ideas to life for use on real actual people. The ones who understand the warp and weft of code, making sure it’ll fit an IE just as well as the idealised size 0 Chrome.</p><p>A Technical Designer in this world is a developer who doesn’t just build the product, but gets involved right from the outset, lending their expertise to the design process.</p><p>As design sprints become ubiquitous, it’s a golden opportunity for devs to get all up in the design teams business and deal with some longstanding gripes:</p><ul><li>Poor communication between design and devs, creating a disparity between what is designed and what is actually built.</li><li>No shared ownership of the user experience, devs don’t see the value in the UX decisions made.</li><li>Frustration in design choices leading to bad code.</li><li>No sense of ownership of the project.</li><li>…<em>Dance code monkey, dance</em>.</li></ul><p>And it’s to the benefit of everyone involved, especially the design team. I’ve been involved in more than one project where they conveniently “forgot” to invite someone from the development team into the sprint. Every time has resulted in a convoluted (and in two cases, downright horrific) “service” that could have been avoided with just a few minutes of developer input.</p><p>All that wasted time…</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fd2W7eZX5z62ziqdi%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fd2W7eZX5z62ziqdi%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fd2W7eZX5z62ziqdi%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="217" frameborder="0" scrolling="no"><a href="https://medium.com/media/2963adafb00e03ab9482fd620853414a/href">https://medium.com/media/2963adafb00e03ab9482fd620853414a/href</a></iframe><h3>To designers…</h3><p>So. Why exactly should you, as a designer have developers in a design sprint?</p><ul><li>I’m pretty sure your sprint team should be a diverse group. I know developers are weird and scary, and probably wear the wrong trainers, but sprints aren’t supposed to be a designer love-in.</li><li>Devs have awesome problem solving brains. It’s what they do. It’s why they are developers. If design thinking is “tackling ill-defined problems in a human-centric way”, you need people who problem solve on the fly, every single day. And contrary to what some of you think, developers are humans too.</li><li>Devs have amazing knowledge and insight. Think back to those guys in the fashion industry, the ones who actually understand how clothes work in the real world, those are your devs. It doesn’t matter how good the design is if you don’t have someone who can make it work. Now imagine how good the design could be if you had that expertise from the very start.</li><li>Devs are <em>craftspeople</em>. It’s like having a digital master carpenter on your team. They take enormous pride in producing elegant things out of complex systems and concepts. And what they build is <em>good.</em></li></ul><h3>To developers…</h3><p>So why should you, as a developer get involved in the arcane arts of design sprints?</p><blockquote>To know your Enemy, you must become your Enemy. — Sun Tzu</blockquote><p>It’s a bit trite, but surely it’s better to understand why these things are happening. You should understand the process that leads to the work that lands in your lap with a nice pink stickie that says: “Make this!”.</p><p>As to the rest:</p><ul><li><strong>It’s fun</strong>. Seriously. It’s challenging, and can be frustrating, but it gives you a chance to stretch your mental muscles in a very satisfying way. Personally, I love the way you can throw out ideas and see that look on a designers face that says: “I’ve <em>never </em>looked at it like <em>that </em>before<em>”.</em></li><li><strong>It feels good to be heard</strong>. You’re in a room where “there is no such thing as a stupid idea”, use that opportunity to voice your opinions. If you’re sick of seeing certain design decisions, raise your voice and explain (nicely) why they are so bloody stupid. You have a chance to steer the room to the right solution.</li><li><strong>Ownership</strong>. Rather than getting handed a wodge of Figma pages and being expected to get on with it, this is now <em>your </em>project. You’ve helped make this baby, and now you get to bring it into the world. It becomes like one of those side projects you do to stop yourself from going metal. Imagine the <em>satisfaction.</em></li><li><strong>You will understand the thinking behind the UX decisions</strong>. No more looking at a design and wondering “say what now?”</li><li><strong>Laziness</strong>. Every dev is lazy, that’s why we use Gulp. Why do more work when you can spend 3 times as long automating it (okay, bad example, but, you know what I mean). The best thing about design sprints is that after the amazing creative splurge of Ideation, the designers have to bugger off and take care of prototyping and testing. You get the fun stuff.</li></ul><h3>For everyone…</h3><p>Shouting to those at the back:</p><ul><li>Better communication — what gets designed is what gets built.</li><li>Better final product.</li></ul><p>I’m not going to extrapolate on these. The benefit should be pretty self evident. If you don’t see it. Step. Away. From. The. Sprint and go and bother some middle management somewhere.</p><h3>I am interested, but…</h3><p>By now you’re hopefully convinced to at least give it a try , but there are still a few doubts. Based on some recent conversations with fellow developers, I’ll take a guess that your top 3 worries are:</p><ol><li>“I don’t understand the process.”</li><li>“I don’t understand the terms to the designers use.“</li><li>“I don’t want to look stupid.”</li></ol><p>These are good and valid points. So here are three quick answers:</p><ol><li>This is a brilliant resource, you’ll understand Design Sprints in 2 minutes: <a href="https://www.interaction-design.org/literature/topics/design-thinking">Interaction Design Federation — What is Design Thinking?</a></li><li>Meh. They like to sound clever. Just start throwing around some fancy language of your own.</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhkDD03yeLnU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhkDD03yeLnU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhkDD03yeLnU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/78c840c53fd47fe1eb3b74fa51fc9ec1/href">https://medium.com/media/78c840c53fd47fe1eb3b74fa51fc9ec1/href</a></iframe><p>3. Remember what I said about “no such thing as a stupid idea”? Yours may be “different”, but <em>that’s</em> why you’re there. That’s your imposter syndrome talking and you should ignore it. If you’re a working dev, you sure as hell ain’t stupid.</p><h3>“Calling Agent Triple X…”</h3><p>It may feel strange getting involved in this. There’s a sense of blurring the lines between two traditionally disparate groups, but as working processes evolve, it’s vital that we do too. Better cross-discipline communication only leads to better work. A good developer never stops learning, and this is a great opportunity to not just gain a whole new perspective, but also teach the other side about what <em>you </em>do.</p><p>It’s like the uneasy detente between East &amp; West Germany in the 80’s, where you’re playing off both sides against each other to bring down the wall. Hell, you’re being David Hasselhoff.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FMQ5rIbnD_P4%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DMQ5rIbnD_P4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FMQ5rIbnD_P4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/198d6df0ea362c6acd81421d3f31145f/href">https://medium.com/media/198d6df0ea362c6acd81421d3f31145f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=127a385507c9" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/why-developers-should-be-in-your-design-sprints-127a385507c9">Why Developers should be in your design sprints.</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a UX for digital users in 2030, with a multi-office, cross-competence team.]]></title>
            <link>https://medium.com/wearehumblebee/designing-a-ux-for-digital-users-in-2030-with-a-multi-office-cross-competence-team-caac1ab79116?source=rss-6b8ed8648e36------2</link>
            <guid isPermaLink="false">https://medium.com/p/caac1ab79116</guid>
            <category><![CDATA[future]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[humblebee-stories]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Paul Aston]]></dc:creator>
            <pubDate>Wed, 23 May 2018 06:56:53 GMT</pubDate>
            <atom:updated>2018-06-19T14:00:39.676Z</atom:updated>
            <content:encoded><![CDATA[<h3>Including: “When is the right time to yell at stakeholders?”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zoEnsNWWfiat4mEVFVx-bg.jpeg" /></figure><p>The brief was pretty straightforward, attempt to define digital services from a user’s perspective in 2030, as part of a major project for a client.</p><p>We would be working as a multi-department, cross-competence team, bringing with us years of experience across a range of disciplines and hopefully no little amount of insight and creativity.</p><p>To attempt to give some structure to the proceedings, 5 product and 5 consumer pillars had been defined — encompassing brand values, technical ambition and the overarching themes the design team wanted to examine.</p><p>So far, so good. Right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f-PT80818TNK_1A2cI9JKg.jpeg" /></figure><h3>Stage 1</h3><p>The first meeting was pretty electric — a room full of the ‘best and brightest’, all hepped up on coffee, Californian sunshine and enthusiasm. Everyone in the room had earned a place at the table and I had that lovely feeling of being potentially the dumbest person in room.</p><p>And there were a <em>lot </em>of people in the room.</p><p>Now, in the interests of full disclosure, I should mention that our team came with something of an agenda. We wanted to come away from this first session with a stake in this new concept that related to our work back home. We wanted a piece of the pie. We were fortunate that we tended to work with a broad focus, and had a pretty diverse portfolio to call upon to find our play.</p><p>Naturally, many of our colleagues had the same idea. The problem that became quickly apparent, is that they were laser focused on one specific project or piece of technology. That was their world and they <em>would </em>inject it into this project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u5PxBKpYmOErK0eMwAuHRw.jpeg" /></figure><p>As I mentioned earlier, there were a lot of people in the room. A lot of people with very specific agendas. So when we started a round-table discussion to examine the pre-defined pillars, it became a case of who could shout loudest about how their speciality would fit into any of these criteria.</p><p>Don’t get me wrong, it was <em>fascinating!</em> These guys are good<em>, </em>and under any other circumstances I could have happily listened all day. However, as we watched the agenda fall by the wayside, and descended into another incredibly granular discussion about how <em>X </em>could make <em>Y </em>work<em>, </em>it became quite clear that we weren’t gaining any real insight into those pillars, and that without some leadership, we were pretty much just involved in a giant case of know-how willy-waving (and yes, the room was 95% male).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zX0tBOAh1BQbSdiHjrhrgg.jpeg" /></figure><p>The following day, we returned to the bat-cave and reassessed the sea of scribbles on the wall. It appeared that the previous evening some judgements had been made by a visiting higher-up, and a few pertinent points had been asterisked. We also had our task for the day. “Start creating personas”.</p><p>Without any insights in the problem, with no real data or research, or any idea of pains or needs to solve for, we dove into it using the <a href="https://medium.com/@timschwab/can-myers-briggs-help-you-find-the-perfect-startup-co-founder-or-employee-b4104fa10cff">Myers-Briggs personality types</a> to build our characters.</p><p>Two things happened.</p><ol><li>We fell a bit too much in love with these people we created. Dad-mode activated.</li><li>We created a mix of characters that were the polar opposite of our client’s core demographic, Nothing wrong with being aspirational, but would we completely change their engagement in 12 years?</li></ol><p>Time ran out. It was time to break up the band. We had a few use cases that had surfaced during our persona building, and instructions to continue creating personas. More feedback was ‘incoming’</p><p>It was time to go home.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FQgimKGS8JpE3u%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FQgimKGS8JpE3u%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FQgimKGS8JpE3u%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="246" frameborder="0" scrolling="no"><a href="https://medium.com/media/e1ec293c62c540693f1493a3168642d2/href">https://medium.com/media/e1ec293c62c540693f1493a3168642d2/href</a></iframe><h3>Stage 2</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F2OP9jbHFlFPW%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F2OP9jbHFlFPW%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F2OP9jbHFlFPW%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="278" frameborder="0" scrolling="no"><a href="https://medium.com/media/b8ef517ca010e6fb3b7c83c51131f11d/href">https://medium.com/media/b8ef517ca010e6fb3b7c83c51131f11d/href</a></iframe><p>First instructions on our return were“Ignore the personas. Build use cases. We want LOTS of use cases”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JdUASSR2FJuV27cfuM7Dig.jpeg" /></figure><p>This was quite refreshing. We were home and felt we had something of a blank canvas to work from.</p><p>One thing we had quickly realised was that personas won’t work for this. How can you create an accurate concept of a person who doesn’t even exist yet? They have no peers or cohort. In fact, we don’t even have the world they live in…</p><p>“The world they live in” — That was the key to understanding this space. What we needed to do was go as wide as we possibly could, get as much insight as possible and make our best accurate guess as to what the world of 2030 would look like.</p><p>SPOILER: <a href="https://medium.com/@paul.aston/the-world-of-a-user-in-2030-9c9a91167c43">It looks like this</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3KMiDwk23GaQVL4ewWy3_A.jpeg" /></figure><p>Thanks to some excellent input from our Finnish Queen-of-all-Workshops, we had arranged all our insights into a Scope Wheel divided them up by category — industry, health, society, etc — and arranged them so those most relevant to our field were closer to the “bullseye”, and the more irrelevant out towards the edge.</p><p>We though this would help us focus on insights most relevant to our project, but in fact we found that it was the ideas on the outer rim that gave us the most inspiration. And in fact, by going wide and looking away from our particular field, we were able to create a rich and well rounded world to ideate around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q6cSY3Vms5Ec8AGHbZ_zbg.jpeg" /></figure><p>With such a fertile basis for ideation, we found that ideas came thick and fast. We worked quickly and wrote down use cases on post-its, and threw them up on the board. After a moment to review and make some initial attempts at clustering we would see areas that maybe needed more focus, and go for another round with a weather eye on the gaps.</p><p>Each time we had another round of ideation we grabbed another brain from the office, quickly immersed them in our world and let them run free. Naturally these ideas ranged from utter genius to utter madness, but already we could see some common themes beginning to emerge.</p><p>What was particularly interesting was that with these ideas we were exploring our actual ‘Right to Play’ in this future world — were these concepts actually something our client should be doing, or were they services provided by a 3rd party that we would simply use?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2lF7pkwAD7itRhtt1_KlKA.jpeg" /></figure><p>With over a 101 use cases, clustered and rated we were ready to start building some user stories. We were lucky in that many of our ideas seemed to have a natural fit with the narrative of the world we’d created, and they seemed to write themselves.</p><p>My colleague compared it to writing a movie — you have this amazing story and just have to find characters to tell it for you. Some of our original personas were revived, and some new ones sprang to life just by exploring the concepts. One of the most gratifying moments was discovering that we needed a retired, elderly person who had mobility problems, a marvellous counterpoint to the fantastical bright young things from before.</p><p>A whole raft of new user stories created, we sent them off to our colleagues. We had doubled the output of two other teams!</p><p>We had simply got lost in the storytelling and through our user stories explain our research and the world we’d created. Which was to become a problem later on…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AI2zgYZNBdjIVouHXMyyWw.jpeg" /></figure><p>Then came the silence.</p><p>We had submitted our work, we’d had great feedback and then we heard nothing. We heard that the lead team had selected their favourite use cases, combined some others and were taking them forward to the management team.</p><p>It felt like we’d done some amazing work and simply tossed it into a hole. We thought we were out of the process.</p><h3>Stage 3</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g5B8i1UCwj0IAGlhCjum9Q.jpeg" /></figure><p>Which made what happened next pretty gratifying.</p><p>We received the next generation of revised user stories. A couple of ours were there pretty much unchanged, but the rest, although richer in content, somehow seemed weaker.</p><p>One of ours had apparently been held up as the benchmark, and we were asked to take over the creation of all of the user stories. We had found the brand values and the right-to-play.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lzp32lm8vgqbzlDXqvL4Jg.jpeg" /></figure><p>So it was back to the drawing board. Or in our case the crazy wall. We pinned up both generations of user stories, any notes we’d received, a summary of our research and anything that seemed relevant. Honestly, there was a reason for that Judge Dredd picture…</p><p>With all of that up, we were able to dot vote our favourite use cases, add copious notes extracting the themes from each, and start pinning up ribbons between common concepts or stories that seemed to compliment each other.</p><p>It looked like the work of a maniac, but we could immediately visualise the next steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZYj4K4u8Wd3yZnzM3dfqLw.jpeg" /></figure><p>We needed to build completely new stories from the use cases that we’d picked, merging the good parts, and letting the product tell the story.</p><p>Based on our benchmark piece, good story telling was crucial.</p><p>But that was only the start, we soon saw our biggest mistake from before. The world that we’d created was not optimistic and our use cases reflected this. We had come up with some strong ideas to relive the pains of future living, but that pain was the essence of our user stories.</p><p>We were also trying too hard to justify our use cases with some heavy handed references to our research.</p><p>It made for some pretty bleak storytelling .</p><p>What do you do in this situation? You turn it on its head. Take the use case, ignore the pain and show the positivity. If you can tell people when something is going wrong. Why not tell them when things are going great instead?</p><p>Immediately the pieces started to fall into place and new <em>positiuve </em>user stories began to emerge.</p><p>It was time to check in and get some feedback…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vORbI1TVlH_WhjHGFYzQnw.jpeg" /></figure><p>The lead team were in town, and it was great to bring them into office and stand by our crazy wall, two freestanding whiteboards and our design desks all covered in notes, scribbles and ideas and talk them through our work.</p><h3>Intermission: “When is the right time to yell at stakeholders?”</h3><p>As a rule, the answer is never. Losing your rag is unprofessional and often means that your ideas get dismissed out of hand.</p><p>However, sometimes, just sometimes, getting a bit ‘passionate’ is the only way.</p><p>Throughout this whole process, I had noticed people using certain technical terms, and holding certain concepts up as ideals. As the Technical Designer in our team I’d raised the point a few times that:</p><ol><li>The terms they were using had nothing to do with the technology they were describing.</li><li>The concepts were at best outdated and at worst horribly misguided.</li><li>Continuing with the above would be an unwise move.</li></ol><p>So hearing these again during our feedback session, despite everything that had been said, and literally surrounded by the days of work that proved the point, there <em>may </em>have been some words said at a slightly increased volume. There was definitely some arm waving and finger pointing.</p><p>I was told afterwards that my case was “compelling” and they had taken it all on board.</p><p>Sometimes, if your client is wrong, you have to tell them.</p><p>If there is a learning here, it is something along the lines of: “If you have to speak loudly make sure you’re carrying a big stack of data”. Or something.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qJ3l5eLTv0sAHI_Batj_fg.jpeg" /></figure><p>So, to carry on with the feedback session.</p><p>And a note on getting feedback. Throughout this whole process we had to fight for feedback at every stage. Coming from a team where we are used to quick ideation and iteration, not only was it frustrating, but it gave the impression that we weren’t part of the core team, and that our input wasn’t really valued.</p><p>Which was strange since at every stage our work had been held up as the standard.</p><p>However, on the whole the reaction was incredibly positive again and we felt that we’d found our voice, that we were hitting the brand values and the actual use cases were relevant and meaningful.</p><p>Not just that. Remember the pillars I mentioned at the beginning? We found that our use cases supported them perfectly.</p><p>The only spanner in the works was that there were two particular scenarios that the management team wanted to explore and they had come from the two most downright depressing user stories from before.</p><p>One was based around an emotionally stunted robot of a man, the other a horribly mangled accident survivor. Woo! Fun!</p><p>However, with our newly found Positive-persona-spin®, we found we could immediately find the essence of the use cases and turn them into something meaningful, and most importantly, not horribly dismal. I mean, these actually gave us a real case of the warm fuzzies.</p><h3>Footnote</h3><p>As was standard operating procedure, we had to push to get feedback. The other team had travelled five and half thousand miles to be in our city and we couldn’t get 20 minutes to talk to them…</p><p>Through the expedient step of grabbing one of them and dragging him out for a drink, my colleague finally heard something.</p><p>We’d killed it!</p><p>Interestingly, it was one of the previously dismal user stories that was the favourite.</p><p>Now we’re just waiting to hear on the next step…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5mA-rfyWexy8hlV0qZOHoA.jpeg" /></figure><p><strong>Takeouts</strong></p><blockquote>Personas don’t work for this</blockquote><blockquote>Easy to get lost in the story</blockquote><blockquote>Don’t be afraid to go wide</blockquote><blockquote>Put a positive spin on it</blockquote><blockquote>Use physical media</blockquote><blockquote>Speak up</blockquote><p>I hope you enjoyed the read. <em>Feel free to comment, ask a question or leave your own opinion. If you enjoyed this article please hit the “Recommend” button.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=caac1ab79116" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wearehumblebee/designing-a-ux-for-digital-users-in-2030-with-a-multi-office-cross-competence-team-caac1ab79116">Designing a UX for digital users in 2030, with a multi-office, cross-competence team.</a> was originally published in <a href="https://medium.com/wearehumblebee">Humblebee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How will the world of a digital user look in 2030?]]></title>
            <link>https://medium.com/wearehumblebee/the-world-of-a-user-in-2030-9c9a91167c43?source=rss-6b8ed8648e36------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c9a91167c43</guid>
            <category><![CDATA[forecasting]]></category>
            <category><![CDATA[business-design]]></category>
            <category><![CDATA[humblebee-stories]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Paul Aston]]></dc:creator>
            <pubDate>Thu, 03 May 2018 13:10:17 GMT</pubDate>
            <atom:updated>2018-06-19T14:05:19.653Z</atom:updated>
            <content:encoded><![CDATA[<p>Casting opinions about the future, with any kind of authority can be a dangerous game. Nils Bohr, Nobel laureate in Physics, is a lot smarter than me, and once said:</p><p>“Prediction is very difficult, especially if it’s about the future.”</p><p>You can make some pretty fair assumption about the state of the world tomorrow or next week, and you can be pretty confident in the world a month or two hence. But once you start getting up to a year or more from now, your predictions become guesses, even if they’re well educated ones.</p><p>That’s not to say that the world ahead is an unpredictable fog of change and random innovation. Much like the weather we can read the state of the now and from that, with our knowledge of previous behaviours make a fair prediction of where we may be heading.</p><blockquote>“A good forecaster is not smarter than everyone else, he merely has his ignorance better organised. “</blockquote><blockquote>— Anonymous</blockquote><p>So, when faced with a project to consider digital services from a user’s perspective in 2030, we realised we would have to tread carefully, despite the overwhelming urge to wave our arms about and make wild and ‘informed’ proclamations about the upcoming golden age of flying cars and sex-robots.</p><p>In the end our approach was simple. We’re looking 12 years into the future, so let’s look at the broader strokes, start with what will be happening in areas like Industry &amp; Health. Despite rapid advances in the science behind these, we know it can take years for a new advance to enter the public domain, so if we look at what is coming along now, we will be able to have a pretty good idea of what will be influencing the society of 2030.</p><p>We also tried steer away from focusing on the hardware coming down the line, technology is enabler, but we wanted to try and find some broad brushstrokes of the world to understand the needs and pains of the future citizen.</p><p>What follows is by no means a definitive prediction, but a selection of a some of the more probable outcomes mixed with a little analysis and no little guesswork. Essentially, some relatively well organised ignorance.</p><p>Let’s start with industry. Industry is about building things, and this takes time. There are buildings being planned now that won’t be completed until 2030.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LmiEevIssUGXOpundCAXbA.jpeg" /><figcaption>With thanks to Simon Stålenhag</figcaption></figure><p><strong>Industry</strong></p><p>First things first, Mars baby! If we’re not living there, we soon will be, and man will most certainly have stepped foot on the red planet. We will have experienced a new kind of space race, not one of nations competing to claim to claim the stars for their side of the iron curtain, but of companies and individuals, buoyed by the success of their silicon valley start-ups, reaching up to achieve their childhood dreams of rocket men and moon bases.</p><p>This will have a number of effects on the industry of the future. First of all, Space will be an industry in an of itself, the technologies developed by SpaceX, Blue Origin et all, will provide low-cost ways of putting a payload into orbit. The cheaper it is to put things up there, the more things will be sent up. There will be a boom of pure science, space mining experiments, industrial R&amp;D and even tourism. Getting things up there, doing things up there and getting people drunk up there will fuel a multi-billion dollar Space industry.</p><blockquote>If NASA is to reach beyond the Moon and someday reach Mars, it must be relieved of the burden of launching people and cargo to low earth orbit. To do that, we must invest more in commercial spaceflight.</blockquote><blockquote>Bill Nye</blockquote><p>Another 1960’s sci-fi-trope will also become reality. As we see the burgeoning space industry take shape, so will we see the rise of robots in the workplace. Automation is nothing new, but as the costs of robotics drops, technologies like 3D printing are sufficiently advanced and AI becomes even more prevalent, more and more simple tasks will be taken over by advanced automated systems. There is already a burger chain employing robotic patty flippers (a novelty, but a full house novelty nonetheless), and many companies are beginning to employ a 3D print-on-demand service for products and parts. The burger joint of 2030 may well be flipping meat grown without ever having been part of an animal (which raises the ethical dilemma of asking if lab grown meat is still murder?)</p><p>Increased automation in the service sector will also promote the rise of the Super Server. -people working in food &amp; retail who provide a high level of genuine customer service. The ‘vinyl sounds better’ of the service industry.</p><p>The upshot of this is that the nature of blue collar work will continue to evolve. There will be less hands-on work per-se, but there will be an increased demand for people to operate the machines doing the grabbers-on stuff. In the way a carpenter may employ a circular saw to take some of the physical labour out of a job, future workers will be employing machines to do even more. Workers will not be replaced, but they will be seriously upgrading their tools.</p><p>If you combine this with the evolution of AI’s, there is chance that their worker’s mate may well be artificial. Being able to explain the intent of a job to something that can understand the context of the task in the overall plan, will bridge the gap between those with vital hands-on experience and the complex machines that traditionally require a ‘white collar’ programmer.</p><p>And the White Collar workers will also see a shift in their working lives. One interesting prediction is that most Fortune 500 companies will have an AI on the Board by 2030. The question is if a machine that can out-think the finest human Go players is an unfair advantage. Or is the start or AI run mega corporations like Neuromancer’s Tessier-Ashpool?</p><p>Having access to an artificially intelligent co-worker will also have some benefits for the average worker. Again having a automated colleague who can understand intent and content will be an advantage, and since they don’t require a desk it can free up co-workers from physical working constraints, allowing for a greater scope of telecommuting.</p><p>Although it is something that is only just beginning to catch in the US by 2030, many companies will be adopting a more Scandinavian approach to the work life balance (fuelled in part by a new workforce who do not have the same job-for-life/work-to-live attitude as previous generations), providing workers with more opportunities to self manage their working time and environments.</p><p>As attractive as this sounds however, it has been proven even today that working more than 2.5 days out the the office damages your relationships with co-workers, which can lead to a sense of alienation or isolation in the workplace.</p><p>It would appear, that isolation will be a common problem for many people, not just at work, but in their personal lives too, as we we see when we take a look at the society of 2030.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bpkc4HOOZbjxjxGh54k_Rw.jpeg" /></figure><p><strong>Society</strong></p><blockquote>By refocusing our space program on Mars for America’s future, we can restore the sense of wonder and adventure in space exploration that we knew in the summer of 1969.</blockquote><blockquote>Buzz Aldrin</blockquote><p>As we explored in the previous section, Space is big business now, and there is a renewed appreciation of scientific advancement. Whilst not as fetishistic as the 1960’s/70’s, there will be a certain creep of ‘sci-fi’ themes into entertainment, design, fashion etc. In some ways this will be the counter point to the web-weariness of the 2020’s, triggered by the social media &amp; data backlashes of the late 2010’s.</p><p>A new era of Digital Responsibility will have emerged, with a promise to only use technology in a way that won’t hurt others.Studies conducted in the 2010’s identified what were joking dubbed iDisorders, mental health and social issues caused by an overuse of social media or dependance on online communities. These ranged from OCD to narcissism, ADHD, social skills deficit and even addiction.</p><p>In the physical world the densification of urban and suburban spaces means that people are pressed into closer proximity than ever before, but the online generation, choosing to live alone and struggling with social skills, ironically feel a greater sense of isolation.</p><p>This is a problem shared by older citizens in 2030, living longer and retiring just before the cut-off age rose, they are physically fit, and able, and have a great deal of free time, but like retirees from previous generations they can find themselves struggling with feelings of loneliness. A problem that has affected the elderly for many generations.</p><p>The impact of this has been a re-appraisal of how we use digital and online services. No longer are they seen as a primary tool of communication — replacing face to face contact, but instead they will be used to facilitate, real, quality human interaction — a simple need that people had begun to forget they actually need for mental wellbeing. Borrowing again from Scandinavia, the concept of Hygge resurfaces as something of a fad, with people looking to share meaningful moments with relatives and loved ones.</p><p>People will also be attempting to live a life that is both sustainable and balanced, having recognised the importance of not just work/life, but also a web/people balance.</p><p>So social issues, mental health problems and a feeling of isolation? It’s time to move onto healthcare.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*BHxbgUjDpO323H72kOQYfw.jpeg" /><figcaption>We don’t have these yet</figcaption></figure><p><strong>Health</strong></p><p>Despite assurances from numerous start-ups in the early 2000’s, we have yet to have a fully functioning Star Trek tricorder, and medicine is still very much at the cutting-into-people stage, but there will have been some interesting developments.</p><p>Transplant technology has continued to move apace, with over 60 transplants a day being conducted in the US. The first lab grown organ has been transplanted into a human and the use of artificial blood is being trialled by the army and emergency services.</p><p>Advances in emergency medicine are also being made through the widespread use of wearable tech, not just watches or glasses, but ‘smart’ or connected clothing that can provide real-time biometric information to first responders before they even arrive at the scene — allowing them to prioritise patents and prepare treatment en-route.</p><p>Smart medicine also has become a staple of mental healthcare with apps being prescribed the alongside conventional medicine. With health tracking being a staple of smart products and with better personal data management, it is possible to provide personalised, curated programmes for patients, with personally tailored nutritional supplements becoming big business.</p><p>This kind of holistic care is the defining factor of healthcare and personal wellness in 2030. The stigma of mental illness has passed and people are taking their mental health as seriously as their physical health, with gym memberships including meditation and relaxing classes, and mental health trackers joining their step counters.</p><blockquote>There is no health without mental health; mental health is too important to be left to the professionals alone, and mental health is everyone’s business.</blockquote><blockquote>Vikram Patel</blockquote><p>With the issues we discussed previously regarding issues with social skills and a creeping sense of isolation, these positive moves to provide better mental health care as a preventative measure will begin to have an impact, and positive human interaction will be seen as a necessary as the trips to the gym.</p><p>However a healthy mind may not guarantee a healthy body, and there may well be a greater divide between the healthy and the not-so healthy with a 33% increase in obesity prevalence and a 130% increase in severe obesity prevalence from levels today. In other words, more people will be obese, and more people will be more obese.</p><p>The blame for this will be falling on both the education system of previous years and the preponderance of cheap fast food still being attractive to lower income households. Despite the best efforts of TV chefs of the past, and the explosion of meal kit subscriptions, there will still be an ignorance surrounding how to cook healthy homemade meals.</p><p>However. Since we’re writing this future, we have also decided that Taco Bell has gone bust. It’s simply for the good of mankind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m9YyJY1rfDRmNJdNjKDrTw.png" /><figcaption>What if your rating takes a Nosedive?</figcaption></figure><p><strong>Personalisation</strong></p><p>The personalised healthcare mentioned above is just one aspect where tailored, curated services will be the norm, for a user of services in 2030, personalisation will be core to their experience. Generation Z want unique and personalised products — and they want to find them found quickly.</p><p>The International Telecommunications Union has pledged that everyone will have a legal, online ID by 2030. Couple this with the proliferation of blockchain and distributed ledger technologies, and the online profiles and data of 2030 will have a very different landscape.</p><p>A single, unified ID will remove the problem of silo-ed online identities and experiences. Rather than using your social media login to access a personal feed and some entertainment, then your Banking ID for finance and your social security for healthcare and government services; you will be able to access everything from a single point of entry.</p><p>Access to this ID will be unlocked using the owner’s biometric data. A two step process involving fingerprint and another physical attribute — your face, a retina scan or even your gait. A system could recognise you as you walk up to it, pre-load your environment and then only need you to look at it to fully unlock.</p><p>Another exciting possibility is that people may choose to own their own data, having it linked to their online ID and stored in their own Personal Data Exchange rather than owned and controlled by third parties, giving them complete control of their privacy and even the ability to monetise their digital footprint by selling access to service providers in order to provide fully personalised advertising and services.</p><blockquote>“Our online lives currently operate in a provider-centric system, where privacy policies tend to serve the interests of the provider or of a third party, rather than the individual. Using the data they collect, advertising networks, social network providers and other corporate actors are able to build increasingly complete individual profiles. This makes it difficult for individuals to exercise their rights or manage their personal data online. A more human-centric approach is needed, which empowers individuals to control how their personal data is collected and shared.”</blockquote><blockquote>Giovanni Buttarelli</blockquote><p>Alongside this will be a set of global ‘preferences’ and services allowing them to seamlessly transition between digital environments (phone, home, car, work, etc), providing the experience regardless of what piece of hardware they are using. Trying a piece of gym equipment in a different gym? Your workout and settings will have preloaded the moment it recognises your face.</p><p>An interesting addition to an online profile will be that persons ‘scores’, both in terms of social credit, but also in terms of predictability. Whilst Social Scoring may not be prevalent in the West (although there will be ‘unofficial’ systems used), it will be a longstanding process in the East, especially China. Citizens will be graded depending on their behaviour, points being removed for such infractions as bad driving, smoking in non-smoking zones, buying too many video games and posting fake news online. Those whose score dips below a certain level will be penalised with certain measures such as banning them from flying, taking a high speed train, the inability to purchase property and blocking them from jobs of trust and responsibility. ‘Good’ citizens can receive perks such as discounts on energy bills, renting things without deposits, and getting better interest rates at the bank.</p><p>On a slightly less sinister note, the Predictability Index is merely a rating of how easy a persons movements are to predict. With prediction at the core of many AI driven services, how easy it is to define what a person will do will be huge benefit both to providers and consumers. In a society accustomed to pretty much all aspects of their lifestyle being enabled by heavily personalised subscription services. Personal delivery will be key — packages will be delivered to the person, not just their building or car. In order to do this providers will need to know the recipient’s most likely location at time of delivery thus optimising logistics and lowering costs.</p><p>Therefore, the easier it is to predict where somebody will be, the lower the cost will be for their service. A person’s Predictability Index will set the price for a person’s services the way their credit rating determines their APR in the US. So in a weird new semantic paradigm shift, “You’re so predictable” will be a compliment.</p><p><strong>The more things change the more they stay the same.</strong></p><p>So this our future world. Not so drastically different from our world now. Not quite a William Gibson-esque techno-distopia, but not yet utopia either. People’s drivers will still be the same, they will want food, shelter, warmth and work. Interpersonal relationships will have been re-examined and social media will have evolved.</p><p>Space will be cool again and we’ll be looking to the stars, but we’ll be looking inward for better mental health.</p><p>Personal data ownership will be be the norm, and combined with the increase in use of AI and automation, people’s general technical fluency will have increased.</p><p>Young people will be be looking at their life scores alongside their game scores.</p><p>And finally, the recognition that digital relationships are no substitute for real people will also have put paid to those dreams of sex robots, sorry.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c9a91167c43" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wearehumblebee/the-world-of-a-user-in-2030-9c9a91167c43">How will the world of a digital user look in 2030?</a> was originally published in <a href="https://medium.com/wearehumblebee">Humblebee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>