<?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 Rose Meredith on Medium]]></title>
        <description><![CDATA[Stories by Rose Meredith on Medium]]></description>
        <link>https://medium.com/@rosemeredith?source=rss-8c83e80ef186------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*x39noYMPM5SxAl3x</url>
            <title>Stories by Rose Meredith on Medium</title>
            <link>https://medium.com/@rosemeredith?source=rss-8c83e80ef186------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:47:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rosemeredith/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[How to… Write a recruitment brief]]></title>
            <link>https://medium.com/@rosemeredith/how-to-write-a-recruitment-brief-88d954242daa?source=rss-8c83e80ef186------2</link>
            <guid isPermaLink="false">https://medium.com/p/88d954242daa</guid>
            <dc:creator><![CDATA[Rose Meredith]]></dc:creator>
            <pubDate>Mon, 15 May 2023 19:18:47 GMT</pubDate>
            <atom:updated>2023-05-15T19:18:47.887Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Usability testing preparation</strong></h4><p>When you are in the preparation phase for a usability test, one of the first tasks is to recruit participants for the study. There are a number of ways you can do this, but if you are free-find recruiting (from their panel rather than a pool of existing contacts) through and external company, you will need to know how to brief them effectively.</p><p>There are a few things you will need for a briefing email. This guide will breakdown the essentials and provide a template to speed up your admin. You may have to add some detail but nobody likes starting with a blank canvas. For the sake of the template, we’re going to imagine we are building a brief for a moderated, remote usability test.</p><p>Firstly, some pointers for what to expect:</p><ol><li>You may not always find the ‘perfect’ participants, but your brief gets you a step closer.</li><li>Know where you can relax, it’s very normal for the recruiters to ask you where the priorities are, if you decide and tell them earlier on, you can reduce the back and forth.</li><li>Near enough every participant you get will give you insight for a usability test, even if they don’t meet your criteria perfectly, be empathetic and grateful for their time, learn what you can and feedback to your partnering recruiters later.</li><li>Remember the lead time, this could range from 2 to 6 weeks depending on complexity, so as soon as you are ready, make recruitment your priority.</li></ol><h3><strong>1. Setting up the brief</strong></h3><p>Highlighted below is an example of the first section of a briefing, the bold areas are where you would need to input project specific information, paired with some examples:</p><blockquote>Hello,</blockquote><blockquote>Hope you’re doing well,</blockquote><blockquote>I have a question around lead time for a recruitment brief (see below) please. We’re aiming to test over a period of <strong>X days</strong> being <strong>Xth, Xth and Xth MONTH</strong>. If you have any questions, please give me a nudge.</blockquote><blockquote>We’re looking to complete some usability testing on <strong>DEVICE (mobile) </strong>using a <strong>WHERE (live site) for WHO (Code ComputerLove)</strong>, each session will be around <strong>LENGTH OF STUDY (1 hour).</strong>The aim of this project is <strong>_____.</strong></blockquote><blockquote>The users will need this link to access the testing, please could you distribute: <strong>ADD LINK</strong></blockquote><blockquote>They can use this link to support in setting upon <strong>TOOL (eg, Teams)</strong></blockquote><blockquote><strong>ADD INSTRUCTIONS FOR TOOL</strong></blockquote><blockquote>Objectives:</blockquote><blockquote><strong>1. Test _____</strong></blockquote><blockquote><strong>2. Review _____</strong></blockquote><blockquote><strong>3. Validate _____</strong></blockquote><blockquote><strong>4. Compare _____</strong></blockquote><blockquote><strong>5. Understand _____</strong></blockquote><blockquote>We will need to talk to a total of <strong>X participants</strong></blockquote><p>This section ensures you are providing key information, such as where, when and why.</p><h3>2. Participant requirements</h3><p>You then need to define who you need for the research study, this information can be sourced via data or existing knowledge (from yourselves or the client)</p><p>The participant requirements can be as specific or broad as you want, it depends on how clear your objectives are and how much existing information you have about the user groups.</p><p>You may have a range of user groups you wish to speak to, which you will have identified when creating your research plan (if you haven’t done this, you can read <a href="https://medium.com/design-bootcamp/research-plans-if-you-fail-to-plan-you-are-planning-to-fail-ce82b5170dd">https://medium.com/design-bootcamp/research-plans-if-you-fail-to-plan-you-are-planning-to-fail-ce82b5170dd</a> for support)</p><p>For the recruitment brief, breaking days down by participant requirements will help the recruiters get a clear view of your expectations.</p><p><em>For example:</em></p><p><em>Day 1: Pure usability testing= 5 new users, not familiar with the site or brand</em></p><p><em>Day 2: Known Experience = 5 current users, who use the site regularly</em></p><p><em>Day 3: Acquisition = 5 In market for X or wishing to switch from X</em></p><p>Below is a template of how this might look, the bold areas are where you would need to input project specific information, paired with some examples:</p><blockquote><strong>Day 1: X journey (eg, Job application process) for 5 <em>new users, not familiar with the site or brand</em></strong></blockquote><blockquote>Requirements</blockquote><blockquote><strong>Needs to be X(aiming to move companies) for X (a new job role) currently, and hasn’t yet made an X (application)</strong></blockquote><blockquote><strong>Female/ Male/ Mix</strong></blockquote><blockquote>Typical customer age group–<strong> age X- X </strong>(we can be flexible with this, treat only as a guide)</blockquote><blockquote><strong>Geographic requirements (UK only, preferably England)</strong></blockquote><blockquote><strong>Language requirements (Must speak English)</strong></blockquote><blockquote><strong>Social grade (A, B, C1)</strong></blockquote><blockquote><strong>Annual household income (between £23- £29K annually)</strong></blockquote><blockquote><strong>Must be a X (creative specialist)</strong></blockquote><blockquote><strong>Must be X (Junior to mid-weight level)</strong></blockquote><p>You can then copy and repeat that template to add in requests for each day required.</p><h3>4. The Formalities</h3><p>You will want to highlight any specific requirements that you have to ensure the sessions run smoothly, these are more formal than the above and act as guidelines for the participation.</p><p>There are no definites for this, and you can chose to be as relaxed or formal as you wish, but they will protect you from paying for a participant that has not followed the guidelines, and is unable to take part.</p><p>An example of some guidelines for the recruitment team:</p><blockquote><strong>Possible session times for reference for each day, please could we ask all participants arrive at least 5 minutes early to tech check their equipment</strong>:</blockquote><blockquote>09.00–10.00</blockquote><blockquote>10.30–11.30</blockquote><blockquote>12.00–13.00</blockquote><blockquote>14.00–15.00</blockquote><blockquote>15:30–16–30</blockquote><blockquote>Also, would you be able to support in handling incentives please?</blockquote><blockquote>We aim to give a £X incentive.</blockquote><blockquote><strong><em>Specific requirements:</em></strong></blockquote><blockquote>Participants must be ok to have the camera on (so we can talk like a normal video call).</blockquote><blockquote>Participants must also consent to being recorded during the session for the purpose of note taking later.</blockquote><blockquote>All participants <strong>MUST</strong> have headphones with a mic as we experience a lot of feedback with lookback otherwise. If they do not have headphones, then depending on how bad the feedback is we may cancel their interview and class as a no-show.</blockquote><blockquote>Participants must ensure the app and WIFI connection works before the session so if they experience any difficulty, we are able to support them beforehand.</blockquote><h3><strong>4. Check and send</strong></h3><p>The last task is to read it over and check with the relevant team(s) involved if you have missed any key information.</p><p>And also, don’t be worried to ask for this feedback, doing it right with lots of voices can be hard and information can be easily missed. You also get to mitigate any issues that might arise later by checking ahead of time.</p><p>As a nice addition, it’s usually good to give the recruitment company 1–2 points of contact form your side, and an opportunity to talk via phone to ensure everyone is clear.</p><h3>Full Template</h3><p>Hello,</p><p>Hope you’re doing well,</p><p>I have a question around lead time for a recruitment brief (see below) please. We’re aiming to test over a period of <strong>X days</strong> being <strong>Xth, Xth and Xth MONTH</strong>. If you have any questions, please give me a nudge.</p><p>We’re looking to complete some usability testing on <strong>DEVICE (mobile) </strong>using a <strong>WHERE (live site) for WHO (Code ComputerLove)</strong>, each session will be around <strong>LENGTH OF STUDY (1 hour).</strong>The aim of this project is ______ so we will require the participants to fit the following:</p><ul><li><strong>Number of Groups of 5 per demographic</strong></li><li><strong>Mindset you need users in</strong></li><li><strong>Demographic detail</strong></li></ul><p>The users will need this link to access the testing, please could you distribute: <strong>ADD LINK</strong></p><p>They can use this link to support in setting upon <strong>TOOL (eg, Teams)</strong></p><p><strong>ADD INSTRUCTIONS FOR TOOL</strong></p><p>Objectives:</p><p><strong>1. Test _____</strong></p><p><strong>2. Review _____</strong></p><p><strong>3. Validate _____</strong></p><p><strong>4. Compare _____</strong></p><p><strong>5. Understand _____</strong></p><p>We will need to talk to a total of <strong>X participants</strong></p><p><strong>Day 1: X journey (eg, Job application process) for 5 <em>new users, not familiar with the site or brand</em></strong></p><p>Requirements</p><p><strong>Needs to be X(aiming to move companies) for X (a new job role) currently, and hasn’t yet made an X (application)</strong></p><p><strong>Female/ Male/ Mix</strong></p><p>Typical customer age group–<strong> age X- X </strong>(we can be flexible with this, treat only as a guide)</p><p><strong>Geographic requirements (UK only, preferably England)</strong></p><p><strong>Language requirements (Must speak English)</strong></p><p><strong>Social grade (A, B, C1)</strong></p><p><strong>Annual household income (between £23- £29K annually)</strong></p><p><strong>Must be a X (creative specialist, who is open to new opportunities)</strong></p><p><strong>Must be X (Junior to mid-weight level)</strong></p><p><em>_Repeat above as needed_</em></p><p>Possible session times for reference for each day, please could we ask all participants arrive at least 5 minutes early to tech check their equipment:</p><p><strong>09.00–10.00</strong></p><p><strong>10.30–11.30</strong></p><p><strong>12.00–13.00</strong></p><p><strong>14.00–15.00</strong></p><p><strong>15:30–16–30</strong></p><p>Also, would you be able to support in handling incentives please?</p><p>We aim to give a <strong>£X</strong> incentive.</p><p><strong><em>Specific requirements:</em></strong></p><p>Participants must be ok to have the camera on (so we can talk like a normal video call).</p><p>Participants must also consent to being recorded during the session for the purpose of note taking later.</p><p>All participants <strong>MUST</strong> have headphones with a mic as we experience a lot of feedback with lookback otherwise. If they do not have headphones, then depending on how bad the feedback is we may cancel their interview and class as a no-show.</p><p>Participants must ensure the app and WIFI connection works before the session so if they experience any difficulty, we are able to support them beforehand.</p><p>For contact please email: Email &amp; Email</p><p>One of us will be available for briefing call when/if you need it!</p><p>Please let me know if there are any questions</p><p>Many thanks</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88d954242daa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Breaking into UX research as a junior]]></title>
            <link>https://medium.com/design-bootcamp/breaking-into-ux-research-as-a-junior-da23917eeca7?source=rss-8c83e80ef186------2</link>
            <guid isPermaLink="false">https://medium.com/p/da23917eeca7</guid>
            <category><![CDATA[graduate-job]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[junior-designer]]></category>
            <dc:creator><![CDATA[Rose Meredith]]></dc:creator>
            <pubDate>Wed, 09 Nov 2022 16:14:21 GMT</pubDate>
            <atom:updated>2023-02-23T05:37:38.855Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Sponge holding pencil- in reference to learning" src="https://cdn-images-1.medium.com/max/468/1*ZcZS5Y2nO3R8pOgPDUDbcQ.png" /><figcaption>Be a sponge</figcaption></figure><p>There’s a never-ending number of articles about individual experiences in the creative world, all giving different perspectives and points of advice on how to be successful and achieve fulfilment in the industry.</p><p>It seems everyone is striving to be a leader, a master of their field, or perhaps even creating their own path into a new innovative job role. However, it feels almost impossible to find an honest reflection on what it’s like to be the junior in the office. For the most part, you’ll find an abundance of lists which define the ‘must-have skills’ to get an entry-level job, or pointless preparation material for the dreaded interview day. What I’m yet to see is a glimpse of a day-to-day junior role and getting started in the industry, so I’m sharing my experiences and reflections here.</p><p><strong>Finding a job: Keeping an open mind</strong></p><p>To start, you need to secure a job, and to do that you need to be proactive. It’s unlikely you will be handed a job at junior level without any effort on your own behalf. I applied for many different roles from the moment I started my master’s degree — even roles that weren’t in the research space, since I considered any design job beneficial to gain experience.</p><p>Around 3 months later I managed to secure two jobs, one which I found on Indeed and the other, the job I am in today, I found via networking on a university trip to the Code Computerlove office. Two very different ways of finding a job, both with their pros and cons, but seeing the actual space and seeing real people face to face really had an impact on how I felt about the role and fuelled my ambition.</p><p><strong>The interview: Attention to detail and self-belief</strong></p><p>After I attended the talk at Code Computerlove, I decided to message the head of research after applying online, and after some discussion I got the opportunity to interview. The interview process was well-structured into 3 sections; an initial phone call, then having to present a portfolio of work, then complete a task related to the role. My advice would be to attend prepared but not scripted.</p><p>The portfolio contained two projects end to end, which showcased as many of the skills, topics, and processes that I thought relevant to the job role as possible. (An example of the type of project work I displayed can be found at: <a href="https://issuu.com/rosemeredith/docs/kelloggs">https://issuu.com/rosemeredith/docs/kelloggs</a> ). I spoke through them in the way you would present back findings to a client, and focused on process more than outcome, which seemed to be received well and allowed the panel to ask more specific questions around decision-making.</p><p>The task was to create a research plan against a brief. Despite being told that it was a simple task that could be done on paper, I tried to make the plan aesthetically pleasing and logical in design. Though this was not necessary, nor suitable for the task’s weight in the real world, it’s the details that get noticed.</p><p>The job role was actually for a senior, but because I displayed character traits that the panel valued, I managed to secure a junior role instead.</p><p>If you take anything from this article, it should be to be persistent and proactive in your search; once you’re in the room, anything is possible.</p><p><strong>Working as a junior: Getting stuck in</strong></p><p>When you start a junior role, you should be continually learning and developing; it’s not helpful to sit in a corner all day taking notes you’ll never review. You should trust yourself and expect your team to push you out of your comfort zone.</p><p>As a junior user researcher, this meant facilitating interviews and tests, presenting findings to clients and the wider team, and having a strong enough view that advocating for the user felt genuine and informed. All of this has taken time and effort to practise, but I have been lucky enough to feel safe and supported in trying and occasionally failing.</p><p>Your job as a junior is to absorb information and practise your skills within the discipline until you’re confident enough to do it alone, so asking questions, getting involved and trying,failing, and learning are an essential part of the process.</p><p><strong>Never be afraid to admit what you don’t know</strong></p><p>Coming from university, with very limited experience in the industry, it’s easy to think you’re qualified enough to push forward without support, likely because you feel that you will look less professional if you ask for help.</p><p>The truth is the exact opposite; I would argue that over 50% of my knowledge and work style has been developed from advice and coaching from people in the workplace.</p><p>Experienced members of the team likely want to support you so they can gain trust and confidence in your ability while you’re learning. It makes for a better culture, opens the floor for feedback and gives others a chance to practise their coaching.</p><p>This also means getting better at receiving criticism; this was never a strength of mine before getting a job in industry, but knowing it comes from a good place is helpful. Remind yourself that the intent will always be improvement — nobody intentionally wants to hurt your feelings.</p><p>Asking and taking advice also develops relationships, which means when you are nervous, you can call or text your fellow cheerleaders at work to calm your thoughts or air whatever it is you’re worried about.</p><p><strong>Levelling up</strong></p><p>As the first few months pass, you should be considering the next steps of your career but be aware of what you need to improve to get there. If you don’t know then you should ask!</p><p>Promotions don’t come simply because you want them; asking your team how you could improve, and looking at the standards around you should guide you on how to move up to the next level. It may also be useful to note that you should strive to preform and behave at the level you aim to be at — this way you can practise and evidence your skills without having to second guess if you are suitable.</p><p>I’ve seen many blogs about not working harder than necessary, and only doing what is required, but if you’re serious about progressing to the next level, that’s not great advice.</p><p>Lastly, gratitude. As a junior you should be grateful for the opportunity, not because you haven’t worked hard to achieve what you have, but because somebody has taken a risk by trusting you.</p><p>Enjoy your time as a junior and remember your main job is to be a sponge, but remember the learning never stops, and that’s what makes this such an interesting path!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da23917eeca7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/breaking-into-ux-research-as-a-junior-da23917eeca7">Breaking into UX research as a junior</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>