<?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 Eliza Burenok on Medium]]></title>
        <description><![CDATA[Stories by Eliza Burenok on Medium]]></description>
        <link>https://medium.com/@burenok.eliza?source=rss-b138941e1076------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BrIZu-LngwU2HpvJt_vObw.jpeg</url>
            <title>Stories by Eliza Burenok on Medium</title>
            <link>https://medium.com/@burenok.eliza?source=rss-b138941e1076------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:50:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@burenok.eliza/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[4 steps toward a product design offer]]></title>
            <link>https://medium.com/design-bootcamp/4-steps-toward-a-product-design-offer-2a2ca7a92b7c?source=rss-b138941e1076------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a2ca7a92b7c</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Eliza Burenok]]></dc:creator>
            <pubDate>Thu, 29 May 2025 11:45:29 GMT</pubDate>
            <atom:updated>2025-05-29T11:45:29.274Z</atom:updated>
            <content:encoded><![CDATA[<p>For the past two years, I’ve been involved in developing the <a href="https://samokat.ru/">Samokat</a> food delivery app (delivery in 15 minutes), and in May, I decided it was time to move on and started looking for a new team. Though I’ve changed jobs before, I still feel a bit of excitement and nervousness every time. That’s why I decided to gather my experience into a short note, where I share the steps and practices that helped me find a new position in a short time.</p><p>I’ve not only been a candidate myself but have also interviewed people for my team. Having been on both sides of the process, I’ve realized that success comes down to three factors: a strong resume, a well-prepared portfolio, and friendliness.</p><h4>A strong resume</h4><p>I’ve seen designers assert their expertise by listing every job they’ve ever had across three pages. The desire to make an impression is understandable, but please don’t do this. The golden rule is to keep your resume to a single A4 page — after reviewing it, recruiters and hiring teams should have a clear idea of who you are.</p><p>If you already have several years of work experience, don’t hesitate to describe your responsibilities factually: your position, the tasks you performed.</p><p>Avoid vague statements like, “We worked with the team to design scenarios and improve the user experience.” Instead, describe the actual scenarios and explain how you determined that the experience was truly improved (this is your chance to show how your design impacted business metrics).</p><p>If my experience at a company lasted more than a year, I break down what I accomplished on each project in chronological order: first there was Project X, then for four months I worked on Project Y, where I was responsible for certain tasks. This makes it easier for recruiters to match your experience and skills with the requirements of the position. And if things don’t work out, you’ll know it’s not that you’re “not good enough” — it just means your current experience and skills don’t fit the role, which is absolutely normal.</p><h4>A well-prepared portfolio</h4><p>The same principle applies here as with your resume: present your portfolio so that people can tell at a glance whether to invite you for an interview.</p><p>As much as we’d like to think otherwise, design directors and art directors often have limited time to review portfolios. Your presentation will stand out if it is visually compelling (I won’t go into layout techniques here, but I’ll include examples of portfolios I like at the end) and relevant.</p><p>If you’re applying for a designer position in a SaaS product, but your portfolio features one case study about an online store and another about a language-learning app, it will be harder for the team to assess your expertise. And anything that’s hard to evaluate is either put on hold as a backup or simply rejected — sadly.</p><h4>Friendliness</h4><p>When I got my second job, I didn’t have as much experience as the position required. But after the interview, I ended up joining the team. Much later, I found out that it was my attitude that convinced the design lead to give me a chance. We still keep in touch, and in the meantime, I’ve conducted many interviews myself. Here’s what I can say: kindness, openness, and a positive attitude can be a huge advantage.</p><p>Many companies build their value systems and look for people who fit in organically. Teaching someone how to create presentations in a brand style or how to name components correctly is a matter of time, but instilling a company’s values and approach is much harder. It’s disappointing when it turns out that you’re just not a good match for each other.</p><p>What we’ve already discussed covers the fundamentals that are good to keep in mind when looking for a job. Next, I’ll share the practical steps I took during the interview process. They’re listed in chronological order and organized by topic for clarity.</p><p>I started by asking myself, “What do I expect from a new place and what opportunities do I want to find there?”</p><p>An honest conversation with yourself will help you later compare company offers with what you set as your own priorities.</p><h3>Step 1. Defining your requirements</h3><p>Before starting your job search, identify two key areas for yourself:</p><ul><li>Your applied tasks and role</li><li>Your strengths</li></ul><p>Write down what you have already accomplished and what you would like to do. This will make it easier to filter suitable vacancies from the start. It’s also a good self-check. For example, when I started thinking about looking for a job, I was sure that I only wanted to work on B2C products. But when I described my experience and the tasks I wanted to take on, it became clear that I was most interested in working with large, multifunctional systems: designing complex scenarios, identifying common patterns, and fully immersing myself in development.</p><p>It’s important to me that the product has a large audience with an extended role model, and that I have direct access to it. At the same time, the conceptual part and highly detailed work with interface elements, while undoubtedly important, are not as interesting to me at the moment.</p><p>To help you avoid uncertainty about which skills are most valuable in B2C, B2B, and end-to-end directions, let’s break each of them down.</p><p><strong>B2C</strong> — consumer products that solve problems users encounter in everyday life. This includes food delivery, personal planning tools, ride-hailing, and payment systems. In all cases, the product always works directly with a person, who is willing to pay for the solution provided. Most often, you have to compete with other offerings on the market, so the product must stand out with high-quality design: simplicity, strong visual execution, and a satisfying user experience. What is expected from a designer in this case:</p><ul><li><strong>Strong UI design skills</strong>, with knowledge of color theory, layout, typography, and principles of visual perception</li><li><strong>Experience working with platform guidelines:</strong> <a href="https://developer.apple.com/design/human-interface-guidelines">Apple Human Interface Guidelines</a>, <a href="https://m3.material.io/">Material Design</a></li><li><strong>Designing for desktop and mobile applications (including mobile web versions)</strong></li><li><strong>Understanding how to conduct market analysis and collect benchmarks</strong></li><li><strong>Ability to conduct qualitative user research:</strong> finding and recruiting respondents, developing methodology and writing scripts, conducting interviews, synthesizing results; and quantitative research: creating surveys and launching them on platforms</li><li><strong>Advanced animation skills:</strong> creating complex prototypes, demonstrating element behavior with transitions</li><li><strong>Popular frameworks:</strong> jobs-to-be-done (JTBD), customer journey, wireframes, priority guides, conceptual design, personas, job stories, mood boards</li></ul><p><strong>B2B and E2E products</strong> are aimed at solving business problems. In this case, the target audience consists of employees or people working according to a specific scheme with narrowly defined tasks. The decision-maker is the company. Business processes in such products are nonlinear, and one of the main tasks of the product team is to simplify the user’s journey as much as possible without disrupting critical operations. Although B2B and E2E products differ in specifics and audience, the skills required of a designer are similar for both:</p><ul><li><strong>Understanding the principles of high-load systems:</strong> how the backend exchanges data with the frontend, how the database is structured, and with whom integrations are necessary — these are significant parts of the work that it’s helpful for a designer to understand.</li><li><strong>Ability to work with complex, multi-step scenarios and to consider edge cases for them.</strong></li><li><strong>Designers will primarily work with desktop products, so it’s important to have a solid understanding of interface design patterns.</strong></li><li><strong>Ability to conduct qualitative user research:</strong> developing research methodology and writing scripts, conducting interviews, and synthesizing results. Recruitment is often unnecessary, since users are employees of the same company and are easy to contact.</li><li><strong>Ability to create business process diagrams to simplify information and use them later in design work.</strong></li><li><strong>Documenting solutions for future use by other teams.</strong> Internal products are often interconnected, so it’s important to develop and use common principles if the company does not yet have a well-developed design system.</li><li><strong>Popular frameworks:</strong> user journey map, task flow, service blueprint, wireframes, stakeholder map, OOUX (object-oriented user experience), sitemap (information architecture), UML diagrams.</li></ul><p>As a result, you should have a clear understanding of your competencies and in which business areas they can be most useful.</p><h3>Step 2. Company search</h3><p>Based on your requirements, select the companies or products you would most like to join. Many designers prefer to send their resumes to every available vacancy indiscriminately. Recruiters refer to this as “shotgun applications” and usually give such candidates low priority.</p><p>I chose companies whose products and values are close to me. To apply, I didn’t use job-search platforms (such as Headhunter, Glassdoor, or Indeed), but instead submitted my resume directly on the career websites of my chosen companies. In my experience, responses come much faster this way than through job search platforms, although this may depend on the employer and the country.</p><h3>Step 3. Resume and portfolio</h3><p>In this exact order: first the resume, then the portfolio. Recruiters look at the first, while the team evaluates the second.</p><p>I’ve already briefly explained the principles of resume writing above, so I’ll move straight to the portfolio — with just one note:</p><p>Try not to make your portfolio using Notion.</p><p>Yes, it’s fast, yes, it offers ready-made templates and a serious time savings. But presenting your work in Notion was fresh in 2017, in 2020, but definitely not in 2025.</p><p>Nowadays, there are plenty of tools that allow you to create a portfolio without any programming skills. This will show the hiring side that you’re a curious designer who explores new tools and isn’t afraid to experiment.</p><p>Here are a few examples of great no-code editors:</p><ul><li><a href="https://www.framer.com/?via=designsystemssurf">Framer</a></li><li><a href="https://cargo.site/templates">Cargo</a></li><li><a href="https://bento.me/en/home">Bento</a></li><li><a href="https://readymag.com/">Readymag</a></li></ul><p>I built my own <a href="https://elizaburenok.github.io/site/">portfolio</a> by hand. For this, I needed knowledge of HTML and CSS, as well as an understanding of how to work with GitHub. Sometimes I think it’s even easier than figuring out a new editor, and it’s free. I designed everything in Figma, then uploaded a screenshot to ChatGPT with a request to break it down into a DOM structure and CSS styles. After that, I simply finished up the layout using a plugin for selecting properties for elements in Figma (it’s much easier to use Dev Mode, but I don’t look for the easy way out). I attached links to my projects, uploaded the code to a GitHub repository, and that’s it — within a week, I had a single-page portfolio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jNWsdpHcvRL2UkMA1Plu5w.png" /><figcaption>AI tools can now generate base code from an uploaded image</figcaption></figure><h3>Step 4. Engaging with teams</h3><p>So, you’ve entered the market and found several teams that interest you. You’ve been scheduled for a meeting with one of them soon — that’s already a big win. Nerves before the conversation are inevitable: new people, uncertainty about where the dialogue will go. To help reduce stress, I always prepare before meeting with a team.</p><p>First of all, I get to know the product and the designers working on it (luckily, I already learned something during the company selection step). Often, it’s enough to find information online about the design director or other team members. I also try to look for any public talks or published materials by the team. This makes answering the question “What do you know about us?” more personal, focusing on the people rather than just the fact that they’ve been on the market for ten years and do such-and-such.</p><p>You’ll definitely be asked about your past experience: what practical tasks you worked on, using case studies as examples; which projects you’re proud of and what you learned from mistakes; why you decided to pursue design and who you follow in the field.</p><p>All these questions can be rehearsed, making your story more structured and coherent. Believe me, there’s nothing more valuable than being able to answer a question clearly, without veering off into other topics for half an hour.</p><p>Prepare your own questions for the team and remember that job searching is a two-way process — you’re choosing people just as much as they’re choosing you.</p><h4><strong>Working on a test assignment</strong></h4><p>This is an evergreen topic of debate: to do or not to do test assignments. The higher the design position you’re applying for, the less likely it is that you’ll be offered a standard test task.</p><p>I don’t believe that test assignments truly demonstrate a designer’s experience, but I do them because they’re a good way to reset your brain and spend a few days working on a new, non-trivial task.</p><p>However, I have one rule — I only do test assignments after meeting the team. Understanding who I’ll be working with makes it easier for me to decide whether I’m ready to invest my time in a test.</p><p>You can discuss the sequence of steps with the recruiter, and if you’re offered a test before meeting the team, you can ask to organize a small meeting to discuss the assignment in more detail and get to know each other.</p><h4>The fear of reaching out first</h4><p>After the meeting, the team usually takes a few days to make a decision. If I don’t hear back after the agreed-upon time, I reach out myself. In a friendly tone, I ask how things are going and if there’s any news.</p><p>Sometimes, silence really does mean that you and the team weren’t a good fit. But there are also times when the recruiter simply forgot. Just imagine how many candidates they’re handling at once — and there are always unexpected events, lunch breaks, feeling unwell, and hundreds of other reasons why you might not get a response. By reaching out, you have nothing to lose. At the very least, you’ll stop tormenting yourself; at best, you’ll show your genuine interest and sincere engagement.</p><p>Looking for a job always feels like an adventure, and there will be moments of low energy and disappointment along the way. The main thing is not to lose faith in yourself and to remember why you’re doing this. I wish you exciting new adventures — and I’ll be starting my own very soon.</p><p><strong>Designers portfolios:</strong></p><ul><li><a href="https://nataliealmosa.ca/">NATALIE ALMOSA</a></li><li><a href="https://www.yihui.work/">Yihui Hu</a></li><li><a href="https://garri.design/">Garri Tonakanyan</a></li><li><a href="https://asekachov.com/">Alexey Sekachov</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xncYki1Pb9CedLAeqg-eTg.png" /><figcaption>Wallpaper</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a2ca7a92b7c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/4-steps-toward-a-product-design-offer-2a2ca7a92b7c">4 steps toward a product design offer</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[Feature owners in design teams]]></title>
            <link>https://medium.com/design-bootcamp/feature-owners-in-design-teams-eefb13bbb65a?source=rss-b138941e1076------2</link>
            <guid isPermaLink="false">https://medium.com/p/eefb13bbb65a</guid>
            <category><![CDATA[team]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Eliza Burenok]]></dc:creator>
            <pubDate>Thu, 22 May 2025 10:56:13 GMT</pubDate>
            <atom:updated>2025-05-22T10:56:13.384Z</atom:updated>
            <content:encoded><![CDATA[<p>Back from a long vacation, and while I’m preparing a piece on interview prep for designers, I wanted to share a quick note on how we motivate our team when we have a lot of mid-level designers, each eager to grow.</p><p>Design career growth is rarely linear. The jump from junior to middle tends to feel more straightforward and transparent than the transition from middle to senior. Different companies define the senior level differently — depending on business goals, the required skill sets vary. But sooner or later, every designer asks themselves: <em>what’s next?</em></p><p>Many companies implement growth frameworks: <a href="https://dmpatterns.com/tools/skillknowledge">competency maps</a>, performance reviews, individual development plans.</p><p>It seems simple — follow step 1, step 2, step 3, and you’re a senior. Sounds great, right? In reality, you might get stuck on step 1, skip step 2, and by step 3 realize the entire plan is outdated. Business priorities may have shifted, the focus might have been solely on the product, or you simply don’t know where or how to apply the skills you’ve picked up.</p><p>So <strong>the transition between levels turns out to be far less clear</strong> than we’d like. This can impact motivation and the overall team atmosphere. While we can’t control everything, we can rely on practical tools and our accumulated experience to help people grow here and now, refining their expertise through real product work.</p><p>One solution that worked well for us: <strong>feature ownership</strong>.</p><h3>Hidden challenges in a designer’s growth path</h3><p>To understand who feature owners are and why they matter, we first need to look at the challenges designers face on their way to becoming senior. Let’s briefly go over the key career transitions for a designer.</p><p><strong>From Junior to Middle</strong></p><p>At this stage, designers build core skills by working on simpler tasks and gradually become more independent. This phase usually takes 2–3 years. During this time, it’s crucial to understand the product, grasp business processes, and start applying knowledge to real problems.</p><p><strong>The Long Middle Stage</strong></p><p>A mid-level designer is already confident with tools and patterns, understands the product and business better, and makes more thoughtful decisions. But this is where many hit a ceiling: the path to senior feels unclear, and the gap between current and required skills can seem too wide.</p><p>Middles typically manage entire product areas and lead tasks end-to-end, though often with support from more senior colleagues. This stage can last 3–5 years, and many lack a clear direction for further growth.</p><p><strong>From Middle to Senior</strong></p><p>Reaching senior means becoming a true expert — someone who can lead projects independently and help others onboard and grow.</p><p>Key skills for moving into a senior role:</p><ul><li>Deep understanding of the product and market (including adjacent solutions)</li><li>Strong design and prototyping skills</li><li>Ability to quickly suggest effective solutions (including conducting design reviews and mentoring others)</li><li>Capacity to quickly dive into new tasks</li><li>Excellent knowledge of the design system and guidelines</li></ul><p>If the team has a lead designer, a senior becomes their right hand and can take over responsibilities when the lead is overloaded.</p><p>In a flat team structure, a senior may act as an informal leader and mentor.</p><p>Now let’s reflect: most design teams have about 4–7 people, including at least one senior and several middles. So here’s the real question — <strong>how can we ensure each middle designer has a clear path to senior?</strong></p><p>Let’s revisit the key senior criteria and see what challenges teams may face:</p><ul><li><strong>Deep product and market understanding — </strong>designers focused on a single product often fall into <a href="https://www.nngroup.com/articles/tunnel-vision-and-selective-attention/">tunnel vision</a>, and their day-to-day workload leaves little time to explore how others solve similar problems.</li><li><strong>Strong design and prototyping skills — </strong>these grow through a variety of tasks — but not every designer gets enough diversity in their workload to build these skills fully.</li><li><strong>Ability to propose strong solutions and support others — </strong>most teams have a dedicated reviewer, so others don’t get to step into this role. Plus, lack of context in other products makes it harder to help effectively.</li><li><strong>Quick onboarding into new tasks — </strong>when a designer is deeply tied to one product, it’s hard to switch and contribute elsewhere — there’s too much missing context.</li><li><strong>Expert knowledge of design systems — </strong>many products reuse the same patterns. To truly master the whole system, a designer needs exposure to different types of tasks.</li></ul><p>One of the lead designer’s core responsibilities is to support growth. But as the team grows, it gets harder to predict how fast and effectively someone will follow a development plan — or whether that plan will stay relevant as the company evolves.</p><h3>How we found a solution</h3><p>Our team has many strong designers looking for new ways to grow. So we decided to run a survey within the team and gather their main requests. Here’s what they mentioned most often:</p><ul><li>Trying to do reviews of other designers’ work</li><li>Diving into related products to better understand how the whole system works</li></ul><p>In addition, our team already had a practice of syncing on the design-patterns we use. I wrote about <a href="https://medium.com/design-bootcamp/why-design-patterns-matter-lessons-from-our-teams-experience-17611c864197"><strong>it</strong></a> last time, so I’ll just give a brief overview here:</p><blockquote>A design-pattern is a common interface principle that helps users complete a task (for example, choosing a payment method or uploading a file). Patterns should be agreed on within the design team, documented, and used across products.</blockquote><p>Over time, discussing patterns <strong>started to feel like mentoring</strong>: if someone had a question, they would go to the person who documented the pattern.</p><p>That’s how the idea came up: <em>what if a designer not only documents a pattern but also</em>:</p><ul><li>Helps review its use in other products</li><li>Explains to the team how to apply it correctly</li></ul><p>After this, we started thinking about how to integrate this practice into our task workflow.</p><p>In total, we ended up with 3 stages:</p><ol><li>Collect and assign patterns among designers</li><li>Create a table of feature owners</li><li>Set up the process of review</li></ol><p>First, we<strong> identified which patterns we already had</strong> in our knowledge base, which were missing, and how to assign them to designers. We held a meeting where each designer brought examples of functional solutions already implemented in their product. We focused on frequency and maturity: it was best if the designer wasn’t using the pattern for the first time and the feature was already live. This way, we could ensure the pattern could be smoothly adopted by other teams, and the designer could answer questions based on experience.</p><p>After the meeting, we <strong>created a table of feature owners</strong> — listing who to contact about each pattern.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AvfFTK7nlC9ww8rOm2pWGQ.png" /><figcaption>An example of a table of features assigned to designers. A screenshot and a brief description are attached for each pattern</figcaption></figure><p>We then <strong>agreed with the team</strong> that reviews could now happen in two formats:</p><ul><li><strong>Feature or user flow review</strong> — to evaluate the entire user journey. Done by the design lead or senior designer, requiring deep expertise.</li><li><strong>Pattern review</strong> — if a designer wants to discuss a specific solution. They create a review task, attach mockups, and the feature owner reviews and comments — either together or asynchronously (for example, directly in Figma).</li></ul><h3>What this approach gave us</h3><p>First, <strong>reviews became faster </strong>— the lead’s workload was shared among the designers. Previously, reviews from the lead could take 2–4 days, now they usually happen the next day after the task is ready.</p><p>Second, <strong>designer engagement increased</strong>. Three months after launching the feature owner practice, we collected feedback from the designers. We wanted to understand who is doing reviews, how often, and if there is any overload considering their product tasks. The team said this practice helped them build connections with other team members they rarely interacted with before due to different tasks.</p><p>Having the chance to develop patterns gave them a sense of involvement and responsibility — they had an area they owned and a visible result of their efforts, which can help during performance reviews.</p><p>Third, <strong>the practice improved knowledge of the design system</strong>. Designers better understood how components work and how to use them.</p><p>This way, we smoothly helped designers prepare for the transition from middle to senior — now they have a clearer idea of what is expected from them and can try senior-level tasks.</p><p>Importantly, feature owners don’t replace the usual competency map but complement it, serving as proof of the designer’s active contributions. There’s no need to recall what someone worked on over the past six months — their work is visible and used by others on the team.</p><p>Currently, this practice runs only within our team, but in the future, we plan to adapt it for other areas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f-HCKH8pHfQKvoSJcjXT-A.png" /><figcaption>Feature owners help other designers to use patterns in their products</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eefb13bbb65a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/feature-owners-in-design-teams-eefb13bbb65a">Feature owners in design teams</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[Why design-patterns matter: lessons from our team’s experience]]></title>
            <link>https://medium.com/design-bootcamp/why-design-patterns-matter-lessons-from-our-teams-experience-17611c864197?source=rss-b138941e1076------2</link>
            <guid isPermaLink="false">https://medium.com/p/17611c864197</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[template]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Eliza Burenok]]></dc:creator>
            <pubDate>Mon, 31 Mar 2025 11:24:22 GMT</pubDate>
            <atom:updated>2025-03-31T11:24:22.110Z</atom:updated>
            <content:encoded><![CDATA[<h3>The hidden cost of unstructured design</h3><p>At the early stages of product development, decisions are made quickly — it’s enough to send someone a message or tweak the implementation directly in production. No long meetings, no approvals from multiple teams, no need to justify every task. Sounds simple, right?</p><p>Unfortunately, over time, these practices lose their effectiveness and turn work into chaos. As the team grows, so does the number of steps required to implement a feature. In large products, inconsistencies and misalignments start to pile up, making it unclear how to fix them. For example, the same UI elements may behave differently, and the tone of voice used might not align with editorial guidelines. Even worse, it’s unclear whom to ask — designers leave the company or simply forget why certain decisions were made.</p><p>As a result, more time is spent clarifying details and making corrections than on actual work.</p><p>During a product’s growth phase, it’s crucial to maintain high quality without sacrificing speed. This becomes much easier when designers have access to an existing pattern wiki and can use the right elements for their solutions. Today, we’ll discuss how to create such a wiki.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jLVaLSSdqeOyXSv27B89mA.png" /><figcaption>Design-patterns are templates used within a product vertical, simplifying <em>the process of choosing how to implement a feature</em></figcaption></figure><h4>How we realized the problem</h4><p>In my design team, there are currently more than 5 people. Each designer is assigned to a product but is also part of the design practice vertical. We develop methods and the common design process.</p><p>At some point, we faced two problems:</p><ol><li>Designers were creating different solutions for scenarios that were reused between products, and users had to relearn how to use the product each time</li><li>There was a lack of understanding of what other products were doing. This made it more difficult for designers to transition between products and prevented them from developing expertise in the processes across different products, which slowed their professional growth</li></ol><p>We approach the implementation of new practices within the team as product tasks. Because of this, the listed problems turned into a hypothesis:</p><blockquote><em>If designers synchronize on implemented solutions, it will speed up feature development and increase their awareness of existing patterns.</em></blockquote><p>The key metrics for testing this hypothesis were Time to Market (TTM) and overall design awareness — how quickly designers can propose a solution to a given task.</p><p>We named the project Design-patterns. To support it, we defined a format, established principles, and launched a pilot.</p><p>Let’s start with the definition.</p><blockquote><strong><em>Design-patterns</em></strong><em> are templates used within a product vertical (a group of products with common goals and users). They simplify the process of choosing how to implement a feature and ensure </em><a href="https://medium.com/design-bootcamp/consistency-in-ux-design-nice-to-have-not-a-must-have-5a0a52bf31f9"><em>consistency</em></a><em> in the user experience.</em></blockquote><p>Design-patters are based on three principles: teamwork, standardization of methods, and prioritization of user needs.</p><p><strong>Examples of design-patterns:</strong></p><p>✅ Searching for the item on a page</p><p>✅ Format for creating a page draft</p><p>✅ Product-specific notification in the descriptor when creating an object</p><p><strong>Not design-patterns:</strong></p><p>❌ Text in the interface — usually, the UX writing team prepares the writing guidelines for the products</p><p>❌ Components architecture — design system is a separate team. A design solution consists of components from the design system but represents a specific part of the user scenario and should be used by multiple teams as a standart</p><h4>When design-patterns can be useful</h4><ul><li>Multiple designers are working on the same or similar products</li><li>Different mechanics are used for similar tasks across the product(s)</li><li>User satisfaction surveys indicate difficulties in learning how to use features</li><li>Designers face the same design challenges but approach them differently</li><li>Feature development takes a long time, and the team struggles to reach a common solution</li><li>Designers rarely synchronize and are unaware of each other’s tasks</li></ul><h3>Pilot and Initial Mistakes</h3><p>We started meeting with a designer from a similar product every two weeks to review which design patterns were being used in ongoing tasks. Our goal was to identify recurring techniques and best practices that aligned with the design system guidelines. By the end of each meeting, we had a finalized pattern that could be integrated into our product.</p><p>Over time, more designers from the team joined these meetings, and that’s when we encountered scaling issues. There were many, but we identified three key challenges:</p><ol><li><strong>Lack of time for the meetings.</strong> We didn’t have a structured agenda, so part of the meeting was spent figuring out what needed discussion. Sometimes, we gathered only to realize there was nothing to talk about and left without any results.</li><li><strong>No clear structure for collected patterns.</strong> They were scattered across different files, making it difficult for newcomers or returning team members to find what they needed.</li><li><strong>Unclear purpose of the meetings.</strong> Designers didn’t fully understand the value of synchronization since existing review and brainstorming sessions already covered feedback on design solutions.</li></ol><p>The new format needed to fully solve at least one of these issues while providing a satisfactory solution for the other two.</p><p>Since we follow the company’s internal design process, we already use various practices, including design critique sessions and reviews. This led us to an important question: <em>What is the primary goal of design patterns?</em></p><p>First, it’s about <strong>standardizing solutions and speeding up development</strong>. Second, it’s about <strong>alignment and synchronization among designers</strong>, allowing them to see their contributions to the knowledge base and grow as professionals.</p><p>In our daily work, we often need to check how similar problems are solved in other products — how the user flow is structured, what components are used, and how many steps it takes. Typically, searching for references involved reaching out to multiple teams and spending a lot of time analyzing different solutions. So, we formulated our goal: <strong>to find solutions faster based on evolving design patterns.</strong></p><p>This raises the question: <em>Why aren’t design patterns managed at the company-wide level?</em> There are two possibilities — either they already exist, or they are still being developed. In our case, they do exist, but they are difficult to apply to niche scenarios. The design system covers general tasks but doesn’t account for specifics, such as warehouse processes or delivery workflows. That’s why we develop local patterns adapted to our users’ needs.</p><p>If your company is just starting to build design patterns, you can take the initiative by identifying universal patterns (such as file export/import or form interactions) applicable across all products, and then adding industry-specific adaptations.</p><p>Design patterns work effectively when designers use a <strong>shared design system</strong> and work on <strong>related products</strong>. This makes it easier to understand task contexts and lowers the entry barrier for newcomers. Our domain includes two product groups: content management (CMS) and client management (CRM). Based on this, we split participants accordingly — CMS designers focus on content-related patterns, while CRM designers work on CRM-specific patterns.</p><p>It was important not only to discuss design patterns but also to document agreements in a clear and accessible way. To achieve this, we divided our syncs into two parts: <strong>discussion and documentation</strong>.</p><p>In the long run, this would become the foundation for a knowledge base within our product vertical — one that could be used not only by designers but also by developers when implementing features.</p><p>Our pilot consisted of weekly meetings for designers, where they discussed active patterns, synchronized on design approaches to functionality, identified best practices, and documented them. We presented the updated format to the design team and launched the pilot meetings.</p><p>And, in true pilot fashion, our ideal vision quickly collided with reality.</p><p>We initially planned weekly meetings, assuming that designers would have enough time to dive into their tasks and create early drafts of patterns. However, in practice, this approach proved ineffective:</p><ul><li>Many tasks didn’t require pattern unification</li><li>There wasn’t enough time to properly prepare documentation</li></ul><p>As a result, we decided to switch to biweekly meetings instead.</p><p>Although the goals of introducing design patterns were clear, there was little motivation to develop them — designers were too busy with product tasks.</p><p>At the same time, many wanted to improve their skills, so we proposed the following approach: <strong>if a designer develops a pattern, they become an expert in its application</strong>. Their knowledge is sufficient to conduct reviews and assist colleagues. For the designer, it’s an opportunity for growth; for us, it’s someone responsible for maintaining and evolving the pattern.</p><p>I’ll share more details about how we organized the process in the next article.</p><p>Our final step was creating documentation templates. Initially, we assumed they weren’t necessary due to individual writing styles, but designers themselves started asking for examples.</p><p>So, we put together a <strong>meeting file</strong> that includes a template for preparing and maintaining pattern documentation. I’ll attach the link at the end of the article — feel free to copy and use it.</p><h3>Revisions and the Final Version</h3><p>It took a long time to refine the format to fit our team. Throughout the process, we actively communicated with designers, identified areas for improvement, and noted what worked well.</p><p>The key here is not to work in isolation — seek feedback from the team and be open to criticism.</p><p>In the end, we established a design pattern workflow, which can be broken down into three steps:</p><ul><li>preparing the file for collaboration</li><li>organizing the meeting</li><li>building the knowledge base</li></ul><h4>Preparing the file for collaboration</h4><p>You can skip the steps if you’re going to use my template.</p><p>Create a new file in Figma — a future space for discussing design solutions with the team and documenting them</p><ol><li>Divide the file into several pages: <br>— 📝 Documentation Template — this is where the master template for creating a new design solution will be placed. When designers need to prepare documentation, it will be enough to simply copy the template and fill it out <br>— 📣 Current for Discussion — a space where the team brings examples for discussing design-patterns<br>— <em>[documented design-pattern] </em>— design-patterns library<br> — Backlog — this is where the entire list of tasks for reviewing design solutions will be stored if there are many</li></ol><h4>Organizing the meeting</h4><ol><li>Create a chat in your work channel or messenger, where you usually communicate with the team</li><li>Schedule a meeting in the team’s work calendar. Describe the goals, frequency, and expected outcomes</li><li>Notify the team in the created chat about the planned meeting. Describe which design solution you want to discuss and attach the link to the “<strong>📣 Current for Discussion” </strong>page. Ask the team to bring examples of how the design-pattern is used in their products in advance</li><li>Gather with the team at the scheduled time</li></ol><h4>How the meeting will go:</h4><ol><li>Designer immersion in the task <a href="https://uxdesign.cc/stop-solving-product-problems-start-solving-customer-problems-6c9cf3e28db3">context</a> (10–15 min). Explain the user flow. Clarify the input data and constraints, the current status of the work, and how you plan to solve the problem</li><li>Each designer then presents their examples of using the design-pattern, preferably including counterexamples</li><li>Synchronization on usage: Similar and different examples. Highlight best practices</li><li>Summarizing: Clarify the time needed for documentation and assign the preparation of documentation to the designer</li><li>After the meeting, create a page for documenting the design-pattern. Transfer all artifacts from <strong>“📣 Current for Discussion”</strong> to the new page</li></ol><h4>Building the knowledge base</h4><p>It doesn’t have to take a lot of time to document the design-pattern. Actually you can use the template during the meeting and fill it during the discussion. After that you only have to highlight the best practices and organize examples from products.</p><ol><li>For the created page for documentation, set the status as <strong>⏳ [design-pattern number] — [design-pattern name] — [date]</strong></li><li>Your template might vary, i prefer including into it: general information about the design-pattern; details of interaction; scenarios; dos and don’ts and examples with the links to the product scenarios</li><li>Describe design-pattern and all interaction specifics using your artifacts from meeting</li><li>If the task requires editing, involve a UX writer. Agree with them on the correct text</li><li>Add a couple of dos and don’ts of how the design-pattern is used</li><li>Once the documentation is ready, move the task to review with the design-pattern moderator in the team</li><li>After the review is done, change the status from ⏳ to ✅</li></ol><h4>Summing up</h4><p>Creating a knowledge base for design-patterns is a collaborative effort. In addition to synchronizing and keeping the library up to date, it’s important to ensure that the design-patterns are integrated into the products. Don’t forget to gather feedback from the teams.</p><p>In the future, design patterns can be integrated into other company processes. For example, they can be included in new employee onboarding to simplify familiarization with the product and design system.</p><p>Additionally, design patterns can be used for team demos, allowing teams to share and discover new and innovative solutions.</p><p><a href="https://www.figma.com/design/6I0W5EWiZ9NtGm6fKhHWTW/Design-patterns?m=auto&amp;t=oo9Qs1VSzj6KWoNf-6">Link</a> to the template</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ICKQUj98HGl7mpowXxcAww.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17611c864197" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/why-design-patterns-matter-lessons-from-our-teams-experience-17611c864197">Why design-patterns matter: lessons from our team’s experience</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[Stop thinking, start doing: how a conceptual model helps the team to build a product]]></title>
            <link>https://medium.com/design-bootcamp/stop-thinking-start-doing-how-a-conceptual-model-helps-the-team-to-build-a-product-fa0c84dcf5bf?source=rss-b138941e1076------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa0c84dcf5bf</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[team-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Eliza Burenok]]></dc:creator>
            <pubDate>Wed, 05 Mar 2025 14:04:52 GMT</pubDate>
            <atom:updated>2025-03-11T05:19:32.458Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why is it hard to turn ideas into actionable solutions?</h3><p>Recently, I did the math: over two years of working on the product, our team launched five projects. Some were more extensive than others, but none of them could be called simple. Every new beginning comes with the fear of a blank page, and when you add deadlines and the responsibility to your team, the stakes get even higher.</p><p>Every designer strives to do their job well: to design a complete user flow, anticipate edge cases, create a seamless experience, account for technical limitations, and meet deadlines. And don’t get me wrong — everyone on the team has their own responsibilities. But the designer’s role is to connect and bring to life the vision of both the business and the user, which is why they are among the first to step into the game at the start of a project. This naturally raises the question: where do you begin? How do you break down a product early on? How do you establish a system of interconnected components? How do you turn a scattered set of features into a comprehensive solution for the user’s problem?</p><p>There are plenty of resources on breaking down a task, but most focus on defining project <a href="https://www.indeed.com/career-advice/career-development/product-manager-goals">goals</a>, validating <a href="https://www.nngroup.com/videos/checking-guessing-ux-slogan/">hypotheses</a>, determining product value, and identifying <a href="https://www.nobledesktop.com/learn/digital-marketing/understanding-consumer-pain-points-in-product-development">user needs</a>. What I want to talk about is: what’s next? Once we’ve done all that, how do we shape the knowledge we’ve gathered? How do we move beyond compiling text documents and start designing?</p><p>Today, let’s talk about the <strong>conceptual model</strong>. I’ve gathered my thoughts and structured our approach to design using best practices. A conceptual model is universal — it works for designers, product managers, and developers alike. In essence, it’s no different from familiar design mockups. Its power lies in how quickly it provides a foundation to work from, allowing you to move from a broad idea to specific, measurable tasks in no time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mOGiTkwsfyrvK7r6QkkHHQ.png" /><figcaption>Conceptual model helps you to bring your knowledge of the opportunity to life</figcaption></figure><h3>Three issues with the “design first, development later” approach</h3><p>Here’s how we typically see the process: a designer receives a task, conducts research (hopefully), and creates a design based on it. Now, let’s imagine this isn’t just a small feature but a full-fledged flow that involves designing a new mechanic from scratch. While the designer is working on the design, the development team is essentially blocked. Without mockups, it’s unclear what to do next. So, the team has to wait for the designer’s solution, discuss it together, make adjustments if necessary, and only then move forward with development.</p><p>Now, let’s think about the downsides of this approach.</p><p>First, <strong>the time required to release a feature doubles</strong>. Development can’t properly begin until the design is finalized. During design discussions, missing requirements and process gaps may arise, so everyone waits for a final decision to avoid wasted work. For the designer, this means having to deliver a large volume of work all at once — ideally in a way that won’t require major revisions later.</p><p>Second, <strong>the team lacks a shared understanding of the product</strong>. As a result, tasks and requests are handled without clear prioritization — if something exists, it must be important. This leads to constant context switching: today you’re working on [X], tomorrow on [Y]. But how do these tasks contribute to the overall product vision? That remains unclear.</p><p>This brings us to the third problem: <strong>without seeing the bigger picture, it’s difficult to build strong connections</strong> within the system. In the end, parts of the product might turn out to be completely disconnected, or gaps in design may emerge. With this approach, scaling the product becomes challenging — there are simply too many unanswered questions. It’s like trying to dig a tunnel without knowing where you are on the map.</p><p>I won’t go into solutions for each of these problems using the conceptual model just yet. Instead, let’s look at how this works through a case study — and at the end, we’ll check whether the conceptual model helped address these three issues.</p><h3>The relationship between complexity levels and the model</h3><p>Before moving forward, it’s important to define what a <strong>conceptual model</strong> is.</p><p>Let’s start with the basics:</p><ul><li><strong>Concept</strong> — an idea or vision that helps shape or guide the direction of development</li><li><strong>Model</strong> — a simplified representation of a real object, created to better understand and improve it</li></ul><p>In other words, a <strong>conceptual model</strong> is an idea translated into a tangible, working material. But we can put it even more simply: a conceptual model helps map the path from point <strong>A</strong> to point <strong>B</strong> — from understanding the problem to finding a way to solve it.</p><p>Let’s pause here for a moment.</p><h3>What do we mean by a “problem”?</h3><p>Problems come in different forms and levels of complexity. We often talk about <strong>user problems</strong>, but in reality, the team first needs to solve many implementation challenges to ensure the final solution actually reaches the user.</p><p>To assess problems, there is a framework called <a href="https://www.nngroup.com/articles/complex-application-design-framework/?source=post_page-----5476acf184c5---------------------------------------">Application Complexity</a>, which identifies five types of complexity in product development. In this article, we’ll focus on three of them: <strong>Integration, Intention, and Information</strong>.</p><ul><li><strong>Integration</strong> — <strong>a system-level problem</strong>. This is common in projects that require integrating multiple architectures and platforms into a single system with a unified user-facing interface.</li><li><strong>Intention</strong> — <strong>a prioritization problem</strong>. Why does the user come to your product in the first place? What are their primary goals, and in what order do they complete them? Early in the design process, the team should focus on a well-defined scenario for a specific user segment before expanding and enriching it with additional use cases.</li><li><strong>Information</strong> — <strong>a data accessibility problem</strong>. What kind of data will the user interact with? Can we provide all the necessary information? The interface acts as a bridge between the user and the system, and the type and volume of data you structure will shape the product’s development path.</li></ul><p>By identifying the type of problem, it becomes easier to <a href="https://arc.net/l/quote/pwwamxpz">determine</a> the <strong>focus of the model</strong> and establish <strong>clear criteria</strong> for evaluating its success.</p><h3>Designing the conceptual model</h3><p>So, we’ve established that you can start working on a conceptual model once you have enough data <a href="https://medium.com/design-bootcamp/models-in-design-71925b3e746c">to explore solution options</a> based on it.</p><p>A conceptual model consists of three key components:</p><ul><li>solution architecture</li><li>user interaction elements</li><li>expected outcome</li></ul><p>It also has the following success criteria:</p><ul><li>focused on user tasks</li><li>clear and intuitive for users</li><li>reflects internal system connections</li><li>understandable for all team members</li><li>adheres to agreed-upon terminology</li><li>easily adjustable</li></ul><h3>The process of developing a conceptual model</h3><p>The entire workflow can be broken down into four stages:</p><ol><li><strong>preparation</strong> (gathering research insights and defining the task)</li><li><strong>design</strong> (creating of the conceptual model)</li><li><strong>discussion</strong> (design critique session with the team)</li><li><strong>decomposition</strong> (breaking the model down into actionable tasks)</li></ol><h3>Preparation</h3><p>As mentioned earlier, a conceptual model <strong>bridges the understanding of the problem with the first steps toward solving it</strong>. I won’t go into detail about the research process here — that’s a topic for another time. Let’s assume the <strong>discovery phase</strong> has already been completed.</p><p>To get started, you can use various artifacts, such as:</p><ul><li>user personas</li><li>object models</li><li>information architecture</li><li>wireframes</li><li>user story maps</li><li>solution boundaries</li><li>prioritization of key tasks</li><li>UML diagrams</li><li>task flows</li></ul><p>A conceptual model is a design task. If your team uses Jira or a similar project management tool, create a task for the conceptual model (or ask your manager to do so). The outcome should be a comprehensive document about the product, including the conceptual model and its corresponding decomposed epics.</p><p>In our workflow, the design task is created by the manager and filled out by the analyst. It typically includes:</p><ul><li>goals</li><li>context &amp; assumptions</li><li>hypotheses</li><li>metrics &amp; constraints</li><li>research findings &amp; business requirements</li></ul><p>Before starting the task, I hold a <strong>kick-off meeting</strong> with the discovery team to align on requirements and clarify any questions. Only after that do I move on to designing the conceptual model.</p><h3>Design</h3><p>For the start, knowledge of the <strong>target user scenario</strong> (job story), <strong>process****maps</strong>, and <strong>technical constraints</strong> (if we are involving neighboring teams) is sufficient. The conceptual model should be built starting from the most frequent scenario for one role with the maximum data set per screen. It is better to lay out more and remove later, than to miss important elements. By default, the product contains a set of concepts that are interconnected but do not necessarily form a cohesive whole. The designer’s task is to identify the essence of the concepts and their interrelations.</p><p>For clarity, I’ve chosen the scenario of finding an ad for a transaction between the user and the exchanger. Let’s write the job story:</p><p><em>When I need to send money to my family, I need to find an exchanger to make the transaction</em></p><p>For this task, the primary scenario will include searching for and choosing an exchanger (presumably based on certain parameters), creating a request, and sending it.</p><p>I start designing with the <strong>user’s task flow</strong>, where I lay out their interaction with the system into three types: user intent (general block), the actual user action (what they specifically do in the block step-by-step), and system response (what happens when the user performs the action). The task flow considers user needs — what are their motivations, and how can we serve them?</p><p>In the task flow, I record which scenarios I will build from it later — alternative, additional, and negative cases. I don’t detail them at this point, just note them down to refine later after the model is agreed upon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eWgd6txMa-YXryayd-5TGQ.png" /><figcaption>The user task flow for creating an ad contains the main scenario, broken down into 3 steps: entering parameters, searching, and selecting an exchanger</figcaption></figure><p>Next, on this diagram, I highlight <strong>objects</strong>. These are usually nouns that the user interacts with within the scenario. I collect all the objects into a relationship model and detail them for each data set, consulting with a system analyst. The object model can later be used for navigation in your product.</p><p>In our example, objects would include: exchanger, ad, and the transaction form.</p><p>Once the task flow is ready, we review it with the business analyst to identify any grey areas in the scenario and ensure business requirements are met. There may be revisions of some parts of the scenario or its additions. Any questions that arise are divided into two groups: those for the users (if we don’t know how their process is structured or how they are used to working) and those for the product team (if we don’t know how our idea will be implemented).</p><p>After discussing the task flow, I proceed to design the conceptual model on mockups. I usually work with no more than five screens for the scenario, focusing on displaying the most complex data: tables, forms, tree structures, etc. If your company has a design system, you can build the mockups directly on it to avoid redoing later. I typically skip wireframes and use ready-made components, as they already include behavior and logic, leaving me only to assemble the mockup. When the scenario is ready, we discuss it again with the analyst to ensure we are on the same page when meeting with the product team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fht5z5fPlI_BW-SoNdMj7w.png" /><figcaption>The conceptual model, based on the task flow, includes the 3 listed steps and reflects the complete set of data</figcaption></figure><p>It’s important to note that each stage can be iterative. While working on the conceptual model, I continuously gather best practices from other teams and look at external resources. The object model, like the task flow, may become simplified or enriched after each discussion.</p><h3>Discussion</h3><p>The work on the conceptual model takes no more than two days, and then we meet with the team to discuss the solution in more detail. I’ve mentioned the <a href="https://medium.com/design-bootcamp/mastering-design-critique-with-a-product-team-why-it-matters-and-how-to-do-it-well-1148a9092ac7">format</a> earlier, and I will just emphasize that the goal of the meeting is to <strong>give an objective evaluation of the feasibility of implementation by various team members</strong>. Therefore, it’s important for everyone to speak up: developers, product managers, analysts, testers.</p><p>The meeting is divided into two parts: a briefing on business requirements and a presentation of the conceptual model by the designer. After each block, the team asks questions.</p><p>In the problems section at the start of the project, I mentioned that team members are blocked by the design. Let’s look at an example of the conceptual model to see what can already be handed off to the team for further work:</p><p><strong>System analysis:</strong></p><ul><li>algorithm for selecting exchange services based on the entered data</li><li>possible transfer restrictions (regulatory, internal)</li><li>current exchange rates at the time of request</li><li>API endpoints for retrieving the list of ads, banks, exchange services, and exchange rates</li><li>data format from the server (JSON, GraphQL, etc.)</li></ul><p><strong>Backend:</strong></p><ul><li>retrieving a list of exchange services based on parameters</li><li>fetching the current exchange rate for the selected currencies</li><li>generating a request to create an order with the selected exchange service and specified amount</li><li>creating of the order</li></ul><p><strong>Frontend:</strong></p><ul><li>structure of an ad card (which fields are received and how to display them)</li><li>data display logic (grid, list, pagination, infinite scroll)</li><li>filters (sending country, receiving country, amount, bank, exchange service)</li><li>sorting (by exchange rate, commission, speed, popularity)</li><li>data updates (refetch, auto-refresh of exchange rates, notifications about rate changes)</li><li>error handling (no exchange services found, no connection, expired exchange rate)</li></ul><p>It is often the case that after the meeting, I leave to refine the model, but this helps to detail the process and immediately set up boundaries for the scenarios. The “analysis, design, and discussion” cycle repeats until the solution is agreed upon by all parties. But there’s no need to be scared of this, as in most cases it involves non-critical refinements, so other team members can continue their research in their area and high-level design based on your model. Their tasks are also created during the meeting and then transferred to Jira and attached to the conceptual model.</p><h3>Decomposition</h3><p>The resulting conceptual model provides a set of necessary functions for the user, which are divided into epics with tasks for all team members. Refer to the model when allocating resources and setting deadlines. They are unlikely to be 100% accurate, but at least the team will have one source to refer to.</p><h3>Challenges you may encounter when working with the model</h3><p>The first attempts at working with a conceptual model take time and require practice. It may not be possible to immediately create a satisfactory architecture, identify objects with relationships, and align them with the team. But over time, you will learn to identify important principles and validate feedback from colleagues. I’ve put together a small list of potential challenges you may face while working on the model:</p><ul><li><strong>incomplete or inaccurate requirements</strong>: you might not have gathered enough data from users, or you may have overlooked the business scenario or involved stakeholders. During the design phase, it’s not necessary to dive into details, but the further you progress, the more important it becomes to have a complete picture of how processes interact.</li><li><strong>difficulty in identifying objects</strong>: initially, it may seem that any entity can be considered an object, or conversely, the entire system may appear to be just a set of features that are hard to call objects. Try to work with a mental model of users and continuously prioritize: which entity is more important for the user in this scenario/this task?</li><li><strong>discrepancy between the model and implementation</strong>: it’s important to remember that the model sets the direction for the product and helps make the initial leap. However, tasks like building architecture, navigation, and other complex modules don’t go away with the model. And often, specific features may intentionally contradict the model, or vice versa. Don’t be afraid of this or rush to redo everything.</li><li><strong>unforeseen complications</strong>: many designers get caught up in the details, especially in the beginning. But it’s important to remember that working on the model shouldn’t take more time than if you had started with the features.</li></ul><p>Let’s recall the problems the team faces at the start of a project:</p><ul><li>long development time</li><li>no shared understanding of the product</li><li>inconsistency of developed features</li></ul><h3>Long-development time</h3><p>The conceptual model lowers the entry barrier for all team members. The designer and analyst/product manager immediately begin working on user scenarios, and based on these, the development team lays out the main system modules and plans integrations with other teams. Working in parallel helps identify issues and missed cases faster than a sequential approach, where the design is created first, followed by development.</p><h3>No shared understanding of the product</h3><p>Usually, the designer and product manager/analyst conduct research into the problem space and then move on to developing specific features. However, before that, time needs to be spent aligning on the functions or terminology. The conceptual model accumulates everything you know about the task and presents it in a format that is easy for others to read. The team looks at the same mockups, which allows them to approach the discussion of tasks more constructively.</p><h3>Inconsistency of developed features</h3><p>When working on a task, it’s hard to avoid tunnel vision — there are too many details to account for in order not to miss anything. Scaling the product under such conditions is extremely difficult because you don’t know what will happen further down the line. A well-developed conceptual model at the early stages helps identify potential problems (such as contradictions in the system’s logic) before they become costly to fix.</p><p>Instead of drawing a conclusion, I would like to leave the ending open: the conceptual model, like any tool, is effective only when used. It evolves alongside the team. Therefore, there is still much to be said about this method. I hope you found something useful, thank you for your time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa0c84dcf5bf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/stop-thinking-start-doing-how-a-conceptual-model-helps-the-team-to-build-a-product-fa0c84dcf5bf">Stop thinking, start doing: how a conceptual model helps the team to build a product</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[Mastering design critique with a product team: why it matters and how to do it well]]></title>
            <link>https://medium.com/design-bootcamp/mastering-design-critique-with-a-product-team-why-it-matters-and-how-to-do-it-well-1148a9092ac7?source=rss-b138941e1076------2</link>
            <guid isPermaLink="false">https://medium.com/p/1148a9092ac7</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[team-management]]></category>
            <category><![CDATA[desıgn]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Eliza Burenok]]></dc:creator>
            <pubDate>Tue, 18 Feb 2025 09:45:23 GMT</pubDate>
            <atom:updated>2025-03-11T05:20:55.784Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Thoughtful design critique </strong>helps improve product quality</h4><p>What comes to your mind when you hear “design critique”? The meeting is halfway through, silence fills the room, and the presenter looks at their colleagues with hope, waiting for any kind of feedback. Or, on the contrary, the meeting has barely started, yet you’re already bombarded with questions, critiques about the shade of the blue button, and comments that everything still looks raw.</p><p>For some, the word “critique” itself is enough to send chills down their spine, making them want to get it over with as quickly as possible.</p><p>At the same time, it’s no secret that building a product is impossible without communication. Every detail matters — thoughtful user flows, page load speed, and how the interface communicates with people. Remove one leg from a stool, and it collapses. So where does the real problem lie?</p><p>Design consists of two key practices: an active phase — <strong>creation</strong>, and an analytical phase — <strong>reflection</strong>. Most teams have learned to be creative, but it seems they haven’t fully figured out how to validate their work.</p><p>Communication, like any other skill, requires learning. It’s a deliberate process that demands both analytical abilities (to process incoming feedback) and soft skills. Over the past few years, designers have developed a strong <a href="https://borism.medium.com/design-critique-culture-b7350baab11c">culture</a> of discussion, but communication with the product team is still inconsistent and not as effective as it could be.</p><p>But how can you take responsibility for a product’s quality without effective communication? A designer’s job isn’t just to create an interface but to ensure it can be successfully implemented. The final user experience depends as much on the designer as it does on the development team. A well-designed product can save backend developers from making excessive requests every 15 seconds and allow frontend developers to implement the design without unnecessary workarounds. And that’s just a simple example. From concept to execution, countless challenges arise, and only through collaboration can teams overcome them and build a product they can be proud of.</p><p>In this article, I will highlight the importance of regular design critique sessions for successful product development and explain how to conduct them with the team. While there’s no universal formula for a perfect design critique, there are several techniques that help structure the process and ensure each meeting leads to measurable outcomes. That’s what we’ll discuss.</p><p>The methods I describe will primarily benefit product designers, but I hope they’ll also be useful for design leads, product managers, and other specialists.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1HyAcyg7F2bi_VbyEi-hqQ.png" /><figcaption>Design critique is based on several iterations with the team and collaborative work</figcaption></figure><h3>Types of design critique and how they differ from other formats</h3><p>Design critique has two key aspects: <strong>practical</strong> and <strong>visionary</strong>.</p><ul><li><strong>Practical</strong> — focused on solving a defined problem. There are clear requirements based on prior research, and your goal is to develop a solution that meets these criteria</li><li><strong>Visionary</strong> — focused on exploring opportunities within a problem space. Neither you nor your team may know what exactly constitutes a “solution” or even a “problem” yet. Your goal is to define the scope of the challenge</li></ul><p>You might be wondering, <em>“How is design critique different from a review?”</em> Let’s break it down.</p><ul><li><strong>Design review</strong> — A meeting with a design lead or the person responsible for the design system to ensure the solution aligns with company/product guidelines and patterns. The goal is to bring the design in line with established formats and maintain consistency</li><li><strong>Design critique with developers</strong> — A session to assess the quality of the design and anticipate potential implementation challenges. The goal is to ensure the design solution is feasible</li><li><strong>Design critique with designers</strong> — A peer-to-peer exchange with fellow designers. The goal is to gain fresh perspectives on your work and find ways to improve the solution</li></ul><h3>Why design critique sessions matter</h3><p>Design critique benefits both you (the designer) and the team. It helps refine your work early on, reducing the need for later revisions.</p><p>By the time designs go into development, you’re often already working on something else. <strong>Going back to tweak details takes time and disrupts your current focus</strong>. Small fixes are one thing, but what if a core issue arises? Imagine that during development, you realize the logic behind <strong>Task A</strong> doesn’t work, forcing you to rethink the entire flow. This not only delays <strong>Task A</strong> but also pushes back <strong>Task B</strong>, affecting the whole product timeline.</p><p><strong>Design critique sessions are essential for the development team</strong>: frontend and backend developers, and analysts. It’s problematic when the task is only understood at the start of the work. Time is spent on clarifying conditions and solving problems instead of actual development.</p><p>For the team,<strong> design critique is an opportunity to collaborate, complementing each other’s expertise</strong>. Through synchronization, you find unexpected solutions — this is from my own experience. During the process, you learn to listen, argue your point of view, and find the best approaches given the existing constraints.</p><p><strong>Design critique elevates the value of design within the company</strong>. The team sees the entire process and realizes it’s more than just designing buttons. Together, you resolve disagreements, improve solutions iteratively, discuss architecture, and identify vulnerabilities. This helps you grow as a professional — explaining the task helps you understand it better. The difference between a junior and senior designer is the ability to justify your choices.</p><p>However, it’s important to note: <strong>design critique is not a review and not an approval of the design</strong>. You don’t bring your work to get it approved by the development team. You come to the meeting to explore the task from different perspectives and consider all the details.</p><h3>Barriers to holding design critique sessions</h3><p>If design critique has so many benefits, why do so few people use it in their work or try to avoid it? There are a few reasons, which Peter Merholz described well in his <a href="https://www.petermerholz.com/blog/critique-is-not-review-and-many-other-thoughts-on-an-overlooked-practice/">article</a>. I will try to summarize them. There are three main reasons:</p><ul><li>Lack of understanding of the format</li><li>Fear of speaking up incorrectly</li><li>Uncertainty about when to seek critique</li></ul><h4>Lack of understanding of what design critique is</h4><p>This one is simple — neither designers nor teams know the format. Or, perhaps they’ve heard of it, but don’t understand how to apply it in practice.</p><p>This issue is common in asynchronous teams, where everyone is focused on their own work and not particularly interested in what others are doing.</p><p>Here, the team leader’s vision (which could be a design lead or senior designer) can help. He can explain the value of the practice, show how to implement it, and provide guidance to the teams.</p><h4>Fear of speaking up</h4><p>The word “critique” can have a negative connotation. Unfortunately, some team processes suffer from excessive formalism, where each employee is solely focused on delivering results. How they get there isn’t as important; the faster, the better — preferably yesterday. People don’t feel safe expressing opinions or asking for advice. In such teams, discussing mistakes is feared, as it might seem unprofessional. The design lead should address this situation through 1:1 meetings with designers and take steps to create a healthy team environment.</p><p>It would be great if design leaders or senior designers also participated in design critiques and invited other teams. This would show junior designers that even experienced professionals can doubt, make mistakes, and not get everything perfect on the first try. Furthermore, it would help them stop fearing to share their opinions, thinking their experience is insufficient. <strong>Great solutions come from exchanging ideas, and every contribution matters as long as there is respect and trust within the team</strong>.</p><p>Think back to how you learned to dive into water or ride a bike. It’s easier when someone who knows how to do it is there first. If no one in your team dares to bring a task for discussion or voice their opinion, take the first step. Junior designers can learn not only how to participate in the discussion but also pick up interesting solutions for their own tasks by observing others.</p><h4>Uncertainty about when to seek critique</h4><p>This point is similar to the first, but here, it’s unclear what material is needed for a design critique. This is an ongoing debate: should you hold a meeting once the mockups are ready, or should you gather the team when the designer receives the business requirements?</p><p>I’d be lying if I said the design process should have a set time for holding design critiques, and meetings should only happen when that time is on the schedule. <strong>Hold meetings when you know enough about the task to discuss it with others, but before the finished task is handed off.</strong></p><p>And don’t limit yourself to mockups. Discussions can happen with user flows, wireframes, or a priority guide. Everything listed here is just a tool to initiate dialogue, not a replacement for it.</p><p>In my opinion, the best time for meetings is the second or third day after a designer takes on the task in discovery. By then, it’s possible to discuss the concept with the business side and have artifacts to bring the development team into the conversation.</p><h3>How teams typically run design critique sessions</h3><p>I’ve come to the conclusion that the critique format can vary depending on the scope of the task.</p><p>If a single scenario or feature is brought to the design critique session, you can try using a <a href="https://uxdesign.cc/the-framework-you-need-to-run-a-successful-design-critique-session-is-here-8eb5c7535e48">matrix</a> structure. It also works well for discussing conceptual models. My team took this further and slightly adjusted this framework to fit our needs — most often, we need to review multiple interconnected scenarios. So, we found it more effective not to separate comments into different blocks but to have a unified discussion about the presented solution.</p><p>There are three main stages:</p><ul><li>Preparation</li><li>Running the meeting</li><li>Summing up and next steps</li></ul><h4>Preparation</h4><p>The key to an effective design critique session is preparation. The meeting is allotted a fixed amount of time, and as the facilitator, you need to stay organized. This is only possible if you know how to guide the discussion.</p><p>In reality, preparation starts as soon as you begin working on the task. As a designer, when you start with the business requirements, you formulate conceptual questions like: “What happens if the user…”; “How will we highlight to the user that…”; “How are two objects connected…”; and so on. Then, you prepare draft artifacts: models, diagrams, or scenarios.</p><p>Some of these questions may be resolved in the kick-off meeting with the product manager/analyst, while others will require input from other specialists.</p><p>Before the design critique session, we usually have a few meetings with the analyst, where we review my initial drafts of the scenarios and gather a list of questions for the development team.</p><p>I typically create a section in Figma and transfer the questions onto sticky notes, which I update during the meeting. Meanwhile, the analyst creates a table of questions in Confluence, which later serves as a reference when writing the full documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qnyaj5Q8cl2_bs-U9rW-aQ.png" /><figcaption>Examples of questions from the discovery team for a design critique session</figcaption></figure><p>Here are some example questions:</p><ul><li>Is publishing considered a change to the page?</li><li>Can we create a general search for parameters like name and type?</li><li>Is a notification feasible on first open?</li></ul><p>It’s best to send the meeting topic and prepared materials with questions to the team ahead of time, so everyone has a chance to review them and won’t waste time getting up to speed during the meeting.</p><h4>Conducting the meeting</h4><p>Creative sessions or presentations are typically conducted by one person. However, when discussing a complex task, I would recommend finding a partner. It’s difficult to be a moderator, answer questions, and take notes all at once. If your team includes an analyst or product manager, share the meeting responsibilities with them.</p><p>📌 The estimated time for the session is <strong>1</strong> <strong>hour</strong></p><p>📌 The team composition includes: designer, analysts, product manager, frontend developers, backend developers, and testers</p><p>At the beginning of the meeting, the analyst takes <strong>10–15 minutes to brief the team</strong>. He explains the business goals, task value, describes the target audience and use cases, and dives into the DoR.<br>Once the briefing is done and the team has asked any clarifying questions, the role of the facilitator shifts to the designer. The designer explains the main scenarios using collected artifacts (task flow or flow chart). During this time, the analyst can note any questions raised by the team to address them later.</p><p><strong>If you’re still unsure about which design artifact is best for the critique</strong> session, here’s a small cheat sheet:</p><p>✔️ If you’re just starting to work on the task and this is the first design critique session with the team, a<strong> low-detail conceptual model</strong> on the primary scenario will suffice. The text can be a draft or even absent.</p><p>✔️ If this is the second or third session with the team, and you’ve already defined the main functional principles and high-level architecture, structure the meeting around the <strong>task flow hierarchy: primary, secondary, and negative scenarios</strong>. The level of detail should be high, and the text should be close to the final version. If you have a design system, now is the time to use it to ensure it covers all cases. If any components are missing, make a request before preparing the final design for handoff to development.</p><p>✔️ If several design sessions have already been held and you’ve addressed all the details in team discussions, present all<strong> task flows gathered in the design system with the finalized text in the interface</strong> for the final meeting.<br>Clarify to the team at the start where your design stands, and categorize the incoming questions into: solve now; can be postponed.</p><p>Peter <a href="https://www.petermerholz.com/blog/critique-is-not-review-and-many-other-thoughts-on-an-overlooked-practice/">described</a> what constitutes proper and undesirable criticism. This can be helpful for your team during the meeting.</p><h4>Feedback Don’ts</h4><ul><li>Do not provide “preference” based feedback (“I like…”)</li><li>Do not offer solutions in the feedback (“Move this to the right”)</li><li>Make assumptions — if you’re not sure about something, ask a clarifying question</li></ul><h4>Feedback Do’s</h4><ul><li>Connect comments to objectives or design standards</li><li>Bring a perspective (either yours, or a persona’s)</li><li>Point out (what seems to be) the obvious — it may not be so to others</li><li>Indicate your level of severity. For example, the emoji model suggested by the Giving Feedback article:<br> 🟥 a red square means that it’s something potentially worth blocking<br> 🔶 a yellow diamond is something where one can be convinced otherwise, but it seems to that it should be changed<br> 🟢 a green circle is a positive confirmation.<br> 🌀 a blue spiral is for either something that uncertain, an exploration, an open alternative, or just a note.</li></ul><h4>Summarizing and next steps</h4><p>Once you’ve covered all the prepared materials, the team may ask questions. If you don’t have answers to some, record them in a convenient way: comments in Figma, sticky notes, or directly on the mockups. These will become the key questions for the next meeting.</p><p>Present your questions that you prepared for the session to the team and make sure to capture all the answers. I usually categorize them into 3 types: <strong>can be implemented</strong> (green), <strong>cannot be implemented</strong> (red), <strong>needs clarification/requires revision</strong> (blue). This color-coding helps break the section into meaningful zones and simplifies future work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*md1_8ALKupb2NDf2w_aMUw.png" /><figcaption>Here is an example of a board filled with questions after a design critique session</figcaption></figure><p>If, during the design discussion, the team suggests making changes, avoid rushing into it right away. Take a pause after the meeting to analyze and make decisions later.</p><p>📌 By the end of the meeting, <strong>determine which scenarios need further work and which can be prepared for handoff to development</strong>. For large tasks, having several sessions is normal. For smaller features, two sessions are enough: in the second session, you present the final version to make sure all cases were considered with the team.</p><p>You can create a to-do list based on the questions and answers discussed during the session. The analyst can take responsibility for questions related to clarifying business requirements or seeking expertise from another team, while you continue working on the mockups.</p><p>As I mentioned earlier, there is no one-size-fits-all formula for conducting a successful design critique. It is largely the result of several iterations with the team and collaborative work. Each participant should have deep expertise, possess empathy and communication skills, as well as the ability to express their viewpoint clearly. The initiator, in turn, should facilitate the meeting and answer the team’s questions, guiding the discussion in a constructive direction. It’s important that the process is transparent, and all participants feel that their opinions are valued, with criticism helping to improve the final product. Regular design critiques not only improve the quality of work but also strengthen collaboration within the team, which in turn increases the overall efficiency of project work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1148a9092ac7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/mastering-design-critique-with-a-product-team-why-it-matters-and-how-to-do-it-well-1148a9092ac7">Mastering design critique with a product team: why it matters and how to do it well</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[Design principle — variability]]></title>
            <link>https://medium.com/@burenok.eliza/design-principle-variability-ecdd2081230b?source=rss-b138941e1076------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecdd2081230b</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[system-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Eliza Burenok]]></dc:creator>
            <pubDate>Sun, 26 Jan 2025 10:01:21 GMT</pubDate>
            <atom:updated>2025-03-11T05:25:34.931Z</atom:updated>
            <content:encoded><![CDATA[<p>When designing the product, we aim to primarily cover the target user scenarios. Over time, the product&#39;s functionality expands: new user segments are added, the number of tasks covered grows, and the business itself evolves. The designer faces the challenge of scaling. How can functionality be added to the product without breaking its structure?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oW6FOiNPQ6Shn6XHXC0SUw.png" /></figure><p>While it’s impossible to create a universal product, there are a few techniques to increase its variability:</p><ol><li>Status model</li><li>Differentiation</li><li>Role model</li></ol><p>I’ll break down the techniques using the example of a product for creating various types of content: media, long reads, banners, and so on.</p><h4>Status model</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z1HDXDlLT25KIs4GIG6Gyw.png" /><figcaption>Status model for a content page</figcaption></figure><p>Provides different page behavior and states depending on the stage of the content workflow. The fewer statuses you use in a product, the better. Designers often mistake attributes for statuses. The difference is that a status represents a change in an object’s state, while an attribute adds a parameter. Statuses are typically used to show that a user action is completed, has caused an error, or is being processed.</p><p>In my experience, the status model is one of the most complex parts of product design. If it’s done poorly at the start, it’s hard to fix later because all processes will depend on it. Also, within a product group, all processes usually follow the same status model, which makes changing it even more difficult.</p><p>On the other hand, properly designed status model reduces the amount of data stored in the database and optimizes content loading.</p><h4><strong>Differentiation of user groups</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gn8FMAqx578vwXPdrGHWOQ.png" /><figcaption>Different segmets of users</figcaption></figure><p>Unlike the role-based model (which I will discuss below), differentiation means that the product has different users who work at different stages of a single business process. They may interact, or they may not overlap in tasks. Generally, within the product, you can find two main user groups: creators and consumers of data. For example, within a content-product managers add products to the catalog so that other departments can use them to create promotions.</p><p>To design cross-functional scenarios, it’s important to to understand how users perform the task step by step, what data they work with, and their <a href="https://medium.com/the-artificial/designing-a-conceptual-model-14ac21b93a22">conceptual model</a>. This allows you to remove unnecessary data, reducing the cognitive load or conversely focusing the user’s attention.</p><h4>Role model for different users</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sPJDbWJefOtmrI2U5O-ogQ.png" /><figcaption>Role model for different users</figcaption></figure><p>The larger the product becomes, the broader the user group it impacts. The role-based model allows designing a product for multiple user groups at once, without creating additional conditions within the scenario.</p><p>Access to sections and functions depends on the role of users. For example, for some users it will be only viewing data — viewers, while for others it will be correcting and adding/removing new entities — editors. The amount of data provided may also vary.</p><p>Designing the information architecture is a complex and multi-layered task. The designer is required to know not only the business process, user segments, and object model features, but also to prioritize the available data. Later, I will go into more detail about each method, show detailed examples of how to build a status model for different tasks, and how to differentiate user groups. For now, that’s all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecdd2081230b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design principle—decomposition]]></title>
            <link>https://medium.com/@burenok.eliza/design-principle-decomposition-bcd33cdb1c39?source=rss-b138941e1076------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcd33cdb1c39</guid>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Eliza Burenok]]></dc:creator>
            <pubDate>Sat, 18 Jan 2025 20:28:04 GMT</pubDate>
            <atom:updated>2025-03-11T05:27:45.401Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, we’ll discuss one of my favourites principles — <strong>decomposition</strong>. Decomposition helps break down a task into smaller, more manageable elements. It is especially useful during the stage of exploring possibilities and defining problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jFW8PEkS3gmVTT74osStqw.png" /><figcaption>Decomposition reflects the thinking process. When we need to understand something complex, the brain breaks it down into smaller parts</figcaption></figure><p>I liked the definition of decomposition from the <a href="https://www.linkedin.com/pulse/decomposition-design-pattern-chris-mckibbin">article</a> “Decomposition as a design pattern” by Chris Mckbbin, so I’ll share it here:</p><blockquote>“[Decompostion] breaks systems down into their smallest useful or meaningful element and then stitching them back together to make something better.”</blockquote><p>The architecture of a digital product is similar to the blueprint of a building: there’s the foundation, the load-bearing structure, and the transitions from one part to another. And just like building, digital product development presents the team with complex questions: What will the product consist of? How can we break down a large task into smaller blocks to speed up the process? How can we avoid doing unnecessary work? How can we build a solution for future reuse? How do we prevent development from stalling while the designer is working on the design?</p><p>I’ll share a couple of techniques I use in my work.</p><h3>Conceptual design</h3><p>The conceptual design is based on the build-measure-learn methodology — iterative improvements based on feedback. Somewhat similar to the model of MVP, isn’t it?</p><p>The main difference is that the <strong>conceptual design is a vision of the product presented in several design screens</strong>, which helps the team understand the end goal and the necessary steps.</p><p>Let’s take at an example. Your team builds the design tool for creating landing pages. Sounds ambitious, but where do you start? Let’s assume the team has already conducted research and knows the primary user benefit.</p><p>In that case, the designer takes the job story and creates 4–6 screens to showcase the core modules of the product. For the the tool, these could include:</p><ul><li>An empty form screen for creating a new page</li><li>A screen with a filled form for creating a page</li><li>A complex page module, such as search</li><li>A screen showing a list of all the pages the user has created</li></ul><p>These screens can be discussed with the analyst to ensure that the main user needs and business cases are covered, without diving into the design details. Even with a minimal number of screens, you can identify which additional and alternative scenarios are needed for each module. If any functionality questions arise, you can always return to user and stakeholder interviews.</p><blockquote>Think of the conceptual design as a way to overcome the fear of the blank page and the urge to do everything at once. Over time, it may become less important, but it will always serve as a point of reference to return to the original idea.</blockquote><p>Next, we conduct a grooming session with the team. Everyone participates in the process:</p><ul><li>The backend team suggests methods and integrations for creating a page</li><li>The systems analyst determines which databases will be needed to store page parameters</li><li>The frontend team estimates which components are required for layout</li><li>The product manager forms epics and creates tasks for each development group</li><li>The business analyst might start outlining basic use cases to pass on to the systems analysis team</li></ul><p>The methods for designing concept can vary — from wireframes and priority guides to hi-fi prototypes. The key is to define what each team member will focus on and plan the work accordingly.</p><h3>Concepts in the task</h3><p>Since we’re talking about concepts, let’s examine them from another perspective: How do you get concepts from a task?</p><p>A business process defines the development of a B2B product. Unlike B2C, in B2B, the initiatives for development are driven by the head of the department. These can either be requests to support an existing process or to create a new one.</p><p>This leads to a chain: <strong>business process → task</strong>. But what comes next?</p><p>Next, we analyze the task. It contains conditions in the form of nouns and verbs, from which we can get concepts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DqFl-7B_jhXYoHPbK1AriQ.png" /><figcaption>Sequence of transforming a business process into a concept</figcaption></figure><p>For example, let’s say the task is to support the process of labeling banners on a website with advertising. Labeling is a legal condition — all advertising formats must be marked in this way. What concepts can we extract from this task?</p><ol><li><strong>Banners</strong>: Banners have certain characteristics, such as width, format, placement, image, and platform (web/app). Banners are created by a group of users. We need to understand who these users are, where they get their tasks from, and whether they pass the result to another department.</li><li><strong>Labeling</strong>: Labeling consists of several parameters: promotional conditions, erid and advertiser. So, we need to investigate where this data comes from, and conduct interviews with legal experts to clarify the details.</li><li><strong>Label placement</strong>: Finally, the label needs to be placed on the banner. We need to figure out whether there’s enough space for it, which data is mandatory for the label, and when the label should appear.</li></ol><p>This results in three concepts: <strong>banners</strong>, <strong>labeling</strong>, and <strong>label placement</strong>. From here, we can break each concept down into parameters and link them to various scenarios. To help with this, an <strong>object map</strong> can be useful.</p><h3>Object map</h3><p>It’s also known as the <strong>data object modelling</strong>. The term was borrowed from object-oriented programming and has become established in design processes.</p><p>Let’s try to define what an <strong>object</strong> is to make the example easier to understand:</p><ul><li>An <strong>object</strong> is an independent part of the system that can be worked with and can exchange information (receive and transmit data)</li><li>An <strong>object map</strong> is a visual representation of how entities interact. From the map, you can see how objects are nested within each other and how they interact</li></ul><p>Consider an example from the chapter on the conceptual model with advertising labeling. We have two entities: banner and labeling. A coin flip determines which one becomes the object. The coin lands on the banner.<br>So, the banner is the object.</p><p>Now, let’s examine its components. We need to familiarize ourselves with two new terms: parameters and metadata.</p><ul><li><strong>Parameters</strong> are the characteristics of an object. For example, for a banner, a parameter could be the platform or placement. Other parameters include the banner’s width and height, its format (square/rectangular), and its placement.</li><li><strong>Metadata</strong> refers to parameters that appear as the object is used or interacted with. For our banner, such metadata could include the creation date and time.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vbf9SWpdxIMkdRXyvFUm7w.png" /><figcaption>An example of an object map</figcaption></figure><p>Here’s a little hack for recognizing objects if you haven’t built a conceptual model:</p><p>Take a familiar user story: <em>“As a [user], I want to [action], so that [result].”</em> Usually, the object is the repeated noun/verb in the sentence.</p><p>For greater detail, we would also distinguish properties for parameters and build nesting levels for objects, but that will be covered in another article.</p><p>Finally, a few words about decomposition. First, it’s not always possible to split a task correctly on the first try. The blocks may initially seem clear, but during the work process, they may require further detailing — and that’s completely normal. The design process is built on iterations, through which the team forms a more accurate understanding of the product. Secondly, all three methods can be combined. Assess the complexity of the task, your understanding of the possibilities, and the deadlines. And that’s it for today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcd33cdb1c39" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>