<?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 Martin Kuplens-Ewart on Medium]]></title>
        <description><![CDATA[Stories by Martin Kuplens-Ewart on Medium]]></description>
        <link>https://medium.com/@mkuplens?source=rss-7dd497afd8b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*ufsgqC0dsQnHkoVzy4UmPg.jpeg</url>
            <title>Stories by Martin Kuplens-Ewart on Medium</title>
            <link>https://medium.com/@mkuplens?source=rss-7dd497afd8b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:48:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mkuplens/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[Interviews That Don’t Suck: The Product Scenario]]></title>
            <link>https://medium.com/swlh/interviews-that-dont-suck-the-product-scenario-4bc3f54986f7?source=rss-7dd497afd8b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bc3f54986f7</guid>
            <category><![CDATA[interviews-and-insights]]></category>
            <category><![CDATA[scenario]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Martin Kuplens-Ewart]]></dc:creator>
            <pubDate>Wed, 19 Aug 2020 15:59:51 GMT</pubDate>
            <atom:updated>2020-08-23T18:52:49.559Z</atom:updated>
            <content:encoded><![CDATA[<h4>Scenario interviews can be invaluable tools for hiring — or an awful experience for candidates and a waste of time for your team. Here’s a framework for making them effective for everyone involved.</h4><figure><img alt="A man and a woman working together at a whiteboard. The woman is sketching." src="https://cdn-images-1.medium.com/max/1024/1*gdNGZU_qK3ZTz0OlRnodyw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@timmossholder?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Tim Mossholder</a> on <a href="https://unsplash.com/s/photos/whiteboard?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>I am a strong believer in hiring product people through an evidence-based, performance-orientated process. Starting with the achievements you expect of the candidate in their first year, shape a rubric for the attributes they need to demonstrate, then use interviews to collect evidence that demonstrates the score to award for each one.</h4><p>Scenario interviews are one of my favourite tools for collecting this evidence for product roles, because behavioural characteristics are so much of what makes a strong candidate a terrific asset to the team.</p><p>Thoughtfully constructed and facilitated, a scenario can give terrific insight into the candidate’s thought process, communication preferences, and professional behaviours.</p><p>But poorly structured and haphazardly run scenarios lead to confusion, poor performance on the day, weak decisions by the hiring team, and leave the candidate with a poor perception of your company.</p><p>In my experience, most organizations run bad scenario interviews.</p><p>In this article I will try to help — by outlining two models that most scenario interviews fall into, explaining why the collaborative model is my preferred approach, and offering five concrete things you can be doing to make your scenario interviews a valuable experience for everyone involved.</p><h3>Two models</h3><p>I’ve been through numerous scenario interviews in my career. Some great, others have been awful. All have fallen more or less into one of two models. I call them ‘figure it out’ and ‘discover, together’.</p><h3>‘Figure it out’</h3><figure><img alt="Photograph of the ocean. A person is sitting on a paddle board, waiting for a wave." src="https://cdn-images-1.medium.com/max/1024/1*BHM5PT-Ox-JLaLrWo0rQlg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@timmossholder?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Tim Mossholder</a> on <a href="https://unsplash.com/s/photos/adrift?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In this model, the candidate is given an outline of a problem or opportunity by the interviewers–usually in writing, sometimes verbally–and is told to work through the problem.</p><p>The interviewers take a largely passive observer role by default, though they may provide prompts if the candidate appears to get stuck. If the candidate wants the interviewers to engage in the process, they must actively invite them to do so.</p><blockquote><em>My worst experience with a scenario interview followed the ‘figure it out’ model.</em></blockquote><p>I arrived at the office, was eventually greeted at the door, and led to a narrow room that barely fit a long table and the dozen chairs set around it. The table held a few scrap post-its and a couple of unpromising whiteboard markers. The wall was filled with old scrawls.</p><p>The two interviewers sat on one side of the table; I squeezed in between the whiteboard wall and the table on the other side.</p><p>After an hour or so of questions back and forth, the interviewers announced it was time for the scenario/whiteboarding exercise.</p><p>“Read the scenario, then work through it. We don’t expect you to reach a solution. We just want to see how you think.”</p><p>The interviewers crossed their arms, and leaned back in their chairs.</p><p>“Show us your stuff,” their posture said.</p><p>The scenario was for a made-up company in an industry completely unrelated to the one I was interviewing for. Neither interviewer gave an indication they had experience or expertise in that field.</p><p>I launched into the usual routine: ask clarifying questions about the brief, state the process I’d follow, share and try to tease out relevant experiences from the interviewers to try and spark ideas and interaction, frame a proposition, and sketch some hypothetical flows.</p><p>The interviewers stayed in their seats, looking on with modest interest, and confused responses when asked to dig into their own experiences to contribute to ideation.</p><p>I didn’t make it past this interview.</p><p>The room was ill-suited for the planned activity, the participants were disinterested in the exercise, and I wasn’t in the top form needed to overcome the situation.</p><p>I left disappointed – both in my performance and in the company for executing on hiring so poorly.</p><h3>‘Discover, together’</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jIvJUz9yl2hze3DRaniXsw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@thisisengineering?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">ThisisEngineering RAEng</a> on <a href="https://unsplash.com/s/photos/whiteboard?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Product work isn’t a solo effort; it’s a team sport. That’s where the ‘discover, together’ model really shines.</p><p>In this model, the candidate begins with a period of discovery – interviewing someone playing the part of a customer. They then brief and collaborate with a future colleague to solve the needs they unearthed.</p><blockquote>Though the interviewers can play the role of customer and ‘team’, the best execution of this model that I have ever experienced used fresh team members to do those jobs.</blockquote><p>Here’s how it went:</p><p>I arrived at the office, was eventually greeted at the door, and led to a room with a long table and about a dozen chairs set around it. The dozen or so interviewers sat around the table along with me.</p><p>There were a handful of whiteboard markers, a stack of post-its, and some notepads and pens on the table.</p><p>After an hour or so of questions back and forth, the interviewers announced it was time for the scenario/whiteboarding exercise.</p><p>“We’re going to bring in a colleague who will play the part of one of our customers. After you have interviewed them, we’ll take a break to let you gather your thoughts, then your ‘team’ will come in to be briefed on what you’ve discovered and what solutions we might offer to customer’s needs.”</p><p>Half of the interviewers left, the rest got comfortable and ready to listen closely.</p><p>I had a lively and engaging conversation with the ‘customer’. We dug deep into the setup of their business, how they were growing with the help of the product, and explored some tricky issues they were running into that ‘we’ hadn’t been solving for yet.</p><p>We took our five minute break, then the ‘team’ came in: a member of the engineering leadership team (no pressure, right?) – it seems product design was swamped that day.</p><p>I shared the conversation I had had with the ‘customer’ — described the context I had learned, some of the pains and problems I had uncovered; they gave me feedback about how those might map to the existing product range.</p><p>We then whiteboarded together, found some areas that might warrant ‘future follow-up’, made some assumptions, and shaped a potential solution that was aligned with the company’s mandate and the customer’s needs.</p><p><em>I got an offer.</em></p><h3>A framework for success: together <em>is </em>better.</h3><p>There were five key ways the ‘discover, together’ experience was the better one for me as a candidate. Put together, they are a framework for effective scenario interviewing:</p><ol><li>The interviewers set the space up for success: the materials and room were right for the task at hand.</li><li>They created psychological safety for exploration and play, drawing a clear distinction between assessors and participants by using new people for role play.</li><li>The scenario was real for the interview team. They empathized with the problems being ‘discovered’ and cared about solving them.</li><li>The ‘team’ engaged actively in collaboration, trading off the lead at the whiteboard as the work demanded it.</li><li>The exercise showcased good practices for product people: learning from customers and collaborating on solutions with their teams.</li></ol><h3>Over to you</h3><p>In analyzing the experiences I shared, it’s clear that the interview team using the ‘discover, together’ model gathered richer, more complete, and — critically — real evidence of the performance I could deliver if I joined their team.</p><p>Though the format took more effort, more time, and more people, <strong>as a hirer</strong> the model enables higher-quality decisions about candidates.</p><p><strong>As a candidate</strong>, the emphasis on discovery proves the company’s customer orientation and support for quality product work; and the respect showed to the candidate demonstrates a healthy, people-orientated culture.</p><p>If making high-quality performance-based hiring decisions is important to you, I hope you consider including a scenario interview that follows the ‘discover, together’ model in your process–and that you find my framework for success a helpful stepping stone to your team’s growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bc3f54986f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/interviews-that-dont-suck-the-product-scenario-4bc3f54986f7">Interviews That Don’t Suck: The Product Scenario</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>