<?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 Dmitry Moystsrapishvili on Medium]]></title>
        <description><![CDATA[Stories by Dmitry Moystsrapishvili on Medium]]></description>
        <link>https://medium.com/@siropinas?source=rss-cffd025cbbf2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lFWR_k2T6bJYNFS8wsd59w.png</url>
            <title>Stories by Dmitry Moystsrapishvili on Medium</title>
            <link>https://medium.com/@siropinas?source=rss-cffd025cbbf2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:17:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@siropinas/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[My First 90 Days as a Product Designer in a German Company]]></title>
            <link>https://medium.com/@siropinas/my-first-90-days-as-a-product-designer-in-a-german-company-5e8e85232490?source=rss-cffd025cbbf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e8e85232490</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-process]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Dmitry Moystsrapishvili]]></dc:creator>
            <pubDate>Tue, 11 Nov 2025 12:43:48 GMT</pubDate>
            <atom:updated>2025-11-11T12:43:48.158Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o63BQwSrvccLWcYFDThdiQ.jpeg" /></figure><p>Hi everyone! My name is Dmitry Moystsrapishvili, and I’ve just completed my first 90 days working as a Senior Product Designer at a German company. In this article, I’ll share what I’ve experienced so far, what stood out to me, and how processes in my large German company differ from those in Russian ones.</p><p><strong>Disclaimer</strong></p><p>I’ve tried to <strong>keep generalizations to a minimum,</strong> since I understand that every company is different. What I’m describing here is my own experience, as well as that of friends and colleagues who’ve worked both in Germany and in Russia. I’d love to hear about your own experience in the comments — it would be great to compare perspectives.</p><h3>The Probation Period in Germany</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8YkMgHFzyf2SXdxLQq8VQ.jpeg" /><figcaption>Probation period in Germany is 6 months</figcaption></figure><p>In Germany, the probation period is twice as long as in Russia — six months.</p><p>Why is that? I think there are a few key factors at play:</p><ol><li><strong>Processes in large European companies move slower than in Russian ones. You can feel it in everything: <br>(a) </strong>Approvals take longer, and sometimes progress is blocked if someone’s on vacation. In Russian companies I worked for, people would often track that person down or get feedback from other stakeholders to move things forward, <br><strong>(b)</strong> There are many syncs, discussions, and updates at different stages of work — with multiple teams or stakeholders at various levels. Sometimes one stakeholder can block progress until another gives a clear “yes.”</li><li><strong>A more relaxed attitude toward working hours:<br>(a) </strong>Colleagues often finish work earlier (of course, not everyone, but it’s noticeable).<br><strong>(b)</strong> Sick leave is perfectly normal. If someone isn’t feeling well, they can take a few days off without seeing a doctor. There’s even paid “burnout leave” if an employee is officially diagnosed with burnout. My friend’s colleague once took a month off for that — and then extended it for another month.</li><li><strong>Releases are less frequent:<br>(a)</strong> I’ve heard from other designers that some of their features took six months to a year before going live.<br><strong>(b) </strong>In my case, after three months of work, my first (not the biggest) feature is just now being released.</li></ol><p>Because of all this, companies simply might not be able to evaluate whether a new hire is a good fit — both professionally and culturally — within just three months.</p><p>So, the first three months are for onboarding and getting used to the environment, while the next three are about taking ownership and contributing fully.</p><p>In my case, this process was a bit faster, since I usually dive into everything quickly and absorb information fast.</p><h3>What Was New for Me?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aEF09EG9BW57QFid6Mu1gg.jpeg" /></figure><p>When looking for a job, I really wanted to join a <em>German</em> company — one without legacy processes from Russian-style management — because I wanted to see how things worked from a completely new angle.</p><p>I can confidently say: that’s exactly what I got! And I genuinely enjoy it.</p><h4>Trust in Product Design Expertise</h4><p>In my company, people really value the expertise of product designers.</p><p>I can’t speak for all German companies, but from what I’ve heard from other designers here, that’s a pretty common approach.</p><p>In practice, it means that designers’ opinions are respected.</p><p>Managers don’t block decisions or micromanage every step — instead, they discuss, challenge, and collaborate.</p><p>Back in Russia, many designers I know (myself included) often felt like <em>“the creative oddballs”</em> in a team of “serious people doing real work.” I’m glad to say that’s no longer the case.</p><h4>Bureaucracy — in a Good Way</h4><p>All processes are clearly documented.</p><p>And if something isn’t documented yet, it’s expected to be, once consistent patterns emerge. Everyone in the team knows where to find the right process or guide.</p><p>I actually love this approach — I’m someone who always tries to simplify interactions, find bottlenecks, and suggest improvements. It’s much easier to do that when everything is transparent and written down.</p><h4>Alignment with Stakeholders</h4><p>Every stakeholder — both within the product and the company — is genuinely invested in product development.</p><p>I’ve never had such <strong>close collaboration with high-level stakeholders</strong> as I do now. They show real interest, share ideas, and challenge solutions constructively.</p><p>Today, I can freely discuss design ideas, research findings, or results with stakeholders during all-hands or planning sessions.</p><p>In Russian companies, I often wasn’t even allowed into such meetings — <em>“we’ll present it ourselves; that’s for managers only.”</em></p><p>I think this reflects the still-developing product design culture in many Russian companies. But regardless of the reason, it definitely made the work less satisfying.</p><h3>What I Especially Like?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sNdClAPZwrpoWEO_2XiVpA.jpeg" /></figure><h4>Cross-Team Alignment</h4><p>Transparency between teams is something we really emphasize.</p><p>We have joint planning sessions and syncs at different stages, even if we’re working on unrelated topics.</p><p>That’s incredibly valuable, because new product ideas often emerge from <strong>synergy between teams.</strong></p><p>A simple example: one team plans to launch a new newsletter about Topic A, while my team works on Topic B, which complements it perfectly.</p><p>Together, we can combine our efforts, save resources, and launch both initiatives in collaboration.</p><p>In contrast, I once worked at a Russian company where the marketing team spent months redesigning the brand identity with an external agency — without ever consulting the product design team.</p><p>As a result, we had to figure out later how (and where) this new identity could even fit into the product. The lack of coordination and trust seriously hurt both the team’s reputation and the product’s quality.</p><h4>Feedback Culture</h4><p>Here, feedback is meant to help you grow — not to criticize you.</p><p>Stakeholders don’t go negative; they give constructive input.</p><p>I often hear phrases like:</p><blockquote><strong>“My expectation is…”</strong> or <strong>“If I were you, I would…”</strong></blockquote><p>This way, feedback becomes direction — not judgment. And when you receive it, you feel supported and motivated to improve.</p><p>Back in university or in some Russian workplaces, I often got the opposite: vague criticism, endless edits, and little clarity on what exactly needed improvement.</p><p>It created a vacuum of feedback — and a tense atmosphere. Nobody wins in that scenario.</p><h3>Conclusion</h3><p>So, my first 90 days in a German company have given me a lot of new professional experience.</p><p>I’ve not only adapted to a different pace and process but also immersed myself in a completely new product culture.</p><p>Here are the key takeaways I’ve learned:</p><ol><li><strong>The German approach is about sustainability, not speed.<br></strong>The goal isn’t to “move fast,” but to build thoughtfully. It may feel slower — but the results are stronger and more stable.</li><li><strong>Design expertise is trusted.<br></strong>Product designers are heard and respected. Instead of micromanagement, there’s collaboration and constructive challenge.</li><li><strong>Documentation and “bureaucracy” actually help.<br></strong>When everything is documented, it’s easier to understand how things work, spot bottlenecks, and improve them.</li><li><strong>Stakeholder collaboration happens at a higher level.<br></strong>You can communicate directly with decision-makers, influence outcomes, and feel part of the bigger picture.</li><li><strong>Feedback culture is about support, not criticism.<br></strong>Constructive phrasing and a genuine desire to help foster a comfortable environment for growth — not defense.</li><li><strong>Alignment and openness between teams.<br></strong>Cross-team transparency leads to creative synergies and stronger solutions.</li></ol><p>Here are my previous articles on how to build a strong product design portfolio:</p><ol><li><a href="https://medium.com/@siropinas/how-to-create-a-strong-product-design-portfolio-in-2025-and-get-hired-part-1-16889999c255"><strong>How to Create a Strong Product Design Portfolio in 2025 and Get Hired (Part 1)</strong></a></li><li><a href="https://medium.com/@siropinas/how-to-create-a-strong-product-design-portfolio-in-2025-and-get-hired-part-2-2519b3b9d5fc"><strong>How to Create a Strong Product Design Portfolio in 2025 and Get Hired (Part 2)</strong></a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e8e85232490" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Create a Strong Product Design Portfolio and Get Hired (Part 2)]]></title>
            <link>https://medium.com/@siropinas/how-to-create-a-strong-product-design-portfolio-in-2025-and-get-hired-part-2-2519b3b9d5fc?source=rss-cffd025cbbf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2519b3b9d5fc</guid>
            <category><![CDATA[how-to-get-hired]]></category>
            <category><![CDATA[product-design-portfolio]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design-portfolio]]></category>
            <category><![CDATA[portfolio]]></category>
            <dc:creator><![CDATA[Dmitry Moystsrapishvili]]></dc:creator>
            <pubDate>Sat, 30 Aug 2025 12:07:36 GMT</pubDate>
            <atom:updated>2026-10-20T16:50:32.690Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ivza2B3shiusGGKjOhrH0w.jpeg" /></figure><p>In 2023–2024 I was a hiring manager and brought 7 product designers into my team. Over the last year, I personally went through interviews with 52 companies and received 2 offers — I accepted one of them.</p><p>Of course, this long journey started with a product design portfolio.</p><p>In the <a href="https://medium.com/@siropinas/how-to-create-a-strong-product-design-portfolio-in-2025-and-get-hired-part-1-16889999c255">first part of this article,</a> I explained what types of product portfolios exist and how they are perceived by the design community and hiring managers.</p><p>In this second part, I’ll talk about how recruiters and hiring managers actually screen your cases, how many cases you should add to your portfolio, and how to describe them so you can <strong>get invited to interviews — and ultimately land your dream job.</strong></p><h3>Topics I’ll cover in this article:</h3><ol><li>How many cases should you include in your portfolio?</li><li>How to describe a case</li><li>What hiring managers pay attention to</li><li>What to do with NDA cases</li><li>Extra tips</li><li>My “humble” opinion</li><li>Conclusion</li><li>Useful resources</li></ol><h3>How many cases should you include in your portfolio?</h3><p>Across different resources (and from designers and hiring managers alike), you’ll often read that a solid product portfolio consists of 2–3 well-developed cases relevant to the job you’re applying for.</p><p>But is that really the case? Let’s break it down.</p><h3>Situation 1: Too few cases</h3><p>If your portfolio only has a couple of cases, a recruiter or hiring manager will review it quickly, pull out the details they need, and make a decision right away.</p><p>Usually, they’ll pick cases to look at based on the most appealing cover or short description.</p><p><strong>Here’s the catch:</strong> some hiring managers assume that <strong>2–3 cases signal a lack of experience </strong>— that you’re either an intern or junior designer. Think of it this way: you call yourself an artist, but in your gallery you only have three arts. Visitors would naturally ask, <em>“Is that it? Where are the rest?”</em></p><p>The same goes for product portfolios. Even if the cases are real and nicely presented, doubts about your competence may arise simply because the hiring manager wants to see more variety before making a decision.</p><p>Also, with just 2–3 cases, <strong>it’s hard to showcase the full breadth of your experience (especially if you’re at Senior level).</strong> Personally, I keep dedicated cases for leadership tracks and process-building within teams because I find it important to show hiring managers that I’m ready to grow into management responsibilities.</p><h3>Situation 2: Too many cases</h3><p>What if your portfolio contains 10 or more cases?</p><p>In that situation, recruiters and managers will usually pick just a few — they don’t have the time to go through everything. That’s why it’s crucial to help them choose: add covers that clearly reflect the case, short descriptions, and tags (more on that later). This way they’ll focus on the most relevant projects for the role and quickly decide whether to invite you for an interview.</p><p>But again, the <strong><em>hiring manager factor</em> comes into play:</strong> some managers might feel overwhelmed and unable to choose. Yes, it happens. In that case, you either get rejected immediately, or they randomly open the first cases they see — which may not be the ones most relevant to their product. That can lead to another rejection simply because your showcased experience didn’t match their needs.</p><p>On the flip side, some managers are looking for top talent and will review multiple cases thoroughly, especially if they see strong potential.</p><h3>So how many cases should you include?</h3><p>Honestly? For some recruiters and managers, 2–3 are enough. For others, 7–10 feels right.</p><p>The problem is: <strong>you’ll almost never know which camp your stakeholder falls into.</strong></p><p>If you’re sending highly targeted applications, you can sometimes check the hiring manager’s social media: in their posts, podcasts, or articles they might share opinions about professional matters, including portfolio expectations. Then you can adjust your application accordingly.</p><p>If you’re mass applying — say, 20–40 applications per day (like I did) — you can’t customize for everyone (and you won’t rebuild your website for each vacancy). In that case, I recommend <strong>sticking to a golden middle ground: 4–7 cases (especially for Senior level),</strong> showcasing your most relevant and impactful work.</p><h3>One more thing — portfolio format matters:</h3><ol><li>If it’s a website, Notion doc, or any advanced text editor, adding 7 cases isn’t a problem.</li><li>If it’s a PDF presentation, once it goes beyond 40–50 slides it becomes too heavy to read — so in that format, it’s better to stick to 2–3 cases.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jYtTkuAlfYcHk73EHW_VgA.jpeg" /><figcaption>How many cases should be included in a portfolio?</figcaption></figure><h3>How to describe a case?</h3><p>Let’s say you have a great product design case and you want to add it to your portfolio. Where do you start?</p><p>Here’s a “golden formula” I’ve found useful and recommend for describing any product case:</p><p><strong>1. Project description (short summary)</strong></p><ul><li>What the project was about, how long you worked on it, who the participants were, and 1–2 final screens.</li><li><em>Goal</em>: help stakeholders quickly understand whether this case is relevant to them.</li></ul><p><strong>2. User problems and pain points</strong></p><ul><li>Describe user struggles before your design. Add metrics, analyst insights, UX research findings.</li><li><em>Goal</em>: show that you think product-first and design to solve real problems, not just to make things pretty.</li></ul><p><strong>3. Research</strong></p><ul><li>Data collection, validation, competitor analysis, user interviews.</li><li><em>Goal</em>: show you can dive deep into problems and generate insights.</li></ul><p><strong>4. Solutions</strong></p><ul><li>What you implemented to fix user problems. Mention prioritization.</li><li><em>Goal</em>: demonstrate structured problem–solution thinking and business/user alignment.</li></ul><p><strong>5. Design process</strong></p><ul><li>Lo-fi, hi-fi prototypes, user flows, brainstorming sessions.</li><li><em>Goal</em>: show the raw process, not just polished UI.</li></ul><p><strong>6. Testing</strong></p><ul><li>Usability tests, A/B tests, 5-second tests, card sorting, etc.</li><li><em>Goal</em>: prove that you care about usability and validation.</li></ul><p><strong>7. Development handoff</strong></p><ul><li>Figma specs, design reviews, dev collaboration.</li><li><em>Goal</em>: show you work effectively with developers.</li></ul><p><strong>8. Results &amp; metrics</strong></p><ul><li>Relative numbers (e.g., “Retention Day 7 improved by 3%”).</li><li><em>Goal</em>: highlight measurable business impact.</li></ul><p><strong>9. Your role</strong></p><ul><li>Your personal contribution at each stage.</li><li><em>Goal</em>: emphasize <em>your</em> value, not just “we as a team.”</li></ul><p><strong>10. Future plans</strong></p><ul><li>Roadmap, next sprint, V2.</li><li><em>Goal</em>: show long-term thinking.</li></ul><p><strong>11. Challenges (optional)</strong></p><ul><li>Where things went off-script, unexpected issues, how you solved them.</li><li><em>Goal</em>: show adaptability and problem-solving under imperfect conditions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZGTcVcuSknMY45T1Bkt-Cw.jpeg" /><figcaption>Approximate structure of a product case</figcaption></figure><h3>What hiring managers look at</h3><p>There are <strong>no universal recipes to please everyone —</strong> different hiring managers want different things. But here are the patterns:</p><h3>Portfolio 360</h3><p>Some managers look for <em>generalists</em>. A T-shaped designer who knows multiple areas is a good fit for startups or design studios. In such portfolios, you’ll see web, mobile, animation, illustration, even 3D.</p><h3>Niche portfolios</h3><p>Others want very specific expertise — fintech, onboarding flows, Growth/Retention, iOS-only, etc. This is common in large companies with specialized teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EhgWdroOYEPB2aGlo0zaSQ.jpeg" /><figcaption>Brief overview of portfolio types</figcaption></figure><h3>UI-first portfolios</h3><p>Visuals often come first. If your portfolio looks outdated, many hiring managers will dismiss it, no matter how solid the process descriptions are. Clean UI, typography, spacing, and hierarchy matter.</p><h3>Process-first portfolios</h3><p>Some hiring managers care more about your problem-solving and product thinking. But beware: overly detailed process slides can backfire — I once had a Head of Design ask me why I showed feature prioritization in my test assignment, implying “Do you think that’s your job here?”</p><p>Also, time matters: some say portfolios are reviewed <a href="https://www.linkedin.com/pulse/demystifying-ux-portfolios-confessions-from-recruiter-holly-bail/">for 2 minutes,</a> others —<a href="https://presentum.io/design/hiring-explained/evaluating-portfolio-and-resume?utm_source=chatgpt.com"> 55 seconds.</a> If the first impression is good, they’ll dig deeper.</p><p>In short: <strong>your portfolio is always a balance</strong> between hiring managers expectations and how you present your experience in the most compelling way possible.</p><h3>What to do with NDA cases?</h3><p>Many designers have NDA-protected work they can’t publish openly. What to do?</p><ul><li><strong>If open publication is forbidden</strong> (common in B2B):<br>You can password-protect your portfolio page and share it with recruiters. In interviews, show the work <em>but anonymize data</em> (fake numbers, changed labels).</li><li><strong>If publication is allowed after release</strong> (common in B2C):<br>Once your work hits the App Store, Mobbin, company blogs, or conference talks, you can safely publish it. Sometimes you’ll need manager approval first.</li></ul><h3>Extra tips</h3><ol><li>Add cases as soon as they’re released (when NDA allows).</li><li>Use relative metrics, not absolute (competitors can calculate product economics if you use absolute numbers in your product cases).</li><li>Always read your employment contract carefully.</li><li>Get portfolio reviews from multiple designers (ideally hiring managers).</li><li>Don’t constantly redesign your portfolio — if you’re getting interviews, it’s working.</li><li>Don’t overload cases with endless screens.</li><li>Don’t write walls of text — unless you’re sure your audience appreciates it.</li></ol><h3>Conclusion</h3><blockquote>There’s no such thing as a “perfect portfolio.”</blockquote><p>Too much depends on the company, the product, and the specific hiring manager. But some universal rules increase your chances:</p><ol><li>Aim for <strong>4–7 cases</strong> — fewer is risky, more is overwhelming.</li><li>Structure matters more than form: follow the chain <em>problem → research → solution → results</em>.</li><li>Respect NDA and contract limitations.</li><li>Update regularly — let your portfolio evolve with you.</li></ol><p>In the end, your portfolio isn’t a fixed set of rules — it’s a living product. It should grow with your experience and adapt to different situations, always answering the key question:</p><p><strong>“Why should we invite you to an interview?”</strong></p><h3>Useful resources</h3><ol><li><a href="https://www.youtube.com/watch?v=zOz96zcI7b4&amp;pp=ygUObWlybyBwb3J0Zm9saW8%3D">Miro team’s portfolio reviews</a></li><li><a href="https://youtu.be/AQMhB_pLdro?si=sYUAEW0AzyezP3Wq">Guide to building niche portfolios</a></li><li><a href="https://www.linkedin.com/pulse/rethinking-future-product-design-portfolio-what-we-even-overland-ogzkc/?trackingId=FUqx6CuZQ0egtEwHuBwZiw%3D%3D">The future of product design portfolios</a></li><li><a href="https://www.linkedin.com/posts/lena-kul_i-can-predict-your-portfolio-rejection-in-activity-7361702701547642880-obUu?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAABB3w-8BaBOoC74nVdPKXS4o9U4_bq8O4jg">Portfolio red flags</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2519b3b9d5fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Create a Strong Product Design Portfolio and Get Hired (Part 1)]]></title>
            <link>https://medium.com/@siropinas/how-to-create-a-strong-product-design-portfolio-in-2025-and-get-hired-part-1-16889999c255?source=rss-cffd025cbbf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/16889999c255</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-design-portfolio]]></category>
            <category><![CDATA[design-tips]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[job-hunting-tips]]></category>
            <dc:creator><![CDATA[Dmitry Moystsrapishvili]]></dc:creator>
            <pubDate>Sat, 26 Jul 2025 09:22:54 GMT</pubDate>
            <atom:updated>2026-10-20T16:50:50.513Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FQ_FWz8fWoksPjee98Yrcw.jpeg" /></figure><p>In 2024–2025, I was job hunting in Germany for a Senior Product Designer position. Over that time, I sent out around <strong>600 applications</strong>, interviewed with <strong>52 companies</strong>, completed <strong>13 design tasks</strong> (2 whiteboard challenges and 11 case studies), and received <strong>2 offers</strong>.</p><p>This series of articles is a deep dive into that journey — the challenges I faced and the lessons I learned along the way.</p><p>The <strong>first article</strong> focuses on <strong>product design Portfolios</strong>: the different formats out there, how recruiters and hiring managers evaluate them — and which ones actually work.</p><p>Throughout my search, I came across countless articles and portfolio guides, but very few took into account the <strong>realities of the hiring process</strong> — and that context matters. Every hiring manager thinks differently. They come from different backgrounds, experiences, and priorities, which makes it nearly impossible to predict what exactly they’ll be looking for.</p><p>For context: I’ve also been on the other side of the table — as a <strong>product Team Lead at RBC</strong> and <strong>Senior Product Designer at MTS</strong>, I’ve reviewed my fair share of portfolios. (spoiler: that experience didn’t help me much in the 2024–2025 job market)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9mVPnxqxjfkA67SwvuQ7QQ.jpeg" /><figcaption>My Job Hunt in Numbers</figcaption></figure><h3>Introduction</h3><p>I’ve often seen — in chats, advice threads, and conversations with other designers — that a <strong>Personal Portfolio Website</strong> is treated almost like a silver bullet.</p><p>The idea seems to be: <em>if you’re a product designer and you have a website plus a solid CV, you’re practically guaranteed to get that first interview invite</em>.</p><h3>Market and Company Specifics</h3><p>I was primarily applying for jobs in <strong>Germany</strong>, occasionally sending out applications to other EU countries like <strong>Poland, Cyprus, Spain, Portugal, the Czech Republic</strong>, and <strong>Estonia</strong>.</p><p>Depending on the local job market and the company itself, expectations around what makes a “great” product design portfolio can vary significantly.</p><p>One particular challenge in <strong>Germany</strong> is the application process itself: many job portals and internal HR systems only allow you to <strong>attach files</strong>, meaning there’s often <strong>no field to paste a link</strong> to an online Portfolio. If your Portfolio exists only as a Website, there may simply be <strong>no way to submit it</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5W78DhMRLgyLtr-4H_Jwkw.jpeg" /><figcaption>Attaching a Portfolio Document to Your Application</figcaption></figure><p>In these cases, candidates are expected to submit a <strong>PDF file</strong> with detailed product design case studies — most commonly formatted as a <strong>Presentation</strong>.</p><p>Some companies may ask you to <strong>upload a PDF</strong> <em>and</em> include a <strong>link to your Portfolio Website</strong>. Others will allow <strong>only one option</strong>, either a file or a link.</p><p>That’s why I strongly recommend having <strong>multiple versions</strong> of your Portfolio ready, so you can easily adapt to each application format.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ev9Kh5FBvOHhelEPohxxBg.jpeg" /><figcaption><strong>Attaching a Link or a Link with a Document to an Application</strong></figcaption></figure><h3>Portfolio Formats</h3><p>Over the past four years, as a Hiring Manager, I’ve encountered various formats that Product Designers use to present their case studies. Below, I’ll describe each format in detail — including its pros and cons, reputation and unique features, and examples from other designers’ portfolios.</p><p><strong>Here is the list of Portfolio Formats I’ll cover in this article:</strong></p><ol><li>Portfolio Website</li><li>PDF file formatted as a case study presentation</li><li>Notion pages with a tree-like hierarchy</li><li>A “Website” created in Figma (a clickable prototype resembling a site)</li><li>Links to presentations made in Figma</li><li>Links to Behance case studies</li><li>Screenshots of product interfaces without any descriptions</li></ol><h3>Portfolio Website</h3><blockquote>A Portfolio Website is arguably <strong>one of the best formats</strong> for a Product Designer’s Portfolio.</blockquote><p>Leads and Hiring Managers most often recommend having a Website — it’s seen as a quality benchmark and an industry standard. I’ve heard this many times from design Leads in YouTube videos, LinkedIn posts, and Telegram chats with job seekers.</p><h4>Pros</h4><ol><li><strong>Easy to read and navigate</strong> (if the design is good)<br>Information is well-structured, navigation is smooth, and you can quickly find the needed case by preview. Since recruiters often skim Portfolios very quickly, it’s crucial to give them the <em>maximum amount of info about you right on the first page.</em> A Website helps with that.</li><li><strong>The “You’re a Product Designer, so you should have a Website” factor<br></strong>Many — including Hiring Managers — believe that if you design interfaces, you should also have your own Portfolio Website. Having a good Website often puts you at an <em>advantage during candidate selection.</em></li><li><strong>Maximum freedom<br></strong>You can design the website any way you want (typography, sizes, spacing, colors, etc.), add animations (like Lottie, Rive, or video showreels), and organize information and cases however you wish. You can essentially realize any design idea. Whether you <em>should</em> do all that is another question (I’ll return to this later).</li></ol><h4>Cons</h4><ol><li><strong>Cost<br></strong>Publishing a Website usually costs money. For example, Webflow’s free plan allows only two pages — not enough for a Portfolio. Framer offers a bit more flexibility on their free tier. Figma Make is a professional-level paid plan (as of 2025). So <em>you should budget for hosting</em> if you choose a paid solution.</li><li><strong>Learning curve<br></strong>Every Website-building platform is a separate product with its own interface, features, and quirks. Learning all of them takes time.</li><li><strong>Time for design and development<br></strong>Unless you use ready-made templates, designing from scratch (e.g., on Webflow) <em>requires significant effort.</em> You need to sketch the structure, create low-fidelity prototypes, define basic components and UI kits (to make future edits easier), build main pages, make responsive versions (Web, Mobile, Tablet), and test everything thoroughly. This all takes a lot of time.</li></ol><h4>What’s Important to Know</h4><p>Here, I’ll share my empirical experience both as a candidate and a Hiring Manager.</p><ol><li><strong>Recruiter instructions from a Hiring Manager’s perspective<br></strong>When a Hiring Manager gets approval to hire and starts searching for a Designer, they give instructions to Recruiters about <em>what criteria to use when screening candidates.</em> For example, I might be looking for a Product Designer to work on an iOS mobile app with personalization features for a new product. What kind of candidate do I want? Most likely, someone whose Portfolio includes mobile apps, personalization, and strong UI — since the product is new. One mandatory criterion might be a Portfolio Website. I might tell recruiters to <em>strictly shortlist only candidates with Websites </em>(even if they come from strong referrals). That means if you don’t have such a Portfolio, you likely won’t be considered, even if your resume and skills perfectly match the role. I once watched a video by a Lead in Berlin who said he never looks at Portfolios unless they are in Website format.</li><li><strong>Too much design on a portfolio site — not always a good thing<br></strong>I’ve often seen candidates’ Portfolios or reference sites overloaded with design: lots of animations, glitch effects, typography trying to be “super beautiful and unusual,” huge decorative headlines behind which the actual case study is hard to find. I get the desire to create something beautiful, but the function of a Portfolio is to make information <em>accessible and readable </em>— after all, we’re talking about Product Design, not graphic or communication design. If it’s hard to find the case study amid all the typography, hiring managers will likely close that Portfolio and move on to the next candidate.</li></ol><h4>Where Can You Build a Portfolio Website?</h4><p>Today, there are many platforms for building Portfolio Websites. Each has its pros and cons, which I won’t go into here. I’ll just say that my current site is built on Webflow, which I find attractive for its price-to-value ratio and features.</p><p>After the <strong>Figma Make </strong>launch, I definitely want to try designing a site there, since it makes editing and scaling easier and faster. It seems like a very flexible tool.</p><p>Here’s a quick list of some platforms that can help you create your Portfolio website, with brief descriptions:</p><ol><li><strong>Webflow<br></strong>Ideal for those who want to build a responsive site with custom animations without needing a developer. Requires a <em>significant investment of time </em>to learn.</li><li><strong>Framer<br></strong>Combines a visual editor with ready-made components, allowing quick site launches. <em>Has templates</em> available for customization.</li><li><strong>Tilda<br></strong><em>Easier to learn than Webflow,</em> convenient for working with blocks, includes built-in animations and basic analytics tools.</li><li><strong>Figma Make<br></strong>A tool that transforms Figma designs into ready-made websites. Convenient because you don’t have to leave Figma, and its AI can generate sites from text prompts, <em>significantly speeding up development.</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5-3mCIdYIiDT0Rqk4C7hKA.jpeg" /><figcaption>Summary: Portfolio Website</figcaption></figure><h3>PDF Portfolio Presentation</h3><p>A <strong>PDF Portfolio</strong> is a very common format on the German job market.</p><p>As mentioned earlier, some application forms don’t even have a field for a website link — only an <strong>Attach File </strong>input. In such cases, if you don’t have a PDF file ready, you’ll have to rely on the hope that the recruiter or hiring manager will open the link to your site if you’ve included it in your CV.</p><p>It can work — but it’s far from a guaranteed method.</p><p>That’s why I recommend having <strong>both</strong> a website <strong>and</strong> a PDF version of your Portfolio. I know it takes a lot of time and effort, but it significantly increases your chances of getting invited to a first interview.</p><h3>Pros</h3><ol><li><strong>Easy to format, edit, and update<br></strong>Creating a Presentation in Figma is relatively fast. One slide = one key idea, one short paragraph, and one or two screenshots or UI frames. This strict format is actually quite comfortable to work with. You can even use a ready-made Portfolio template from the Figma Community, customize the design if you want, and simply fill it with content. If something doesn’t feel right, you can easily rearrange slides, swap case studies, add a cover page, etc. Doing the same on a website can take much longer.</li><li><strong>Time-saving<br></strong>You don’t need to learn a new tool to create a PDF Portfolio — Figma is more than enough to quickly put together a solid presentation and start applying.</li><li><strong>Completely free<br></strong>No comment needed. You can build and export your PDF Presentation entirely for free, even on Figma’s Free plan.</li><li><strong>Maximum control over attention<br></strong>Presentations are viewed <em>slide by slide. </em>That means viewers won’t randomly jump around like they might on a Website. You can guide them through an “ideal” storytelling path — and most likely, they’ll follow it.</li></ol><h3>Cons</h3><ol><li><strong>No interactive elements<br></strong>A PDF File can’t include hover animations, dynamic transitions, or micro interactions. That makes the Portfolio feel less “alive” compared to a Website.</li><li><strong>Slide count matters<br></strong>Hiring Managers and Recruiters won’t be thrilled to open a 100-slide deck. Unlike Websites, where you can quickly skim and pick a case or two, PDFs require linear reading. That’s why you need to keep your PDF Portfolio <em>within a reasonable length.</em></li><li><strong>Large file size<br></strong>PDF Portfolios can get very heavy due to all the images, screenshots, and visual content. Ideally, you should compress your PDF to under 50MB. However, many compression tools reduce quality — and I’ve had cases where full-color images turned black and white after compression. I couldn’t find a tool that fixed this consistently, so for some assignments, I had to send <em>uncompressed PDFs. </em>On top of that, <em>some companies set very strict file size limits</em>for uploads — I once came across a 5MB limit. What can you even attach at 5MB? I still have no idea…</li></ol><h3>What to Keep in Mind</h3><ol><li><strong>Table of contents<br></strong>Just like a case list on a Website, a clear Table of Contents helps Hiring Managers quickly jump to the most relevant case studies. It also gives a high-level overview of what your Presentation includes.</li><li><strong>Slide numbering<br></strong>Adding “X/Y” slide counters in footers (e.g., 5/34) gives viewers a sense of how much is left to go. A small detail — but combined with the Table of Contents, it shows you care about the viewer’s time and experience (which reflects well on you as a Product Designer).</li><li><strong>One slide = one idea<br></strong>To hold attention and improve comprehension,<em> stick to one idea per slide.</em> Keep text minimal. This greatly increases the odds that someone will make it to the end of your Presentation.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9TRhga3ml4MXyFObPSJ9Wg.jpeg" /><figcaption>Summary: PDF Portfolio Presentation</figcaption></figure><h3>Figma Presentation</h3><p>A <strong>Figma presentation</strong> is essentially the same format as a PDF Portfolio, but with a bit more flexibility, since it’s built as a <strong>prototype inside Figma</strong>, styled like a slide deck.</p><h3>Pros</h3><p>All the benefits of a PDF Portfolio apply here as well — but there are a few extra advantages:</p><ol><li><strong>Interactive elements<br></strong>Since this is a Figma Prototype, you can include things like animations, buttons, GIFs, Lottie files, and even videos (if you’re on a paid plan). If these interactions are well-integrated into the storytelling and used sparingly, the result can be a <em>very engaging and pleasant experience.</em></li><li><strong>No file size worries<br></strong>With a Figma Presentation, there’s no need to think about file size — you’re just sharing a link, not uploading a file, which simplifies the submission process.</li></ol><h3>Cons</h3><p>While Figma Presentations share the same <strong>slide count limitations</strong> as PDFs, they also come with a few significant drawbacks:</p><ol><li><strong>Not everyone can open a Figma link<br></strong>During your job search, your Portfolio might be viewed by anyone — a Recruiter, Hiring Manager, Designer, Developer, or someone from Marketing.</li><li><strong>Not all of them will be able to open a Figma prototype<br></strong>For example, recruiters often don’t have a Figma account, and they’re unlikely to create one just to view your portfolio.</li><li><strong>Access issues<br></strong>Sometimes candidates send a link <em>without view permissions.</em> In these cases, reviewers have to request access — and in fast-paced hiring workflows, they might not bother. Even if they do, it creates friction, delays the process, and can cost you attention that quickly shifts elsewhere.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OHJMpTyugApRbFjRTWulgg.jpeg" /><figcaption>Summary: Figma Presentation</figcaption></figure><h3>“Website” in Figma (Clickable Prototype Styled Like a Website)</h3><p>I’ve come across Portfolios like this a few times — and to be honest, they looked quite solid.</p><p>It’s essentially a <strong>hybrid format</strong>: a Portfolio Website recreated as a C<strong>lickable Figma Prototype</strong>.</p><h3>Pros</h3><p>This type of prototype usually replicates the <strong>structure and design</strong> of a real portfolio website, so it shares <strong>all the same advantages</strong> as a standalone site.</p><h3>Cons</h3><p>All the typical downsides of hosting and maintaining a website disappear — because there’s <strong>no hosting fee</strong> (it’s just a Figma prototype).</p><p>The only downside is the <strong>potential access issues</strong> mentioned earlier under Figma Presentation — not everyone may be able to open or view the prototype smoothly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0rHoZDrFOsvfMzjWsX2HrA.jpeg" /><figcaption>Summary: “Website” in Figma</figcaption></figure><h3>Notion Pages with Tree Hierarchy</h3><p>Notion is often used to showcase case studies in a format similar to a Website.</p><h3>Pros</h3><ol><li><strong>Almost free “hosting”<br></strong>A Notion Portfolio is an almost completely free way to present your product cases. The only big drawback is that in the free version, each file uploaded has a size limit — max 5MB per file. So you won’t be able to upload a single 10MB file; you’ll need to compress large images.</li><li><strong>Easy editing and scaling<br></strong>Notion allows you to quickly and effortlessly create new case pages, organize them in the desired order, and create nested pages as needed.</li><li><strong>Time-saving<br></strong>Just like with a PDF Portfolio, you can build a Notion Portfolio without spending extra resources learning new tools.</li></ol><h3>Cons</h3><ol><li><strong>Limited tools<br></strong>Notion’s functionality for creating a visually rich Portfolio is <em>quite limited: </em>no option to choose custom fonts, limited typography size choices, few text highlighting options, and a small default color palette. Together, these limitations narrow your creative possibilities, which may make your Portfolio less attractive compared to competitors.</li><li><strong>Difficult to view<br></strong>The same downside as with Figma files or Figma “sites”: not all Stakeholders can open a Notion Portfolio, reducing your chances of progressing to interviews.</li><li><strong>Negative reputation<br></strong>Many Hiring Managers — especially within the design community — have a negative view of Notion Portfolios and might not even consider candidates who use this format.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OkciZaaiiSl95IGBQ6KD9w.jpeg" /><figcaption>Summary: Notion Portfolio</figcaption></figure><h3>Behance Portfolio</h3><p>Many Designers still send links to their Behance profiles or individual case studies as their Portfolio.</p><h3>Pros</h3><ol><li><strong>Free and simple tool<br></strong>Behance is free and quite straightforward for publishing Case Studies.</li><li><strong>Designer recognition<br></strong>Behance allows you to <em>earn jury recognition and award ribbons.</em> While this might not directly influence a Hiring Manager’s decision, it can attract attention because ribbons aren’t given out to every project, even high-quality ones.</li></ol><h3>Cons</h3><ol><li><strong>Outdated format<br></strong>Nowadays, Behance is seen less as a portfolio platform and more as a <em>social network for Designers.</em> People use it mainly for inspiration, browsing references, following peers, and community engagement.</li><li><strong>Hard to select case studies<br></strong>Often, applicants share a link to their entire Behance profile instead of specific cases. Experienced Designers may have many projects, making it difficult for Hiring Managers to decide what to focus on. This can overwhelm them and reduce your chances.</li><li><strong>Unclear individual contribution<br></strong>Behance cases often represent team projects with multiple Designers involved. Although roles are usually listed (often at the end), it can be hard for Hiring Managers to <em>separate your work from that of your colleagues.</em> This makes it difficult to assess your personal contribution and determine if you fit the role.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i2R79SrZJnyrdaIC9OS1sw.jpeg" /><figcaption>Summary: Behance Portfolio</figcaption></figure><h3>Screenshots of Product Screens Without Any Descriptions</h3><p>I think this format shouldn’t even be considered a Portfolio, because simply showing screens without any commentary has long been a <strong>big no-no</strong> (though I still saw such applications in 2024).</p><h3>My “Modest” Opinion</h3><p>No matter how many opinions I read about Portfolio Formats, most sounded toxic and absolute: <em>“You’re job hunting for too long because you don’t have a website.”</em></p><p>From my own experience, Portfolio format <strong>doesn’t really affect the conversion rate to interviews much.</strong></p><p>I went through multiple interview stages with big companies using Notion Pages, PDF Presentations, and a Webflow Portfolio Website.</p><blockquote>If one Hiring Manager has certain preferences, it doesn’t mean others will shortlist candidates the same way.</blockquote><p>When I hired Designers for my team in 2023 and 2024, I reviewed different Portfolios: Behance cases, links to Figma and Behance (honestly, just out of curiosity). A couple of times, Figma “Websites” and Notion documents were very well designed, and I never regretted opening those links. For example, one of my mentees/friends/former colleagues with a Notion Portfolio got an offer from one of Yandex’s flagship products.</p><p>With this short paragraph, I just want to ask everyone once again <strong>not to be categorical and limit themselves to one opinion</strong>. Such attitudes often sound toxic, short-sighted, and — frankly — hurtful on a human level.</p><h3>Interesting Insights from Personal Experience</h3><p><strong>Hiring processes vary across companies</strong></p><p>Different teams<strong> look for candidates in different ways.</strong> In one company, a Recruiter reviews the Portfolio and resume first, then passes them to the Hiring Manager if everything looks good and fits the job criteria. In another company, the Recruiter might conduct the initial interview — you get excited thinking the process has started — but then the Portfolio is shown to the Hiring Manager, who doesn’t like it, and you get rejected.</p><p>Why is this important for candidates? From my experience, it’s crucial for managing expectations and <strong>reducing emotional disappointment</strong> after being rejected following an interview with a Recruiter. The Hiring Manager might reject you just because they didn’t like the Portfolio. Personally, I believe that to save everyone’s time, the Hiring Manager should immediately review Portfolios shortlisted by the Recruiter.</p><p><strong>Your portfolio is your product</strong></p><p>You can easily call your Portfolio <em>your product.</em> Here you are the Designer, Developer, UX Researcher, Product Manager, and tester all at once. That’s why it’s very important to think about all product aspects of your portfolio:</p><ul><li><strong>How users interact with your portfolio</strong> (Hiring Managers, Recruiters, potential Colleagues).<br>For example, you may have prepared an amazing PDF Presentation — but it’s 200MB in size. I understand there are many images, but often people don’t want to wait so long to download it. <em>Compress the file </em>so Recruiters can easily load and forward it, even with slow internet. Small things like slow loading can spoil the impression, which is especially critical during a quick screening stage. Once, I received a file that was several gigabytes… I don’t even remember what was inside, but it was something terrible.</li><li><strong>MVP is also a product<br></strong>If you haven’t finished everything but want to start applying, you can leave less important things for later. There’s always a version 2! In your MVP, you can include the most important elements and add the rest over time.</li><li><strong>Consistency of user experience is important<br></strong>If it’s a Website, the case pages should likely have the same structure, interaction patterns, color tokens, and typography. This helps users not get lost or confused while consuming the content.</li><li><strong>Test your Portfolio thoroughly.<br></strong>Check how fast your Portfolio loads (too many animations on a site can slow page load), whether all PDF pages remain in color after compression (sometimes color is lost), that all buttons on the site lead to the correct pages, that Vimeo animations embedded in Behance cases play properly, that Figma or Notion Portfolio links open for users without accounts, and how content displays on Web, Mobile, and Tablet. It’s very important to <em>verify all these little details.</em></li></ul><h3>Conclusion</h3><blockquote><strong>There is no perfect Portfolio format</strong></blockquote><p>What works for one Hiring Manager might not suit another at all. One might insist on having a Website, while another prefers everything to fit into a PDF that opens without authorization.</p><p>In the 2024–2025 market, a Portfolio is not just a collection of cases but a <strong>Product with a clear goal:</strong> to pass the screening and get an interview invitation. This means you should treat it like a product: think about the users (Recruiters and Hiring Managers), consider platform limitations, test responsiveness, and — most importantly — make it easy for people to understand who you are, what you’ve done, and why they should choose you.</p><blockquote><strong>Portfolio format is just a tool</strong></blockquote><p>It’s not the format itself that matters, but how clearly and convincingly you present yourself in it. A well-structured Notion document can work better than an overloaded Webflow site. And a clean PDF presentation with a table of contents can outperform a Behance portfolio with a few ribbons.</p><p><strong>If in doubt — </strong>create an MVP now and improve it later. The main thing is not to get stuck in endless portfolio revisions, as that is a <strong>huge waste of resources.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16889999c255" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Micro Animations in Product Design as a Way to the User’s Heart]]></title>
            <link>https://medium.com/@siropinas/micro-animations-in-product-design-as-a-way-to-the-users-heart-8447ce73b916?source=rss-cffd025cbbf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8447ce73b916</guid>
            <dc:creator><![CDATA[Dmitry Moystsrapishvili]]></dc:creator>
            <pubDate>Thu, 18 May 2023 13:54:46 GMT</pubDate>
            <atom:updated>2023-05-20T12:19:17.159Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7NwNjcVewncnyaMfGi_W6w.png" /></figure><h3><strong>Intro</strong></h3><p>In today’s digital age product designers are constantly striving to create user experiences that could be both <strong>functional and emotionally engaging.</strong> One design element that has emerged as a powerful tool in achieving this goal is micro animations.</p><p>Micro animations are small, subtle animations that are integrated into a product’s user interface. They are used to convey <strong>feedback, provide context and enhance the overall user experience</strong> bringing product close to what we call <strong>Minimal Lovable Product</strong> <strong>(MLP).</strong></p><p><em>In this article we will explore the importance of micro animations in product design as a way to reach a user’s heart (bring product closer to MLP) and increase product’s metrics.</em></p><h3>Animation impact on product</h3><p>Let’s talk about how micro animations affect a product generally and user experience in particular.</p><blockquote><em>Firstly, I’d like to consider the </em><strong><em>functional aspect</em></strong><em> of animations in a product. It’s more about practical benefits for users that help them do their jobs properly and successfully</em></blockquote><h4><strong>Feedback</strong></h4><p>Animations indicate to users that their actions are completed, profiles are registered or verified, etc. That makes users feel more in control of their experience and relieves anxiety or anger while completing their tasks.</p><p>For example, when user shazams a song in a loud bar and the App can’t recognise a song, the animation and constantly changing text show user that the shazamming process is still running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gMbiJyP5g8wathY2qscXAA.gif" /><figcaption>Song recognition process in Shazam</figcaption></figure><h4><strong>Improved Navigation</strong></h4><p>Animations also play a role in improving navigation within the product and guide the user through the product. Seems like it’s obvious today, but animated transitions from current page to the next page (e.g., when user taps the cell to view the content) show how exactly user may return to the previous page. It is simple as that: just swipe back — from left to right. That’s where animations suggest the solution and improve user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5wE5lpB9pZgGX-b3jIIxEA.gif" /><figcaption>Telegram transitions inside a chat/channel and back</figcaption></figure><p>Imagine, if there aren’t transition animations in a product. Here in Ozon Bank the next page just appears overlaying the previous. That may (even for a fraction of a second) confuse a user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RZBTUGTBwcWetEKRWxBHOA.gif" /><figcaption>Transitions inside cells and back in Ozon Bank</figcaption></figure><h4><strong>Enhanced Understanding</strong></h4><p>Micro animations also help improve the user’s understanding of the product’s functionality.</p><p><em>Animated onboardings</em> demonstrate how the product works and draws the attention to new features promoted by stakeholders (e.g., to increase some metrics).</p><p>VN uses animated onboarding to helps users better understand how the video editing process works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z7g66ZRMeEedrzXseiLswg.gif" /><figcaption>Animated onboarding in VN</figcaption></figure><p><em>Premium features promotion</em> may look better with micro animations. They provide users with all necessary information about values that will be received after premium activation. Telegram promotes its premium very delicate, so that users may already “feel the taste” of its features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l7w4KcN6vEyNSjQaSLsnag.gif" /><figcaption>Premium features promotion in Telegram</figcaption></figure><h4><strong>Personality and Brand Identity</strong></h4><p>Micro animations help create a sense of <em>personality and brand identity.</em> Users constantly bumping into consistent animations may get used to them and start feeling the brand voice translated by product team through an App or Web interface. This strengthens the <em>brand awareness</em> and consequently makes users more loyal to the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m0S0So1-5fS3uEBLEo0Z5Q.gif" /><figcaption>Animated gradient in Apple Music as a playlist cover</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yL1fpYnpuIDzLIdaKeeFsQ.gif" /><figcaption>Animated stokes in Apple Music as a playlist cover</figcaption></figure><p>These colourful gradients and dynamic strokes are really associated with Apple Music and no other music streaming platforms. Animations have a <em>meditative effect</em> on users, look very nice and smooth.</p><blockquote><em>Secondly, micro animations may affect the </em><strong><em>emotions of users</em></strong><em> engaging them to use a product more often</em></blockquote><h4><strong>Delight and Surprise</strong></h4><p>Micro animations help create a sense of delight and surprise establishing a <em>positive emotional connection</em> with the product. For example, when 4th season of “Stranger Things” was released Spotify created “Stranger Things Official Playlist”, which was full of animations delivering <em>new emotional experience</em> to users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jH-5tCMZv5P8i99WY0ANFQ.gif" /><figcaption>“Stranger Things Official Playlist” in Spotify</figcaption></figure><h4><strong>Empathy and Connection to Product</strong></h4><p>Not only good UX copyright or friendly UI establish <em>human-oriented user experiences</em> in product. Micro animations may express <em>sympathy and understanding</em> to users. Accordingly, users feel human-like support from the product they’re using.</p><p>For example, if Shazam can’t recognise a song, there appears a very disappointing message: “We didn’t quite catch that, try again”. If there was an animation of a sad smile, the text wouldn’t be perceived like something formal and insincere. The animation of the smile would tell user “Hey, I’m also sad, you’re not alone here, I support you. Let’s try again”. It may have decreased the frustration (even if a little bit) from a negative user scenario.</p><figure><img alt="Shazam fails recognising a song" src="https://cdn-images-1.medium.com/max/1024/1*FhzrNUqRWAYE2Qh8DmaffA.jpeg" /><figcaption>Shazam fails recognising a song</figcaption></figure><h4><strong>Emotionally Engaging User Experiences</strong></h4><p>Dynamic animations and interactions evoke different positive emotions, such as excitement, joy, or wonder. It creates a stronger bond between the user and the product making it <em>memorable and appealing</em></p><p>For example, one of the main Premium features in Telegram is the access to an enormous library of emoji animations, reactions and statuses. The “ecosystem” of all motion design of Telegram is based on it and being successfully sold to Premium users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fohl1frver_CT7tqOxDy8Q.gif" /><figcaption>Library of animated emojis in Telegram</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nZcLg_NXeISaOGRB3GQRMw.gif" /><figcaption>Animated emoji reactions in Telegram</figcaption></figure><p>In Beatstar, which I play everyday (ahah), there are lots of animations that make gaming process simply <em>fun and emotional.</em> I literally feel how this box is opening and I really want to touch it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvclvWQfjiJBgbIzqhvLkQ.gif" /><figcaption>Song box opening animation in Beatstar</figcaption></figure><h3><strong>Metrics</strong></h3><blockquote><em>So, how exactly do micro animations affect the metrics?</em></blockquote><p>Animations in a product may have a significant impact on various metrics at the same time. Unfortunately, it could be <em>difficult</em> to count the specific results.</p><p>For example, there was an animation of like in Spotify. It was smooth and had a tactic feedback, so that user really could physically feel this <em>liking experience.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6TFHWFjUw-_P569YBMS1eA.gif" /><figcaption>Liking animation in Spotify</figcaption></figure><p>How exactly could product managers/designers count the effectiveness of animation implementation? If I say “just count the numbers of like clicks before and after the animation implementation and compare them”, I would be wrong.</p><p>Animation is just a part of this whole experience.</p><p>To estimate the result of animation implementation, we should also consider:</p><ol><li><em>In-App modal views or onboardings</em> making accent on current feature.</li><li><em>Marketing campaigns</em> advertising the product, feature, ecosystem of products.</li><li><em>Rebranding</em> in the company. Owing to it the overall number of product users may have increased. As a result, the total number of users of the “Like” feature</li><li><em>Deleting the competitors App</em> from the App-markets, probably, leads to increasing number of substitute products users (e.g., when the Spotify and Apple Music exited the Russian market, large amount of users started using Russian music streaming services).</li></ol><p>So, there is no clear answer to the question: “How exactly do micro animations affect the metrics in a product?”. It’s all about <em>overall user experience</em> with lots of factors and relations, which should be considered while counting the results of animation implementation.</p><blockquote><em>Here I would like to highlight the approximate list of the </em><strong><em>most common metrics,</em></strong><em> on which micro animations may influence. It’s not something new, so I wouldn’t dive deep into this topic</em></blockquote><h4><strong>tNPS</strong></h4><p>User loyalty may increase, because micro animations make overall user experience better.</p><h4><strong>Retention</strong></h4><p>Being more loyal or interested in product, user returns to it more willingly.</p><h4><strong>Time Spent in a Product</strong></h4><p>Also correlates with previous points. If the user is loyal to the product, then the average Time Spent in it may increase.</p><h4><strong>Jobs/Tasks Success or Conversion</strong></h4><p>Sometimes micro animations help user achieve the final steps of current User Flow. For example, Mac OS through (as for me, annoying enough) bouncing animation indicates, when the task isn’t completed. So, a user is literally forced to finish the started process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KgQ-mnd33KLJBjFWodhgqg.gif" /><figcaption>Bouncing animation in Mac OS</figcaption></figure><h4><strong>Activation</strong></h4><p>Thanks to micro animations, users better understand a product, premium features, product values during onboarding. It may lead to increased number of registrations.</p><h4><strong>Adoption</strong></h4><p>Micro animations reduce the number of days, during which users adopt to new functionalities across the product. So, the usage of new features also increases.</p><h3>Final note about micro animations</h3><p>Micro animations integrated into the product create both <strong>functional and emotionally engaging user experiences</strong> that bring the product closer to the Minimal Lovable Product (MLP).</p><p>Good micro animations require a certain level of motion design skills (Lottie, Json, After Effects), practice and patience, but the results from their implementation in the product will exceed all expectations.</p><p>#motiondesign #design #productdesign #animations #microanimations #userexperience</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8447ce73b916" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Микроанимации в дизайне продукта как путь к сердечку пользователя]]></title>
            <link>https://medium.com/@siropinas/%D0%BC%D0%B8%D0%BA%D1%80%D0%BE%D0%B0%D0%BD%D0%B8%D0%BC%D0%B0%D1%86%D0%B8%D0%B8-%D0%B2-%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD%D0%B5-%D0%BF%D1%80%D0%BE%D0%B4%D1%83%D0%BA%D1%82%D0%B0-%D0%BA%D0%B0%D0%BA-%D0%BF%D1%83%D1%82%D1%8C-%D0%BA-%D1%81%D0%B5%D1%80%D0%B4%D0%B5%D1%87%D0%BA%D1%83-%D0%BF%D0%BE%D0%BB%D1%8C%D0%B7%D0%BE%D0%B2%D0%B0%D1%82%D0%B5%D0%BB%D1%8F-4feb5272b678?source=rss-cffd025cbbf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4feb5272b678</guid>
            <dc:creator><![CDATA[Dmitry Moystsrapishvili]]></dc:creator>
            <pubDate>Thu, 18 May 2023 13:54:42 GMT</pubDate>
            <atom:updated>2023-05-18T14:35:42.023Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7NwNjcVewncnyaMfGi_W6w.png" /></figure><p>В современную цифровую эпоху дизайнеры продукта стремятся создать пользовательский интерфейс, который мог бы быть как <strong>функциональным, так и эмоционально привлекательным.</strong> Один из элементов дизайна, который стал мощным инструментом для достижения этой цели, — <em>микроанимации.</em></p><p>Микроанимации — это небольшие анимации, интегрированные в пользовательский интерфейс продукта. Они используются для <em>фидбэка, предоставления контекста и улучшения пользовательского опыта</em> в целом, приближая продукт к тому, что мы называем <strong>минимально привлекательным продуктом (MLP).</strong></p><p><em>В этой статье мы рассмотрим важность микроанимаций в дизайне продукта как способа достучаться до сердечка пользователя (приблизить продукт к MLP) и повысить метрики.</em></p><h4>Влияние анимаций на продукт</h4><p>Давайте поговорим о том, как микроанимации влияют на продукт в целом и на пользовательский опыт (User Experience) в частности.</p><blockquote><em>Во-первых, я хотел бы рассмотреть </em><strong><em>функциональный аспект</em></strong><em> анимаций в продукте. Это больше о практических преимуществах для пользователей, которые помогают им правильно и успешно выполнять свои работы (джобы)</em></blockquote><h4><strong>Фидбэк</strong></h4><p>Анимации показывают пользователям, что их действия завершены, профили зарегистрированы или верифицированы и т.д. Это позволяет пользователям лучше контролировать свои действия и снимает тревогу или гнев при выполнении задач.</p><p>Например, когда пользователь шазамит песню в громком баре, а приложение не может распознать песню, анимация и постоянно меняющийся текст показывают пользователю, что процесс шазаминга все ещё продолжается.</p><figure><img alt="Распознавание музыки в Shazam" src="https://cdn-images-1.medium.com/max/1024/1*gMbiJyP5g8wathY2qscXAA.gif" /><figcaption>Распознавание музыки в Shazam</figcaption></figure><h4><strong>Улучшенная навигация</strong></h4><p>Анимации также улучшают навигацию и помогают пользователю ориентироваться в продукте. Сегодня это кажется очевидным, но анимированные переходы с текущей страницы на следующую (например, когда пользователь нажимает на ячейку для просмотра содержимого) показывают, как именно пользователь может вернуться на предыдущую страницу. Всё просто: нужно свайпнуть назад — слева направо. Именно здесь анимация предлагает решение и улучшает пользовательский опыт.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5wE5lpB9pZgGX-b3jIIxEA.gif" /><figcaption>Анимированные переходы в Telegram внутрь чата/канала и обратно</figcaption></figure><p>Представьте, если бы в продукте не было анимаций перехода. Здесь, в Ozon Bank, следующая страница появляется поверх предыдущей. Это может (даже на долю секунды) запутать пользователя.</p><figure><img alt="Переходы внутрь ячейки и обратно в Ozon Bank" src="https://cdn-images-1.medium.com/max/1024/1*RZBTUGTBwcWetEKRWxBHOA.gif" /><figcaption>Переходы внутрь ячейки и обратно в Ozon Bank</figcaption></figure><h4><strong>Улучшенное понимание функциональностей</strong></h4><p>Микроанимации также помогают пользователям лучше понять функциональности продукта.</p><p><em>Анимированные онбординги</em> демонстрируют работу продукта и привлекают внимание к новым функциям, продвигаемым стейкхолдерами (например, для увеличения метрик).</p><p>VN использует анимированный онбординг. Он помогает пользователям лучше понять, как работает процесс редактирования видео.</p><figure><img alt="Анимированный онбординг в VN" src="https://cdn-images-1.medium.com/max/1024/1*Z7g66ZRMeEedrzXseiLswg.gif" /><figcaption>Анимированный онбординг в VN</figcaption></figure><p><em>Продвижение премиум-функций</em> выглядит более продающе с микроанимациями. Они информируют пользователей о ценностях, которые будут получены после активации Premium-аккаунта. Telegram продвигает свой Premium очень деликатно, чтобы пользователи могли «почувствовать вкус» его фич.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l7w4KcN6vEyNSjQaSLsnag.gif" /><figcaption>Промоушн премиум-фич в Telegram</figcaption></figure><h4><strong>Индивидуальность и фирменный стиль</strong></h4><p>Микроанимации создают ощущение <em>индивидуальности и фирменного стиля бренда.</em> Пользователи, постоянно сталкивающиеся с последовательной анимацией, могут привыкнуть к ней и начать чувствовать голос бренда, транслируемый командой продукта через приложение или веб-интерфейс. Это повышает<em> узнаваемость бренда</em> и, следовательно, делает пользователей более лояльными к продукту.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m0S0So1-5fS3uEBLEo0Z5Q.gif" /><figcaption>Анимированный градиент в Apple Music как обложка плейлиста</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yL1fpYnpuIDzLIdaKeeFsQ.gif" /><figcaption>Анимированные обводки в Apple Music как обложка плэйлиста</figcaption></figure><p>Эти красочные градиенты и динамичные обводки ассоциируются с Apple Music, а не с другими музыкальными стримингами. Анимации оказывают <em>медитативное воздействие</em> на пользователей, выглядят привлекательно и плавно.</p><blockquote><em>Во-вторых, микроанимации влияют на </em><strong><em>эмоции пользователей,</em></strong><em> побуждая их чаще пользоваться продуктом</em></blockquote><h4><strong>Восторг и удивление</strong></h4><p>Микроанимации создают ощущение восторга и удивления, создавая <em>положительную эмоциональную связь</em> с продуктом. Например, когда вышел 4-й сезон «Очень странных дел», Spotify создал официальный плейлист сериала, который был полон анимаций, доставляющих пользователям <em>новые эмоции от взаимодействия с интерфейсом.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jH-5tCMZv5P8i99WY0ANFQ.gif" /><figcaption>Официальный плейлист «Очень странных дел» в Spotify</figcaption></figure><h4><strong>Эмпатия и связь с продуктом</strong></h4><p>Не только хорошие UX-копирайтинг или дружественный UI создают <em>ориентированный на человека пользовательский опыт</em> в продукте (Human-Oriented User Experience). Микроанимации могут выражать <em>сочувствие и понимание</em> пользователям. Следовательно, они чувствуют человеческую поддержку от продукта, который они используют.</p><p>Например, если Shazam не может распознать песню, появляется очень разочаровывающее сообщение: «Мы не совсем уловили это, попробуйте еще раз» (“We didn’t quite catch that, try again”). Если бы на экране была анимация грустной улыбки, то текст не воспринимался бы как что-то формальное и неискреннее. Анимация говорила бы пользователю: «Эй, мне тоже грустно, ты здесь не один, я тебя поддерживаю. Давай ещё раз попробуем”. Это могло бы уменьшить разочарование (хотя бы немного) от негативного пользовательского сценария.</p><figure><img alt="Shazam не смог распознать музыку" src="https://cdn-images-1.medium.com/max/1024/1*FhzrNUqRWAYE2Qh8DmaffA.jpeg" /><figcaption>Shazam не смог распознать музыку</figcaption></figure><h4><strong>Эмоционально вовлекающий пользовательский опыт</strong></h4><p>Динамичные анимации и взаимодействия могут вызывать разные положительные эмоции: азарт, радость или удивление. Это укрепляет связь между пользователем и продуктом, делая взаимодействие <em>запоминающимся и привлекательным.</em></p><p>Например, одна из основных функций Premium в Telegram — доступ к огромной библиотеке анимаций эмодзи, реакций и статусов. На нём основана «экосистема» всего моушн-дизайна Telegram, которая успешно продается пользователям Premium.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fohl1frver_CT7tqOxDy8Q.gif" /><figcaption>Библиотека анимированных эмодзи в Telegram</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nZcLg_NXeISaOGRB3GQRMw.gif" /><figcaption>Анимированные эмодзи-реакции в Telegram</figcaption></figure><p>В Beatstar, в который я играю каждый день (ахах), есть множество анимаций, делающих игровой процесс <em>весёлым и эмоциональным.</em> Я буквально чувствую, как открывается эта коробка и мне очень хочется прикоснуться к ней.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvclvWQfjiJBgbIzqhvLkQ.gif" /><figcaption>Анимация открытия коробки с песней в Beatstar</figcaption></figure><h4>Метрики</h4><blockquote><em>Итак, как именно микроанимации влияют на метрики?</em></blockquote><p>Анимации в продукте могут одновременно влиять на разные метрики. К сожалению, подсчитать конкретные результаты может быть <em>затруднительно.</em></p><p>Например, раньше в Spotify была <em>анимация лайка.</em> Она была плавной и имела тактическую обратную связь, поэтому пользователь мог физически почувствовать этот опыт.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6TFHWFjUw-_P569YBMS1eA.gif" /><figcaption>Анимация лайка в Spotify</figcaption></figure><p>Как именно продакт-менеджеры/дизайнеры могут посчитать эффективность от внедрения этой анимации? Если я скажу «просто посчитайте количество лайков до и после реализации анимации и сравните их», то это будет ошибкой.</p><p>Анимация — лишь небольшая часть всего пользовательского опыта.</p><p>Чтобы оценить эффективность внедрения этой анимации, следует также учитывать:</p><ol><li><em>Модальные окна/шторки или онбординги</em> <em>в приложении</em> с акцентом на функции лайка.</li><li><em>Маркетинговые кампании,</em> рекламирующие продукт, функцию, экосистему продуктов.</li><li><em>Ребрендинг</em> в компании. Благодаря нему могло увеличиться общее количество пользователей продукта. Как следствие — общее число пользователей фичи «Лайк»</li><li><em>Удаление приложений конкурентов с рынков приложений, </em>вероятно, увеличило количество пользователей продуктов-субститутов (например, когда Spotify и Apple Music ушли с российского рынка, большое количество пользователей начало пользоваться российскими музыкальными стримингами).</li></ol><p>Итак, нет однозначного ответа на вопрос: «Как именно микроанимации влияют на метрики в продукте?». Всё дело в <em>общем пользовательском опыте</em> с множеством факторов и взаимосвязей, которые следует учитывать при подсчёте результатов реализации анимации.</p><blockquote><em>Здесь я хотел бы выделить примерный список наиболее распространенных метрик, на которые могут влиять микроанимации. Это не что-то новое, поэтому я не буду углубляться в эту тему</em></blockquote><h4><strong>tNPS</strong></h4><p>Лояльность пользователя может возрасти, потому что микроанимации улучшают общий пользовательский опыт.</p><h4><strong>Retention</strong></h4><p>Будучи более лояльным или заинтересованным в продукте, пользователь охотнее возвращается к нему.</p><h4><strong>Time Spent in a Product</strong></h4><p>Также коррелирует с предыдущими пунктами. Если пользователь лоялен к продукту, то среднее время, проведенное в нём, может увеличиться.</p><h4><strong>Jobs/Tasks Success or Conversion</strong></h4><p>Иногда микроанимации помогают пользователю выполнить последние шаги текущего пользовательского пути (User Flow). Например, Mac OS через (как по мне, достаточно раздражающую) прыгающую анимацию показывает, когда задача не выполнена до конца. Таким образом, пользователь буквально вынужден завершить начатый процесс.</p><figure><img alt="Прыгающая анимация в Mac OS" src="https://cdn-images-1.medium.com/max/1024/1*KgQ-mnd33KLJBjFWodhgqg.gif" /><figcaption>Прыгающая анимация в Mac OS</figcaption></figure><h4><strong>Activation</strong></h4><p>Благодаря микроанимациям пользователи могут лучше понять продукт, премиум функции, ценности продукта во время онбординга. Это может привести к увеличению количества регистраций.</p><h4><strong>Adoption</strong></h4><p>Микроанимации могут сократить количество дней, в течение которых пользователи осваивают новые функции продукта. Таким образом, использование новых функций также может увеличиться.</p><h3>Финальная заметка о микроанимациях</h3><p>Микроанимации, интегрированные в продукт, создают как <strong>функциональный, так и эмоционально вовлекающий пользовательский опыт,</strong> что приближает продукт к минимально привлекательному (MLP).</p><p>Хорошие микроанимации требуют определенного уровня навыков в моушн-дизайне (Lottie, Json, After Effects), практики и терпения, однако результаты от их внедрения в продукт превзойдут все ожидания.</p><p><a href="https://vc.ru/tag/motiondesign">#motiondesign</a> <a href="https://vc.ru/tag/design">#design</a> <a href="https://vc.ru/tag/productdesign">#productdesign</a> <a href="https://vc.ru/tag/animations">#animations</a> <a href="https://vc.ru/tag/microanimations">#microanimations</a><a href="https://vc.ru/tag/userexperience">#userexperience</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4feb5272b678" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>