<?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 Shira Ben-Cohen on Medium]]></title>
        <description><![CDATA[Stories by Shira Ben-Cohen on Medium]]></description>
        <link>https://medium.com/@shirabc?source=rss-d6ffb7b15d2a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wLAE4xUurmgNQpXiCCL1-Q.jpeg</url>
            <title>Stories by Shira Ben-Cohen on Medium</title>
            <link>https://medium.com/@shirabc?source=rss-d6ffb7b15d2a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:02:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shirabc/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[UX Researcher by training. AI Builder by necessity.]]></title>
            <link>https://medium.com/meliopayments/ux-researcher-by-training-ai-builder-by-necessity-23e86612fc9b?source=rss-d6ffb7b15d2a------2</link>
            <guid isPermaLink="false">https://medium.com/p/23e86612fc9b</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[claude-code]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Shira Ben-Cohen]]></dc:creator>
            <pubDate>Sun, 28 Jun 2026 09:26:30 GMT</pubDate>
            <atom:updated>2026-07-02T09:31:49.572Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*V3Ijn6HbSN9lbLlfNXykJA.png" /></figure><p>If you’re in a non-programmer role like me, and are looking for ways to get started building custom tools with Claude, this post is for you.</p><p>Right now, as I’m writing this, a stakeholder I work with is opening a link in their browser. They’re filling in a form, and when they hit submit, a Request ID gets generated, the row lands in our shared spreadsheet, an email goes out to our team, and a message posts to our UXR team Slack channel.</p><p>Six months ago, that thing didn’t exist. Neither did my ability to build it.</p><p>UX research teams move fast and stay small. Every manual process, every email written by hand, every request tracked in a separate file, takes up time that doesn’t go to actual research. I wanted to build infrastructure that works without me.</p><blockquote>If you’re a UX researcher, this story is yours. If you’re not — the tools may be different, but the problem isn’t.</blockquote><h3>The vision I wrote about</h3><p>Six months ago, I published a<a href="https://medium.com/meliopayments/how-to-scale-ux-research-in-a-fast-moving-environment-practical-guide-4490390e2227"> blog post about scaling UX research</a>. I wrote about intake forms, prioritization systems, and a Gold/Silver/Bronze support model. I described frameworks. I shared a vision.</p><blockquote><em>“My vision for research at Melio isn’t about doing more studies. It’s about building an ecosystem.”</em></blockquote><p>At the time, that was exactly what it was: A vision.</p><p><strong>This is the story of what happened when I decided to actually build it.</strong></p><p><em>(Quick note: Melio was acquired by Xero last year. I’ll keep saying “Melio” in this post because that’s the team identity, but the workspace I’m building in is Xero.)</em></p><h3>The problem I couldn’t ignore</h3><p>The intake form I described in my last post existed, but it lived in a static Google Form. Submissions required manual processing, with no automatic logging. Priority scoring lived in the spreadsheet — separate from the submission experience. With no confirmation to the submitter, and no connection to anything my team actually used.</p><p>Before this tool existed, every research request meant a manual process: duplicating a Google Sheet template, saving it in the right folder, following up with the stakeholder to confirm receipt, tracking it by hand across multiple files.</p><p>Every. Single. Request.</p><p>That’s the kind of time you can’t measure in hours until you stop spending it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*ZQqeAhgVna12afRk3e3ZHg.png" /><figcaption>The original intake form — functional, but entirely disconnected from the team’s workflow.</figcaption></figure><p>What would it look like if this thing actually worked? Not as a concept, but as a real tool. One that runs while I’m on leave. One that stakeholders submit to at midnight and the right people get notified by morning.</p><p>I had no idea how to build that. I’m a UX researcher. I don’t code.</p><p>But I had a problem I genuinely cared about solving. And it turned out that was enough to start.</p><h3>How I thought about solving it</h3><p><strong>Bolt, then Claude Code, and then I hit the same wall twice.</strong></p><p>My mental model was simple: I didn’t need to build a new product. I needed to connect the things that already existed in my work life: the form, the sheet, the email, the Slack channel — in a way that they could talk to each other without me in the middle.</p><p>I tried a few different paths. My first attempt used a vibe coding tool (Bolt) that built the form from a description. Beautiful result. And then our security team declined the integration request because Bolt wasn’t in our approved tool stack, and connecting it to internal systems wasn’t an option. Not a tool problem. A context problem.</p><p>My second attempt used Claude Code — a terminal-based tool where you describe what you need and it writes the code. An hour later I had a working form with correct priority scoring logic. Then I tried to share it with a colleague.</p><p><em>“Where do I open it?”</em></p><p>I didn’t have a good answer. The form existed on my laptop. Nowhere else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*rYXAoPGhVooJcezjgMhX3w.png" /><figcaption>The form built in Claude Code: working logic, correct scoring, zero reach.</figcaption></figure><p>The pattern I kept hitting wasn’t about the code. It was about connection. Every tool I tried could produce the form. None of them could close the gap between “thing that works on my screen” and “thing that lives inside my company’s actual workflow.”</p><p>That gap was the real problem I needed to solve.</p><h3>The moment it clicked</h3><p><strong>Claude Cowork.</strong> That’s what finally changed things — not because the AI was smarter, but because it was <em>connected</em>.</p><p>A few weeks later, I got a license for Claude Cowork: a desktop AI tool wired into my company’s Google Workspace.</p><p>The form moved from a file on my laptop to a live URL any employee at the company could open. No external hosting. No IT ticket. Just a working URL I could send to anyone.</p><p>I sent it to a colleague. She opened it in her browser. On her laptop. Filled it out.</p><p>I was so excited.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*PdvS4gRMpRxQQ9cvSFYplg.png" /><figcaption>The live form, running on Google Apps Script, accessible to any employee via a single URL.</figcaption></figure><p>After that, submissions started landing in our shared Google Sheet automatically. The right columns, the right format, And the right row. But when I tried to add email notifications, I hit a wall I couldn’t get past on my own. I fixed lines of code. Nothing. I tinkered more. Still nothing. I ran the same test fifteen times.</p><p>So, I went to our VP of Engineering.</p><p>I showed him the form, the sheet, and the email logic that wasn’t firing. He asked a few questions and adjusted a few lines around OAuth scopes and the Gmail API manifest.</p><p>The email landed in my inbox.</p><p>Then in the team inbox.</p><p>I watched it happen in real time and felt like I’d witnessed a magic trick — even though Claude and I had built 95% of what made it possible.</p><p>The lesson here isn’t <em>“ask engineers to do it for you.”</em> It’s: <strong>know when you’ve hit the edge of your current knowledge.</strong> It took the right person twenty minutes to fix what would have cost me three more days. That’s not a compromise. That’s how you actually ship.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*gJ3In_tHk4F25uapFuzHCQ.png" /><figcaption>The team notification email, with the full priority breakdown and a direct link to the sheet.</figcaption></figure><p>After that, I connected the form to our team Slack channel — that part I did without asking anyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*UJq0021D83gtwRmjqV9UTA.png" /><figcaption>Every new submission landing in #uxr-requests — priority level and submitter name in the subject line.</figcaption></figure><h3>What the tool actually does now</h3><p>When a stakeholder submits a research request:</p><ol><li>The form calculates a priority score across six dimensions: impact, user centrality, dependency, timeline, alternatives, and strategic alignment</li><li>A unique Request ID is generated automatically: UXR-0062, incrementing safely regardless of row deletions or reorders</li><li>The submission lands in the correct row of our shared team sheet</li><li>A styled confirmation email goes to the submitter</li><li>A notification email goes to the UXR team — all fields, the full priority breakdown, and a direct link to the sheet</li><li>The same notification posts to Slack</li></ol><p>We’re now on Version 18. The whole thing runs on Google Apps Script, with no external server, no hosting costs, and no infrastructure outside of Google’s own ecosystem.</p><p>Now, none of that happens manually. Requests arrive in our inboxes and in Slack. The row is already in the sheet. The ID is already assigned.</p><h3>This is about foundations, not features</h3><p>I want to be clear about something. The intake form isn’t the destination — it’s the infrastructure.</p><blockquote><em>Building it taught me that scaling UX research isn’t just about better frameworks or smarter prioritization. It’s about building systems that work without you. Systems that run at midnight, send their own emails, and don’t require a researcher to be awake and available to receive a request.</em></blockquote><blockquote><em>That’s what I mean when I say ecosystem.</em></blockquote><p>And Phase 2 is already in motion. The next step is connecting these intake submissions to our company Jira — so a research request doesn’t just land in a sheet, it links directly to the product epic it’s meant to inform. When that’s live, the gap between “someone wants research” and “that research is connected to the actual product work” closes significantly.</p><p>One form, one sheet, and one Jira connection. That’s how you build infrastructure for a research function that scales.</p><h3>What I learned</h3><p><strong>1. The hard part is connection, not code.<br></strong> Writing the form was fast. Wiring it to a sheet, two emails, and a Slack channel — that’s where most of the time went. If you’re building something for your team, optimize early for <em>where it has to plug in</em>.</p><p><strong>2. Match the tool to where your work actually lives.<br></strong> My first attempts produced beautiful things that couldn’t connect to anything real. The tool that won was the one already inside my company’s ecosystem. That’s not a coincidence.</p><p><strong>3. Know when to ask for help.<br></strong> Twenty minutes with the right engineer beat three days alone. The version of me that would have insisted on figuring it out solo would still be debugging OAuth scopes today. Pride is expensive.</p><p><strong>4. Ship V1. Then V2. Then V18.<br></strong> Each version had one job: fix the one thing breaking the experience. Not a full rebuild — a targeted fix. That’s how you reach V18 without losing your mind, and that’s how a non-engineer ends up with a production tool.</p><h3>And the vision keeps moving</h3><p><a href="https://medium.com/meliopayments/how-to-scale-ux-research-in-a-fast-moving-environment-practical-guide-4490390e2227">In my last post</a>, I wrote about <strong>research democratization</strong> — PMs, designers, and others running research responsibly with the right training and tools.</p><p>We’ve launched workshops for designers and PMs on running their own unmoderated usability testing. The teams who went through are starting to run their own studies — with our support, but independently. The training pillar isn’t a plan anymore. It’s moving.</p><blockquote><em>Two things are being built at the same time: </em><strong><em>the UXR team’s own infrastructure, and the broader team’s ability to do research themselves. That’s the ecosystem</em></strong><em>: Not one tool, not one training, but both, compounding.</em></blockquote><p>One intake form. Many teams. An ecosystem that’s actually being built.</p><p>If you’re a researcher thinking about building something for your team — start. Even if you don’t know how to yet.</p><p>Let’s see where we are six months from now.</p><h4>About Shira Ben Cohen</h4><p>Senior UX Researcher by day, Design Thinking lecturer by night. Shira holds an MA in Design from UCA and a BA in Social Work. She’s spent the last decade helping companies like Intel and Melio scale their research impact — and recently, build the tools to do it.</p><p><strong>Fun fact:</strong> Shira was an Olympic Torchbearer at the Paris 2024 Olympic Games.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*IpR4EUGGFJT0qQuiJPS1NQ.png" /><figcaption>Shira is carrying the Olympic Torch in Paris Olympic games 2024</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23e86612fc9b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/meliopayments/ux-researcher-by-training-ai-builder-by-necessity-23e86612fc9b">UX Researcher by training. AI Builder by necessity.</a> was originally published in <a href="https://medium.com/meliopayments">Melio’s R&amp;D blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to scale UX research in a fast-moving environment: practical guide]]></title>
            <link>https://medium.com/meliopayments/how-to-scale-ux-research-in-a-fast-moving-environment-practical-guide-4490390e2227?source=rss-d6ffb7b15d2a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4490390e2227</guid>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[melioproduct]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-research-process]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Shira Ben-Cohen]]></dc:creator>
            <pubDate>Sun, 25 Jan 2026 13:10:36 GMT</pubDate>
            <atom:updated>2026-01-25T20:44:54.497Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*s6t40thpyfTOd1XbT5zvCw.png" /></figure><p>Every good UX researcher knows that when demand for research explodes, speed alone isn’t the solution.</p><p>Joining a fast-moving company where UX research is already valued is, in many ways, a dream scenario. There is trust in research, a strong appetite for insights, and high expectations. Teams want to talk to users. They want answers. They want support.</p><p>But very quickly, reality sets in.</p><p>One researcher. Many teams. Dozens of requests.</p><p>The question I found myself asking early on was simple but not easy:</p><p><strong>How do you scale UX research without becoming a bottleneck, and without compromising quality?</strong></p><h3>The “good problem” few companies reach</h3><p>I joined Melio a few months ago, after nearly a decade in a large American corporate environment where UX research had established processes, tools, and dedicated budgets. What I found was an environment of high trust that came with urgent demand. One of the main reasons I chose to join Melio was seeing a genuine appetite for research already present. The infrastructure had been laid, and the value of research was understood. I wasn’t going to spend my time convincing teams <em>why</em> research matters - something many researchers I know still struggle with in other organizations.</p><p>But even ‘healthy’ demand brings its own challenges -high demand quickly turns into volume, a wide variety of needs, and urgency.</p><p>In many startups, and even in some larger companies, research is still perceived as an “extra, nice-to-have luxury. Something you do if there’s time, budget, or the right person around. So when research <em>does</em> exist, and teams actively ask for it, it says a lot about an organization’s maturity. It usually means there is already trust, proven impact, and a shared belief that research improves decision-making.</p><p>I joined as the only UX researcher on the team, as my colleague had gone on maternity leave shortly before I started. I had to hit the ground running. By my tenth day in the role, I had already received three urgent research requests: one foundational study, one tactical usability test, and one concept validation for a new dashboard.</p><p>Shortly after that, during our quarterly planning, I found myself staring at nearly twenty research requests across different domains. I remember feeling genuinely overwhelmed.</p><p><strong>There was so much to consider:</strong></p><p><strong>Prioritization - </strong>How do I choose what to deal with first?</p><p><strong>UXR Support level - </strong>How do I support as many teams as possible?</p><p><strong>Research Democratization - </strong>How do I scale research instead of blocking it?</p><blockquote>In this essay, I will answer each of these questions using frameworks I’ve accumulated over time, shaped by hands-on experience and a lot of learning along the way.</blockquote><h3><strong>Prioritization</strong></h3><h4>Understanding the Ask: Turning requests into strategic dialogue</h4><p>One of the first things I did was introduce a structured intake form that every research request had to go through. It wasn’t complicated, but it forced clarity. Teams were asked to articulate what they wanted to learn, why it mattered, how it would influence a decision or the roadmap, who the target audience was, and what assumptions or hypotheses were in play. Over time, I added more questions to these early conversations. What’s the risk if we <em>don’t</em> do this research? Is it blocking an immediate decision? How broad is the expected impact?</p><p>Each answer mapped to weighted options that helped generate a priority level, from P1 (must do) to P5 (won’t do). It wasn’t perfect, and it wasn’t meant to be rigid, but it created transparency and direction.</p><p>I still remember the first time we used it end-to-end. One research request was canceled altogether when we realized it could be replaced by informal conversations with a few users in that industry to get an initial signal. Another request turned into a quick in-app survey that gave the team useful direction within two days. Other requests were reprioritized or rescheduled. It saved time, reduced noise, and, most importantly, turned vague requests into meaningful discussions. Still, prioritization alone didn’t solve the problem. I kept thinking: <em>What do I do when I have ten P2 requests?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w9-5DL6WKJOiNREPaak1ew.png" /><figcaption><em>Image: Visualization created by Shira with NotebookLM</em></figcaption></figure><h3><strong>UXR support level</strong></h3><h4>A tiered research support model</h4><p>Clear prioritization helped, but it didn’t answer the bigger question of how I could support multiple teams at the same time. That’s when I realized something important: I couldn’t be everywhere, but I could be intentional.</p><p>During that first quarter, I led one foundational, strategic study end-to-end. At the same time, I supported other teams in different ways. For one team, I built the research plan, interview guide, and recruitment strategy, while the PM and designer ran an unmoderated test and analyzed the results themselves. For a more experienced team, I reviewed their interview guide and acted as a consultant while they ran the study independently.</p><p>This is something many researchers do intuitively, but, I remembered a framework I had seen years ago that was publicly shared by the GitLab UX Research team, and decided to use it to formalize practices I was already applying intuitively</p><p>It was a tiered research support model:</p><ul><li><strong>Gold</strong>: End-to-end research ownership</li><li><strong>Silver</strong>: Partial support and targeted execution</li><li><strong>Bronze</strong>: Review, guidance, framing, and feedback</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zur2gw7JgGJtKDixwDNwRA.png" /><figcaption><em>Image: Visualization created by Shira with NotebookLM, based on a framework originally shared by the GitLab UX Research team</em></figcaption></figure><p>I loved it. Putting language around something I was already doing helped set expectations. Teams understood what kind of support they could expect, and I was able to scale my impact. More teams met users, learned faster, and made more informed decisions.</p><p>But a new question quickly emerged:<br><strong>How do you offer Silver or Bronze support to teams that aren’t trained to do research well?</strong></p><h3>Research democratization</h3><h4>Enabling scale while protecting methodological integrity</h4><p>This is where my longer-term vision comes in.</p><p>I believe in empowering <strong>PwDRs</strong>-<em>People who Do Research but are not UX Researchers</em>: Product managers, designers, and others who want to engage with users responsibly, with the right guidance. The goal isn’t to replace researchers. It’s to free them up to focus on the most complex, high-impact, foundational work, while enabling teams to move faster where appropriate.</p><p>The approach I’m working toward for scaling research impact is built on three pillars: <strong>tools, AI, and training.</strong></p><p>One of the most common traps I see is teams starting with a method instead of a question.<br> “Shira, we need a usability test” or<br> “We need a survey.”</p><p>That’s not a research question - that’s a research method.</p><blockquote>Scaling research responsibly means educating teams, for example, on the difference between research goals, research questions, and interview or test questions. Choosing the wrong method wastes time, resources, and often results in data no one can actually use.</blockquote><p>This is why <strong>education</strong> is critical. Teams who will go through structured training, as we plan to execute later this year in Melio, will be certified as <strong>research champions</strong>. They’ll learn how to translate needs into research questions, write screeners, and understand when different methods are appropriate. Only then does it make sense to hand them <strong>tools</strong>.</p><p>We’re already leveraging tools like Maze for unmoderated usability testing and solution validation, and we’re starting to explore <strong>AI-moderated </strong>qualitative tools that allow fast recruiting from panels and early qualitative signals without a live moderator-saving significant time in the research process. These tools don’t replace researchers. They help researchers scale, identify patterns early, and decide where deeper exploration is most valuable.</p><h3>From UXR studies to a research ecosystem</h3><p>I keep thinking of our next steps as a mature UX research organisation, and this vision often comes to mind:</p><blockquote>My vision for research at Melio isn’t about doing more studies. It’s about building an ecosystem.</blockquote><blockquote>One where researchers focus on high-impact decisions, product teams operate with guided independence, and fast tools coexist with deep rigor.</blockquote><p>Research should enable speed - not block it. It’s about taking the appetite we have in Melio for research, prioritizing it well, with the prioritization system designed through strategic questioning, educating teams with tools, leveraging AI when needed, and supporting more and more UXR studies with different support levels (gold, silver, and bronze). This is how we plan to scale research impact. This is my vision.</p><p>Scaling UX research is a design challenge in itself - and this is only the beginning.</p><p>Let’s see where we are six months from now ;)</p><h3><strong>About Shira Ben Cohen</strong></h3><p>Senior UX Researcher by day, Design Thinking lecturer by night. Shira holds an MA in Design from UCA (University of Creative Arts in London) and a BA in Social Work, giving her a unique lens on user empathy. Shira has spent the last decade helping companies like Intel and Melio scale their research impact.</p><p><strong>Fun fact:</strong> Shira was an Olympic Torchbearer at the Paris 2024 Olympic Games, carrying the flame toward the opening ceremony!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6jIGNlzrGbKJMj1sjzHc-w.jpeg" /><figcaption>Shira is carrying the Olympic Torch in Paris Olympic games 2024</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QhMKuclOqFVFffQd.png" /><figcaption><a href="https://bit.ly/jobs-medium">visit our career website</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4490390e2227" width="1" height="1" alt=""><hr><p><a href="https://medium.com/meliopayments/how-to-scale-ux-research-in-a-fast-moving-environment-practical-guide-4490390e2227">How to scale UX research in a fast-moving environment: practical guide</a> was originally published in <a href="https://medium.com/meliopayments">Melio’s R&amp;D blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we have improved the Candidate Rejection Experience at Intel using UX Research Techniques]]></title>
            <link>https://medium.com/@shirabc/how-we-have-improved-the-candidate-rejection-experience-at-intel-using-ux-research-techniques-b2b88159bafa?source=rss-d6ffb7b15d2a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2b88159bafa</guid>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[talent-acquisition]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <dc:creator><![CDATA[Shira Ben-Cohen]]></dc:creator>
            <pubDate>Tue, 02 Jun 2020 16:00:34 GMT</pubDate>
            <atom:updated>2020-06-02T16:09:30.555Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>By Shira Ben-Cohen</strong></p><p><em>Welcome to my 4th blogpost! I’m a</em> passionate Talent Experience Researcher and Strategist working <em>at Intel’s Global Talent Acquisition group. I believe a user-centered approach like Design Thinking and Service Design is the key to an in-depth organizational cultural change and shifting people’s mindsets.</em></p><p>Saying no is hard. It’s difficult for those who say it but even worse for those who hear it.</p><p>Candidates are people, not flat pieces of data captured on a resume. They have desires, dreams, experiences, and emotions. At the end of the day, candidates want experiences that match their expectations, that have been built up by their daily interaction with the consumer marketplace. They also have the need for human connections, to be seen and heard and to feel like unique individuals</p><p>Unfortunately in the Talent Aquisiotn space, we spend more time telling people no than getting to tell them yes. I think it&#39;s fair to say the industry has worked hard to improve the application process experience, the interview experience, and the onboarding experience however we have not done much to advance the experience at the most painful stages of the hiring process, candidate disposition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/1*lt7_WtAdnZtBQ4W_CAD4ig.png" /><figcaption>Designing how we say no is imperative to the business success</figcaption></figure><p>As a Talent Acquisition program manager and a UX researcher who aims to improve our global talent acquisition groups’ ability to attract and hire the best talent for Intel, I am always on the lookout for the new industry trends, trendspotting for innovation and leading programs to enhance the hiring experience for our external customers ( candidates ) and to our internal customers and stakeholders ( recruiters and hiring managers) end to end.</p><p>In this article I am going to share with you my journey from discovering the need to improve the experience at its termination point through the new solution design process I conducted, the development of a core set of design principles and the final output they generated to create a new more human way to tell candidates no.</p><h3><strong>Ready? Let’s start</strong></h3><p><strong>User Experience research</strong> focuses on understanding user expectations, behaviors, needs, and motivations through methodical, investigative approaches. Insights are then used to ensure that all product design decisions benefit the user.</p><p>And this is what I did 😊</p><h3><strong>Data collection and analysis — understanding our candidates</strong></h3><p>The understanding we need to improve the rejection experience didn’t come up in isolation, it arose clearly from the annual candidate survey we participated in designed by the Talent Board, this survey provided us tons of <strong>quantitative and qualitative data</strong> which I collected and synthesized. It was clear that a candidate’s experience was better in relation to how far the candidate progressed in our hiring process but then dropped down dramatically when a candidate was being dispositioned from our process.</p><p>Those red flags together with my <strong>researcher orientation and curiosity</strong> drove me to further investigate users to better understand and uncover what do our candidates feel, think and do when being informed that their candidacy is being removed.</p><h3><strong>Industry and competitors benchmark — feeling like a secret investigator</strong></h3><p>I went deeper. I explored everything written on the internet about “candidate disposition” I was surprised to find out that this area was hardly being discussed and treated in the industry, I wanted to learn from thought leaders about it but there wasn’t much content to consume.</p><p>Luckily I have an extensive network in the Talent Acquisition industry so I have met with friends and colleagues who lead recruiting functions in the most wanted companies and <strong>interviewed them about their rejection process, eager to learn best practices</strong>, how do they say no to candidates, when, what tool do they use and who is responsible for it in their org?</p><p>I asked my engineer friends to send me their past rejection notes from other companies and I captured critical elements that I liked and didn’t like for further use.</p><h3><strong>Empathy is a critical element, meet your customer for a coffee</strong></h3><p>It wasn’t enough for me to read about it or review <strong>survey dashboards</strong>, I wanted to hear real people talk about their feelings and motivations while being interviewed in other companies. I wanted to <strong>empathize with my customers, </strong>understanding how they feel<strong> </strong>so I have reached out to several colleagues and friends who I knew that they are in the job search journey and followed their experiences. I even captured one of them on video.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*zU6Ukrd7Eww62V_L2jgUow.jpeg" /><figcaption><em>Generating empathy with the team before we start to ideate by showing them real candidates interview video</em></figcaption></figure><h3><strong>Analyzing data into insights and Experience Guiding Principles-</strong></h3><p>After collecting tons of data I continued and extract the data into insights, which I framed as <strong>Experience Guiding Principles</strong>. The guiding principles would serve as the north star to focus on as I worked to create a better way to say no.</p><p>1. <strong>Use a Human-Centric approach</strong> — As recruiting, processes become more automated, the importance of keeping human interaction at the center increases.</p><p>2. <strong>Focus on Experience</strong>- Experiences are something you feel and sense. How candidates feel about their recruiting experience is a competitive differentiator. People have the need to be seen and heard, they want to know where they stand and set expectations</p><p>3. <strong>Focus on Emotions to Drive Behaviors:</strong>- Human behavior is driven by emotions. We influence behavior by creating recruiting experiences that elicit emotions, you want your candidates to refer their friends? You want them to apply again? You have to build and maintain a relationship with them, and that means, thinking emotions in the business strategy you plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*52UNABWvDTprYVhljcC2Hg.jpeg" /><figcaption><em>The experience guiding principles serve the larger team to ideate for solutions further in the design process.</em></figcaption></figure><h3><strong>Presentation of Insights-collaborate with holistic teams</strong></h3><p>Designing a new solution is not something you do alone in a vacuum, so my next step was to take the data and turn into three main <strong>personas</strong>, that represent different types of candidates, and share it with a holistic cross-functional team.</p><h4>I conducted and lead a full-day design session focused on:</h4><ul><li>Generating empathy towards our candidates among the larger team</li><li>Presenting design research findings in a clear and organized fashion.</li><li>Envisioning the ideal User Journey using Service Design Blueprint</li><li>Gathering actionable recommendations moving forward</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*Tfr0h1RIkESvIuQAaMFpOQ.jpeg" /><figcaption><em>Starting to uncover the critical touchpoints for candidate rejection using service design blueprint</em></figcaption></figure><h3><strong>Strategy -turn the design into actionable recommendations</strong></h3><p>After working closely with the larger team, each is a subject matter expert in the recruiting world, we made a plan of action that included the following five steps:</p><ol><li>Training recruiters on the “<strong>Investment rule</strong>“, a framework that helps recruiters determine the best way to communicate, or engage, with candidates, which states: “<em>The deeper into the process a candidate goes, the higher touch our communication back to the candidate, should be.”à </em>we inserted this framework into our global training.</li><li><strong>Rewriting the “Thank you for applying</strong> “ notification in a more personal wayàif you apply for a job you’d get the revised version embedding all of our guiding principles in it</li><li><strong>Redesigning the entire rejection notifications</strong> sent out from our ATS ( Applicant Management System) -à See a real example below</li><li><strong>Implementing a new disposition rationale</strong> in our system– recruiters may now select a disposition reason that provides a more personalized message.</li><li><strong>Asking for candidate feedback — </strong>I designed and launched Intel’s first Candidate Experience Survey to help us collect ongoing customer feedback and assess our experienceà ( <em>this requires an additional blog post haha</em> 😊)</li></ol><h3><strong>Our old rejection message:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*tw4d0wAjoZ1znkX9xqhEig.png" /><figcaption>An old notification example before we changed it: Not so personal, lack of empathy, CTA links weren’t updated</figcaption></figure><h3><strong>An example of one of our new </strong>rejection message:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IPMb9LyvRdy-xs26OP8-qQ.png" /><figcaption>How we apply Our Experience Guiding Principles in the new notifications</figcaption></figure><h3><strong>Falling in love with my job</strong></h3><p>One of my happiest moments this year was when I got an email from my peer showing me a letter from one of the candidates who received our new notification saying :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*qgxWQFTN14iUUb8vTsC6zw.png" /><figcaption>This made me smile:)</figcaption></figure><p>That was so exciting for me to hear. This authentic feedback made me fall in love with my job even more 😊</p><p>I hope you enjoyed reading my journey and learned something new! Leave me a comment ‘I’d love hearing your thoughts!</p><p>#UX #UserExperienceResearch #UXResearch#DesignThinking #ServiceDesign #TalentAquisition #RecruitmentMarketing</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2b88159bafa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Taking Talent Transformation a step forward through Design and digital collaboration]]></title>
            <link>https://medium.com/practical-service-design/taking-talent-transformation-a-step-forward-through-design-and-digital-collaboration-4d788b89e523?source=rss-d6ffb7b15d2a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d788b89e523</guid>
            <category><![CDATA[talent-acquisition]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <dc:creator><![CDATA[Shira Ben-Cohen]]></dc:creator>
            <pubDate>Tue, 16 Apr 2019 02:42:01 GMT</pubDate>
            <atom:updated>2019-04-17T05:08:42.348Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Taking Talent Transformation a step forward through Design and Digital collaboration</strong></h3><p><em>This is a guest post by </em><a href="https://www.linkedin.com/in/shirabc/"><em>Shira Ben-Cohen</em></a><em>. Shira is based in Israel and is designing the Global Talent &amp; Hiring partners experience at Intel’s Global Talent Acquisition group. She believes that Service Design &amp; Design Thinking is the key to an in-depth organizational cultural change and shifting people’s mindsets.</em></p><p>As the workforce is dramatically changing, talent leaders and experts need to continue to evolve to stay relevant, increase our employability both internally and externally to our orgs, and continue to attract, hire, and retain the best talent.</p><blockquote><strong>Employability</strong> is one way of saying: stay relevant, develop your day-to-day skills, become better in how you do your work, and take a step forward into and with the future.</blockquote><p>As talent professionals, there are multiple ways to increase our employability and relevancy by learning new techniques to do our job as our profession evolves over time. For example, “classical” recruitment has dramatically shifted into what we call today “<strong>Recruitment Marketing</strong>,” which made us adopt and use more marketing approaches in our day-to-day work by seeing our candidates as customers and our job openings as products.</p><p>However, as talent professionals, there are other ways in which we must evolve our own skillset to stay employable in the ever-changing workforce, and those skills are <strong>Design Thinking </strong>and<strong> Digital Collaboration.</strong></p><p>Let me elaborate about those methods and tools, and showcase to you how we are using it at Intel to create a learning organization and shape our talent processes and professionals.</p><h3><strong>Using Experience Design in the Talent space at Intel</strong></h3><p>In my previous blog posts, I shared <a href="https://blog.practicalservicedesign.com/my-quest-to-bring-service-design-to-my-workplace-37b665cc6556">my journey to bring Service Design to Intel</a> and how we used design techniques to <a href="https://blog.practicalservicedesign.com/using-service-design-to-shape-the-future-of-talent-acquisition-a-new-approach-that-puts-the-4e5523f186a5">shape the future of our Talent Acquisition org at Intel.</a></p><p>GTA (Global Talent Acquisition) org in Intel was the first to implement and use broadly Design Thinking and <strong>Service Design</strong> to shape and improve new processes, adopt new tools, and embed an experience mindset among our talent professionals across the entire talent organization.</p><h3><strong>Like a ripple effect in our Talent org, we started small and expanded bigger</strong></h3><p>If you want to take Experience Design and start using it, remember that big change always starts with small steps. To emphasis this I’d like to share with you our journey of implementing and using design methods in our Talent Acquisition org and how we expanded the usage like a ripple effect:</p><ul><li>We have used Design Thinking principles to improve our <strong>Candidate Experience</strong> in one of our main growth units at Israel, that led to huge growth with amazing feedback from candidates who went through our improved recruiting process.</li><li>We have used Service Design to improve our <strong>diversity hiring</strong> in the US and were able to identify major gaps by visualizing our diversity hiring process and improve it.</li><li>We have leveraged ideation sessions using Service Design to re-imagine our Dispositioning and <strong>rejection experience</strong> globally</li><li>We have used Service Design methods to draw future journeys for our internal employees in the <strong>internal mobility</strong> space</li><li>And lastly but most impactful, we have used it to redesign our future ideal hiring journey for our <strong>Hiring Managers</strong> that kicks off our GTA transformation and forever changed how Intel has doing its recruiting!</li></ul><p>This makes me very proud, as we recognize the benefits of using design methods and expand it to other units in our global Talent Value organization.</p><h3><strong>Wait a minute, what is the difference between Design Thinking and Service Design?</strong></h3><p>I have mentioned Design Thinking here and Service Design, both are part of the overall Experience Design domain. However, what is the difference?</p><p>There are many ways to try explaining the difference and I have found a culinary example to be the clearest and easy to understand. Think of a recipe for a good cake, and now think of actually baking that cake.</p><p>Design thinking is a great methodology with steps, “rules,” values, and principles, such as: co-creation, customer-centricity, ideation, and prototyping etc. It’s the recipe!</p><p>Service Design is the actual art of baking the cake (if the cake was a service that you apply design thinking to). It puts the framework into action and suggests a set of practical tools for you to go and implement the principles, such as Service Blueprinting to visually map an experience, which I am a big fan of.</p><h3><strong>A mini case study: How being ‘customer obsessed’ helped us shape the Hiring Manager’s experience</strong></h3><p>This is no longer new to anyone who is working in the talent world, that Candidate Experience effects hiring and is imperative for the business success. (If you haven’t heard about it, you either new to the talent acquisition world or you were living on the moon :)</p><p>Just as we have carefully improved our Candidate Experience, we have decided to take it a step forward, and as a <strong>customer-obsessed</strong> Talent organization, we started measuring and researching our highly critical audience, the Hiring managers, those who actively screen, interview, hire, and retain our most valuable asset, our talent! What about their experience through the process? How can these design methods help to improve it?</p><p>After extensive <strong>qualitative research</strong>, that included in-depth interviews with hiring managers around the globe, we came to understand what our gaps were and what our hiring managers needed from us as a talent organization.</p><p>We met with a holistic group of professionals from around the globe and together we <strong>ideated and co-created</strong> a new recruiting process, putting the experience first, and from the perspective of our hiring managers.</p><p>One of Service Design’s main tools we used is the <strong>Service Blueprint</strong>. The Blueprint helped us build the process process, step after step, and visually map it using a legend that helps us consider all the elements and components to create our desired experience. You can read more about it in my <a href="https://blog.practicalservicedesign.com/using-service-design-to-shape-the-future-of-talent-acquisition-a-new-approach-that-puts-the-4e5523f186a5">previous blog post</a>.</p><p>We wrapped up this amazing design session with the desired <strong>future journey</strong> on the wall, written on post-its, and we extracted it into a tactical and strategic roadmap. After a year of hard work, we are now in the stage of kicking off global training for our Talent Acquisition org, presenting the new process, mindset and set of behaviors that will take Intel Talent teams a step forward! What excitement!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*hCHo2crwL0_-pzM4" /><figcaption><em>Using service blueprinting to co-create and visualize a new experience</em></figcaption></figure><h3><strong>Digital collaboration enables design #GoDigital ! #UpskillYourself!</strong></h3><p>The above example was one way we have used Service Design to improve our hiring experience, but applying Design Thinking in one session isn’t enough. What will you do with all the information and ideas you came up with the day after if it only lives stuck on your walls?</p><p>Although I adore a good post-it session, this does not work all the time, especially when working globally, when you can’t meet up at the same room and enjoy the benefit of a hands-on design session.</p><p>As design thinking becomes vital to business success, the ability to work creatively from different locations becomes even more critical. This is where a tool like <a href="https://mural.co/">MURAL</a> become relevant.</p><blockquote>Digital collaborative tool allows us more creativity in each meeting and empowers the individual to share their view and design together, virtually, through visual collaboration</blockquote><p>One of the ways you can use this tool is by documenting the new design that gets created in the room, and continue iterating on it after the session ends. You also could share it to all the session participants and keep the conversation going after you complete the first design session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ct7ICg5B4-9imqtaWM_2zg.jpeg" /><figcaption>While ideating with post-its I’m capturing everything digitally</figcaption></figure><h3><strong>The benefits of digital collaborative tools</strong></h3><p><a href="https://www.youtube.com/watch?v=6DLMIzwhAp4&amp;index=1&amp;list=PLDZa1OFNww6Pvi-Mr7j0u093XWZYlVtiK">Mural, </a>a digital, collaborative tool, enables organizations to take each meeting, workshop or team brainstorm a step forward towards a design-driven organization.</p><p>Its benefits are clear:</p><p>1. <strong>Remote collaboration</strong> is a prominent part of work today and MURAL enables remote teams to participate in mutual design sessions equally and creatively while re-architecting the whole talent process. <strong>It sparks new behavior on how we interact with each other at work</strong>.</p><p><strong>2. Keep the momentum</strong> from one meeting to another by automatically saving your visual session in the tool which enables a continuously working experience for you as an individual and as a team.</p><p>3. <strong>Digital whiteboards inspire</strong> your “out of the box” thinking, improve any brainstorm through a live, visual, and up-to-date format that boosts teams’ productivity.</p><p>4. <strong>Empowerment and accountability</strong> are our new mantras; each professional is both empowered to make design decisions when re-architecting the talent experience and are accountable for it. Skype meetings often led by one person, while others are doing emails in the meanwhile, but live whiteboards empowered each participant and enhance the accountability to take forward and implement our own solutions.</p><blockquote><strong>Let’s get upskilled and become more employable by starting to use collaborative tools such Mural for our meetings, brainstorming sessions, and design thinking workshops.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YMxdXV4ytpWug0Ksv5vaEw.jpeg" /><figcaption>Example of a real, completed design session outputs . Now we can share it with our stakeholders</figcaption></figure><h3><strong>Embracing a learning culture to strengthen our employability everywhere</strong></h3><p>Knowing the future of the workforce consists greatly of remote employees, we need to adopt experience design techniques ( Design Thinking &amp; Service Design ) together with digital collaborative tools to transform the ways we work, grow our employability, and ultimately help to build learning organizations.</p><h3>Join the community!</h3><p>Want to learn more about service design? Join over 5,500 members in our free, global <a href="http://www.practicalservicedesign.com/community/">Service Design Community of Practice in Slack</a>. It’s a great place to post questions, share and discover links and resources, and connect with others building their practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*8xQxcPsn30nvCtuU1Be7YQ.gif" /><figcaption>Clap if you liked it!</figcaption></figure><p>You should give this article a 👏🏻 or 50, and follow us on Medium!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*JfuHxQhpVOEJYpQ4n84NZQ.png" /><figcaption>Continue the conversation, and join the global Service Design Community of Practice in Slack at <a href="http://www.practicalservicedesign.com/community">www.practicalservicedesign.com/community</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d788b89e523" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-service-design/taking-talent-transformation-a-step-forward-through-design-and-digital-collaboration-4d788b89e523">Taking Talent Transformation a step forward through Design and digital collaboration</a> was originally published in <a href="https://medium.com/practical-service-design">Practical by Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Service Design to shape the future of Talent Acquisition — A new approach that puts the…]]></title>
            <link>https://medium.com/practical-service-design/using-service-design-to-shape-the-future-of-talent-acquisition-a-new-approach-that-puts-the-4e5523f186a5?source=rss-d6ffb7b15d2a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e5523f186a5</guid>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Shira Ben-Cohen]]></dc:creator>
            <pubDate>Sat, 06 Jan 2018 18:33:41 GMT</pubDate>
            <atom:updated>2018-01-06T18:33:41.613Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_3z1sjps5ryhkq97S9BoFA.jpeg" /></figure><h3>Using Service Design to shape the future of Talent Acquisition — A new approach that puts the experience first</h3><p><strong>By Shira Ben-Cohen</strong></p><p><em>This is a guest post by </em><a href="https://www.linkedin.com/in/shirabc/"><em>Shira Ben-Cohen</em></a><em>. Shira is based in Israel and is designing the Global Talent &amp; Hiring partners experience at Intel’s Global Talent Acquisition group. She believes that Service Design is the key to an in-depth organizational cultural change and the shifting of people’s mindsets.</em></p><h3>. . .</h3><p>On my <a href="https://blog.practicalservicedesign.com/my-quest-to-bring-service-design-to-my-workplace-37b665cc6556">previous blog post</a> I shared <em>my quest in bringing Service Design to my organization</em> and wrote about our first usage of this amazing technique in the Talent Acquisition space.</p><p>I ended my blog post by describing my dream next step…</p><p>I wrote how I want to take Service Design one step further by stepping backwards with our <strong>Business Process Performance</strong> teams that shape the backstage of the recruiting world, and look at when our clients are also our <strong>recruiters and hiring managers</strong>, verses only the candidates.</p><p>Well, guess what? My dream came true :)</p><h3>The Holy Trinity of the hiring sphere</h3><p>We all know the <strong>Candidate Experience</strong> is imperative for the business. Hiring professionals work hard to keep a quality talent pool full and market shows how organizations are shifting and retooling their processes towards candidate experience enhancement.</p><p>But hey, haven’t we forgotten someone else’s experience?</p><p><strong>Hiring managers and recruiters</strong> are key drivers in the candidate experience; in fact they are the enablers of a complete hiring process thus, together with candidates I call them the “Holy Trinity of the hiring sphere”.</p><p>If you want to boost up your talent acquisition organization you should think of <strong>your hiring partners as your customers</strong> too and place <strong>their experience</strong> at the center when designing your overall hiring approach</p><p>Now that you have defined your key customers and got to know their needs, it’s time to take it to the next level in your Experience Design strategy.</p><p>Let me share with you how we started doing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/469/1*h88sIcHMA4hne6eOyyd2GA.png" /><figcaption>Hiring Managers &amp; Recruiters are key drivers in the candidate experience</figcaption></figure><h3>Designing for service, not just process</h3><p>Whether it’s opening a new req, sourcing for talent, or engaging with candidates, all of these are <strong>interactions</strong> that exist between our hiring partners throughout the entire hiring lifecycle, and each interaction is a <strong>service</strong>.</p><p>In the Talent domain, we’re not just selling products (positions), we manage services.</p><p>Often time when we design a process we start with the rules, structure, and policies the org has to meet. This time we switched directions, took those interactions (services) we wanted to enhance and asked, “What do we want our customer experience to be like in those service experiences?”</p><p>This new approach helped us:</p><p>1) <strong>Design for the experience</strong> rather than the process</p><p>2) Design our <strong>future ideal service</strong> rather improve a current one (I’ll elaborate about it more down the road)</p><h3>Talent Acquisition as a stage</h3><p>And here is where the awesomeness of the Service Design methodology comes into play.</p><p>On our first workshop day, and before we dove into the service Blueprinting session, I introduced my colleagues the notion of “The Stage.”</p><blockquote><strong>Talent acquisition world as one whole stage, comprised of 3 perspectives: The Front stage, The Backstage, and The Behind-the-scenes</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Il538u8ZjRts2XsP7_MgDw.jpeg" /><figcaption><em>Service Design Stages, by Practical Service Design — the original</em><a href="https://blog.practicalservicedesign.com/the-difference-between-a-journey-map-and-a-service-blueprint-31a6e24c4a6c"><em> article</em></a></figcaption></figure><p>1. <strong>The front stage</strong> is where the action happens. It’s everything our candidate experiences, what they do and the people they interact with. If you treat the hiring managers and recruiters also as consumers of the talent acquisition service landscape, then they too become front stage actors experiencing different journeys throughout the life cycle.</p><p><em>For example:</em></p><ul><li>The entire candidate journey. Each email they receive, phone call they get from us, or meeting they have, etc.</li><li>It’s any interaction our Hiring managers have with recruiters</li><li>Or any other interaction our recruiters experience along the process</li></ul><blockquote><strong>Three different actors, each of them experience a different journey. Each of them have their own front stage along the hiring process.</strong></blockquote><p><strong>2. The backstage</strong> is where all the support processes live that produce the front stage.</p><p><em>For example :</em></p><ul><li>Our Talent management <em>CRM</em> system that produces forms that our candidates fill when they join our community.</li><li>It’s our Applicant Tracking System ( <em>ATS</em> ) that enable the entire recruitment process management for both our recruiters and hiring managers.</li><li>It’s any other actor that <em>support</em> recruiting efforts such as admin or infrastructure assistant.</li></ul><p>3. <strong>Behind-the-scenes</strong>, where all the intangible things that the organization must do to make both the front and backstage possible. Rules, regulations, policies, budgets.</p><p><em>For example:</em></p><ul><li>Your org hiring <em>budget</em> and workforce planning that you need to follow</li><li>Organizational diversity <em>goals</em> and how it affects your decision making process</li><li>Disability <em>regulations</em> or other country rules like how long a position must be posted externally before you close it etc.</li></ul><p><strong>Understanding the concept of “The stage” before diving into mapping activity allowed us create meaningful conversations while re-imagining our new services. It made us concentrate on our actors experience and not only on our business processes, and leverage the Human Centered approach per se.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TvnX_Jn4Nrhw5HXvUCcTJg.jpeg" /><figcaption><em>Service Design Stages, by Practical Service Design — the original</em><a href="https://blog.practicalservicedesign.com/the-difference-between-a-journey-map-and-a-service-blueprint-31a6e24c4a6c"><em> article</em></a></figcaption></figure><h3>Future states design vs. Current states- How did we do it?</h3><p>Future mappings are based on an “ideal” state for a user type, experience, or a to-be service structure.</p><p>Since we wanted to reinvent how our hiring partners experience would feel in the future, versus mapping the actual “today” state, we gathered a <strong>cross functional group of subject matter experts</strong> from all around the globe.</p><p>Each member with a different expertise, region, and role to make sure we would have the right people with the right skill set, that would represent both their roles in the hiring process and to advocate our three different audience voices. (Yes, the holy trinity of hiring).</p><p>We divided the group into three tracks to work simultaneously, each on a different focus within the hiring process and in each track we started envisioning the new experience…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*6r1QTOqugWP75lpX43WUpg.png" /><figcaption>Designing the ( future )“ideal” hiring process and experience</figcaption></figure><h3>PART 1- Envisioning our Service experiences</h3><p>The 1st day was dedicated to envisioning our future state for our service, using the meat of Service Design, which is off course, the legendary <strong>Blueprint</strong> tool.</p><p>Unlike my previous Blueprinting session, where we took an existing service and mapped it out in order to ideate improvement insights, this time, we started with imagining our ideal service <strong>from scratch</strong>.</p><p><strong>Our base principles were</strong>: creating a seamless process, meaningful relationship, and true partnership with our main stakeholders. These principles guided us throughout our activities.</p><p>We started building our new service, step by step, “<strong>end to-end</strong>,” concentrating on the ‘front-stage’ experience first.</p><p>Then we went mapping the “<strong>surface-to-core” </strong>of the ‘backstage’ and ‘behind the scenes’ components of the service we have just created, using the future-state blueprinting format as our check list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oh6KIA6XvzAX0fxH_07HKA.jpeg" /><figcaption>Blueprinting the future process in action</figcaption></figure><h3>An example</h3><p>Let’s say you build a new process for opening new requisitions. You envision the end to end process, step by step , left to right. And then you start mapping it using the blueprinting legend.</p><p>It could look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*hOSXW9RbTvwUERu8Ai3gmA.png" /></figure><p><strong>Finished the first step? Great, now move to the next one.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*r-Ocm6segPVKIZry908K2g.jpeg" /><figcaption>We had the blueprint legend printed with us</figcaption></figure><h3>Digital vs. Analog</h3><p>While sticky notes are the tool of choice of every designer and fun to use, at this session I took some time to explore a digital way to replace the analog Post-it notes technique we all love.</p><p>Yes, stickies make teams work with their hands, get up, and be creative, and I love sticky notes, I really do, it is also always looks so nicely and impressive on walls when you conclude a full day workshop… But…</p><p>There are digital tools today that allow you the same creativity, collaborative work! It also let you <strong>document in real time</strong> all that is being produced, and most important, you can continue the work from the same point you have ended it and <strong>follow up with your teams</strong> when you are not at the same room anymore, not to mention the same region.</p><p>I tried <a href="https://mural.co/">Mural</a> this time to document our work and I LOVED it. I am definitely going to adopt it for any future session I conduct!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/1*2P9xnGz78XGuLftG_JGAGg.jpeg" /><figcaption>Our digital blueprint map on Mural-beautiful visualization</figcaption></figure><h3>PART 2 — Defending the Experience</h3><p>On our 2nd day of this workshop we got the three groups together, to share and look at the blueprinting outputs from the three separate tracks.</p><p>Each team represented and articulated their own flow, based on the specific scenarios they have assigned to redesign.</p><p>The entire group could put up their questions, thoughts, concerns while the representing groups had to <strong>defend</strong> their outputs and when needed, based on the feedback received, the flows got refined, altered and ratified while captured items requiring deeper next level work.</p><p>Our next step was to prioritize all of our ideas into an <strong>actionable &amp; strategic plan</strong> and build our future Talent Acquisition <strong>road map</strong> and bring it back to the organization.</p><p>It was fascinating to see how the teams quickly adopted the <strong>experience mindset</strong> and the service design terminology (“Actors”, “Front stage”, “Backstage” and” Experience”) when presenting and sharing their work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vD-c7upRvU5zYOUPB26lVw.jpeg" /><figcaption>On the Second day Each team represented their own flow, based on the specific scenarios they have assigned to redesign.</figcaption></figure><h3>Turning into a Design-Driven Organization</h3><p>True. Transforming your org into a design-driven organization takes time, but those small steps, one after another are taking us forward in embedding our cultural mindset to become a <strong>Customer Centric company</strong>.</p><p>I’m so proud of my managers and my company to embrace new disciplines such as Service Design into our process design work, and I’m so lucky to be able to bring Service Design and be part of this transformation we already starting to see in our Global Talent Acquisition organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e02TwP4lsY9RBgmAIvw5CQ.jpeg" /></figure><h3>Takeaways</h3><p>1. <strong>The world’s a stage, and every element in it counts</strong>. When driving change, don’t think just about your end users, think about all actors that enable the action to happen, set the background for the working teams to understand “The Stage “concept before you start designing together.</p><p>2. <strong>Start with the desired experience, then move backwards to the processes </strong>— leave aside everything you used to do when designing how you want things to happen in your business workflow. Think about your customers, what are their needs and start from there. Don’t worry for the systems you have to use, or the rules you need to follow, they would incorporate into your new model, and you might even think of other touchpoints you want to add that never there before.</p><p>3. <strong>Dare to imagine your future ideal state-</strong> Current-state mapping is great, don’t get me wrong, but there are certain situations that it’s not enough. YES, it’s much harder to map workflows that don’t exist, but totally needed when driving inherent improvements.</p><p>4. <strong>Move forward, go digital</strong>. I know it might sound obvious to many of you, but to those who still feel the sticky notes are our best friends to encourage certainty and engagement in workshops, I strongly recommend a collaborative digital tool, such as Mural. This makes life so much easier.</p><p>5. <strong>Dream Big. Start small</strong>. Using Service Design to rethink our hiring processes didn’t happen in a day. If you want to start using Service Design in your org and see your company shifted it culture to be more design driven , start with small steps, tiny scenarios, interested supportive stakeholder etc. and it would take you further.</p><p><strong>But don’t forget to dream big :)</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e5523f186a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-service-design/using-service-design-to-shape-the-future-of-talent-acquisition-a-new-approach-that-puts-the-4e5523f186a5">Using Service Design to shape the future of Talent Acquisition — A new approach that puts the…</a> was originally published in <a href="https://medium.com/practical-service-design">Practical by Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My quest. My inspiration. My story of introducing service design]]></title>
            <link>https://medium.com/practical-service-design/my-quest-to-bring-service-design-to-my-workplace-37b665cc6556?source=rss-d6ffb7b15d2a------2</link>
            <guid isPermaLink="false">https://medium.com/p/37b665cc6556</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[service-blueprinting]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Shira Ben-Cohen]]></dc:creator>
            <pubDate>Wed, 03 May 2017 17:23:26 GMT</pubDate>
            <atom:updated>2017-05-05T06:26:33.985Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3FYDp8s9_4TCjOGKHpYIw.jpeg" /></figure><p><em>This is a guest post by </em><a href="https://www.linkedin.com/in/shirabc/"><em>Shira Ben-Cohen</em></a><em>. Shira is based in Israel and is designing the Global Talent &amp; Hiring partners experience at Intel’s Global Talent Acquisition group. She believes that Service Design is the key to an in-depth organizational cultural change and the shifting of people’s mindsets.</em></p><p>Given my professional background — Talent Acquisition Business Partner in the technology sector — I feel lucky to live in an era of dramatic changes. Above all, the recruitment world has shifted toward a recruitment marketing world which its main principle is a <strong>Candidate Centric Approach</strong>. Simply put, in today’s tech world, employers must consider their candidates as consumers. And consumers expect the services brands provide them to be <em>seamless, authentic and delightful .</em> This insight led me to explore the recruitment marketing aspects, and also led me to my current position at Intel in Israel and part of a global team.</p><p>Part of my responsibility at Intel is looking for new and innovative approaches and strategies for attracting more quality talent into our organization, both from our consumers eyes (leads and candidates) and our hiring partners eyes (recruiters, hiring managers etc.).</p><p>I am now officially doing what was previously based on professional curiosity.</p><h3>So excited that I had to clear my throat from the threatening tears of joy</h3><p>Diving deeper in online research, I stumbled upon this video “ <a href="https://vimeo.com/145916599">A journey to service design</a>” by <a href="http://www.meganerinmiller.com/">Megan Erin Miller</a>. This is what the exciting moment of the discovery looked like:</p><h3>Shira Ben-Cohen on Twitter</h3><p>When you experience an AHAHA moment. #serviceDesign. Yes. @meganerinmiller -I&#39;m so inspired by your talk! https://t.co/LmfhNvSXbA thank you!</p><h3>Megan Erin Miller on Twitter</h3><p>@shirabc awwww I am so happy to hear that!</p><h3><strong>The ringing bells of an “aha moment”</strong></h3><p>That was it — I found what I was looking for, and it was a double strike! Not only had I been inspired by Megan’s personal path, but also I knew that Service Design provides practicality that could help me bring value to my organization in a different approach.</p><p>On a very personal level, while listening to this video and the reading I did right after, I literally got so excited that I had to clear my throat from the threatening tears of joy. Not kidding.</p><p>I particularly thought that the combination of a method that cares not only about the client experience (candidates in my case) but also about the experience of the people involved in <em>delivering</em> the services was an essential component of it.</p><p>Service Design, as a collaborative method, also allows multi-disciplinary teams to work together on a common problem and visualize it “end-to-end” and most importantly at a deeper level, map the problem ‘surface-to-core’ in a way that enables teams to reach to holistic solutions, those kind of solutions that they will be happy to implement for the long term, as <em>they </em>were the one who identified them and now feel very connected to them, as they were born “bottom up” rather other solutions that organizations tend to bring to teams “top down,” which many times gets a lower success rate and engagement.</p><p>I felt that all of those component are exactly what we could use in our Talent Acquisition organization to bring a significant change in the way we do recruitment.</p><blockquote>I felt the wind of change and I was so moved.</blockquote><h3>And thus, my journey began</h3><p>And thus, my journey to bring Service Design to Intel began. In my case, I literally came to my non-local supervisor, a true visionary, on her next visit to Israel and told her about Service Design and how I believe it could bring Intel value.</p><p>Honestly, I did not feel I did a good job advocating and convincing, as I was still on the exploration part of my discovery path myself. I had a long way to go, but, surprisingly enough as she was presenting our new team structure a week later, my name was followed by the title “Service Design”.</p><p>And that’s literally how I started owning the field and felt ready to go to the next level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/465/0*VuSXW92TsbRzL2CN." /></figure><h3><strong>Connecting the dots; following your passion</strong></h3><p>Now that it’s an official part of my job with all the responsibility of representing the new field as it should be and applying it, I have started my path in upscaling my skills and learning everything I could learn about service design. This brought me to buy some books on Amazon, reading and viewing literally (almost) everything the internet could offer me.</p><p>Now that I know how beneficial service design is, I got to the point where I wanted to socialize what it is to my entire group and colleagues and find the right place to start implementing it.</p><p>One of the challenges in socializing a new method without the ability to demonstrate a successful project yet is how to summarize everything you know in a short and easy manner that others could connect with and would like to give up their busy time to go and try it. During my first conversations, I found myself tiring my team with heavy explanations about service design principles, using the language of design.</p><p>I must admit, the level of enthusiasm wasn’t as I was expected. After few iterations and some other videos watched on the net, I shortened my explanation to a story, speaking more about our clients, and showing some past work examples we had that was reminding me of Service Design, such as team workshops, to reflect how service design could be used in our current state within the org.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*W7yJ7IV55XVe9k5uXcS1jQ.png" /><figcaption>Always equip yourself with enough of those</figcaption></figure><p>The next question was, who would want to adopt a new discipline and would be ready to free their team to try something new? At the same time I came to my org with Service Design, my manager and I knew that there was going to be a face-to-face session of recruiters in the USA , and that one of their challenges is in the diversity space and how to increase diversity hires. Diversity is also one of <a href="https://hbr.org/ideacast/2017/03/making-intel-more-diverse">Intel’s high priorities</a>.</p><p>There it was! A real need in the organization for improvement. Bang! This could be our chance! And that’s what we did. Sometimes, opportunities are literally nearby; all you have to do is keep an open radar, observe, spot, be creative and connect the existing dots.</p><blockquote>There it was! A real need in the organization for improvement. Bang!</blockquote><h3>Your soul is perfect, your work isn’t</h3><p>I have started working on building the workshop with the chosen team, we have met with their manager and thought about the problem statement, what is it exactly that we want to tackle using service design. We worked on defining the problem statement, the goals and expected outcomes from the workshop, the right audience, the length of it, the blueprinting session, preparing the process we wanted to map in advance with the help of the team ahead of time, and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*wn-JRnJh1GZLI3qMWu3Ltw.png" /><figcaption>Who said something about digital blueprinting ?</figcaption></figure><p>I remember myself struggling again and again while doing the preparation work, it always felt like it wasn’t good enough! I kept on reading books, blogs etc. and although all of the sources indicated one common way, they were all slightly different, and I wanted to include <strong>everything</strong> I knew so I could come out with the <strong>perfect</strong> solution in hand.</p><p>Searching for the perfect way would never lead you to a perfect place, is the making and trying and re-shaping it again and again that would lead you to better results each time.</p><blockquote><strong>Searching for the perfect way would never lead you to a perfect place</strong></blockquote><h3>The power of the community!</h3><p>Eventually there were questions from the ground that I needed answers for, and sometime the abundance of information you have is the last thing you need… and then I found the<a href="http://www.practicalservicedesign.com/community"> PSD vibrant and kicking community on Slack</a>. I have joined this special community of almost 3,000 service design enthusiasts and professionals from all over the globe (proudly as the first and only Israeli there so far!).</p><p>Aside from keeping up reading whatever I found there, I started posted some questions, and immediately got answers and replies. People actually were willing to assist and conversation were happening in a short while. And you know what? It happen in less than an hour, because when you are part of a global community there is always someone awake, no matter from which timezone you are in.</p><h3>This is what service design is all about, isn’t it?</h3><p>It was time. We had gathered at the blueprinting session, started aligning on the process we chose to tackle end-to-end, and we were ready for the in-depth blueprinting part where we start asking all the relevant question and digging into the current and ideal future state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*Sf889n7jaAkCbOSgA_eMZQ.png" /></figure><p>At the beginning I thought that the blueprinting part would never reveal new insights to us since we were spending a lot of time walking the current end-to-end flow and the team seemed to say many true and smart comments at the first part already.</p><p>Inside myself, I had doubts of the expected outcomes, but as we started working we created an impressive visual board where we were able to see in front of our eyes what is actually underneath that particular use case.</p><p>The ideation session concluded in a long list of new ideas for improvement and major “ah-ha” moments and critical insights that we were able to capture from this successful session.</p><p>Feedback from this day was great (we even conducted a short survey that reflected what we have achieved from the team’s comments) — not only that it enabled us to understand what the client experience is like, it helped us see the business process that occur behind the scene and suggest better service experiences solutions that would improve the experience both for our teams and our candidates at the same time.</p><blockquote>After all, this is what service design is all about, isn’t it?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/454/0*dI4DilK2IzEuR6MZ." /></figure><h3>What I learned from all this</h3><p>After sharing my learnings with you, I feel as if it could applied in so many others areas of life. I am very practical normally, but I can’t escape my inherent spirituality after all, therefore these are my spiritual keys from this wonderful experience:</p><p>1. <strong>Go with your intuition</strong>. Even if you are new to service design, still not sure you know how to advocate for it, but you feel you have found your way — go with your intuition. Pursue it. Speak about it, socialize it again and again. People listen not only to your words, but to your passion that comes out from your eyes and tone of voice.</p><p>2. <strong>Find existing allies, understand their motivation and seek to bring value</strong>. There is always a problem to solve, start with identifying what your peers are working on and suggest to join forces at that point, where you could really help them rather adding additional work that they won’t have bandwidth for.</p><p>3. <strong>Big change starts with small wins</strong>. Accept the fact that it won’t be perfect for the first time. You can continue to read and polish your work endlessly but the point is to get things done. Choose the discipline that fits you best, ignore others, and start doing.</p><p>4. <strong>Use the wisdom of the community and their good will</strong>. Don’t over-judge yourself for asking questions that might “look” unprofessional.” I found that people are eager to help — the goodness of people comes out in those communities — and we are all here to learn and help each other. Today you <em>ask </em>something, tomorrow you will be able to <em>answer </em>someone else’s question and bring value to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*40GM9YURyiNBBI6e." /></figure><h3>What’s next? Dream big</h3><p>If I dare and dream big, I would like to see service design as a discipline being implemented in the entire talent organization and keep spreading it to more recruitment teams around the globe. I truly believe in its high potential as a different way to approach business objectives using a client-centric approach in an holistic,co-creative mindset to improve the business services both externally and internally.</p><p>Dream big and taking it even one step further for me, means also, taking few step backwards into our <em>Business Process Performance</em> teams, that shape the backstage of the recruitment world, and bring service design there. In time, our clients would be our recruiters and hiring managers themselves , and the services we would improve would be the tools, policies and processes we design for them.</p><blockquote>It’s the internal perspective that would drive the external behavioral change and an in-depth cultural change towards a Human-Centered Approach.</blockquote><p>After going through this experience, touching the main “actors” in the process, and gaining true insights, I believe, as mentioning before, that everyone can be an amazing ambassador for better service experiences no matter where they are coming from.</p><p>All you have to have is a belief in it, passion to drive it, persistence to try it, and the courage to dream big. What are you waiting for!?</p><h3>But before you go…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*ZPU5Ubt5Xhg6vH0Oc6BEag.png" /></figure><p>You should give this article a 💚, follow me <a href="https://medium.com/u/d6ffb7b15d2a">Shira Ben-Cohen</a> on Medium <em>(and on Twitter — </em><a href="https://twitter.com/shirabc"><em>@shirabc</em></a><em>) and even tweet this article!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*QSw-aVqQOe9509fAne2b6A.png" /><figcaption>Continue the conversation, and join the global Service Design Community of Practice in Slack at <a href="http://www.practicalservicedesign.com/community">www.practicalservicedesign.com/community</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37b665cc6556" width="1" height="1" alt=""><hr><p><a href="https://medium.com/practical-service-design/my-quest-to-bring-service-design-to-my-workplace-37b665cc6556">My quest. My inspiration. My story of introducing service design</a> was originally published in <a href="https://medium.com/practical-service-design">Practical by Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>