<?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 Eddy Bogomolov on Medium]]></title>
        <description><![CDATA[Stories by Eddy Bogomolov on Medium]]></description>
        <link>https://medium.com/@edijsbogomolovs?source=rss-c1205aedad6a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HFTqrvcm5QT6rpWirSH3RQ.jpeg</url>
            <title>Stories by Eddy Bogomolov on Medium</title>
            <link>https://medium.com/@edijsbogomolovs?source=rss-c1205aedad6a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:42:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@edijsbogomolovs/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[How to actually understand AI: A simple guide]]></title>
            <link>https://edijsbogomolovs.medium.com/how-to-actually-understand-ai-a-simple-guide-ec43ad275e49?source=rss-c1205aedad6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec43ad275e49</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Eddy Bogomolov]]></dc:creator>
            <pubDate>Sun, 02 Nov 2025 18:05:03 GMT</pubDate>
            <atom:updated>2025-11-02T18:05:03.881Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7d-1tadrpmbesFK8Fa0lGg.png" /></figure><p>Imagine you wake up tomorrow and your coffee machine already knows you are tired. Before you say a word, it brews a stronger cup.</p><p>How did it know?</p><p>That moment captures the essence of artificial intelligence: <strong>machines that can mimic human intelligence.</strong></p><h3>Starting from the beginning: What is intelligence?</h3><p>At its core, intelligence is the ability to perceive, learn, and make decisions.</p><p>Humans do this naturally:<br>- We observe patterns (dark clouds mean rain).<br>- We learn from experience (bring an umbrella).<br>- We adapt (never forget it again).</p><p>Artificial intelligence is simply the science of teaching machines to do the same. It is a branch of computer science that aims to create systems capable of performing tasks that typically require human intelligence.</p><h3>Step 1: The foundation: Machine learning</h3><p>Early AI systems were rule-based.<br>They followed explicit instructions: if X happens, do Y.But the world is unpredictable, full of exceptions and patterns that cannot be easily programmed.<br>So scientists asked a new question: <strong>What if machines could learn rules from data instead of being told what to do?</strong></p><p>That question led to machine learning.</p><p>Machine learning involves training algorithms to identify patterns, make predictions or decisions based on data, without being explicitly programmed to perform the task.</p><h3>How it works</h3><ol><li>Feed data in: lots of examples (for instance, photos of cats and dogs).</li><li>Find patterns: the system learns what makes a “cat” or a “dog.”</li><li>Predict: it starts recognizing new images correctly.</li></ol><p>No hand-coded rules. Just learning from examples.<br>Machine learning is about finding patterns in data and generalizing from them.</p><h3>Step 2: Supervised learning - learning with a teacher</h3><p>Supervised learning is a type of machine learning where the algorithm learns by example.</p><p>You provide:</p><ul><li>Input data (A): for instance, an image of a dog</li><li>Correct output (B): the label “dog”</li></ul><p>The model sees thousands of labeled examples and learns to map A to B.<br>After training, it can recognize new dogs it has never seen before.</p><p>Supervised learning uses labeled data to teach models through feedback.<br>The model aims to make accurate predictions or decisions for new, unseen data based on this learned mapping.</p><p>It is commonly used in spam detection, medical diagnosis, and price prediction.</p><h3>Step 3: Unsupervised learning - learning without labels</h3><p>Now imagine you give the machine a box of photos with no labels.<br>It must find patterns on its own.</p><p>It might group images that look similar and discover clusters like:<br>- These are cats.<br>- These are dogs.<br>- These might be raccoons.</p><p>That is unsupervised learning.<br>Instead of being told the right answer, the algorithm uncovers hidden structures or relationships within data.</p><p>This approach is used when the correct outputs are not known or labeled.<br>The model infers its own rules, helping uncover insights that humans might not easily see.</p><p>Common uses include market segmentation, customer behavior analysis, and data compression.</p><h3>Step 4: Deep learning - machines that learn like the brain</h3><p>Machine learning was powerful, but it struggled with complex data like images, sound, or language.<br>So researchers looked to nature for inspiration and built <strong>neural networks</strong>: systems modeled after how the human brain works.</p><p>Think of a <strong>neural network</strong> like a team of detectives working together to solve a mystery:</p><ul><li>The first detective looks for simple clues: shapes, edges, or tones.</li><li>The next detective studies those clues to recognize patterns: like a face or a sound.</li><li>Later detectives combine these patterns to reach a conclusion: “That’s a cat” or “That’s the word ‘hello.’”</li></ul><p>Each “detective” layer builds on the work of the previous one, gradually turning raw data into understanding.<br>When many layers of these “detectives” work together, we get <strong>deep learning</strong>: a powerful form of machine learning that structures algorithms in layers to create an <strong>artificial neural network</strong> capable of learning and making intelligent decisions on its own.</p><p>This layered approach allows machines to process vast and complex data through multiple levels of abstraction, much like how our brains interpret the world: from simple shapes to complete concepts.</p><p>Deep learning excels at <strong>pattern recognition</strong> and powers technologies such as <strong>image and speech recognition</strong>, <strong>natural language processing</strong>, and many others that require deep understanding of data.<br>It pushes the boundaries of what machines can learn and often surpasses human performance in specialized tasks.</p><h3>Step 5: Large language models (LLMs)</h3><p>At the frontier of deep learning are large language models.<br>These models are designed to process, understand, and generate human language.</p><p>They are trained on massive datasets of text, learning grammar, reasoning, facts, and even tone by identifying patterns across vast amounts of information.</p><p>Models such as GPT (generative pre-trained transformer) and BERT (bidirectional encoder representations from transformers) use specialized architectures to handle a wide range of language tasks: from translation and summarization to question answering and content creation.</p><p>By leveraging scale and complex neural structures, LLMs can produce outputs that are contextually relevant and syntactically coherent.<br>They are the reason why systems like ChatGPT can communicate in a human-like way.</p><h3>Step 6: The bigger picture - the AI landscape</h3><p>AI is not a single technology. It is a layered ecosystem.<br>At the broadest level:</p><ul><li>Artificial intelligence is the umbrella term for systems that perform human-like tasks.</li><li>Machine learning is a subset focused on learning from data.</li><li>Deep learning is a more advanced subset that learns through neural networks.</li><li>LLMs are specialized deep learning systems focused on human language.</li></ul><p>Other fields like computer vision, robotics, and reinforcement learning also live within this ecosystem, each addressing a specific form of intelligence.</p><h3>Step 7: Why it matters</h3><p>AI is not just about building smarter machines.<br>It is about amplifying human potential.</p><p>Doctors diagnose faster.<br>Cars drive safer.<br>Businesses make smarter decisions.<br>Creators write and design more efficiently.</p><p>The goal of AI is not to replace human intelligence but to extend it: to let machines handle repetitive or data-intensive work so that humans can focus on creativity, empathy, and strategy.</p><h3>When broken down from first principles, AI becomes easier to understand:</h3><ol><li><strong>Artificial intelligence</strong>: answers the question <em>“Can machines act intelligently?” </em>Example: virtual assistants, chatbots</li><li><strong>Machine learning</strong>: answers the question <em>“Can machines learn from data?</em>Example: email filters, recommendation systems</li><li><strong>Deep learning</strong>: answers the question <em>“Can machines recognize complex patterns?” </em>Example: face recognition, speech-to-text systems</li><li><strong>Large language models (LLMs)</strong>: answer the question <em>“Can machines understand and generate language?” </em>Example: ChatGPT, Google Bard</li></ol><p>AI is not magic. It is math, data, and feedback loops repeated millions of times.<br>The real magic is that through these loops, machines begin to learn in ways similar to us: not by memorizing, but by recognizing patterns and adapting over time.</p><p>When your phone predicts your next word or your car corrects your lane, remember: it is not guessing. It is learning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec43ad275e49" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI is quietly rewriting how we think, work, and build.]]></title>
            <link>https://edijsbogomolovs.medium.com/ai-is-quietly-rewriting-how-we-think-work-and-build-217c2a891714?source=rss-c1205aedad6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/217c2a891714</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Eddy Bogomolov]]></dc:creator>
            <pubDate>Thu, 30 Oct 2025 12:26:24 GMT</pubDate>
            <atom:updated>2025-10-30T12:26:24.984Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_LZq5l0pD6NkImczgA2d5w.png" /></figure><p>Three years ago, I was writing user stories. Now I’m editing them.<br>I was coding. Now I’m designing architecture.<br>I was analyzing data. Now I’m interpreting what it means.</p><p>The work hasn’t disappeared. It just moved up a level.<br>From doing to directing. From creating to curating.</p><p>This shift isn’t just personal: it’s systemic.<br>AI is speeding up everything around us.</p><p>ChatGPT reached 100 million users in 2 months.<br>Telegram needed 61.<br>That’s not a small difference. That’s a new kind of time.</p><p>Products that once grew over years now explode in weeks.<br>Cursor hit 100 million ARR faster than Slack did in a decade.<br>Lovable made 100 million ARR in two months: with fifteen people.<br>AI is compressing time, shrinking teams, and amplifying output.</p><p>And with that, user expectations are shifting too.<br>We no longer want tools. We want outcomes.</p><p>Creation is becoming generation.<br>Instead of building every slide or layout, we describe what we want.<br>Tools like Gamma or Tome transform prompts into full presentations.</p><p>Manual work is becoming automated.<br>Repetitive workflows fade into the background.<br>Cursor and Replit AI handle debugging, refactoring, and testing in seconds.</p><p>Generic experiences are becoming personalized.<br>Templates are out.<br>Lovable and Framer AI create unique designs shaped by context, not presets.</p><p>Complex systems are becoming simple.<br>What once required experts: like SAP configurations or CRM setups,<br>is now guided by conversational copilots that handle the heavy lifting.</p><p>And visualization is becoming insight.<br>I used to wrestle with Tableau dashboards.<br>Now ThoughtSpot and Perplexity turn raw data into clear, instant answers.</p><p>AI doesn’t just change interfaces: it changes expectations.<br>We no longer want to build step by step.<br>We just want to start with a question and end with an answer.</p><p>Traditional software gave us tools to accomplish tasks.<br>AI delivers the result we actually wanted.</p><p>We used to design in Photoshop, present in Google Slides, write in Word.<br>Now we generate with Midjourney, Gamma.ai, and EvenUp.<br>Users no longer want to drive. They want to arrive.</p><p>Before AI, value lived in the journey.<br>We started, learned, created.<br>Software gave us capabilities.</p><p>Now value lives in the destination.<br>We ask. We receive.<br>Software gives us outcomes.<br>The path becomes irrelevant when teleportation exists.</p><p>AI isn’t replacing people. It’s removing friction.<br>It’s turning thought into output.</p><p>The real advantage isn’t speed. It’s clarity.</p><p>Those who learn to guide: not grind, will move faster than ever before.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=217c2a891714" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The hidden cost of the “Wow” behind AI prototyping]]></title>
            <link>https://edijsbogomolovs.medium.com/the-hidden-cost-of-the-wow-behind-ai-prototyping-31bd16e2dff0?source=rss-c1205aedad6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/31bd16e2dff0</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Eddy Bogomolov]]></dc:creator>
            <pubDate>Thu, 23 Oct 2025 15:21:03 GMT</pubDate>
            <atom:updated>2025-10-23T15:21:03.376Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pLMt5KOUjnSahhzqShpTOA.png" /></figure><p>AI’s magic comes with a catch. Here’s my story of chasing that “wow” moment and learning where designers really shine.</p><p><strong>What you’ll learn</strong></p><ul><li>AI prototypes look amazing at first but create big expectations for speed.</li><li>As projects get more complex, AI needs more fixes and slows down.</li><li>Designers still do the important work of making designs feel right.</li></ul><p><strong>The first prototype feels like magic</strong><br>It was awesome. The product manager gave me a document for a mobile app login screen. I put it into an AI tool like Uizard, and in minutes, a prototype popped up, buttons, layout, 70% done. The team was shocked. “Wow,” someone said. The client loved it too. AI felt like a superhero power.</p><p><strong>When AI stops working well</strong><br>The magic didn’t last. New needs, like extra features, messed up the AI. The same instructions that worked before gave me bad results. I tried changing my words, adding details, but it still needed tons of fixes. AI wasn’t saving time anymore, it was taking it. So, I opened Figma. It was faster to design myself than keep fixing AI’s mistakes.</p><p><strong>The expectation problem</strong><br>That first “wow” fools everyone. People think AI can stay that fast, but it can’t. When projects get more feedback, like user changes or extra features, you need more prompts to tell AI what to do. More layers, more prompts, more fixes. AI built a dashboard in an hour. But when we got user feedback and added new features, I had to write tons of new prompts. Fixing AI’s output took longer than designing it myself.</p><p><strong>Where AI helps and where it doesn’t</strong><br>AI is great for starting fast. It turns ideas into rough prototypes in minutes. But when things change, AI struggles. You end up spending more time explaining what you want than just doing it. The last 30% making it perfect, user-friendly, and human needs a designer’s touch.</p><p><strong>Tips for using AI smartly</strong></p><ul><li><strong>Be honest upfront</strong>: Tell everyone AI is for quick starts, not final designs.</li><li><strong>Mix tools</strong>: Use AI for early ideas, then switch to Figma for details.</li><li><strong>Save good instructions</strong>: Keep track of what works to make AI faster next time.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31bd16e2dff0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to judge a design without a single user test]]></title>
            <link>https://edijsbogomolovs.medium.com/how-to-judge-a-design-without-a-single-user-test-060569404423?source=rss-c1205aedad6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/060569404423</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Eddy Bogomolov]]></dc:creator>
            <pubDate>Mon, 13 Oct 2025 10:22:53 GMT</pubDate>
            <atom:updated>2025-10-13T10:22:53.420Z</atom:updated>
            <content:encoded><![CDATA[<p>Every designer’s seen it: <br>Another post asking, ”Which design is better : A or B?” or saying if we will add Hick&#39;&#39;s Law this product will be better.</p><p>Or worse someone’s redesigned Airbnb from scratch, without a single user, without any data, and without the slightest understanding of the business.</p><p>And it made me pause.</p><p>How do I actually know if what I’m designing is better, or even good enough, when I don’t have user research, metrics, or business input?</p><p>Because if I’m not clear on what “better” even means, I’m not really designing, I’m just choosing what looks nicer. <br>And that’s not design. That’s decoration. At least I am thinking like that but I know that a lot of people will not agree with me.</p><p>Let’s be honest: without data, saying something is “better” doesn’t really hold up.</p><p>But if “better” is off the table, what’s the alternative?</p><p>Let’s explore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ndNqtiOh4kg2Fn7ToYqgAQ.jpeg" /></figure><h3>Rules, frameworks, and a different way to think</h3><p>Step back for a moment: <br>What do we actually know about assessing design?</p><p>At its core, good design should:<br>- Support business goals <br>- Help users compile core product goals <br>- Reduce friction along the way</p><p>There are frameworks for this. <br>Lots of them: <br>Nielsen’s 10 Usability Heuristics, Gerhardt-Powals’ Cognitive Engineering Principles, the UX Honeycomb… the list goes on.</p><p>I tried using many of them myself. <br>But while teaching beginner product designers at <a href="https://uxtribe.eu/">uxtribe.eu</a>, I realized something important:</p><p>Most of these models are too abstract.<br>They don’t land. They don’t stick. <br>And without real users or business input, they often don’t make sense.</p><p>So then what?</p><p>What can you use when you’re on your own — just a designer, a screen, and a question?</p><h3>Four questions that changed how I review design</h3><p>I didn’t plan these questions. <br>They just kept showing up in critiques, workshops, and product reviews. <br>Eventually, they became the way I look at every interface.</p><p>They’re simple. <br>They’re fast. <br>And they work, especially when there’s no research to lean on.</p><p>Here they are:</p><p>- Clarity: Is it obvious what this product does and who it’s for?<br>- Mental effort: does the experience feel effortless to understand and follow?<br>- Ease of use: can users reach their goal with minimal effort or confusion?<br>- Visual design: Does the visual design guide users toward the primary action?</p><h3>1. Clarity</h3><p>Is it obvious what this product does and who it’s for?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a4U1U5Sq_v9oufyncf0mbw.jpeg" /><figcaption>Jobber’s hero is confident but unclear. The headline focuses on emotion, not context, leaving users to guess what the product actually does. Visuals hint at landscapers and contractors, but the copy doesn’t confirm it until the fine print. In a 5-second window, that’s too late.</figcaption></figure><p>The headline focuses on emotion, not context — leaving users to guess what the product actually does.<br>Visuals hint at landscapers and contractors, but the copy doesn’t confirm it until the fine print.</p><p>In a 5-second window, that’s too late.</p><p>When you land on Airbnb, you don’t need to guess: <br>You’re here to book a place to stay. There’s a giant search bar, listings with prices, and photos of actual homes.</p><p>Now compare that to a site with a clever headline like “Redefining the way people belong.” <br>Sounds cool, but what does it *mean*?</p><p>Why this matters:<br>If users don’t understand what your product is or who it’s for, they won’t stick around long enough to find out.</p><h3>2. Mental effort</h3><p>Does the experience feel effortless to understand and follow?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i5N3nL0Nz4sW0FajUtM3Uw.jpeg" /><figcaption>The Zoom dashboard is clear but mentally demanding. With multiple focal points — profile, meetings, summaries, schedules, the user must constantly decide where to look first. It’s well-structured for experts, but for new users, the lack of hierarchy adds unnecessary mental effort before action.</figcaption></figure><p>On Airbnb, search results appear instantly. Filters are visible. Dates, guests, price , all right there.</p><p>Now imagine if the calendar only appeared “after” choosing a listing. Or if filters were buried under “advanced tools.”</p><p>Nothing’s broken. But now you’re making users think harder than they should.</p><p>Why this matters:<br>Mental load adds up quickly. The more users have to figure things out, the less likely they are to continue.</p><h3><strong>3. Ease of use</strong></h3><p>Can users reach their goal with minimal effort or confusion?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VrcaooboFFX3i9k_swbS7g.jpeg" /><figcaption>The flow to add an activity during a call feels heavier than it should. What starts as a simple social action turns into a multi-step process with context shifts and permission screens. Instead of staying in the moment with the call, users have to pause, read, and confirm, reducing the overall ease of use for something meant to feel instant and collaborative.</figcaption></figure><p>Airbnb’s core flow is straightforward: <br>Search → Choose → Book.</p><p>Now picture a version where “Book Now” is hidden, the calendar resets every time you change filters, and error messages are vague.</p><p>That version still works — but it’s frustrating.</p><p>Why this matters:<br>If users can’t move forward easily, they lose confidence. Friction, even small, creates drop-off.</p><h3>4. Visual design</h3><p>Does the visual design guide users toward the primary action?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U6t2sFNWfBzzZwdISWdJvw.jpeg" /><figcaption>The visual design creates a strong brand impression but offers little directional guidance. The large imagery and typography draw attention, while the “Order” button feels secondary. It works as a visual intro if content continues below the fold, but not as an action-driven entry point.</figcaption></figure><p>On Airbnb, important actions stand out. <br>There’s contrast, spacing, hierarchy. The “Continue” or “Book” button always draws the eye.</p><p>Now imagine everything on the screen has the same color, size, and weight.</p><p>Suddenly, nothing stands out — and users hesitate.</p><p>Why this matters: <br>Visual design isn’t about making things look pretty. It’s about creating direction. <br>Good visuals reduce thinking and increase flow.</p><h3>A real example: TailwindApp.eu</h3><p>Let’s apply these four questions to a real-world product: Tailwind app, a Baltic-made cashflow forecasting tool I recently reviewed.</p><p><strong>Clarity:</strong><br>The landing page has a strong visual (a graph), but the actual value proposition is buried in small text. <br>It takes effort to understand what the tool does and who it’s for.</p><p><strong>Mental effort:</strong><br>The dashboard looks clean — but when users interact with the graph, they’re overwhelmed. <br>Dots, labels, overlapping data — all the information is there, but it’s hard to interpret.</p><p><strong>Ease of use:</strong><br>Connecting a bank account, a core action, takes over 10 steps and multiple confirmations. <br>Even inside the product, it’s unclear what you can click or do next.</p><p><strong>Visual design:</strong><br>Tailwind has a beautiful split-screen layout (past vs. future). <br>But uniform colors and lack of visual hierarchy make it hard to know where to focus.</p><p><strong>The takeaway? </strong><br>Even without data, these four questions made it easy to spot both strengths and pain points in the experience — fast.</p><p><a href="https://www.figma.com/deck/PNCxonINENBKAsRJhJTXl8/Product-review--Tailwind?node-id=1-25&amp;viewport=-87%2C22%2C0.51&amp;t=nFPRYNHJ8ovHi5ID-1&amp;scaling=min-zoom&amp;content-scaling=fixed&amp;page-id=0%3A1">Here is a presentation that guides you through the example.</a></p><h3>Is this a replacement for data or research?</h3><p>No absolutely not.</p><p>You can’t replace real user insights with gut feeling. <br>And you shouldn’t try to.</p><p>But these four questions aren’t about claiming something is better.<br>They’re about helping you see more clearly especially when you don’t have access to data, users, or stakeholders.</p><p>They give you a way to confidently say: <br>“This works.” <br>Or: <br>“This has friction.” <br>Without needing a spreadsheet to prove it.</p><p>They don’t give you certainty. <br>But they give you focus. <br>And sometimes, that’s exactly what you need.</p><h3><strong>In closing: a simpler way to see</strong></h3><p>If you’re ever staring at a design, unsure what’s working or arguing with your team about “A vs. B” pause and ask:</p><p>- Is it clear what this product does and who it’s for? <br>- Does it feel effortless to understand and follow? <br>- Can users reach their goal without unnecessary steps? <br>- Is the visual design guiding them in the right direction?</p><p>You don’t need a new framework. <br>You need a better lens.</p><p>This is mine.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=060569404423" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first try with Figma Make]]></title>
            <link>https://edijsbogomolovs.medium.com/my-first-try-with-figma-make-25167f6c03ee?source=rss-c1205aedad6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/25167f6c03ee</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Eddy Bogomolov]]></dc:creator>
            <pubDate>Sat, 04 Oct 2025 13:06:00 GMT</pubDate>
            <atom:updated>2025-10-13T07:43:35.848Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8dL9HUc45ffi6C2HhigIHw.jpeg" /></figure><p>In this article, you’ll see how I used Figma Make to build 4 very different projects from a weekend prototype to my own startup idea.<br>But it didn’t start that way. Before any of those projects existed, I tried Figma Make once and almost never came back.</p><p>The day Figma announced Figma Make, I felt like a kid who’d just been handed the keys to a candy store.<br>A tool promising effortless interactions, no code required?<br>I clicked in the second it went live.</p><p>But instead of magic… I got silence.<br>Let’s just say the experience wasn’t quite there yet.<br>Some things worked, most didn’t. The interface felt clunky. The feedback loop was slow. What started as excitement quickly spiraled into frustration.</p><p>I closed the tab.<br>And with it, I closed the idea that Figma Make could be part of my workflow.</p><p>At least, that’s what I thought<br>until months later, when a few projects forced me to reopen that door.</p><h3><strong>A reason to return</strong></h3><p>There’s a never-ending buzz around AI, and Figma Make kept popping up in that noise.<br>Meanwhile, I was buried in a few projects.</p><p>Just getting designs to a “usable” state felt like a grind.<br>And honestly, I was exhausted.</p><p>Every review felt like dragging people through mud.<br>Static screens. Arrows everywhere.<br>Stakeholders squinting, trying to imagine how it would work.<br>Developers nodding politely, then building something completely different.</p><p>I was tired of it.<br>Tired of performing interactions on static screens while everyone tried to keep up.<br>Tired of writing specs no one read.<br>Tired of developers missing edge states, even when I’d marked everything in red.<br>Tired of skipping details myself just to hit deadlines.</p><p>It wasn’t just slowing me down,<br>it was breaking engagement.<br>Stakeholders stopped asking questions.<br>Developers stopped looking closely.<br>And I stopped believing the design would survive the handoff intact.</p><p>Every project hit the same wall.<br>Stakeholders couldn’t feel the product, static screens left too much to imagination.<br>A modal looked fine on a slide, but no one knew if it blocked the flow or dismissed on click-away.<br>Reviews ended with nods, but alignment quickly unraveled.</p><p>Developers faced the same gap. Even with detailed notes, things slipped: dropdown behaviors, partial validation, hover vs. selection states.<br>These weren’t edge cases , they were daily friction that slowed everything down.</p><p>Deadlines got tighter, priorities kept shifting, and coded prototypes weren’t an option.<br>Writing longer specs only buried the problem deeper.</p><p>What I needed was a way to say:<br><strong>“Here, click it. This is how it should work.”</strong></p><p>That’s why I turned to Figma Make.<br>Not for shiny demos, but as a bridge:<br>Interactive enough for stakeholders to experience.<br>Precise enough for developers to trust.<br>Lightweight enough to actually fit my schedule.</p><h3>Getting hands on with Figma Make</h3><p>I didn’t want to write another “first impressions” post after a weekend of tinkering.<br>If I was going to talk about Figma Make, I wanted it to be honest.<br>Not one day of use but months.<br>So I decided to put it through fire: four real projects.</p><h4>Project 1 - The Weekend App</h4><p>The first was a small consultation project I took on for a local startup over a weekend.<br>They needed help turning a rough idea into something tangible.<br>The request sounded simple:<br>“Can you create a mobile app that lets merchants use it as a cashier , no products, just a simple flow to add a sum and take payment?”</p><p>Normally, this kind of engagement would mean static screens, arrows, and endless explaining. Instead, I opened Figma Make.</p><p>Within hours, I delivered a working prototype:<br>A barebones mobile UI where you tap “Add amount,” enter a number, and hit “Pay.” It looked real enough to test.</p><p>The moment the founder tapped through it on their phone, something shifted. They stopped asking <em>what it would do</em> and started reacting to <em>how it felt to use</em>. It wasn’t code but it felt like a real product.</p><p><strong>The wins were huge:</strong></p><ul><li>The founder instantly connected with the idea seeing it as something real, not just another set of screens.</li><li>Instead of designing the profile screen from scratch, Figma Make gave me a solid foundation to build on.</li><li>The prototype made meetings more focused and decisions faster.</li><li>Clicking through flows exposed scenarios that would’ve gone unnoticed in static screens.</li></ul><h4>Project 2 - Checkout audit tool</h4><p>For my second project, I decided to test Figma Make on my own idea, <br>a checkout audit tool where users could paste a URL and instantly get suggestions to improve conversion.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-Qn3EeCUybU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-Qn3EeCUybU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-Qn3EeCUybU%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c46c822a5cd22b6f05b658bbbae7cd23/href">https://medium.com/media/c46c822a5cd22b6f05b658bbbae7cd23/href</a></iframe><p>Normally, this kind of idea would never make it past my notes.<br>I’d start thinking about where I’d find a developer, what tech I’d need to learn, how long it would take and the momentum would die before I even opened Figma.</p><p>This time, I opened Figma Make.</p><p>Within minutes, I had a working layout.<br>I wrote a few prompts, defined the rules for reviewing checkout pages, and Figma Make did the rest, a simple screen with a URL input field, a results panel showing audit findings, and a recommendations list with next steps.<br>It wasn’t pixel-perfect , but it was real enough to click through, validate the idea, and run first tests on the same day.</p><p><strong>Wins</strong></p><ul><li>Built a functional layout in minutes without polished designs or heavy prep.</li><li>Could validate the core idea fast and gather feedback while the excitement was fresh.</li><li>Speed turning a vague idea into a tangible product the same day.</li><li>Skipped the usual blocker of “where will I find a developer” and just started building.</li></ul><p><strong>Losses</strong></p><ul><li>The technical side hit a wall: API calls never went through despite reconfiguring and swapping providers.</li><li>The interface worked, but the data pipeline didn’t, leaving the prototype half alive.</li></ul><h4>Project 3: Clunky B2B Tool</h4><p>This project started with a familiar story: a powerful internal tool built entirely by developers. It did everything it was supposed to, but using it felt like wrestling with an overgrown spreadsheet. Buttons everywhere, no clear hierarchy, and users getting lost in the process. Instead of saving time, it created more work. Feedback was consistently negative.</p><p>I decided to rebuild the experience in Figma Make. Not with static mockups, but with a functional prototype that looked and felt real. Rows could be clicked, details slid in from the side, inline edits worked, and validation appeared instantly. Within minutes, people understood how the tool should actually behave.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FERDJblqxXj8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DERDJblqxXj8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FERDJblqxXj8%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b5f1b2d81ec05fc775ccda7a95cf27ec/href">https://medium.com/media/b5f1b2d81ec05fc775ccda7a95cf27ec/href</a></iframe><p><strong>Wins</strong></p><ul><li>B2B tools don’t need to be flashy. They need to be fast, clear, and predictable. Figma Make turned out to be perfect for that. By using simple styling like Tailwind, I focused entirely on how the interface worked, not how it looked.</li><li>At one point, I was stuck figuring out how to show the “current price” in a table. I tried prompting Figma Make, and it suggested adding a star icon next to the active price with a tooltip explaining it. That small, AI-generated idea solved a real usability problem in seconds.</li><li>When customers saw the interactive table, something clicked. They instantly understood what was editable, how to search, and how to work with data. The prototype didn’t just explain, it demonstrated.</li></ul><p><strong>Losses</strong></p><ul><li>Then reality hit. Figma Make isn’t built for complex flows. When I tried to add multiple features or pages, the prototype began to break. Fixing one thing often caused another to fail.</li><li>Heavy prototypes also made minor visual tweaks painful, and z-index issues kept messing up layered elements, especially when columns were frozen.</li></ul><h4>Project 4: A governance B2B Tool</h4><p>A complex and outdated governance platform that needed a full structural rethink. The project had already been running for a while, and most designs were in place. However, I noticed the client was struggling to understand the end-to-end experience because there were so many conditional flows that made everything overly complex.</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNxbfFnNA_a0&amp;type=text%2Fhtml&amp;schema=google&amp;display_name=YouTube&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNxbfFnNA_a0" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0a916b2f9a6255ca00ed9d229ccb925e/href">https://medium.com/media/0a916b2f9a6255ca00ed9d229ccb925e/href</a></iframe><p><strong>Wins</strong></p><ul><li>Learning from the previous project, instead of building one big prototype, I divided the product into smaller, digestible Figma Make flows. This approach allowed me to show different states, for example, what happens when an order is submitted, declined, or approved.<br>It helped the business clearly see what was missing and what worked well.</li><li>Instead of manually designing mobile screens, I asked Figma Make to generate them for me, and it worked surprisingly well.</li></ul><p><strong>Loses</strong></p><ul><li>This project used up all of my Figma Make credits, which stopped me from working and taught me a tough lesson: AI prompts aren’t infinite.</li><li>I imported existing designs from Figma, but the results were messy. Auto layout and spacing needed more attention, yet time was limited.<br>It worked, but not as smoothly as planned.</li></ul><h3>What I Learned</h3><p>Working across four very different projects made one thing clear: Figma Make changed how I design.</p><p>Instead of handing off static screens and hoping people imagined the right interactions, I started delivering real experiences that anyone could click, feel, and understand instantly. Reviews turned from explanations into conversations.</p><p>It wasn’t perfect. Things broke. Prompts sometimes misfired. Changes didn’t always stick. I hit credit limits and got locked out mid-flow. Some prompts took minutes to process. APIs failed. But even with all that, the trade-off was worth it.</p><p><strong>What worked</strong></p><ul><li>I worked up to eight times faster than before</li><li>Developers could experience interactions instead of reading specs</li><li>Missing states surfaced early before handoff</li><li>Startup ideas moved from concept to test in hours, not days</li><li>Stakeholder reviews became shorter and more focused</li><li>Collaboration improved because everyone worked from the same prototype</li><li>Edge cases appeared naturally through interaction, not documentation</li></ul><p><strong>What didn’t</strong></p><ul><li>Occasional breakages that forced file duplication</li><li>Limited daily credits and slow execution on complex prompts</li><li>Figma Make sometimes overwriting elements unintentionally</li><li>Unapplied changes that required rework</li><li>API integrations that rarely behaved as expected</li></ul><p>Despite the friction, <strong>F</strong>igma Make changed the rhythm of my work.<br>I no longer needed to explain everything in words; I could show it.</p><p>I believe tools like this will soon be part of every product team’s workflow. Not just for designers, but for anyone shaping a product: PMs, founders, marketers, and engineers. Titles will matter less than the ability to think and test through interaction.</p><p>At one point I even skipped designing a profile page entirely. I just wrote a prompt.<br>It looked great. The time I saved was unbelievable.</p><p>For dense, logic-heavy interfaces, that speed and clarity were worth every glitch along the way.</p><h3>Discover more stories that inspire growth</h3><p><a href="https://uxdesign.cc/figma-make-the-biggest-shift-in-ux-ui-since-sketch-5483e18f76d7">Figma Make: the biggest shift in UX/UI since Sketch</a></p><p><a href="https://medium.com/design-systems-collective/how-figma-make-cut-our-design-validation-time-by-67-65fc8c033e64">https://medium.com/design-systems-collective/how-figma-make-cut-our-design-validation-time-by-67-65fc8c033e64</a></p><p><a href="https://medium.com/user-experience-design-1/how-to-prompt-figma-makes-ai-better-for-product-design-627daf3f4036">https://medium.com/user-experience-design-1/how-to-prompt-figma-makes-ai-better-for-product-design-627daf3f4036</a></p><p><a href="https://medium.com/user-experience-design-1/is-figma-make-ready-for-dev-handoff-9fe2594630e3">https://medium.com/user-experience-design-1/is-figma-make-ready-for-dev-handoff-9fe2594630e3</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25167f6c03ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 1: Product designer’s journey building an app with ChatGPT-5]]></title>
            <link>https://edijsbogomolovs.medium.com/part-1-product-designers-journey-building-an-app-with-chatgpt-5-fa3edd27fd10?source=rss-c1205aedad6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa3edd27fd10</guid>
            <category><![CDATA[chatgpt5]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Eddy Bogomolov]]></dc:creator>
            <pubDate>Sat, 09 Aug 2025 09:36:16 GMT</pubDate>
            <atom:updated>2025-08-09T09:36:16.505Z</atom:updated>
            <content:encoded><![CDATA[<p>For three days, my Figma Make file sat in front of me.<br>Tangled lines. Messy frames. Half-built screens.</p><p>One moment my prototype worked.<br>The next, it didn’t.</p><p>I was tired.<br>Tired of rewriting prompts.<br>Tired of chasing bugs I couldn’t name.</p><p>The idea I was working on was simple but ambitious:<br>A <strong>Checkout Auditor</strong> tool.<br>A place where users could paste their checkout page URL and instantly get tips on how to improve conversion.</p><p>Then, one morning, coffee in hand, I saw it on YouTube: <em>ChatGPT-5 is here</em>.</p><p>The spark from the past few days was still buzzing in my head.<br>Maybe this was the missing piece.</p><p>But I hesitated.<br>The last time I touched a terminal, the iPhone 6 was new.<br>I’m a product designer.<br>Code isn’t my playground.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SgvTRQBKAYy0LP-Fgoccmw.png" /><figcaption>Deleting everything in Pico and pasting fresh code like a digital exorcism.</figcaption></figure><h3>Day one: stepping into the unknown</h3><p>The first problem hit me instantly.<br>I couldn’t <em>see</em> the app.</p><p>In Figma Make, I could drag, drop, and watch it take shape.<br>Here, I had nothing but faith — and a feed full of LinkedIn posts praising ChatGPT-5.</p><p>Then came the terminal.<br>I felt like a tourist in a city with no map.</p><p>The Pico editor blinked back at me, waiting.<br>My fingers made 300 mistakes at once.<br>Every error sent me running to ChatGPT, asking it how to fix my mess.</p><p>Just as I thought I was getting somewhere, ChatGPT froze.<br>An error message appeared.</p><p>I sighed, then asked it to start over.<br>This time, I told it: give me every step, all the code, from the very beginning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VCmsHBMI8Tpt3YSTxYyXig.png" /><figcaption>ChatGPT ghosted me mid-convo classic.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGflPymlHpRNvmLqlpnEsg.png" /><figcaption>Day one: folders, commands, and praying Node.js is awake</figcaption></figure><h3>Slowing down to speed up</h3><p>It failed again.<br>Not a tiny bug — a dead stop.</p><p>So I switched to the “super dummy” approach.<br>No skipping ahead.<br>No guessing.</p><p>I made ChatGPT check me after <em>every</em> step.<br>Type a command.<br>Wait.<br>Confirm.<br>Move on.</p><p>It was painfully slow.<br>But for the first time, I wasn’t drowning in unknown errors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_uedxnaWfI3GFlrrEaG4dQ.png" /><figcaption>Making a shiny new folder so my chaos has somewhere to live.</figcaption></figure><h3>The tiny victory</h3><p>I was ready to quit.<br>Tomorrow, I told myself. I’ll start again tomorrow.</p><p>Then… wait.<br>It works.</p><p>The terminal spat out lines that made sense.<br>The app loaded without complaint.</p><p>I stared at the screen, not trusting it.<br>Then I smiled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YX95B-N1kbM_HgavGbfjCA.png" /><figcaption>Hit run… and boom, my Checkout Auditor is alive at localhost:3000.</figcaption></figure><h3>The wall at the end of the day</h3><p>It worked — but my URL logic didn’t.<br>The checkout screen showed up empty.<br>Cloudflare stopped taking screenshots.</p><p>That was it for day one.<br>Four hours gone.<br>My head felt like a browser with too many tabs open — everything running, nothing responding.</p><p>Tomorrow, I’ll see if ChatGPT-5 can get me past this wall.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa3edd27fd10" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A brief history of me screwing up]]></title>
            <link>https://edijsbogomolovs.medium.com/a-brief-history-of-me-screwing-up-9c1dea542bac?source=rss-c1205aedad6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c1dea542bac</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[mistakes]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Eddy Bogomolov]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 09:11:30 GMT</pubDate>
            <atom:updated>2025-08-04T09:23:51.025Z</atom:updated>
            <content:encoded><![CDATA[<p>My path into product design wasn’t planned.<br>I didn’t wake up one day and decide, “This is it.”<br>Instead, I stumbled through engineering, side hustles, failed startups, and half-baked ideas — each one teaching me something the last didn’t.</p><p>And slowly, by building, breaking, and rebuilding, I found something I actually cared about: design.</p><p>Not just design as aesthetics, but as thinking, problem solving, and creating value.<br>This is a story of that messy, surprising journey.</p><h3>Chapter 1: Aviation dreams and a crash course in reality</h3><p>Let’s rewind. I studied aviation engineering in Latvia — which, looking back, wasn’t exactly a masterstroke. Latvia isn’t known for a booming aviation industry. We’ve got one major airport and not a huge demand for engineers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fmGEKoGgbCMMnLoBi9k32Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*24rMGY4yCm0mU9aHrNBp8Q.png" /><figcaption>Working on the L-39 on the left, flying over Riga on the right a short but memorable time in aviation.</figcaption></figure><p>Still, I went all in. I even started training for a private pilot license, chasing the dream of flying.</p><p>I spent nearly four years in aviation — diving deep into math and physics, working on aircraft, and getting some flight time. It was challenging, fascinating, and — eventually — humbling.</p><p>Because one day it just clicked: <em>this isn’t for me.</em></p><p>I didn’t see a future in it. Not here, not now.</p><p>And so came the big question:<br><strong>If not this… then what?</strong></p><h3>Chapter 2: From running ideas to cold calls</h3><p>At the time, I was running a lot — long distances, often alone. And on those quiet runs, ideas had a way of sneaking up on me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6MDa29ecAEphCrJ_ZKmzeg.png" /><figcaption>In between dreaming up my first app, I stayed active in the local tech scene through events and meetups.</figcaption></figure><p>One day, the thought struck:<br><em>What if there was an app to connect people for sports or training?</em><br>Something simple, social, and useful.</p><p>I reached out to a friend — the local “IT guy” in our neighborhood — and asked,<br>“Can we build it?”<br>“Sure, why not?” he said.</p><p>We started contacting developers and agencies to find out what it would cost. The answer? Way more than we had.</p><p>It could’ve ended there. But instead, it sparked something else.</p><p>We figured: if we can’t build our own product yet, maybe we can build <em>for</em> others. Learn the ropes. Start somewhere.</p><p>So we pulled up 1188.lv — a Latvian business directory — and searched for companies without websites. If they didn’t have one, we called them. Cold.</p><p>Five calls. Three said yes.</p><p>Suddenly, we had our first clients. No portfolio. No process. Just some curiosity, a little courage, and a lot of improvising.</p><h3>Chapter 3: manamajaslapa.lv our first real venture</h3><p>Those first few projects gave us the push to formalize what we were doing.</p><p>We launched <strong>manamajaslapa.lv</strong> — offering websites, branding, and marketing.<br>It sounded professional. We weren’t.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ch-u4koRZtiLpWsPZp522Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mbk0t8Gl1VLIft5Mcxidmw.png" /><figcaption>On the left, our agency website. On the right, our first project — a site for a local brewery. Fun fact: we spent a few days just creating the hero image.</figcaption></figure><p>At that point, I didn’t even know how to open Photoshop.</p><p>The agency was just the two of us:<br>Me — sales, management, and client comms.<br>Him — code, tech, and everything else.</p><p>We got real clients, real deadlines, and real stress. One client had us making changes almost daily. Full redesigns. Endless feedback loops.<br>In another case, we hadn’t defined roles properly and ended up stepping on each other’s toes.</p><p>What I started to learn here — slowly — was that good design isn’t just about how things look. It’s about setting expectations, managing feedback, and aligning people before you start building.</p><p>We needed structure. We needed clarity. And we needed better process.</p><p>Eventually, I realized I didn’t just want to build for others.<br>I wanted to create something of my own — something that could live and grow without relying on client calls.</p><h3>Chapter 4: Talenthire.io the one that got away</h3><p>After years of juggling agency work and full-time jobs, I was burned out.I didn’t want to keep building for clients. I wanted to create a real product. That’s when <strong>Talenthire.io</strong> was born.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0SbFD6w7EmzLJTp6H12qjA.png" /><figcaption>Screens from the Talenthire.io app</figcaption></figure><p>The idea was simple: in industries like iGaming and customer support, companies needed to hire fast — and assess candidates’ spoken English and communication quickly.</p><p>Our solution? <strong>Video CVs</strong>. Candidates would record a short video introducing themselves — helping recruiters make better decisions earlier in the hiring process.</p><p>We built an MVP and pitched it to <strong>Startup Wise Guys</strong>.</p><p>They passed.</p><p>A few months later, COVID hit. Remote hiring exploded. Video CVs became the norm.<br>To our surprise, Startup Wise Guys backed a similar idea not long after.</p><p>That stung. But it was also a turning point.</p><p>I began to realize that ideas are only part of the equation. Timing matters. Execution matters.<br>And more than anything, you need partners who are just as committed as you are.</p><h3>Chapter 5: Ideapartners.co from teaching to building again</h3><p>Even after all that, I couldn’t stop building. And along the way, I had discovered something else I loved: <strong>teaching</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FBfxvi9tX4FxymtpelSzrA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lCixK-gKhtY9FP5RuvvJTA.png" /><figcaption>“On the left, the Ideapartners team. On the right, one of my UX classes in action.</figcaption></figure><p>I’d been running workshops, mentoring students, and teaching UX while working on products — and it was making me a better designer.</p><p>So I thought: What if we created a company that combined teaching with real-world design?</p><p>That’s how <strong>Ideapartners.co</strong> was born — a company focused on running design sprints, UX education, and collaborative design.</p><p>I started it with four partners. We launched a few UX bootcamps and worked with startups and non-profits. Things went well — at first.</p><p>But eventually, internal tensions showed up again. We had different visions. The company split into two branches:</p><ul><li><strong>UXTribe</strong> — focused on bootcamps and education</li><li><strong>Ideapartners</strong> — focused on participatory design and service research</li></ul><p>Both had strong momentum.<br><strong>UXTribe</strong> graduated over 100 students, with 90+ landing design jobs. These weren’t just numbers — my students were passionate, motivated, and serious about their futures.</p><p>But over time, <strong>UXTribe</strong> became more of a personal project. Today, it’s something I run to stay sharp, stay connected, and keep giving back. <a href="https://medium.com/@edijsbogomolovs/how-ux-teaching-made-me-a-better-designer-thinker-and-an-ultralearner-4d3c586cb355"><em>(You can read more about it here.)</em></a></p><p><strong>Ideapartners</strong>, on the other hand, eventually shut down.</p><p>We realized that scaling service design and deep research work is really hard. It’s slow. It’s people-intensive. And it doesn’t scale well, especially if you want to keep the quality high.</p><p>Still, it left a mark. We worked on some amazing projects — like co-creating a brand identity with over 100 people for the <strong>University of Oxford</strong>. That one I’ll never forget.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Ynf_zrG72niWXZBf6wNjw.png" /><figcaption>After weeks of workshops and iterations, this is the final identity we created for the Research Hub.</figcaption></figure><h3>Chapter 6: Mazaisdakters.lv solving my own problem</h3><p>By this point, I knew one thing for sure:<br>I didn’t want to build services anymore. I wanted to build a product that could work <strong>without me</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HqhbvudkM36ZIERLRPD5XA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XER84fMhN3yIHwBVCuU-hg.png" /><figcaption>A photo of me from the shoot on the left, and on the right — how it landed in the website’s hero section.</figcaption></figure><p>And I wanted to solve a real problem — <strong>my own</strong>.</p><p>I have two dogs. And every time we had to go to the vet, it was time-consuming and stressful.<br>I kept thinking: Why can’t the vet come to us?</p><p>So, together with a partner who was a veterinarian, we built <strong>Mazaisdakters.lv </strong>a simple website where people could schedule home visits for their pets.</p><p>From day one, we got clients. The idea made sense. But building trust and credibility takes time, and I was ready for that.</p><p>What I wasn’t ready for was the pressure I felt from inside the team.<br>I didn’t feel like a co-founder. I felt like an employee.<br>Creative freedom disappeared, and so did my energy for it.</p><p>So I stepped away.</p><p>Not every project has to succeed. Sometimes, just recognizing when to leave is the win.</p><h3>Final Thoughts</h3><p>As you’ve probably noticed, I screw up a lot.<br>But the one thing that’s kept me alive and growing is that I learn after every project.</p><p>Each misstep helped shape my path.<br>Over time, those failures turned into insights.<br>And somehow, along the way, I built a successful career in <strong>product design</strong>.</p><p>So how did I choose this profession?</p><p>I didn’t. I just kept following ideas. I kept creating.</p><p>And even now, I’m still doing it.</p><p>Right now, I’m starting to build a new product again.<br>I don’t know if it will work. But I do know this:<br>There has never been a better time to build,<strong> e</strong>specially in this new era of AI. It’s easier, faster, and more accessible than ever before.</p><p>So if there’s ever a time to try again — it’s now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c1dea542bac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How UX teaching made me a better designer, thinker and an ultralearner]]></title>
            <link>https://medium.com/design-bootcamp/how-ux-teaching-made-me-a-better-designer-thinker-and-an-ultralearner-4d3c586cb355?source=rss-c1205aedad6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d3c586cb355</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Eddy Bogomolov]]></dc:creator>
            <pubDate>Sun, 20 Jul 2025 05:51:10 GMT</pubDate>
            <atom:updated>2025-10-05T10:01:53.766Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q2GI1vj2D2IY_fqA5Gvsfg.jpeg" /><figcaption>When you and your friends try to stage a serious startup photo.</figcaption></figure><p>A few months ago, a friend asked me a question that stuck.</p><blockquote><em>“Why are you still teaching? I see you struggling to prepare slides again. You’ve taught this before, why not just reuse the old stuff?”</em></blockquote><p>I laughed at first. Then I paused.</p><p>Because honestly, it’s a fair question.</p><p>Teaching takes time.<br>Teaching takes effort.<br>Teaching doesn’t scale.</p><p>But what my friend didn’t realize is this:<br>Teaching is how I stay in shape mentally, emotionally, professionally.<br>It’s not just what I give to others. It’s what I gain for myself.</p><h3>Teaching UX is not easy</h3><p>If you’ve ever tried explaining what user experience is to a room full of 10 students, each from a different country, with different English levels, different professional backgrounds, and different levels of exhaustion,<br>you know it’s not a “plug and play” experience.</p><p>You can’t rely on scripts. You can’t wing it.<br>You have to adapt, translate, simplify, challenge, and clarify, sometimes all in the same sentence.</p><p>Even after five years of running <a href="http://uxtribe.eu/">UX bootcamps</a>, I still get that knot in my stomach before class starts.</p><p>Because each time, I’m forced to re-learn how to explain complex ideas simply.</p><p>And that’s the magic.</p><h3>Why I Changed uxtribe to 1:1</h3><p>Over the last few months, UXtribe has shifted its format.<br>No more group classes. No more lecture-style bootcamps.</p><p>Now, it’s fully one-on-one.</p><p>I’ve received a few messages asking <em>why?</em><br>From a business perspective, it makes no sense. It doesn’t scale. It’s not “efficient.”</p><p>They’re right. But they’re also missing the point.</p><p>Here’s what I’ve learned from going 1:1:</p><ul><li><strong>Learning becomes deeply personal</strong> — We focus on your specific goals, blockers, and career path. No generic content.</li><li><strong>Immediate feedback</strong> — Students don’t have to wait until “Q&amp;A time” to get clarity. Every session is feedback.</li><li><strong>True accountability</strong> — There’s no place to hide. You show up fully, and so do I.</li><li><strong>Real-world depth</strong> — We work on your actual challenges, not textbook hypotheticals. Your portfolio, your job prep, your design tests.</li><li><strong>Fewer distractions</strong> — No group pressure, no comparison, no waiting for others to catch up.</li><li><strong>Faster growth</strong> — Many students progress faster in fewer hours because we focus on what matters.</li></ul><p>Scaling this model is hard. But the <strong>impact</strong> is far greater.<br>And that’s what I care about, helping people break into UX with clarity, confidence, and critical thinking.</p><h3>What students are saying</h3><p>Here’s what one of our recent students shared after completing the program:</p><blockquote>“I see UI patterns, rhythm, hierarchy and user psychology everywhere now. I also see things on a different level in different fields, even in my current job. Whether it is marketing campaigns, materials or stand design — creating enjoyable user experience is vital. Just in 4 months’ time I am able to create a mobile app design in one day. Thank you Eddy for this practical and fun UX/UI bootcamp. Those late hours alone in the office but with a supportive team of 6 people in Zoom created so many new skills and experiences. One of the greatest investments made in my career.”</blockquote><p>This is why I teach. Not to lecture. But to unlock real progress — for both of us.</p><h3>Why I don’t recycle my slides</h3><p>Yes, I could reuse materials.<br>Yes, I could avoid one-on-one mentoring.<br>Yes, I could optimize my time and treat it like a business.</p><p>But I don’t.</p><p>Because the moment I stop updating, refining, and reacting…<br>I’m no longer a teacher. I’m a content machine.</p><p>If you stop being curious, your students will stop being curious.<br>That’s a lesson I’ve learned the hard way.</p><p>The moment you start saying, <em>“This worked last year, it’s good enough,”</em> you’re done.</p><h3>Enter: Ultralearning</h3><p>If you haven’t read <em>Ultralearning</em> by Scott H. Young, I recommend it.<br>The core idea is simple: intense, self-directed learning projects are the fastest way to master complex skills.</p><p>And guess what’s one of the most powerful ultralearning strategies?</p><p><strong>Teach what you’re trying to learn.</strong></p><p>Teaching forces you to:</p><ul><li>Break down concepts to the essentials</li><li>Spot your own blind spots</li><li>Constantly update your mental models</li><li>Stay accountable (because real people are watching)</li></ul><p>For me, teaching UX design is my ultralearning system.<br>Every question from a student forces me to check myself.<br>Every exercise I create reveals what I truly understand and what I’ve just memorized.</p><p>It’s pressure. But it’s productive pressure.</p><h3>The ROI of teaching</h3><p>The truth is, the biggest beneficiary of all this isn’t my students.</p><p>It’s me.</p><p>Teaching keeps me sharp.<br>It pushes me to think, reflect, and grow.<br>It helps me explain my thinking to stakeholders.<br>It improves my communication, my design decisions, and my empathy.</p><p>In short: <strong>teaching makes me a better product designer</strong>.</p><h3>So why do I teach?</h3><p>Not just to give.<br>But to learn.</p><p>Not just to share knowledge.<br>But to sharpen it.</p><p>Not just to grow others.<br>But to grow myself.</p><p>Teaching is my gym.<br>My ultralearning project.<br>And one of the best decisions I’ve ever made.</p><p>If you’re looking for a learning experience that adapts to you, not the other way around take a look at <a href="https://uxtribe.eu/">UXtribe.eu</a>.<br>We don’t teach from slides. We teach from real work, real pressure, and real growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d3c586cb355" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-ux-teaching-made-me-a-better-designer-thinker-and-an-ultralearner-4d3c586cb355">How UX teaching made me a better designer, thinker and an ultralearner</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a User-Friendly Order Tracker for the Largest Telecommunications Provider in the UK.]]></title>
            <link>https://medium.com/design-bootcamp/designing-a-user-friendly-order-tracker-for-the-largest-telecommunications-provider-in-the-uk-158e356a77e9?source=rss-c1205aedad6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/158e356a77e9</guid>
            <category><![CDATA[uxui-order-tracker]]></category>
            <category><![CDATA[ux-for-telecommunication]]></category>
            <category><![CDATA[ux-for-order-tracker]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[order-tracker-design]]></category>
            <dc:creator><![CDATA[Eddy Bogomolov]]></dc:creator>
            <pubDate>Mon, 23 Jan 2023 17:03:19 GMT</pubDate>
            <atom:updated>2023-01-25T05:25:02.406Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tHGJ_5SIZqD3pu5I1lwJCg.png" /><figcaption>The new order tracker design</figcaption></figure><p>Do you know that feeling of frustration when you place an online order and can’t seem to track its status? Well, let me tell you my own personal story of designing an order tracker.</p><p>In this story, you’ll learn about:</p><ul><li>The best practices for building better UX for an order tracker</li><li>The design process behind it</li><li>The UX challenges that come with designing an order tracker</li><li>And the battles that come with working with developers.</li></ul><h3>Background</h3><p>This company is going through digital transformation, and as a part of that, they are re-platforming<a href="https://www.vodafone.co.uk/"> the leading website</a> for retail customers.</p><p>This company was looking to revamp its order tracker. The current order tracker version had a significant number of users, with 3.8 million visitors per year. The help center was flooded with over 73,000 calls, to be exact, all about order tracking. Customers were inquiring about the status of their orders, delivery times, delays, and other issues. This influx of calls was putting a strain on the help center, and as a result, costs were increasing.</p><p>That’s where I came in. My goal was to design a new and improved order tracker to provide customers with the needed information and reduce the number of calls to the help center.</p><p>The project objectives were:</p><ul><li>The main goal was to decrease calls to the help center</li><li>Communicate more precisely order status;</li><li>Use language that is familiar to customers;</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FCTFBVwXPxcPAhmESRh10g.png" /><figcaption>The order tracker before the redesign.</figcaption></figure><h3>The call for adventure</h3><p>As a<a href="https://edijsbogomolovs.com/"> multidisciplinary product designe</a>r with seven years of experience, I was excited to design a new order tracker for this company. But as I dove into the project, I soon realized that the sheer size of the organization made communication a complex and time-consuming task. Navigating through layers of product owners, managers, developers, and stakeholders proved to be a major hurdle. Despite the challenges, I was determined to see the project through with the help of a dedicated development team and a diverse group of stakeholders, including a product owner, lead architect, and experience manager.</p><h3>Finding main pain points</h3><p>The first step was to understand how the current order tracker works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lc7eiZW6o7uxp_gEGA2_wQ.png" /><figcaption>When creating an order tracking system, there are many different factors to consider. To make sure it’s user-friendly, it’s important to understand how all the different parts of the system work together. Here’s a list of the different variables you’ll need to take into account</figcaption></figure><ul><li>Do all the ordered products have the same journey?</li><li>What kind of carriers do we have to use, and are they applicable to all ordered products?</li><li>What are the delivery types?</li><li>How are we labeling the order statuses now?</li><li>How are milestones related to statuses?</li><li>What are the user journeys?</li><li>What are the technical restrictions on what kind of data we are getting?</li></ul><h4><strong>Inconsistent messaging</strong></h4><p>To begin this project, I needed to gain a comprehensive understanding of the current order tracking system and how all of its components worked together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ySM0PxXQ9qU9zyY5C0JPwg.png" /><figcaption>Messaging that we use across different mediums.</figcaption></figure><p>During my research, I discovered that we were not consistently providing customers with accurate delivery information. For instance, when a customer orders a device on our website, they may be given an estimated delivery time of the next day between 8 am and 6 pm. However, upon receiving their confirmation email, the estimated delivery date may be changed to December 11th. And upon checking the order status, they might see yet another delivery estimate of December 11th, 2022. This inconsistency in delivery information can cause confusion and frustration for our customers.</p><p>I recognized that the current system might be causing confusion and dissatisfaction for our customers, as they were receiving inconsistent information from various sections of our website. I understood that this could be a source of frustration for them.</p><h4><strong>Order statuses vs. Order Milestones</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wOIfilvrL_V8XwQmx1doeQ.png" /><figcaption>Responses what we are getting from the database</figcaption></figure><p>The next issue I encountered was how we communicated information about the status and milestones of orders. I found that many different statuses and milestones were being used, and it was difficult for customers to understand how they were related. I realized that we needed to work on the service side to ensure everything was clear and organized.</p><p>One of the primary issues was that the statuses and milestones were too similar in wording, which made it difficult for customers to distinguish their meanings. This led to confusion and difficulty in understanding which status was appropriate to use. For instance, there were different statuses such as “open,” “order received,” and “order confirmed,” which caused confusion.</p><h3>Layout</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S_TwHawxF2kj3vgVpwGOMw.png" /><figcaption>Confusing parts of the current order tracker.</figcaption></figure><p>When I first looked at the order tracker layout, I immediately noticed that it needed to be updated. The design and layout were different from what customers were used to seeing on similar websites, and it took me a while to figure out how everything worked. I found it challenging to quickly scan and understand the information presented, and there were a few things that I couldn’t figure out right away. Questions like “What are the delivery groups?” “What’s the status of my order?” and “When will I receive it?” were on my mind.</p><p><strong>Summarizing everything, we discovered four main opportunities:</strong></p><ol><li>Making sure that the delivery information provided to customers is consistent and clear. This will help set the right expectations and improve the brand’s credibility and the product’s value.</li><li>Understanding how customers think, feel, and predict the order tracker statuses and milestones. For example, when the order tracker says that an order has been received, what does that mean to the customer?</li><li>Aligning the service-side responses with the customer side. This will help us understand when and in which order statuses to provide clear and relevant information to customers.</li><li>Improving the layout and information hierarchy of the order tracker. We want to use conventional UI patterns so that customers can easily predict what information they will receive and find the information they need.</li></ol><h3>Working on the challenges</h3><p>Resolving the problems with the order tracker was a challenging task, but with the collaboration of our team of developers, managers, and product owners, we were able to standardize the order status and milestones. The process was not always straightforward, but we found a solution that worked effectively.</p><p>I found it helpful to start by collecting all the information in one place using Figjam, online whiteboarding, and collaboration tool. I gathered screenshots, questions, meeting summaries, and everything else I thought would be helpful. By consolidating all information in one location, we were able to generate new ideas and come up with ways to enhance the order tracker efficiently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8IVxuc4-mjoz9mk4XThEnQ.png" /><figcaption><em>The Figjam file workspace screenshot: that we used for keeping all materials, brainstorming, and wireframing</em>.</figcaption></figure><p>Figjam proved itself to be quite useful for quick wireframing. It would be more effective to show the team how and where the information would be presented in the new design rather than just talking about it. This helped to create momentum and focus on the content side of the redesign.</p><p>Finding the right balance regarding the level of detail in the wireframes was also important. Using wireframes with less detail could have led to discussions about the design’s specifics rather than the main objectives of the redesign. However, providing the appropriate level of detail in the wireframes helped the team grasp how the new design would function and what information it would convey to customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e0AcWKTMvWx6Rv86CXlS9w.png" /><figcaption>Wireframing the log-in journey for the order tracking in Figjam</figcaption></figure><p>Through wireframing and various iterations of feedback and revisions with the team, I developed a mind map that encapsulated all the crucial components of the order tracker. This included delivery types, carriers, product groups, customer journeys, and use cases. It was the first document that brought all the different parts of the order tracker together in one place and served as an excellent reference for the team.</p><p>The mind map was a valuable tool that helped us visualize the different elements of the order tracker and how they fit together. It gave us a clear understanding of the big picture and helped us to identify any areas that needed further attention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NsVR44IchbfzjYOH5hd5CA.png" /><figcaption>The mindmap I created in Figjam helped create a visual guide for the team.</figcaption></figure><p>At this point in the process, we clearly understood what information needed to be included in the order tracker. But it was just as important for us to understand what information our users expected to see in the order tracker. We wanted to ensure that we were meeting their needs and providing them with the information they needed to track their orders effectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_3jvT2WCSEnYOBiI5cTycA.png" /><figcaption>Information architecture comparison table showing what different information competitors are placing on the order tracker page.</figcaption></figure><p>We researched and analyzed multiple order tracking tools to identify the best data and organization for our customer’s use. I examined the layout, data hierarchy, and design elements to understand what was effective and what needed improvement in creating the ultimate order tracker.</p><p>With this information in mind, we created an initial design for our new order tracker. We knew what types of data needed to be included and had a good idea of how that information should be organized. We also used an existing design system to save time and increase efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cehb2avi_JtCix0X8bwsRw.png" /><figcaption>The first iteration of the order tracker</figcaption></figure><h3>Validating design</h3><p>To ensure that our new order tracker design would meet the needs of our customers, we wanted to validate our design by testing it with real users. The goal of the test was to gather insights into the attitudes and behaviors of our customers, so we could identify any needs or pain points in our design and ensure that the experience was as smooth as possible.</p><p>We used Userzoom to conduct an unmoderated usability test and card sorting. We asked various questions to understand users’ behavioral habits when tracking their orders, their expectations when tracking their orders, and if they understood the information shown on the order tracking page.</p><p><strong>As a test results:</strong></p><ol><li>Participants generally liked the simplicity and information clarity of all designs.</li><li>The milestones for each scenario were appreciated, showing the different stages to make it easier to follow and track the process.</li><li>Participants did not feel the tracking information belonged under “Settings” and found this confusing. They expected this to be under “My Account.”</li><li>Adding a more precise location of the package, including the date and time of progress update — perhaps presented under expandable milestones.</li><li>Include assistance links/options in case of any issues.</li><li>Replace vague timelines with precise dates, i.e., instead of “next working day” and ”shortly.”</li></ol><h3>The final steps</h3><p>After an intense user test, we immediately began implementing the research findings into our design. Our first step was to streamline the order process by simplifying the order statuses and milestones. I went from having nine different statuses to just three — “on track,” “completed,” and “canceled.” We also organized the milestones into two distinct groups — “broadband” and “non-broadband,” with the only difference being the addition of the “activation” milestone for the broadband group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*elgz9hKfUvgJGg8t-TxjDA.png" /><figcaption>Order status &amp; milestones before(Left) and after(Right).</figcaption></figure><p>We also realized that using different date formats was confusing customers, so we decided to standardize and use one date format throughout the order tracker. Instead of using phrases like “tomorrow” or “shortly,” we used a more precise date and time range. This helped customers to have a better understanding of when they could expect to receive their orders.</p><p>To make things more user-friendly, we have included a summary section on our website to establish clear expectations for our customers. This is particularly beneficial for items with multiple components, such as broadband service, which often necessitates four distinct parts and an engineer visit for activation. By providing this information in advance, we aim to make the ordering and delivery experience as seamless as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PetWYFVUJuYpsGLCovz6ZQ.png" /><figcaption>Order tracker page designs on the left before research and on the right after research.</figcaption></figure><h3>Battles with Developers</h3><p>We faced a couple of challenges when agreeing on using images and the stepper component change. I knew both were crucial to creating a valuable order-tracking experience for our customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hkzPlOqVNnuR1rRdcyrnpQ.png" /><figcaption>Before vs. after</figcaption></figure><p>I included an image in the order tracker because it allows for quick and easy information communication. This means customers can recognize what they ordered instead of recalling it from memory.</p><p>Throughout the project, I showcased designs with and without images side-by-side to demonstrate the significance of incorporating images and convinced the team to invest time in them.</p><p>We heard from our customers that they want more information about when each milestone will happen on the order tracker. So, we decided to update our stepper component to include this information. It may seem like a small change, but it can be quite a big task when you’re working within a big organization and have to adhere to a design system.</p><h3>Design process summary</h3><ol><li>We created a designated space for async work, where team members could access screenshots and questions at their convenience, fostering a more collaborative environment.</li><li>We delved deep into the existing microsites, emails, and support threads to gain a fresh perspective on the project’s current state.</li><li>Our quick wireframing technique allowed us to align with the team on functionality and identify any missing pieces.d gaps.</li><li>We organized all information in an easily digestible format, so all team members could quickly grasp the main aspects of the project. We employed a mind map in this project.</li><li>We also conducted a thorough competitor analysis, comparing their solutions and focusing on UI patterns and mental models.</li><li>We utilized a design system to streamline the design process.</li><li>We put our designs in front of real users to see their reactions and truly gauge their effectiveness.</li><li>And last but not least, we covered all bases by producing design variations that accounted for uncommon use cases, ensuring a seamless design handoff to developers.</li></ol><h3>Conclusion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUtL8ky5bhhh1ZQZvC0oIg.png" /><figcaption>The order tracker design before on the left and after a redesign on the right.</figcaption></figure><p>Designing an order tracker for the largest telecommunications provider in the UK was an exciting and fulfilling experience. The process allowed me to work through the entire design process, from user research to implementation. It was gratifying to see how my efforts and ideas translated into a real application that customers will use on a daily basis. Overall, it was an excellent opportunity to be a part of a team that was able to deliver a valuable solution for the customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=158e356a77e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/designing-a-user-friendly-order-tracker-for-the-largest-telecommunications-provider-in-the-uk-158e356a77e9">Designing a User-Friendly Order Tracker for the Largest Telecommunications Provider in the UK.</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Advocate and Articulate User Experience!]]></title>
            <link>https://medium.com/uxtribe/how-to-advocate-and-articulate-user-experience-adcf7915e25e?source=rss-c1205aedad6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/adcf7915e25e</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-articulation]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[how-to-articulate-design]]></category>
            <category><![CDATA[ux-and-design]]></category>
            <dc:creator><![CDATA[Eddy Bogomolov]]></dc:creator>
            <pubDate>Sun, 15 May 2022 16:10:10 GMT</pubDate>
            <atom:updated>2025-05-18T20:19:07.282Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IFCX0JySlpGKhTXKkOQeTA.png" /><figcaption>UX designer vs Stakeholder.</figcaption></figure><p>It’s getting better and better but still, how many times have you had to justify why user experience matters and what it actually means?</p><p><a href="http://uxtribe.eu/">As a UX teacher </a>and UX designer, I often find that people do not understand user experience design. I mean, not just the stakeholders but also the designers themselves. If I am being honest, this isn’t totally their fault, UX is a pretty new field, and the design itself is subjective. There are also different reasons why people barely understand user experience design, and one of them is culture.</p><p>Every time we have our UX Bootcamp, I usually start by saying, “The difference between a UX designer and an artist is that a designer creates a solution using data but an artist by using emotions.” What I mean when I say that is that there is no place for subjectivity amongst UX designers.</p><p>Everyone is a “designer,” but not everyone understands the UX designer’s challenge. There are many people who know little or nothing about design but who have the authority to oversee and dictate the design practice.</p><p>In this article, I will share tactics and strategies that will help you convince stakeholders that your decisions are the best choice.</p><ol><li>Desing</li><li>Understand your stakeholders</li><li>Connect your design back to the user.</li><li>Have a plan for presenting your work and asking the right questions.</li></ol><p>4. Respond to feedback by refocusing on user needs and business goals.</p><p>5. Involve your stakeholders from the start.</p><h3>Designer vs. Stakeholder: Is there a shared understanding of UX design?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jVtuswsjz0kRbhi81mLg8Q.png" /><figcaption>UI is part of UX, not a separate unit.</figcaption></figure><p>To successfully cover how to convince stakeholders, we must first understand their perceptions and beliefs about designs. We also need to fully understand what the user experience design space is all about.</p><h4>Look vs. Value</h4><p>A stakeholder wants all the aesthetics! Often, this is at the expense of the product value.</p><p>A couple of years ago, when I was working for a large consultancy agency, we created UX for a German enterprise brand. The main goal was to simplify onboarding and make it more engaging.</p><p>The first design iteration was terrific, but the second iteration revealed a massive gap in our work. During the second iteration, stakeholders prompted phrases such as add a button here, move it here, and so on. These discussions led us to light vs. dark mode, yellow color vs. green color, and one button vs. three buttons. As you can imagine, we forgot about the primary goal of simplifying onboarding and making it more engaging for the users.</p><p>People often look at something and react without considering the project’s original intent. Instead of focusing on the product value, a team (such as ours) might be tempted to find a compromise about the product look, in other words, to save the product design from rainbow Kamasutra. This isn’t a bad idea, but the original intent that focuses on the project’s value is the UX designer’s goal and should always be considered.</p><h4>Why are stakeholders requesting more aesthetics?</h4><p>In recent times, UX design is gradually becoming more about aesthetics than about problem-solving. Only a few people still perceive UX designers as artists responsible for making stuff more professional.</p><p>UX is a new term that has evolved over the past decades and continues to evolve. Too many companies were and are still trying to develop fancy words that cause miscommunication and set wrong expectations.</p><p>Answer this question: what is the difference between UX, CX, UCD, and HCI? UX has almost completely replaced graphic or web design as we used to know it. Apart from that, designers are trying to grow popularity by redesigning large companies’ websites without any clue what the business needs are, thereby focusing on aesthetics.</p><p>Everyone is obsessed with how things look more than how they work!</p><p>The transition from traditional design (the look of designs) to using a design as a competitive advantage isn’t quite there yet. The result of this ongoing process is that some designers and stakeholders tend to focus more on look than the design value itself. It happened with us, too; the product look was more important than the product value.</p><h4>Everyone is a designer, but is everyone a UX designer?</h4><p>Let’s be honest, everyone knows good design when they see it. The same can be said for other arts, such as music. I may not know how to play an instrument, but I know a pleasing tune when I hear it.</p><p>So many of us use many different apps daily, which influences our opinion of how things work or should work. This means that every time we see a design, we already have an unconscious expectation about it.</p><p>As a designer, imagine a sprint demo or design review, all your work is exposed, so it naturally attracts more opinions and ideas than any other area in the organization. Everyone has suggestions and recommendations.</p><p>The continuous occurrence of non-experts having an opinion about your design work is, unfortunately, gradually becoming more and more integrated into the design process.</p><p>Therefore, before starting the discussion about a design, you should know these so that you can educate your team and stakeholders:</p><ol><li>UX designers do much more than just design beautiful things. We add value to the products. Do you remember Myspace, the social network before Facebook? Facebook destroyed Myspace with a better user experience and an understanding of the user’s needs and motivation. Isn’t the like button still one of the most popular features?</li><li>People tend to emphasize the more visual side of the product instead of its value. You need to remember and reiterate that it is not about look but about the value that the design creates. Ask yourself, why is this product or feature important?</li><li>Everyone has their expectations of a design. Try to familiarize yourself with their design preferences and use them to your advantage.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3xZVbZj0XlNhJF0W6tiQGA.png" /><figcaption>In reality, who is responsible for the design.</figcaption></figure><h3>Misconception Amongst Designers</h3><p>Let’s do a quick experiment.</p><p>If you know a UX designer, ask them this question: what makes a good design? You will hear a lot of different answers to the same question; a good design solves business and user pain points, a good design should be desirable or easy to use, etc…and they will all be correct. Still, despite their slight nuance, the one thing that we often forget is that the users influence our design.</p><p>As a designer, you can develop an excellent design based on user research. But, if you fail to communicate your designs with stakeholders or the team, you risk the design being completely different from what you intended in the end.</p><p>It’s almost impossible, but the design has to be supported by everyone. Effective design communication and strong relationships are as powerful as an excellent design solution, so I strongly advocate that design should be participatory. We, as designers, should design not for stakeholders but with stakeholders.</p><p><strong>So, what makes a good design?</strong></p><p>A good design solves a problem, is desirable, and is supported by everyone. The keyword here is “everyone.” Your design needs to get approval from the whole team and all stakeholders!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EuR3577hWbmsPfkYRunNHQ.png" /><figcaption>Stakeholders are as crucial as users.</figcaption></figure><h3>Understanding stakeholders; why is this important?</h3><p>As UX designers, we are good at defining user needs and their pain points. But often forget that we need to do the same thing for the people who hold the keys to our success. We forget the essentials that we need to create relationships with stakeholders and other influencers in the team. We must get in their heads, find out what makes them tick, and with this information, approach them in a way that is productive and valuable for everyone.</p><p>Okay, let’s look at it this way, imagine that you will be presenting the design to stakeholders during a meeting. What kind of distractions can the stakeholders have? They can be dealing with things in their personal and professional life that are more important to them than the current design project. They can also have completely different perspectives and experiences. Many various factors can influence their decision-making. How would you make sure that you present your case to them effectively?</p><p>“They are not designers, and they don’t understand” that’s not true. Stakeholders’ reactions to our design often have an underlying situational explanation that we might never know about.</p><p>Engage with them on a more personal level, see their perspectives and understand them. Create a shared experience. You can gain someone’s trust and commitment little by little over time. The goal is to learn how to approach and respond to them.</p><p>Understand the stakeholders! They are just as important as the end-users.</p><h3>Set feasible objectives!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*betkuKIuXlqpW6nzocCCDw.png" /><figcaption>Keep the objective at the center of the discussion.</figcaption></figure><p>Recently, I participated in a meeting where a designer presented a new feature for a product to stakeholders. In the first 20 minutes of the meeting, the stakeholders were presumably still on track. But once the designer asked how do you like the new feature? The stakeholders immediately started asking a bunch of questions. The designer’s responses were nothing but broad, using phrases such as “from my experience,“ “from my perspective,” and so on. These responses did not convince the stakeholders, and neither was the designer allowed to discuss another product feature.</p><p>What two things can we learn from the above story?</p><p>First, set objectives for yourself, e.g., getting agreement from the stakeholders. Second, it is the designer’s job to keep the meeting on track and get the stakeholders’ agreement on the design.</p><p>When preparing for a meeting, remember why you are there and do not allow anyone else to lead the discussion in a different direction.</p><h3>Necessary Strategies in Responding to Stakeholders</h3><p>We have reached the point where you are just one step away from having the design discussion.</p><p>You have set an objective for the meeting — To get agreement from stakeholders.</p><p>You have done an excellent job understanding stakeholders’ personalities and building a relationship with them.</p><p>Most importantly, you now know that you need to focus on the value of the product instead of the look and that the design’s success depends on team agreement.</p><p>Now, you need to know what you should say to achieve your objective of getting the stakeholders’ agreement.</p><p>To successfully get agreement from the stakeholders about your design, you need to have answers to these three questions:</p><h4>What problem does it solve?</h4><p>With our designs, as UX designers, we are solving problems. Every decision we make should reflect that. This is an idea associating your design with an agreed-upon metric. Stakeholders can easily ask many questions and completely forget about the purpose of the meeting. This is where you remind them to focus on the metric that was agreed-upon. Without a metric, the conversation can quickly transform into the monster of addressing each concern.</p><h4>How does it affect the user?</h4><p>You are the only window between users and stakeholders. Your response should always represent the user. This means that you have to understand the user. You can get to know the users through observations and usability studies and use existing research as evidence for your design decision(s). Tell stakeholders a story about your users and how your design will help solve their pain points.</p><h4>Why is it better than the alternative?</h4><p>We need to demonstrate to stakeholders why our solution is better than the alternatives, including those suggested by the stakeholders. We want to ensure that our response includes examples, data, options, comparisons, or any other visual demonstration of why our designs are the best choice for both the user and business. Your answer to this question is your opportunity to talk about why your design is better and go ahead to visually show why and how your design will make a difference.</p><p>These three questions create the foundation for every response you provide to stakeholders. It would be best if you communicated that your design solves a problem, makes it easy for users, and is better than the alternatives.</p><h3>The Best Tactics in Responding to Stakeholders</h3><p>While strategy is the action plan that takes you where you want to go, the tactics are the individual steps and actions that will get you there.</p><h4>Show a comparison</h4><p>Too often in meetings, we talk about design pros and cons, but our words are not effectively demonstrating the effect on user experience. Therefore, an excellent tactic is to show a comparison between your proposed design and the suggested changes. Show them side by side that the differences between the two are apparent.</p><h4>Propose an alternative</h4><p>The next tactic for responding is to show a design alternative. Show how you explored different variations of design. There is always more than one way of solving a problem. Any solution you propose will create space for more conversation, whether right or wrong.</p><h4>Give them a choice</h4><p>Good design is about unity. All design elements support each other to create the whole. This tactic is about giving a choice to stakeholders between what they want and a new thing they are suggesting.</p><p>For example, you know that the header goal is to guide users to the form page, and now stakeholders are asking you to add a button next to the form button. Give the stakeholders a choice to decide what is more critical, the form submission or a new CTA.</p><h4>Ask others to weigh in</h4><p>Show that people around you support your design decisions. You are not alone in the room. Ask other people to weigh in. That way, you will be able to convince stakeholders that others are already in agreement with you. By doing this, you will also take pressure off of yourself. When you let other people take their stand, you tactically avoid the awkward position of disagreeing with a stakeholder.</p><h4>Postpone the decision</h4><p>If all tactics fail, and you feel that the conversation is going in the wrong direction and can negatively impact the user experience, postpone the decision! Often, good ideas at the moment turn out to be poor choices in the future. Lead with “yes,” “Yes, I see your point. We need to find the right solution. How about I take the next few hours to work on it, and then we can check-in.” Iterating design is always a good idea.</p><h3>The ideal response!</h3><p>We will be dividing the ideal response into 6 phases:</p><h4>Thank you, repeat, prepare</h4><p>First, it is essential to create a natural transition between stakeholders’ feedback and your response. Start your answer with thank you — “<strong>Thank you</strong> for coming up with this idea to change colors on the CTA buttons.” <strong>Repeat </strong>stakeholder’s suggestions -”I know you would like to increase account dashboard engagement with the users by changing the CTA color.” <strong>Prepare</strong> stakeholders for your response — “We’re intentionally using the red color CTA’s to maintain consistency across design, so let’s talk about the best way to help you.”</p><h4>Identify the problem</h4><p>We always need to keep the stakeholders’ attention on the goal. Otherwise, the conversion can quickly switch directions and become unproductive. Always repeat the problem your design is solving, and ensure that everyone is on the same page. For example, “the issue we’re trying to address is that when a user sees the interface for the first time, they are confused by several buttons and don’t know what each one means and what they need to do next.”</p><h4>Describe your solution</h4><p>Tell a story about your design and how it connects to solving the problem. For example, “Our solution is to capture the bulk of the user’s attention by highlighting the primary button. We will use a red button against outlined buttons. As a result, the button will stand more against other buttons and unconsciously lead users towards engagement. This solution will create an invisible order in how users should consume information and react”.</p><h4>Empathize with the users</h4><p>Emphasize and remind Stakeholders that, as UX designers, we are solving problems for specific users. Say something like, “We don’t want our users to be overwhelmed by the number of options in the main header. Instead, we can provide more value to them by reducing choices. “</p><h4>Appeal to the business</h4><p>Our designs should be motivated by the need to grow a business. Convince stakeholders that your design will impact the business. Bring up the goals, the KPIs, and other metrics. Here’s an example, “We believe our solution will increase conversion because it reduces the choices users need to make, and fewer options mean faster decision time which in turn increases engagement with the users.”</p><h4>Lock in agreement</h4><p>Getting an agreement is the most crucial phase of your IDEAL response. Without an agreement, everything that you present is just an idea. Put stakeholders in a position where they need to decide to keep the project moving forward. Ask them directly, “Do you agree”? “Do you agree that we will provide greater visibility and improve the experience? Or do you think we need to change CTA colors and risk getting lost in the other options?”</p><p>To sum up, design articulation is vital to creating a successful design. UX designers do not make final decisions but the stakeholders. You, as UX designers, most be prepared on how to articulate design.</p><p>This article is highly inspired by Tom Greever’s book “Articulating design decisions.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adcf7915e25e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxtribe/how-to-advocate-and-articulate-user-experience-adcf7915e25e">How to Advocate and Articulate User Experience!</a> was originally published in <a href="https://medium.com/uxtribe">uxtribe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>