<?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 Hugh Wallace on Medium]]></title>
        <description><![CDATA[Stories by Hugh Wallace on Medium]]></description>
        <link>https://medium.com/@tumshie?source=rss-1c9ea7c8d206------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YA7CDRyP-mawmHfNwXyI-Q@2x.jpeg</url>
            <title>Stories by Hugh Wallace on Medium</title>
            <link>https://medium.com/@tumshie?source=rss-1c9ea7c8d206------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 14 Nov 2026 22:00:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tumshie/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 trouble with innovation]]></title>
            <link>https://medium.com/@tumshie/the-trouble-with-innovation-2b3e4e6b8531?source=rss-1c9ea7c8d206------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b3e4e6b8531</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Hugh Wallace]]></dc:creator>
            <pubDate>Fri, 07 Apr 2023 12:41:30 GMT</pubDate>
            <atom:updated>2023-08-09T06:17:42.712Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>This blog post was first published on the <a href="https://researchdata.scot/blog-trouble-innovation">Research Data Scotland</a> website.</blockquote><p>When I think about innovation, I often cast my mind back to the rise and fall and rise again of the humble QR Code. First invented in Japan in 1994, QR Codes had a bit of a moment in the UK in the early 2010s and then pretty much vanished without trace towards the middle of the decade.</p><p>Suddenly, little chequered squares adorned posters the length and breadth of the land, a technologist’s dream-come-true where the physical and digital worlds connected as one.</p><p>The reality, sadly, was a lot of clunky and disappointing experiences. As it turned out, very few people knew what QR Codes were, let alone how to scan them, and lots of campaigns didn’t even bother tailoring content for mobile devices.</p><p>I reflected on them in a <a href="https://blog.nms.ac.uk/2012/01/04/26-treasures-the-mobile-experience/">blog post I wrote in 2012</a>, where we’d stitched together a solution for a few hundred quid and at least tried to adhere to best practice. But as it turned out, usage and interest peaked around that time, and QR Codes petered out, never to be seen again…</p><figure><img alt="a collage of QR Codes" src="https://cdn-images-1.medium.com/max/1024/0*ZbCQinIsCkblR0NO" /><figcaption>A collage of QR Codes from street posters in Edinburgh City Centre, collected in 2012.</figcaption></figure><p>I jest, of course, and <a href="https://qz.com/1917661/qr-codes-are-finally-having-their-moment-because-of-covid-19">this article in <em>Quartz </em>neatly</a> surmises what happened when Covid took hold in 2020. And while it’s not obvious how much gas is left in the QR Code tank, it at least proves that sometimes the new and shiny tech discovery is worthy of its initial brouhaha.</p><p>This offers a useful segue into the problematic world of innovation and what we’re trying to achieve at <a href="https://researchdata.scot/">Research Data Scotland</a>.</p><p>It’s fascinating to look back at the <a href="https://www.smartinsights.com/digital-marketing-strategy/technology-for-innovation-in-marketing-2/">Gartner Hype Cycle from 2011</a> when QR Codes were supposedly en route to mainstream adoption, and see a number of familiar phrases that – 12 years later – still haven’t really lived up to their early promise, such as Virtual Worlds, Augmented Reality, and Internet of Things. And despite leaps and bounds in terms of technological developments it’s hard to argue that any of them are firmly established. Instead they find themselves caught in some sort of infinite loop, never quite living up to the initial fanfare.</p><h3><strong>FOMO, futurists and funding</strong></h3><p>Stepping back through the various roles I’ve occupied, I’ve had plenty experience where those sort of hype cycles can have a real impact on delivery – on occasion distracting from critical projects, but at worst diverting money, resource and attention away from strategic priorities and unexciting-but-vital things like core infrastructure.</p><p>There are a variety of reasons why this happens within organisations, but from my own experience I’d list the most significant of these as FOMO, futurists and funding.</p><p>FOMO, or the fear of missing out, can be the most irrational of these, and plays to some basic human frailties: <strong><em>others are doing it so why aren’t we?</em></strong> Unpick this a little and you tend to find the grass isn’t always greener on the other side, but if the PR and hype have already taken hold (particularly at the top of organisations) it can become an unstoppable force.</p><p>Futurists – those who pertain to know where things are heading and are often very good at influencing – can shape and spin narratives in a way that isn’t always beneficial. A futurist with the ear of a budget holder may fan the FOMO fire, resulting in incoherent product decisions.</p><p>Funding overlaps lots of the points stated above: it’s often more attractive, newsworthy or (seemingly) finger-on-the-pulse to fund initiatives that are perceived as stretching boundaries, but that can be at the expense of adding actual value.</p><p>For public or third sector organisations like our own, it’s critical that there is a clear-eyed view of how to effect demonstrable change, and to make strategic decisions that aren’t driven purely by technology trends.</p><p>There was an interesting panel discussion at the <a href="https://futurescot.com/futurescot-events/health-care-2023/">Health and Care Transformation conference</a> I presented at last month. Amongst an array of excellent questions from audience members, an important point was made about the consistent application of data standards, and how this could make a tangible difference in terms of impact – making it easier to catalogue, search and utilise data. Yet this is the kind of low-level initiative that’s perceived as an administrative headache, rather than something worthy of funding.</p><p>The same conference threw up multiple references to Artificial Intelligence, certifying that the hype cycle is well and truly alive with AI. AI comes with *many* tricky issues that aren’t necessarily getting the critical analysis they deserve, and one of the current problems is the sheer volume of airtime it’s eating up, smothering everything in its wake.</p><p>For digital old timers like myself, we’ve been here before. NFTs last year, blockchain and crypto the year before, and then a long list of things like big data, robotic process automation, VR headsets and countless mobile apps all blending into one another.</p><p>And the risk here is that important stuff gets left behind. I’m not denying that some of these developments have had valuable and game-changing impact, but the emphasis on innovation shouldn’t always be skewed by the newest shiniest thing.</p><h3>Innovation with a small i</h3><p>We’re endeavouring to put some boundaries around innovation within Research Data Scotland, and making sure our focus is on delivering products that fix real-world problems and don’t distract from our mission at large.</p><p>In <a href="https://medium.com/@tumshie/starting-as-we-mean-to-go-on-31606dff2d47">my previous post</a> I talked about getting the plumbing right, but just as important is the need to ask difficult questions. Does a similar solution already exist? Will it scale? Is the technology futureproof? What are the ethical implications? Have a diverse range of users been consulted?</p><p>As we mature our thinking and plans, these questions will help us put a framework in place to make good decisions about the products and processes we lead with.</p><p>Until then we’ll continue to bring new, improved and (hopefully) ground-breaking services to the research community in Scotland. Just don’t call it innovation.</p><h3>Further reading/listening:</h3><ul><li><a href="https://ez.substack.com/p/degenerative-ai">Degenerative AI</a> — Ed Zitron’s snarky, sweary takedown of a growth-at-all-costs mindset</li><li>The Ada Lovelace Institute has an <a href="https://www.adalovelaceinstitute.org/search/?select-keywords%5B0%5D=ai-policy">excellent array of articles</a> considering the ethics, standards and policy around AI</li><li><a href="https://www.health.org.uk/news-and-comment/podcast/ai-in-health-care-hope-or-hype-with-professor-sir-john-bell-and-dr-axel-heitmueller">AI in health care: hope or hype?</a> This podcast features Sir John Bell and Dr Axel Heitmueller’s thought-provoking views on challenges in health care</li><li><a href="https://medium.com/doteveryone/start-with-values-how-innovation-can-be-bold-fast-and-responsible-799a5629438d">Start with values: How innovation can be bold, fast and responsible</a> — Rachel Coldicutt’s post from 2019 frames the questions we should be asking when we innovate</li><li><a href="https://podcasts.apple.com/us/podcast/why-a-i-might-not-take-your-job-or-supercharge-the-economy/id1548604447?i=1000607834685">Why A.I. Might Not Take Your Job or Supercharge the Economy</a> — Ezra Klein’s podcasts offer a thoughtful, nuanced perspective that’s not always evident iN the rest of the <em>New York Times</em>’ content</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b3e4e6b8531" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starting as we mean to go on]]></title>
            <link>https://medium.com/design-bootcamp/starting-as-we-mean-to-go-on-31606dff2d47?source=rss-1c9ea7c8d206------2</link>
            <guid isPermaLink="false">https://medium.com/p/31606dff2d47</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Hugh Wallace]]></dc:creator>
            <pubDate>Thu, 19 Jan 2023 11:49:07 GMT</pubDate>
            <atom:updated>2023-04-09T06:53:07.130Z</atom:updated>
            <content:encoded><![CDATA[<p>A (relatively) new year feels like an opportune moment to reflect on the progress we’ve been making at <a href="http://www.researchdata.scot/">Research Data Scotland</a> (RDS), and how we’ll be stepping things up a gear as the year progresses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Nr07x2I8bgIH5xME4E44Q@2x.jpeg" /><figcaption>Photo by Nick Fewings on Unsplash</figcaption></figure><p>RDS is still a very young organisation – 2022 was our first full year operating as an independent charity and all but one of our staff have been recruited in the last 12 months. This means we’re piecing together our day-to-day operations, considering how we’ll be working alongside other organisations in the sector, and defining the type of services we need to deliver.</p><h3><strong>Developing a Researcher Access Service</strong></h3><p>A priority has been to develop the thinking and plans around what we’re calling the ‘Researcher Access Service’.</p><p>One of the main reasons that RDS exists is to <strong>simplify</strong> and <strong>speed up</strong> access to public sector data, and in turn enable this data to be used for research purposes in the public good. The Researcher Access Service is being designed to streamline and enhance applications and approvals processes, and offer an end-to-end digital journey for the first time.</p><p>Currently the ways and means of accessing this data (for example, in areas such as health, education, child protection, and justice) is pretty fragmented.</p><p>From a researcher’s perspective, even simple requests can get complicated very quickly, forcing people to work across multiple websites and follow often convoluted processes. From an internal perspective, administration tools are limited and there is no effective means to track and monitor applications.</p><h3><strong>Getting the plumbing right</strong></h3><p>The exciting thing is that we have the opportunity to get the design right before we move into implementation.</p><p>Many of my previous roles have involved rolling out solutions on top of ‘broken plumbing’. This means that as much as you try to work to change legacy systems and broken processes, you’re often left making compromises and introducing workarounds because there isn’t the time, budget, or in many cases the mindset shift, required to make meaningful long-term change happen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8-tpiDueYBXPGzmNfvkRA@2x.jpeg" /><figcaption>Some plumbing, yesterday. Photo by Bruce Warrington on Unsplash</figcaption></figure><p>Making sure we retain a laser-like focus on the fundamental elements that make up the service – the design, infrastructure, cross-organisation agreements, business processes and supporting content – and avoid getting diverted by shiny new tools and platforms is going to be a key challenge for our team.</p><p>This tweet from Ben Terret, formerly of the UK Government Digital Service, neatly encapsulates the point:</p><h3>Ben Terrett on Twitter: &quot;On this Skype call IIRC pic.twitter.com/y0AFRPfcry / Twitter&quot;</h3><p>On this Skype call IIRC pic.twitter.com/y0AFRPfcry</p><h3>Working in partnership</h3><p>We’re in the fortunate position of already having a good chunk of user research and analysis that highlights where some of the issues lie. We also have strong ties with our partners who have a long track record of working in this area, including Public Health Scotland, Scottish Government, Administrative Data Research Scotland, National Records of Scotland and the Edinburgh Parallel Computing Centre.</p><p>We’ve also benefited from the knowledge offered by <a href="https://saildatabank.com/">SAIL Databank</a>, <a href="https://www.healthdatagateway.org/">HDR-UK</a> and <a href="https://www.ons.gov.uk/">Office of National Statistics</a>, all of whom have been very generous with sharing their time and expertise.</p><h3>Embedding best practice</h3><p>We’ll be striving to adopt the principles and best practice outlined in the <a href="https://www.gov.scot/publications/digital-scotland-service-standard/">Digital Scotland Service Standard</a> and <a href="https://www.gov.scot/publications/the-scottish-approach-to-service-design/">Scottish Approach to Service Design</a>, bringing areas like accessibility and security to the fore, and making sure we’re developing the service incrementally.</p><p>To that end we’ve recently engaged <a href="https://www.nexerdigital.com/">Nexer Digital</a> to help deliver the first round of improvements, which includes overhauling and re-platforming our website, prototyping user journeys, and appraising technology options for the full end-to-end service. Bringing the skills and experience they’ve gained from working with clients such as Department of Education, UKRI and Mind, and working in close partnership with our own team, is a big part of getting the right plumbing in place.</p><p>As the service develops, I’ll be attempting to share information on this blog and via RDS’s social channels, so keep your eye out for updates as they happen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31606dff2d47" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/starting-as-we-mean-to-go-on-31606dff2d47">Starting as we mean to go on</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>