<?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 Mathew Kelcher on Medium]]></title>
        <description><![CDATA[Stories by Mathew Kelcher on Medium]]></description>
        <link>https://medium.com/@BreakingFrames?source=rss-17991a447f7e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7SIsV0kMslzf3PnQo137tg.jpeg</url>
            <title>Stories by Mathew Kelcher on Medium</title>
            <link>https://medium.com/@BreakingFrames?source=rss-17991a447f7e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:48:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@BreakingFrames/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[Adding a Dimension to Design: learning to design in AR]]></title>
            <link>https://medium.com/design-bootcamp/adding-a-dimension-to-design-the-transition-from-2d-to-3d-c056cd7250a3?source=rss-17991a447f7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c056cd7250a3</guid>
            <category><![CDATA[augmented-reality]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[mixed-reality]]></category>
            <category><![CDATA[extended-reality]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mathew Kelcher]]></dc:creator>
            <pubDate>Tue, 18 Oct 2022 17:07:45 GMT</pubDate>
            <atom:updated>2022-12-06T07:16:53.317Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>My journey as a 2D experience designer transitioning into the 3D world of mixed reality</em></h4><p><em>This article is an expanded version of my interview with </em><a href="https://medium.com/@michael1991"><em>Michael Lever</em></a><em> at </em><a href="https://matchboxxr.com/"><em>Matchboxxr</em></a></p><p><strong>What was your journey into Mixed Reality?</strong></p><p><strong>Fun fact</strong>: not so long ago, I was hardly interested in Mixed Reality, because I associated it entirely with Virtual Reality. I had a <strong>mental block around VR and usability</strong>. The idea of wearing a mask for prolonged periods of time and replacing your actual surroundings didn’t appeal to me in terms of experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*5exyB7KbzjvzoxdKx0Keow.png" /><figcaption>AI generated image of a 2d pony learning to design for a 3d world</figcaption></figure><p>Apple’s decision to include back facing Lidar sensors on the iPhone 12’s was a shifting point. I was really intrigued. Why would Apple decide to add this rather unknown technology to a mass-market product ?</p><p>That got me thinking about the <strong>potential for Augmented Reality</strong>.</p><p>Of course I was already familiar with AR, but mostly for what I call <strong>i<em>nwards facing </em>experiences like the AR face filter effects</strong> that we see on social media platforms.</p><p>But what we witnessed with Apple’s release meant more to me. I took it as a sign that we were moving towards mass adoption of what I call <strong><em>outwards facing AR:</em> overlaying digital objects on our physical environment and being able to interact with them</strong>. Suddenly, the possibilities seemed huge.</p><p><strong>Do you work with a particular app or device? If so, why?</strong></p><p>I am working mostly with Unity and Vuforia. There are so many platforms available depending on what you want to do, and it took me a fair amount of searching and experimenting before focusing on Unity. I use <strong>Unity because it has the most flexibility</strong>, and it was the best choice for experimenting with projecting digital overlays onto our physical environment.</p><p>As for a headset, I don’t own one; but that will probably change when Apple announces theirs 2023. So for the time being, I experience AR like most of the world does, through my phone :)</p><p><strong>How do you begin of a piece of work?</strong></p><p>Right now I am in a phase of exploration and discovery. That means I spend my time building AR experiences entirely for myself. There is no limit to my creative process: <strong>I launch experiments based on what interests me</strong>. Most of it comes from my imagination and the subjects that I am passionate about. I find myself constantly imaging “<strong><em>what if I could do this</em></strong>” or “<strong><em>what if I could do that</em></strong>” ?</p><p>Because I am making things for myself — <strong>I have the luxury of being my own client </strong>— I don’t work the same way as I do when I’m designing in 2D (at least not for now). So it is like I have a life in 2D and another in 3D.</p><p>In my 2D work life, I am a strategic designer, I use user research and workshops to align stakeholders on what to build before it is built.</p><blockquote>My current approach in 3D design much simpler, because it is just for me. I’m sure that <strong>in the end my 2D and my 3D lives will all merge in a very coherent approach</strong>, but I’m not there just yet.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*sJzTp3NI-7iwzA0iKEUrmA.gif" /><figcaption>YSL Rouge Sur Mesure Lipstick Printer &amp; Application</figcaption></figure><p>I suppose that the rouge sur mesure application that we designed for YSL Beauty is an <strong>example of where my 2D and 3D design lives came together.</strong></p><p>The app connects to a <strong>personal lipstick printer</strong>, that lets users print custom lipstick shades from their phone. Here, <strong>AR is used for the virtual try-on </strong>part of the experience: you can see the lipstick shade on your lips before you print it.</p><p>It was a no-brainer to use AR for this part of the experience, but the <strong>AR try-on is one part of an overall experience</strong>.</p><p>I think we could have blinded ourselves with the novelty of the AR powered try-on, but instead we focused on the overall experience.</p><p>At the outset, we <strong>researched</strong> how people actually go about trying lipstick. We needed to understand the parts of that experience to conserve and also where there were hidden opportunities that would let us go beyond.</p><p>We learned a lot. Replicating a try-on with AR is one thing, but how do you replicate the part when people put lipstick swatches on their arm so they can analyse the colours and textures?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*a9ZWYopVd5GhnyMc_6nYxQ.png" /><figcaption>AR lipstick try-on in the YSL Rouge Sur Mesure app</figcaption></figure><p>We didn’t want to lose sight ofthese opportunities, so when planning the functionality of the app everything was mapped to a journey map. That way we could track the experience we wanted and how it related to real customer opportunities and emotions at each moment of the experience.</p><p>The decisions we made were based on human, business and technological factors. But In the end, it was about making a seamless experience that transitions between physical and digital reality.</p><p><strong>And what approach do you follow for the rest of your project?</strong></p><p>When I’m desiging for myself, once I have an idea, or concept, I usually write it out or <strong>draw a storyboard</strong> to describe how I imagine the experience, to bring it to life.</p><p>Then I’ll <strong>take an inventory of what I know and what I would need to learn</strong> in order to build that experience. Because before staring to make anything, I determine where I have the least knowledge and, as counter-intuitive it may seem, I start with the hardest part.</p><p>I often <strong>consult expert resources</strong> to get better at building what I want to build and it is part of this amazing process. We are lucky to have access to tons of tutorials and resources to answer our questions as we go.</p><p>The <strong>craft side of the project is important</strong>, because as in 2D, understanding how things work behind the scenes is part of what let us design better products.<strong> I do not think you have to master coding</strong>, but it is a great way of learning how to think in Augmented Reality.</p><p><strong>What are the pain points for designing for Mixed Reality?</strong></p><p>This is more a question of shifts you have to go through.</p><p>The first is a <strong>mindset shift.</strong></p><blockquote>Coming from 2D design, I describe moving into AR as “<strong><em>adding a dimension to my work</em></strong>”. That should give some idea of the degree to which working in AR impacts how I think about design. It totally reinvented this concept in my mind.</blockquote><p>As a 2D designer I create experiences within a frame (any four sided format, most often a screen), <strong>with AR the frame is gone</strong>.</p><p>That demands a totally different mindset, one that knows how to <strong>design</strong> <strong>outside</strong> <strong>of that frame</strong>.</p><p>The second shift is about <strong>finding <em>your</em> way</strong> in this huge unknown MR universe. There is so much information available, there are so many platforms, new things are happening every single day. We are opening the doors to <strong>a world of endless possibilities in Mixed Reality</strong>, it is very exciting. Yet at the same time, it is painful to feel so slow when everything is going so fast, right ?</p><p><strong>Do you have any thoughts for improvement in this space?</strong></p><p>Today, I see two spheres in AR.</p><p><strong>The super cool</strong> (and kind of gimmicky one): filter effects on social media, the great success of Pokemon Go, that makes AR mainstream and visible (which is great). And the <strong>very high-end one</strong>, in fields such as medicine and heavy industry, that the masses do not come across and do not need to understand. Super useful but far from the mainstream.</p><p><strong>There is inevitably going to be a third sphere that evolves between these two</strong>. I think designers will play a critical roll in defining the form that it takes. Being conscious of this as designers will let us start imagining it, and maybe leave less room for big players to impose their views on the topic (hello Metaverse).</p><p>The second improvement is directly related to that awareness : <strong>we need to gather.</strong></p><p>As this MR universe expands quickly, our knowledge may be condemned to stay segmented (<em>we are not AIs or super-humans)</em>, so I believe the only way we can own it is to <strong>surround ourselves with other designers and experts </strong>to share, learn faster, and understand how to increase the impact of our work as designers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c056cd7250a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/adding-a-dimension-to-design-the-transition-from-2d-to-3d-c056cd7250a3">Adding a Dimension to Design: learning to design in AR</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Discovery ≠ Ideation]]></title>
            <link>https://medium.com/@BreakingFrames/product-discovery-ideation-70f230341472?source=rss-17991a447f7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/70f230341472</guid>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-tips]]></category>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Mathew Kelcher]]></dc:creator>
            <pubDate>Mon, 05 Sep 2022 08:47:51 GMT</pubDate>
            <atom:updated>2022-09-05T08:47:51.787Z</atom:updated>
            <content:encoded><![CDATA[<p><em>It might sound less fun, but Ideation is not the same as Discovery</em></p><p>I’ve been asking friends and colleagues in the product and design field how they approach Product Discovery. After asking a few times, I realised that for many, <strong>discovery</strong> evokes creative, coffee infused sessions with post-it lined walls and whiteboard drawings, totally incomprehensible to the next group of people that pass through your meeting room. <br>It was clear : <strong>product discovery was synonymous with ideation</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8uDIeEdMEAgqGf84OmOLRw.png" /><figcaption>AI generated image of an ideation session..coffee cups and post-its included</figcaption></figure><p>Of course ideation<em> is a part of </em>discovery, but I would not even consider it to be the primary activity during discovery.</p><p>So then, if ideation is not discovery — and I’m taking away your post-its and markers (for now), we can ask the question “<strong>what is product discovery”?</strong></p><p>I see it as an approach to risk mitigation in 4 interrelated parts, each part having relationships and potential impacts on the other parts. This explains why product discovery is a non-linear process: what you learn in one part of discovery can make you return to another part to re-think it. That is part of an ongoing <strong>discovery dialogue</strong> that makes for good discovery, good products, and good business.</p><p><strong>Part one is Business strategy</strong></p><p>Stakeholder alignment on a business strategy and desired product outcomes is the fundamental starting point for discovery. This usually means having an alignment workshop with product stakeholders before engaging the rest of the product teams. It is surprisingly rare to find stakeholders that are aligned at a strategic level.</p><p>The time invested in <strong>aligning and communicating your business strategy </strong>pays for itself many times over, because equipping your product teams with a clear vision and target outcomes is what empowers them to make the decisions that deliver results for your business (article about that coming soon).</p><p><strong>Part two is Customer Understanding</strong></p><p>Product discovery requires an in-depth understanding of your customers. That understanding comes from frequent, <em>in-depth</em> user research (qualitative research). I refer to <em>“in-depth”</em> research because building a great product, requires that you go beyond understanding your customers’ problems. You need to have a deep understanding of their motivations, behaviours, and how your product fits into their lives.</p><p>Luckily, there are many resources available to help you learn how to move beyond surface research and gain deep insights into your customers’ perspective. <strong>Armed with customer insights</strong>, your product team can start to choose which ones to address in your product. Keep in mind that the ones you choose should be those that align with your product and business objectives defined at the beginning (article about that coming soon).</p><p><strong>Part three is Solutions</strong></p><p>Here is your favourite part. Product discovery requires solutions and ideation is a powerful approach to generating potential solutions (yes, you can have your markers and post-its back).</p><p>This is the moment where having product team members (with varied backgrounds and perspectives) participating in ideation sessions can generate multiple solutions <strong>capable of achieving business and customer goals</strong>. As you generate solutions, you’ll see the value of using a visual mapping tool to align your solutions with the work you’ve done in the previous parts.</p><p>At this point, you’ll want to stay open to multiple solutions. Narrowing your focus to a single solution would bias testing and counter the risk mitigation effect of product discovery (article about that coming soon).</p><p><strong>Part four is Testing</strong></p><p>With multiple potential solutions, we need to prove which ones will actually deliver value to our customers and our business. The goal during testing is to test your high potential solutions with the smallest possible investment.</p><p>I have good news, you don’t need an MVP to test a solution. There are many tools and strategies available to test without having to code or invest extensively in a potential solution.</p><p>One of my favourite testing approaches is assumption testing, as detailed by Teressa Torres in her book “<a href="https://www.goodreads.com/en/book/show/58046715-continuous-discovery-habits">Continuous Discovery Habits</a>”. This approach lets you test multiple solutions in parallel by testing their shared assumptions.</p><p>Another favourite testing resource is David Bland and Alex Osterwalder book “<a href="https://www.strategyzer.com/books/testing-business-ideas-david-j-bland">Testing Business Ideas</a>” that provides a detailed inventory of testing tools and information to help you understand when and how to use them.</p><p>Testing, like user research, brings more answers and insights that will ultimately help determine into which solutions your “delivery” efforts and investments should be concentrated.</p><p><strong>The missing part</strong></p><p>While writing in an effort to counter the idea that Product Discovery is akin to ideation, I have shared a simplified overview of the 4 parts I consider to be key to Product Discovery.</p><p>But in no way is Product Discovery a one-size fits all, mechanical 1–2–3–4 approach. It is much more than a static series of parts: it is non-linear, it moves, it evolves, and it needs to be revised regularly. <strong>Discovery needs to be tailored to the organisation that relies on it.</strong></p><p>Product Discovery is <strong>first and foremost</strong> a human activity. It makes product teams learn about the people they are building for. In return, Discovery aligns and empowers your product teams (and that is fundamentally a human endeavour).</p><p>For the sake of this article, I put forward the primary output of Product Discovery as being risk mitigation. But my deep conviction is that the core outputs of good Product Discovery are<strong> confidence and alignment.</strong></p><p><strong>Confidence</strong> in knowing that what you have decided to build has a high probability of generating the results your business and customers <em>need</em>; <strong>alignment</strong> between the teams who have contributed to the Discovery process and own the results they are trying to generate.</p><p><strong>That’s much more than an ideation workshop will ever bring.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70f230341472" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>