<?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 Jason Kogan on Medium]]></title>
        <description><![CDATA[Stories by Jason Kogan on Medium]]></description>
        <link>https://medium.com/@jasonkogan?source=rss-dc84d51b8c56------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QGYwbREaLwf422YYGKC1RQ.png</url>
            <title>Stories by Jason Kogan on Medium</title>
            <link>https://medium.com/@jasonkogan?source=rss-dc84d51b8c56------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:52:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jasonkogan/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 in board game design]]></title>
            <link>https://uxdesign.cc/ux-in-board-game-design-97bfcdb1d581?source=rss-dc84d51b8c56------2</link>
            <guid isPermaLink="false">https://medium.com/p/97bfcdb1d581</guid>
            <category><![CDATA[board-games]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jason Kogan]]></dc:creator>
            <pubDate>Wed, 07 Jan 2026 15:06:01 GMT</pubDate>
            <atom:updated>2026-01-08T23:03:05.617Z</atom:updated>
            <content:encoded><![CDATA[<h4>I treated my board game like a product and used UX practices to improve its UI—simplifying the game and maxing the fun.</h4><p>As a User Experience (UX) professional, it’s hard to ignore the correlation between UX and board game design. From defining personas, to prototyping and usability testing, to content hierarchy… The parallels are incredible and if you’re a board game designer, you’re likely already doing them, perhaps without knowing it.</p><p>The benefits of applying UX design to board game design only starts here (during the initial design phase). But UX principles are beneficial from start to finish. For example, heuristics can be used to <a href="https://www.nngroup.com/articles/usability-heuristics-board-games/">audit and improve</a> final UI elements. <a href="https://uxdesign.cc/board-game-ux-help-and-documentation-74335da5ce20">Information Architecture principles</a> can be used in component design and rulebook creation. And <a href="https://mindclashgames.com/board-game-iconography-how-smart-symbols-enhance-ux-and-playability/">leveraging common iconography</a> will ensure players can easily understand intent.</p><p>Here are the key takeaways that you should consider when designing your board game (and will be explored below):</p><ul><li>UX practices will improve your board game.</li><li>You must clearly identify who your game is for, connect with them, and listen to them, in order to improve.</li><li>Having an open mind is critical to the design process.</li><li>Your main job is to steer the ship and bring your vision to life. You need to decide what’s best for your game.</li></ul><p>Before we go any further, let’s all speak the same language. Each time you play a game-in-progress, it’s called a playtest. I have now had many playtests, gotten so much invaluable feedback, and played my game with dozens of people. I sincerely want to thank everyone who have participated in the process for their time and opinion. I would not be where I am today without them.</p><p>WARNING: This is a <strong>deep dive</strong> into the evolution of a single component of a larger board game. A card. This card has gone through roughly 10 iterations, but I’ll focus on 3 critical checkpoints, outlining the changes, what drove those changes, and the learnings along the way. There is <a href="https://uxdesign.cc/board-game-ux-help-and-documentation-74335da5ce20">definitely a bit of an art</a> to designing the best card design.</p><p>At this point I’ve lost count of how many times I have created what I thought was the “final design” (ok not really, but you get the point). Just like a digital product, a board game is never truly done, until it’s published, but revisions can always come later..</p><p>For now, let’s dive in. Meet Mort.</p><figure><img alt="An illustration of a character named Mort." src="https://cdn-images-1.medium.com/max/800/1*d5fl77SOt8bg5L_sb-5YUQ.png" /><figcaption>This was Mort. He’s now dead.</figcaption></figure><p>Now say goodbye. Great Uncle Mort is dead. This should be a solemn occasion, but it’s not.<br>Mort’s house is full of priceless artifacts, questionable heirlooms, and deeply personal stuff that no one will admit to wanting. As his “closest” relatives, you have gathered for the reading of the Will, each of you hoping to walk away with more than your fair share.</p><p>And here’s one of the “questionable heirlooms”, v1 of the item.</p><figure><img alt="Illustration of a board game card. It has a Taxidermy Ferret. The card also features a suit and value (4 egg), a power (Discard 1 card) and two win condition." src="https://cdn-images-1.medium.com/max/610/1*STaUU3z1JyiVKkeJcncl2g.png" /><figcaption>v1 Taxidermy Ferret</figcaption></figure><p>The card has 4 main areas, each trying to communicate something different:</p><figure><img alt="This shows a breakdown of the 3 card components (suit and value, the flavour text and photo, and the power)" src="https://cdn-images-1.medium.com/max/1024/1*EV02h1V7EreSixdI77JJpA.png" /><figcaption>Left: Value and Suit. Middle: Fun. Right: Power.</figcaption></figure><ol><li>Left: This is the value and suit of the card (think 6 of Diamonds).</li><li>Middle: This is the “fun” part of the card. Each card has a unique and quirky item name and picture.</li><li>Right: When a player wins this card, the winner gets a power (good or bad).</li></ol><p>And the 4th card feature:</p><figure><img alt="The back of the card is black, indicating that the win condition at the top (with a black arrow) is in play. Players must play the highest value Painting to win the Taxidermy Ferret." src="https://cdn-images-1.medium.com/max/1024/1*sY3T0QJ2sh-WyOQf1AhaDA.png" /><figcaption>Left: Back of the draw deck of item cards, indicates Black or White. Right: Top box (black arrow) and bottom box (white arrow)</figcaption></figure><p>That last features requires a little explanation. I love interesting mechanics. I came across this game where the back of the draw deck influenced the flipped card’s impact, so I built this into my game. It was meant to work that when the Taxidermy Ferret is drawn and placed next to the draw deck, it may be won in one of 2 possible ways:</p><ol><li>If the card back of the draw deck has a <strong>black</strong> spade: The Taxidermy Ferret may be won with the highest Painting item (the picture icon).</li><li>If the card back of the draw deck has a <strong>white</strong> spade: The Taxidermy Ferret may be won with the highest Sculpture item (the face icon).</li></ol><p>That’s a lot of heavy lifting for one card. And a lot of things that are relevant based on where the card lives (in your hand vs on the table).</p><p>I had many playtests, spoke to many people. Here’s a snippet of feedback that I heard:</p><ul><li>“My favourite part of the game is the story and all the quirky items!“</li><li>“I want more control over how a card on the table is won”</li><li>“The cards are very ‘busy’”</li><li>“I don’t love the ‘black vs white’ language”</li><li>“The cards are too confusing, and the game is not complex enough for me”</li></ul><p>UX Translation:</p><ul><li>I needed to reduce the cognitive load of the cards.</li><li>I should consider designing separate UIs for some of these features.</li><li>I needed to leverage the Design Process Model to understand, iterate and address the feedback.</li></ul><p>One painful adjustment is that I needed to “kill my first darling”: The back of the deck influences the flipped card. It wasn’t working. I decided to introduce a mechanism where players would vote using their cards instead of relying on the back of the deck.</p><p>Let’s look at v2, the next major iteration:</p><figure><img alt="v2 of the same Ferret card with visual improvements, and also additional complications shown in the next series of photos." src="https://cdn-images-1.medium.com/max/610/1*5RLyBXpLHJ5WQuGgr1YQGA.png" /><figcaption>v2 Taxidermy Ferret</figcaption></figure><p>I made a mistake. I tried to make one card do the work of four, or more. It had a suit and value, a power, two win conditions, and now even more… I had failed to prioritize the user’s primary goal. Just because I could do more in the card, doesn’t mean I should!</p><p>This version of the card has 5 main areas, each trying to communicate something different:</p><figure><img alt="Shows 3 cleaned up areas on the Ferret card. Now the value and suit are together, and the win conditions have been moved to the bottom and are together for easier digestion." src="https://cdn-images-1.medium.com/max/1024/1*XAGWl4k3zyt2TESbzjU4ug.png" /><figcaption>Left: Value and Suit. Middle: Fun. Right: Win Condition.</figcaption></figure><ol><li>Left: Same as v1. This is the value and suit of the card.</li><li>Middle: Same as v1. This is the “fun” part of the card.</li><li>Right: Same as v1 (Feature #4), but now combined at the bottom of the card, and changed to Gold vs Red.</li></ol><p>Note: The “power” (Feature #3 from v1) was moved to separate tokens, simplifying the card design. But I also took the opportunity to add more of what players were asking for, story…</p><figure><img alt="Some added complexities were added to the card based on feedback. A murder mystery escape meta game was added, visualized here. The ability to vote with a card (red or gold) was added, visualized here." src="https://cdn-images-1.medium.com/max/1024/1*MdNY2Ue93BtS56j7HzxvhQ.png" /><figcaption>Left: Puzzle components. Right: Red (or Gold) border colour.</figcaption></figure><p>4. Puzzle: I turned every card into a piece of a meta game. It was now part murder mystery, part escape game, and I loved the “progress”.</p><p>5. Voting: Players could now vote Red or Gold to decide the win condition of a card on the table.</p><p>I thought the cards were now amazing. They gave players the ability to vote on win condition. The value and suit were together and easier to see. The win conditions were together at the bottom and colour-matched the voting. AND there was a super cool escape room murder mystery.</p><p>I thought I had addressed all of the feedback and focused on more of what people wanted, more story, less card confusion, more game complexity, no “black/white” battle… but I ignored the most critical feedback, the cards are too busy.</p><p>Now I was hearing feedback like:</p><ul><li>“I find the cards confusing.”</li><li>“There’s a lot on the cards that doesn’t matter right now.”</li><li>“So you can only solve the mystery once?” (Uhhh yes, it’s an escape room!)</li><li>“The tokens (formerly ‘powers’) are so much fun!”</li></ul><p>I took a step back to think about what the game was trying to be. Was the game a way for me to make people think I was smart, or was it trying to make players “feel” like they were bickering greedy relatives at a Will reading (and having fun doing so). Obviously I was aiming for the latter.</p><p>I also decided to take a moment and consider who this game was for: Casual and hobby gamers looking for a palate cleanser between rounds of Wingspan, or Ark Nova. As such, it needed to be less complex, and more focused on the “fun” part. I needed to take another look at the cards, trying to focus more on what the players I was targetting wanted, and MUCH less of what they didn’t want.</p><p>UX Translation:</p><ul><li>I needed to define my Personas and get into their mindset, and only build for them.</li><li>I needed more usability testing.</li><li>I needed to ensure my content hierarchy matched my user’s goals and the context in which they were using my cards.</li><li>My SMEs had influenced too much feature creep.</li><li>I needed to reduce cognitive load of the cards. For real this time.</li><li>I needed to consider designing <em>even more</em> separate UIs for some of these features.</li></ul><p>Also worth noting, I decided that I needed to “kill my second darling”. The murder mystery escape game. I loved it. But it was too much, and more importantly, it was not for my target audience. Maybe I’ll use it in a future game.</p><p>Here’s v3.</p><figure><img alt="v3 of the Ferret card has been largely simplified. It only has a suit and value, and fun flavour text now." src="https://cdn-images-1.medium.com/max/610/1*KXe9U0JLKs79W-A4FxICZA.png" /><figcaption>v3 Taxidermy Ferret</figcaption></figure><p>This version of the card has 2 main areas:</p><ol><li>Name and value: Same as v1&amp;2. This is the value and suit of the card.</li><li>Story: Same as v1&amp;2. This is the “fun” part of the card. Now with even more ‘fun’ jokes.</li></ol><p>I bet you’re wondering… where did everything else go?</p><ul><li>Powers: These were moved to tokens in v2.</li><li>Escape game/Murder mystery: This was removed entirely.</li><li>Voting: This was removed entirely, similar to v1.</li><li>Win condition: This was moved to a new card type, introducing the Treasure card:</li></ul><figure><img alt="This shows the win condition of the card (highest or lowest) of a particular suit is determined by the back of the draw deck now. These cards have been separated from the previously reviewed Ferret cards." src="https://cdn-images-1.medium.com/max/1024/1*gYBlP9KJQS9qpahMF7XHDQ.png" /><figcaption>Left: Back of the draw deck of Treasure cards, indicates Gold (up) or Red (down). Right: Gold box (always indicates “Highest”) and Red box (always indicates “Lowest”)</figcaption></figure><p>Each round a (newly designed) Treasure card is flipped, and the top of the draw deck indicates if the highest or lowest card played will win the Treasure.</p><p>When I finally simplified the cards I was able to find space for my first darling (hello old friend). And even better, it totally “fit” into the game and worked as I had originally envisioned. I was very happy.</p><p>This also gave me the ability to add more story into the game (what people wanted), introduced Treasures that the players could chase, and allowed me to overhaul the rules of the game to make it feel more like a greedy Will reading, complete with an embezzling Executor! Everything just clicked and the game felt much more fun &amp; engaging, felt like a bunch of greedy relatives bickering, and most importantly, was far less confusing.</p><p>Overall, taking a <a href="https://uxdesign.cc/board-game-ux-minimalist-design-ab812ee5412d">minimalist design approach to the card</a> (instead of trying to have one card to more work than it should) made the card easier to understand, added more space for thematic fun, and improved the game overall.</p><p>I need to do even more playtesting, but based on the feedback I’ve already heard from this newest version, I believe the cards (at least) are “ready”. Over this journey the most critical takeaways were:</p><ul><li>You must clearly identify who your game is for and build for them.</li><li>Your game will only improve if you remain open to feedback (even if it means shelving something you really like – it can always come back, in this game or the next one)</li><li>Stay focused on your vision – just because ideas are shared, doesn’t mean implementing them will make your game better. It’s your game, you decide.</li></ul><p>If you are curious to what attending the Will reading and is like, the game draws inspirations from <a href="https://boardgamegeek.com/boardgame/115/im-the-boss">I’m the boss</a>, <a href="https://boardgamegeek.com/boardgame/172/for-sale">For Sale</a>, and <a href="https://boardgamegeek.com/boardgame/220/high-society">High Society</a>.</p><p>As you can see, board game design and UX go hand in hand. Designing for your audience is like Persona creation. Playtesting is like usability testing. The playtesting mindset is the Design Process Model, expanding and contracting as you identify and work to resolve negative feedback. Having a deep background in User Experience has helped greatly, and sped up my game design process. It’s been 2 months since Great Uncle Mort is Dead was born, and I think I’m ready to start pitching it to publishers. I would not be here today without both my obsession with board games, and my passion for User Experience.</p><p>If you’ve made it this far and would like to talk about board game design, or user experience, let’s connect.</p><p>All cards were designed by me and include iconography from NounProject, whereas the illustrations of the Taxidermy Ferret, Mort, the scrolls, and “Mona Lisa” were AI generated as placeholders. If and when this game is published they will likely be replaced, by the publisher.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97bfcdb1d581" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/ux-in-board-game-design-97bfcdb1d581">UX in board game design</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The springboard mindset: rethinking website templates with AI + IA]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jasonkogan/the-springboard-mindset-rethinking-website-wemplates-with-ai-ia-4279e47c9dcb?source=rss-dc84d51b8c56------2"><img src="https://cdn-images-1.medium.com/max/1536/1*MybqZVZz_to-LmxwANBq4w.png" width="1536"></a></p><p class="medium-feed-snippet">How a simple mindset shift is changing the way we build websites for good.</p><p class="medium-feed-link"><a href="https://medium.com/@jasonkogan/the-springboard-mindset-rethinking-website-wemplates-with-ai-ia-4279e47c9dcb?source=rss-dc84d51b8c56------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jasonkogan/the-springboard-mindset-rethinking-website-wemplates-with-ai-ia-4279e47c9dcb?source=rss-dc84d51b8c56------2</link>
            <guid isPermaLink="false">https://medium.com/p/4279e47c9dcb</guid>
            <category><![CDATA[wordpress-templates]]></category>
            <category><![CDATA[ai-development]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <dc:creator><![CDATA[Jason Kogan]]></dc:creator>
            <pubDate>Thu, 11 Sep 2025 12:27:42 GMT</pubDate>
            <atom:updated>2025-09-18T02:47:50.309Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A simple guide to freelance pricing]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.startupstash.com/a-simple-guide-to-freelance-pricing-832c230b750f?source=rss-dc84d51b8c56------2"><img src="https://cdn-images-1.medium.com/max/2600/1*EKSYCrn3T6Jg1JNsIK80og.jpeg" width="4491"></a></p><p class="medium-feed-snippet">Are you a freelancer? Do you hire freelancers? Here&#x2019;s a simple way to figure out a fair rate.</p><p class="medium-feed-link"><a href="https://blog.startupstash.com/a-simple-guide-to-freelance-pricing-832c230b750f?source=rss-dc84d51b8c56------2">Continue reading on Startup Stash »</a></p></div>]]></description>
            <link>https://blog.startupstash.com/a-simple-guide-to-freelance-pricing-832c230b750f?source=rss-dc84d51b8c56------2</link>
            <guid isPermaLink="false">https://medium.com/p/832c230b750f</guid>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[freelance]]></category>
            <category><![CDATA[pricing]]></category>
            <category><![CDATA[freelancers]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <dc:creator><![CDATA[Jason Kogan]]></dc:creator>
            <pubDate>Mon, 04 Apr 2022 16:17:43 GMT</pubDate>
            <atom:updated>2022-04-18T15:29:58.770Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Using your UX superpowers to get corporate buy-in]]></title>
            <link>https://uxdesign.cc/using-your-ux-superpowers-to-get-corporate-buy-in-8ef97b9d8d77?source=rss-dc84d51b8c56------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ef97b9d8d77</guid>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jason Kogan]]></dc:creator>
            <pubDate>Mon, 28 Feb 2022 11:28:40 GMT</pubDate>
            <atom:updated>2022-02-28T11:28:40.033Z</atom:updated>
            <content:encoded><![CDATA[<h4>Great user experience hinges on understanding user behaviour and developing empathy. Those goals are equally relevant in getting business stakeholder support.</h4><p>When dealing with larger organizations, those around you may only care about the wireframes you produce, but there’s a bigger picture to keep in mind. Building a narrative about your wireframes and why they are right for your target audience is critical to getting buy-in and bringing stakeholders along. Typical UX tools like Experience Maps, User Flows, Personas, etc are often confusing to non-UX professionals and only by defining a clear vision and strategy will you ensure that stakeholders understand your design decisions.</p><h3>What’s a Vision and Strategy and why do they matter?</h3><p>A <strong>Vision</strong> defines ‘why’ our product is needed by stating the goal that we will strive for in the long run, our “north star”. It is aspirational and communicates where the product is aiming to go and what it’s working to achieve. NOTE: Some may also call this a “Mission Statement”.</p><p>A <strong>Strategy</strong> helps us explain ‘how’ we will reach our desired future state — our vision. It will resemble a high level description of the tactics we will explore in the immediate future.</p><p>Here are the Vision and Strategy statements of some notable brands (can you guess who?).</p><p>Example 1:</p><ul><li>Vision: <a href="https://mission-statement.com/apple/">We believe that we are on the face of the earth to make great products and that’s not changing.</a></li><li>Strategy: Bring the best user experience to our customers through innovative hardware, software, and services.</li></ul><p>Example 2:</p><ul><li>Vision: <a href="https://www.ikea.com/gb/en/this-is-ikea/about-us/the-ikea-vision-and-values-pub9aa779d0">To create a better everyday life for the many people.</a></li><li>Strategy: Offering a wide range of well-designed, functional home furnishing products at prices so low that as many people as possible will be able to afford them.</li></ul><p>Example 3:</p><ul><li>Vision: <a href="https://www.forbes.com/sites/patrickhull/2012/12/19/be-visionary-think-big/?sh=29c0ce2c3c17">Be the earth’s most customer centric company; to build a place where people can come to find and discover anything they might want to buy online.</a></li><li>Strategy: We strive to offer our customers the lowest possible prices, the best available selection, and the utmost convenience.</li></ul><p>The above examples refer to Apple, Ikea and Amazon respectively.</p><p>Let’s take Apple as an example, armed with the Vision and Strategy they prioritized and invested in developing a closed ecosystem. This way all products offer a consistent and easy to use interface, your data is seamlessly synced and you get one continual experience across all your devices.</p><p>Ultimately having a Vision and Strategy helps the business decide what should be in their product (and how to prioritize their roadmap), and what should not be included.</p><h3>How to develop a Vision and Strategy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uvuWroSZMHfd89i-mI_JHQ.jpeg" /></figure><p>I like to develop a Vision and Strategy by performing qualitative user research, dissecting supplemental research studies provided by the business and leveraging data analytics from existing products.</p><h4>Step 1: Conduct interviews and identify key quotes and supporting documents</h4><p>If you’re a UX Researcher, you likely already do this, but for everyone else, you’ll start by building a screener to make sure you identify and interview the right people. You should consider interviewing both subject matter experts within the business as well as your target audience.</p><p>Write and conduct interviews, take notes, and identify key quotes as you go — record your interviews (with permission) and revisit them to get verbatim quotes. There are many <a href="https://medium.com/user-experience-design-1/search?q=qualitative+research">resources available</a> on how to write and conduct user research interviews, so that won’t be covered here. Your interviews will likely yield two things: insights you hear by several interview subjects and additional reports, assets and documents you should review.</p><h4>Step 2: Synthesize the results into Emerging Themes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mdcE0KOc4OcbWyqa_3mshA.jpeg" /></figure><p>Once the interviews are complete, create a simple spreadsheet with all of the quotes you’ve identified throughout the process. You’ll start to notice quotes can be grouped, I call these “Emerging Themes”. As you continue to group your quotes, those Emerging Themes may change and evolve, this is natural. You’ll likely end up with 4–6 emerging themes when all is said and done.</p><p>Now review the additional documents identified by the interview subjects — these could be independent research studies, powerpoint presentations of business strategy, or articles with validated insights. Identify and extract any insights that support the emerging themes you’ve defined.</p><p>If you’re redesigning a product that currently exists, you can also leverage existing data analytics to reinforce your Emerging Themes.</p><h4>Step 3: Determine the impact to your design decisions</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rWIThTGEHc7HGfrfJXCHXg.jpeg" /></figure><p>Finally you’ll identify and suggest how everything you’ve learned will impact your design approach. This could be descriptions or lists of what content and tools should be included and ultimately what questions need to be addressed by your design. Most critically, this will help identify what should not be included in your product. This can be further reinforced with visualizations, low fidelity wireframes, or examples from competitors.</p><h4>Step 4: Define your Vision and Strategy</h4><p>Armed with the Emerging Themes and Design Implications your Vision and Strategy should effectively write themselves. By doing all of this due diligence you’ll have connected the dots from the desires of your target audience and the business to your design decisions that will come to life in the wireframes. Before proceeding, now would be a good time to seek buy-in from the business — After all, they have the final say.</p><p>Getting buy-in is most effective when using a common format that non-UX professionals can understand. In today’s world that’s primarily Powerpoint or similar, but feel free to explore alternatives that work for you and your organization. The key is building a physical asset that communicates the narrative you’ve built and is easily shared within the business.</p><h3>Now bring your design decisions to life</h3><p>That’s it. You’ve now successfully connected the dots and created a narrative that your business stakeholders can buy into and use internally to get corporate alignment (if needed). When your wireframes are presented to the business, everyone will understand the logic behind your design decisions..</p><p>All that’s left to do is usability test your wireframes and <a href="https://medium.com/user-experience-design-1/5-steps-to-properly-synthesize-your-usability-test-findings-a6c7cab52a48">synthesize the results</a>, then launch your product!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ef97b9d8d77" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/using-your-ux-superpowers-to-get-corporate-buy-in-8ef97b9d8d77">Using your UX superpowers to get corporate buy-in</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Your Most Desirable Product, Not your MVP]]></title>
            <link>https://medium.com/swlh/design-your-most-desirable-product-not-your-mvp-44f63918dc73?source=rss-dc84d51b8c56------2</link>
            <guid isPermaLink="false">https://medium.com/p/44f63918dc73</guid>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jason Kogan]]></dc:creator>
            <pubDate>Thu, 13 Aug 2020 14:37:22 GMT</pubDate>
            <atom:updated>2021-09-21T16:57:03.149Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design Your Most Desirable Product, Not Your MVP</h3><p>Are you thinking about bringing a digital product to life? I know your timelines are tight, your budgets are small, and the boardroom is likely full of decision-makers pulling you every which way. When push comes to shove and you’ve got to get your product in the market, someone will likely tell you to “focus on your MVP” — Minimum Viable Product. Let’s unpack what this concept represents:</p><ul><li>Minimum: Only build minimal functionality “needed.”</li><li>Viable: Build functionality that makes sense for the business. If it’s not viable for the business, it doesn’t get built!</li><li>Product: Your “launch-ready,” minimally functional, business-centric, product!</li></ul><p>Further to the above, the word “Viable” is significant to most product people through the lens of Human-Centered Design (HCD).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*6W_UUETr_ltSIfThQZazkg.png" /></figure><p>It’s therefore implied that your MVP <em>should be</em> focused on the business first and (likely) the user second! I would suggest that you consider coming at the issue through a different lens.</p><p><strong>Don’t think about your Minimum Viable Product. Think about what could be your Most Desirable Product and build around that.</strong></p><h3>What is the Most Desirable Product (MDP)?</h3><p>I like to think of the MDP as similar to the structure of the planet Earth: it has a core, the surrounding mantle (where you’ll find the “liquid hot magma”) and the crust.</p><ul><li>The Core: What main functionality would create the absolute Most Desirable Product for your users (based on the problem you’re trying to solve). This is the core of your launch product.</li><li>The Mantle: What foundational functionality is needed in order to support your core functionality.</li><li>The Crust: Now that you’ve got your core functionality and all supporting functionality defined, you need to validate that the planned product is viable for the business (today or in the future assuming your business can afford a runway).</li></ul><p>Without the Earth’s crust, there is nowhere for us (humans) to physically exist — likewise, without the business validation (short or long term), there is no place for your product to exist.</p><p>So the MDP does need to consider business viability, but it doesn’t get in the way of the what the product can be at launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*VMYD82QY3zS6qCDQtoRYaw.png" /></figure><h3>How do you define YOUR Most Desirable Product?</h3><p>Now that we share an understanding of the components that define an MDP I’m sure you’re wondering “How do I actually define the Core and the Mantle? What is my most desired functionality? And what other features do I need to support it?”</p><p>Your list of features is LONG, and your time is SHORT. So let’s build your MDP.</p><h4><strong>Identify the Core</strong></h4><p>The first step is to ensure you know who you’re building for and exactly what you’re building — this may seem obvious, but do you have a clear idea of your target and your “why”? (Check out the Golden Circle if you need clarity on this.)</p><p><em>When I worked on the US Foods digital transformation, the place we were starting from and the place we were going to were fundamentally different.</em></p><p><em>The starting digital experience was a glorified brochure. Potential clients could learn about US Foods and submit a request to become a client. There was a home-grown ecommerce platform available to established customers, but it was lacking compared to the standard digital shopping experience customers experience every day and was drastically underutilized. US Foods offered a plethora of supporting services for customers, each on its own microsite, entirely disjointed from the main website.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PLnkV3TbsMusHnGryvBtnA.png" /></figure><p><em>We identified our audiences (and defined personas) for the new digital experience:</em></p><ul><li><em>New Prospects: First-time visitors to US Foods (the primary target audience of the original website).</em></li><li><em>Leads: A new audience, a New Prospect who has created an account with US Foods but has yet to become a client. They’ll have access to a new and yet-to-be-defined restricted member area that provides value and helps to develop a long and fruitful relationship.</em></li><li><em>New Customer: Leads who have been accepted as full customers. They’ll get access to the restricted member area with additional yet-to-be-defined customer-only tools and services. They’ll need to be onboarded to all new functionality including ecommerce.</em></li><li><em>Legacy Customers: Customers who are used to mainly interacting with their sales reps in person to place orders and had mainly not used the website as there was no value for them (or minimally used it for the ecommerce capabilities).</em></li></ul><p><em>For the purpose of our MDP, we had chosen to primarily target Leads and in doing so, our Core functionality would need to sell the benefits of becoming one.</em></p><p><em>We also needed to define our vision, which (roughly) landed as follows:</em></p><p><em>By creating a universally accessible personalized experience that delivers the right content, products and services to restaurateurs, we will empower them to “make it.”</em></p><p><em>The vision boils down to ensuring all restauranteurs receive a personalized benefit from US Foods that can be accessed wherever they are (at home, on the job, or on the go).</em></p><p><em>With the audience and vision defined, I was able to identify the Most Desirable functionality — the creation of a member area that would provide instant and ongoing value to leads. Whether those leads turn into customers or not, they will appreciate and rely on the value US Foods provides.</em></p><h4><strong>Establish your Mantle</strong></h4><p>The next step is to identify the Core-supporting functionality, but first you’ll need a laundry list of features to cherry-pick from, so if you haven’t done so, brainstorm, dream, and jot down all your ideas (there are no bad ones)! Use whatever tools or process you’re most comfortable with: experience maps, storyboarding, sketching, mind mapping, etc. I’d go further into this topic, but that’s not the focus of this article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MLV4OfFHSDFZlw68W5itBw.png" /><figcaption>For US Foods we did experience mapping with embedded empathy mapping to create high level requirements — NOTE: Yes these are deliberately blurred due to client confidentiality.</figcaption></figure><p>The next step is to identify all of the supporting functionality that is ONLY needed in support of the Core (directly or indirectly). This will likely be a robust list of what you see as dependencies, nice-to-haves and wish list items.</p><p>With your list of supporting functionality plentiful, prioritization will be key to defining your Mantle. While it’s nice to have everything when you launch, it’s just not realistic. Only through functional pruning will your launch product take shape — your MDP.</p><p><em>Knowing our Core audience is registered prospects (Leads) and needing to deliver the best value for them meant that we weren’t going to touch the ecommerce platform for launch. This was ideal because enhancements there would’ve been a deep rabbit hole of complexity and effort on the home-grown platform. There was, however, a long list of features that may be needed to create a value-based member area:</em></p><ul><li><em>Revamped look, feel and navigational user experience</em></li><li><em>Robust and dynamic content platform</em></li><li><em>Authentication functionality (register, login, password reset)</em></li><li><em>Customer segment identification</em></li><li><em>A personalization engine</em></li><li><em>A member-only dashboard with customizable reports</em></li><li><em>Integrated purchase history and ecommerce integration</em></li><li><em>Social media publishing platform for sharing insights</em></li><li><em>Integrated restaurant services (marketing services, menu evolution, waste management, employee management, personnel training)</em></li></ul><p>With your (probably) long list of Core-related functionality, you probably need to prioritize everything. The goal of this exercise is to let you draw some clear lines about what’s important to your Core (for launch), and what can wait.</p><p>In a <a href="https://medium.com/@jasonkogan/how-to-design-rapidly-during-these-unprecedented-times-819da636760f">previous article</a>, I touched on how you might prioritize leveraging the HCD factors as categories, effectively scoring each feature based on its desirability to the user, viability to the business and feasibility to build. For the purpose of MDP, I would look at each feature in your roadmap and modify the scoring as follows:</p><ul><li>Desirability to the user: Score out of 35 (35 = VERY desirable, 1 = no value)</li><li>Viability to the business: Score out of 20 (20 = VERY viable, 1 = no value)</li><li>Feasibility for the tech team: Score out of 45 (45 = VERY easy to build, 1 being very difficult to build)</li></ul><p>The higher the score, the greater the value! You’ll notice that I’ve weighted each category unevenly towards feasibility and desirability — the business viability has a presence, but it’s less important at this point. You may want to tweak how you weight each category, but I find this works for me. With your scoring complete, you’ll have a good guide to deciding what’s in for launch. What comes out of this process should be a Mantle full of functionality that’s easy to build, desired by users, and that supports your Core.</p><p><em>Looking back at the US Foods list of core-related functionality, this is what made the cut:</em></p><ul><li><em>Revamped look, feel and navigational user experience</em></li><li><em>Robust and dynamic content platform</em></li><li><em>Authentication functionality (register, login, password reset)</em></li><li><em>Customer segment identification</em></li><li><em>A p̵e̵r̵s̵o̵n̵a̵l̵i̵z̵a̵t̵i̵o̵n̵ ̵ recommendations engine</em></li><li><em>A member-only dashboard w̵i̵t̵h̵ ̵c̵u̵s̵t̵o̵m̵i̵z̵a̵b̵l̵e̵ ̵r̵e̵p̵o̵r̵t̵s̵̵</em></li><li><em>I̵n̵t̵e̵g̵r̵a̵t̵e̵d̵ ̵p̵u̵r̵c̵h̵a̵s̵e̵ ̵h̵i̵s̵t̵o̵r̵y̵ ̵a̵n̵d̵ ̵e̵c̵o̵m̵m̵e̵r̵c̵e̵ ̵i̵n̵t̵e̵g̵r̵a̵t̵i̵o̵n̵̵</em></li><li><em>S̵o̵c̵i̵a̵l̵ ̵m̵e̵d̵i̵a̵ ̵p̵u̵b̵l̵i̵s̵h̵i̵n̵g̵ ̵p̵l̵a̵t̵f̵o̵r̵m̵ ̵f̵o̵r̵ ̵s̵h̵a̵r̵i̵n̵g̵ ̵i̵n̵s̵i̵g̵h̵t̵s̵</em></li><li><em>I̵n̵t̵e̵g̵r̵a̵t̵e̵d̵ ̵r̵e̵s̵t̵a̵u̵r̵a̵n̵t̵ ̵s̵e̵r̵v̵i̵c̵e̵s̵ ̵(̵m̵a̵r̵k̵e̵t̵i̵n̵g̵ ̵s̵e̵r̵v̵i̵c̵e̵s̵,̵ ̵m̵e̵n̵u̵ ̵e̵v̵o̵l̵u̵t̵i̵o̵n̵,̵ ̵w̵a̵s̵t̵e̵ ̵m̵a̵n̵a̵g̵e̵m̵e̵n̵t̵,̵ ̵e̵m̵p̵l̵o̵y̵e̵e̵ ̵m̵a̵n̵a̵g̵e̵m̵e̵n̵t̵,̵ ̵p̵e̵r̵s̵o̵n̵n̵e̵l̵ ̵t̵r̵a̵i̵n̵i̵n̵g̵)̵</em></li><li><em>M̶u̶l̶t̶i̶-̶l̶a̶n̶g̶u̶a̶g̶e̶ ̶s̶u̶p̶p̶o̶r̶t̶</em></li><li><em>Mobile a̶n̶d̶ ̶T̶a̶b̶l̶e̶t̶ support</em></li></ul><h4><strong>The Crust — Viability validation</strong></h4><p>We’re almost there! You should now have:</p><ul><li>Personas defined and one or more chosen for your Core</li><li>A vision defined for your product</li><li>A robust product roadmap (and whatever supporting brainstorming assets you created)</li><li>Prioritized launch product roadmap (the Core and Mantle functionality only)</li></ul><p>Seeing as our MDP process has been almost entirely focused on everything but the business, now’s the time for a reality check. Speak in whatever language your decision makers speak: prioritized roadmap and vision for product leaders; experience map, sketches and ROUGH wireframes for design leaders; or a PowerPoint presentation with your vision brought to life through your launch plan for business folks.</p><p>Personally, I like telling stories through compelling visuals and tying everything back to the defined vision — I do this using PowerPoint. Either way, before you proceed, the business will need to understand the plan and approve of the direction. If you’ve done things right, they’ll see the (possibly longer-term) value to them and immediate value to the user and approve!</p><h4><strong>Final thoughts</strong></h4><p>As compared to what your typical MVP process might look like, the end result may be similar, but how you got there, and your overall mindset should ensure your product is even more successful.</p><p>The Most Desirable Product process may not work in all scenarios, and like all design process tools, it’s more important to understand the tools in your arsenal so when an appropriate situation arises, you choose the right tool. Perhaps this will be the right tool for you next time you’re launching a product and you’re asked to “define your MVP”</p><p>If you’re curious about the evolution of US Foods, you can <a href="http://usfoods.com/">check out the live website</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lvbrmVBG1an5Kq5OU8nBqA.png" /></figure><p>If you have any questions about any of this or just want to connect, I’m <a href="http://linkedin.com/in/jasonkogan">pretty easy to find</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44f63918dc73" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/design-your-most-desirable-product-not-your-mvp-44f63918dc73">Design Your Most Desirable Product, Not your MVP</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>
        <item>
            <title><![CDATA[5 steps to properly synthesize your usability test findings]]></title>
            <link>https://uxdesign.cc/5-steps-to-properly-synthesize-your-usability-test-findings-a6c7cab52a48?source=rss-dc84d51b8c56------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6c7cab52a48</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[synthesis]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Jason Kogan]]></dc:creator>
            <pubDate>Tue, 28 Jul 2020 20:14:21 GMT</pubDate>
            <atom:updated>2020-07-30T22:12:49.572Z</atom:updated>
            <content:encoded><![CDATA[<p>After I’ve designed anything, I want to validate that I’m headed in the right direction, and you should as well. To do this I take my static page designs and stitch them together in a logical way — in the industry, we call this a “prototype”. Much like a <a href="https://en.wikipedia.org/wiki/Concept_car">car prototype</a> that you might see at a car show, this may be done very early in the design process, and by the time the product hits the market, it might look quite different. That’s because of the findings designers get from the (usability) testing they perform. You might be asking yourself at what stage should I run these tests? And how do I run my tests, what are the dos and don’ts? And who should I get to participate in my tests? And how many should I run? And most importantly (because it’s what I’ll dig into today), how do I decide what makes it into the next version of my prototype?</p><p>So very quickly…</p><p><strong>When should you run your tests and how many rounds of testing should you have?</strong></p><p>That all depends on your product. You can run testing after you’ve done your initial sketches, after your basic wireframes are done, after you add high fidelity content, or colours, or full UI elements, etc. This is likely an article in and of itself, so I’ll just stop here.</p><p><strong>How do you run your tests and what are the dos and don’ts?</strong></p><p>This is definitely a topic for a separate article, but quickly, let’s first clarify that we are not talking about a “user test” (this is not a test about or of the user), we’re talking about “usability testing” which validates organically derived functionality and usefulness or identifies confusion — any pass/fail is a judge of the design and use of the product only, not the user. This should be clearly communicated to your test subjects.</p><p>Additionally, you should set up a mindful scenario based on the goals your users may have while using your product. Don’t guide the user step by step, and don’t use labels that you have in your prototype.</p><p><strong>Who should participate in your tests?</strong></p><p>This one should be pretty straight forward: your target audience — so make sure you qualify your participants first. And yes, you can test with your non-target audience, but they’ll have to “pretend” to be your target audience, or the feedback won’t be entirely relevant, either way this approach is not nearly as effective. And to answer your next question, no, you shouldn’t use the same people for each round of testing, because they’ll have seen your product so their feedback won’t be as genuine.</p><p><strong>How many tests should you run? And at what stage should you run them?</strong></p><p>At each stage through the design process that you want to test your product, you should do so with 5 different people. Why 5? With 5 people you’ll identify 80% of the major issues, so there are diminishing returns after that. It’s true, you’ll just have to believe me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D22cbdyQWVhRKHLPSrgbPA.png" /></figure><p>Now for the point of this article, how do you decide what changes to make based on your test findings?</p><h3>How to properly synthesize test results</h3><p>Let’s use a real-world example to bring these abstract concepts to life.</p><p><em>I recently </em><a href="https://medium.com/@jasonkogan/how-to-design-rapidly-during-these-unprecedented-times-819da636760f"><em>built a digital product for Staples Canada</em></a><em> where teachers would create lists of desired school supplies from the entirety of the Staples product catalogue. Parents would then find their class by searching for their school and teachers name. A list of recommended products are presented to the parent, some are Required (included in the package by default and harder to remove), some are Suggested (included in the package by default and easy to remove) and some are Optional (not included in the package by default, but easy to add). The parent chooses which products they need, adds them to cart, and completes their purchase.</em></p><p><em>Let’s assume that I wanted to run 5 usability tests with real parents — I’d get them to walk through the parent experience under the guise of the following scenario:</em></p><p><em>“It’s time to get school supplies for your child for the upcoming school year, they attend grade 3 at Eastwood Primary School. You have a leftover notebook from last year as well as a stapler, pencil sharpener and a pair of scissors. You know that your teacher, Mrs. Steele, has asked you to go to Staples School Tools to buy the supplies you need.”</em></p><p><em>Ideally, I’d find 5 parents who have children in grade 3 for the tests…</em></p><h4><strong>Record your test sessions (and take detailed notes)</strong></h4><p>Before we talk about the steps of synthesis, it’s worth noting that you should record your test sessions. Make sure to ask your test subjects if it’s ok to record them and tell them what the recordings will be used for — likely just to provide abstracted feedback that will shape your product going forward. No personal information or auditory sound (or video) will be shared, transparency is important. It’s rare that you’ll actually need to identify test subjects or use actual footage or audio from your tests, but it is important to accurately capture as much detail from your tests as possible.</p><p><em>For my tests I use an app on my phone called VoiceRecorderLite, it’s easy to use and feature-rich enough for me. Then I use otter.ai for transcription. I tend to listen to the recordings as they transcribe in case anything gets mis-interpreted. If you don’t think you’ll have time to re-listen to the entire interview again, as you’re making your recordings note down the exact time when your test subjects share something that you think you’ll need, then only transcribe those bits. Some of this is easier done if you can have someone sit in on your tests and take notes.</em></p><h4><strong>Step 1: Identify the findings from each test</strong></h4><p>Use sticky notes (or a spreadsheet) to extract quotes that speak to pain points or general confusion (we’ll call these “findings”) encountered during each test. It’s very likely that you’ll see repeats, that’s expected — in fact, it’s what you’re after.</p><p><em>In my early tests I had two approaches to the class supplies list page and tested both. The user would start on the landing page, enter search criteria, select their class from the search results and get to one of two class supplies list pages — afterwards I’d show them the second one and get comparative feedback. Here’s what the two pages looked like:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OWVFiDR7-xe9GEZoCs6z_Q.png" /></figure><p><em>I received a notable amount of feedback from all test respondents, which would look like a word document with a lot of quotes and raw notes — transcribed from my interviews.</em></p><h4>Step 2: Group your findings into themes</h4><p>Now put all of your findings about similar topics together, creating clusters of findings. You may find that as you cluster your findings that sub-clusters immerge, or that you may want to re-cluster them in a different way, that’s ok, that’s why we’ve used sticky notes! Once you are happy with your clusters, name them, we’ll call these “themes”.</p><p><em>In my case, these were the main themes I created:</em></p><ol><li><em>Navigation</em></li><li><em>“Nice to have” functionality</em></li><li><em>Instruction / copy</em></li><li><em>Add to cart widget</em></li><li><em>Product information and functionality</em></li></ol><h4>Step 3: Consolidate finding and convert them into insights</h4><p>Now that your themes are defined, you should see that the same pain points, frustrations and confusion happen over and over again. Combine all findings that are about a single thing into one and denote the issue (we’ll call this an “insight”).</p><p><em>Using School Tools as my lens, here are some sample insights that were derived from my tests:</em></p><ol><li><em>Ability to Share my list</em></li><li><em>The word “Bundle” is confusing</em></li><li><em>Clarity on the difference between Suggested &amp; Optional products</em></li><li><em>Where can schools go for information?</em></li><li><em>Confusion around number of packages / bundles</em></li><li><em>What’s in my cart?</em></li><li><em>How do I search for / add products that aren’t displayed?</em></li></ol><p><em>As you can see, some of these are simple labeling issues (#3), some are about desired functionality that can likely be added easily (#1, #4, #6) and some are more significant and general confusion that will be harder to solve (#2, #5, #7).</em></p><h4>Step 4: Identify the solutions for each insight</h4><p>Now it’s time to start thinking about how to solve the problems that have come to light. Review each insight and list possible solutions. In some cases, you may not be able to visualize the fix and may need to go back to the drawing board. Much like how you designed the original approach, you may need to sketch, wireframe and test any new approaches depending on their complexity.</p><p><em>Back to the School Tools test results…</em></p><p><strong><em>“Ability to share my list” solutions:</em></strong></p><p>1. <em>Add share link to the top of the page</em></p><p>2. <em>Add share icon to top of page</em></p><p>3. <em>Add “share this list” widget to bottom of page</em></p><p><strong><em>“The word bundle is confusing” solutions:</em></strong></p><p><em>4. Remove the concept of a “bundle” and focus on product importance only (Required, Suggested and Optional)</em></p><p><strong><em>“Clarity on the difference between Suggested &amp; Optional products” solutions:</em></strong></p><p>5. <em>Copydeck updates required</em></p><p>6. <em>Add tooltip on mouse hover or mouse click of the “importance badge” with description</em></p><p>7. <em>Decide if both types are needed</em></p><p><strong><em>“Where can schools go for information?” solutions:</em></strong></p><p>8. <em>Add “Schools” landing page to navigation, this will be a static content page with program benefits</em></p><p><strong><em>“Confusion around number of packages / bundles” solutions:</em></strong></p><p>9. <em>Associate package quantity with “Summary”, instead of “Add to cart” button in “Add to cart widget”</em></p><p>10. <em>Add “How many packages do you need?” prompt to the top of the page</em></p><p>11. <em>Consider moving this functionality later in the user experience (not on this page)</em></p><p><strong><em>“What’s in my cart?” solutions:</em></strong></p><p>12. <em>Add staples.ca cart icon and # of items in cart to header</em></p><p><strong><em>“How do I search for / add products that aren’t displayed?” solutions:</em></strong></p><p>13. <em>Use staples.ca header</em></p><p>14. <em>Inject staples.ca search box</em></p><p>15. <em>Consider this functionality to be available later in the user experience</em></p><p><em>You may have noted that some insights only have a single solution proposal, that’s alright, some problems are simpler to solve than others. You may have also noted that all solutions are numbered, and the numbers don’t reset with each insight. This is deliberate, see the next step.</em></p><h4>Step 5: Map out the solutions on a time vs value matrix</h4><p>Of the solutions that are explored in step 4, you’ll likely be able to make some assumptions on the perceived value of each one to the user (and the business), and how much time each one will take to design (and build!). Some solutions that involve going back to the drawing may turn out better, but they may equally not yield an improvement, it’s hard to say. The simple truth is that you may not have time to design the ideal solution for everything now — also, some things are just better solved only after you have real users using your product. Additionally, what you perceive to yield the most value might take A LOT more time to fix. So, you need to decide which solutions to attempt, and which to defer or ignore. You can do it!</p><p><em>This is how I perceived the time to design vs value matrix for the solutions I identified in step 4. Anything that fell in the top right I focused on (fast and high value). If I had time for items in the top left (fast, but low value) or bottom right (lengthy, but high value), I’d choose to tackle them next. Anything in the bottom left was unlikely to get tackled (lengthy, and minimal value) — luckily I had very few of these!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ddySPLfHth4-e0zCBjCu7A.png" /></figure><h4>That’s it!</h4><p>If you follow the above steps, you will have successfully synthesized the results from your usability tests. The last thing you need to do is just decide which updates you’ll attempt, make the updates, and continue testing and refining your product! Choosing which changes to implement depends on how much time you have, and which are the “right” adjustments for your product, that’s up to you and is just part of the design process.</p><p>Synthesis isn’t that tough, but it’s often rushed, steps are skipped, and assumptions are made without connecting the dots. The practice of User Experience is about many things, finding the intersection of the business, the user, and technical feasibility, and general empathy development, but at its core, it’s critical that all decisions connect and are drawn from insight. It’s alright to make assumptions, but those assumptions should always have some basis from your research, testing, or other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*Ns06iY_MtiEJLW_-" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://twitter.com/uxminaspretas">UX Para Minas Pretas</a> (UX For Black Women), a Brazilian organization focused on promoting equity of Black women in the tech industry through initiatives of action, empowerment, and knowledge sharing. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6c7cab52a48" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/5-steps-to-properly-synthesize-your-usability-test-findings-a6c7cab52a48">5 steps to properly synthesize your usability test findings</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 steps on how to design rapidly (during these unprecedented times)]]></title>
            <link>https://medium.com/@jasonkogan/how-to-design-rapidly-during-these-unprecedented-times-819da636760f?source=rss-dc84d51b8c56------2</link>
            <guid isPermaLink="false">https://medium.com/p/819da636760f</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[schools]]></category>
            <category><![CDATA[rapid-prototyping]]></category>
            <dc:creator><![CDATA[Jason Kogan]]></dc:creator>
            <pubDate>Mon, 13 Jul 2020 21:12:26 GMT</pubDate>
            <atom:updated>2020-07-24T03:38:32.108Z</atom:updated>
            <content:encoded><![CDATA[<p>As I thought about how to share some highlights and lessons from my most recent work, I really wanted to avoid using words like COVID, or “these unprecedented times” but it’s the reality we’re all facing, so instead, I’m leaning in.</p><p>These have been ‘unprecedented times’ on a number of fronts for me — including my work to bring Staples School Tools to life. It’s now four weeks post-launch, most of which was spent “coordinating strategic improvements” and I now feel ready to shine a spotlight on it.</p><p>For Parents, Staples School Tools offers a way to quickly identify what school supplies they need for the educational success of their children, to save them time, money and to help their school through donations.</p><p>For Teachers, Staples School Tools is a way to quickly inform Parents what school supplies are critical to success, to standardize the education experience and get more from their relationship with Staples.</p><p>The most significant complexities come from how School Tools integrates and remains unique from the Staples.ca platform. It offers integrated sign in and products catalogue, and work with the existing cart and order process. The site lives outside of the traditional Staples.ca header and footer, adds “bundling” in cart, has a unique discount and donation program, introduces a new scheduled delivery order type, and offers program-specific products. All told, it is the largest single functional update to Staples.ca since its launch.</p><p>If you’re curious, check it out (<a href="https://bit.ly/3frOwRl">staples.ca/schooltools</a>). If you want to learn more about its creation process during these “unprecedented times”, read on.</p><p>Below you’ll find a high-level overview of my journey that started Feb 1st (with a target launch date of April 1st, read: an extremely aggressive timeline). The steps outlined below are relatively universal to the product development lifecycle, especially when timelines are tight.</p><p>Note that this is not the only way to design rapidly, anyone from the Lean UX world will likely have an opinion, but I’d suspect it’s quite difficult to be lean when you’re working with a big corporation — happy to discuss this and be proven wrong.</p><h3>Step 0: Choose your tools, wisely</h3><p>Before you tackle any complex project you must choose your tools. You likely have many in your toolbox, choose the ones you rely on the most and leverage them. For me that’s:</p><ul><li>Strategy / Decking</li><li>Research, Interviews and synthesis</li><li>Userflows</li><li>Wireframes</li><li>Prototypes</li><li>Spreadsheets and lists</li></ul><h3><strong>Step 1: Be an information sponge!</strong></h3><p>No matter the timeline, the first step is to develop the right context for your project by understanding the background, the competition, and most importantly, your audience. Boardroom meetings were had with store operators, internal folks who ran the former program, and the digital team who would inherit the new program. Surveys and interviews were done with teachers and parents. Explorative research was completed on the former system, the competitors, and the friends (Staples US existing product).</p><h3><strong>Step 2: Define your target users — their goals, motivations and frustrations</strong></h3><p>If this sounds familiar, that’s because it is and would be called a persona. It would typically be used to capture goals, motivations and pain points, it would critically help the designer develop empathy, and would help with corporate alignment. Rather than building formal Personas I developed 3 mindsets that would act as a lens to all of my future thinking. I tend to prefer this less formal approach: the UX designer’s version of method acting.</p><figure><img alt="Each persona you develop should be used as a lens that all things are viewed through." src="https://cdn-images-1.medium.com/max/936/1*c_8BrU6XaZCu88PmHoiDuA.png" /></figure><h3><strong>Step 3: Set your “North Star”</strong></h3><p>Next, turn your research into findings and use them to get further managerial alignment. Set your vision, define your strategy, and set your goal posts. In the case of School Tools we were going to build a “Teacher-based personal assistant for Parents”. Having a clear vision is important — particularly when timing is tight — it helps you focus on the right things, and justifies the things you don’t. For this exercise you’ll need powerpoint (or equivalent): write out your narrative, add your supporting research, keep slides low on text, and tell a compelling story. With your vision defined, you can move into design.</p><h3><strong>Step 4: Design your MVP (actually your MDP)</strong></h3><p>Firstly, I always prefer to design for the <strong>full vision</strong>, exploring all potential features (and I advise you to do the same). I may not fully explore all edge cases or work out the complexities, but I like having the full vision in front of me, then I can figure out what should launch first.</p><p><strong>How to decide on your “MVP”?</strong></p><figure><img alt="Human Centered Design requires consideration for the developers, the business and the user!" src="https://cdn-images-1.medium.com/max/936/1*6W_UUETr_ltSIfThQZazkg.png" /></figure><p><strong><em>Consider your HCD mindset (Viability, Feasibility and Desirability) and what MVP actually means, “Minimum Viable Product”. In other words, what minimal feature-set can we “get away” with, in order for the product to be viable for the business? I would suggest asking a different question, what features are most desired by your audience (and what supporting features do they need)? In other words, what do you need to build first to delivery the Most Desirable Product (MDP) for your audience? Figure that out, and you’ll know what you need for launch.</em></strong></p><p>Once I’ve thought about my MDP, I get to designing. I’m a “pictures worth a thousand words” kinda person, so I like to start by creating a userflow. I use Omnigraffle for this for numerous reasons (I can discuss this separately if you have questions). I start by mapping out all the pages I would need. Parents would need a landing page to search from, they’d need a results page, and they’d need a teacher-created shopping list. What if they can’t find their class? What if they want more information about a product? Are all products equally important? What if they already have products on the list? Let the userflows… flow.</p><figure><img alt="User flows always help to map out the entire customer experience. Start with them, revise them as needed." src="https://cdn-images-1.medium.com/max/936/1*ebh--85jBf3GRPGjFLygYA.png" /></figure><p>Once I knew what pages I needed, I started with some Crazy 8s to jump-start my creative juices and I opened Figma to start designing. Why Figma? I was leveraging the existing Staples Design System (SDS) which was Figma-based, and impressively comprehensive. I moved the mouse around, clicked on some things, watched a “How to Figma” video or two, looked at my Outlook Calendar to remind myself of the timing I was up against, and opened Sketch instead. While I know now that Figma would have likely been the right choice, I simply did not have time to waste fumbling around in a new platform, the clock was ticking and April 1st was not that far away — also I didn’t need the collaboration aspect of Figma as I’d be the only one working on the wires, and I liked Sketch! In short, use the tools you are most comfortable with, unless you have time to explore the new / better option.</p><p>Using assets from the SDS I quickly had a seemingly polished multi-page product — but I had yet to seek internal approval and buy-in on direction. I quickly installed a Sketch Plugin called “Rough”, it would take my nicely polished designs and make a version that looked drawn, it was perfect for demonstrating a few things:</p><ul><li>Leveraging the SDS was the fastest way to build a product that “felt” like Staples</li><li>I could design in high fidelity right from the start, and just “Rough” my designs for feedback and approvals, I know some of you may think this would take more time, but I had all the building blocks, so I used them.</li></ul><figure><img alt="If you’re designing in a higher fidelity out the gate, be sure to make it clear that your work is still WIP." src="https://cdn-images-1.medium.com/max/936/1*8-SgIyjzvR3DL3opRJCXYg.png" /></figure><p>The key to this approach is to be open to any and all feedback and direction — no matter how polished your designs may appear. This process is not about “you” and how “perfect” or “right” you can design out of the gate. I deliberately “Rough” my designs to show that they are malleable. After all, the “U” in “UX” doesn’t stand for “You”, it’s about the “User” — yes they may sound similar.</p><p>Before I knew it, I’d stopped using “Rough” and I just had a polished set of wireframes and a few informal user tests. I didn’t have a functional spec. I didn’t have user stories. I had a vision, I had three mindsets.</p><p>For the record, I did actually start by creating some “traditional” UX assets like formal Personas, and an experience map but quickly abandoned them. I was in a fortunate scenario where I just needed to get to launch in whatever way possible, nobody asked me for any particular deliverables, so I only stuck to those that helped me get there and those that the other parties required. You may need, or may be asked to pull other tools from your toolbox, this depends on the organization and team you’re working with. If you need help figuring out which tools are right for you, I’m happy to help.</p><h3><strong>Step 5: Take a nice break — thanks to COVID</strong></h3><p>In the spirit of “leaning in” to the societal impact of COVID and in offering full visibility, things were on schedule for launch when all non-essential projects at Staples were put on hold, School Tools was one of them; ok this isn’t really a “Step” but it happened, and speed bumps may happen to you. I had no visibility into how this impacted other projects, but to me, it meant that my April 1st date which was 3 weeks away, was no longer, and that School Tools may never see the light of day — this happens, surprisingly often in a corporate setting, priorities change. All development stopped (we’d started building the foundation work for the parent experience). I switched focus to documenting functional specs and building a prioritized and phase-based product roadmap. I hoped that ‘one day’ the project might come back to life, and that when it did my vision could be realized in the way I’d planned.</p><p>I was sad, knowing that I might never get to see the impact of my work on this project come to life. This, above all, is my goal as a designer.</p><h3><strong>Step 5 (for real): Build your prioritized roadmap</strong></h3><p>Days passed. Functionality was documented. Priorities were set. I typically prioritize based on a three-score system:</p><ol><li>How feasible and easy is the feature to build (1 = Very feasible and easy, 3 = Unimaginably difficult!)</li><li>What is the viability and usefulness of the feature to the business (1 = Critical to the business!, 3 = Basically useless to the business)</li><li>How desirable would this feature be to the target audience (1 = Absolutely essential!, 3 = Entirely useless)</li></ol><p>The lower the score, the higher the priority. Is this subjective? Yes. Does it do the job? I believe so. These prioritization categories may look familiar because they are the same three pillars referenced earlier that make up Human Centered Design.</p><p>With a prioritized roadmap in hand and uncertainty around the future of the school year, Staples decided to reignite focus on School Tools. Now more than ever Teacher would need a tool that connected them with their students, ensuring everyone had the supplies needed for success. We re-engaged the development partners and re-started the build process. That said, the school year was impacted and parents’ heads were elsewhere, rightfully so.</p><p>We took the opportunity to assess our priorities and timeline and I proposed building a better and more robust product out of the gate vs our original plan. There were a couple other house-of-cards type decisions that encouraged a later launch date, but parents and teachers would ultimately benefit.</p><h3><strong>Step 6: Create lists of lists and just GSD</strong></h3><p>Once you have the full vision of your product on paper, and a prioritized roadmap, you just have to list everything you need, list all of the steps needed to do the things you need, and track progress as you tick them off your list. There are many tools that you can use for this that include <a href="https://bit.ly/32dJDaX">Basecamp</a>, <a href="https://bit.ly/2WhX4mh">Trello</a>, <a href="https://bit.ly/32hQhwK">ActiveCollab</a>, any collaborative spreadsheet, or even a good To Do app (I’m liking <a href="https://bit.ly/2DBxeTP">Zenkit</a> these days). Here are some of the elements I needed to accomplish for this project:</p><ul><li>Design all edge cases and every function, but stick to those only needed for launch, then design for your other viewports — Mobile in my case.</li><li>Test, test, test, test, test. Refine. Repeat.</li><li>Gather, update, and create the language for every page, every view port, every edge and error case, and the help centre — then edit it, then get approval from legal, then translate it.</li><li>Design for additional languages — French is on average 20% longer than English, so you’ll likely need to make design considerations and tweaks.</li><li>Ensure the Information Models for products on Staples were updated for the functionality — coordination was needed to add meta data to products on Staples for various reasons.</li><li>Given the robust Staples catalogue, ensure Teachers can easily find the best products for them, and suppress the others — customizations to search.</li><li>Ensure that standard Staples cart, checkout order process can accommodate the goal of the program, to save time and money for Parents — this manifested in numerous ways, like showing lists as bundles in cart, auto applying discounts to eligible products, boxing School Tools orders separately, introducing a new type of scheduled delivery.</li><li>Support the operations team on the transition to the new program, through comms and training.</li><li>Ensure analytics are properly planned for and set up.</li><li>Update all email touchpoints to make sure the users experience is cohesive.</li><li>Translate everything into “tech speak” (Jira, and User Stories — in this case, it meant working very closely with the dev partner)</li><li>As functionality came to life, test it, and validate it was built to the vision.</li><li>Prioritize and re-prioritize features, bugs and enhancements as needed — and be prepared to make compromises.</li><li>Track everything that’s done, take detailed notes — this will likely come in handy.</li></ul><p>I think it goes without saying, but this approach can only work if you’re good at juggling and if you have strong leadership, partners and supporting teams; I obviously was able to leverage the full team at Staples to make this happen — over 50 contributing individuals. YMMV.</p><p>Staples School Tools formally launched June 23rd in just under 5 months from drawing board to launch — a corporate project like this could easily take twice that or more. It was an amazing whirlwind journey and I loved every minute of it! Is this the only way to design rapidly? Certainly not, but it works for me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*LpFszVEHcDsuko8jamgFYA.png" /></figure><p>If anything you’ve read today might work for you, use it. If you make anything rapidly as a result of this or you have any tips for next time, share it. And if you have any questions about any of this, ask it (here) — or <a href="https://bit.ly/3gSIM3x">connect with me</a>.</p><p>Otherwise, if you’ve read this far and you’re curious about <a href="https://bit.ly/3frOwRl">School Tools, check it</a> (out).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=819da636760f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>