<?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 Nicolas Backal on Medium]]></title>
        <description><![CDATA[Stories by Nicolas Backal on Medium]]></description>
        <link>https://medium.com/@nicolasbackal?source=rss-6e26a1aa7077------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*pYB3FEORNo9Z36cjFbBgPw.jpeg</url>
            <title>Stories by Nicolas Backal on Medium</title>
            <link>https://medium.com/@nicolasbackal?source=rss-6e26a1aa7077------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:49:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nicolasbackal/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[Colorful Beginnings]]></title>
            <link>https://medium.com/product-cookbook/colorful-beginnings-8934af8aa851?source=rss-6e26a1aa7077------2</link>
            <guid isPermaLink="false">https://medium.com/p/8934af8aa851</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[icebreaker]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[activity]]></category>
            <dc:creator><![CDATA[Nicolas Backal]]></dc:creator>
            <pubDate>Tue, 09 Jan 2024 04:04:55 GMT</pubDate>
            <atom:updated>2024-01-09T04:22:36.642Z</atom:updated>
            <content:encoded><![CDATA[<h4>A fun icebreaker activity for a team offsite</h4><figure><img alt="An illustration showing three wrapped gifts representing the gift exchange described in the article." src="https://cdn-images-1.medium.com/max/1024/1*JmyP7gCDe9nCFxxM2sVnhw.jpeg" /><figcaption>A hidden gift for each team member.</figcaption></figure><h4>The Palette of Engagement</h4><p>A few months ago, we planned our team-wide offsite to close the year. Instead of focusing just on work, we sought to create an environment to foster collaboration, share stories, and create connections. With this aim, we started the day with an icebreaker activity that transformed standard introductions into a surprise, fun, and memorable activity. This was not just about kicking off an event; it was about creating a unique experience that would resonate with each team member long after the week ended.</p><h4>A Colorful Icebreaker Game</h4><p>We chose unique, colorful water bottles as the centerpiece of our activity, but you can use any gift that fits your budget. Wrapped to conceal their colors, these bottles became mysterious gifts, each one holding the promise of a delightful reveal. Paired with each bottle was an icebreaker question, a key to unlock the rich stories and insights every team member held. The setup was simple; we put all the gifts in the middle and started a <a href="https://en.wikipedia.org/wiki/White_elephant_gift_exchange">white elephant</a> round where each member had the option to unwrap a gift and answer its question or steal a previously opened one.</p><p>Once everyone had an open gift, it was clear that our colorful icebreaker was more than just an activity; it was an opportunity for deeper connections, laughter, and team spirit. Each bottle, now a personal keepsake, serves as a reminder of the stories shared and the connections formed. This experience underscored the idea that the most robust teams are built on a foundation of shared experiences and the willingness to open up and connect. So, when planning your next team event, remember that the key to a memorable start isn’t just about the activities you choose but about creating moments that allow each unique color and story within your team to shine through.</p><h3>Recipe</h3><h4>Ingredients</h4><ol><li><strong>One water bottle per participant in various colors:</strong> We bought Owala, but you can use any brand that fits your budget. Don’t worry if you end up having a few duplicate colors; the activity will still work.</li><li><strong>Wrapping paper or bags:</strong> To add an element of surprise and anticipation to each gift.</li><li><strong>Icebreaker Questions:</strong> Write one for each wrapped gift and keep them work-friendly. <em>We are attaching the questions we used a the bottom of this article.</em></li></ol><h4>Step by Step</h4><p><strong>Before the Activity</strong></p><ol><li><strong>Wrap:</strong> Carefully wrap the colorful water bottles individually, ensuring the colors are completely concealed, transforming them into identical-looking parcels of potential and anticipation.</li><li><strong>Attach questions:</strong> Attach one question to each wrapped gift, turning them into catalysts for conversation and connection.</li><li><strong>Set the stage:</strong> Arrange the wrapped bottles in a central location, creating a visual focal point that piques curiosity and excitement. Prepare the space for the activity, ensuring everyone will have the opportunity to engage and participate fully.</li></ol><p><strong>During the Activity</strong></p><ol><li><strong>Kick-off with explanation:</strong> Begin the activity by explaining the rules and the intent behind them. The activity should take around 30 minutes for 20 participants (more or less).</li><li><strong>First choice:</strong> Invite the newest team member to select a wrapped gift. They’ll read the attached question aloud, answer it in front of the group, and then reveal the water bottle and its color. This moment marks the start of the journey from individual to collective sharing.</li><li><strong>Continuing the chain to the right:</strong> As each participant takes their turn, they face a choice: pick a new wrapped bottle or ‘steal’ an already opened one. If they choose to steal, they must also answer the bottle’s question. If someone’s bottle gets stolen, they will get a chance to go again immediately (<a href="https://en.wikipedia.org/wiki/White_elephant_gift_exchange">white elephant</a> style).</li><li><strong>Encourage openness and sharing:</strong> Foster an environment where each answer and story is welcomed with enthusiasm and interest. Encourage participants to listen actively and respond, turning the activity into a dialogue rather than a series of monologues.</li><li><strong>Concluding reflections:</strong> Once all bottles have been chosen and all questions answered, take a moment to reflect on the experience. Discuss the revelations, the shared moments, and how the activity helped everyone see their teammates in a new, more colorful light.</li></ol><h4><strong>Icebreaker questions</strong></h4><p>These are the questions we used, but you can create your own. Feel free to use these by printing, cutting, and attaching one to each gift.</p><ol><li>What is the most interesting place you have ever traveled to?</li><li>If you could have any superpower, what would it be and why?</li><li>What hobby or activity do you enjoy outside of work?</li><li>If you could learn a new skill or talent instantly, what would it be?</li><li>If you were stranded on a deserted island, what three things would you want to have with you?</li><li>What is your favorite way to relax and unwind after a long day?</li><li>What is your favorite thing about the city or town you live in?</li><li>What is the most unusual or interesting job you have ever had?</li><li>If you could have any job for a day, what would you choose and why?</li><li>If you could live in any fictional world, which one would you choose?</li><li>What is one interesting fact about yourself that most people don’t know?</li><li>What is the weirdest food combination you’ve ever tried and surprisingly enjoyed?</li><li>If you could have a personal song that played every time you entered a room, what would it be?</li><li>If you could swap jobs with any colleague for a day, who would it be and why?</li><li>What’s the most hilarious thing that has happened to you at work?</li><li>What’s the silliest nickname you’ve ever had, and how did you get it?</li><li>If you could be any cartoon character for a day, who would you choose, and what would you do?</li><li>What’s your go-to dance move when nobody’s watching?</li><li>If you could only eat one type of food for the rest of your life, what would it be?</li><li>What’s the most embarrassing fashion trend you’ve ever followed?</li><li>If you could be a contestant on any game show, which one would you pick?</li><li>What’s the most adventurous thing you’ve ever done?</li><li>If you could be a professional in any sport, which one would you choose and why?</li><li>What’s the most bizarre thing you’ve ever eaten for breakfast?</li><li>If you could time travel to any decade for a day, which one would you pick, and what would you do?</li><li>What’s your favorite pizza topping?</li><li>Do you prefer reading physical books or e-books?</li><li>What’s your favorite outdoor activity?</li><li>What’s your favorite board game?</li><li>Are you a morning person or a night person?</li></ol><p>Thanks for reading our recipe. Our goal is to share our experiences working together using a short-read format with instructions that you can try on your own — just like a cookbook. We hope you found it useful!</p><p><a href="https://medium.com/u/e617cb34e395">Katie Le</a> &amp; <a href="https://medium.com/u/6e26a1aa7077">Nicolas Backal</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8934af8aa851" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-cookbook/colorful-beginnings-8934af8aa851">Colorful Beginnings</a> was originally published in <a href="https://medium.com/product-cookbook">Product Cookbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The team norms workshop]]></title>
            <link>https://medium.com/product-cookbook/the-team-norms-workshop-3e7bd3888106?source=rss-6e26a1aa7077------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e7bd3888106</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[Nicolas Backal]]></dc:creator>
            <pubDate>Thu, 01 Sep 2022 16:50:35 GMT</pubDate>
            <atom:updated>2022-09-01T16:50:35.765Z</atom:updated>
            <content:encoded><![CDATA[<h4>A tool to improve your team’s collaboration tactics.</h4><figure><img alt="An illustration showing a shape with a missing puzzle piece." src="https://cdn-images-1.medium.com/max/1024/1*a-eJkmheP_XlZghMm6ThqA.png" /><figcaption>The team norms workshop.</figcaption></figure><p>Over time, every team develops ways to interact and communicate with each other. Doing this successfully, even with people outside of the immediate team, is critical for the team to be successful. If team members cannot effectively interact, the team will likely fail. That’s where <strong>team norms</strong> come in!</p><h3>Team norms are a set of guidelines to shape team member interactions.</h3><p>Team norms can emerge naturally or be developed during a team meeting, and more norms can be added as the team evolves.</p><p>For example, if a team develops and launches a digital product, a team norm could be to gather for a celebration. This happened to us naturally; without writing it on paper, it became a norm we adopted. On the contrary, if team members frequently fail to meet due dates or are overcommitting, the team can pause and formally create a norm to plan and set goals each week.</p><h3>You can run a team norms workshop anytime.</h3><p>Even if you’re moving fast, it’s good practice to pause every now and then to reflect on what went well, what needs to be improved, and what needs to be updated.</p><p>We had an offsite coming up, and there were several new members on the team. We didn’t have great onboarding, so we wanted to formalize how our team operates. We thought a team workshop would be perfect for this. In our case, we blocked 1.5 hours during the team offsite, but you can do this any day as long as you block time with no distractions. In terms of cadence, a workshop like this can be done as often as you like; just ensure your team understands the goal and that everyone is equally involved in the process.</p><h3>Running a team norms workshop.</h3><p>Made it this far? Great! Now, let’s go through how to run a team norms workshop.</p><p>As mentioned above, you need a set amount of time where the team can fully concentrate on the activity, so ensure you can make this happen before going any further. On the workshop itself, we recommend starting with a quick intro on what norms are. This should be simple and clear, but if anyone has any doubts, it is time to clear them out.</p><p>The team will work individually and as a group during the workshop on three activities. The first activity involves writing down all the existing norms that are currently in place and voting for the favorite ones. In our case, it was interesting and motivating to see what people voted for, and it helped us validate the norms that were working for the team.</p><p>The second activity involves writing new norms that they’d like to see adopted. These can come from anywhere but should fall under one of these categories: decision-making, conflict resolution, values, and communication. For example, it could be something complex like using <a href="https://www.ncfp.org/knowledge/fist-to-five-voting-and-consensus/">fist of 5 voting</a> or something small like using Confluence instead of Google Docs as the source of truth for all projects.</p><p>The third activity is the hardest one. This involves spending time writing which norms they would like to remove or change. For example, we have a norm of running a team retro once a month, and someone suggested a change to allocate more time for discussion instead of just listing feedback.</p><p>Like most of our workshops, we like to end with voting. We asked everyone to vote for 3 things they’d like to add or change. We then discussed as a group which had the most votes, why we think it was important, and how to implement it potentially. At this point, the workshop is mostly done; the last thing to do is to pick someone to (1) write down existing norms into a “How we work” team charter that is visible to everyone and (2) follow up on the top 3 norms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MmBtwjQiTZMDjBewTDTGfA.png" /></figure><h3>Recipe</h3><h4>Prepare for the workshop</h4><ol><li>Block 1.5 hours on everyone’s calendar and ensure people are fully committed.</li><li>Duplicate our <a href="https://miro.com/app/board/uXjVPfU9SQ4=/?share_link_id=922204191057">Miro template</a> (or create your own) and give edit access to everyone on your team. If you don’t have Miro, don’t panic, you can use any tool that supports a post-it-like experience, like a whiteboard if everyone works onsite.</li><li>Create a short deck or talk that explains what norms are to use as an intro for the workshop.</li></ol><h4>Running the workshop</h4><p>The key for this workshop to be successful is ensuring that time is appropriately managed. Start by designating a timekeeper (this can be you) and ensure they have access to a timer of some sort. If you use Miro, <a href="https://miro.com/marketplace/timer/">their timer</a> feature is exceptional for this.</p><p><strong>Intro: 5 min</strong> — Give an intro to norms and the workshop</p><p><strong>Section 1: “What are the team norms currently in place?”</strong></p><ol><li>5 min — Each member individually writes existing team norms.</li><li>5 min — Individually move these post-its into one of the four categories: Decision making, conflict resolution, communication and tools, and values.</li><li>5 min — Individually heart (or like) the post-its that resonate with you. This is a pulse check on what norms the team appreciates most.</li><li>10 min — Group discussion. Is anything surprising? Which ones received the highest likes? Why?</li></ol><p><strong>Section 2: “New norms to improve the team”</strong></p><ol><li>5 min — Individually write new norms that could benefit the team</li><li>5 min — Move these individually to one of the four categories as well.</li></ol><p><strong>Section 3: “Change or delete norms”</strong></p><ol><li>10 min — Individually write modifications of existing or new norms.</li><li>5 min — Voting time! Each person gets three votes to choose which norms they want to add or changes they want to implement. Keep in mind the voting just applies to the ideas added in sections 2 and 3.</li><li>20 min — Group discussion. What are the main things that people want to remove or change? Were there any surprises? What are people most excited about?</li></ol><p><strong>Conclusion: 10 min</strong> — Ask for volunteers or designate someone on the team to lead the top three voted items. This number is not set in stone; if there are more norms, the team feels strongly about, make sure someone is responsible for making them a reality.</p><h3>Ingredients</h3><ol><li>A whiteboarding tool like Miro that ideally has built-in voting.</li><li><a href="https://miro.com/app/board/uXjVPfU9SQ4=/?share_link_id=922204191057">The team norms workshop template</a>.</li><li>A timer. Ideally, this is a built-in feature in your tool, like Miro.</li></ol><p>Thanks for reading our recipe. Our goal is to share our experiences working together using a short-read format with instructions that you can try on your own — just like a cookbook. We hope you found it useful!</p><p><a href="https://medium.com/u/e617cb34e395?source=post_page-----9cb2d799f7e4--------------------------------">Katie Le</a> &amp; <a href="https://medium.com/u/6e26a1aa7077?source=post_page-----9cb2d799f7e4--------------------------------">Nicolas Backal</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e7bd3888106" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-cookbook/the-team-norms-workshop-3e7bd3888106">The team norms workshop</a> was originally published in <a href="https://medium.com/product-cookbook">Product Cookbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using FigJam to collaborate around copy and language]]></title>
            <link>https://medium.com/product-cookbook/using-figjam-to-collaborate-around-copy-and-language-c0e1d1dafc37?source=rss-6e26a1aa7077------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0e1d1dafc37</guid>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux-copy]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Nicolas Backal]]></dc:creator>
            <pubDate>Fri, 03 Jun 2022 00:17:34 GMT</pubDate>
            <atom:updated>2022-08-28T15:57:58.831Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An illustration showing three versions of the same screen with alternative texts." src="https://cdn-images-1.medium.com/max/1024/1*AmqeOTq3nh9Ia471fFHRTg.png" /><figcaption>Same screen, multiple versions</figcaption></figure><p>Working on UX copywriting is hard. There are many things that the team has to do to get the copy to communicate the right action to the user. Many resources, <a href="https://medium.com/search?source=home-------------------------------------&amp;q=ux+copywriting">articles</a>, and <a href="https://careerfoundry.com/en/blog/ux-design/ux-writing-books/">books</a> talk about writing great copy for your product, but for this short recipe, we want to focus on the tools we use to collaborate around it.</p><h3>Our current toolkit made it hard to collaborate around copy.</h3><p>Katie and I have been collaborating around copy for a while. Whenever we need to brainstorm about it, we usually start on Figma since we have the latest designs there. For the first work session, this worked well, but things started to get more complicated as designs evolved and more people got involved. We inevitably moved those discussions into documents or Slack threads. This made collaboration difficult for all the relevant stakeholders since we didn’t know the source of truth. When it was time for implementation, no one knew where to find the latest version.</p><h3>FigJam saved the day in an unexpected way.</h3><p>When <a href="https://www.figma.com/figjam/">FigJam</a> came around, we started using it immediately since we were always looking to improve our brainstorming sessions. One day, we needed to develop the right copy for an action modal. I copied the screen from Figma into FigJam, and we started adding post-its around it with all the copy suggestions. As the discussion began to pick up, someone on the team double-clicked on a paragraph in the mock itself to explain a new concept. That’s when we realized that the text was editable, but the rest of the frame stayed intact. In other words, anyone could edit the copy, but no one could accidentally move components around. <strong>This was huge</strong> since the fear of destroying the mockup was removed, and anyone could come in, duplicate the screen, and try a new version.</p><p>FigJam quickly became our source of truth for copy brainstorming sessions and final versions. Once the copy was done, the designer could easily copy the screen back to the Figma file, and all the layers and relationships would stay intact.</p><h3>Recipe</h3><ol><li>The designer builds the screens on Figma. In this step, it is crucial to ensure that all the layers and auto-layout are correctly set up to allow text to wrap nicely, even when more lines or paragraphs are added.</li><li>Create a FigJam file and copy over the relevant screens that require brainstorming around copy.</li><li>Share the FigJam file with relevant stakeholders, for example, product managers, content creators, copywriters, etc.</li><li>Teach everyone how easy it is to duplicate screens in FigJam and encourage them to try updating the text.</li><li>Once the team decides on the final version, the designer can copy the screen back to Figma and continue working on the flow.</li></ol><p><strong>Pro tip:</strong> You don’t need to wait for the final version to be ready. It’s so easy to copy screens from Figma to FigJam and back that you can do this process as many times as needed for your project.</p><h3>Ingredients</h3><ol><li>Figma to design and build your screens.</li><li><a href="https://www.figma.com/figjam/">FigJam</a>, a new tool by the Figma team, to brainstorm and collaborate around copy.</li><li>A way to share the FigJam link with your team. We use Slack, but any communication or documentation tool will work.</li></ol><p><em>Please note that Katie and I are not affiliated with Figma or FigJam. This article aims to share how we have to use the tool to improve our design processes.</em></p><p>Thanks for reading our recipe. Our goal is to share our experiences working together using a short-read format with instructions that you can try on your own — just like a cookbook. We hope you found it helpful!</p><p><a href="https://medium.com/u/e617cb34e395?source=post_page-----9cb2d799f7e4--------------------------------">Katie Le</a> &amp; <a href="https://medium.com/u/6e26a1aa7077?source=post_page-----9cb2d799f7e4--------------------------------">Nicolas Backal</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0e1d1dafc37" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-cookbook/using-figjam-to-collaborate-around-copy-and-language-c0e1d1dafc37">Using FigJam to collaborate around copy and language</a> was originally published in <a href="https://medium.com/product-cookbook">Product Cookbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a mid-term prototype to unlock your team.]]></title>
            <link>https://medium.com/product-cookbook/creating-a-mid-term-prototype-to-unlock-your-team-9cb2d799f7e4?source=rss-6e26a1aa7077------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cb2d799f7e4</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[prototype]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Nicolas Backal]]></dc:creator>
            <pubDate>Wed, 02 Mar 2022 01:13:11 GMT</pubDate>
            <atom:updated>2022-08-28T15:58:43.189Z</atom:updated>
            <content:encoded><![CDATA[<h3>Creating a mid-term prototype to unlock your team</h3><h4>How vision and near-term prototypes were not enough to align the team.</h4><figure><img alt="An illustration showing a desktop computer with a website wireframe inside." src="https://cdn-images-1.medium.com/max/1024/1*8KTU_kWOQJ19zuCGQcjtdQ.png" /><figcaption>The mid-term prototype</figcaption></figure><p>A few months ago, we had the opportunity to work on a brand new product which involved launching a net new product to the market. We started with a three-year vision prototype to get buy-in and then immediately went into designing our alpha release to get engineering started. Moving from ten thousand feet high to deep in the weeds confused our team because we didn’t give them anything in between.</p><h3>Vision and near-term prototypes are not enough to align the team.</h3><p>We first developed a 3+ year vision for our product area that was reviewed by the team and approved by leadership. This helped us create excitement and get the investment we needed to fund the idea. You can read more about our process to create a shared vision in our “<a href="https://medium.com/product-cookbook/aligning-the-team-around-a-north-star-3e2b90fa9e68">Create shared focus with vision prototypes</a>” recipe.</p><p>Assuming that everyone now understood where we wanted to go, we switched gears and put our efforts into what we’re shipping first in our alpha and beta releases. We set up launch milestones, and created high-fidelity mocks for the user flows required for each launch. In contrast to the vision prototype we created initially, these were very focused and targeted to solve specific use cases.</p><p>We reviewed these mocks in design reviews with engineering teams and leadership again, but the overall sentiment was confusion and misunderstanding. We heard questions like “You’re showing web, what would it look like on mobile?” and “Why is the experience so hard?”.</p><p>After a few meetings like these, we were in shock. How is it that leadership and the core team agreed (and were excited!) about the vision but were confused about our alpha and beta flows? It turns out there was a missing layer.</p><h3>The unexpected missing layer.</h3><p>At this point, we had a vision prototype meant for long-term vision and a short-term, high-fidelity prototype meant for engineers to build out user flows, like what happens when you click a button. After meeting privately with a few folks on the team, it turns out no one knew what we were going to ship one year from now.</p><p>We realized we needed a <strong>mid-term prototype</strong> that was rooted in reality and could demonstrate what we could build with our resources within one year.</p><p>We blocked two weeks on our calendars and got to work. First, we took our vision and removed all the bits and pieces that we knew would not make it for our initial launch. Second, we looked at how the information architecture and overall navigation would fit in our apps. And third, we built a prototype that showed what we could realistically make available to the public in the next year.</p><h3>A mid-term prototype helped us move forward.</h3><p>After a few rounds of iterations, we brought this new prototype to our core and leadership team. Our goal was to align on what we could GA within one year. We made it clear that we did not want feedback on individual flows and that what we were showing was not a vision.</p><p>The outcome was what we hoped for. People were aligned, and there was a shared understanding of what will be launched for our first release. For example, we showed a clear strategy for our new IA across all clients, including mobile, that showed precisely what we were planning on doing for the first public release. With everyone aligned, we were ready to move back into execution mode at full speed.</p><h3>Recipe</h3><ol><li>Start your project by creating a shared vision and getting it approved by your leadership team.</li><li>Block roughly two weeks on your calendar to work on your general access (public) release. This will be your one-year prototype, where you show what will be launched based on your vision. Note that you don’t need to block your calendar for this prototype fully; make sure that this is your primary focus during this time.</li><li>Get the relevant stakeholders together (in our case, the lead designer, product managers, and engineers), and start by creating a list with the main use cases and flows that will make it to your initial release.</li><li>Take your vision prototype and remove all the features and flows that will not be part of your first public release.</li><li>Study any missing pieces that are needed to tell your public release story at a high level. In our case, we spent a few days aligning on our overall information architecture and navigation, making sure that it fits all of our apps and clients.</li><li>With that, create this new mid-term prototype that shows your first public release product. Remember, this is <strong>not</strong> visionary!</li><li>Present this to your leadership team and get it approved before moving into the short-term features and immediate tasks.</li></ol><h3>Ingredients</h3><ol><li>A brainstorming tool like Figjam or Miro to brainstorm with the team.</li><li>A design tool like Figma to create the user flows and prototypes.</li><li>A recording tool to easily share a demo of your prototype with your team and relevant stakeholders. We use (and love) Loom.</li><li>A presentation tool of your choice to build a deck for readout, like Keynote or Google Slides.</li></ol><p>Thanks for reading our recipe. Our goal is to share our experiences working together using a short-read format with instructions that you can try on your own — just like a cookbook. We hope you found it useful!</p><p><a href="https://medium.com/u/e617cb34e395">Katie Le</a> &amp; <a href="https://medium.com/u/6e26a1aa7077">Nicolas Backal</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cb2d799f7e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-cookbook/creating-a-mid-term-prototype-to-unlock-your-team-9cb2d799f7e4">Creating a mid-term prototype to unlock your team.</a> was originally published in <a href="https://medium.com/product-cookbook">Product Cookbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hey designers and engineers, you can be friends]]></title>
            <link>https://uxdesign.cc/hey-designers-and-engineers-you-can-be-friends-7037abc69a85?source=rss-6e26a1aa7077------2</link>
            <guid isPermaLink="false">https://medium.com/p/7037abc69a85</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Nicolas Backal]]></dc:creator>
            <pubDate>Wed, 15 Dec 2021 11:54:43 GMT</pubDate>
            <atom:updated>2021-12-15T21:10:29.086Z</atom:updated>
            <content:encoded><![CDATA[<h4>The way great designers and engineers think is not that different after all</h4><figure><img alt="An illustration with two hands doing a high five." src="https://cdn-images-1.medium.com/max/1024/1*0vOJyiczqfnesS9it1-wgA.png" /><figcaption>High five designers and engineers.</figcaption></figure><p>Building a digital product is hard. Whether you’re a product designer, a product manager, or an engineer, we all play a significant role in the user experience. And perhaps, one of the biggest challenges we face is building great relationships and communication channels within our teams.</p><p>Over the past few years, I’ve encountered <a href="https://uxdesign.cc/product-designers-are-clashing-with-developers-and-its-ugly-59e9875d9866">countless posts</a> and reads on <a href="https://www.linkedin.com/pulse/gap-egor-kloos/">the gap</a> between product designers and engineers. Somehow it has become evident to our industry that this gap is growing, and it is a problem affecting our product development process. New roles, like the Design Engineer, have emerged trying to bridge the gap and get us to communicate more often with one another.</p><p>While this problem is true for some teams, I’ve had the experience of working with designers and engineers that communicate and build great products. Design and feasibility decisions are made in conjunction, and the outcomes are shown as a reflection of great team ownership and collaboration.</p><h4><strong>What is the secret behind great design and engineer collaborations?</strong></h4><p>The more I heard about this problem, the more I wanted to dig deeper and understand what caused it and how teams are solving it. After watching colleagues work, reading more about engineering processes, and learning from the overall practice, I realized that engineers and designers that collaborate effortlessly are the ones that share the same core principles that fundamentally define their processes. Designers and engineers are not that different, after all. Their way of approaching a problem is similar, and there is a shared understanding of the whys, not just the whats.</p><h3><strong>What are some of the core fundamental thinking principles that designers and engineers share?</strong></h3><h4><strong>Every problem is unique, so they don’t presume a solution.</strong></h4><p>At the heart of their professions, designers and engineers are problem solvers. They rely on tested processes but can quickly adapt and use pattern recognition to come up with ideas.</p><p>Usually, when a problem is presented, many assumptions and possible solutions have been made by different stakeholders. Wise designers and engineers move backward to investigate the origin that caused the problem and dig deeper into those causes, trying to find ways to address the true user needs effectively.</p><p>They also know that almost every problem is larger than it initially appears, and the scope of the work will grow on its own, so it’s better to look at the bigger picture at the beginning, knowing that the team can reduce the scope later.</p><h4><strong>The heart of their process is problem-solving.</strong></h4><p>Engineers and designers agree that the most important part of the process is focusing on the problem. The goal is not to include lines of code, mathematical calculations, or Figma prototypes. The goal is the solution for the problem, regardless of how they got there.</p><p>Great designers and developers focus on the problem and embrace a process that involves understanding that there is always a trade-off — quality vs. cost, speed vs. accuracy, time vs. quality. At the end of the day<strong>, </strong>great products emerge from optimizing among these alternatives and finding the right balance between trade-offs.</p><h4><strong>The components rule the system</strong>.</h4><p>Strong collaboration comes from understanding that every single piece or component is there for a reason. Every element plays a crucial role in keeping the system running, even the smallest ones. Smart engineers and designers keep that in mind when adding new pieces to their products and align on why these should be included in the first place.</p><p>They also know to be careful when asking a component to do more than one thing. At a high level, this can be desirable to optimize cost and time, but letting a piece serve multiple purposes can be disastrous and requires a high level of skill from the user. For example, a button that saves an item on your favorites list <em>and</em> completes a payment can be confusing. That’s why it is better to design and build each part to serve its purpose.</p><h4><strong>They think systematically.</strong></h4><p>Both designers and engineers apply their foundational thinking across all aspects and touchpoints of the problem. That means they think about the whole system and ensure that every single part is there for a reason. While it may feel easier to focus on a piece or feature, they are always taking a step back, studying how a new part will affect the overall system.</p><p>At the end of the day, they understand that the system must be analyzed as a whole, but each part also deserves its own analysis. Each component behaves in relationship with the rest of the system and its connections.</p><h4><strong>Work and communicate on the why, not just the what.</strong></h4><p>When decisions are made, there are reasons behind them. Those decisions are important and were decided for a reason, so articulating the intent is key to great design and engineer collaborations. At the same time, they find a way to preserve critical decisions while exploring new possibilities, allowing new team members to drive initiatives while keeping the overall pace in the right direction.</p><p>In terms of communication, translating complex terminology to words that the relevant audience can understand is as important as the outcome. How can teams be aligned if the members inside are not speaking the same language? This may feel like a waste of time, but wise designers and engineers understand the importance of doing this early on.</p><p>While some of these principles may seem basic or obvious, taking the time to learn and embrace them can feel crunched when trying to build a product on a tight timeline. But doing so early on can have a huge impact on the outcome of the product and increase the chance for a successful launch.</p><p>Want to read more about this topic? Here are some interesting reads I’ve found useful.</p><ul><li><a href="https://uxdesign.cc/true-collaboration-with-cross-functional-peers-engineering-product-management-design-7be163369bb0">True collaboration with cross-functional peers (Engineering + PM + Design)</a></li><li><a href="https://uxdesign.cc/product-designers-are-clashing-with-developers-and-its-ugly-59e9875d9866">Product designers are clashing with developers, and it’s ugly</a></li><li><a href="https://www.linkedin.com/pulse/gap-egor-kloos/">The Gap</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7037abc69a85" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/hey-designers-and-engineers-you-can-be-friends-7037abc69a85">Hey designers and engineers, you can be friends</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[Onboarding new team members]]></title>
            <link>https://medium.com/product-cookbook/onboarding-new-team-members-1cd8bbe8a1bf?source=rss-6e26a1aa7077------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cd8bbe8a1bf</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Nicolas Backal]]></dc:creator>
            <pubDate>Tue, 09 Nov 2021 23:08:29 GMT</pubDate>
            <atom:updated>2022-08-28T16:01:35.310Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An illustration showing a welcome to the team banner hanging from a wall." src="https://cdn-images-1.medium.com/max/1024/1*mq9XMWChSsBzvbmyFoQfNQ.png" /><figcaption>Welcome to the team!</figcaption></figure><h4><strong>When growing your team, make sure everyone is set up for success</strong></h4><p>Hi! We are Nicolas Backal and Katie Le, product designer and product manager at Okta. We have been working together for years, and we want to share the lessons we’ve learned through the lens of a cookbook with detailed recipes for creating a great design-product partnership.</p><p>For the past year, Katie and I have been working together co-owning a couple of scrum teams. We constantly collaborate with our engineering partners and seek constant feedback from other product managers and designers, but the day-to-day work usually comes down to us two. This has worked well since we have created a shared process, and after working together for years, our workstream runs fast and smoothly.</p><p>Recently we were presented with the exciting opportunity to co-lead a new business initiative. This means more responsibility and the opportunity to launch a new product to the market. But like any new project, it comes with challenges, like realizing early on that we were not going to succeed on our own. We needed to build a team, and we needed to do it fast. We had a lot of help with recruiting (thankfully!), but as soon as a new team member joined, a plan was needed to get them started and set up for success.</p><h3>Create a plan to onboard new members to your team</h3><p>Before starting any task, make sure everyone on your team, but in particular new members, has a clear understanding of the project’s vision, any existing foundation work they should know about, and has access to the necessary resources to succeed.</p><h4>Create and share a project vision</h4><p>Imagine you join a team that is building a new transportation vehicle, and as your first task, you are asked to design the steering wheel. Without context, any attempts will likely end in constant failures. How many tires does it have? Does it fly, or does it float? It would help if you had an overview of the project, understand the shared vision, and know how parts connect to successfully design your piece. This is true for almost every project.</p><p>In our case, we started by creating a moon-shot prototype that showed the project’s goals at a high level. We made sure to keep it at a vision level and avoid focusing on too much detail. The goal was to show new team members how the whole machine was supposed to work but still keep the details open-ended before splitting our tasks into pieces.</p><p>Finding the time to do this when your hands are full can be a challenge on its own, but your new team members will appreciate it since it will allow them to start driving sooner and in the right direction.</p><h4>Map any existing products that will act as the foundation for the new initiative</h4><p>Our new project is going to be based on functionality that we support on an existing product. Once the first new members joined our team, I assumed we all understood the existing functionality the same way, but that was not the case. It quickly became evident that without a shared understanding of existing architecture and constraints, we were not going to succeed individually or as a team.</p><p>We decided to take a step back and invest time building materials that highlighted the essential components of our existing product. Once we had this, we blocked time to review it a couple of times and continued doing so until we all understood the foundation needed for the new project. At first, this may seem like a waste of time. Why would you spend resources documenting an existing product? But in the long run, it allowed the team (particularly new team members) to design faster while building on existing architecture.</p><h4>Create an onboarding document and keep it updated</h4><p>When joining a new team is crucial to meet the relevant stakeholders and understand the team’s culture and processes. This has become even harder with the shift towards remote work since it is more complicated than ever to meet everyone on your team and know where to find the needed resources.</p><p>Katie had the great idea to create an onboarding document that we would share with any new colleague that joined our team, regardless of their job or profession. Think about it as a hub or home base, where all the crucial links and stakeholders are listed to help you get started.</p><p>This short hub contains a list of relevant stakeholder responsibilities and how to reach them. We included a section with our culture, where we talk about important meetings, communication channels, and collaboration tools. Lastly, we added links to all the essential documents and libraries someone should have access to get started.</p><p>Keep in mind that this document is and should be an evolving process. People leave, and others join. New documents are created while others become irrelevant, so it’s crucial to keep them updated.</p><h4>Bonus: Invite new team members to relevant channels and meetings</h4><p>Adding new team members to relevant communication channels and meetings sounds obvious, but failing to do so promptly can delay progress in a significant way. At the same time, adding new hires to all meetings and comms can feel overwhelming, so try to focus on the most important one that will help them get started. Do you have a weekly planning meeting? Is there a demo day? Do you have an overall team channel where high-level topics are discussed?</p><p>We created a list with channels and meetings to keep on hand for whenever a new team member joins, and we make it a point to welcome them warmly when they attend a meeting for the first time.</p><h3>Ingredients</h3><ol><li><strong>A prototyping tool to create a vision demo.</strong> We used Figma, but other great resources include Sketch or Adobe XD. Depending on your project, you may use a low fidelity prototyping tool like pen and paper. As long as the story is clear, you should be good to go.</li><li><strong>A recording software that allows videos to be shared easily.</strong> Once we had the vision prototype ready, we recorded ourselves walking through it and shared the link with the team. This made it easier for all of us to access whenever we need a vision refresher quickly. We used Loom, but QuickTime or any other recording tool will do.</li><li><strong>A diagramming tool.</strong> For our existing architecture mapping, we needed a tool that allowed us to create diagrams and flows. We tried FigJam, but we have successfully used Miro in the past. Just remember, it should be easily shared with your team.</li><li><strong>A documentation or writing tool.</strong> For the onboarding hub, you will need a place to write and link all the relevant resources. Honestly, almost any software will work for this nowadays. In our case, we used Google Docs since all our documents live in Drive. Don’t want to start from scratch? Feel free to <a href="https://docs.google.com/document/d/1704z7nj8LV4Evs1wELv9uFjThEn_CG-db0VbJtXDY50/edit?usp=sharing">duplicate and use our template</a>.</li></ol><h3>Recipe</h3><h4><strong>For the vision prototype:</strong></h4><ol><li>Create a vision demo for your project. <a href="https://medium.com/product-cookbook/aligning-the-team-around-a-north-star-3e2b90fa9e68">Here is a deep dive into creating visionary prototypes</a>.</li><li>Once the prototype is created and finalized, record a video with you (or someone on your team) walking through it. This is the same demo you will be doing when presenting during a meeting but recorded instead. Start by creating a quick script, and after a few recording attempts, the video should be ready to go.</li><li>Make sure the video is stored somewhere everyone can access, and the proper sharing permissions have been set. Loom or Google Drive make this easy.</li></ol><h4><strong>For the existing architecture mapping:</strong></h4><ol><li>List the most critical flows and constraints that everyone should know before working on the new project.</li><li>Once you have a list, go through these flows and take a screenshot of each relevant screen.</li><li>Add the screenshots to your diagramming tool of preference and connect the flows accordingly.</li><li>You may notice that some crucial elements cannot be captured with a simple screenshot. You can get creative and add any missing information to your diagram however you want (e.g., using post-its or shapes).</li></ol><h4><strong>For the onboarding document:</strong></h4><ol><li>Create a new document and add a short welcoming intro. Feel free to <a href="https://docs.google.com/document/d/1704z7nj8LV4Evs1wELv9uFjThEn_CG-db0VbJtXDY50/edit?usp=sharing">duplicate and use our template</a>.</li><li>List all the relevant stakeholders and members. Pro tip: link their names to Slack or a wiki directory to make it easier for new members to find them.</li><li>Next, list all important meetings and communication channels that everyone should know about.</li><li>Add a short description of the team’s culture and processes.</li><li>Link any critical documents such as your vision prototype, existing specs, and diagrams.</li></ol><p>Thanks for reading our recipe. Our goal is to share our experiences working together using a short-read format with instructions that you can try on your own — just like a cookbook. We hope you found it useful!</p><p><a href="https://medium.com/u/e617cb34e395?source=post_page-----3e2b90fa9e68--------------------------------">Katie Le</a> &amp; <a href="https://medium.com/u/6e26a1aa7077?source=post_page-----3e2b90fa9e68--------------------------------">Nicolas Backal</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cd8bbe8a1bf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-cookbook/onboarding-new-team-members-1cd8bbe8a1bf">Onboarding new team members</a> was originally published in <a href="https://medium.com/product-cookbook">Product Cookbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aligning the team around a north star]]></title>
            <link>https://medium.com/product-cookbook/aligning-the-team-around-a-north-star-3e2b90fa9e68?source=rss-6e26a1aa7077------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e2b90fa9e68</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Nicolas Backal]]></dc:creator>
            <pubDate>Sun, 02 May 2021 18:03:12 GMT</pubDate>
            <atom:updated>2022-08-28T16:03:54.321Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An illustration showing a rocket flying up to the sky!" src="https://cdn-images-1.medium.com/max/1024/1*hS0U4wdHk9Rjw5BGKa83sA.png" /><figcaption>The vision prototype rocket!</figcaption></figure><h3>Create shared focus with vision prototypes</h3><h4>Inspire and convince teams about your product vision</h4><p>For the past few months, my colleague <a href="https://medium.com/u/e617cb34e395">Katie Le</a> (Product Manager) and I (Product Designer) have been working on solving multiple end-user pain points. These problems came from numerous origins, such as customer feedback, end-user surveys, and internal ideas.</p><p>As we started to work on these, we realized that products that evolve without a vision can end up with features that no one uses or that add unnecessary complexity. To avoid this dilemma and wasting time/money, we decided to create a north star vision prototype for our area.</p><h3><strong>Vision prototypes align the team using images in addition to words</strong></h3><p>Vision prototypes have a lot of similarities with product development prototypes. Both of them serve the purpose of testing and validating our product and design ideas while getting feedback from users as they try to complete a task with an unbuilt product.</p><p>However, vision prototypes have added value in that they help the team make effective decisions in the long run and allow us to discover what the product is missing and what we shouldn’t spend time developing. If a feature is not aligned with the vision, we probably should not spend time on it.</p><p>Lastly, high-fidelity vision prototypes help communicate our ideas to the executive team and other stakeholders. While decks help show the business goals, prototypes show concrete visuals that get everyone on the same page.</p><h3><strong>Creating the prototype is only half the battle</strong></h3><p>We started creating a list of the critical long terms problems that our prototype is looking to solve. Once we had a list of problems, we jointly picked the top solutions that we wanted everyone to visualize. This list quickly became very long, and we had to pick the most abstract or controversial ideas that would most benefit from having a visual.</p><p>Along the way, we reached out to other leaders across corporate development, product marketing, and partnerships to collaborate on ideas. It was key to get buy-in from adjacent organizations so that by the time it got to executives, everyone already felt a part of the solution.</p><p>Next, Katie and I validated our prototype with real customers and end-users. Since this was meant to be a long-term vision, it was hard to get the right level of feedback from our users, so we crafted our questions to be high-level rather than detail-oriented.</p><p>Katie created a deck to outline problems, business goals, and success metrics, and I created a vision prototype. This was only half the battle, though. We spent the next 3 months socializing our vision deck and prototypes.</p><h3><strong>Lessons learned</strong></h3><ul><li><strong>Allocate time to develop your vision.</strong> It took longer than expected — we spent 1 month iterating and designing, and then several months socializing it. Once we did, it was easier to make product decisions because everything we designed, tested, and developed was aligned with our north star.</li><li><strong>Build a case to get more people working on your project.</strong> When executives understood our long-term plan, it was easier to get the time and people we needed to make it happen.</li><li><strong>Avoid focusing on the details.</strong> While we wanted the vision prototype to feel real and polished, it was essential to focus on the big picture and the overall story we were trying to tell. We knew we’d have time to develop the little details and flows once the vision was approved.</li><li><strong>Make your deck short and concise.</strong> Our deck ended up having too many slides in it to start (40+). We had to distill it down into an 8-slide deck, with the prototype, that fit into a 20-minute presentation.</li><li><strong>Start off with a written vision document, </strong>which the PM can drive. We are fans of long-form writing and the clarity it requires you to have. If you can create the long-form doc, the deck and vision prototypes will come more easily.</li></ul><h3><strong>Recipe</strong></h3><p>When you set out to create a vision for your product area, try incorporating a vision prototype in your presentation to get a shared understanding.</p><h4><strong>Ingredients</strong></h4><ol><li>A note tool to brainstorm about the key scenarios you want to include. We used Miro, but any documentation or note-taking tool could work.</li><li>A design tool that has prototyping capabilities. We used Figma, but there are great options out there, like Figma or Adobe XD.</li><li>At least 5 users or customers to validate your ideas with. You can have more, but you start to recognize patterns after 5 users.</li><li>A presentation tool to show your ideas, prototypes, and findings. We used Google Slides since it’s really easy to share and collaborate, but there are some great options out there.</li></ol><h4><strong>Instructions</strong></h4><ol><li>Brainstorm the top 3 to 5 opportunities that are crucial to showing the critical functionality of your product using a note/brainstorm tool. Don’t focus on the details; instead, think 5 years from now.</li><li>Identify your personas and write the most important tasks they will have to complete a task in the same brainstorm tool.</li><li>Draw one or multiple user flows that show the key tasks. Focus on the high-level strokes, not on the details.</li><li>Create a polished prototype without focusing too much on the details, and make sure the flows are clearly prototyped and represented.</li><li>Validate your prototype with your customers or end-users. Record the sessions.</li><li>Create a deck that touches on opportunities, why these opportunities are worth solving right now, and success metrics. Add your vision prototype to the end.</li><li>Socialize with relevant stakeholders.</li></ol><p>Thanks for reading our recipe. Our goal is to share our experiences working together using a short-read format with instructions that you can try on your own — just like a cookbook. We hope you found it useful!</p><p><a href="https://medium.com/u/e617cb34e395">Katie Le</a> &amp; <a href="https://medium.com/u/6e26a1aa7077">Nicolas Backal</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e2b90fa9e68" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-cookbook/aligning-the-team-around-a-north-star-3e2b90fa9e68">Aligning the team around a north star</a> was originally published in <a href="https://medium.com/product-cookbook">Product Cookbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The superpowers of great product designers]]></title>
            <link>https://uxdesign.cc/the-superpowers-of-great-product-designers-d5ea6823b2ac?source=rss-6e26a1aa7077------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5ea6823b2ac</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[superpowers]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Nicolas Backal]]></dc:creator>
            <pubDate>Wed, 10 Mar 2021 11:38:07 GMT</pubDate>
            <atom:updated>2021-03-12T23:34:16.533Z</atom:updated>
            <content:encoded><![CDATA[<h4>And the tale of the five magic skills.</h4><figure><img alt="The superpowers of great product designers written in a comic-styled logo." src="https://cdn-images-1.medium.com/max/1024/1*w2u-CxWcNLwjui7HHUc2yw.png" /></figure><p>Product designers, like super-heroes, are always faced with unprecedented villains. These maleficent beings come in all types, sizes, and shapes, sometimes with powers of their own, and for the most part, they all try to make someone’s life miserable. They come from all over, like a broken flow or a change in customer behavior, and every so often, they evolve into something completely different. The truth is, even if one goes away, there will always be a new villain emerging around the corner.</p><h3>So how do we fight these villains?</h3><p>That’s where product designers come in. Like super-heroes, all product designers have different skills and powers and use these to fight the malefic beasts that are constantly attacking their product users. Sometimes a quick solo fight will do the trick, but in other cases, it can take years for a team of product designers to finally destroy a beast. To understand how product designers fight against these frustrating monsters and how their powers evolve and grow, we need to dive deeper into their origin.</p><h3>How do product designers find their powers?</h3><p>Commonly, product designers start their magic life by getting their base abilities from education. They spend countless hours sitting in classrooms, reading books, and training their craft. Sometimes they even create fake villains to practice the use and strength of their powers. This process goes on until the product designer is equipped with a basic set of capabilities, such as empathy, interpretation, ideation, prototyping, and testing. This essential skill set will act as their armament when the genuine adventure begins in the actual world against real monsters.</p><p>Those necessary skills that school gave them worked great against smaller villains. But as soon as the path widens and the challenges grow, the product designer starts to discover that they need something more against the new significant beast. The kind of magic that they now need is not taught at school or in books- it has to be found, but it quickly becomes their primary source of power once they do.</p><p>Discovering these superpowers is not an easy task for designers. They didn’t get a map to follow, and new paths become constant failures. Yet, patience and persistence eventually lead them in the right direction. Once finally found, these superpowers will accompany the designer in all future adventures.</p><h3>What are these product design superpowers?</h3><p>In reality, every product designer has their superpowers, and they grow and evolve based on the challenges they face. We can see some common ones across great designers, and regardless of how they named them, they act in a similar matter. Without further ado, some of the top 5 superpowers the best product designers share are telepathy, metamorphosis, shapeshifting, panoramic vision, and hypercognition.</p><figure><img alt="The word telepathy written in a comic-styled logo." src="https://cdn-images-1.medium.com/max/1024/1*6xxiqwyXoJ2kLoFvganb_Q.png" /><figcaption>The first superpower: Telepathy</figcaption></figure><h3>Telepathy</h3><p>For product designers, telepathy is the power to receive and transmit information with their super-team continually. Influential designers understand that they are not facing these challenges on their own, and the best results emerge when they collaborate as a team with all the superheroes that fight side to side with them.</p><p>This first superpower starts with their alliance with another superhero, the product manager. Like Batman and Robin, or Misty Knight and Colleen Wing, the product manager is their partner in all fights. They create a strategy together and have each other’s back along the way. One is weak without the other, and their project’s success is a direct result of their constant communication, creativity, and trust.</p><p>Next up are the engineers- the army that makes the magic happen. Without them and their majestic powers (sometimes the product designer doesn’t understand it), the product designer and manager are lost. They ensure the final battle is won, and a constant conversation between them and the designer, along the entire process, produces the best magical outcomes.</p><p>Lastly, they have the invisible force that gives the product designer an unprecedented amount of strength; their peers. Even though each product designer may be fighting their own battles, great designers find ways to help each other and understand that if one wins, they all do.</p><figure><img alt="The word metamorphosis written in a comic-styled logo." src="https://cdn-images-1.medium.com/max/1024/1*sSW5IJvwUXsOiXzMPCbohA.png" /><figcaption>The second superpower: Metamorphosis</figcaption></figure><h3>Metamorphosis</h3><p>The power of metamorphosis allows the designer to evolve their creations as their project progresses continually. After defining their battle and doing their necessary research, the product designer will work some magic and produce a solution to fight the villain. Yet, most of the time, the first solution doesn’t work as expected. Great product designers use this power to transform their designs and come up with many solutions regularly. This process goes on and on until the best solution is presented and used against the villain.</p><p>Legend says that some product designers can keep transforming their creations forever, but at a certain point, with their help of their team, they choose the best design for the battle.</p><figure><img alt="The word shapeshifting written in a comic-styled logo." src="https://cdn-images-1.medium.com/max/1024/1*tb3lm_duA63wIozDKcAnxw.png" /><figcaption>The third superpower: Shapeshifting</figcaption></figure><h3>Shapeshifting</h3><p>It turns out that the creations transform, but the product designer needs to adapt as well. This skill is painful to learn, but when mastered, the product designer will grow at a pace not seen before. To better understand what shapeshifting means, we need to break it down into two stages.</p><p>The first phase includes mastering the ability to seek feedback. By this point, the product designer has learned that feedback is crucial for better outcomes, but it does not always come on its own. The product designer has to leave the comfort zone and seek constructive feedback from their team, colleagues, and even users. This new kind of adventure will initially feel extremely uncomfortable, but soon, it will become part of the creative routine.</p><p>The second phase involves removing the ego and recognizing that they, like any other superhero in the world, can make mistakes, and the best attempt at a given challenge is not always the best. The product designer learns to understand that others are trying to help them and that by listening and adapting to feedback, their magic becomes more powerful. This superpower is probably one of the most challenging to learn and can take the product designer years to master.</p><figure><img alt="Panoramic vision written in a comic-styled logo." src="https://cdn-images-1.medium.com/max/1024/1*n2hJoC9oT11l08wHhGcJyw.png" /><figcaption>The fourth superpower: Panoramic Vision</figcaption></figure><h3>Panoramic Vision</h3><p>On many occasions, organizations are fighting more than one villain at a time. This is true for small startups but becomes more relevant as companies grow, and more super-heroes join the adventure. When this happens, a natural thing to do is split up and have each product designer fight against a unique villain. While this may seem vital since it gives the designer a chance to focus on a single battle, the reality is that their organization is fighting a bigger war.</p><p>This is when the superpower of panoramic vision comes in. Like the Ten-Eyed Man, great product designers learn to focus on their areas while keeping an eye on the whole organization. They master the skill of fighting a single villain while creating outcomes aligned with the bigger goals and think systematically as new solutions emerge.</p><p>This superpower on its own is hard to use, but when combined with the ones listed above, the results can be magnificent.</p><figure><img alt="The word hypercognition written in a comic-styled logo." src="https://cdn-images-1.medium.com/max/1024/1*Q48BP-LPnr6LBGFxxAfeYQ.png" /><figcaption>The fifth superpower: Hypercognition</figcaption></figure><h3>Hypercognition</h3><p>The hypercognition superpower gives the product designer a chance to perform complex mental operations while working on their magical solutions.</p><p>By this point, the product designer has learned that every villain is different, even if they look similar. Every battle is unique and can quickly evolve. This might make it harder to keep using the processes learned at magic school.</p><p>This superpower gives the product designer the ability to create their means and to evolve with it. It touches all of their soft and hard skills and allows them to make each more efficient. Hypercognition changes as new tools are presented while the process evolves and repeats indefinitely. Like villains, new tools and weapons are always around the corner, and the product designer has to adapt their methods for each new battle.</p><figure><img alt="Five icons representing the five superpowers." src="https://cdn-images-1.medium.com/max/1024/1*AwUnSdMz1AyNpPrEURj0DQ.png" /><figcaption>The five superpowers</figcaption></figure><p>Together, the necessary skills and these superpowers will make any product designer more powerful and exceptional against even the most famous monsters. The best part is that every product designer already has a few of them under their magic belt. And if they don’t, they now know they can seek them.</p><p>I hope this guide helps you in your journey and gets you excited about the idea that there are always new skills to learn — best of luck with your future adventures.</p><figure><img alt="The end written in a comic-styled logo." src="https://cdn-images-1.medium.com/max/1024/1*2zsnH-MSQDd-Ig_o_lcMpA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*AMSLjygJs3CJCdp4" /><figcaption>The UX Collective donates US$1 for each article published on our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. 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=d5ea6823b2ac" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-superpowers-of-great-product-designers-d5ea6823b2ac">The superpowers of great product designers</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 5 books that helped me transition to UX design]]></title>
            <link>https://uxdesign.cc/the-5-books-that-helped-me-transition-to-ux-design-4f1be589dab3?source=rss-6e26a1aa7077------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f1be589dab3</guid>
            <category><![CDATA[books]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Nicolas Backal]]></dc:creator>
            <pubDate>Thu, 07 May 2020 11:20:29 GMT</pubDate>
            <atom:updated>2020-05-07T11:20:29.284Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="UX Books" src="https://cdn-images-1.medium.com/max/1024/1*ER15prlShTi_umKzBYnbTA.png" /></figure><p>Transitioning careers can feel like a hard, almost impossible, thing to do. Not knowing where or how to start could be frustrating. Yet, a lot of people go through this process every day.</p><p>A few years ago I decided to embark on this adventure, and discovered that the secret is quite simple: read (a lot). With hundreds of design-related books out there, it can feel quite overwhelming to get started. Here is my personal list of the top 5 books that helped me transition from Architecture to UX Design.</p><p>This list is intended for anyone who wants to transition careers, but also for any designer who wants to learn and deepen their knowledge in UX Design.</p><h3>1. The shape of Design by Frank Chimero</h3><p>This is one of my favorite books on <strong>design theory</strong> and I read it at least once a year. <a href="https://frankchimero.com/">Frank Chimero</a> focuses on the why rather than the how, and explores design practice topics like storytelling, concept, craft, and improvisation.</p><blockquote>“How enables, but Why motivates…”</blockquote><p><a href="https://www.goodreads.com/book/show/13017981-the-shape-of-design">The Shape of Design</a></p><h3>2. UX for Beginners: 100 Short Lessons to Get You Started by Joel Marsh</h3><p>When I decided to transition into UX Design this was one of the first books I read. Since then, it has never left my desk. The book is a great resource for understanding the <strong>practical skills </strong>required to solve digital challenges.</p><p>The book is broken into one hundred short and illustrated lessons that will help anyone get started on the core concepts of UX Design.</p><p><a href="https://www.goodreads.com/book/show/26457147-ux-for-beginners?from_search=true&amp;qid=av6pfbvGOi&amp;rank=1">UX for Beginners</a></p><h3>3. Customers Included (2nd Edition): How to Transform Products, Companies, and the World — With a Single Step by Mark Hurst</h3><p>Another key area that designers need to get their heads around (and be comfortable with) is design research. This book is one of the best I’ve read on <strong>research theory</strong> by answering the question “why do companies so often fail to give customers what they want?”</p><p>Here you’ll find real-world case studies from companies like Apple, Google, and Netflix, that clearly explain why including the customer is an essential ingredient to success for any product.</p><p><a href="https://www.goodreads.com/book/show/25315892-customers-included-2nd-edition">Customers Included (2nd Edition)</a></p><h3>4. Rocket Surgery Made Easy: The Do-It-Yourself Guide to Finding and Fixing Usability Problems by Steve Krug</h3><p>This book is the how-to companion to <a href="https://www.goodreads.com/book/show/18197267-don-t-make-me-think-revisited"><em>Don’t Make Me Think: A Common Sense Approach to Web Usability</em></a><em> </em>and works as a great tool to get started on the <strong>user research practice</strong>.</p><p>In the book, Steve Krug explains an approach to usability testing that anyone can easily apply to their own website or application. You will learn how to test any design, stay focused on what is important, and fix the core problems that emerge.</p><p><a href="https://www.goodreads.com/book/show/6658783-rocket-surgery-made-easy">Rocket Surgery Made Easy</a></p><h3>5. Atomic Design by Brad Frost</h3><p>In our modern world, we have to design interfaces that work for more than one device with sizes and capabilities constantly changing. To make this process easier it is important to get an understanding of how <strong>design systems</strong> work and why they are so helpful.</p><p>This book will be essential for anyone that wants to learn how to roll out consistent, high-quality interfaces, and will teach you how to effectively create and maintain components and pattern libraries.</p><p><a href="https://www.goodreads.com/book/show/35496817-atomic-design?ac=1&amp;from_search=true&amp;qid=chkwSVR6CO&amp;rank=1">Atomic Design</a></p><h3>Bonus books</h3><p>If you are done with the essential books mentioned above and want to get deeper into the practice of UX Design, here are some more recommendations I’ve found quite useful.</p><ul><li><a href="https://www.goodreads.com/book/show/13436116-lean-ux">Lean UX</a></li><li><a href="https://www.goodreads.com/book/show/840.The_Design_of_Everyday_Things">The Design of Everyday Things</a></li><li><a href="https://www.goodreads.com/book/show/17744.The_Visual_Display_of_Quantitative_Information">The Visual Display of Quantitative Information</a></li></ul><h3>Looking for more book recommendations?</h3><p>Here are some of the best lists I’ve seen that I use every time I’m looking for a great design book recommendation.</p><ul><li><a href="https://uxdesign.cc/ux-books-on-user-research-strategy-2c8eeef820a8">UX Books: the essential reading list</a></li><li><a href="https://uxdesign.cc/5-ux-books-thatll-change-how-you-think-about-design-4925a0d51de7">5 UX Books that’ll change how you think about design</a></li><li><a href="https://uxdesign.cc/best-new-ux-books-from-the-last-3-years-d975403b2956">The best new UX Books from the last 3 years</a></li></ul><p>Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f1be589dab3" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-5-books-that-helped-me-transition-to-ux-design-4f1be589dab3">The 5 books that helped me transition to UX 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[Our ever-changing windows]]></title>
            <link>https://uxdesign.cc/our-ever-changing-windows-ea74fa7a9015?source=rss-6e26a1aa7077------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea74fa7a9015</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[t]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[covid19]]></category>
            <dc:creator><![CDATA[Nicolas Backal]]></dc:creator>
            <pubDate>Mon, 27 Apr 2020 12:00:00 GMT</pubDate>
            <atom:updated>2020-05-02T13:27:33.749Z</atom:updated>
            <content:encoded><![CDATA[<h4>A UX designer’s view on how an invisible enemy changed the way we interact through our windows.</h4><figure><img alt="Illustration: He looked out the window Hopelessly, from The Glorious Nosebleed by Edward Gorey." src="https://cdn-images-1.medium.com/max/1024/1*2LMQt9ByWH1AsHptC963fw.png" /><figcaption>He looked out the window Hopelessly, from The Glorious Nosebleed by Edward Gorey</figcaption></figure><blockquote>“My favorite journey is looking out the window.” <strong>Edward Gorey</strong></blockquote><p>Windows. All of them. Regardless of their size or shape, they connect us with people on the other side. We sit on the second floor of what I used to consider a relatively quiet street. Every day hundreds of people walk by it, and I got used to the noise made by their talk, laugh, and walk. I got so used to it that some days I wouldn’t even hear it, even though in the back of my mind there was some comfort knowing it was always there. The noise that came through my window created a strange relationship between the people walking by it and myself, giving a reassuring sense of a passive connection that we are not alone.</p><p>But suddenly it stopped. It happened so quickly that I don’t even know how to describe it. We were all ordered to shelter-in-place to protect ourselves from an invisible enemy, but what we didn’t expect was the silence that came with it. Suddenly, the street felt silent, and the lack of sound created a sense of loneliness and disconnection with my community.</p><p>The window that used to connect me with other people suddenly became empty. I could spend hours looking outside, but I could only find a few strangers wearing a mask trying to get to their destination as fast as they could. No more laughs, waves, or high fives.</p><p>When the windows became empty we decided to look in a different kind of window. One that fits in our pocket and is “connected” to the rest of the world.</p><blockquote><strong>When the “real” windows became empty, we looked for comfort in the digital ones.</strong></blockquote><p>Technology is an amazing thing and it can get us closer to where we want to be. Likewise, the web has done what seemed impossible a few years ago. It created a network of nodes that connect the world in an almost unreal way.</p><p>The first few weeks of digital connections during the shelter-in-place were great. We were able to chat, eat, and laugh with friends from all over the world. This dystopian reality suddenly freed everyone&#39;s calendar, and we were all eager to connect with each other through these digital windows.</p><p>But something was missing. I was able to connect with my friends and family, but I was pulling further away from my immediate community. My apartment window still projected an empty street, and even though I felt close to friends from far away, I wasn’t able to replace that comforting feeling of people walking outside.</p><p>The digital nodes from our social networks, while being great, also create a struggle to remain human. Avatars replace faces, our existence gets replaced with a short description<em>,</em> and the lack of engagement invites the awkward silence. When we use technology to talk with each other, we act in a different way.</p><blockquote>We become the temporary center of attention that comes and goes with the press of a button.</blockquote><p>As designers, we build digital interfaces trying to find the most effective way to complete a goal. What if the goal that I want is to feel there’s a human on the other side, and to have a passive feeling that we are in this together? Will technology ever allow for this to happen? Or will we, as digital designers, continue to design and build windows for quick interactions rather than passive human connections?</p><p>When this strange journey is over, there’s a high chance that many of us will continue to work from home for a long time, and days may go by without physically seeing another human. Even when we do, wearing a mask may become the norm, and facial expressions may go unnoticed. The digital windows may be the only way to see our faces, and while we may need to get used to our empty windows, I hope we can find a way to stay human through our digital ones.</p><blockquote>Will technology find a way to passively connect with each other and give us a sense of community?</blockquote><figure><img alt="Illustration of a man standing inside a phone by Nicolas Backal." src="https://cdn-images-1.medium.com/max/1024/1*7d6ukIPknyjN0jhdklTeuA@2x.jpeg" /><figcaption>Looking through my phone</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea74fa7a9015" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/our-ever-changing-windows-ea74fa7a9015">Our ever-changing windows</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>
    </channel>
</rss>