<?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 Kevin Rapley on Medium]]></title>
        <description><![CDATA[Stories by Kevin Rapley on Medium]]></description>
        <link>https://medium.com/@kevin-rapley?source=rss-86b6b70b890e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Gw6_35DRZ8atqLsl</url>
            <title>Stories by Kevin Rapley on Medium</title>
            <link>https://medium.com/@kevin-rapley?source=rss-86b6b70b890e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:53:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kevin-rapley/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[Principles Against Neutral User Research]]></title>
            <link>https://kevin-rapley.medium.com/principles-against-neutral-user-research-5d30b572b065?source=rss-86b6b70b890e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d30b572b065</guid>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[ethical-research]]></category>
            <category><![CDATA[user-research-design]]></category>
            <dc:creator><![CDATA[Kevin Rapley]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 21:41:17 GMT</pubDate>
            <atom:updated>2025-12-15T21:41:17.039Z</atom:updated>
            <content:encoded><![CDATA[<p>Neutrality in research is often mistaken for professionalism. In practice, it can obscure harm and protect existing decisions.</p><p>This document sets out a position: research exists to inform judgement, not to legitimise outcomes.</p><h4>Research is not a validation service</h4><blockquote>This is not an obstruction. It is responsible practice.</blockquote><p>Once decisions have been taken, research cannot be expected to endorse them. Running studies under those conditions risks misrepresenting users and evidence.</p><p>Where questions are framed to confirm a preferred direction, this should be made explicit. In some cases, the appropriate research response is to pause, reframe, or advise against proceeding.</p><p>This is not an obstruction. It is responsible practice.</p><h4>Neutral facilitation is not the same as objective research</h4><p>Objectivity does not require silence. Nor does it require avoiding challenge.</p><p>When briefs contain assumptions that place responsibility on users rather than systems, these assumptions should be surfaced and tested. When language minimises risk or harm, it should be examined. Don’t allow harm to be smuggled past scrutiny.</p><p>Professional challenge is a core research skill, not a behavioural failure.</p><h4>Participants are not research inputs</h4><p>Research relies on people giving their time, attention, and, often, personal experience. That creates an obligation of care.</p><p>Methods that rely on sustained emotional labour, distress, or pressure should be reviewed and, where necessary, redesigned. When participant well-being is at risk, a research session should be paused or stopped.</p><p>Ethical research protects participants first. Data quality follows from that.</p><h4>“Edge cases” indicate structural weakness</h4><p>Patterns of repeated difficulty are rarely incidental. They often point to systemic design constraints rather than individual capability.</p><p>Treating these users as marginal risks masks underlying issues that affect fairness, accessibility, and trust. Breakdowns and failures should be treated as priority signals, not exceptions.</p><h4>Pace must not override risk</h4><p>Speed is not neutral. It shapes who succeeds and who struggles. Where time pressure affects outcomes, this should be visible in research findings.</p><p>Where delivery timelines limit the ability to assess risk, this limitation should be clearly stated.</p><p>Rushed evidence tends to increase downstream cost. This includes rework, complaints, and loss of confidence.</p><h4>Insight must have consequences</h4><p>Research outputs that do not inform decisions, trade-offs, or refusals should be questioned. Evidence that is consistently acknowledged but not acted upon is itself a signal.</p><p>Tracking what is not adopted is as important as monitoring what is. This rigour supports transparency and organisational learning.</p><h4>Focus on systems, not individual blame</h4><p>User difficulty should prompt examination of policies, defaults, rules, and incentives. Individualising failure limits the scope of improvement.</p><p>Research should aim to explain how systems produce outcomes, not simply describe user behaviour in isolation.</p><p>This supports more durable and equitable design decisions.</p><h4>Ethics requires judgement, not only process</h4><p>Not all ethical considerations can be resolved through checklists or templates.</p><p>Professional judgement is required, particularly in complex or sensitive contexts.</p><p>Recording uncertainty, trade-offs, and areas of discomfort strengthens accountability. It does not weaken confidence in the research.</p><h4>Research requires independence</h4><p>When research is tightly coupled to delivery pressure, its ability to surface risk is reduced. Maintaining space for independent analysis protects evidence quality.</p><p>Where findings are downplayed, reframed, or excluded, this should be documented and escalated appropriately.</p><h4>Accountability begins with participants</h4><p>The primary responsibility of research is to the people whose experiences inform it. Decisions should be assessed against their likely impact on those users.</p><p>Where evidence suggests increased harm or exclusion, this must be clearly stated, regardless of inconvenience.</p><h3>What this position rejects</h3><ul><li>Research used solely to endorse decisions</li><li>Neutrality used to avoid challenge</li><li>Pace prioritised over safety</li><li>Insight without decision-making impact</li><li>Comfort prioritised over accuracy</li></ul><h3>What this position supports</h3><ul><li>Rigorous methods</li><li>Explicit assumptions</li><li>Clear articulation of risk</li><li>System-level analysis</li><li>Ethical judgement made visible</li></ul><h3>Closing statement</h3><p>Research that avoids discomfort does not become more objective. It becomes less valuable.</p><p>The role of user research in public service is not to reassure systems, but to help them treat people more fairly, more safely, and more honestly.</p><p>That sometimes requires saying no.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d30b572b065" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Respecting Boundaries: The Vital Role of Informed Consent in Research]]></title>
            <link>https://kevin-rapley.medium.com/respecting-boundaries-the-vital-role-of-informed-consent-in-research-47cfa1505f32?source=rss-86b6b70b890e------2</link>
            <guid isPermaLink="false">https://medium.com/p/47cfa1505f32</guid>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[research-ethics]]></category>
            <dc:creator><![CDATA[Kevin Rapley]]></dc:creator>
            <pubDate>Sun, 02 Jul 2023 13:35:41 GMT</pubDate>
            <atom:updated>2023-07-02T13:39:17.668Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v1d3SeFD5_yjaJYiw6J_Xg@2x.jpeg" /><figcaption>Photo by Philipp Wüthrich on Unsplash</figcaption></figure><p>My post is the second in a series on conducting ethical user research. The first post <a href="https://kevin-rapley.medium.com/responsible-research-navigating-the-path-to-ethical-excellence-b138b8c747a9">signposts the topics I shall cover</a> as we navigate this path and find ways to become responsible researchers. I will cover the basics and attempt to explore the less-beaten track of ethics and responsibility.</p><h3>Informed consent is the cornerstone of ethical research</h3><p>Obtaining informed consent from participants engaged in user research is a legal obligation under the Data Protection Act and General Data Protection Regulation (GDPR). Within its context, user researchers must describe ‘the how’ of research, for instance, whether participation happens at or away from a research site. In addition, how data is stored, disposed of, archived and accessed must also be transparent and detailed to participants. Besides being a legal obligation, informed consent should be considered the cornerstone of ethical research. Rather than treating it as a compliance tick box exercise, obtaining informed consent builds an ethical relationship between researcher and participant. In the hands of the participant is placed the power of choice, a feeling of respect and knowing that safeguarding is in place to uphold boundaries.</p><p>A participant must freely give consent without any explicit or implicit coercion. You would think it easy to make inevitable coercion not take place. Physical force or threats, emotional manipulation, deceiving, or providing misleading information are the extremes of coercion that ethical researchers will undoubtedly avoid. Coercive non-compliance to ethics can happen unknowingly when a researcher or research team err due to naivety from lack of experience, wisdom or judgement.</p><p>The coercive pitfalls that research must avoid are:</p><ul><li><strong>Physical force or threats</strong> include physical intimidation, harassment, or threats to the participant’s well-being or safety.</li><li><strong>Emotional manipulation</strong> involves tactics that exploit a participant’s emotions, vulnerabilities, or personal relationships to coerce them into giving consent.</li><li><strong>Deception or misleading information</strong> about the research’s nature, purpose, or potential risks and benefits can undermine the participant’s decision-making.</li><li><strong>Unequal power dynamics</strong> involve a significant power imbalance between the researcher and participant, such as situations where the participant feels obligated to consent due to professional hierarchies, employment relationships, or dependency.</li><li><strong>Financial or material inducements</strong> that offer excessive or disproportionate financial rewards, gifts, or benefits might unduly influence the participant’s decision-making process and compromise their ability to provide voluntary consent.</li><li><strong>Manipulating social or peer pressure</strong> to participate in research by leveraging social norms, expectations, or relationships can undermine the ability to consent freely.</li><li><strong>Withholding relevant information</strong> is a failure to provide participants with all necessary information related to the research, including potential risks and alternative options, which can prevent them from making an informed decision.</li></ul><p>I will write on unequal power dynamics that examine the ethical implications of power imbalances between researchers and participants and strategies to address them in a future post. Avoiding the extremes of coercion detailed in the first three bullet points above, I shall move on to the last three.</p><h3>Financial or material inducements</h3><p>First and foremost, participants should not be offered any incentives before obtaining consent. These inducements may influence their choice if incentives are presented or discussed before obtaining informed consent. For example, a researcher recruits participants to understand the experience of engaging with the Department for Work and Pensions to receive state benefits. The target group may be hard to reach or vulnerable across many factors. The researcher will likely engage with homeless individuals, immigrants and refugees, elderly individuals, people with disabilities, low-income communities, and linguistic or ethnic minorities. An individual may not be willing to participate in the research. However, the researcher presents an incentive before obtaining informed consent that influences their decision for financial gain contradictory to their consent.</p><h3>Manipulating social or peer pressure</h3><p>Inadvertently manipulating or pressuring an individual’s informed consent can be avoided by designing out factors from the research plan. Unfortunately, there are also factors subject to inherent bias skewed by the viewpoints of the research team. These inherent biases, by virtue, are likely unknown. Regardless of the unknown, removing inherent bias from research is critical to ensuring study outcomes’ validity, objectivity, and fairness.</p><p>How can research minimise inherent biases? A self-awareness and education by researchers engaged in continuous reflection, standardised procedures and protocols, a rigorous study design, and a preference toward diversity within the team will help minimise and address inherent bias. I talk broadly as this continuous reflection must happen throughout a study. For our purposes of avoiding manipulation or pressure to allow freely given consent, here are some factors to be mindful of and avoid:</p><ul><li><strong>Excessive group influence:</strong> Avoid creating situations where participants feel pressured to conform to the opinions or actions of a majority. Allow individuals to freely express their thoughts and opinions without feeling coerced by group dynamics.</li><li><strong>Biased framing:</strong> Presenting the research to emphasise the desired response or outcome can unduly influence participants’ decisions. Ensure that information is presented objectively, neutrally, and without bias to avoid manipulating their consent.</li><li><strong>Social approval or disapproval:</strong> Avoid creating an environment where participants perceive their consent or dissent will lead to social judgment, rejection, or adverse consequences. Participants should feel empowered to make decisions based on their judgment, independent of social pressures.</li><li><strong>Authority figures or power differentials:</strong> Be cautious of situations where individuals in positions of authority or power exert undue influence over participants. Minimise power differentials and ensure that participants feel comfortable asserting their autonomy and making independent decisions.</li><li><strong>Peer competition or comparison:</strong> Avoid creating an environment where participants feel compelled to consent due to peer competition or the fear of being left out. Encourage individual autonomy and emphasise that participation is a personal choice.</li><li><strong>Emotional manipulation:</strong> Avoid tactics that exploit participants’ emotions, vulnerabilities, or personal relationships to coerce them into giving consent. Ensure there are no emotional appeals to influence their decision-making process unduly.</li><li><strong>Time pressure or urgency:</strong> Participants should have sufficient time to consider their options, ask questions, and make an informed decision. Avoid imposing unnecessary time constraints that may compromise their ability to give consent freely.</li><li><strong>Misrepresentation of participation rates:</strong> Providing false information about the number of participants who have already consented can create an illusion of social pressure or the need to conform. Present accurate information without manipulating perceived norms.</li></ul><h3>Withholding relevant information</h3><p>Referring back to the Data Protection Act and GDPR, researchers have a legal obligation to inform, provide and uphold the individual rights of participants. These individual rights are:</p><ul><li><strong>The right to be informed</strong>. This GDPR requirement is essential for transparency. The right to be informed relates to collecting and using personal data. A researcher must inform a participant of the purpose of processing any data they provide, how long the research team will retain that data and which individuals they will share it with. Researchers must provide this information to obtain informed consent and reiterate when the data is collected.</li><li><strong>The right to erasure</strong>. Participants have the right to enforce the erasure of their personal data when the data is no longer necessary for its original purposes, when they withdraw their consent, or when they object to legitimate interest or direct marketing processing. Legitimate interest means a reasonable basis where researchers use data in ways that participants would reasonably expect and have minimal privacy impact.</li><li><strong>The right to access</strong>. Participants have the right to submit a Subject Access Request (SAR) for their personal and any other supplementary information to their data. Researchers must respond to a request without delay and within one month. The research team must reasonably search for the requested information and provide it in an accessible format, concise, intelligible and disclosed securely.</li><li><strong>The right to rectification</strong>. Participants have the right to request resolutions of inaccuracies and incomplete information. The same request period and action apply to rectification as the right to access.</li><li><strong>The right to restrict processing</strong>. Participants have the right to restrict the processing of data they provide. However, this right is not absolute. Researchers can refuse when an exemption applies. Exemptions include when the request is</li></ul><ol><li>Purely personal or concerning a domestic household activity</li><li>When a competent authority enforces it by law</li><li>When an intelligence service requires the data for processing</li></ol><ul><li><strong>The right to data portability</strong>.</li><li><strong>The right to object</strong>.</li><li><strong>Rights involving automated decision-making and profiling</strong>.</li></ul><h3>In the next post</h3><p>I will further explore privacy and confidentiality alongside ethical considerations surrounding the collection, storage, and use of user data in research.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47cfa1505f32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Responsible Research: Navigating the Path to Ethical Excellence]]></title>
            <link>https://kevin-rapley.medium.com/responsible-research-navigating-the-path-to-ethical-excellence-b138b8c747a9?source=rss-86b6b70b890e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b138b8c747a9</guid>
            <category><![CDATA[privacy-protection]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[bias]]></category>
            <category><![CDATA[disclosure]]></category>
            <category><![CDATA[ethics]]></category>
            <dc:creator><![CDATA[Kevin Rapley]]></dc:creator>
            <pubDate>Wed, 28 Jun 2023 14:28:27 GMT</pubDate>
            <atom:updated>2023-07-06T18:22:00.580Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AtDLvAsR6kw3L0JNhvB8Ag@2x.jpeg" /><figcaption>Photo by Marija Zaric on Unsplash</figcaption></figure><blockquote>My first article on responsible research you read tells my own story from a generalist unaware of my responsibility through a specialist reflecting upon my practice while navigating the intricacies along the path to ethical excellence. I end by signposting the topics I shall cover as we navigate this path and find ways to become responsible researchers. I will cover the basics and attempt to explore the less-beaten track of ethics and responsibility.</blockquote><h3>The Unaware Generalist</h3><p>Looking back more than ten years ago (closer to fifteen), when I first began to conduct user research activities as a user-centred designer, I was unaware of my responsibility to ensure participant safety, the protection of personally identifiable data, and the steps I must take to stay within the rules of the law in the United Kingdom. My job was as ‘UX Designer.’ At that time, it was an all-encompassing role spanning interaction design, front-end development, visual design, information architecture, and user research. It was typical of the era. We UX Designers were generalists with little time to reflect upon the specifics of any one area of expertise within a project we were tasked with. When I began conducting user research activities, it was also before General Data Protection Regulation (GDPR) came into force across the United Kingdom and Europe to replace the 1995 Data Protection Directive used by European countries. GDPR ushered in new guidelines for data handling in the more connected Internet-powered world.</p><p>My go-to textbook was “Observing The User Experience: A Practitioner’s Guide to User Research” (2003, Morgan Kauffmann) by Mike Kuniavsky. It was and still is an excellent textbook on planning user research, recruiting participants, conducting studies and analysing it. It did not, however, mention how to conduct responsible research – research with an ethical backbone.</p><h3>The User Research Specialist</h3><p>Fast-forward to today, and I specialise in user research. The industry has evolved and matured with dedicated specialisms across the many hats I wore as a generalist UX designer. In my practice, I conduct responsible research. I can reference GDPR and other great sources for principles, policies and guidance on providing research integrity. Regardless, maintaining responsible research and navigating the path to ethical excellence is a moving target that involves establishing a reflective practice, collaboration with participants, and exciting discussions with our peers.</p><p>The topics you and I will consider in the follow-up articles cover the basics and the less-beaten track of ethics and responsibility. I will consider:</p><ol><li><strong>Informed Consent:</strong> <a href="https://kevin-rapley.medium.com/respecting-boundaries-the-vital-role-of-informed-consent-in-research-47cfa1505f32">The importance of obtaining informed consent from participants and how it contributes to ethical user research</a></li><li><strong>Privacy and Confidentiality:</strong> Exploring the ethical considerations surrounding the collection, storage, and use of user data in research</li><li><strong>Bias and Fairness:</strong> Discussing how to identify and mitigate biases in user research, ensuring fairness and inclusivity in the process</li><li><strong>Transparency and Disclosure:</strong> Highlighting the significance of transparently communicating the purpose, methods, and potential implications of user research to participants</li><li><strong>Power Dynamics:</strong> Examining the ethical implications of power imbalances between researchers and participants and strategies to address them</li><li><strong>Vulnerable User Groups:</strong> Exploring ethical considerations when conducting research involving vulnerable user populations, such as children, individuals with disabilities, or marginalised communities</li><li><strong>Data Protection and Security:</strong> Discussing the ethical responsibilities of researchers in safeguarding user data and ensuring secure research practices</li><li><strong>Ethical Data Handling:</strong> Addressing the responsible handling, analysis, and sharing of research data while maintaining participant anonymity and confidentiality</li><li><strong>Impact and Accountability:</strong> Evaluating the ethical impact of user research outcomes and discussing the importance of accountability for researchers</li><li><strong>Participatory Design:</strong> Exploring the ethical benefits and challenges of involving users as active co-designers in the research process</li></ol><p>These topics should provide a solid foundation for discussing various aspects of responsible user research as we navigate the path to ethical excellence.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b138b8c747a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week notes: W/C 12/12/22]]></title>
            <link>https://kevin-rapley.medium.com/week-notes-w-c-12-12-22-88b5d4df471d?source=rss-86b6b70b890e------2</link>
            <guid isPermaLink="false">https://medium.com/p/88b5d4df471d</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Kevin Rapley]]></dc:creator>
            <pubDate>Sat, 17 Dec 2022 13:09:16 GMT</pubDate>
            <atom:updated>2022-12-17T13:09:16.468Z</atom:updated>
            <content:encoded><![CDATA[<p>I completed the first week of my contract as senior user researcher for <a href="https://mojdigital.blog.gov.uk/">Justice Digital</a> at the UK’s Government office, the <a href="https://www.gov.uk/government/organisations/ministry-of-justice">Ministry of Justice</a> (MoJ). I joined a team working on an aspect of <a href="https://www.gov.uk/government/organisations/hm-prison-and-probation-service">His Majesty’s Prison and Probation Service</a> (HMPPS), an executive agency sponsored by the MoJ. The work stream I joined is working on ‘Managing a Workforce’ (MaW). There are three products under our responsibility:</p><ol><li>Allocating people on probation (PoP) to a probation practitioner (PP) via an <strong>Allocation Tool</strong> managed by senior probation officer’s (SPO)</li><li>Measuring the workload of PP’s and capacity to allocate PoP on a national, local, and individual level with a<strong> Workload Measurement Tool</strong> (WMT)</li><li>Setting a level of risk for PoP to reoffend or require safeguarding with a <strong>Tiering Micro-service</strong></li></ol><h4>General MaW team learnings</h4><p>The team’s focus is on the <strong>Allocation Tool</strong> that is in <a href="https://www.gov.uk/service-manual/agile-delivery/how-the-beta-phase-works">private Beta</a>. I arrive into an established team where their existing user researcher is moving to the <a href="https://www.gov.uk/government/organisations/home-office">Home Office</a>. Over this week and next I am receiving a handover to get up to speed with the history of the product and the goals moving forward. The welcome to the team, the documentation to induct me and handover notes and discussions with the existing user researcher have been excellent and thorough.</p><p>There was an expectation from me that I would initially feel overwhelmed by the amount of information I would need to take in. I don’t want to play it down, there is a lot. However, the way the team have engaged me and described the product they are building has helped with a reasonable grasp at this point that I have been able to probe questions and add to discussions in meetings through this week.</p><p>This week I have also tried to meet as many of the team on a 1–2–1 basis as possible. I have a few more to meet next week. I have also been able to identify some potential gaps or problems that have arisen through my identification or talks with people on the team:</p><ul><li>There isn’t a dedicated Service Designer role on the team. It is being picked up in part by the existing User Researcher and Business Analyst.</li><li>At the point where a user research study has been synthesised and data provided back to the team and before designs are developed, the Solutions Architect involvement and collaboration need to be established.</li><li>During the private beta, the team engaged with one location initially and developed the product to meet the requirements of this locality. When engaging with a wholly different location both geographically and urban versus rural topography, ways of working and user needs do not match. The team now needs to iterate upon the product that has moved from prototype through to production code during the first engagement — my gut feeling is having a Service Designer on the team and engaging the Technical Architect at the point of design would have mitigated this problem.</li><li>There isn’t a dedicated Software Tester to provide quality assurance and provide the necessary perspective to consider how the software may be used and check all possibilities to find weaknesses. Regression testing is taking place, but if you are not fully aware of points of weakness throughout the software development lifecycle, regression tests will not be written to uncover those points of weakness. I hear that this isn’t a MaW team problem but a wider MoJ capability that is not fulfilled.</li></ul><h4>User research</h4><p>What I learned yesterday that excites me and causes some apprehension is the scope of the research activities I will be completing within the team. When coming into a project that is in private Beta, it is natural to think research will be evaluative on the prototype and built product. The reality of the situation is:</p><p><strong>Explorative Research</strong></p><ul><li>The <a href="https://www.gov.uk/service-manual/agile-delivery/developing-a-roadmap">roadmap</a> includes areas that are unknown and where we don’t know the user’s needs. For instance, we will need to explore the custody process in relation to MaW for the Allocation Tool and WMT. This will need to be run as a <a href="https://www.gov.uk/service-manual/agile-delivery/how-the-discovery-phase-works">Discovery phase</a> spanning <a href="https://scrumguides.org/scrum-guide.html#the-sprint">several sprints</a>.</li><li>There remains elements of exploration and planning within the current phase of work. These explorative elements are being brought into weekly ‘UCD Pods,’ a user-centred design working group to collaborate on introducing research in this area. The work here is based on real and known user needs.</li></ul><p><strong>Evaluative Research</strong></p><ul><li>As expected, usability testing and system evaluation of the prototype</li><li>Ongoing testing of the developed private Beta platform</li><li>Analysing the analytics and error logs of the private Beta</li><li>Responding to and logging queries from SPO’s and PP’s</li></ul><p><strong>Building relationships with our service users</strong></p><ul><li>Creating support models for ongoing feedback from SPO’s and PP’s</li><li>Maintenance research to understand the best methods of capturing feedback in context through the system</li><li>Onboarding new teams to the private Beta</li></ul><p>There are several modes and areas for getting involved in research. I will need to manage my time to ensure that a balance of explorative and evaluative research is followed. It could be all too easy to get mired in reacting to feedback rather than evaluating the private Beta against established heuristic and ergonomic standards, as well as not dedicating enough time to the explorative research.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88b5d4df471d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week notes: W/C 5/12/22]]></title>
            <link>https://kevin-rapley.medium.com/week-notes-w-c-5-12-22-b0745cfac47a?source=rss-86b6b70b890e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0745cfac47a</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[mindfulness]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Kevin Rapley]]></dc:creator>
            <pubDate>Tue, 06 Dec 2022 15:07:08 GMT</pubDate>
            <atom:updated>2022-12-06T15:10:11.576Z</atom:updated>
            <content:encoded><![CDATA[<p>My first week out of work between jobs. I ended employment with my previous employer on 30/11/22. My role was made redundant due to a downturn in business. For the first time in my career, I shall begin contracting on 14/12/22. I am joining Justice Digital at the Ministry of Justice UK Government department. I join them as a Senior User Researcher within His Majesty’s Prison and Probation Service (HMPPS).</p><p>At the start of the week, I felt wretched with an upset stomach. It wasn’t the best start. I will use these two weeks before the start of my contract to get prepared for Christmas. I’ve wrapped my kid’s presents and will shop for the food and drink needed during the festive period.</p><p>As someone with variable attention stimulus traits and who can struggle with a deficit in self-regulation and attention regulation, I want to prepare myself mentally for the upcoming contract. Medically, I am diagnosed with combined-type ADHD (Attention-Deficit, Hyperactivity Disorder). I learned recently that this label is <a href="https://www.additudemag.com/attention-deficit-disorder-vast/amp/">not a good description of the condition</a>, with <a href="https://www.psychologytoday.com/gb/blog/1-2-3-adhd/202106/why-adhd-should-be-renamed">problematic words such as ‘disorder’</a> and <a href="https://www.healthyplace.com/blogs/livingwithadultadhd/2017/10/is-there-a-better-name-for-adhd">prejudices amounting from its historical labelling</a>.</p><p>My mental preparation will include:</p><ul><li>I am writing a ‘<a href="https://www.manualof.me/">manual of me</a>’ to share with my new colleagues. It is “a simple document which helps you communicate your working preferences, motivations and needs so that we can work better together.”</li><li>Begin writing weekly notes to make sense of work and form a robust reflexive practice. You’re reading my first entry.</li><li>Reflect upon the work I recently began to understand my purpose and values.</li><li>Write more toward the <a href="https://bit.ly/reops-sourcebook">sourcebook of completing Research Operations activities</a>. It will help me to remain in the research headspace and provide a framework for best practices as I commence my new role.</li><li>Be kind to myself and allow time for relaxation, exercise, and play. The bullet points above will be helpful, but I don’t need to be dogmatic in pursuing them.</li></ul><p>That is all for now. I have come to the end of this entry feeling more apparent in my mind and better prepared for having taken the time to note down my thoughts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0745cfac47a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Toward a practitioner sourcebook for Research Operations]]></title>
            <link>https://kevin-rapley.medium.com/toward-a-practitioner-sourcebook-for-research-operations-22a4571b6793?source=rss-86b6b70b890e------2</link>
            <guid isPermaLink="false">https://medium.com/p/22a4571b6793</guid>
            <category><![CDATA[researchops]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[research-leadership]]></category>
            <category><![CDATA[research-management]]></category>
            <category><![CDATA[research-ethics]]></category>
            <dc:creator><![CDATA[Kevin Rapley]]></dc:creator>
            <pubDate>Tue, 22 Nov 2022 16:57:10 GMT</pubDate>
            <atom:updated>2022-11-22T16:57:10.127Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“ A sourcebook to enable all experience levels of ResearchOps will help the profession become more accessible. ”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D0muETkDDCwCUxpt" /><figcaption>Photo by <a href="https://unsplash.com/@mazerone?utm_source=medium&amp;utm_medium=referral">Simone Pellegrini</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I stand on the shoulders of giants who have paved the way for a structured approach to supporting and operationalising user research with Research Operations (ResearchOps). The <a href="https://medium.com/researchops-community">ResearchOps community</a> provide a framework entailing <a href="https://medium.com/p/1bcd2820d75a">eight pillars of user research</a>. Each pillar covers a broad area of focus that needs consideration to fulfil a specific and complete research project. The eight pillars are as follows:</p><ul><li><strong>Environment </strong>— Research strategy is crafted by the environment specifying how an organisation directs and regulates user research, whether it is still untried, inexperienced or mature in carrying it out, and the views of pivotal stakeholders.</li><li><strong>Scope </strong>—Scoping research strategy defines the research’s how, when, reach, impact, process, and methods.</li><li><strong>Recruitment and admin</strong> — A research function needs to decide whether to establish and maintain a database of participants to draw from with enough information to enable ease of participation for each project. Alternatively, whether using a specialist research recruitment agency to provide participants is sufficient.</li><li><strong>Data and knowledge management</strong> — Managing data and knowledge ensures teams know the process for reviewing previous learning, communicating, and centralising project discoveries.</li><li><strong>People</strong> — Ensuring that the people involved in research meet baseline competency and are supported to grow the practice and develop their skillset and knowledge in user research.</li><li><strong>Organisational context</strong> — A vital component of the research strategy is stakeholder management and engagement and determining strategic and policy objectives within an organisation. Stakeholders involved in individual projects, organisational strategy, and policy programmes expect to be informed and provide direction.</li><li><strong>Governance</strong> — Consider research ethics throughout project lifecycles and include information and guidelines on good research conduct and governance that follow all legal and ethical requirements or policies.</li><li><strong>Tools and infrastructure</strong> — Before starting a research practice, get the required infrastructure and procurement details for providing research systems (document templates, ethical review process, non-conformance handling procedures) and tools (hardware, software, subscriptions).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7c5ftjh6DpwHQnCY" /><figcaption>Photo by <a href="https://unsplash.com/@keebarber?utm_source=medium&amp;utm_medium=referral">Keenan Barber</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The pillars give ResearchOps practitioners a broad framework to structure their operations and support for research and researchers. It doesn’t provide detailed rules, guidance, principles and how researchers should conduct research with participants and others involved in or accessing a study. A sourcebook to enable all experience levels of ResearchOps practitioners a point of reference, I feel, will help the profession become more accessible to interested people who want to become a ResearchOps Manager or have greater involvement in operationalising research.</p><figure><img alt="A screen capture of the key for symbols used in the Research Operations Sourcebook with descriptions for rules, guidance, principles, and conduct. A link is provided to the document for access to the descriptions." src="https://cdn-images-1.medium.com/max/1024/1*I_ae-YdzyYXFi86y19br2g.png" /><figcaption>A key to symbols and colours used to communicate rules, guidance, principles, and conduct sections detailed within the ResearchOps Sourcebook.</figcaption></figure><p>In a previous role, I worked for a fashion and home interior retailer, Next. I worked within the e-commerce research and design team that handled customer account registration, management, payment method selection, shopping basket, and payment transactions. Next provide retail finance as a payment option. They call this the ‘Next pay credit account.’ When working with credit accounts and payment transactions with the retailer, I was bound by the <a href="https://www.handbook.fca.org.uk/handbook/CONC/2/2.html">Financial Conduct Authority</a> (FCA) regulations. This financial regulatory body is independent of the UK Government yet works with HM Treasury and is the organisation regulating the financial services industry in the UK.</p><p>I appreciate the <a href="https://www.handbook.fca.org.uk/handbook/GEN/2/1.html">clarity of FCA regulatory documentation</a>, which makes clear a rule that must be adhered to versus guidance that is supplementary or indicates good practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GzoQUM8KyVGvHEIdWuUHSQ.png" /><figcaption>A guidance container to introduce the <em>Organisational Context</em> pillar.</figcaption></figure><p>I adopted the clarity of rules, guidance, principles and conduct used by the FCA in their regulatory documentation for use in the <a href="http://bit.ly/reops-sourcebook">ResearchOps Sourcebook</a>. For ease of referencing a passage in the sourcebook, similar to FCA documents, each pillar uses an abbreviated code. For example, <strong>ORG-CONT</strong><em> </em>abbreviates <em>Organisational Context</em>. Within each pillar, there can be multiple discrete points that help practitioners to meet the pillar. A numerically ordered list following the abbreviated code enables referencing particular passages in the document.</p><p>A general guidance container is used for each discrete point detailing who the section applies to. The container may include further guidance along with rules, principles and conduct sections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kV96cMZ8zFjCjumnLUjKkA.png" /><figcaption>An example of a guidance section within a general guidance container.</figcaption></figure><p>Along with documentation for the eight pillars of ResearchOps, I have enabled references to external regulations crucial to ethical research conduct. For instance, the <a href="https://www.ukri.org/councils/esrc/guidance-for-applicants/research-ethics-guidance/">UK Research and Innovation rules</a> (UKRI) or the Information Commissioner’s Office (ICO) UK <a href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/">General Data Protection Regulation</a> (GDPR).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YJ_RkrODGgxeRFgMjkJ5gg.png" /><figcaption>External regulations that are crucial to ResearchOp’s ethical research conduct.</figcaption></figure><h4>I have started the ResearchOps Sourcebook. I now seek community collaboration to complete and review.</h4><p>Now that I have started on the <a href="http://bit.ly/reops-sourcebook">ResearchOps Sourcebook</a>, I open it up to the community and adopt the principle of working in the open. If you would like to collaborate in writing content, editing, or reviewing, please get in touch, and I shall provide access to the working document.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22a4571b6793" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>