{
    "version": "https:\/\/jsonfeed.org\/version\/1",
    "title": "ivan's blog: posts tagged about",
    "_rss_description": "It is my diary. I’m ivan zviahin, an designer, manager, car enthusiast.",
    "_rss_language": "en",
    "_itunes_email": "ivanzviahin@gmail.com",
    "_itunes_categories_xml": "",
    "_itunes_image": "http:\/\/www.ivanzviahin.by\/blog\/user\/userpic-square@2x.jpg?1711411913",
    "_itunes_explicit": "no",
    "home_page_url": "http:\/\/www.ivanzviahin.by\/blog\/tags\/about\/",
    "feed_url": "http:\/\/www.ivanzviahin.by\/blog\/tags\/about\/json\/",
    "icon": "http:\/\/www.ivanzviahin.by\/blog\/user\/userpic@2x.jpg?1711411913",
    "author": {
        "name": "Ivan Zviahin",
        "url": "http:\/\/www.ivanzviahin.by\/blog\/",
        "avatar": "http:\/\/www.ivanzviahin.by\/blog\/user\/userpic@2x.jpg?1711411913"
    },
    "items": [
        {
            "id": "183",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/process\/",
            "title": "Design process",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/proces\/\">на русском<\/a> · in english<\/p>\n<p>Globally, each and every designer faces three types of tasks in their daily life. The first type is just about fixing something. The second group are likely to resolve some small problem. And lastly, they happen to do a big project. Depending on the type of task, there may come a different approach.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/Proprocess-3.jpg\" width=\"2434\" height=\"2560\" alt=\"\" \/>\n<\/div>\n<ol start=\"1\">\n<li>“Fix something” is by far the simplest one. There is no rocket science in here. What we do is go handle it. It might be difficult from the point of view of the process to do something wrong here.<\/li>\n<\/ol>\n<ol start=\"2\">\n<li>“Solve a small problem” in a large project. For instance, we may desire to add up the ability to like publications in the news feed or attach the ability to build on QR codes to your profile. To read <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/process-story\/\">process for a small task<\/a> go straight to point five.<\/li>\n<\/ol>\n<ol start=\"3\">\n<li>“Do a large project”. This is something way bigger, which consists of dozens, hundreds, thousands of tasks from the second point. And  most importantly, in this approach we are to break a large project into smaller tasks. So, when it comes to the third type, then first you need to ↓<\/li>\n<\/ol>\n<h2>1. Understanding goals<\/h2>\n<p>As a rule, this is a meeting with all stakeholders. Together we describe <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/goal-mission\/\">goal and mission<\/a> and  define the <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/portret\/\">audience<\/a> for which we the product will be made. We write out the main hypotheses that have a direct connection with the goal and mission. For each hypothesis, the success criteria are described and outlined — a set of high-level metrics and indicators.<\/p>\n<ul>\n<li><a href=\"https:\/\/telegra.ph\/Kak-sformirovat-pravilnoe-ponimanie-zadachi-v-produktovom-dizajne-podrobnyj-gajd-04-22\">More about understanding<\/a> Naer and Zviahin so far only in russian<\/li>\n<\/ul>\n<h2>2. Taking a birdview of product<\/h2>\n<p>In here we have to understand the scope of the product and what other systems the product can potentially hook. There are a few simple ways that I tap into to sort it out. It must be noted that most often is it better to make use of everything to broaden your horizons.<\/p>\n<ol start=\"1\">\n<li>System diagrams. The temptation for many designers is to go straight to interface development. Yet designing interactions at such an early stage can interfere with the development of the basics of your product. As part of a workshop with all stakeholders, you need to describe the project through system diagrams.<\/li>\n<\/ol>\n<ul>\n<li><a href=\"https:\/\/www.intercom.com\/blog\/applying-systems-thinking-in-product-design\/\">Applying systems thinking in product design<\/a> Shekman Tang<\/li>\n<li><a href=\"https:\/\/www.intercom.com\/blog\/design-futures-1-creating-systems-not-products\/\">Creating systems not destinations<\/a> Paul Adams<\/li>\n<\/ul>\n<ol start=\"2\">\n<li>User journey map. It helps tremendously to look at the product from another perspective. We go beyond the edges of the product and try to understand how the user will find the product, how he will understand the specifics of the work, etc. What are the roles, what are the stages, what are the goals and actions at these stages. As part of a workshop with all stakeholders, you need to describe the product through a user journey map. It is important to note that this is just our representation and the representation of stakeholders. In reality, everything may be different and you need to verify this card with potential users at the discovery stage.<\/li>\n<\/ol>\n<ul>\n<li><a href=\"https:\/\/katesyuma.com\/miroverse\/\">Miroverse Step – 2 – CJM<\/a> Kate Syuma<\/li>\n<\/ul>\n<p>It is a good practice at this meeting to outline a potential discovery plan.<\/p>\n<h2>3. Make sure we are on the right track<\/h2>\n<p>It is time to validate the concept and search for growth points. I have a few simple ways to accomplish this.<\/p>\n<ol start=\"1\">\n<li><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/in-depth-interview\/\">In-depth interviews.<\/a> A great way to find new insights, point-by-point. However, you should not immediately take them to work, it is best to validate them with points 2 and 3.<\/li>\n<li>Surveys. A quantitative study that can confirm the insights from point 1 and give reasons for reflection in isolation from qualitative research.<\/li>\n<li>Data analysis. A quantitative study that can confirm the insights from point 1 and give reasons for reflection in isolation from qualitative research.<\/li>\n<li>Competitor analysis. Top-level view of the set of functions of your direct and indirect competitors. This will help find something new and check out what you already have.<\/li>\n<li>Analysis of the metrics used. Desk research. As a rule, we are not the first in the world to do this, and quite a lot of articles with research and best solutions have already been written about many practices. We cannot say that they will suit us, but they are worth studying.<\/li>\n<li>Analysis of user feedback. Work with reviews in stores and with what arrives at the support service. There are often diamonds there that can confirm your idea or hypothesis.<\/li>\n<\/ol>\n<p>All these ways can change your model from point two.<\/p>\n<h2>4. Prioritizing it and splitting into versions<\/h2>\n<p>Next, we need to divide our entire concept into small user stories, prioritize them and divide them into versions.<\/p>\n<p>So, a map of user stories. This is such a visualization of the solution scope, which helps us determine the minimum valuable product and its evolution. Below is a good video that explains how it works in three minutes.<\/p>\n<div class=\"e2-text-video\">\n<iframe src=\"https:\/\/www.youtube.com\/embed\/TaMLUf3gISo?enablejsapi=1\" allow=\"autoplay\" frameborder=\"0\" allowfullscreen><\/iframe>\n<\/div>\n<p>To prioritize stories by importance, you can use <a href=\"https:\/\/www.productplan.com\/glossary\/moscow-prioritization\/\">moscow framework,<\/a> and <a href=\"https:\/\/medium.com\/radius-engineering\/project-estimation-through-t-shirt-size-ea496c631428\">t-shirt size framework<\/a> for technical complexity.<\/p>\n<p>As a result, we have dozens, hundreds, thousands of user stories that are prioritized and divided into versions.<\/p>\n<h2>5. Approaching each story individually<\/h2>\n<p>In a while, we work with each story (a small task) by a similar process, but still a little different.<\/p>\n<ol start=\"1\">\n<li>Understanding the task<\/li>\n<li>Discovery<\/li>\n<li>Formulation of hypotheses and low-fi prototypes<\/li>\n<li>Scouping and high-fi prototypes<\/li>\n<li>Review the result and launch!<\/li>\n<li>Result analysis and new iterations<\/li>\n<\/ol>\n<p><b><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/process-story\/\">Learn more about the design process of a small task →<\/a><\/b><br \/>\n<b><a href=\"https:\/\/drive.google.com\/file\/d\/1npBBtwRmWbiGo038QA97r0Iq0h5LJzgh\/view?usp=sharing\">Poster, PDF 2.3 MB<\/a><\/b><\/p>\n",
            "date_published": "2022-04-18T19:19:46+00:00",
            "date_modified": "2023-11-21T20:50:40+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/Proprocess-3.jpg",
            "_date_published_rfc2822": "Mon, 18 Apr 2022 19:19:46 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "183",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [
                    "system\/library\/jquery\/jquery.js",
                    "system\/library\/media-seek\/media-seek.js"
                ],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/Proprocess-3.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/remote\/youtube-TaMLUf3gISo-cover.jpg"
                ]
            }
        },
        {
            "id": "180",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/corridor-tests\/",
            "title": "Corridor tests",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/koridornye-testy\/\">на русском<\/a> · in english<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/david-travis-WC6MJ0kRzGw-unsplash-2.jpg\" width=\"2560\" height=\"1295\" alt=\"\" \/>\n<\/div>\n<h2>What are these tests for<\/h2>\n<p>So, at this stage you already have prototypes and formulated hypotheses. Now it remains to shake this bag and make sure that everything works as intended. Or rather, check the interface, icons, signatures, accents, and so on.<\/p>\n<h2>It’s simple<\/h2>\n<p>We have already formulated hypotheses, so we just write them out. We formulate tasks for users.<\/p>\n<p>We are preparing a clickable prototype, if it is needed. We fix the “gates”, in other words, the conversion marks of the interface. For example: opening a form, successful completion, sending, and so on.<\/p>\n<p>We are looking for participants for testing. We conduct testing and mark all the most important things. We draw conclusions and analyze them. Bingo, 100% percent you will change your attitude to your ideal prototypes.<\/p>\n<h2>1 step. Define hypotheses<\/h2>\n<p>Hypotheses are assumptions that we are going to test in the course of the study. It is better to formulate it according to the template: “If we do (the idea), then he will be able to positively influence (the criterion of success), since (why is this idea good)”.<\/p>\n<h2>2 step. Choose a testing method<\/h2>\n<p>All testing methodologies are divided into unmoderated and moderated according to the degree of independence of the task by respondents, as well as by the location of the respondent and the interviewer at the time of testing.<\/p>\n<p><b>First click.<\/b> The research participant follows the link and gets a very simple task. For example: “Where would you click to find information about leasing programs?”, “Choose leasing to purchase the selected car”. Only the first click is recorded. If the majority of respondents click “wrong way”, it signals that there are usability problems on the screen.<\/p>\n<p><b>Side by side.<\/b> The essence of the method is to compare two options and choose one based on the principle of better visibility or recognition of the target object. Respondents are asked to compare two images of the interface or select a specific element on two versions of the image. For example: “Find and select the A1 payment method”, “Which of the banner options is more recognizable for the material ‘Cars for leasing on ave’”.<\/p>\n<p><b>For patency.<\/b> The method is closest to moderated testing. It assumes the presence of the interviewer next to the respondent at the time of the test. We select conversion points and give the respondent a task that should lead him along the path you need. As a result, the facts of passing the points are recorded and notes are made about the difficulties encountered by the user.<\/p>\n<p><b>Moderated testing.<\/b> With such a check, the user performs the assigned tasks in relation to the product or service, while the researcher or moderator watches him in real time. Each of the above methods can be moderated. The reliability of the results and the depth of the insights obtained during such testing is considered better than when using methods without moderation.<\/p>\n<h2>3 step. Respondents’ choice<\/h2>\n<p>For testing, we need representatives of the target audience who are faced in real life with the tasks that are described in the testing tasks. However, the corridor test makes allowances in this matter, and absolutely all direct or indirect Internet users can become respondents.<\/p>\n<p>Five to eight respondents are enough to identify interface problems. If all respondents face the same difficulty— this is a reason to stop testing, make edits to the prototype and start testing a new version.<\/p>\n<p>If the resources and time to work on the site are very limited, we are guided by the principle: “less is better than nothing.” Three respondents are better than none.<\/p>\n<h2>4 step. Task formation<\/h2>\n<p>The quality of the results and their objectivity directly depends on the formulation of questions and tasks in testing. Checklist for the formulation of the task:<\/p>\n<ol start=\"1\">\n<li>Described accurately.<\/li>\n<li>Announced in full.<\/li>\n<li>Relevant to the respondent’s experience.<\/li>\n<li>It is possible to perform without prompts.<\/li>\n<\/ol>\n<h2>5 step. Preparation of the prototype<\/h2>\n<p>A test prototype can be:<\/p>\n<ol start=\"1\">\n<li>Interactive clickable prototype.<\/li>\n<li>A test version or a working website.<\/li>\n<li>Just a picture.<\/li>\n<\/ol>\n<p>Checklist for testing the prototype:<\/p>\n<ol start=\"1\">\n<li>Scripts are executed.<\/li>\n<li>There are different options for executing the script.<\/li>\n<li>Texts, numbers and visual content are similar to the real ones.<\/li>\n<li>There are no errors and typos in texts and figures.<\/li>\n<li>There are no hints.<\/li>\n<li>It is possible to quickly return to the beginning of the script.<\/li>\n<\/ol>\n<h2>6 step. Testing process<\/h2>\n<p>Properly conducted testing will be less stressful for the respondent, will be easier to moderate and, therefore, will give more relevant results. Advice – shut up, listen to the respondent and do not prevent him from not understanding anything.<\/p>\n<p>The respondent speaks most of the time during testing. The moderator speaks only if absolutely necessary. Any intervention by the moderator affects the course of the experiment and distorts the data.<\/p>\n<p>If the respondent has stopped “thinking out loud” – remind him about it: “So… So, you think that... What do you see here? Tell me what happened.”<\/p>\n<p>Questions often force the respondent to take a defensive position. You can replace questions with motivational phrases like: “Tell me a little bit about it... Describe it in more detail... Share your feelings... Let’s talk about it... Help me understand...”.<\/p>\n<p>In what cases to help:<\/p>\n<ol start=\"1\">\n<li>The respondent should feel that you are encouraging him, not the product.<\/li>\n<li>If the respondent has tried several methods of action and asks for help.<\/li>\n<li>The respondent thinks that the task is completed, but it is not.<\/li>\n<\/ol>\n<p>How to do it:<\/p>\n<ol start=\"1\">\n<li>Focus on the task, remind the purpose of the task.<\/li>\n<li>Make a general hint: “Remember how you started doing the task”, “You have already seen it”.<\/li>\n<li>To say directly what to do next.<\/li>\n<\/ol>\n<p>It is important to record the moments where the respondent encountered difficulties. After testing, we ask the respondent a few questions. You don’t have to follow the direct recommendations for changing the site that the respondent will express during the conversation. Conclusions and recommendations are usually made from observing behavior, not from a conversation.<\/p>\n<h2>7 step. Recording of results and conclusions<\/h2>\n<p>Even at the stage of hypothesis formulation, we recommend creating a table containing decomposed hypotheses and tasks for testing with the content of user steps or beaten conversion points.<\/p>\n<p>After each meeting, record the test result in the table: whether the hypothesis was confirmed, whether the respondent coped with the task without errors. We also add insights and other notes describing the user’s behavior at a particular step of the task.<\/p>\n<p>Based on this document, we draw conclusions about the confirmation or non-confirmation of the hypothesis, as well as formulate new ones, if necessary.<\/p>\n<h2>Table for recording results<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/Screenshot-2021-12-21-at-00.57.17-3.jpg\" width=\"2560\" height=\"569\" alt=\"\" \/>\n<div class=\"e2-text-caption\"><a href=\"https:\/\/docs.google.com\/spreadsheets\/d\/1jUvKw8LC8IRR54LL9nPpM__AIBPysdwt8xXmK4RDAR4\/edit?usp=sharing\">Table template in Google Docs<\/a><\/div>\n<\/div>\n",
            "date_published": "2022-01-18T08:47:11+00:00",
            "date_modified": "2022-01-18T08:46:29+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/david-travis-WC6MJ0kRzGw-unsplash-2.jpg",
            "_date_published_rfc2822": "Tue, 18 Jan 2022 08:47:11 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "180",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/david-travis-WC6MJ0kRzGw-unsplash-2.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/Screenshot-2021-12-21-at-00.57.17-3.jpg"
                ]
            }
        },
        {
            "id": "179",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/in-depth-interview\/",
            "title": "In-depth interview",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/research-interview\/\">на русском<\/a> · in english<\/p>\n<p>In-depth interview is a communication in the form of questions and answers, the purpose of which is to obtain the information needed by the researcher. The key task is not just to ask, but to see the world through the eyes of others and feel what they feel. Below I will tell you about the advantages and disadvantages of open and closed questions, about popular techniques, about the stages of interviews and solving difficult situations.<\/p>\n<h2>Closed questions<\/h2>\n<p>Almost always asking closed-ended questions is bad. They assume a binary answer: yes or no.<\/p>\n<p>Advantages:<\/p>\n<ul>\n<li>allow you to get specific information<\/li>\n<li>confirm or refute hypotheses<\/li>\n<li>nice change of subject<\/li>\n<\/ul>\n<p>Disadvantages:<\/p>\n<ul>\n<li>we get little information<\/li>\n<li>there are no details and details<\/li>\n<li>we can impose our opinion<\/li>\n<\/ul>\n<h2>Open questions<\/h2>\n<p>These usually begin with the words: “why, why, how, describe, tell us what you think and so on.”<\/p>\n<p>Advantages:<\/p>\n<ul>\n<li>allow the respondent to answer without restrictions<\/li>\n<li>give the respondent the opportunity to freely talk about their feelings and comment on events<\/li>\n<li>provoke a person to reflect, analyze their actions and thoughts that may not have occurred to them before<\/li>\n<\/ul>\n<p>Disadvantages:<\/p>\n<ul>\n<li>may provoke a long confused response<\/li>\n<li>the respondent may go “wrong way”<\/li>\n<\/ul>\n<p>A dirty trick, how to turn a closed question into an open one. Closed question + “Tell me...” = Open question.<\/p>\n<h2>The “Five Whys” technique<\/h2>\n<p>In order to find the cause of behavior, problems, inconsistencies, it is necessary to consistently ask the same question — “Why?”, and look for answers to this question. Each new question is added to the answers to the previous question.<\/p>\n<p>Often the repetition of the same question causes discomfort. How to make it better:<\/p>\n<ol start=\"1\">\n<li>Reformulate, for example, “What is the reason?” or “Because of what... is it happening?” or “Why is that?”.<\/li>\n<li>Say that you will ask “Why?” because you want to get to the root cause.<\/li>\n<\/ol>\n<h2>Technique “What? Who? · Where? When? · How? Why?”<\/h2>\n<p>The technique works well if you need to understand who the people who will be the users of your product are. Find out what they are doing, what problems they are facing.<\/p>\n<ul>\n<li>What happened? What was the hardest part? What does a person do? Who else is involved? What’s wrong with the current solution?<\/li>\n<\/ul>\n<p>Find out the context. Where it happens and when.<\/p>\n<ul>\n<li>Where did this happen? When was the last time this happened?<\/li>\n<\/ul>\n<p>How they do it. How to solve problems already. Why is it so.<\/p>\n<ul>\n<li>How exactly did this happen? Why was it difficult? How did you manage? How often is it repeated? Has the solution to the problem changed over time and why?<\/li>\n<\/ul>\n<h2>Stage: Preparation<\/h2>\n<p>Preparation consists of six steps:<\/p>\n<ol start=\"1\">\n<li>Understand the purpose of the interview.<\/li>\n<li>Do desk research on the topic.<\/li>\n<li>Make a plan: questions, situations, features.<\/li>\n<li>Formulate hypotheses.<\/li>\n<li>Think about what else might be useful for an interview.<\/li>\n<li>Have 3 main questions.<\/li>\n<\/ol>\n<h2>Stage: Interview<\/h2>\n<p><b>Start<\/b><\/p>\n<ul>\n<li>Tell us who you are and why you are conducting this interview.<\/li>\n<li>Indicate the duration.<\/li>\n<li>There are no wrong answers. You are here to find out the real experience of a person.<\/li>\n<li>The first questions should be made introductory to relax the respondent.<\/li>\n<\/ul>\n<p><b>The main part<\/b><\/p>\n<ul>\n<li>Talk about the respondent’s life, not about your idea.<\/li>\n<li>Ask about specific things that happened in the past, and not about views or opinions on the future.<\/li>\n<li>Talk less, listen more.<\/li>\n<li>Use the techniques of “Five Whys” and “What? Who! · Where? When? · How? Why?” to dig deeper.<\/li>\n<li>Show friendliness and interest. Be simpler.<\/li>\n<li>Speak in your native language<\/li>\n<li>Keep the question neutral. Don’t give your opinion. Don’t rate.<\/li>\n<li>Ask to compare.<\/li>\n<\/ul>\n<p><b>Ending<\/b><br \/>\nThank the respondent. Find out if the person wants to add something or ask you. Ask for the contacts of other people you can talk to. Agree on a potential sequel.<\/p>\n<h2>Difficult situations: the respondent is silent<\/h2>\n<p>Sometimes the respondent comes across silent. You should tell him about the value of the conversation. Tell me who you are and why this is all happening now. So to speak, to interest the respondent. Push the goal aside and establish personal contact.<\/p>\n<h2>Difficult situations: indecisive respondent<\/h2>\n<p>Sometimes the respondent does not give clear answers to each question. And yes and no, and so and so. Perhaps this is even very good. The respondent may have different experiences and it is worth digging deeper here. Ask about each option separately, why yes, why not. Ask for examples of all situations.<\/p>\n<h2>Difficult situations: talkative respondent<\/h2>\n<p>The respondent walks away after the question and gives completely useless information. Sometimes they can’t even be stopped, and the interview time is ticking. Here it is important to skillfully stop the respondent. For example, offer to discuss it later. It is also necessary to interrupt carefully, try to do it “on the inhale”.<\/p>\n",
            "date_published": "2022-01-11T08:46:26+00:00",
            "date_modified": "2022-01-11T08:51:12+00:00",
            "_date_published_rfc2822": "Tue, 11 Jan 2022 08:46:26 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "179",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": []
            }
        },
        {
            "id": "178",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/competitor-analysis\/",
            "title": "Competitor analysis",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/analiz-konkurentov\/\">на русском<\/a> · in english<\/p>\n<p>I consider the analysis of competitors within a specific feature as one of the ways to analyze and search for ideas. This is not about creating something bigger and not about the overall assessment of the market.<\/p>\n<p>It is important to note that we already know the problem and the goal. We have a success criterion and an audience is defined. What’s next?<\/p>\n<h2>We describe the evaluation criteria<\/h2>\n<p>The criteria will be different for each feature. We describe briefly, but as concretely as possible:<\/p>\n<ol start=\"1\">\n<li>How well the problem or task is solved. There may be several solutions. For example, adding a photo on the submission form or something else.<\/li>\n<li>The first interaction with interface.<\/li>\n<li>Keyboard shortcuts and interactivity.<\/li>\n<li>Anything else that is important in the context of a particular feature...<\/li>\n<\/ol>\n<h2>Looking for competitors<\/h2>\n<p>As a rule, 3-4 direct competitors are already known. We include it in the list and divide it into platforms, if necessary. Each platform is a separate analysis.<\/p>\n<p>Do not forget about indirect competitors. Newspaper, radio, apartment sale service, visa application form. They help to find the “new”, but they should be treated skeptically. A feature that works cool for them may not be needed by our audience at all.<\/p>\n<h2>Write to the table<\/h2>\n<p>We write down the criteria and add the “score” and “comment” field next to each one.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/compit.jpg\" width=\"2277\" height=\"755\" alt=\"\" \/>\n<div class=\"e2-text-caption\"><a href=\"https:\/\/docs.google.com\/spreadsheets\/d\/1YJtrJd9_mGNQn9eiK1YKRmKXCIP-uDqGGXtjqMa-rZ4\/edit?usp=sharing\">Template in Google Docs<\/a><\/div>\n<\/div>\n<p>The “score” is from 0 to 5. The better the competitor’s criterion is implemented, the higher the score.<\/p>\n<p>“Comment” – What influenced the assessment? Why not 5? Optionally, you can add more screenshots for clarity.<\/p>\n<h2>Making conclusions<\/h2>\n<p>In the process of filling out the table, ideas will appear that solves the problem well, and what is not very good and how it can be improved. Based on the information received, we make hypotheses.<\/p>\n",
            "date_published": "2022-01-03T08:37:03+00:00",
            "date_modified": "2022-01-03T08:40:54+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/compit.jpg",
            "_date_published_rfc2822": "Mon, 03 Jan 2022 08:37:03 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "178",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/compit.jpg"
                ]
            }
        },
        {
            "id": "177",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/portret\/",
            "title": "Audience",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/audience\/\">на русском<\/a> · in English<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/audiiience.png\" width=\"1590\" height=\"628\" alt=\"\" \/>\n<\/div>\n<p>Why do I need to understand the audience? To catch the right mental model when designing the interface, to show empathy, to make the most understandable product. And often it’s not very easy to do.<\/p>\n<p>There is, for example, such a tool — persons or portraits of audiences. I don’t really believe in these ways. Why? First, most often, they are collected on the basis of superficial information. Secondly, the audience is dynamic and often very diverse. Yesterday’s personas may not be the reality of today.<\/p>\n<p>And if everything is so bad, then what to do? I have a couple of thoughts on this.<\/p>\n<h2>1. Use the data<\/h2>\n<p>We go to analytics and try to identify our audience there based on banal characteristics:<\/p>\n<ul>\n<li>gender,<\/li>\n<li>age,<\/li>\n<li>place of residence,<\/li>\n<li>income.<\/li>\n<\/ul>\n<p>If the data doesn’t work, take a survey or look at the statistics of your social networks.<\/p>\n<p>You may notice that based on the data alone, it is already possible to split the audience into several portraits. Now we have a very superficial idea of who these people are and into which segments they are roughly divided. Let’s take the statistical middle of each segment and try to find out more about them.<\/p>\n<h2>2. Communicate with users weekly<\/h2>\n<p>In theory it sounds very scary and difficult, in practice it is very interesting and useful. And yes, I’m talking about weekly interviews. We already have an idea of the average audience. It remains to find them and talk.<\/p>\n<p>What is there to talk about so often? It turns out that there is always a lot there: to check prototypes of current tasks, to talk about life, about the future, about problems, to discuss functions from the backlog. In a couple of months, you will have a good understanding of who your audience is. What segments it has and what segments it have:<\/p>\n<ul>\n<li>problems,<\/li>\n<li>motivations,<\/li>\n<li>context,<\/li>\n<li>expectations.<\/li>\n<\/ul>\n<p>Where can I get users? Good question. Unloading the database and sending emails with an invitation to talk. Here is already your fantasy how to position it. Perhaps this is some kind of closed club of users close to the product or just an opportunity to get a T-shirt with the company logo.<\/p>\n<p>An alternative to an interview or an additional source of information can be any kind of community or commentators in stores and social networks.<\/p>\n<h2>3. Complete portraits in the process of communication<\/h2>\n<p>Perhaps you need to fix the new information somehow. Therefore, it seems logical to take the portraits from the first paragraph and supplement them in the process.<\/p>\n<h2>⌘⌘⌘<\/h2>\n<p>Example of portraits of the car sales ad board av.by after years of work.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/ps_1.jpg\" width=\"2560\" height=\"2524\" alt=\"\" \/>\n<\/div>\n",
            "date_published": "2021-12-27T07:55:58+00:00",
            "date_modified": "2022-04-27T20:05:54+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/audiiience.png",
            "_date_published_rfc2822": "Mon, 27 Dec 2021 07:55:58 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "177",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/audiiience.png",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/ps_1.jpg"
                ]
            }
        },
        {
            "id": "176",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/goal-mission\/",
            "title": "Goal and mission",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/goal\/\">на русском<\/a> · in english<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/gomi-1.jpg\" width=\"2386\" height=\"943\" alt=\"\" \/>\n<\/div>\n<p>Or how I formulate the goal and mission when working with a task.<\/p>\n<h2>Goal<\/h2>\n<p>The goal is the final point in the business world that we want to achieve by doing something. For example, we want to increase revenue by 33% for the third quarter by increasing the number of service payments.<\/p>\n<ol start=\"1\">\n<li>The goal should be specific. What exactly do we want to increase? Can I segment it in more detail?<\/li>\n<li>Measurable. You need to specify a number. Numerical definition, quantity in absolute or percentage form.<\/li>\n<li>With a deadline. How much time do we need to achieve success? When should the planned result be received?<\/li>\n<\/ol>\n<h2>Mission<\/h2>\n<p>The mission is what we will help the user with if we do something. For example, we want to help the user quickly find out about the appearance of new ads for interesting searches. If 25% percent of users use it in a month, it will be considered a success.<\/p>\n<h2>Can they be together?<\/h2>\n<p>Yes. The coolest thing is when you manage to make decisions in the field of intersections of mission and goal, but sometimes it happens that the solution is only in the field of mission or goal. And that’s fine.<\/p>\n<h2>How to formulate it?<\/h2>\n<p>Discuss the problem with your product manager. Discuss how this affects our end users and our business. Discuss what success looks like by defining success criteria. Write down your open questions and think about how you will answer them. Look at past research. Challenge the wording — is this the right problem, is it formulated correctly?<\/p>\n",
            "date_published": "2021-12-21T08:23:21+00:00",
            "date_modified": "2022-04-27T19:56:07+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/gomi-1.jpg",
            "_date_published_rfc2822": "Tue, 21 Dec 2021 08:23:21 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "176",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/gomi-1.jpg"
                ]
            }
        },
        {
            "id": "155",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/development-levels\/",
            "title": "Development levels",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/urovenprorabotki\/\">на русском<\/a> · in english<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/devlevels-1.png\" width=\"1590\" height=\"628\" alt=\"\" \/>\n<\/div>\n<p>I would like to talk about resolving an important problem in the product team. The issue is that it takes too long to complete tasks. One of the reasons is that the level of elaboration is too deep. As if we have no time at all, and yet the functionality should be fully completed. The only thing remaining is to reduce the level of development. We decided to lower it not for all tasks, but only for some.<\/p>\n<p>User scenarios in any product can be divided into three levels. Level one is scenarios that people use almost every day. We called such scenarios the main ones. The second is important, but not often necessary. These scenarios were called intermediate. The third is exceptions, these are just those scenarios that are usually completely forgotten.<\/p>\n<h2>Level 1<\/h2>\n<p>These are the most essential scenarios that the user uses every day. For example, searching for products in a store or reading news in a magazine. The development of such scenarios should be at the highest level. Here you need to spend time on checks and testing. Think through all the exceptions, make animations and hotkeys. Such scenarios are not numerous.<\/p>\n<h2>Level 2<\/h2>\n<p>These are important scenarios. But they are not often used. For example, profile settings. In such scenarios, you need to spend time on design and testing, but you can be more cool about mistakes. It makes no sense taking into account hotkeys. If some scenario ends up with an error, then it’s not as bad as in the first case. Someone says that this is why the car interior is made as comfortable as possible, compared to the engine compartment.<\/p>\n<h2>Level 3<\/h2>\n<p>Scenarios that are too popular among programmers. They can be ignored in the design. However, we must remember them, it need to be processed, but it should be done as simple as possible. For instance, imagine opening one page in two browser tabs and in one of them doing some action that changes the status of something else. And then you go to another one and do the same action, how should the system behave? Only the quality of the code depends on the ability to handle exceptions, but the success of the product is grounded on the first two levels.<\/p>\n<h2>Conclusion<\/h2>\n<p>No one needs a store with a perfectly thought-through scenario for adding a product to “Favorites” in two browser tabs, when the product search works poorly and is unclear.<\/p>\n",
            "date_published": "2021-08-15T21:28:01+00:00",
            "date_modified": "2022-04-27T19:57:37+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/devlevels.png",
            "_date_published_rfc2822": "Sun, 15 Aug 2021 21:28:01 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "155",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/devlevels.png",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/devlevels-1.png"
                ]
            }
        },
        {
            "id": "156",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/situational-leadership\/",
            "title": "Situational leadership",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/situacionnoe-liderstvo\/\">на русском<\/a> · in english<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/leadership-1.png\" width=\"1590\" height=\"628\" alt=\"\" \/>\n<\/div>\n<p>Situational leadership is a style of people management that involves the use of one of the four management styles, depending on the situation and the level of development of employees in relation to the task. According to this model, there are 4 leadership styles and 4 degrees of employee development.<\/p>\n<h2>4 management styles<\/h2>\n<p>The first is directive style, or leadership by command. High focus on the task and low focus on the people. The leader gives specific instructions and monitors the completion of tasks.<\/p>\n<p>The second is mentoring style, or leadership by selling ideas. Combining a high focus on the task and on the people. The manager continues to give instructions and monitor the execution of tasks, but at the same time explains the decisions made to the employee, offers to express their ideas and suggestions.<\/p>\n<p>The third is a supportive style, or leadership by participating in the organization of the working process. High focus on people and low focus on the task. The leader supports and helps their employees in their work. The leader is involved in the decision-making process, but the decisions are made by the team.<\/p>\n<p>The fourth is the delegating style. Low focus on both people and the task. The leader transfers authority, rights, and responsibility to other team members.<\/p>\n<h2>4 degrees of employee development<\/h2>\n<p>The first. An employee at this level is highly motivated, shows a lot of enthusiasm, but has only basic knowledge and skills.<\/p>\n<p>Second. An employee at this level usually already has the knowledge and skills, but such an employee feels demotivated for some reason.<\/p>\n<p>Third. An employee at this level has the knowledge and well-developed skills to complete the task, but their self-confidence and abilities are unstable, which in its turn can affect motivation.<\/p>\n<p>Fourth. The employee at this level demonstrates a masterful command of the skills necessary to complete this task. In addition, they are motivated and confident.<\/p>\n<h2>Total<\/h2>\n<p>10% knowledge, 100% motivation – directive style.<br \/>\n30% knowledge, 10% motivation – mentoring style.<br \/>\n70% knowledge, 40% motivation – supportive style.<br \/>\n100% knowledge, 100% motivation – delegating style.<\/p>\n",
            "date_published": "2021-08-15T21:27:55+00:00",
            "date_modified": "2022-04-27T19:58:00+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/leadership-1.png",
            "_date_published_rfc2822": "Sun, 15 Aug 2021 21:27:55 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "156",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/leadership-1.png"
                ]
            }
        },
        {
            "id": "157",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/self-checking-the-interface\/",
            "title": "Self-checking the interface",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/check-list-to-verify-the-interface\/\">на русском<\/a> · in english<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/checklist.png\" width=\"1590\" height=\"628\" alt=\"\" \/>\n<\/div>\n<p>Before each interface screen, I ask myself these questions:<\/p>\n<ol start=\"1\">\n<li>And in this case, does a person have some kind of habit? Are there any familiar patterns of such an interface in the world?<\/li>\n<\/ol>\n<ol start=\"2\">\n<li>Am I forcing the user to do something that a computer can do? For example, the field is immediately in focus.<\/li>\n<\/ol>\n<ol start=\"3\">\n<li>Have I lost the data that the user gave me?<\/li>\n<\/ol>\n<ol start=\"4\">\n<li>Did I remove all the extra stuff from this screen? Is it possible to connect some functionality? Can I add some utility?<\/li>\n<\/ol>\n<ol start=\"5\">\n<li>I try to imagine that I didn’t see anything before this screen. Do I understand everything on this screen?<\/li>\n<\/ol>\n<ol start=\"6\">\n<li>Have I done everything to avoid using the modal interface? Can I show all the functions at once? Can I use a quasi-mode? Have I thought through stack navigation well?<\/li>\n<\/ol>\n<ol start=\"7\">\n<li>Is it easy for me to hit each element with my cursor or finger? Have I shown the click areas?<\/li>\n<\/ol>\n<ol start=\"8\">\n<li>Have I thought about the feedback of each action? It should be fast, constant and simple. Sometimes emotional, where it is necessary. Have I prepared animations of important interface elements? Do I need tactile feedback and sound feedback?<\/li>\n<\/ol>\n<ol start=\"9\">\n<li>Does the interface fit into the user’s mental model? Can I reduce the resistance if I go beyond the limits of this model?<\/li>\n<\/ol>\n<ol start=\"10\">\n<li>Is the interface complete and systematic? Can I reuse something? Do all the elements correspond to the design system?<\/li>\n<\/ol>\n<ol start=\"11\">\n<li>Did I get an <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/aesthetic-and-clean-things-work-better\/\">aesthetic, simple and clean interface?<\/a> Have I lost my simplicity trying to explain what kind of screen it is?<\/li>\n<\/ol>\n<ol start=\"12\">\n<li>Did I forget about darkmode?<\/li>\n<\/ol>\n<ol start=\"13\">\n<li>Did I forget about tablets? About small smartphones?<\/li>\n<\/ol>\n<ol start=\"14\">\n<li>Did I describe all the extreme states? How many lines of text? How to position images and so on. What does the screen look like without data?<\/li>\n<\/ol>\n<ol start=\"15\">\n<li>Are there any extra loaders? Ideally, there should be no loaders at all. Do I need skeletons?<\/li>\n<\/ol>\n<ol start=\"16\">\n<li>Did I forget to consider what the interface would look like with the larger font?<\/li>\n<\/ol>\n<ol start=\"17\">\n<li>Did I discuss the syntax with the ux editor?<\/li>\n<\/ol>\n<ol start=\"18\">\n<li>Did I add a cherry to the cake? Did I do something small but important that will surprise the user?<\/li>\n<\/ol>\n",
            "date_published": "2021-08-15T21:27:47+00:00",
            "date_modified": "2023-08-23T13:36:10+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/checklist.png",
            "_date_published_rfc2822": "Sun, 15 Aug 2021 21:27:47 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "157",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/checklist.png"
                ]
            }
        },
        {
            "id": "154",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/process-story\/",
            "title": "Design process · task",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/proces-istorii\/\">на русском<\/a> · in english<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/Frame-5-1.png\" width=\"2386\" height=\"1085\" alt=\"\" \/>\n<\/div>\n<p>At the entrance there are always high-level requirements from product manager or from the project documentation. Usually it looks like a request, less often in more detail with hypotheses already put forward. For example, we want to add the ability to like publications in the news feed or add the ability to add QR codes to your profile.<\/p>\n<h2>1. Understanding<\/h2>\n<p>I understand high-level requirements. I write out <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/goal-mission\/\">goal and mission.<\/a> I note how we will understand that the result will be achieved — the criteria of success. Most often, this is some kind of indicator in numbers. I specify the target <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/portret\/\">audience.<\/a><\/p>\n<ul>\n<li><a href=\"https:\/\/telegra.ph\/Kak-sformirovat-pravilnoe-ponimanie-zadachi-v-produktovom-dizajne-podrobnyj-gajd-04-22\">More about understanding<\/a> Naer and Zviahin so far only in russian<\/li>\n<\/ul>\n<p><i>Best practice:<\/i><\/p>\n<ul>\n<li><i>draw a system diagram of the task,<\/i><\/li>\n<li><i> synchronize this understanding with team members.<\/i><\/li>\n<\/ul>\n<h2>2. Discovery<\/h2>\n<p>I need the analysis to formulate a large number of valid hypotheses. I have several working methods.<\/p>\n<ol start=\"1\">\n<li>Analysis of the current solution, if there is one, or a personal idea of the solution to the problem. We are experienced designers, we can immediately tell what can be improved.<\/li>\n<li><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/competitor-analysis\/\">Competitor Analysis.<\/a><\/li>\n<li>User feedback analysis. Work with reviews in fear and with what arrives at the support service.<\/li>\n<li>Analysis of feedback from other departments, if appropriate. For example, a commercial department or a marketing department.<\/li>\n<li><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/in-depth-interview\/\">In-depth interviews<\/a> with a potential audience.<\/li>\n<li>Analysis of the metric that we are using. Desk research. As a rule, we are not the first in the world to do this, and quite a lot of articles with research and best solutions have been written about many practices. We cannot say that they will suit us, but it is worth studying.<\/li>\n<li>Data analysis.<\/li>\n<\/ol>\n<h2>3. Hypothesis formulation and low-fi prototypes<\/h2>\n<p>After the analysis, I have a lot of ideas and I try to formalize them using the mask.<\/p>\n<ul>\n<li>If we do <i>(idea)<\/i>, then it can positively affect the <i>(success criterion)<\/i>, because <i>(why is this a good idea)<\/i>.<\/li>\n<\/ul>\n<p>For each hypothesis, I usually make simple and cheap prototypes. It helps to live with the idea and explain it to others. Sometimes it helps to find new hypotheses.<\/p>\n<p>Next, we prioritize each hypothesis. Priority is estimated by two parameters:<\/p>\n<ul>\n<li>how much does the hypothesis help to achieve the goal or mission (from 0 to 10) together with the product manager,<\/li>\n<li>how technically difficult it is to implement (also from 0 to 10) together with engineers.<br \/>\nFor each hypothesis, I divide one by the other and get a coefficient. We sort and get what needs to be taken into work in the first place.<\/li>\n<\/ul>\n<p><i>Best Practice:<\/i><\/p>\n<ul>\n<li><i>make design session, show prototypes and diagrams to other designers in the team, analysts, and product manager. There we make a decision what ideas we go ahead with,<\/i><\/li>\n<li><i> check the best ideas with <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/corridor-tests\/\">corridor tests.<\/a> This helps to find some gaps in the interface.<\/i><\/li>\n<\/ul>\n<h2>4. Scoping and Hi-fi prototypes<\/h2>\n<p>We started by understanding the problem. Next, we thought big when we generated hypotheses. Take this larger-scale vision, this long-term plan or dream, and then start small, break it down into the smallest pieces. And keep removing functionality until you get the least valuable solution. We usually do this together with the product manager.<\/p>\n<p>For a better solution, I make layouts, make all the states, work with the syntax of interface elements and text. I write explanatory notes for developers and animate screens and interface elements.<\/p>\n<p><i>Best Practice:<\/i><\/p>\n<ul>\n<li><i>look at user scenarios through the <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/development-levels\/\">development levels,<\/a><\/i><\/li>\n<li><i> check every screen <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/self-checking-the-interface\/\">with my checklist,<\/a><\/i><\/li>\n<li><i> check the result with <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/corridor-tests\/\">corridor tests.<\/a> This helps me find some gaps in the interface,<\/i><\/li>\n<li><i> note this task, I will need to be returned to after some time and check the result with expectations,<\/i><\/li>\n<li><i> give the layouts to another designer for a design review so that he looks through them and tries to find some gaps and errors,<\/i><\/li>\n<li><i> give the layouts for a product review so that the analyst or product manager compares the layouts with the user story.<\/i><\/li>\n<\/ul>\n<h2>5. Review of the result and launch!<\/h2>\n<p>After the tests, I do a review of the result to compare what I have planned with the result. Next  comes the launch.<\/p>\n<h2>6. Analysis of the result<\/h2>\n<p>After some time, depending on the task, I return to the task and analyze the result together with the product manager. Did the results match our expectations? We draw conclusions. For convenience, I fix tasks with dates and conclusions in a Google Table, without any rocket science.<\/p>\n<p>Then iterations, iterations and iterations. If everything is bad, we return to point one, if it is good, too, but with new goals.<\/p>\n<h2>— That’s a long time!<\/h2>\n<p>This whole process sounds complicated and long, yes. However it must be noted that in reality this is not as long as it seems. The first 6 steps of the average task complexity are done within 1-2 working days. Moreover, the ideal process is described here, in real life, some items are skipped or automated.<\/p>\n<p><b><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/process\/\">Design process · big project →<\/a><\/b><\/p>\n",
            "date_published": "2021-07-08T22:19:25+00:00",
            "date_modified": "2023-05-10T21:09:44+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/Frame-5-1.png",
            "_date_published_rfc2822": "Thu, 08 Jul 2021 22:19:25 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "154",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/Frame-5-1.png"
                ]
            }
        },
        {
            "id": "153",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/principles\/",
            "title": "Principles",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/principi\/\">на русском<\/a> · in english<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/Frame-2.png\" width=\"2386\" height=\"1085\" alt=\"\" \/>\n<\/div>\n<p>Principles help me make decisions. I stole some from others, some were invented by myself.<\/p>\n<h2>Entrepreneur<\/h2>\n<p>I compare the time spent with the benefits received. I do not do self-expression, I am looking for a solution that is cheap, at the same time, the solution brings the maximum benefit. I value the company’s resources.<\/p>\n<h2>Trash<\/h2>\n<p>The more time the designer spends on the layout, the harder it is for them to throw out this layout. I make cheap prototypes and small iterations in mockups to easily throw out these solutions in case they don’t work.<\/p>\n<h2>Focus<\/h2>\n<p>Far better to spend more time analyzing the problem and offer a strong solution than to solve the problem without understanding. On average, it takes about half of the time to understand a task.<\/p>\n<h2>Game<\/h2>\n<p>A simple way to reduce your level of anxiety or the importance of something is to imagine that everything that is happening around is a computer game and I have a certain resource for the day. First, I can’t do more than I can do. Second, failure is not the end of the world, it helps to move forward. I will have many opportunities.<\/p>\n<h2>Iceberg<\/h2>\n<p>Usually, when I give an estimate, you only estimate the time of those tasks that are immediately clear. But about the same number of tasks come in the process. A simple way is to multiply the visible time by two, then it will be more truthful. But the visible area depends on the experience of the designer, so each designer has their own parameters.<\/p>\n<h2>Empathy<\/h2>\n<p>The trouble is if the designer resolves their own problem, and not the <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/goal-mission\/\">problem of the user or business.<\/a> I am trying to relive person’s task. Maybe I should become one for a couple of days.<\/p>\n<h2>Initiative<\/h2>\n<p>Simple, but important. No one can plan my week better than me. No one forces me or reminds me about the tasks. No one explains the requirements for the task to me. No one will tell me about the technical limitations in detail.<\/p>\n<h2>Transparency<\/h2>\n<p>I don’t keep my thoughts to myself. I speak out if I feel that my vision helps to achieve the goal.<\/p>\n<h2>Responsibility<\/h2>\n<p>If you promised, you should do it, put it as a priority. If I don’t have time, I must tell the person who is waiting as soon as possible.<\/p>\n<h2>Right now<\/h2>\n<p>I am trying to resolve the problem simply, and then think about how to add functionality. I found the “Perfect world”, then I thought about how to do it right now, but without losing quality. If the complete ideal solution is a cake, then in the first version you need to make a cupcake with a cherry.<\/p>\n<h2>Perfect world<\/h2>\n<p>First, I am trying to remove all restrictions and generate ideal solutions. To see the final point, which we will go to later. It often happens that these “ideal solutions” can be easy to implement.<\/p>\n",
            "date_published": "2021-07-08T22:19:10+00:00",
            "date_modified": "2022-04-11T21:20:50+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/principles.png",
            "_date_published_rfc2822": "Thu, 08 Jul 2021 22:19:10 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "153",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/principles.png",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/Frame-2.png"
                ]
            }
        },
        {
            "id": "152",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/mission\/",
            "title": "Popularize systems thinking and simplicity through lens of design",
            "content_html": "<p><a href=\"https:\/\/ivanzviahin.by\/blog\/drafts\/missia\/\">на русском<\/a> · in english<\/p>\n<p>These are not just buzzwords. These are important things that I had to undergo and learn through, things that reflect a large number of attempts to try out various things in design.<\/p>\n<h2>— Mom, who turns on the street lights every day?<\/h2>\n<p>Since childhood, I have been passionate about researching different subjects, looking for a system in each solution, trying to find patterns and thinking about all the options for the outcome of the action. It’s always been in my DNA. I appreciate people who are looking for a system at every step, thinking about how to make it fault-tolerant and scalable.<\/p>\n<p>Sometimes I even thought that popularizing systems thinking was my destiny, after I came to my senses and realized that this was not only my plus, but also a minus. In simple tasks, a systematic approach prevents me from making decisions quickly. For this, I came up with <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/development-levels\/\">development levels<\/a> of a task and I use them every day. I am sure that the phrase “system thinking” definitely deserves to be here.<\/p>\n<h2>— Ah, that’s why sometimes beautiful things work better<\/h2>\n<p>It’s incredibly important to me how things look and how people feel when they use them. Emotions, emotions and emotions again. I am one of those people whose mood changes for the better when I am in a beautiful place or surrounded by beautiful objects. I’m trying to popularize <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/aesthetic-and-clean-things-work-better\/\">beauty and aesthetics<\/a> in my work as much as I can.<\/p>\n<h2>— Van, well, don’t complicate it!<\/h2>\n<p>I often heard this phrase from my manager at the beginning of my career. The ability to make a complex thing is simple — it’s worth a lot. I’m trying to find a middle ground between “I’ll explain and sign everything right now” and “let’s remove everything unnecessary and make it simple.” It is infinitely important to reduce cognitive resistance and give a person as much information as he needs at the moment, no more.<\/p>\n<h2>My kind of thing<\/h2>\n<p>Simplicity · beauty · collaboration · respect · truth · learning. If they are not there, I feel uncomfortable. Areas that attract me are communication, cars, travel, music, wine.<\/p>\n<h2><a href=\"https:\/\/ivanzviahin.by\/blog\/all\/principles\/\">Design principles<\/a><\/h2>\n<p>Entrepreneur · trash · focus · game · iceberg · empathy · initiative · transparency · responsibility · right now · perfect world.<\/p>\n<h2><a href=\"http:\/\/ivanzviahin.by\/cv-zviahin.pdf\">CV,PDF ↓<\/a><\/h2>\n<h2>Press<\/h2>\n<p>Design Community · <a href=\"https:\/\/youtu.be\/Brz_XeX-wAQ?si=XVf8eEeGTN63QwEO\">How we made a news card in the feed and increased CTR of first card by 32%.<\/a><\/p>\n<p>habr.com · <a href=\"https:\/\/habr.com\/ru\/companies\/tinkoff\/articles\/743534\/\">How to build an understanding of the problem in product design.<\/a><\/p>\n<p>whydesign.io · <a href=\"https:\/\/www.instagram.com\/p\/CmTbKpqthe6\/?igshid=NWQ4MGE5ZTk=\">Design is an opportunity to popularize system thinking and simplicity.<\/a><\/p>\n<p>#FFDD2D design conf · <a href=\"https:\/\/www.youtube.com\/embed\/KafkVtiT1-w\">How to implement the design process in your work and improve the results.<\/a><\/p>\n<p>Design Spot <a href=\"https:\/\/medium.com\/p\/8ac4d9add363\">If you haven’t conducted an interview with a user, you’re not a designer.<\/a><\/p>\n<p>Nativ <a href=\"https:\/\/www.youtube.com\/watch?v=rzm8GxdZETc\">About UX · UI and something else. Interview with Ivan Zviahin and Alexey Tischenko.<\/a><\/p>\n<p>Independent magazine of bureau Gorbunova “Who is the student” <a href=\"https:\/\/ktostudent.ru\/vanja-zvjagin\/\">Ivan Zviahin. Just do maximum.<\/a><\/p>\n<p>Transit Maps <a href=\"http:\/\/transitmap.net\/post\/163696560175\/minsk-birman\">Absolutely beautiful map.<\/a><\/p>\n<p>vc.ru <a href=\"https:\/\/vc.ru\/flood\/34836-vse-deystviya-v-biznese-dolzhny-byt-krasivymi\">All actions in business should be beautiful.<\/a><\/p>\n<p>vc.ru <a href=\"https:\/\/vc.ru\/marketing\/75253-50-materialov-chtoby-delat-internet-marketing-samostoyatelno?\">50 materials to do online marketing yourself. My article is number 13.<\/a><\/p>\n<p>Skillbox <a href=\"https:\/\/skillbox.ru\/media\/design\/vybiraem-respondentov-dlya-uxissledovaniya\/\">“Who should I ask?”: choosing respondents for UX research.<\/a><\/p>\n<p>Skillbox <a href=\"https:\/\/skillbox.ru\/media\/design\/ask-expert-text-tube-map\/\">Ask an expert: how can I make useful titles on the metro map?<\/a><\/p>\n<p>RAUX 2020 <a href=\"https:\/\/youtu.be\/8Eek--ZCBuI?t=944\">Markup is the competence of the design team. The story of how we did it.<\/a><\/p>\n<p>Marketing.by <a href=\"https:\/\/marketing.by\/keysy\/ramamba-kharu-avebay-poyushchiy-kokos-v-reklame-av-by-zastavit-vas-krutit-rolik-na-povtore\/\">A singing coconut in an av ad.by will make you turn the video on repeat.<\/a><\/p>\n<p>Marketing.by <a href=\"https:\/\/marketing.by\/keysy\/aida-pioneer-prodolzhila-istoriyu-s-karpom-v-novoy-reklamnoy-kampanii-dlya-av-by\/?fbclid=IwAR3W1lycXuCdjk9Tpd60DU0z-lzAWhP_oWL7s3m3NiZcZ8v1d0I-1j-aMLQ\">AIDA Pioneer continued the story with carp in a new advertising campaign for av.by.<\/a><\/p>\n<p>Marketing.by <a href=\"http:\/\/marketing.by\/keysy\/av-by-pokazal-kak-mashina-prevrashchaetsya-v-dengi-\/\">av.by showed how the car turns into money.<\/a><\/p>\n<p>Marketing.by <a href=\"https:\/\/marketing.by\/keysy\/dazhe-karp-znaet-novaya-reklamnaya-kampaniya-av-by-gde-rybu-ozvuchil-izvestnyy-akter-dublyazha\/\">Even fish knows: the new av.by advertising campaign.<\/a><\/p>\n<p>Marketing.by <a href=\"http:\/\/marketing.by\/keysy\/istoriyu-zhizni-belarusov-cherez-ikh-avtomobili-pokazali-v-reklamnoy-kampanii-av-by\/\">The history of the life of Belarus through their cars.<\/a><\/p>\n<p>BTW <a href=\"https:\/\/btw.by\/kejsy\/33606-kejs-aida-pioneer-av-by-prevrashhaet-mashinu-v-dengi.html\">AIDA Pioneer case: av.by turns a car into money.<\/a><\/p>\n<p>BTW <a href=\"https:\/\/btw.by\/kejsy\/27043-garazh-zhizni-v-reklamnoj-kampanii-av-by-ot-aida-pioneer.html?fbclid=IwAR1BQo65D6MbIxZeHPEQ2_NsmnXgpC_AqkqvV0M01YM1TvipsSBTAa0Qavk\">Garage life in the advertising campaign av.by from AIDA Pioneer.<\/a><\/p>\n<p>BTW <a href=\"http:\/\/btw.by\/kejsy\/733-skhema-minskogo-metro-takaya-chto-drugie-goroda-zaviduyut.html\">The scheme of the Minsk metro, such that other cities envy.<\/a><\/p>\n<p>Probusiness.io <a href=\"https:\/\/probusiness.io\/marketing\/6730-uniki-vyrosli-pochti-vtroe-auditoriya-prilozheniy-v-8-raz-keys-o-reklamnoy-kampanii-av-by.html\">The audience of app av.by has grown 8 times.<\/a><\/p>\n<p>Onliner <a href=\"https:\/\/realt.onliner.by\/2017\/07\/31\/metro-128\">Russian art director and Belarusian designers have developed a new Minsk Metro Map.<\/a><\/p>\n<p>Canva.com <a href=\"https:\/\/www.canva.com\/ru_ru\/obuchenie\/50-sovetov-po-sozdaniyu-portfolio-dizajnera\/\">Designer’s portfolio – tips, templates, and examples. My website is number 14.<\/a><\/p>\n<p>Realt.by <a href=\"https:\/\/realt.by\/news\/article\/24146\/?fbclid=IwAR0FOHFb18YL0hAiMX8DyqPO6mYStXocvJFlFvnLx6AvzhtYCVnnQ1TNPEs\">The designer has developed a new metro scheme in Minsk.<\/a><\/p>\n<p>ТR <a href=\"https:\/\/tr.ru\/news\/2471-shema-minskogo-metro-ot-ili-birmana-stala-predmetom-sporov-rossiyan-i-belorusov\">Minsk Metro Map from Ilya Birman became a subject of controversy.<\/a><\/p>\n<p>Village <a href=\"http:\/\/www.the-village.me\/village\/city\/news-city\/262187-birman-metro\">Ilya Birman developed the Minsk metro scheme with errors.<\/a><\/p>\n<p>Village <a href=\"http:\/\/www.the-village.me\/village\/city\/situation-city\/262193-birman-explain\">Ilya Birman will correct errors in the Minsk metro scheme.<\/a><\/p>\n<p>Citydog <a href=\"https:\/\/citydog.by\/post\/zaden-shema-metro\/\">Designers have developed an alternative scheme of the Minsk metro.<\/a><\/p>\n<p>International Science Forum. <a href=\"http:\/\/www.conf.art-gzhel.ru\">The effective approach for classification of electronic sales.<\/a><\/p>\n<p>Communication in Social Human Knowledge, Economics, & Education. <a href=\"http:\/\/elib.bsu.by\/handle\/123456789\/151651\">Materials 4th International scientific-practical conference. Infographic as effective tool for content-marketing.<\/a><\/p>\n<p>KYKY <a href=\"https:\/\/kyky.org\/special-project\/proveryaem-teoriyu-sapozhnik-bez-sapog-na-chyom-ezdyat-lyudi-kotorye-delayut-avtomobilnyy-sayt\">What do people who make a car site drive.<\/a><\/p>\n<p>KYKY <a href=\"http:\/\/kyky.org\/news\/dizaynery-narisovali-alternativnyy-variant-shemy-minskogo-metro\">Designers have drawn an alternative version of the Minsk metro scheme.<\/a><\/p>\n",
            "date_published": "2021-07-08T22:18:53+00:00",
            "date_modified": "2025-03-14T12:02:10+00:00",
            "_date_published_rfc2822": "Thu, 08 Jul 2021 22:18:53 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "152",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": []
            }
        }
    ],
    "_e2_version": 3849,
    "_e2_ua_string": "E2 (v3849; Aegea)"
}