<?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 Ian Franklin on Medium]]></title>
        <description><![CDATA[Stories by Ian Franklin on Medium]]></description>
        <link>https://medium.com/@ian.franklin?source=rss-a9d2ebe543c1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Zx2fJDL7PvB3qdjF.</url>
            <title>Stories by Ian Franklin on Medium</title>
            <link>https://medium.com/@ian.franklin?source=rss-a9d2ebe543c1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:42:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ian.franklin/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[Creating a Coherent User Research Capability]]></title>
            <link>https://medium.com/ideasmiths-blog/creating-a-coherent-user-research-capability-1243cb36bf10?source=rss-a9d2ebe543c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/1243cb36bf10</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Ian Franklin]]></dc:creator>
            <pubDate>Wed, 25 Nov 2020 21:53:21 GMT</pubDate>
            <atom:updated>2020-11-26T09:14:47.199Z</atom:updated>
            <content:encoded><![CDATA[<p>For the forthcoming book User Research Explained I have just published my second chapter summary in a blog. In the chapter I set out what I believe are the essential features of a successful user research capability, what needs to be in place for it to be effective and able to do work and achieve. The first chapter and blog I wrote is on ResOps.</p><p>Rather than repeat the blog here I provide a link. Have a look at the whole User Research Explained publication and please do follow it as more blogs will be appearing soon. For my blog please follow this link:</p><p><a href="https://medium.com/user-research-explained/creating-a-coherent-user-research-capability-8e96af3e683f">Creating a Coherent User Research Capability</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/307/1*sRpFc7S_fZWNmr6V_NQERw.jpeg" /><figcaption>Everyone Working in Harmony</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1243cb36bf10" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideasmiths-blog/creating-a-coherent-user-research-capability-1243cb36bf10">Creating a Coherent User Research Capability</a> was originally published in <a href="https://medium.com/ideasmiths-blog">ideasmiths</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Coherent User Research Capability]]></title>
            <link>https://medium.com/user-research-explained/creating-a-coherent-user-research-capability-8e96af3e683f?source=rss-a9d2ebe543c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e96af3e683f</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Ian Franklin]]></dc:creator>
            <pubDate>Wed, 25 Nov 2020 19:14:54 GMT</pubDate>
            <atom:updated>2020-11-25T19:14:54.551Z</atom:updated>
            <content:encoded><![CDATA[<p>How to set up a vibrant coherent user research capability is a book in itself but here I will just cover four main things which from my experience are key to a successful user research capability.</p><h3>Centralised Finance and Budget</h3><p>With the way that modern projects are organised there seems to be a fashion for user research budgets to be on a by project basis and projects buy user researcher resource time from a central pool and projects have to buy any equipment or services on a as needed basis.</p><figure><img alt="Medieval female and male armourers" src="https://cdn-images-1.medium.com/max/190/1*_Imlura2iJ0oT2wTSI4tAQ.jpeg" /><figcaption>Equipment is essential</figcaption></figure><blockquote>User research needs it own budget to cover equipment, tools and services. Individual projects will not pay for this stuff. User researchers need to be able to deliver from day one on a project.</blockquote><p>There are three big impacts of this style of funding:</p><ol><li>either user research gets left out (because it is not understood)</li><li>or under resourced (because it just seen as ‘having a nice chat’)</li><li>or becomes funded only as far as the warm body of a practitioner leading to a frustrated researcher who has no tools, services, SaaS, routes to users etc.</li></ol><p>I strongly advocate for a centralised user research capability that has its own budget and finance procedures to procure everything that a user researcher needs to deliver within the Agile framework.</p><p>I leave it to organisations to figure out if they then cross charge these services on a cost recovery basis to individual projects or if they fund it from an organisational operational budget. I will say if it is cross-charged then the user research capability should be charged out as the full package of costs and not just a warm body if the profession is its own profit centre. That is projects need to see that a user researcher has to come with all tools, services and infrastructure if they are to be effective.</p><p>In my view a centralised budget is the only way that your capability can grow and deliver a range of services that depend on yearly billing of SaaS, call off contracts for user recruitment and usability lab or other room hire etc. Individual projects will not do this tools procurement from project budgets and even if they do the duplication of effort as many projects procure the same services and tools is not cost effective.</p><p>I have seen places where user research does not have its own centralised budget and it leads to frustrated researchers who can only use a few methods and who have a nightmare trying to make the simplest things happen e.g. hire a room for a usability lab session. In one place the user researchers every 30 days cracked the free trial codes of software because getting individual projects to repeatedly buy it was exhausting. Such frustrations are a good way to lower staff retention.</p><blockquote>Without a budget it can be a nightmare for user researchers to make the simplest things happen</blockquote><h3>Services and Procurement</h3><p>I have mentioned already in the<a href="https://medium.com/user-research-explained/user-research-and-resops-to-infinity-and-beyond-9ce764feedf9"> ResOps blog</a> the kind of software, tools and SaaS that a user researcher might need. In order to get these a user research capability will need to be able to resource a senior/lead/head of user researcher to follow a procurement and contract management process to get these things and to maintain these products and services. As well as someone able to do the contract management a procurement procedure will be needed for both these main contracts and one off purchases for example to hire a usability lab or meeting room in another geographical location if you are doing research around your country.</p><blockquote>You are going to need a head of user research with the clout to do procurement.</blockquote><p>Someone in the user research capability should have the ability to sign off these procurements and contracts. It will really slow down your users researchers if every sprint they have to wait for someone in high authority outside of the project or capability to sign off straight forward purchases. Two week sprints can pass very quickly with inactivity if these procurement activities are blocked. It is unrealistic to expect individual projects to do all of this; what is better a user researcher constantly badgering their delivery manager/SCRUM master to hire a meeting room somewhere for a portable usability lab or the user researcher to be able to get it done through their own user research capability? What will make the user research capability look more slick and professional?</p><figure><img alt="Medieval female blacksmith" src="https://cdn-images-1.medium.com/max/500/1*j5TrNTxs6DKDS30tyyuwnQ.jpeg" /><figcaption>Stoking the Agile furnace</figcaption></figure><blockquote>In fast paced two week Agile sprints user researchers need to live in a world of Yes, not a world of get three quotes.</blockquote><h3>People, Competences and Compensation.</h3><p>A few years back people told me that young people were no longer looking for old fashioned careers with career structures, grading and pay scales. That in the new funky new media internet world that all they wanted was experience and the chance to do cool things at work. This has not been my experience when working with graduate trainees and junior user researchers. People want to know where they fit, what they should be doing, what skills and experience they need to progress and what compensation package could they expect. This is because young graduates going into their first professional jobs all have student loans to repay and aspire to have a home of their own and at work still want a sense of place, achievement and progression.</p><p>I am not saying that you need a gradist organisation with overbearing seniors, a strict hierarchy and compliant juniors happy to do the research note taking and other admin. User research and Agile requires team players at all levels. You do need some grading structure that indicates what people can be expected to do and a competency framework that helps people (leaders, mentors and practitioners of all levels) to understand what training they should be getting and what they need to do next. You will also need a head of user research with the experience to keep all this in place and guide people through it through example and (servant) leadership.</p><figure><img alt="Medieval armouring workshop showing craft workers and woman at a forge" src="https://cdn-images-1.medium.com/max/307/1*sRpFc7S_fZWNmr6V_NQERw.jpeg" /><figcaption>Everyone working in harmony</figcaption></figure><blockquote>People need to be able to understand where they fit, are they doing OK, what can rightfully be expected of them and what do they need to develop and learn.</blockquote><p>It is also important that people understand that to be a senior user researcher has nothing to do with time served or knowing more methods; more methods just makes you a more versatile practitioner. Your user researchers need to know that being senior and above is about thought leadership, stakeholder engagement, and being an effective champion and communicator of the value of user research and the outcomes it can deliver.</p><p>There are vast tracts written on competency modelling and some organisations, especially the public sector, have huge manuals that cover each competency in detail and indicators of the correct behaviour and how to measure them. You don’t need this level of depth but do define what a competency is, what skills it needs and what the indicators and measures are of it being successfully done. The Skills Framework for the Information Age (SFIA) now covers a lot of the user research skills at different levels; it is worth a look for inspiration. User research is a new thing for many organisations and what you want to avoid, and what I have seen in small agencies, is where after a few years the grad trainee or junior from two or three years back starts calling themselves a ‘senior’ when all this indicates is that they have used a couple of methods a lot with varying degrees of success over the last 24 months. A competency model is not a stick to hit people with to stop them getting more money or a tick box exercise to make HR happy. It is about helping people understand where they are in their profession and what they need to achieve next to become better.</p><blockquote>A competency model is not a stick to hit people … it is about helping people understand what they need to achieve next to become better.</blockquote><h3>Centralised User Research Profession</h3><p>For me these three things of</p><ol><li>Centralised Finance and Budget</li><li>Services and Procurement</li><li>People, Competences and Compensation</li></ol><p>Adds up to a centralised user research profession; now this might sound very grand for a small agency.</p><figure><img alt="Medieval journeyman craft workers building a cathedral" src="https://cdn-images-1.medium.com/max/233/1*CpfnzPjlmSScs80UHaAUWg.jpeg" /><figcaption>The User Research guild</figcaption></figure><blockquote>User research is now a profession in its own right</blockquote><p>So lets say it will give you a recognized group of people who are seen as having user research skills and can advise on user research who have the capability to actually do quality user research. In a small agency they also do other things and have other job titles, so will be perhaps your user research community of practice. If things go well it can be grown into a user research profession, a new service that you sell to your clients. If you are a large organisation then you really should be building up a user research profession, the days of user research being a tag on for the UX designer, content writer, front end coder, business analyst really have passed for large corporates. User research is now a profession in its own right and to be honest always was in the fields of mission critical and safety critical systems design (where it was known as ergonomics or human factors).</p><h3>Deploying the User Research Capability</h3><p>The movement of services online has meant that many business processes are now done by the consumer and citizen themselves. Organisational performance is now dependent not on highly trained staff members but the end user; an end user with many demands on their time, distractions and usually other things that they would rather be doing. It is as if the success of your organisation is now dependent on an arm’s length unmotivated selfish ‘employee’ that you cannot manage, train, discipline, or motivate and who can mess up as much as they like and then blame you the boss since they [the customer] are always right.</p><figure><img alt="Medieval female scuptors and masons at work on a castle" src="https://cdn-images-1.medium.com/max/287/1*2NcycKMBKp5OyHgdqL2LIA.jpeg" /><figcaption>From group sessions to delivery</figcaption></figure><blockquote>If you are wondering what users researchers do: if everything is running smoothly with your products and services, your user researchers have done it.</blockquote><p>User research is the key to understanding the needs of this distant ‘employee’; building this intuitive frictionless interface with your services does not happen by magic, although it sometimes looks like magic when it happens. Often the frictionless interface is not noticed at all as there is no grating sound, sparks, heat or smoke, just a smooth quiet continuation. So if you are ever left wondering what it is that your users researchers do, if everything is running smoothly with your complex internet delivered products and services, chances are that your user researchers have already done it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e96af3e683f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/user-research-explained/creating-a-coherent-user-research-capability-8e96af3e683f">Creating a Coherent User Research Capability</a> was originally published in <a href="https://medium.com/user-research-explained">User Research Explained</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Book Chapter — User Research and ResOps: To Infinity and Beyond]]></title>
            <link>https://medium.com/ideasmiths-blog/book-chapter-user-research-and-resops-to-infinity-and-beyond-15bd69ddcecb?source=rss-a9d2ebe543c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/15bd69ddcecb</guid>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Ian Franklin]]></dc:creator>
            <pubDate>Sat, 17 Oct 2020 08:21:52 GMT</pubDate>
            <atom:updated>2020-10-17T08:21:52.082Z</atom:updated>
            <content:encoded><![CDATA[<h3>Book Chapter — User Research and ResOps: To Infinity and Beyond</h3><p>For the forthcoming book User Research Explained we are releasing summaries of the chapters as blogs. A few months back Adrian Murphy who I have worked with approached a load of people about doing a book with the proceeds going towards Covid charities. Other authors include Steve Portigal and Indie Young. I feel humbled to even have any of my random thoughts and scribbles in the same volume as their work.</p><p>We decided that the focus of the book would be for non-user researchers and that its aim would be to illuminate what user research is and what it does. User research can look very odd to technical people, it can seem like some mysterious art full of unfathomable rituals and ceremonies. Also we do weird stuff like talk to actual users, engage with actual users, and try to get under the skin of actual users and understand their full rich complexity and bizarreness.</p><p>My first blog is on Research Operations (ResOps) and there will be another on building a user research capability. Rather than repeat the blog here I provide a link. Have a look at the whole User Research Explained publication and please do follow it as more blogs will be appearing soon. For my blog please follow this link:</p><p><a href="https://medium.com/user-research-explained/user-research-and-resops-to-infinity-and-beyond-9ce764feedf9">User Research and ResOps</a></p><figure><img alt="Research operations diagram from the ResOps community." src="https://cdn-images-1.medium.com/max/1024/1*GgYPZL3zh5wiO60WqeUKvA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15bd69ddcecb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ideasmiths-blog/book-chapter-user-research-and-resops-to-infinity-and-beyond-15bd69ddcecb">Book Chapter — User Research and ResOps: To Infinity and Beyond</a> was originally published in <a href="https://medium.com/ideasmiths-blog">ideasmiths</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Research and ResOps: To Infinity and Beyond]]></title>
            <link>https://medium.com/user-research-explained/user-research-and-resops-to-infinity-and-beyond-9ce764feedf9?source=rss-a9d2ebe543c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ce764feedf9</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[user-research-design]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[researchops]]></category>
            <dc:creator><![CDATA[Ian Franklin]]></dc:creator>
            <pubDate>Thu, 15 Oct 2020 19:20:44 GMT</pubDate>
            <atom:updated>2020-10-15T19:20:44.115Z</atom:updated>
            <content:encoded><![CDATA[<h3>1 Introduction</h3><p>Over the last two years, the discipline of Research Operations (ResOps) has emerged to counter the misunderstanding that user research is easy to do and requires people with few skills, resources and budget. ResOps is about putting all the moving parts in place for a user research capability so that it can be productive and delivery focussed and not constantly overcoming barriers and blockers.</p><blockquote>ResOps is about putting all the moving parts in place for a user research capability so that it can be productive and delivery focussed and not constantly overcoming barriers and blockers.</blockquote><p>If you are a delivery manager, product owner, or one of the more techy roles in Agile development user research can:</p><p>a) Look a bit weird and</p><p>b) Look as if it is made up by user researchers as they go along.</p><p>I am passionate about user research. In my long career, the main reason for IT failure was the failure to meet user needs. I am equally passionate about ResOps because for the first 20 years of my career I had to find my own users, and, for recording data, I had nothing more than a notebook and a pen. As a contractor in the new Internet world, I experienced large organisations that spent a fortune on Big Tech but who thought that, since user research was just ‘having a nice chat with someone’, did not see the need to invest in user research capability.</p><p>I have been asked what is the return on investment of user research and I say infinity; what I mean by that is that a badly designed, unusable system will have an ROI of zero as millions get wasted. Good user research will ensure an intuitive usable service that meets user needs. The equation from zero to something gives you an increase that is a divide by zero; divide anything by zero and you get infinity. So do the math, invest in ResOps and user research and get a ROI of infinity, it seems like a very good deal to me.</p><h3>2 Research Operations (ResOps) — The Moving Parts of a User Research Capability</h3><h3>2.1 Common mistakes of starting user research</h3><h4>The first user research hire is a junior level person</h4><p>This comes from the idea that user research is a nice chat and requires no special skills. Invariably things will go badly as the junior will not be doing real user research but a pale imitation of it.</p><h4>No resources or budget allocated beyond the salary of a single user researcher</h4><p>With no budget allocated there is very little that a user researcher can do beyond running around the shopping centre showing people your designs for ten minutes (guerrilla user research). You will get no quality data.</p><h4>No ethical and methodological framework</h4><p>From the time you design research and start inviting people to come and take part, you have a moral obligation to the psychological and emotional safety of the participant and the researcher. There are research codes that cover these moral obligations.</p><blockquote>From the time you design research and start inviting people to come and take part, you have a moral obligation to the psychological and emotional safety of the participant and the researcher.</blockquote><h3>2.2 What to do to avoid the mistakes</h3><p>To avoid these mistakes you need to set up a user research capability with a ResOps infrastructure. This takes a budget, you are going to have to pony up some hard cash. The capability is the structure and ResOps the moving parts.</p><h3>3 Re+Ops Model</h3><p>The ResearchOps community, setup by Kate Towsey and Emma Boulton, has proposed a model of ResOps. Their diagram is used with permission and is free to use under a Creative Commons license and is presented below. The rest of my blog below summarises the ResOps elements of this model — the moving parts. I summarise the user research capability — the framework within which ResOps operates — in another blog. However, both need each other for successful delivery. For the ResOps community diagram, look here <a href="https://app.mural.co/t/researchopscommunity7839/m/researchopscommunity7839/1539419866773/d21dd2cce77e9e502dcdb46c4abfa7ad8a0aff88">The ResearchOps framework</a> and for the blog here <a href="https://medium.com/researchops-community/a-framework-for-whatisresearchops-e862315ab70d">Kate Towsey Blog</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UPRRP4zuDLyeMJZX" /></figure><p>The aim of a ResOps approach is to enable a user research practice that:</p><ul><li>Is democratic in that the team, the stakeholder and, where necessary, user representatives, can be involved</li><li>Consistently delivers actionable insights</li><li>Delivers through a defensible methodology and justifiable results which will survive scrutiny</li><li>Is logistically smooth in operation</li><li>Is a standardised repeatable methodology</li><li>Is a set of methods appropriately mapped to stages of development</li><li>Has support mechanisms in place</li><li>Can be costed and budgeted</li><li>Has automated tasks where possible</li></ul><h3>4 The Moving Parts of ResOps</h3><p>I like to think of ResOps as being a bit like Lego that can be put together to make many different types of research design to answer many different questions and inform very different design goals. In another blog Emma Boulton describes the 8 pillars of ResOps; here I have summarised the pillars and concentrated on why they are important. For Emma’s blog please look here <a href="https://medium.com/researchops-community/the-eight-pillars-of-user-research-1bcd2820d75a">Emma Boulton 8 pillars of ResOps blog</a>.</p><p>As with Lego, you can make the research equivalent of a car, a spaceship, or a house — but the essential building blocks will be the same. You won’t need every type of brick in every piece of research instead, like the child with the big mixed up box of bits, you will think search through and choose the appropriate bits and customise to fit. Just one word of advice, never leave the ethical research brick out. <strong>NEVER! </strong>Which is why I start with it first.</p><blockquote>As with Lego, you can make the research equivalent of a car, a spaceship, or a house — but the essential building blocks will be the same. You won’t need every type of brick in every piece of research.</blockquote><h3>4.1 Ethical Research Practice</h3><p>We do research by consent with people; we do a form of human research. In order to give informed consent, a participant must be capable emotionally, intellectually and mentally to give consent. Ethical research practices with humans follow international law under the United Nations to prevent crimes against humanity. You must adopt an appropriate ethical framework and may wish to adapt an existing one. In the UK some user research capabilities have adopted the Market Research Society’s (MRS) code of ethics.</p><blockquote>Ethical research practices with humans follow international law under the United Nations to prevent crimes against humanity.</blockquote><p>Very few people wake up in the morning wanting to do bad things and hurt people. Unethical research tends to be done due to:</p><ul><li>Ignorance</li><li>Incompetence</li><li>Naivety</li></ul><p>Don’t turn your user researchers into bad people by accident and omission.</p><blockquote><em>Don’t turn your user researchers into bad people by accident and omission.</em></blockquote><h3>4.2 Research Spaces</h3><p>User researchers need spaces to do their work:</p><ul><li>Places to plan research</li><li>Places to do research</li><li>Places to do analysis</li><li>Places to share insight and collaborate with teams</li></ul><p>Many organisations seem to fill their office spaces with as many desks as possible with very few spaces for meetings and collaborative work. User researchers do their work as part of a creative and collaborative team, they need space for collaboration.</p><p>User research with participants is often done in venues such as dedicated usability labs or, if you have a portable usability lab, in a meeting room with good internet connection. Whether you build your own spaces or go out and hire them, your user researchers need easy access to spaces for research. You need to make it easy for user researchers to book, hire, and pay for specialist spaces. In a two week sprint, you want your researchers to be doing research and not endless procurement paperwork.</p><blockquote>Whether you build your own spaces or go out and hire them, your user researchers need easy access to spaces for research.</blockquote><h3>4.3 Methodology and Methods Playbook</h3><p>A methodology and methods playbook is needed which sets out the approaches to user research that are acceptable for your organisation and users. The playbook should include qualitative and quantitative methods and how they can be used together. The methods will be broadly of two types: exploratory research with people to explore the problem space and testing with users to evaluate the solution space.</p><p>This does not mean that user research practitioners cannot suggest new methods or adapt existing ones; what you want to give people is a playbook they can choose from. The other important thing that the playbook provides is an indication of the outcomes that are expected from each method. The outcomes are important as they will show how the investment in data collection and analysis will inform the design.</p><blockquote>A methods playbook sets out the approaches to user research that are acceptable for your organisation and users and gives an indication of the outcomes that are expected from each method.</blockquote><h3>4.4 Recruitment of Participants</h3><p>With the time constraints of a two-week sprint, the most important thing for a user researcher is to be able to easily access your users. Getting to users that fit a particular profile of interest for that design iteration has to be achieved quickly, and with little bureaucratic fuss. The direct routes that link your organisation to your customers can be difficult for a user researcher to access (marketing and sales departments can be very protective of their contacts), or it would be illegal for them to contact customers for purposes of research because of data processing laws. There are two main routes to your users, but both take time and money.</p><p><strong>i) Market research recruitment agencies: </strong>These can be a surprisingly inexpensive way of finding users. Often they will charge about £80/$100 to find a user with a £40/$50 incentive on top. Given the total cost of a sprint, that you often only need five or six users in a sprint, and they get people that meet your profile for that sprint, this really is quite cheap.</p><p><strong>ii) Internal Teams: Communications, Marketing and Sales, Business Change and Continuity: </strong>Depending on the data processing laws and what your customers have agreed to, these teams can be very good routes to your customers. These teams can be very protective of their contacts, so someone will have to do some stakeholder finessing to get them onside.</p><h3>4.5 Tools</h3><p>User researchers need tools to do their job whether it be software or equipment. There still, oddly, seems to be the idea that nothing special is needed to perform user research. Tools can include such things as: high spec laptop, Cloud services, recording equipment, portable usability lab, remote unmoderated tools, online questionnaire tool, analytics tools that also records user feedback. These cost money and need to be budgeted for.</p><blockquote>There still, oddly, seems to be the idea that nothing special is needed to perform user research.</blockquote><h3>4.6 Supporting Infrastructure</h3><p>User researchers will be collecting a lot of data and insights. All of this data needs to be stored in ways which are:</p><p>i) Secure so you comply with local data processing and retention laws</p><p>ii) Easily searchable and findable so that when in 18 months time someone asks “why did you do that?”, you can find the data that supports the design decision. Your golden thread of design decision making must be clearly articulated in a coherent re-creatable story.</p><p>Needless to say, as user researchers change projects or even leave, you need somewhere that all this is stored. I won’t go into details here but this means two types of solutions:</p><ul><li>Firstly some kind of Cloud-based storage</li><li>Secondly some kind of searchable knowledge repository, Wiki, or collaboration tool.</li></ul><h3>4.7 Governance</h3><p>The governance of ethical research requires the administration of:</p><ul><li><strong>Consent cataloguing and storage:</strong> your research participants consent has to be catalogued and stored so that the wishes of the participant are upheld if they choose to withdraw at a later date.</li><li><strong>Risk assessment of research for participants:</strong> if you have had to do a risk assessment because the participant is vulnerable, has a disability or other issue that causes you concern, then you need to have recorded what decisions you made and the mitigations you took.</li><li><strong>Researcher safety and risk assessment:</strong> similarly, certain types of research, or research with vulnerable service users, may mean that you need to do a risk assessment for your user researchers. For example, in-home should be done in pairs, at least. The research might be exposing user researchers to difficult topics which, with repetition, cause mental health and other issues.</li><li><strong>Data Retention and Data Sharing Laws:</strong> depending where you are in the world, there will be data retention and data sharing laws which your user researchers will need to follow. The participants’ data will need to be anonymised or pseudonymised; and a register needs to be kept of data held and destruction dates.</li></ul><h3>5 Conclusion</h3><blockquote><em>ResOps is not about scale, it is about ensuring that you do the right thing right.</em></blockquote><p>ResOps is not about scale — it is about ensuring that you do the right thing right. Of course, if you are a large corporate with your own rooms for research, budgets for kit, and lots of hires with the job title somewhere of user researcher, I would hope that you are taking a ResOps approach to what you do and how you do it. If you are a small agency, where user research is part of another role, and you are using a cast-off laptop with free recording software to document participant sessions and hire cheap rooms for research, you still need to take a ResOps approach.</p><blockquote>If you are a small agency, where user research is part of another role, you still need to take a ResOps approach.</blockquote><p>Adopting an ethical research code of practice, complying with cybersecurity and data storage privacy laws, having a contract with a market research recruitment agency to get the right participants are all just as important and, for some of these issues, a legal requirement to do. If you do expand you will find it easy to scale up your ResOps as it will have a solid foundation; you won’t have the CEO objection of “we have not done it like this before, this seems like unnecessary cost”, and the good habits will be in place. Furthermore, you will look good against your competitors — when you go for the bigger projects you will look like a professional outfit.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ce764feedf9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/user-research-explained/user-research-and-resops-to-infinity-and-beyond-9ce764feedf9">User Research and ResOps: To Infinity and Beyond</a> was originally published in <a href="https://medium.com/user-research-explained">User Research Explained</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>