{
    "version": "https:\/\/jsonfeed.org\/version\/1",
    "title": "ivan's blog: posts tagged casestudy",
    "_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": "https:\/\/ivanzviahin.by\/blog\/user\/userpic-square@2x.jpg?1711411913",
    "_itunes_explicit": "no",
    "home_page_url": "https:\/\/ivanzviahin.by\/blog\/tags\/casestudy\/",
    "feed_url": "https:\/\/ivanzviahin.by\/blog\/tags\/casestudy\/json\/",
    "icon": "https:\/\/ivanzviahin.by\/blog\/user\/userpic@2x.jpg?1711411913",
    "author": {
        "name": "Ivan Zviahin",
        "url": "https:\/\/ivanzviahin.by\/blog\/",
        "avatar": "https:\/\/ivanzviahin.by\/blog\/user\/userpic@2x.jpg?1711411913"
    },
    "items": [
        {
            "id": "193",
            "url": "https:\/\/ivanzviahin.by\/blog\/all\/feed\/",
            "title": "New feed entry point · Tinkoff",
            "content_html": "<p>How we made the personal feed in the bank app more readable by increasing 1-week feed retention rate several times over.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/feedmain.jpg\" width=\"2560\" height=\"1918\" alt=\"\" \/>\n<\/div>\n<p><a href=\"https:\/\/apps.apple.com\/RU\/app\/id455652438\">Tinkoff<\/a> is an online ecosystem or super app based on financial and lifestyle services. The best mobile privetely-held bank in the world according to Global Finance. The third largest bank in the CIS with 30,000,000 customers.<\/p>\n<p>A personal feed is a product. With the help of which we are building a communication platform where people learn all about finance, save money and have fun. Businesses need a personal feed to sell financial products through it. Users need to have fun, learn something new, be part of an expert community. In simple words, it’s just a feed of events and news.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-old.jpg\" width=\"2541\" height=\"2031\" alt=\"\" \/>\n<\/div>\n<p>The personal feed is having a positive impact. We test disabling the feed on new users and compare metrics across our products. There has been a drop in metrics, including cashback, bonuses and airline tickets. The product is working well, but we need to make it more efficient.<\/p>\n<p>The feed is in a difficult-to-reach place on the interface. To get to it, you have to open the “City” tab, which doesn’t tell you what’s on there. You have to look at a complicated screen and open the bottom sheet with the feed.<\/p>\n<p>People say the feed is hard to find. If people can’t access the feed, they won’t come back. If they don’t come back, they won’t use the product.<\/p>\n<p>By comparison, the stories on the home screen get visited several times more often and people come back more often, even though both are feeds with content, just in different formats.<\/p>\n<h2>Problem for users<\/h2>\n<p>We want to make the feed accessible. To make you more likely to open the feed on the mobile app. It’s heavily hidden at the moment.<\/p>\n<h2>Problem for business<\/h2>\n<p>Increase retention rate in the feed. If we increase the retention rate in the feed, customers will be more engaged with our products. If customers use more products, the bank will make more money.<\/p>\n<h2>Audience<\/h2>\n<p>The audience is very wide and diverse. But we aimed at all our bank users with an active lifestyle. I can’t share the audience of the personal feed, but it makes up the majority of the total number of customers. Considering that we have 30,000,000 customers, the scale of the product is confirmed. Wow!<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-audience-dia-3.jpg\" width=\"2541\" height=\"873\" alt=\"\" \/>\n<\/div>\n<h2>Success criteria<\/h2>\n<p>↑ 1-week feed retention rate<br \/>\n↑ 1-week app retention rate<br \/>\nWe also need to keep people engaged in the feed, which will be difficult.<\/p>\n<h2>Discovery<\/h2>\n<p>We’re looking for a solution in other products, but we haven’t found any yet. So, we’ll have to come up with a solution ourselves. We looked at what our users had to say. We’ve put together a job spec for a Data Analyst. But...<\/p>\n<p>But I find interesting is this. It’s not just about moving the feed. How do you get people to go there? The analysis shows us this:<\/p>\n<ol start=\"1\">\n<li>We already have a big audience that goes to the bank every day. We just need to put the feed on the home screen and get people interested.<\/li>\n<li>We already have content on the home page in the form of Stories, which is a great product.<\/li>\n<\/ol>\n<p>So, what we have<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-2.jpg\" width=\"2541\" height=\"579\" alt=\"\" \/>\n<\/div>\n<p>This scheme helped us make some guesses.<\/p>\n<h2>Hypothesis formulation and low-fi prototypes<\/h2>\n<p>These are the hypotheses.<\/p>\n<ol start=\"1\">\n<li><b>Main screen.<\/b> Adding the feed to the home screen will make it easier to access and more likely to be used.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1.jpg\" width=\"2541\" height=\"1923\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>We had many more options than I’m going to show you. I’ll show you the best ideas and how they look. I thought the best idea was to put content in a separate tab.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1-1.jpg\" width=\"2541\" height=\"1878\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>We stopped because we realised it was unrealistic to expect people to read content on secondary screens in the bank. We tried adding stories to secondary screens. It doesn’t work. Right, let’s move on.<\/li>\n<\/ul>\n<ul>\n<li>The second idea was to just put the feed under all the accounts, as there aren’t that many of them on average.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1-2.jpg\" width=\"2541\" height=\"1878\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>We saw that people don’t scroll past the second screen. How can we open it from the first screen? We added a right swipe option.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1-3.jpg\" width=\"2541\" height=\"1878\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>It’s cool, but it looks complicated. It’s not natural. Turn the story feed into a smart widget.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1-4.jpg\" width=\"2541\" height=\"1878\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>Interesting idea, but we don’t have the guts to do it. There’s a big risk we’d mess up the stories and it’d all fall apart. But on day five, we had a brainwave...<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1-5.jpg\" width=\"2541\" height=\"1878\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>It’s much more straightforward to swipe down than to swipe right. Pull to refresh is no longer necessary as all the data is updated in real time. It seems to be the best idea, so we’ve decided to go with it. And opening quick tools works the same way in iOS, which gave us the green light to go ahead with it.  We showed this idea to everyone who was interested: the product managers, the designers and the stakeholders of the home screen. We got a few doubts in response, but everyone was generally on board with this solution. We gave this to user testing, and we were pleased with the results. Let’s consider some other possibilities.<\/li>\n<\/ul>\n<ol start=\"2\">\n<li><b>Interest.<\/b> Make an entry point interesting to increase its open and retention rate.<\/li>\n<\/ol>\n<ul>\n<li>The simplest way to get people interested is to create an information trigger on the outside. I think stories are probably the best trigger, but it’s tricky to make stories and a feed one platform. It’ll probably be a separate story soon.<\/li>\n<li>But for now, we just need something simple. And here’s the thing: if you’ve been keeping up with our content, you’ll have noticed that we recently added a <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/news-card\/\">news card in the feed.<\/a> It would be great to take the most interesting words from the introductory text and put them outside.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i2.jpg\" width=\"2541\" height=\"1809\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>Let’s move on to the next item on the agenda.<\/li>\n<\/ul>\n<ol start=\"3\">\n<li><b>Clear.<\/b> Make the opening of the feed simple and clear to increase accessibility.<\/li>\n<\/ol>\n<ul>\n<li>Somehow we have to teach people how to use the new feed. At first we tried to come up with some kind of detailed training, but then we realised that the easiest way to do was to just pull the feed a few times. And stop when the person has done it.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i3.jpg\" width=\"2541\" height=\"1968\" alt=\"\" \/>\n<\/div>\n<ol start=\"4\">\n<li><b>Habit.<\/b> If we don’t change user habits, we’ll keep old stuff.<\/li>\n<\/ol>\n<ul>\n<li>Some people use the current feed the old way. We shouldn’t break their habit. Let’s add a history button. This is about the new way to access the feed. Don’t show it for a long time. If the user opens the feed, we’ll remove the button.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i4.jpg\" width=\"2541\" height=\"1833\" alt=\"\" \/>\n<\/div>\n<ol start=\"5\">\n<li><b>Additional entry points.<\/b> Finding more entry points will increase availability.<\/li>\n<\/ol>\n<ul>\n<li>When we spoke with users we found something interesting. When people contact the support team (chat) they go to watch stories on the home screen because they’re afraid to close the app (in general!!!). We must find a way to deal with these situations. This could affect how accessible the feed is.<\/li>\n<\/ul>\n<ul>\n<li>We knew this idea wouldn’t make it into the first version, so we didn’t make a prototype. But you can imagine it in your mind.<\/li>\n<\/ul>\n<h2>Priority<\/h2>\n<p>I met with the product manager and engineers to estimate the hypotheses according to two parameters: business value and technical complexity. We made a list of priorities.<\/p>\n<ol start=\"1\">\n<li><b>Main screen.<\/b> Adding the feed to the home screen will make it easier to access and more likely to be used.<\/li>\n<\/ol>\n<ul>\n<li>∞ ⁄ 5 = ∞<\/li>\n<\/ul>\n<ol start=\"2\">\n<li><b>Interest.<\/b> Make an entry point interesting to increase its open and retention rate.<\/li>\n<\/ol>\n<ul>\n<li>3 ⁄1 = 3<\/li>\n<\/ul>\n<ol start=\"3\">\n<li><b>Clear.<\/b> Make the opening of the feed simple and clear to increase accessibility.<\/li>\n<\/ol>\n<ul>\n<li>3\/1 = 3<\/li>\n<\/ul>\n<ol start=\"4\">\n<li><b>Habit.<\/b> If we don’t change user habits, we’ll keep old stuff.<\/li>\n<\/ol>\n<ul>\n<li>3 ⁄ 2 = 1.5<\/li>\n<\/ul>\n<ol start=\"5\">\n<li><b>Additional entry points.<\/b> Finding more entry points will increase availability.<\/li>\n<\/ol>\n<ul>\n<li>4 ⁄ 4 = 1<\/li>\n<\/ul>\n<h2>Scoping<\/h2>\n<p>We break down our ideas into iterations to get the product to users quickly and make sure it’s perfect.<\/p>\n<p><i>Iteration 1<\/i><\/p>\n<ul>\n<li><b>Main screen.<\/b> If we make the feed on the home screen, it will increase its accessibility and retention rate. This is our main idea, we will  make it.<\/li>\n<li><b>Interest.<\/b> Make an entry point interesting to increase its open and retention rate. I really want to do it at once, so that it will be the cherry on the cake. But if we don’t have time, we’ll put it in a separate iteration. Of course, it will be an ab-test to understand the impact of this particular idea.<\/li>\n<\/ul>\n<p><i>Next iterations<\/i><\/p>\n<ul>\n<li><b>Clear.<\/b> Make the opening of the feed simple and clear to increase accessibility. Let’s test it separately, in case this problem doesn’t exist and it is clear and simple without some additional activities.<\/li>\n<li><b>Habit.<\/b> If we don’t change user habits, we’ll keep old stuff. Important stuff. But we’ll run the first iteration only for new users and if everything is good there, we’ll make this idea and publish an update for everyone.<\/li>\n<li><b>Additional entry points.<\/b> Finding more entry points will increase availability. Oh, it’s definitely a contender to make it out of the first round!<\/li>\n<\/ul>\n<p>— Let’s go!<\/p>\n<h2>Iteration 1 · hi-fi<\/h2>\n<p>I just wanted to point out that our lo-fi prototypes already sounded pretty hi-fi. Having said that, we didn’t come across any major technical issues. So, all the ideas from the concepts made it through to the hi-fi stage, which is pretty unusual.<\/p>\n<p>But the final solution was this. The feed on the main screen looks like a top sheet that you can open by swiping from the top to the bottom. Plus, we made it so you can just click on the dragger and text to open it. We figured this out during the UX tests, but we assumed it in advance.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-new.jpg\" width=\"2541\" height=\"2031\" alt=\"\" \/>\n<\/div>\n<p>Above the dragger is a shortened descriptor from the feed, which changes every day along with the full descriptor inside the feed. You can read about this in the case study about <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/news-card\/\">the news card.<\/a><\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-new2.jpg\" width=\"2541\" height=\"1860\" alt=\"\" \/>\n<\/div>\n<p>Just then, Sergei Egorov came along. The second designer to join us. I needed to move on to other things. Sergei took the reins as the second designer on the project. The second half of the work on the final layouts is creating animations of opening and closing the feed. Based on my prototype, Sergei put together a much more detailed one with a description of all the details.<\/p>\n<p>To close the feed, just hit the close button or swipe down. When we were testing it out, we realised that we needed to make closing by swiping up, so that it’s the reverse of opening. This meant there were three ways to close the feed in total. This way, everyone would know how it worked.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-new3.jpg\" width=\"2541\" height=\"2031\" alt=\"\" \/>\n<\/div>\n<p>We had to get the most complex interactive feature in the Tinkoff app up and running at the time, which was a big challenge for the whole team. It was pretty straightforward to develop the animation and the feed itself on Android, but we hit a few snags on iOS. But we managed to get around all those limitations in the end. Sometimes we had to switch up our strategy and come up with quick fixes, so Sergei spent a lot of evenings with the engineers. Sergei says,<\/p>\n<ul>\n<li><i>“We often sat with the engineers late into the night tweaking details and catching endless bugs together. I even picked up a few lines of code in Xcode.”<\/i><\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-serg.jpg\" width=\"2541\" height=\"1992\" alt=\"\" \/>\n<\/div>\n<p>At some point, we got everything to a state that could be called a release state. And it was so lovely to see that happen!<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/feedmain.jpg\" width=\"2560\" height=\"1918\" alt=\"\" \/>\n<\/div>\n<h2>First launch and results<\/h2>\n<p>We released it as an AB test for a new audience. At the same time, we ran a separate AB test on the description. Here’s what we found out.<\/p>\n<ol start=\"1\">\n<li>We saw a big jump in the number of people who stuck around and checked out the feed on a weekly basis (1-week feed retention rate).<\/li>\n<li>The percentage of users accessing the feed on the app shot up several times. This indicator saw a nice increase, even if it couldn’t help but grow.<\/li>\n<li>The engagement rate of the feed saw a slight decrease. This is because more people are now entering the feed, but the quality of these users has dropped. They’re not as active as they could be. We’ll be addressing this in the next episodes.<\/li>\n<li>There was no change to the weekly retention rate of the app, statistically speaking. We were disappointed, but not overly so. It’s really difficult to make changes.<\/li>\n<li>The descriptor did the job. Without it, the retention and open rates in the feed were lower.<\/li>\n<\/ol>\n<p>I’m happy to say that we met our goals, and we’re all proud of that.<\/p>\n<h2>Role and platforms<\/h2>\n<ul>\n<li>I participated in the formulation and confirmation of the problem together with the product manager.<\/li>\n<li>I did the primary research.<\/li>\n<li>I formulated hypotheses and participated in prioritization together with the product manager and engineers.<\/li>\n<li>Together with the manager, we divided all the hypotheses into iterations.<\/li>\n<li>I designed lo-fi and and first part of hi-fi mockups and described the requirements together with the technologists and engineers.<\/li>\n<\/ul>\n<p>Half of the layouts and animations were designed by Sergei Egorov. He joined us in the middle of the project as the second designer. Sergei helped QA engineers to run all the flow and described bugs.<\/p>\n<p>Basically, all solutions work on android and iOS.<\/p>\n<h2>Reflection<\/h2>\n<p>I think the first version of the personal feed opening could have been made much simpler, but it’s great that we overestimated the requirement at the start and made the transition above the level of the traditional design approach in the company. I’m really proud of this little project. See you in the next episodes, thank you!<\/p>\n<h2><a href=\"https:\/\/telegra.ph\/Kak-my-zatashchili-personalnuyu-lentu-na-glavnyj-ehkran-mobilnogo-banka-i-povysili-metriki-v-3-raza-04-13\">Story about the same, but from Sergei, only in Russian<\/a><\/h2>\n",
            "date_published": "2024-08-26T22:36:06+00:00",
            "date_modified": "2024-10-01T15:07:17+00:00",
            "image": "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-audience-dia-2.jpg",
            "_date_published_rfc2822": "Mon, 26 Aug 2024 22:36:06 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "193",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-audience-dia-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/feedmain.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-old.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-audience-dia-3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1-1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1-3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1-4.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i1-5.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-i4.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-new.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-new2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-new3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-feed-serg.jpg"
                ]
            }
        },
        {
            "id": "186",
            "url": "https:\/\/ivanzviahin.by\/blog\/all\/pd-job-pathways\/",
            "title": "Design career paths",
            "content_html": "<p>How we made design career paths and criteria for transition from one role to another for designers and got an effective tool to make a personal development plan. Additionally, we helped designers understand how they can develop and what level they are at now.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cm-map.jpg\" width=\"2434\" height=\"2560\" alt=\"\" \/>\n<\/div>\n<h2>Intro<\/h2>\n<p>A classic problem in a design team is that designers need to become managers in order to grow their careers. And we faced this problem too. Before some changes, each designer could only develop along one track: from middle to senior, and then please only go to management. After all, this was the only way for a designer to feel career growth and start earning more.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cm-asis.jpg\" width=\"2526\" height=\"615\" alt=\"\" \/>\n<\/div>\n<p>That’s not cool, especially when we started running into situations where experienced designers don’t want to become managers. They want to be experts and grow further as designers, not peоple managers. There were two such cases in my time. Necessary to change something and we formulated the problem.<\/p>\n<h2>Problem<\/h2>\n<ol start=\"1\">\n<li>Designers don’t understand how they can grow in their career path. Plus they don’t understand what level they are at now.<\/li>\n<li>From team to team, designers have different development plans, and some have none at all, or they have them, but not about development.<\/li>\n<li>Designers think they can earn more and grow only if they become people managers.<\/li>\n<\/ol>\n<p>We conducted a survey of three questions. We collected more than 35 answers. The results confirmed the problems described above. The survey could not have been conducted, it was enough that this problem was confirmed by design managers. But it’s better to be sure than to make a mistake.<\/p>\n<p>Additionally, we suspected that many experienced designers go into people-management, burn out and quit afterward. We couldn’t confirm this because of the difficulty of collecting reliable data.<\/p>\n<h2>Criteria for success and audience<\/h2>\n<p>Quantitative survey shows that designers <b>understand how they can grow<\/b>, where they are now, and where they aspire to go in the future. All designers <b>have a personalized development plan<\/b> and are aligned together.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cm-audience-(1).jpg\" width=\"2560\" height=\"1240\" alt=\"\" \/>\n<\/div>\n<p>The problem was solved within the Tinkoff Bank company, which is more than 200 designers of different levels and specializations. Graphic, interface, communication designers.<\/p>\n<h2>Actions<\/h2>\n<p>Obviously, we need some kind of explicitly described path-map that explains to designers how to develop. What were my actions?<\/p>\n<ol start=\"1\">\n<li>I researched how other companies do it.<\/li>\n<li>I looked for similar problems on the internet. There are plenty of them too.<\/li>\n<li>I called 4 design and not only design managers from other companies for an interview to share how it’s done.<\/li>\n<\/ol>\n<p>I analyzed the results and finally realized that there are different development tracks: people-manager track and individual contributor track. We can also build something similar.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cm-tobe.jpg\" width=\"2526\" height=\"798\" alt=\"\" \/>\n<\/div>\n<p>But a path-map is not enough, we need something that will help us evaluate the designer and hint how we can develop further.<\/p>\n<p>I don’t believe in schemes where everything is described in detail: what books to read, what courses to take, something else to do. Because I haven’t come across a single successful case where it worked. Plus I have tried to build such schemes myself before and it is very difficult and expensive to keep such schemes up to date. Moreover, it turns out in reality that it is not necessary.<\/p>\n<p>As it turns out, each person is individual and the situation is also individual. We just need some role boundaries and growth criteria. Then it’s a matter of the specific situation and communication between the designer and his manager. The main thing is that development plans should include not work tasks, but actions that will help the designer to grow as a specialist.<\/p>\n<p>We need to make<\/p>\n<ol start=\"1\">\n<li>Design career paths<\/li>\n<li>Criteria for transition from one role to another<\/li>\n<\/ol>\n<h2>1. Design career paths<\/h2>\n<p>Sooo, paths. I want to remove some of the legalities. We have done dozens of iterations and the result is this one. It’s perfect for me. Design career paths edited due to the fact that I had to hide sensitive information.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cm-map.jpg\" width=\"2434\" height=\"2560\" alt=\"\" \/>\n<\/div>\n<p>The most popular question was this. What is the difference between a design lead and an expert designer? There is no difference between the roles, they are both the same level of knowledge specialists. There is a difference in focus.<\/p>\n<p><b>Expert designer focus are future, conceptual design, product vision, design strategy, interface quality, visual language. Design lead are process, x-communication, reward and recognition, performance, underperformance, hiring. Everything else is common.<\/b><\/p>\n<h2>2. Criteria for transition<\/h2>\n<p>Everything is clear with career paths, now we need to somehow understand what are the criteria for transition from one role to another. 60% of all criteria I wrote based on my expert opinion, 40% I looked up something in other companies. We did more than 20 iterations to improve the structure and content. Showed the map to design leaders, collected feedback. Selectively showed it to designers in 1-on-1 meetings.<\/p>\n<p>After the final collection of feedback we realized that some criteria are not clear to designers, but for the sake of speed we simplified the description and came up with a scheme where we will describe the criteria in detail in separate articles to be written by designers themselves. After the articles were written, we started adding links in the table as additional information and clarification.<\/p>\n<p>We chose the easiest format to launch the tool as early as possible and that’s Google Docs.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cm-crit.jpg\" width=\"2526\" height=\"1644\" alt=\"\" \/>\n<\/div>\n<p>The criteria are clear, but how can a supervisor create a growth plan for designers? For this we came up with a simple method that consists of several steps.<\/p>\n<ol start=\"1\">\n<li>Make a copy of the table and make a separate page for each designer.<\/li>\n<li>Independently evaluate each designer for each point, for example from 1 to 3. I like coloring the table cells in shades of one color.<\/li>\n<li>Ask each of your designers to do the same thing independently. Let them also do this on their own. Then discuss the results 1 on 1 and combine these two tables into one.<\/li>\n<li>Choose the right development strategy, considering the interests of the designer and the team. Choose 1-3 most important growth points (not more!) and develop a plan. We trust mentors to decide specifically what needs to be done. Such issues are resolved personally and I don’t believe it can be formalized in any way. Each person is an individual and each person needs their own approach.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cm-crit-2.jpg\" width=\"2517\" height=\"1644\" alt=\"\" \/>\n<\/div>\n<p>Hurrah! The plans exist and now they do not consist only of work tasks. Furthermore, each manager now has at least one topic for discussion at 1-on-1 meetings to monitor the progress of each designer. It is on these meetings that progress needs to be supported.<\/p>\n<p>By the way, after all this, you can easily compare one designer with others and draw conclusions what portrait of the team as a whole. We tested it on five designers, made minor changes.<\/p>\n<h2>Launch<\/h2>\n<p>It seems like it’s time to implement. We needed to do it in a way that would get minimal resistance from the designers. I came up with a plan like this:<\/p>\n<ol start=\"1\">\n<li>Conduct a test development plan and conduct a criteria review for four designers selectively and gather feedback.<\/li>\n<li>Ask the lead designers to show design career paths and criteria in 1 on 1 meetings and collect feedback.<\/li>\n<li>Once changes are added, make a public announcement to the entire design department.<\/li>\n<li>Hold 2-3 public workshops.<\/li>\n<li>Make final edits.<\/li>\n<\/ol>\n<p>That’s exactly what we did. Bow!<\/p>\n<h2>Results<\/h2>\n<p>I went through more than 20 development plans. In the end, I saw clear development plans with growth points and no work tasks. This is a success, but we need to keep monitoring this further and add this to the onboarding of new designers.<\/p>\n<p>I conducted an anonymous survey among designers and got these results.<\/p>\n<div class=\"e2-text-table\">\n<table cellpadding=\"0\" cellspacing=\"0\" border=\"0\">\n<tr>\n<td><i>Issue<\/i><\/td>\n<td><i>Yes, %<\/i><\/td>\n<td><i>No, %<\/i><\/td>\n<\/tr>\n<tr>\n<td>You know about the competency map?<\/td>\n<td>81,8<\/td>\n<td>18,2<\/td>\n<\/tr>\n<tr>\n<td>Do you understand how you can develop in the company as a whole?<\/td>\n<td>83,4<\/td>\n<td>16,6<\/td>\n<\/tr>\n<tr>\n<td>Do you know what you need to develop in yourself to move further along your career path?<\/td>\n<td>78,8<\/td>\n<td>21,2<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<h2>Next steps<\/h2>\n<p>I plan to collect feedback and make improvements. If the topic takes root, make it more convenient in a separate software that is being developed by the internal product team in the company. Separately write detailed articles on different topics from the criteria and insert links in the table with the criteria. I want these articles to be written by the designers themselves.<\/p>\n<h2>Role and reflection<\/h2>\n<p>I was the owner of this project, so I made career paths and criteria myself, but with the help of a huge number of our designers. My manager validated the directions of thought. Special thanks to the design managers and designers who implemented it all to themselves and wrote feedback. I take my hat off to you all.<\/p>\n<p>I didn’t come up with anything new. But I am proud that I was able to convince everyone and implement  it in such a big company. I am proud of the work we have done together. See you in the next episodes, thank you!<\/p>\n<h2><a href=\"https:\/\/drive.google.com\/file\/d\/1_kk4OkFfXh0nPcU9JdWV0b4sBhPWmmG5\/view?usp=sharing\">Poster, PDF 3.4 MB<\/a><\/h2>\n",
            "date_published": "2023-11-16T22:35:39+00:00",
            "date_modified": "2024-01-31T22:08:13+00:00",
            "image": "https:\/\/ivanzviahin.by\/blog\/pictures\/cm-map.jpg",
            "_date_published_rfc2822": "Thu, 16 Nov 2023 22:35:39 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "186",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cm-map.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cm-asis.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cm-audience-(1).jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cm-tobe.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cm-crit.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cm-crit-2.jpg"
                ]
            }
        },
        {
            "id": "191",
            "url": "https:\/\/ivanzviahin.by\/blog\/all\/comments\/",
            "title": "Comments in stories",
            "content_html": "<p>I’d like to share a story about how we made a comments in stories. By doing so, we increased the number of stories read and the number of days in stories by 13%. I won’t describe the case in detail here, as it is described in <a href=\"https:\/\/telegra.ph\/Kak-my-vstroili-kommenty-v-istorii-mobilnogo-banka-Tinkoff-07-27\">great detail by Misha,<\/a> I will only share a few points.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-comments.jpg\" width=\"2560\" height=\"1796\" alt=\"\" \/>\n<\/div>\n<p>Tinkoff is an online ecosystem or super app based on financial and lifestyle services. The best mobile privetely-held bank in the world according to Global Finance. The third largest bank in the CIS with 30,000,000 customers.<\/p>\n<h2>Situation and challenge<\/h2>\n<p>We need to sell financial products in some way, this is the company’s main income. In order to do this more effectively, we talk about financial products in stories. Consequently, engagement in these stories has a positive effect on sales. That’s why we decided to make a comments module as a tool for engaging in our stories. At the same time, we conducted research and made sure that people want to be involved in the community, to share their opinions, to ask questions.<\/p>\n<h2>Actions<\/h2>\n<p>We did a simple discovery. Analyzed similar products, analyzed similar solutions within Tinkoff and did a desk study of benchmarks. In the end we have 6 hypotheses, prioritized them and took the first two hypotheses in the first iteration to cover all success criteria. As part of the first iteration, made hi-fi mockups and tested them. I’m not talking about a dozen approaches, how the comments could look like, it’s all <a href=\"https:\/\/telegra.ph\/Kak-my-vstroili-kommenty-v-istorii-mobilnogo-banka-Tinkoff-07-27\">described in detail by Misha.<\/a><\/p>\n<h2>Results<\/h2>\n<p>At the beginning of September we launched AB test. A few weeks later, we go into analytics, and the number of comments there has increased 70 times in relation to the previous weeks. What is the reason? Comments were enabled on Junior users (kids under 14). They made this feature monumental.<\/p>\n<p><b>Total number of stories read increased by 12.9% and number of days by 13.2%<\/b><\/p>\n<p>And these are the results of adult clients, in children it is 2-3 times higher, but we don’t include children in the results for obvious reasons. The role of designer was performed by Misha Naer. I played the role of the head of the design process. And these are the results of the first iteration, further on it will be more interesting. See you in the next episodes, thank you!<\/p>\n",
            "date_published": "2023-09-04T21:53:32+00:00",
            "date_modified": "2023-09-12T23:25:52+00:00",
            "image": "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-comments.jpg",
            "_date_published_rfc2822": "Mon, 04 Sep 2023 21:53:32 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "191",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-comments.jpg"
                ]
            }
        },
        {
            "id": "185",
            "url": "https:\/\/ivanzviahin.by\/blog\/all\/news-card\/",
            "title": "News card in personal feed · Tinkoff",
            "content_html": "<p>How we made a news card in the feed and increased CTR of first card by 32%, 1-week retention rate of the feed by 8%, open rate by 4% and engagement rate by 35%.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-new-sexy-feed.jpg\" width=\"2560\" height=\"2005\" alt=\"\" \/>\n<\/div>\n<p><a href=\"https:\/\/apps.apple.com\/RU\/app\/id455652438\">Tinkoff<\/a> is an online ecosystem or super app based on financial and lifestyle services. The best mobile privetely-held bank in the world according to Global Finance. The third largest bank in the CIS with 30,000,000 customers.<\/p>\n<p>A personal feed is a product. With the help of which we are building a communication platform where people learn all about finance, save money and have fun. Businesses need a personal feed to sell financial products through it. Users need to have fun, learn something new, be part of an expert community. In simple words, it’s just a feed of events and news.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-old-feed.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<h2>Problem for users<\/h2>\n<p>Analyzing different types of cards and collections, we noticed an increase in interest in news cards, especially when we combine them into collections. Based on this insight, we decided that we need to develop in this direction.<\/p>\n<p>Hence the problem — people want to be able to see an up-to-date selection of news based on their interests. They don’t want to collect this news in different places, they want to see it all at once. Most importantly, this was confirmed in a series of user interviews that were aimed at finding the answer “Why do users use the feed?”<\/p>\n<p>We decided that it needed to be checked somehow cheaply. And we collected a selection of news based on the type of card already available.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-with-news-old-card.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>After such an experiment, we noticed a significant increase (+24%) in the CTR of this card relative to the most popular card in this place. So we realized that we need to improve the user experience of this card and come up with maximum ways to engage a person.<\/p>\n<h2>Problem for business<\/h2>\n<p>We are always looking for ways to increase CTR with the feed cards. Because with the growth of CTR → engagement grows. With the growth of engagement, the loyalty of users grows, and with the growth of loyalty, the revenue from sales of our internal services grows.<\/p>\n<h2>Audience<\/h2>\n<p>The audience is very wide and diverse. But we aimed at all our bank users with an active lifestyle. I can’t share the audience of the personal feed, but it makes up the majority of the total number of customers. Considering that we have 30,000,000 customers, the scale of the product is confirmed. Wow!<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-audience-dia.jpg\" width=\"2541\" height=\"528\" alt=\"\" \/>\n<\/div>\n<h2>Success criteria<\/h2>\n<p>We will consider the success criterion to be CTR of this card, which will be higher than CTR of the news card from the experiment above (which means it will be higher than any other card in the first place of the feed).<\/p>\n<p>Additionally, we will look at the open and 1-week retention rate of the feed, because the first card will be visible in a hidden state.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-compare-was-willbe.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<h2>Discovery · Interview<\/h2>\n<p>Fortunately, quite by chance, we conducted a series of interviews with our users in parallel. We were trying to find an answer to the question of why users read the feed. We had a small product market fit, but we didn’t understand exactly why it happened.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-interview.jpg\" width=\"2526\" height=\"1551\" alt=\"\" \/>\n<\/div>\n<p>Total 19 in-depth interviews. The latest news got into the top 3 insights. This confirms our initial insight. In addition, we realized that we need to recommend news in a personalized format and give only a selection of headlines.<\/p>\n<h2>Discovery · Analysis of similar products<\/h2>\n<p>Next, we went to see how different products aggregate different information into a card. Here we found some interesting ideas.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-similar-products.jpg\" width=\"2526\" height=\"1413\" alt=\"\" \/>\n<\/div>\n<p>First, almost all cards with no more than four lines of content. If more, then do a horizontal scroll. Secondly, it is important to understand the date of publication, how new the material is. Third, currency exchange rates and investment stickers look cool together with a selection of news as a single widget. Fourth, the introductory description, as an engagement tool, creates the effect of personalization. Additionally a personal address by name attracts a lot of attention. (everyone already knows that)<\/p>\n<h2>Wow! As a result, we had a lot of ideas. We have described them in the form of hypotheses below<\/h2>\n<h2>Hypothesis formulation and low-fi prototypes<\/h2>\n<p>Now the card is colored and we know that this is important. When the feed is hidden, a piece of the card is visible and it attracts attention. We decided not to experiment with this and further considered it only in color.<\/p>\n<ol start=\"1\">\n<li><b>Dates.<\/b> If we display the publication dates of articles, it may affect card CTR.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-dates.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<ol start=\"2\">\n<li><b>Pictures.<\/b> If we add pictures to the news, it may affect card CTR.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-pic.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<ol start=\"3\">\n<li><b>Personalisation.<\/b> If we display news based on user interests, it may affect CTR and retention rate.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-pers.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<ol start=\"4\">\n<li><b>Name.<\/b> If we contact to you personally, it may affect feed open rate.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-name.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<ol start=\"5\">\n<li><b>Introductory text.<\/b> If we write a humorous introductory text, it may affect retention rate.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-text.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<ol start=\"6\">\n<li><b>Currency rates.<\/b> If we display currency rates and share price, it may affect retention rate.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-rates.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<h2>Priority<\/h2>\n<p>I set up a meeting with the product manager and engineers to estimate all hypotheses according to two parameters: technical complexity of the implementation (from 1 to 5) and business value (from 1 to 5). We divided one into the other and got an hi-level prioritisation coefficient. So...<\/p>\n<p><i>Card CTR <\/i><\/p>\n<ul>\n<li><b>Dates.<\/b> If we display the publication dates of articles, it may affect card CTR.<br \/>\n3 ⁄ 1 = 3<\/li>\n<li><b>Pictures.<\/b> If we add pictures to the news, it may affect card CTR.<br \/>\n3 ⁄ 1 = 3<\/li>\n<li><b>Personalisation.<\/b> If we display news based on user interests, it may affect card CTR and retention rate.<br \/>\n5 ⁄ 5 = 1<\/li>\n<\/ul>\n<p><i>Open rate<\/i><\/p>\n<ul>\n<li><b>Name.<\/b> If we contact to you personally, it may affect open rate.<br \/>\n3 ⁄ 1 = 3<\/li>\n<\/ul>\n<p><i>Retention rate<\/i><\/p>\n<ul>\n<li><b>Introductory text.<\/b> If we write a humorous introductory text, it may affect retention rate.<br \/>\n3 ⁄ 2 = 1.5<\/li>\n<li><b>Currency rates.<\/b> If we display currency rates and share price, it may affect retention rate.<br \/>\n2 ⁄ 2 = 1<\/li>\n<\/ul>\n<h2>Scoping<\/h2>\n<p>We divide all into iterations in order to deliver a valuable product as quickly as possible. We focus on three metrics card CTR, retention rate and feed open rate. Therefore, we can take one hypothesis for each metric in each iteration. Of course, we understood that they could influence each other, but speed is more important.<\/p>\n<p><i>Iteration 1<\/i><br \/>\nWe definitely make a news card with dates right away. We had a dispute about the pictures, the product manager believed that it would work better without pictures. We agreed on an AB test. Additionally, we will take the appeal by name, since it affects another metric.  We do not take hypotheses aimed at retention rate in the first iteration due to the fact that they are complex, and we want to deliver value as early as possible.<\/p>\n<ul>\n<li><b>Dates.<\/b> If we display the publication dates of articles, it may affect card CTR.<\/li>\n<li><b>Pictures.<\/b> If we add pictures to the news, it may affect card CTR.<\/li>\n<li><b>Name.<\/b> If we contact to you personally, it may affect open rate.<\/li>\n<\/ul>\n<p><i>Iteration 2<\/i><br \/>\nThe text-introduction will be launched separately. Potentially, this can affect the retention rate individually, it is interesting to check.<\/p>\n<ul>\n<li><b>Introductory text.<\/b> If we write a humorous introductory text, it may affect retention rate.<\/li>\n<\/ul>\n<p><i>Iteration 3<\/i><br \/>\nAfter that, we will add a widget with currency rates and investment tickers. It is also interesting to test them separately because this hypothesis is also aimed at the retention rate.<\/p>\n<ul>\n<li><b>Currency rates.<\/b> If we display currency rates and share price, it may affect retention rate.<\/li>\n<\/ul>\n<p><i>Iteration 4<\/i><br \/>\nNext, we try to personalize the news (a difficult thing), so in the end.<\/p>\n<ul>\n<li><b>Personalisation.<\/b> If we display news based on user interests, it may affect CTR and retention.<\/li>\n<\/ul>\n<p>— Let’s go!<\/p>\n<h2>Iteration 1 · hi-fi<\/h2>\n<p>We added only 4 news, it seems enough to start and looks easy. We tried to make the interface as simple as possible, we have already made mistakes with this many times in the collections. And there was an insight from users that they want to see all the current news in a list at once. We borrowed the algorithm from a web magazine, it is already ready there, current news.<\/p>\n<p>We had two options:<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-1-news.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>I chose the second option. It looks simpler and more aesthetically pleasing. Next...<\/p>\n<p>Added dates. There are not too many options for how this can be shown, so we made it as simple as possible. We already have a date display style in other cards.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-1-datesandrules.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>We enter the dates according to special rules that I have formed.<\/p>\n<div class=\"e2-text-table\">\n<table cellpadding=\"0\" cellspacing=\"0\" border=\"0\">\n<tr>\n<td><b>Have<\/b><\/td>\n<td><b>Show<\/b><\/td>\n<\/tr>\n<tr>\n<td>≤ 5 min<\/td>\n<td>just now<\/td>\n<\/tr>\n<tr>\n<td>< 1 hour<\/td>\n<td>56 min ago<\/td>\n<\/tr>\n<tr>\n<td>< 2 hours<\/td>\n<td>1 hour ago<\/td>\n<\/tr>\n<tr>\n<td>< 1 day<\/td>\n<td>23 hours ago<\/td>\n<\/tr>\n<tr>\n<td>< 2 days<\/td>\n<td>yesterday<\/td>\n<\/tr>\n<tr>\n<td>< 8 days<\/td>\n<td>6 days ago<\/td>\n<\/tr>\n<tr>\n<td>≥ 8 days<\/td>\n<td>18 february<\/td>\n<\/tr>\n<tr>\n<td>≥ 1 year<\/td>\n<td>18 february 2020<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>Added an appeal by name. I made it as simple as possible, using the available styles from other cards. That’s where we stopped.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-1-name.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>Added pictures. As I said before, we had disagreements on this, so it got into the first iteration, we will run them AB test. Option A without pictures, option B with pictures. We will show the card 50-50, we will look at the card CTR.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-1-abpics.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>That is all.<\/p>\n<p>We didn’t do any interface tests, because it seems to us that there is nothing to check here. I checked only the list of <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/self-checking-the-interface\/\">self-checking the interface.<\/a> So, it was → will be.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-1-willbe.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<h2>First launch and results<\/h2>\n<p>AB test results. At the first visit, users tap better on the news card without pictures. The relative uplift in CTR is 9%. It does not affect taps when re-entering. It does not affect the return to the feed. The card without pictures won, I cried :-(<\/p>\n<p>In general, first card CTR +8% (new format and dates) and feed open rate +4% (address by name). Cool! Let’s move on to the next iterations.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-role-3.jpg\" width=\"2526\" height=\"1527\" alt=\"\" \/>\n<div class=\"e2-text-caption\">This is a product manager, his name is Nikita. Nikita is glad that he won the AB test. He was for the option without pictures<\/div>\n<\/div>\n<p>Moving on!<\/p>\n<h2>Iteration 2 · hi-fi<\/h2>\n<p>Hello again! It’s time to work with the retention rate as part of the news card and we have an introductory text on this. The main idea is that we want to make an introductory text that will change every day. It should have a welcoming meaning.<\/p>\n<p>We strongly believe that the text should be humorous, this was confirmed in user interviews, people want something entertaining, a lot of sad things are happening in the world anyway. This can be a great reward for action.<\/p>\n<p>We have not found an editor resource that will write an introductory text every day for several days ahead. So I came up with and wrote them myself. I really want to test this.<\/p>\n<p>What might it look like? We didn’t want to come up with something new (so as not to complicate the idea of test) yet, so we took the text style from other cards as a basis and applied it in our news card. The main thing is that it should be readable, simple and understandable. We have reduced the number of articles to make it look easier visually. We removed the “current news” descriptor and moved it inside the introductory text to make it all look easier.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-2-text.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>An important learn that we found. We are well aware that it is ideal to use the hook model for the retention rate boost. And we even figured out how to do it. The reason is the position of the feed in the app and the policy of contacts to send push messages. We promised ourselves to try it after moving the feed to a more accessible place in the app. But about this in another story.<\/p>\n<p>While we design a text, another idea came up. What if we ask some interesting question in the introductory text, and somewhere in the middle of the feed we give an answer in the form of a story card. If we use the story card, we won’t need to develop anything additionally – perfect for the test. It seems that in addition to the retention rate, we can influence the engagement rate of the feed.<\/p>\n<p><b>feed engagement rate = (user tap + like + bookmark + share + swipe) \/ all users × 100%<\/b><\/p>\n<p>The idea should work because people will look for an answer, react to it and get involved in other content. Sounds interesting?<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-2-story.jpg\" width=\"2526\" height=\"1776\" alt=\"\" \/>\n<\/div>\n<p>Sure! Sounds interesting. So, it was and will be. Of course, guys, we started with an AB test to understand the impact of the second iteration on the result.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-2-willbe.jpg\" width=\"2526\" height=\"1731\" alt=\"\" \/>\n<\/div>\n<h2>Second launch and results<\/h2>\n<p>In general, feed 1-week retention rate +8% (introductory text with a question and answer) and feed engagement rate +35% (introductory text with a question and answer). It’s hard to understand why it affected engagement so much, but I like it. The test did not affect the CTR of the first card and the open rate in any way, which is also important.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-2it.jpg\" width=\"2541\" height=\"528\" alt=\"\" \/>\n<\/div>\n<h2>Iteration 3 and 4 · not done<\/h2>\n<p>An interesting thing happened, we decided to redo the concept of the feed as a whole and separate the news selection from the text and the address by name. The introductory text and the appeal should become part of the feed itself and be independent, but that’s another story.<\/p>\n<p>So, we have postponed working with currency exchange rates and personalisation. But I want to show you the layouts and developments on these tasks, they should not be lost. We will return to them later, but in another story.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/pic-34.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<h2>Role and platforms<\/h2>\n<p>I participated in the formulation and confirmation of the problem together with the product manager. I communicated with analysts to find out insides. I participated in user interviews and analysis of similar products. The research team helped me a lot, thanks to them.<\/p>\n<p>I formulated hypotheses and participated in prioritization together with the product manager and engineers. Together with the manager, we divided all the hypotheses into iterations. I designed lo-fi and hi-fi mockups and described the requirements together with the technologists and engineers. I helped QA engineers to run all the flow and described bugs. I wrote dozens of introductory texts for the news card. Basically, all solutions work on android and iOS.<\/p>\n<h2>Reflection and final results<\/h2>\n<p>Although the results cannot be called super-high, but they can be called real.<br \/>\nWe achieved:<\/p>\n<ul>\n<li>first card CTR without development +24%<\/li>\n<li>first card CTR with development +8%<\/li>\n<li>feed open rate +4%<\/li>\n<li>feed 1-week retention rate +8%<\/li>\n<li>feed engagement rate +35%<\/li>\n<\/ul>\n<p>I would certainly like more. Unfortunately, we couldn’t do all the planned iterations, but it was influenced by external factors. Plus, in the second iteration, it was hard for me to throw out the subscription model. But we understood that it was too early to give such functionality, the card does not take into account interests.<\/p>\n<p>The story looks real and confirms the theory of <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/process-story\/\">my design process,<\/a> which works in practice. Next time we’ll try to do more iterations. See you in the next episodes, thank you!<\/p>\n<p>Here I’m telling the same story, only live:<\/p>\n<div class=\"e2-text-video\">\n<iframe src=\"https:\/\/www.youtube.com\/embed\/Brz_XeX-wAQ?enablejsapi=1\" allow=\"autoplay\" frameborder=\"0\" allowfullscreen><\/iframe>\n<div class=\"e2-text-caption\">Don’t forget to turn on the subtitles, this presentation is in English and I’m speaking in my native language<\/div>\n<\/div>\n",
            "date_published": "2023-03-21T20:31:00+00:00",
            "date_modified": "2024-07-18T22:34:26+00:00",
            "image": "https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-color.jpg",
            "_date_published_rfc2822": "Tue, 21 Mar 2023 20:31:00 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "185",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [
                    "system\/library\/jquery\/jquery.js",
                    "system\/library\/media-seek\/media-seek.js"
                ],
                "og_images": [
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-color.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-1-platforms-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-new-sexy-feed.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-old-feed.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-with-news-old-card.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-audience-dia.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-compare-was-willbe.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-interview.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-similar-products.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-dates.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-pic.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-pers.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-name.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-text.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/lofi-rates.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-1-news.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-1-datesandrules.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-1-name.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-1-abpics.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-1-willbe.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-role-3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-2-text.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-2-story.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-2-willbe.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-2it.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/pic-34.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/remote\/youtube-Brz_XeX-wAQ-cover.jpg"
                ]
            }
        },
        {
            "id": "183",
            "url": "https:\/\/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=\"https:\/\/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": "https:\/\/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": [
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/Proprocess-3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/remote\/youtube-TaMLUf3gISo-cover.jpg"
                ]
            }
        },
        {
            "id": "168",
            "url": "https:\/\/ivanzviahin.by\/blog\/all\/registration\/",
            "title": "Registration by phone number",
            "content_html": "<p>How we did registration by phone number and now 82% of new users successfully use it.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/reg-0.jpg\" width=\"2560\" height=\"1391\" alt=\"\" \/>\n<\/div>\n<p><a href=\"https:\/\/av.by\">av.by<\/a> is a online board for car sales. 4 platforms are web mobile, web desktop, android and ios apps. We have quite a big post base of 55 000 posts. Our company is 60 people with 1 500 000 users per month. This is the largest platform for the sale of cars in Belarus.<\/p>\n<h2>Problem and audience<\/h2>\n<p>We happened to have implemented registration only via email. We understood that this was not the most convenient way, but it worked well for many years.<\/p>\n<p>We are a big project for Belarus and have a very different audience. Most of them do not live in big cities and have no idea what an email is and how to use it. Some of them are not able to submit an ad without the assistance of relatives and friends.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/reg-1.jpg\" width=\"2526\" height=\"1569\" alt=\"\" \/>\n<\/div>\n<p>Nearly once a month, regularly, some users come to our office to ask for help to submit an ad. And the problem is not in the submission form, but in registration via mail. Plus, this problem has been confirmed more than once in the support service.<\/p>\n<p>The problem is clear, the audience is large, it’s time to start doing something.<\/p>\n<h2>Solution<\/h2>\n<p>There is nothing to invent here, I want to register right away via the phone. Everyone has a phone, it’s a great solution. Registration via social networks is not suitable, not everyone has social networks. But, there are a few nuances.<\/p>\n<ol start=\"1\">\n<li>We cannot cancel registration via email due to technical limitations. We will support two ways.<\/li>\n<li>We cannot use the sign in via SMS message, it is expensive for us. Therefore, we considered logging in through a combination of a phone number plus a password. We use SMS messages only during registration.<\/li>\n<\/ol>\n<p>This is what the flow of the current solution and potentially a new one look like.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/reg-2.jpg\" width=\"2526\" height=\"1041\" alt=\"\" \/>\n<\/div>\n<p>Plus, after analyzing the current solution, we noticed that users are facing difficulty entering a password. For security, we ask users to enter a password longer than 6 characters. But users found out about this after the submission, which increased the registration time. This is what registration looks like step by step.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/reg-3.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>If at least 30% of new users use the new registration method, we will consider it a success.<\/p>\n<h2>Results<\/h2>\n<p>82% of new users use registration via a phone number. Users do not come to our office, and the support service does not receive requests for help.<\/p>\n<h2>Platforms<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/reg-4.jpg\" width=\"2526\" height=\"1785\" alt=\"\" \/>\n<\/div>\n<p>Basically, all solutions work on four platforms: web, android and ios. We also made the desktop version, but I don’t show it because only 17% of the audience use it.<\/p>\n<h2>My role<\/h2>\n<p>I participated in the development of prototypes, made layouts and information architecture, interacted with engineering team and product manager. I communicated with the support service to find out about user requests, and together with the support and the product manager, we determined the metrics. With my involvement I helped to improve the user experience and the number of requests decreased.<\/p>\n<h2><a href=\"https:\/\/av.by\">Go to av.by<\/a><\/h2>\n",
            "date_published": "2021-10-27T19:55:21+00:00",
            "date_modified": "2021-12-21T20:00:59+00:00",
            "image": "https:\/\/ivanzviahin.by\/blog\/pictures\/reg-0.jpg",
            "_date_published_rfc2822": "Wed, 27 Oct 2021 19:55:21 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "168",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/reg-0.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/reg-1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/reg-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/reg-3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/reg-4.jpg"
                ]
            }
        },
        {
            "id": "167",
            "url": "https:\/\/ivanzviahin.by\/blog\/all\/form\/",
            "title": "Toll service on the form · av.by",
            "content_html": "<p>How we added a toll service on the ad submission form and increased the conversion to purchase this service by 48 %.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cc-0-3.jpg\" width=\"2560\" height=\"2040\" alt=\"\" \/>\n<\/div>\n<p><a href=\"https:\/\/av.by\">av.by<\/a> is an online board for car sales. 4 platforms are web mobile, web desktop, android, and ios apps. We have quite a big post base of 55 000 posts. Our company is 60 people with 1 500 000 users per month. This is the largest platform for the sale of cars in Belarus.<\/p>\n<h2>Problem for the business<\/h2>\n<p>We earn money by toll services to promote ads for the sale of cars. This happens in different places of the product. But up to now, we have never advertised toll services on the submission form. We thought it was a dark pattern. But after some time we noticed all competitors do it and this has become commonplace. We decided to test it and observe the results.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cc-1-2.jpg\" width=\"1983\" height=\"2560\" alt=\"\" \/>\n<\/div>\n<p>We have a lot of sellers and each of them posts several ads per month. This proves that the submission form is a good place to sell promotion toll services. Therefore, we want to create the value of a toll service at the start of the sale for sellers and earn on it.<\/p>\n<h2>Audience<\/h2>\n<p>Our audience is sellers. For simplicity reasons, I will unite all car sellers in Belarus with one person. His name is Sasha, say hello to Sasha!<\/p>\n<h2>Problem for sellers<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cc-2-2.jpg\" width=\"2526\" height=\"1155\" alt=\"\" \/>\n<\/div>\n<p>There is definitely no problem for sellers. The main challenge that needs to be solved is to conduct research and find the value of submitting an ad with the purchase of a toll service or rather accelerating the sale from the start of the sale.<\/p>\n<h2>Success criteria<\/h2>\n<p>Any increase in the sale of the toll service will be a success. Yet it is important that this not affect the conversion to ad submission in any way.<\/p>\n<h2>Research<\/h2>\n<p>We conducted more than 5 user interviews and realized that sellers are interested in buying a paid service at the start of the sale if we guarantee that the visibility of their ads will increase several times. And this will affect the reach of sellers and the speed of sales. We cannot guarantee an increase in the speed of sales. A lot of factors affect the speed.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-3-5.jpg\" width=\"2526\" height=\"1356\" alt=\"\" \/>\n<\/div>\n<p>I have done an analysis of competitors. This helped us to find value and generate several hypotheses.<\/p>\n<h2>Hypotheses and priorities<\/h2>\n<p>Here I want to tell you about the ideas and show the prototypes.<\/p>\n<ol start=\"1\">\n<li>If we focus on increasing the visibility of the ad in the product, it could increase the number of sales. Sasha submits an ad by clicking on the blue button and filling out the submission form. In the end, we ask him about the promotion with an emphasis on the visibility of the ad.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h1.jpg\" width=\"2526\" height=\"1740\" alt=\"\" \/>\n<\/div>\n<ol start=\"2\">\n<li>If we publish an ad in any case, it will not affect the conversion to submission in any way. If the service has been selected, we submit an ad and then send the seller to pay.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h2.jpg\" width=\"2526\" height=\"1740\" alt=\"\" \/>\n<\/div>\n<ol start=\"3\">\n<li>If we make the toll option selected by default, it will help to increase the number of sales. It’s scary enough, but I want to test through A · B tests.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h3.jpg\" width=\"2526\" height=\"1740\" alt=\"\" \/>\n<\/div>\n<ol start=\"4\">\n<li><s>If we make a service with a discount, it will motivate the seller to agree to purchase the service.<\/s> We do not have a discount module, it is very expensive to make it technically.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h4-1.jpg\" width=\"2526\" height=\"1740\" alt=\"\" \/>\n<\/div>\n<ol start=\"5\">\n<li><s>If we say how many people use the promotion, it will stimulate the seller to agree to the purchase.<\/s> We didn’t really believe in this hypothesis, plus technically it’s not simple.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h5.jpg\" width=\"2526\" height=\"1740\" alt=\"\" \/>\n<\/div>\n<ol start=\"6\">\n<li><s>If we offer to increase the price of the ad by the price of the service, it will increase the number of payments as it will make the purchase conditionally free.<\/s> It’s also complicated and looks like cheating. We didn’t really believe in this hypothesis.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h6.jpg\" width=\"2526\" height=\"1740\" alt=\"\" \/>\n<\/div>\n<p>Together with the product manager and engineers, we estimated each hypothesis according to two parameters: the complexity of implementation and value. As a result, we got priorities and decided that we would check only the first 3 hypotheses.<\/p>\n<h2>1. If we focus on increasing the visibility of the ad in the product, it could increase sales<\/h2>\n<p>We cannot guarantee that the speed of sales will increase. This is influenced by many factors. But we can guarantee that we will increase the visibility of the ad on the platform. We turned to a data analyst and he informed us that, on average, visibility increases by 5 times.<\/p>\n<p>So, at the end of the submission form, we need to place a block for choosing the publication method. With promotion or not. We don’t have many options on how to do this.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cc-1h-0.jpg\" width=\"2526\" height=\"1674\" alt=\"\" \/>\n<\/div>\n<p>The third option is good, but it’s scary to multiply the most important button. The second one is not very clear, it was confirmed on testing. We decided to go further with the first option.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cc-1h.jpg\" width=\"2526\" height=\"1740\" alt=\"\" \/>\n<\/div>\n<p>Sasha clicks ‘submit an ad’, fills in all the data about the car, and ends up seeing a toll service. There is a free ad submission and a toll one, in which we guarantee ×5 views after publication. A person will receive these views because after submitting the ad, the services of the TOP ad and price allocation will be applied to the ad.<\/p>\n<p>We conducted corridor tests that helped us find the best visual, vulnerable places in the interface and text. Plus, we realized that instead of a discount (we decided not to make this hypothesis, number 4), we would show the monetary benefit of buying a package relative to the services separately.<\/p>\n<h2>2. If we publish an ad in any case, it will not affect the conversion to submission in any way<\/h2>\n<p>We had two options for how to save the conversion into an ad submission.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-2h-1.jpg\" width=\"2526\" height=\"1062\" alt=\"\" \/>\n<\/div>\n<p>The second option is good, but we were afraid that showing promotions after submission was a bad idea. After completing the main action, the user has weaker attention to detail. Since the main action has already taken place and the person wants to quickly look at the result. Without tests, we decided to move on with the first option.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cc-2h-2.jpg\" width=\"2526\" height=\"1740\" alt=\"\" \/>\n<\/div>\n<p>Once the service has been selected, we submit an ad and send the seller for payment. Therefore, the paid service should not affect the conversion to submission.<\/p>\n<h2>3. If we make the toll option selected by default, it will help to increase sales<\/h2>\n<p>Since it’s scary to make a toll service selected by default, we decided to conduct an experiment. After all, this can also affect the conversion to submission. Option A → pre-selected standard sale, option B → pre-selected quick sale for 9 BYN.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cc-4.jpg\" width=\"2526\" height=\"1776\" alt=\"\" \/>\n<\/div>\n<p>Release!<\/p>\n<p>A · B test results. Option A – they pay less and the conversion to ad submission does not change, option B – they pay more and the conversion to ad submission does not change. Therefore, we go further with option B.<\/p>\n<h2>Results<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cc-res.jpg\" width=\"2526\" height=\"1740\" alt=\"\" \/>\n<\/div>\n<p>+48% to the conversion to the purchase of this service, the conversion to ad submission has not changed.<\/p>\n<h2>Platforms<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/cc-pla.jpg\" width=\"2526\" height=\"1851\" alt=\"\" \/>\n<\/div>\n<p>Basically, all solutions work on four platforms: web, android, and ios. We also made the desktop version, but I don’t show it because only 17% of the audience uses it.<\/p>\n<h2>My role<\/h2>\n<p>I was engaged in the analysis of competitors, the formation of hypotheses, their prioritization, interviews, prototypes, and mockups. Besides me, the team included: designer, product manager, engineers. I helped QA engineers to run all the flow and described bugs.<\/p>\n<h2><a href=\"https:\/\/av.by\">Go to av.by<\/a><\/h2>\n",
            "date_published": "2021-10-20T22:47:48+00:00",
            "date_modified": "2022-04-01T21:48:07+00:00",
            "image": "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-6.jpg",
            "_date_published_rfc2822": "Wed, 20 Oct 2021 22:47:48 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "167",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-6.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-5-1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-2-1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-3-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-3-3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-3-4.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h4.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-0-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-0-3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-1-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-2-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-3-5.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h4-1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h5.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-h6.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-1h-0.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-1h.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-2h-1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-2h-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-4.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-res.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/cc-pla.jpg"
                ]
            }
        },
        {
            "id": "165",
            "url": "https:\/\/ivanzviahin.by\/blog\/all\/watercheck\/",
            "title": "Watercheck app",
            "content_html": "<p>How I did a research and found several effective solutions for retention growth during the first user interaction with the app.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-0.jpg\" width=\"2560\" height=\"1327\" alt=\"\" \/>\n<\/div>\n<p><a href=\"https:\/\/apps.apple.com\/by\/app\/watercheck\/id942101001#?platform=iphone\">Watercheck<\/a> is the most necessary app for any diet and fitness, controlling the amount of liquid you drink during the day.<\/p>\n<h2>Primary analysis<\/h2>\n<p>I did the initial review of the first interaction with app and made some notes. This will help me put together a list of hypotheses in the future.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-1.jpg\" width=\"2496\" height=\"2361\" alt=\"\" \/>\n<\/div>\n<h2>Competitor Analysis<\/h2>\n<p>I wanted to understand the difference between our product and others in terms of convenience, attractiveness, and demand. I googled –Top 10 Water Tracking Apps– and installed the first three from the rating.<\/p>\n<p>Comparing the first interaction, I paid attention to the mechanics that bring users back to the application and help them understand that this is exactly what they need.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-2.jpg\" width=\"2496\" height=\"2415\" alt=\"\" \/>\n<\/div>\n<h2>Feedback from users<\/h2>\n<p>The easiest way is to go to the App Store and read user reviews. There may be some diamonds that will help me to resolve the problem. 17 reviews → 2 diamonds.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-3.jpg\" width=\"2496\" height=\"1620\" alt=\"\" \/>\n<\/div>\n<p>Firstly, users think that notifications help them to achieve their goals. Some ask for the opportunity to customize them.<\/p>\n<p>Secondly, users believe that the daily rate of water should be customized immediately, taking into account their weight, activity, age, sex and the most interesting thing – the temperature outside. This will help to make their daily goals more accurate.<\/p>\n<h2>Domain Research<\/h2>\n<p>To begin with, you need to understand the purpose of people who want to monitor the amount of water they drink. I had three interviews and did desk research. I composed questions and selected different people for interviews. I will describe only the most interesting points.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-4.jpg\" width=\"2496\" height=\"1266\" alt=\"\" \/>\n<\/div>\n<p>Desk research. This is what scientists from different universities and research centers say, water:<\/p>\n<ul>\n<li>is the source of energy,<\/li>\n<li>removes toxins,<\/li>\n<li>helps to lose weight,<\/li>\n<li>improves skin, hair and nails,<\/li>\n<li>improves digestion,<\/li>\n<li>reduces blood pressure,<\/li>\n<li>takes away joint pains,<\/li>\n<li>a lot of water is bad, you need to know the norm.<\/li>\n<\/ul>\n<h2>Research Retention metrics<\/h2>\n<p>Then I did a desk research, analyzed trackers in other areas of activity, and noticed an interesting sequence of actions. To influence Retention, mobile applications show the basic value, show how it works, and form habits.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-5.jpg\" width=\"2496\" height=\"1017\" alt=\"\" \/>\n<\/div>\n<p><b>Value and how the application works.<\/b> The first step is to answer the question: what problem does the application solve? Our key mission in the first cycles of use is to make the user’s way to the desired result as simple and clear as possible, to show the key value.<\/p>\n<p>Next, we need to increase the motivation of the first action, far better to make a person do it right now. Tell them how everything works. Give a person a goal and visualize the process of achieving this goal.<\/p>\n<p><b>Reward after action.<\/b> The fact is that a person does not solve their initial task when they perform the main action. Therefore, it is necessary to give the user a reward that exists in the area of their problems.<\/p>\n<p>You shouldn’t give a reward all the time, only sometimes. It is like commenting on a post on Facebook. We don’t know what and how many comments they will get. We must always maintain some level of novelty and uncertainty. It raises more interest.<\/p>\n<p><b>Put something of your own.<\/b> Focus on human investment. The more we invest in something, the more we get attached and appreciate it. For example, call your friends in this application and follow their progress. Or display the amount of water we drink at all times. It will be harder to refuse such investments.<\/p>\n<p>It seems that by simplifying the process of achieving a certain goal we maximize the share of those who will reach this goal. Generally – that’s right, but the maximum number of those who reach the goal does not mean that this approach maximizes the share of those who will continue to use the product.<\/p>\n<p><b>To the next cycle.<\/b> For example, thematic notifications. It is this thing that restarts the cycle and sends the person one step at a time with the action which will have a positive impact on Retention. The topic of such notifications can be as follows from any of the previous three stages: main action, reward or investments.<\/p>\n<p><b><a href=\"https:\/\/www.geckoboard.com\/best-practice\/kpi-examples\/retention-rate\/\">Retention Rate as the Lifestyle industry benchmark<\/a><\/b><\/p>\n<div class=\"e2-text-table\">\n<table cellpadding=\"0\" cellspacing=\"0\" border=\"0\">\n<tr>\n<td>Days<\/td>\n<td>Retention Rate<\/td>\n<\/tr>\n<tr>\n<td>30<\/td>\n<td>36 %<\/td>\n<\/tr>\n<tr>\n<td>90<\/td>\n<td>18 %<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<h2>Hypotheses and priorities<\/h2>\n<p>After I formulated the hypotheses, I found an experienced iOS developer and asked him to estimate the resource for developing these hypotheses. I did estimate the priourities on my own.<\/p>\n<p><b>1. Value.<\/b> If we make a screen that reveals the value of the application at the beginning of the interaction, it could have a positive impact on Retention because it shows the value of the application to the user.<br \/>\n<i>– Hight priority, low resource.<\/i><\/p>\n<p><b>2. Tutorial.<\/b> If we do a tutorial that will guide a person through the main function of the application, including the definition of the daily norm of water drinking, it will have a positive impact on Retention because it will show how the application works.<br \/>\n<i>– Hight priority, medium resource.<\/i><\/p>\n<p><b>3. Rewards.<\/b> If we make a system that will sometimes give rewards (tips, achievements, facts) after the main action and the completed goal in a day, it will be able to affect the Retention, because this system will be engaging, therefore it will help to form a habit.<br \/>\n<i>– Hight priority, medium resource.<\/i><\/p>\n<p><b>4. Friends.<\/b> If we make a system that will be able to invite friends to the application and tell them about their success, it will be able to affect the Retention, because this system will motivate the user to drink water, so it will help to form a habit.<br \/>\n<i>– Hight priority, medium resource.<\/i><\/p>\n<p><b>5. Notifications.<\/b> If we make different types of notifications, which will not only remind about water, but also about the progress of friends, weather and changes in the daily rate of drinking water, they could affect the Retention, because they will return the user back so it will help to form a habit.<br \/>\n<i>– Medium priority, low resource.<\/i><\/p>\n<p><b>6. Notifications settings.<\/b> If we make a notification setting that will help users customize their time intervals, it could affect Retention because new reminders will bring the user back so it will help to form a habit.<br \/>\n<i>– Low priority, medium resource.<\/i><\/p>\n<h2>Prototypes<\/h2>\n<p>I didn’t have time to make high-fidelity prototypes, so I will show low-fidelity prototypes, sometimes medium-fidelity.<\/p>\n<p><b>1. Value<\/b><br \/>\nIf we make a screen that reveals the value of the application at the beginning of the interaction, it could have a positive impact on Retention because it shows the value of the application to the user.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-6.jpg\" width=\"2496\" height=\"1077\" alt=\"\" \/>\n<\/div>\n<p><b>2. Tutorial<\/b><br \/>\nIf we do a tutorial that will guide a person through the main function of the application, including the definition of the daily norm of water drinking, it will have a positive impact on Retention because it will show how the application works.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-7.jpg\" width=\"2496\" height=\"2100\" alt=\"\" \/>\n<\/div>\n<p><b>6. Notifications settings<\/b><br \/>\nIf we make a notification setting that will help users customize their time intervals, it could affect Retention because new reminders will bring the user back so it will help to form a habit.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-8.jpg\" width=\"2496\" height=\"1077\" alt=\"\" \/>\n<\/div>\n<p><b>3. Rewards<\/b><br \/>\nIf we make a system that will sometimes give rewards (tips, achievements, facts) after the main action and the completed goal in a day, it will be able to affect the Retention, because this system will be engaging, therefore it will help to form a habit.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-9.jpg\" width=\"2496\" height=\"1080\" alt=\"\" \/>\n<\/div>\n<p><b>4. Friends<\/b><br \/>\nIf we make a system that will be able to invite friends to the application and tell them about their success, it will be able to affect the Retention, because this system will motivate the user to drink water, so it will help to form a habit.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-10.jpg\" width=\"2496\" height=\"1080\" alt=\"\" \/>\n<\/div>\n<p><b>5. Notifications<\/b><br \/>\nIf we make different types of notifications, which will not only remind about water, but also about the progress of friends, weather and changes in the daily rate of drinking water, they could affect the Retention, because they will return the user back so it will help to form a habit.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/wc-11.jpg\" width=\"2496\" height=\"1074\" alt=\"\" \/>\n<\/div>\n<p>Then all over again, the main action, reward, or investment. It is this thing that restarts the cycle and sends a person to a next step with the action, which will have a positive impact on Retention.<\/p>\n<h2>Testing<\/h2>\n<p>I did not have time to test, but I will tell you how I would do it if I had a chance.<\/p>\n<p>The first hypothesis is about value. I would use corridor tests so that a person would go through this scenario and then I would measure the knowledge of value by talking to the user or the survey.<\/p>\n<p>The second is the tutorial. Here it is vital to understand whether the user has understood how the application works. I would check it through the corridor tests. There is some doubt that the calculation of the daily norm could immediately work badly. Here you can do an A · B test, with and without the calculation of the daily norm, to measure failures. We could interview users to find out if it is really important at the start.<\/p>\n<p>The third is the rewards. The important thing is human interest. You may follow the reading time of these screens. Perhaps we should think about the rating of these rewards Useful or Useless.<\/p>\n<p>The fourth is friends. Here you need to monitor the percentage of users who have added friends. Plus, keep track of how notifications of friends return people to the application, whether the motivation works. Maybe you should conduct a survey to find out the motivation.<\/p>\n<p>The fifth is different notifications. It seems to be a good field for A · B tests. Measure the return to the application.<\/p>\n<p>The sixth is notification setting. I would use corridor tests to test the interface itself and keep track of the percentage of users who use them and measure the return to the application with new notifications.<\/p>\n<p>In general, I would follow the Retention Rate metric in the first day cohort. I might run these hypotheses sequentially and in groups to understand what worked best.<\/p>\n<h2>Ideas for Retention after 1st session<\/h2>\n<p>At this stage, I would work with displaying and highlighting human investments. The more we invest in something, the more we get attached and appreciate it. For example, how much water we drink all the time, a collection of achievements and tips, personal and friends statistics. It will be difficult to refuse such an application for a long time.<\/p>\n<p>The second is the new functionality that is opened depending on the amount of water drunk at all times.<\/p>\n",
            "date_published": "2021-09-16T17:08:45+00:00",
            "date_modified": "2022-11-18T17:17:52+00:00",
            "image": "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-0.jpg",
            "_date_published_rfc2822": "Thu, 16 Sep 2021 17:08:45 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "165",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-0.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-4.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-5.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-6.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-7.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-8.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-9.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-10.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/wc-11.jpg"
                ]
            }
        },
        {
            "id": "159",
            "url": "https:\/\/ivanzviahin.by\/blog\/all\/searches\/",
            "title": "Saved searches · av.by",
            "content_html": "<p>How we made a feature that 27 % of buyers have used and achieved their goal.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-0.jpg\" width=\"2560\" height=\"2040\" alt=\"\" \/>\n<\/div>\n<p><a href=\"https:\/\/av.by\">av.by<\/a> is an online board for car sales. 4 platforms are web mobile, web desktop, android, and ios apps. We have quite a big post base of 55 000 posts. Our company is 60 people with 1 500 000 users per month. This is the largest platform for the sale of cars in Belarus.<\/p>\n<h2>Problem for users<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-1.jpg\" width=\"2526\" height=\"1692\" alt=\"\" \/>\n<\/div>\n<p>Search is the main tool for the classified, 80% of users start with search. People needed to fill in a lot of fields to get the result they needed (filter down by price ranges, car make and model, etc.). Support confirmed that people had to re-enter all the search criteria every time, and they wanted to be able to save it.<\/p>\n<h2>Problem for the business<\/h2>\n<p>As a classified, we want to be able to connect as many car sellers to as many buyers as possible so everything that will help streamline the experience of searching for a suitable car is essential.<\/p>\n<h2>Audience<\/h2>\n<p>Our audience is buyers. For simplicity reasons, I will unite all car buyers in Belarus with one person. His name is Vova, say hello to him!<\/p>\n<h2>Success criteria<\/h2>\n<p>Based on our experience with previous launches, we set as an internal target that 25% of monthly buyers should use the saved search feature.<\/p>\n<h2>Research<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-ca.jpg\" width=\"2526\" height=\"2295\" alt=\"\" \/>\n<\/div>\n<p>I did competitor analysis and then the idea came out that Vova does not need saved searches. He needs to be able to find out about new posts on his request in time. Like a push or email notification. This was confirmed in interviews. In total, there are several ideas.<\/p>\n<h2>Ideas<\/h2>\n<p>Surely, I met with product manager and development team. We estimated the value and complexity of implementing each idea. As a result, we refused several ideas.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-id.jpg\" width=\"2526\" height=\"1182\" alt=\"\" \/>\n<\/div>\n<p>Ideas:<\/p>\n<ol start=\"00\">\n<li>Saved searches. The interface for saving and the interface for storing and managing searches. This idea is numbered zero because without saved searches it is impossible to make the following ideas.<\/li>\n<\/ol>\n<ol start=\"1\">\n<li>Subscribe to new ads based on saved searches. Like push or email notifications. The subscription could not have been done in the first iteration, but we strongly believed in its success after interviews.<\/li>\n<\/ol>\n<ol start=\"2\">\n<li><s>Promotion of saved searches on the first screen. Search screen.<\/s> This is an important feature, I strongly believed in it, but due to limited technical resources, we refused it. Subscription seemed more important to us. I’ll tell you more about it later.<\/li>\n<\/ol>\n<ol start=\"3\">\n<li><s>Promotion of last entered searches on the first screen. Search screen.<\/s> Due to limited technical resources, we abandoned it. I’ll tell you more about it later.<\/li>\n<\/ol>\n<h2>0. Saved searches<\/h2>\n<p>We needed to place the save search button in the list of ads and we don’t have many options.<\/p>\n<ol start=\"1\">\n<li>If we make the button non-sticky, then you can place the block somewhere in the feed. On the plus side, we have the opportunity to tell Vova more about the feature right away. The huge minus is block will be less noticeable with a relatively sticky button.<\/li>\n<\/ol>\n<ol start=\"2\">\n<li>If we make the button sticky, then there are two places immediately where it can be placed. The first is in the navigation bar next to the sorting. Cons — the function will be less noticeable and will constantly create information noise.<\/li>\n<\/ol>\n<ol start=\"3\">\n<li>The second is in the sticky toolbar at the bottom, next to the blue parameters button. This toolbar hides when we scroll down and appears when scrolling up. Which reduces the information noise when searching for ads. One of the advantages is the good brightness of the button.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-01.jpg\" width=\"2526\" height=\"1692\" alt=\"\" \/>\n<\/div>\n<p>We chose option 3!<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-21.jpg\" width=\"2526\" height=\"1692\" alt=\"\" \/>\n<\/div>\n<p>After entering all the fields in the filter on the list of posts, there is a save search button in front of the parameters. This toolbar is sticky. At the first interaction after the release of saved searches, we show onboarding with a call to try saved searches.<\/p>\n<p>Let’s push the button!<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-22.jpg\" width=\"2526\" height=\"1692\" alt=\"\" \/>\n<\/div>\n<p>After pushing on the button, we highlight the saved searches in the navigation through animation. If Vova goes to the saved searches section, he can quickly go to the right one or delete them.<\/p>\n<p>We had doubts about the clarity of the saved search icon. We decided to test this through corridor tests. We conducted 2 tests, made changes, then conducted 5 tests and made sure that there were no problems.<\/p>\n<h2>1. Subscribe to new ads based on saved searches<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-23.jpg\" width=\"2526\" height=\"1692\" alt=\"\" \/>\n<\/div>\n<p>Vova sees the updated onboarding about the subscription and push on it. A modal screen opens with information that the search has been saved and now you can subscribe to find out about new ads. By default, the subscription is enabled. Closes the modal screen.<\/p>\n<p>Vova closes the app and locks the phone. After a while, he hears “Pam-Pam”.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-24.jpg\" width=\"2526\" height=\"1692\" alt=\"\" \/>\n<\/div>\n<p>I received a notification that a new ad for my search has appeared. We also send an email notification. Vova clicks on the notification and sees a list of ads. In this list, new ads are marked with a special blue tag. Also, Vova can go to her saved searches and turn off notifications if they get bored.<\/p>\n<p>We could have shown the ad card after clicking on the notification but decided that a list with the “new” tag would be better. Because there may be several new ads.<\/p>\n<p>It was important for us that the interface worked well. We conducted 4 corridor tests and made sure that Vova understood everything. Release!<\/p>\n<h2>Results<\/h2>\n<p>The result was through the roof as more than 27% of buyers use this solution. More than half of them use subscriptions. We set as an internal target that 25% of monthly buyers should use the saved search feature. Goal – achieved, Vova – pleased. We are also sure that this has had a positive impact on user engagement.<\/p>\n<h2>Idea 2 and 3. Promotion of saved and last entered searches on the first screen (We didn’t do that)<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-5.jpg\" width=\"2526\" height=\"1740\" alt=\"\" \/>\n<\/div>\n<p>However, let me remind you that we had two additional ideas. I strongly voted for this solution. This is the placement of saved and last entered searches on the main search screen. Vova opens the application and sees an additional block with saved and last entered searches.<\/p>\n<p>I specified that this decision should be made. The product manager was of a different opinion. Development resources were very limited and had to be spent on other things.<\/p>\n<p>What experience did I get? I realized that it is important to do the features part by part. This will help deliver good solutions to the user faster. Then enhance this solution or add smth new. But I still believe that this decision will give huge value.<\/p>\n<p>And was it possible to somehow simplify the solution that eventually came out? Yes, it was possible to do only saved searches (only idea 0), without subscriptions. This has already produced a result.<\/p>\n<p><i>P.S. To date, we have already made this idea. The result was through the roof as more than 41% of buyers use this solution. And Vova became a happier user.<\/i><\/p>\n<h2>Role<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/ss-4.jpg\" width=\"2526\" height=\"1635\" alt=\"\" \/>\n<\/div>\n<p>In this project, I did competitor analysis, prototypes, mockups and tested them. Participated in the formalization of ideas. I teamed up with the product manager and engineers on this project.<\/p>\n<p>I communicated with the support service to find out about user requests, and together with the support and the product manager, we determined the metrics. With my involvement, I helped to improve the user experience and the number of requests decreased.<\/p>\n<p>Basically, all solutions work on four platforms: web, android, and ios.<\/p>\n<h2><a href=\"https:\/\/av.by\">Go to av.by<\/a><\/h2>\n",
            "date_published": "2021-08-23T22:52:00+00:00",
            "date_modified": "2022-02-21T19:35:45+00:00",
            "image": "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-0.jpg",
            "_date_published_rfc2822": "Mon, 23 Aug 2021 22:52:00 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "159",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-0.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-ca.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-id.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-01.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-21.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-22.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-23.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-24.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-5.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/ss-4.jpg"
                ]
            }
        },
        {
            "id": "158",
            "url": "https:\/\/ivanzviahin.by\/blog\/all\/finance\/",
            "title": "Finance · av.by",
            "content_html": "<p>How we moved the media format of loan and lease applications to the service format and increased the number of applications by one-third and started making bigger profits.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/fin-0.jpg\" width=\"2560\" height=\"1391\" alt=\"\" \/>\n<\/div>\n<p><a href=\"https:\/\/av.by\">av.by<\/a> is a online board for car sales. 4 platforms are web mobile, web desktop, android and ios apps. We have quite a big post base of 55 000 posts. Our company is 60 people and we have 1 500 000 users per month. This is the largest platform for the sale of cars in Belarus.<\/p>\n<p><a href=\"https:\/\/av.by\/finance\">av.by finance<\/a> is a separate product embedded in the post board. This product enables to buy a car on credit or leasing.<\/p>\n<h2>Problem and research<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/fin-1.jpg\" width=\"2526\" height=\"1575\" alt=\"\" \/>\n<\/div>\n<p>The lease application used to look like this. Under the price. This is just a banner that is linked to the page of the leasing company’s website. For simplicity, I will unite all car buyers in Belarus with one person. His name is Vova, say hello to him :-)<\/p>\n<p>Vova needs to get a loan or lease. And we need more completed applications. We receive money from financial companies for each submitted application. We had an insight from user interviews that 72% of car transactions are made with the help of a loan or lease. This is a big market and we want to make money on it.<\/p>\n<p>It is difficult for Vova to choose a loan because now only one financial offer is shown on the card. He has nothing to compare it with. Plus, each financial institution has its own website and its own application form. When Vova fills in several, it is difficult for him because they are all different and you need to figure it out again.<\/p>\n<p>Yet we understand that if we give Vova a solution, we will be able to earn more on loans and leases. Success is an increase in the number of applications by 20%. We have a lot of such Vovas, 300 000 people a month. It is worth it to do such a task.<\/p>\n<p>We conducted 12 interviews. 5 with financial companies 7 with buyers, we carried out an analysis of competitors and came up with 6 solutions.<\/p>\n<h2>Ideas<\/h2>\n<ol start=\"1\">\n<li>List all car loans or leases in one place.<\/li>\n<li>A formalized list of available car loans  or leases on the car card.<\/li>\n<li>Promotion tools in car loans or leases list.<\/li>\n<li>Mass submission of a request for all available  car loans or leases.<\/li>\n<li><s>Automatic transfer of the application from one company to another, if the first company refused.<\/s><\/li>\n<li><s>Analytics for financial companies so that they could improve their car loans or leases.<\/s><\/li>\n<\/ol>\n<p>Surely, I met with the engineers to estimate the complexity of implementing each solution. Together with the product manager, we estimated the effectiveness of each solution. Based on these two parameters, we prioritized solutions. As a result, they refused to automatically transfer the application from one company to another and from analytics.<\/p>\n<p>Next, I will detail first four solutions.<\/p>\n<h2>1. List all car loans or leases in one place<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/fin-2.jpg\" width=\"2526\" height=\"1881\" alt=\"\" \/>\n<\/div>\n<p>Vova is opening the  menu and sees a new product Finance, taps it. Next, Vova sees all the loans and leases for buying a car or other transport. Vova sees the parameters, compares them, and sends the request. Vova can also open the car loan or lease page and explore it in more detail. Most importantly, we made a product management system inside the project with formalized parameters.<\/p>\n<p>We conducted 5 corridor tests that helped us find bad places in the interface. We expected that this would definitely affect the growth in the number of applications. We started making money on the subscription fee for the placement, which gave us an additional revenue stream.<\/p>\n<h2>2. A formalized list of available car loans  or leases on the car card<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/fin-3.jpg\" width=\"2526\" height=\"1785\" alt=\"\" \/>\n<\/div>\n<p>On the left, I showed the previous lease offer. Let me remind you that when Vova clicked, we transfer to the website of a financial company. It worked like a banner ad. Immediately below the price, you can see that this car can be purchased on credit or on lease.<\/p>\n<p>At the end of the card, I show the best offers and give the opportunity to view all the products by clicking on the button. Now we already have formalized car loans and leases and we can show not one, but several loans at once so that Vova could choose the right one.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/fin-4.jpg\" width=\"2526\" height=\"1785\" alt=\"\" \/>\n<\/div>\n<p>So, there are two places on the card where we advertise car loans. We built the architecture so that the entire list of suitable car loans would be displayed in a modal window. To provide access to the list anywhere, we will create a good user experience. We did not come to this immediately. There were disputes with the product manager, but my version outwon on the corridor tests.<\/p>\n<p>So Vova can only send applications one by one. We expected that this would definitely affect the growth in the number of applications.<\/p>\n<h2>3. Promotion tools in car loans or leases list<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/fin-5.jpg\" width=\"2526\" height=\"1785\" alt=\"\" \/>\n<\/div>\n<p>It will give us extra money for services. Any company can buy a promotion. Instead of our finance service, we will show the final loan or lease. I don’t think that this will give us an increase in applications, but we can make money on it.<\/p>\n<h2>4. Mass submission of a request for all available  car loans or leases<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/fin-6.jpg\" width=\"2526\" height=\"1905\" alt=\"\" \/>\n<\/div>\n<p>When Vova opens the list of available loans (modal screen), we will give him the possibility to send a request to everyone If he has no desire to understand and speed is important to him.<\/p>\n<p>We conducted 5 corridor tests that helped us find bad places in the interface. We think that this will greatly boost the growth of applications, but we DO understand that this will decrease their quality.<\/p>\n<h2>Result is +32%<\/h2>\n<p>We came up with 4 solutions. In total, we got a 32% increase in applications. Plus, we made extra money on promoting products and placing companies on the lists.<\/p>\n<p>What went wrong? We made many solutions in parallel, so we could not find out what exactly gave the maximum growth. In the future, I would make features one after another or for different groups of people.<\/p>\n<h2>Platforms<\/h2>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/fin-8.jpg\" width=\"2526\" height=\"1518\" alt=\"\" \/>\n<\/div>\n<p>Please be noted that all solutions work on four platforms such as web, android, ios. We also made the desktop version, but I don’t show it because only 17% of the audience use it. You probably have noticed that along with the car loans and leases, the design has completely changed. Yes, we did a redesign and technical relaunch of the platforms, made a design system and created main components. But this is another story.<\/p>\n<h2>Role<\/h2>\n<p>In this project I did research, prototypes, mockups and tested them. Participated in interviews and brainstorming.<\/p>\n<p>On the project I closely teamed up with a product manager, analyst, engineers. I helped the product manager prioritize ideas, make users story and together with the engineers, we prioritized ideas according to technical complexity. I helped QA check the work of test builds, described bugs.<\/p>\n<p>My work on the project after working on the interface was very positively noted by marketing, because I made a set of banners for the launch together with them, wrote texts for Release notes together with the engineers, helped illustrate the release.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"https:\/\/ivanzviahin.by\/blog\/pictures\/fin-7.jpg\" width=\"2526\" height=\"1785\" alt=\"\" \/>\n<\/div>\n<h2><a href=\"https:\/\/av.by\/finance\">Go to av.by finance<\/a><\/h2>\n",
            "date_published": "2021-08-23T20:57:34+00:00",
            "date_modified": "2022-01-18T20:24:19+00:00",
            "image": "https:\/\/ivanzviahin.by\/blog\/pictures\/fin-0.jpg",
            "_date_published_rfc2822": "Mon, 23 Aug 2021 20:57:34 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "158",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/fin-0.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/fin-1.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/fin-2.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/fin-3.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/fin-4.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/fin-5.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/fin-6.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/fin-8.jpg",
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/fin-7.jpg"
                ]
            }
        },
        {
            "id": "154",
            "url": "https:\/\/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=\"https:\/\/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": "https:\/\/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": [
                    "https:\/\/ivanzviahin.by\/blog\/pictures\/Frame-5-1.png"
                ]
            }
        }
    ],
    "_e2_version": 3849,
    "_e2_ua_string": "E2 (v3849; Aegea)"
}