<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kirill Vechtomov on Medium]]></title>
        <description><![CDATA[Stories by Kirill Vechtomov on Medium]]></description>
        <link>https://medium.com/@kirillvechtomov?source=rss-e7b99c38f8da------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BJCreIJK9pAoRkVblGcT-A.png</url>
            <title>Stories by Kirill Vechtomov on Medium</title>
            <link>https://medium.com/@kirillvechtomov?source=rss-e7b99c38f8da------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:18:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kirillvechtomov/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Prototyping On Paper]]></title>
            <link>https://medium.com/@kirillvechtomov/prototyping-on-paper-ef6e0c513254?source=rss-e7b99c38f8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef6e0c513254</guid>
            <category><![CDATA[rapid-prototyping]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Kirill Vechtomov]]></dc:creator>
            <pubDate>Wed, 21 Mar 2018 20:59:48 GMT</pubDate>
            <atom:updated>2018-03-22T06:06:13.512Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*2pdR0RP4o9httHWm.jpg" /></figure><p>Prototyping with pen and paper is arguably the easiest and fastest way to start. There are many opinions (as usual) whether it’s worth using this method or not. Like any tool, it has it’s own good and bad. I use it almost daily for clarifying the ideas for myself, to communicate it to others, and sometimes for testing with users.</p><h3>Pros</h3><ul><li>Super fast</li><li>Dirt cheap</li><li>Can iterate quickly</li><li>Easy to throw it out (don’t get too attached)</li><li>Roughness makes it easy to position it as a work-in-progress</li><li>Helps with getting early user feedback</li><li>No need for any equipment, power, internet connection, etc.</li><li>Anyone can do it</li></ul><h3>Cons</h3><ul><li>Roughness makes it hard for some people to grasp that it’s just a conceptual prototype</li><li>May require more explanation and setting the expectations</li></ul><h3>Tools needed</h3><p>You can use any piece of paper and something to write on it. I’ve used napkins, scratchpads from the hotels, random pieces of paper from conference handouts, and of course my notepad which is (almost) always with me. I really like the dotted grid paper, as it’s not as heavy visually and still provides a grid for straight lines.</p><p>And, of course, something to sketch with — pen or pencil. I tried both, and even though it’s easier to make corrections to pencil sketches, I personally prefer a pen. And whenever I need to “fix” a mistake, I just sketch it again on the next page. This enforces the idea of a throw-out prototype =) Also gives you an opportunity to add other tweaks whenever you need to re-draw a sketch. So, instead of polishing your pencil-made prototype, you can quickly iterate right away. Helps to build this habit.</p><p>Some people use special stencils with various UI elements (e.g. iOS standard interface objects like tabs, buttons, toolbars, etc.). I tried this once but didn’t like it. I felt it like I was back in school with rulers and other tools to make perfect lines. I prefer hand-writing though there is nothing wrong with using the tools that you find may be working better for you. However, I think the fewer tools you have to rely on the fewer obstacles you may have when prototyping with what you have at that moment. And these metal sketching stencils will become another thing not to forget to carry in your bag.</p><h3>How to</h3><p>Not sure how what to say here =) you just draw lines, circles, and other geometric shapes. Transfer the images to your head on the paper. As I said, in most cases I use just simple dot-grid paper, so I start with drawing a box to sketch in. For a mobile app — a rectangular that looks like a smartphone screen, for a web app — a rectangular that looks like a web browser. When you get this first shape — time to go wild =)) If you screw up a line, just turn the page and do it again. The more you do this — the better you will become in thinking about these sketches as just a temporary first step in your prototyping journey.</p><h3>Tips</h3><ul><li>Do not wait until you get your favourite sketching notebook to start, use any paper you have right now.</li><li>Do not get attached to the prototype, treat it as a throw-away draft to learn something from it and move on.</li><li>Do not spend too much time on it, it’s a temporary phase.</li><li>Show it to somebody other than yourself, that’s the main point of the prototype.</li></ul><p><em>{These tips are the ones I could think of at the moment, will be adding more over time}</em></p><h3>Examples</h3><p>Here are a few recent ones I made. You can see how rough (and fast) they are. And yours can be, too. That’s totally OK. The sooner you can get comfortable with the idea that your prototype doesn’t have to be pixel-perfect, the earlier you’ll start ripping the benefits for your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RPmXt1i8KAulA9vx.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X7U9y27bGgnokAx0.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9MR03OV-npMvKORO.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fEdJrnnhglqW-Rk8.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NKACsTbijod2HPdb.jpg" /></figure><p><em>Originally published at </em><a href="http://getprototyping.com/rapid-prototyping-101/prototyping-on-paper/"><em>getprototyping.com</em></a><em> on March 21, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef6e0c513254" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping Benefits]]></title>
            <link>https://medium.com/@kirillvechtomov/rapid-prototyping-101-a2765b048d85?source=rss-e7b99c38f8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2765b048d85</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[rapid-prototyping]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Kirill Vechtomov]]></dc:creator>
            <pubDate>Tue, 27 Feb 2018 15:13:35 GMT</pubDate>
            <atom:updated>2018-03-06T02:43:47.475Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why you should prototype</h3><p><strong>A real story about one entrepreneur</strong>, let’s call her Denise.</p><p>Denise has been working hard on launching her new technology startup. Her team of designers, developers, and QA has spent 10 months crafting the experience to make it look, feel, and function exactly how she envisioned. Finally, it’s (close to) perfect and she releases it to her customers only to realize that they are not exactly raving about it, it’s confusing, clunky and doesn’t solve the problem the way <strong>she </strong>thought<strong> assumed</strong> it would. She raises her hands to the sky and shouts “Why??? Oh, why didn’t I listen to my good old friend Kirill from <a href="http://getprototyping.com/">GetPrototyping.com</a>?”… and then she gets back to work re-work (of course, after trying to come up with a good reason for her VCs why she hadn’t validated her assumptions earlier).</p><p>The cost of such mistakes could easily double the development time, or could even cause you lose precious time before your competition shows up with a better product (because <strong>they did listen</strong>).</p><p>One of the main tools to significantly reduce the risk of something nobody needs or can’t figure out how to use is prototyping, or more precisely — Rapid Prototyping.</p><h3>Benefits</h3><p>There are a lot of advantages of product prototyping which I will cover later, but if I had to summarize — prototyping reduces the cost and risks and increases the chances of creating successful products. It can literally save your company a ton of time, money and make your product experience a delight. Who doesn’t want that, right? (Well, maybe a monopoly wouldn’t be as concerned =)</p><p>However, rapid prototyping is a tool, and every tool has its pros and cons. If used properly, the value of prototyping can be tremendous. If not — the insights can lead you down a wrong path. On this website, I will be teaching you everything you need to know to extract the best value from Prototyping.</p><p><em>Originally published at </em><a href="http://getprototyping.com/rapid-prototyping-101/benefits-of-prototyping/"><em>getprototyping.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2765b048d85" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping Definition]]></title>
            <link>https://medium.com/@kirillvechtomov/prototyping-definition-7e8e34bedaa?source=rss-e7b99c38f8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e8e34bedaa</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[rapid-prototyping]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Kirill Vechtomov]]></dc:creator>
            <pubDate>Wed, 21 Feb 2018 21:16:34 GMT</pubDate>
            <atom:updated>2018-03-06T02:42:30.442Z</atom:updated>
            <content:encoded><![CDATA[<p>There are quite a few ways people try to define prototyping. Many industries and situations can benefit from using prototypes, and variety of “materials” being used may explain the variations in its definitions. Overall, however, there are commonalities. I never liked academic definitions, so here is my attempt to put it in layman’s terms.</p><blockquote><strong><em>Prototyping</em></strong><em> is a way to </em><strong>quickly</strong><em> create a </em><strong>simulated (or simplified)</strong><em> version of the product you have in mind for the purpose of </em><strong>testing</strong><em> it with your target users to understand what needs to be changed before releasing the product.</em></blockquote><p>The key words here are ‘quickly’, ‘simulated’ and ‘testing’. A prototype is supposed to help you save time and gain insights from your users faster, which makes it impractical to fully develop it, so some people can call it fake.</p><p>A great example to illustrate a physical prototype concept is Google Glass:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0THMPRQSn02jyGJ_rotxUg.png" /></figure><p>And an example of a digital prototype:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/753/1*w_moC71TKWGrs8BpUiYEmQ.png" /></figure><p><em>Originally published at </em><a href="http://getprototyping.com/rapid-prototyping-101/prototyping-definition/"><em>getprototyping.com</em></a><em> on February 21, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e8e34bedaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping Tools]]></title>
            <link>https://medium.com/@kirillvechtomov/prototyping-tools-e54868f7248d?source=rss-e7b99c38f8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/e54868f7248d</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[rapid-prototyping]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Kirill Vechtomov]]></dc:creator>
            <pubDate>Mon, 15 Jan 2018 07:20:57 GMT</pubDate>
            <atom:updated>2018-03-01T17:39:24.149Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gW8sNOl3e6t1Iitk.jpg" /></figure><p>Depending on the stage and situation you want to use physical or digital tools or a combination of both.</p><h3>Starting from scratch</h3><h3>Physical prototyping tools</h3><p>If you don’t have any existing screens, proof of concepts (or sometimes even a functioning product), you want to start with pen and paper because you can create a testable prototype within a few minutes, just to communicate the idea. Personally, I am a huge fan of paper sketching at the beginning of any new idea. It’s not just blazing fast, but it also helps you clarify the thoughts in your head.</p><p>This is how it typically works out for me. I start sketching in my notebook (or any piece of paper if I don’t have my moleskin nearby). First, take sucks. Flip the page. The second take is better, but alignment or sizing doesn’t fit. Flip the page. The third take is good enough to think about it a bit more. Make corrections right in the sketches without redrawing them. It does look messy and that’s fine =) Then, I take several sheets of letter-size (A4 for Europe) paper with a dotted grid on them, and transfer the latest iteration from the notebook. That’s it. Your first rough prototype is ready to be tested. The best thing about paper prototyping is that you don’t get attached to the results at all, so it’s easy to throw them away and start over. It literally, takes 5 minutes to sketch a few screens. Super agile =)</p><p>Another popular option — whiteboards, which is great for a team session thanks to its size. However, what I noticed is that if I am doing it alone, paper works much better for me.</p><h3>Digital prototyping tools</h3><p>There is a plethora of modern prototyping tools out there, and most of them are amazing. In the recent years, UX design and prototyping has been trending, and following the best capitalism traditions, where there is a need, there will be an entrepreneur to fulfil this need. In case of software prototyping tools, there are dozens of companies solving this problem in various “sizes and shapes”. Everyone tries to be different. Some focus on specific unique value propositions (UVP), some are adding more bells and whistles. It feels like there is a new “best prototyping tool” released every single month, and becoming an expert in all of them seems like a full-time job on its own. That’s why lots of entrepreneurs stick to the tools they learnt about first. The choice of spending time learning a new prototyping tool versus launching your new venture is obvious.</p><p>This played a great favour for Invision. They were one of the first (or maybe the first) services that figured out how to empower people without design background and create a very decent simulation of a functional prototype. In fact, they are “faking” it, but who cares, right? It’s a close enough experience to communicate to users or stakeholders without a single line of code. Basically, Invision (and most other prototyping tools) sells time. It can save a ton of time especially for startuppers who are searching for the right product. (I am not affiliated with Invision, but it’s one of my favourite tools, and it helps a lot of people prototype faster). Back to the main topic =)</p><p>These digital prototyping tools require different levels of coding and design skills. Some of them are easy-to-learn for anyone, no coding necessary. Plus, you can easily share your prototype with your users or investors. What else do you need? The cons of this type of simulation, is that you cannot replicate full native experience, e.g. not all animations and transitions are available within these tools, but they are getting better and better, and they are definitely good enough to start testing your prototype, which is what you need to do as fast as possible (at least in the beginning).</p><p>Some tools allow you to create design right there, and others require you to use a separate app (e.g. Sketch or Photoshop) to craft the mockups and then upload them to this prototyping tool to define interactions and screen transitions.</p><p>To summarize, there are lots of tools, and they vary in what you can do with them, how fast you can create a prototype, and what skills you will need to acquire (or get some help with). I will be reviewing the main tools in further articles, covering their pros and cons (and potentially, video lessons. You can let me know which tools you want me to make some training videos for, first via email.)</p><h3>Hybrid prototyping tools</h3><p>The third category is a mix of physical and digital elements, and a good example is iOS mobile app “Pop”, which allows you to sketch your screens on paper, take photos, and link them together using the mobile app. As a result, you will have an interactive prototype that you can test using a mobile device. I tried this app once when they just launched, and it was OK, but I didn’t include it in my toolkit.</p><h3>Starting with an existing application.</h3><p>Sometimes, you may start with something that’s already created or live. In that case, the most time-efficient option is to use what exists and start testing it. As an example, there may be a proof of concept or live web app that you either inherited or somebody else created for you. Start building off it (unless it was tested and you believe it needs to be thrown away completely =) and just go test what you have asap. Then, iterate based on the results. This may save you some time or may send you down the wrong path =) so be careful how you use it. What I always try to find out before testing somebody else created is how they did it, what was the reasoning behind the design decisions, and what user insights they used to create it. If possible, sit down with the person who made it and just ask them to fill you in on their thinking process and who they ended up with that design. In most cases, there will be some valuable information they can share, but always be mindful of other person’s (and yours for that matter) biases that influenced the decisions they made.</p><h3>My favourite prototyping tools</h3><p>After years of designing and testing prototypes, and trying out different apps, this is my main toolkit (with increasing fidelity):</p><ol><li>Pen &amp; Paper</li><li><a href="https://balsamiq.com/">Balsamiq</a></li><li><a href="https://sketchapp.com/">Sketch</a> + <a href="https://www.invisionapp.com/">Invision</a></li></ol><p>I will show how I use this tools in future lessons.</p><p><em>Originally published at </em><a href="http://getprototyping.com/prototyping-tools/"><em>getprototyping.com</em></a><em> on January 15, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e54868f7248d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping Methodology. Step 4 — Learn]]></title>
            <link>https://medium.com/@kirillvechtomov/prototyping-methodology-step-4-learn-be2b97471072?source=rss-e7b99c38f8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/be2b97471072</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[rapid-prototyping]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Kirill Vechtomov]]></dc:creator>
            <pubDate>Wed, 15 Nov 2017 22:46:14 GMT</pubDate>
            <atom:updated>2018-02-27T15:41:15.683Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Attention</strong>: This is a super important step.</p><p>In the previous step (<a href="http://getprototyping.com/prototyping-methodology/step-3-test/">Step 3 — Test</a>) you carefully observed the users’ behaviour and took all the notes possible, and maybe even voice/video recordings. Now, you probably think it’s time to make all the changes to address the comments or suggestions you’ve heard. Not so fast. First, you want to be cautious about what users have said. Relying just on their words, thoughts, or suggestions puts you in a risky position. Users’ behaviour is way more valuable and a much better indicator of what’s working and what’s not working.</p><p>There is a great story proving the point. A few years ago, at one of the Walmart’s stores management surveyed their customers for ideas on how to improve their shopping experience. Almost everybody asked for less cluttered aisles and shelves. They said there were too many products on each shelf, too many shelves, and too narrow aisles. The management delivered exactly what their customers had asked for. And I admire their devotion and desire to listen to the most important group of people. However, the reality hit them hard when the sales plummeted after they updated the store’s layout. Shortly after, they reverted the changes, and the sales bounce back to the previous levels. They learnt their lesson.</p><p>During your testing, you may hear many suggestions on how to improve your product or feature. If your idea resonates with them, they will likely get passionate sharing their thoughts and trying to help you with your new product. It may start with “You know what else would be cool?…” or something like that. And you definitely should make a note of all such ideas because there might be something new and valuable. But don’t jump into making the changes right away. Try to analyze their behaviour instead, and understand the underlying reason why they are asking for this. Use 5-Whys method to dig deeper and get to the core. And after you understand their motivation you can think about the optimal way to address their core need. Sometimes, it can be exactly what they told you about, but most often there is a better way to help them achieve what they are trying to.</p><p>Sometimes, your thorough thinking leads to the exact solution that was asked for by your users. That’s totally fine and you may conclude you should have implemented their ask right away. Reality shows that it may be hit or miss, and if you skip analysis phase, the risk of making a mistake is much higher.</p><p>Also, don’t forget that you are running a business, and you want to strike the right balance between customer and business needs. So, if you product update cause a negative impact on your bottom line (like with Walmart’s example) you should be ready to act. Such things happen and that’s absolutely fine. The key to success is to test often and iterate quickly. If you are doing an experiment, you may be able to minimize your risks by rolling out your new feature to a limited number of users. Then, observe their behaviour and analytics, and iterate if necessary before launching it to everybody. One of the methods we use for that is A/B testing, and I will be covering this topic in future.</p><p>Got a bit sidetracked… Back to analyzing test results =)</p><h3>Biases</h3><p>Every person has some sort of biases. Usually, you may not even notice this. It could be as simple as an assumption that everybody uses their mobile device with one hand because you do it this way. Humans (including designers, we are also humans, you know =) tend to think their own behaviour applies to everybody or at least majority of their users. This is often incorrect and that’s why you have to get rid of your biases before analyzing the results. One of my favourite quotes — “Design for them, not you” — is a good reminder of this problem. I even have a sticker on my notebook =)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qytW6nW4hLDDrX2F.jpg" /></figure><h3>Prioritization</h3><p>After you identified all the valid problems with your prototype, time to arrange the list, so you can tackle the most important ones. In an ideal world you want to fix every single thing, but in our flawed world with limited time and resources, you want to be strategic about what you spend your precious time on. So, you want to go through a prioritization exercise to group the discovered issues depending on their severity. One of the big questions I ask when prioritizing is “Does it stop users from using your app?” If yes, this is a critical issue that needs to get fixed before the next round of testing (yes, you heard me, it’s an ongoing process and should never stop). It’s hard to give you any solid advice on what issues are a higher priority without seeing the product itself =) So, I can suggest that you play it by ear and you should be able to estimate the severity based on your gut feeling. Also, you can ask me anytime, and I’ll be glad to help you out, free advice just for you =)</p><h3>Solutions</h3><p>Deciding on the list of issues to fix is very important and requires some thinking. But <strong>how</strong> you are going to fix them will require a bit more creative thinking, and will depend on your circumstances (e.g. type of the prototype, level of fidelity, scope, etc.). In some cases just making a button bigger may solve the issue that users didn’t see it. In other cases, you may have to change the application map to make it better aligned with your users’ mental model. If you have done it right, and have got a good understanding of how your target audience lives and breathes, and what their true needs are, then the overall structure/logic of your product should not need a complete overhaul. But if your testing revealed that they were very confused about what it did, and where to find stuff they were looking for, this requires more time and effort, for sure. But you can do it! I believe in you! =)</p><p><strong>A few “red flags” examples that your product needs more work:</strong></p><p>– Users found something confusing and didn’t know what to expect from a menu or a button.</p><p>— They weren’t sure where to find a piece of information or some functionality.</p><p>— They paused looking at the screen.</p><p>— They said “interesting”, “oh”, “um”, or any other sign of hesitation.</p><p>— They asked where they could find this or that.</p><p><em>Originally published at </em><a href="http://getprototyping.com/prototyping-methodology/step-4-learn/"><em>getprototyping.com</em></a><em> on November 15, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be2b97471072" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping Methodology. Step 3 — Test]]></title>
            <link>https://medium.com/@kirillvechtomov/prototyping-methodology-step-3-test-902da333c93e?source=rss-e7b99c38f8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/902da333c93e</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[rapid-prototyping]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Kirill Vechtomov]]></dc:creator>
            <pubDate>Sun, 05 Nov 2017 23:27:09 GMT</pubDate>
            <atom:updated>2018-02-27T15:38:39.397Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Attention</strong>: This is a super important step.</p><p>You’ve got your prototype ready (<a href="http://getprototyping.com/prototyping-methodology/step-2-prototype/">see Step 2 — Prototype</a>), now what? Time to test it with your users. It sounds obvious, but you’d be surprised to find out how many people who do prototyping do not go outside and test it with their target audience. This is the whole point of doing this — so you can show it to real users (or prospects) and find out if you are going in the right direction or not. Otherwise, you miss out on the main value of prototyping and risking the success of your product.</p><p>In the first step (see <a href="http://getprototyping.com/prototyping-methodology/step-1-define/">Step 1 — Define</a>), you’ve already decided on the high-level logistics — where you are going to test it and if you need any tools to do this. Assuming you know exactly who your users are and how to connect with them, here are the main points:</p><h3>Recruitment</h3><p>You can do it yourself or through an agency (quite expensive). DIY is definitely cheaper, but you have to invest your time in this, and this can get very time-consuming — searching, reaching out, scheduling, rescheduling, etc. This is my least enjoyable part, feels like a job I’d prefer delegating to someone else, but if you are bootstrapping, you can do it yourself. Hopefully, you have been investing in building your relationships beforehand, so you can ask your network to help with a few introductions. This will speed up the process. I am very grateful to have such a great network that is willing to help me with introductions or insights.</p><h3>Number of participants</h3><p>Many people think that you need at least 15–20 tests to get at least some decent statistical validity, but the guru of usability testing — Jakob Nielsen — discovered that the <a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">optimal number of test participants is 5</a>. You should be able to discover about 75% of usability issues, which is more than enough to make adjustments and go for another round. If you could get 20 people who agreed to help you with that, you’d be better off splitting them into 4 rounds. Such approach will reveal more valuable results, than wasting all 20 right away. From my experience, you should recruit 7 people to have a 2-person buffer, in case they don’t show up or if the feedback they provide does not bring a lot of value.</p><h3>Incentives</h3><p>It varies and depends on how much does their time cost and how close your connection is. For bootstrapping, considering that the person doesn’t have to travel to your location, and you have some common connections, $10–20 Starbucks gift card for 15–30 minutes of their time would work. If you ask for more of their time, increase the amount appropriately. Ideally, try to understand the person’s preferences and choose the gift card that’s more relevant for this particular participant. For example, I chose David’s Tea instead of Starbucks for a person who was really into loose leaf tea. And when there wasn’t a Starbucks close by, I bought a Waves card because it was right across the street from their place.</p><h3>Test Plan</h3><p>The agenda completely depends on your current phase and what assumptions you are trying to validate. I will write a more detailed post on what questions to ask, how, and when.</p><p>For understanding the problem and concept testing, you want to ask more open-ended and broad questions. E.g. if you want to validate your idea, do not start with your solution. Rather ask them to describe their “flow” related to the problem you are trying to solve, how often they face this problem, in what scenarios and environments, how they deal with it, are they using existing products to help with this, how painful this is for them, and how satisfied they are with the current solution. For this phase, I just prefer asking several very open questions, e.g. “Describe me the last time you did {this}, walk me through the steps you took”, and let the conversation unfold itself. You want to uncover the underlying cause why they do what they do. And only then, show the prototype and ask what they think about this. One of my favourite methods to understand the core of the problem is <a href="https://en.wikipedia.org/wiki/5_Whys">5-Whys</a>.</p><p>For later phases, you want to discover usability problems, e.g. if they can find what they are looking for if they can understand the gestures, buttons, and the flow of your app. This is more of a traditional usability testing and I will be covering this topic in future posts, as there is a lot to learn there.</p><p>Before going out to users, you want to run through your test with somebody you work with (or a friend). This “rehearsal” has been valuable for me every single time. It’s so easy to miss small things here and there, and testing your test plan may help you find the gaps, and when you hear yourself you can feel if it flows smoothly. If I am working on a project alone, I just ask my wife to be the pretend user and simulate the testing session with her.</p><h3>Moderating</h3><p>Even if you prepared a great test plan and took care of the rest, what can ruin your testing is the way you conduct the test: how you present yourself, how you treat the person, how good you can control your ego and biases, when do you give incentive, how you respond to participant’s questions, etc. A few most important things to keep in mind: be polite and respectful, ask open-ended questions, let the user do the talking, don’t take it personally, and be grateful for their time and desire to help you.</p><p>Oh, and don’t forget to capture all their feedback (notes, audio, or video). Human’s memory is not a reliable data storage =) What was your name again? =)) What I find challenging is doing the testing and taking notes at the same time. You want to be following what the participant does with the prototype and maintain eye contact with them while they talk to you, not scribble stuff in your notebook. If possible, ask your partner or a friend to take notes, would help a lot, and you will less likely to miss something important if you can focus on the person, and your buddy can focus on the notes.</p><h3>Logistics</h3><ul><li>What equipment do you need? Smartphone? Laptop? Don’t forget to charge them.</li><li>Do you need Internet? Will the test location have Internet?</li><li>Do you need to book a meeting room or just meet at a coffee shop location?</li><li>Don’t forget to remind the participant in advance, and give them all details about the timing, location, driving directions, and contact details.</li></ul><p>PS this article is just a high-level overview of the testing process. I will be writing the whole series because there is <strong>a lot</strong> to learn.</p><h4><a href="http://getprototyping.com/prototyping-methodology/step-4-learn/">Step 4 — Learn</a></h4><p><em>Originally published at </em><a href="http://getprototyping.com/prototyping-methodology/step-3-test/"><em>getprototyping.com</em></a><em> on November 5, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=902da333c93e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping Methodology. Step 2 — Prototype]]></title>
            <link>https://medium.com/@kirillvechtomov/prototyping-methodology-step-2-prototype-71f2625e6579?source=rss-e7b99c38f8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/71f2625e6579</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[rapid-prototyping]]></category>
            <dc:creator><![CDATA[Kirill Vechtomov]]></dc:creator>
            <pubDate>Thu, 02 Nov 2017 20:54:39 GMT</pubDate>
            <atom:updated>2018-02-27T15:33:21.155Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Attention</strong>: This is a super important step.</p><p>After you have defined the scope, fidelity, tools, and logistics (<a href="http://getprototyping.com/prototyping-methodology/step-1-define/">see Step 1 — Define</a>), it’s time to start prototyping your product. This step may have a lot of variations depending on the details. In this post, I will provide a high-level overview of what to do for each phase of your product, and then, will dive deeper in each of the phases in future posts. I decided to draw analogy with a child to illustrate how the prototype grows =)</p><h3>Phase 1: “Baby”</h3><h4>When</h4><p>Initial phases of your product, ideation, conceptual work, brainstorming, etc.</p><h4>Tools</h4><p>Paper, pencil/pen.</p><h4>Process</h4><p>Sketch your concept on a piece of paper. It could be anything from napkins in a coffee shop, or printed <a href="http://getprototyping.com/resources/">templates</a> for a specific screen size. I try to always carry my notebook to sketch ideas, and I’ve tried all possible grid types. The best one that works for me is dotted grid, not as cluttered as squared grid, and not as messy as blank paper. A grid would help to keep the lines straight, especially if your sketch is more complex, but any piece of paper will work. That’s the beauty of paper prototyping — it’s the cheapest and fastest way to communicate ideas and validate high-level assumptions. I always start with paper.</p><h3>Phase 2: “Toddler”</h3><h4>When</h4><p>Figuring out new screen layout or user flow, minimizes paper format constraints when testing with users (interactions are more real than with paper)</p><h4>Tools</h4><p>There are a lot of options that can help you create medium-fidelity prototypes fast. My favourite is Balsamiq, I will be reviewing all tools in future posts.</p><h4>Process</h4><p>Working with a digital tool requires some basic skills, but anyone can figure it out within an hour. For example, Balsamiq has a built-in library of UI elements and it’s very easy and intuitive. By this time, you have likely created (and, I hope, tested) paper prototype and have a good idea of what needs to go into the digital version. Just analyze the testing results from the previous round and consider these insights when you start converting your paper prototype into digital format.</p><h3>Phase 3: “Teen”</h3><h4>When</h4><p>As you prototype matures, and you keep testing and iterating it, you will realize that you have the user flow and screens layout is performing quite well with your test participants. It means it’s time to increase your fidelity and switch gears. Time to test UI in more details e.g. colours, sizing, interactions, animations, etc. Usually, at this stage the visual fidelity will be very close to the soon-to-be-released production UI.</p><h4>Tools</h4><p>Even more tools in this category, and new ones appear on a regular basis. Some of them allow creating high-fidelity visual designs, and other also include functionality to create clickable interactive prototypes, which can make your prototype look and function exactly like a real working app or website would. Some of the tools a very impressive, and I will be reviewing and comparing them in future posts.</p><h4>Process</h4><p>This process requires the most effort, as it involves creating high-fidelity mockups and sometimes even code, depending on the chosen tool and results of your <a href="http://getprototyping.com/prototyping-methodology/step-1-define/">Definition step</a>. Even though creating a high-fidelity prototype will take noticeably more time than low- and medium-fidelity, the results of testing it will likely produce more valid insights. Some people will be distracted by the low fidelity of your earlier prototypes, and their feedback may be affected by the fact that what they see is so far off from what they expect to see as the end product. Also, if you need to show your prototype to investors, they will be expecting at least a high-fidelity clickable prototype (and sometimes even a working version which requires coding).</p><h4><a href="http://getprototyping.com/prototyping-methodology/step-3-test/">Step 3 — Test</a></h4><p><em>Originally published at </em><a href="http://getprototyping.com/prototyping-methodology/step-2-prototype/"><em>getprototyping.com</em></a><em> on November 2, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71f2625e6579" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping Methodology. Step 1 — Define]]></title>
            <link>https://medium.com/@kirillvechtomov/prototyping-methodology-step-1-define-7c6309229bab?source=rss-e7b99c38f8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c6309229bab</guid>
            <category><![CDATA[rapid-prototyping]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Kirill Vechtomov]]></dc:creator>
            <pubDate>Thu, 02 Nov 2017 00:26:57 GMT</pubDate>
            <atom:updated>2018-02-27T15:28:44.390Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Attention</strong>: This is a super important step.</p><p>You may find yourself a little impatient (like I am when I get super excited about a new idea =) which happens about every hour =) and you probably want to jump right into prototyping, but before you do it, you have to answer several questions. The answers will guide your prototyping and testing efforts and can potentially save you a lot of time. And we both know how crucial time is for a startup.</p><h3>1. Scope</h3><ul><li>Why do you want to prototype this? What are you trying to learn?</li><li>Do you have a new product idea and you want to validate a proof of concept?</li><li>Is it an enhancement that you want to run by your target audience before putting into next release?</li><li>You’ve identified a need for a new feature that your users want, and you want to understand where you should put the menu item for it, so people can find and use it.</li><li>One of the millions of other questions you may have.</li></ul><p>Every prototype has to have a specific question (or several) that it is supposed to help clarify what you want to learn. Otherwise, what exactly you are trying to achieve with it?</p><h3>2. Type</h3><p><strong>Vertical</strong> vs <strong>Horizontal</strong>.</p><p>Depending on the questions you define, you may need either vertical or horizontal prototype. Horizontal works better for broader learnings, like validating your overall startup idea. A vertical prototype is mostly used when you want to understand more low-level things, like a specific interaction pattern, or screen layout for your new feature. When you have an existing product that you are adding new feature to, go with vertical.</p><p>For example, the first prototype version for one of my startups, I just sketched 4 screens on paper, 1 screen per section of the platform. That’s a horizontal protoype. And later, when I was working on defining and designing a new flow for upgrading the subscription plan. And even though the platform had many screens, I prototyped only a few that were needed for this specific flow. That’s a vertical prototype.</p><h3>3. Fidelity/Level</h3><p>This is a big topic by itself, and I will be writing more about various nuances of the dimensions and fidelity levels used in prototyping. In brief:</p><ul><li>There are 3 fidelity levels: <strong>low-fidelity</strong>, <strong>medium-fidelity</strong>, and <strong>high-fidelity</strong>.</li><li>There are 3 dimensions of fidelities (if this makes sense): <strong>visual</strong>, <strong>functional</strong>, and <strong>content</strong>.</li><li>Any fidelity dimension may be of any level.</li></ul><p>For example, the sketch you see below has low fidelity in all 3 dimensions (visual, functional, content), it’s more abstract. Visually — not even close to what the app will look like. Functional — not functioning at all, you will have to simulate the flow (if needed) by manually changing screens based on user interactions. Content — not real content, just lines to communicate the idea and visual hierarchy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/0*fxAgoEaBx8MfRHde.jpg" /></figure><p>Usually, you start with low-fidelity prototypes at the beginning and increase the fidelity with further iterations.</p><h3>4. Logistics</h3><p>Questions you should answer:</p><ul><li>Whom are you testing with?</li><li>Where can you find them? (if you can)</li><li>How are you going to test it? Remotely or in-person? In an office or at where the user would likely use your app?</li><li>Will you be able to use a device with a screen?</li><li>Will you have Internet connection where you will be testing?</li><li>What tools are you going to use?</li></ul><p>For example, if you don’t have direct access to your users and will be testing remotely through an existing online usability testing tools, a paper prototype won’t be as valuable.</p><h4><a href="http://getprototyping.com/prototyping-methodology/step-2-prototype/">Step 2 — Prototype</a></h4><p><em>Originally published at </em><a href="http://getprototyping.com/prototyping-methodology/step-1-define/"><em>getprototyping.com</em></a><em> on November 2, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c6309229bab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping Methodology]]></title>
            <link>https://medium.com/@kirillvechtomov/prototyping-methodology-70b82f7c02b8?source=rss-e7b99c38f8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/70b82f7c02b8</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[rapid-prototyping]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Kirill Vechtomov]]></dc:creator>
            <pubDate>Fri, 20 Oct 2017 06:36:10 GMT</pubDate>
            <atom:updated>2018-02-27T15:18:14.170Z</atom:updated>
            <content:encoded><![CDATA[<p>Prototyping is a great method to get your ideas out of your head onto paper or screen, but what are you going to do with this stuff? A prototype is just one stage of a process, and you have to know and follow the process in order to benefit from it.</p><p>There are various interpretations of the number of steps in Rapid Prototyping (3–5 stages). I prefer explaining all 5 of them to highlight the bigger picture and draw attention to each of the steps because they are all critical to success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*lX3MmKodsEWQCIHcXc-KVQ.png" /></figure><h3><a href="http://getprototyping.com/prototyping-methodology/step-1-define/">1. Define</a></h3><p>You have to decide what you are going to test, what answers you are looking for, what type and level of fidelity will work best for your particular objective.</p><h3><a href="http://getprototyping.com/prototyping-methodology/step-2-prototype/">2. Prototype</a></h3><p>This is the prototyping itself when you produce something tangible that you can use to test. Depending on what kind of prototype you decided to use in the previous step, the result can be either physical or digital.</p><h3><a href="http://getprototyping.com/prototyping-methodology/step-3-test/">3. Test</a></h3><p>Even though you can use your prototype yourself, just to “think with your hands”, so to say, the most value comes from showing it to other people, the potential users, and stakeholders. Getting their feedback and gathering insights is what you are really looking for.</p><h3><a href="http://getprototyping.com/prototyping-methodology/step-4-learn/">4. Learn</a></h3><p>The testing results from the previous steps should feed into your thinking process. You should analyze what you’ve heard and seen and think carefully before jumping to any conclusions. The quality and validity of your learnings are very important. If you did testing incorrectly and asked the wrong questions, this may derail the whole process and send you down the rabbit hole.</p><h3>5. Iterate</h3><p>After decoding your test results and extracting the insights you were looking for, it’s time to apply all you’ve learned to the next version of your prototype.</p><p>Though this 5 steps process looks like a to-do list with a start and end, it is a good practice (and my strong recommendation) to continue prototyping, testing, and learning. <strong>A product that does not evolve is a dead product</strong> (unless you have a monopoly, then you probably don’t care about all the stuff I am telling, anyway =)</p><h4><a href="http://getprototyping.com/prototyping-methodology/step-1-define/">Step 1 — Define</a></h4><p><em>Originally published at </em><a href="http://getprototyping.com/prototyping-methodology/"><em>getprototyping.com</em></a><em> on October 20, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70b82f7c02b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>