<?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 Gytis Markevičius on Medium]]></title>
        <description><![CDATA[Stories by Gytis Markevičius on Medium]]></description>
        <link>https://medium.com/@gytismark?source=rss-cb8554375d0a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*sekG1m5MRuDuSlnmZeNGVQ.jpeg</url>
            <title>Stories by Gytis Markevičius on Medium</title>
            <link>https://medium.com/@gytismark?source=rss-cb8554375d0a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:34:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gytismark/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[Building a website: expectations vs reality]]></title>
            <link>https://medium.com/@gytismark/building-a-website-expectations-vs-reality-3ce2be50c1ab?source=rss-cb8554375d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ce2be50c1ab</guid>
            <category><![CDATA[website-design]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[expectations-vs-reality]]></category>
            <category><![CDATA[online-business]]></category>
            <category><![CDATA[online-marketing]]></category>
            <dc:creator><![CDATA[Gytis Markevičius]]></dc:creator>
            <pubDate>Fri, 29 Apr 2022 16:35:18 GMT</pubDate>
            <atom:updated>2022-05-02T12:46:23.617Z</atom:updated>
            <content:encoded><![CDATA[<h4>“I need a website!” they say. “Why do you think you need it?”, “Because I need to &lt;sell more, get more attention, or any other goal&gt;”.</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fnh9k1qzeLf99S%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fgive-it-to-me-nh9k1qzeLf99S&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2Fnh9k1qzeLf99S%2Fgiphy.gif%3Fcid%3D790b7611e6a55749aad2a140d2298328abd07f79c54aebe5%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="494" frameborder="0" scrolling="no"><a href="https://medium.com/media/2fd39da6c9f13efe18a4f24c27133e70/href">https://medium.com/media/2fd39da6c9f13efe18a4f24c27133e70/href</a></iframe><p>Before investing time and resources into building a new website, you need to have realistic expectations about what it can and cannot do.</p><h3>Website 101</h3><p>It is important to have a basic understanding of the service before you ask for it.</p><p>When you are thinking about building a website you need to consider two things: functionality and visuals.</p><p>The functionality is based on what the website needs to do. Does it need to sell, get leads, showcase content like photos or articles or promote your business?</p><p>The function will dictate the technical part of the project. The more you want it to do, the more time and money you will need to invest to build it.</p><p>The website also needs visuals that are usually made of branding, content (text and photos) and design (graphic, UI and UX design).</p><p>Visuals generally depend on your brand and your audience preferences. You want to speak to your audience through a unique perspective (i.e. your brand). This is also where you have the most freedom. You can decide what visual language you want to use as there are many ways to appeal to the same audience.</p><h3>Answer the main question</h3><blockquote><em>The first question you need to answer yourself is “What does the website need to achieve?”.</em></blockquote><p>Maybe you have a short-term rental business and you want a website that facilitates bookings or maybe you want people to read your articles, or just sell them something.</p><p>A website can help you achieve all of these objectives, but you need to know exactly what your main goal is. Write it down describing all the details that you can think of.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3dggJ5AmqDP93APjjx%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2FDealorNoDeal-deal-dealornodeal-or-no-3dggJ5AmqDP93APjjx&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2F3dggJ5AmqDP93APjjx%2Fgiphy.gif%3Fcid%3D790b7611291009be5afa27cdd86f36ffc0cb0dc0b64f1502%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/c3403f8fecbddd1a09af5bf9cd4ef7e2/href">https://medium.com/media/c3403f8fecbddd1a09af5bf9cd4ef7e2/href</a></iframe><p>This will help to keep your eye on the target. It will also help if you are planning to hire someone to build a website for you as this will most likely be one of the first questions they’ll ask you.</p><h3>When do you need a website?</h3><blockquote><em>The main benefit of having a website is that you are in control of your content.</em></blockquote><p>When you use other websites or platforms to post your content or sell products, you have to play by their rules. If they change them, you will have to oblige. If they decide to favour video content vs pictures you will need to change your content to stay afloat and competitive.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FJUYApzwPNTil9Q5O0r%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fbloodshotmovie-vin-diesel-bloodshot-vindiesel-JUYApzwPNTil9Q5O0r&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2FJUYApzwPNTil9Q5O0r%2Fgiphy.gif%3Fcid%3D790b7611a8a97bfcc3801ff74dbf3eb6b9b12738fe75e720%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/645aca5b766975d50878fc6814f9f9e8/href">https://medium.com/media/645aca5b766975d50878fc6814f9f9e8/href</a></iframe><p>Big social media websites have massive user bases and a lot of businesses are advertising there, so everyone competes for attention.</p><p>If you get people to come to your website, you are the only thing they will pay attention to as long as they are engaged, thus your odds for success are much higher.</p><p>If you are a content creator or you want to sell something, you probably want to have your website.</p><blockquote>Your website, your content, your rules.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fkbz6iLCGXDLgI%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fking-of-the-world-im-titanic-kbz6iLCGXDLgI&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fkbz6iLCGXDLgI%2Fgiphy.gif%3Fcid%3D790b761164e14a8b336b0d562506079e1af2fdc1df68a533%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="355" frameborder="0" scrolling="no"><a href="https://medium.com/media/d953a57757830936726e0d373bb7b81f/href">https://medium.com/media/d953a57757830936726e0d373bb7b81f/href</a></iframe><p>The catch is that you will need considerably more time and effort to get people to come to your website. This is where you will need to invest in marketing, search engine optimisation (SEO), content strategy, advertising, etc.</p><h3>Where to start?</h3><p>Now, for those of you who need a website to run a business, usually an e-shop or blog, I would recommend starting with a template.</p><p>There is a bunch of website builders out there. Google for the top 10 and pick the one that matches your needs. It is quick and easy. And if you can spare a few additional dollars, you can get a higher-end template that will look better than most free templates out there.</p><p>What is important is that you get started. You can always upgrade, change or get a custom-designed website later.</p><blockquote><em>Content is king. It is not the template that people come for to your site; it is what you offer them.</em></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FAobQDNI4K7a4U%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2FAobQDNI4K7a4U&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2FAobQDNI4K7a4U%2Fgiphy.gif%3Fcid%3D790b7611a5cb5d9a79bb25229c1baa9ff569c8e3eb65e86f%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/c0f7c759c7ac44d3e48e89996aca4705/href">https://medium.com/media/c0f7c759c7ac44d3e48e89996aca4705/href</a></iframe><h3>How much will it cost?</h3><p>Even if you have a clear idea of why you need a website, it may not be the right time to build it, especially if you are just starting out.</p><p>A website, even if you built it yourself, comes with additional expenses. Even the most basic website will need a domain name (e.g. <a href="http://www.gytismark.com/">www.gytismark.com</a>) and hosting (a place where your website will live) which can cost anywhere from $70 to $500 a year depending on what you need.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FLdOyjZ7io5Msw%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fmake-it-rain-get-paid-LdOyjZ7io5Msw&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExOTc1YTFiNzdjNzVlZDM2MTdhMzQwMjc4MmU5OTYwNmM5MDUwM2ZhMyZlcD12MV9pbnRlcm5hbF9naWZzX2dpZklkJmN0PWc%2FLdOyjZ7io5Msw%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="325" frameborder="0" scrolling="no"><a href="https://medium.com/media/651f2821908523f99ea3f6786e8e5ff5/href">https://medium.com/media/651f2821908523f99ea3f6786e8e5ff5/href</a></iframe><p>If you are building an e-shop there will be additional costs to manage your stock, shipping, payments, etc. Different business goals will require a different mix of features and complexity and will affect the overall cost of building and maintaining the website.</p><p>Your two main options are:</p><ul><li>If you have the know-how* — *built it yourself. This will save you money a the cost of your time (depending on your skills level).</li><li>If you have zero knowledge* — *hire a freelancer or a company. It will cost you more but will save you a lot of time and headache.</li></ul><p><strong>Worth knowing.</strong> The website can be built using a template or completely from scratch. However, there are some middle options where freelancers can pick and tailor templates to your needs.</p><p>If you have specific needs or a unique situation, hire a product designer who can design everything from scratch based on your unique business goals, market trends, marketing strategy, and user profile to create the best possible experience for you and for your customers (learn more at <a href="http://gytismark.com/">gytismark.com</a>).</p><p>💡 <strong>Word of advice.</strong> If you have better things to do than building a website and you can afford it — hire someone to do it for you. Focus on the things that cannot be outsourced as easily like networking, client relations and management.</p><p>I am convinced that most people who use computers on daily basis could build a website using website building platforms. The question is: Should they?</p><p>Speaking from experience, I have seen people overestimating themselves and ending up with a very bad website that probably does more damage than good. Plus, they spend a lot of time building it and when the results don’t meet expectations, that time is wasted.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FpdVzZpZ6mLp9MhP36y%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Ftheoffice-the-office-tv-new-boss-pdVzZpZ6mLp9MhP36y&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2FpdVzZpZ6mLp9MhP36y%2Fgiphy.gif%3Fcid%3D790b7611ce332cc0b5691f690a9e3ec34f602243fde8afcd%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="362" frameborder="0" scrolling="no"><a href="https://medium.com/media/c66eeeff5126439cd7c21ec0570c210d/href">https://medium.com/media/c66eeeff5126439cd7c21ec0570c210d/href</a></iframe><p>Remember that people have fairly high standards for web experience. If you see a website that doesn’t work or looks strange would you buy anything from that business?</p><h3>The biggest misunderstanding</h3><p>Once you have your website up and running, what you have is a place where people can come to see your product.</p><p>But just because they can, it doesn’t mean they will. You need to figure out how to get them to come to you. I am talking about marketing, SEO, advertising strategy, etc. Getting a website is probably the easiest step in the whole process of trying to sell something.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FghuvaCOI6GOoTX0RmH%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FghuvaCOI6GOoTX0RmH%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FghuvaCOI6GOoTX0RmH%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="362" frameborder="0" scrolling="no"><a href="https://medium.com/media/08e01fb59c212dd1e4377269d26873cb/href">https://medium.com/media/08e01fb59c212dd1e4377269d26873cb/href</a></iframe><blockquote><em>The success or failure of the website depends on having the correct assumptions and putting in the work. It may run like a swiss watch and look like an Italian sports car, but if no one visits it, you won’t get much out of it.</em></blockquote><p>This happens more often than one would think. People get custom websites and then they sit and wait for the money to start pouring. Ain’t going to happen, pal.</p><p>In other words, you need to get people to come to your website. Then you need to ensure that it works and that the users’ experience is great. If website visitors feel confident about your brand and products, they will feel more inclined to buy something.</p><p>If you are a content creator, you will have to commit to creating and uploading your content regularly. And I mean REGULARLY. That will be your primary product and the main way to attract users. If you are selling products, you will probably focus on advertising and marketing campaigns.</p><p>The percentage of people coming to your website vs those who buy something is very low (less than 10%). It means that you need to get a lot of people coming in.</p><p>Once you get people coming in, you will be able to track them to see how users interact with your website and what is their experience. This is where things get interesting (at least for me) as this is when you can start testing different ideas to optimise your website for the best results.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F12aW6JtfvUdcdO%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fted-trump-cruz-12aW6JtfvUdcdO&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2F12aW6JtfvUdcdO%2Fgiphy.gif%3Fcid%3D790b7611ec5f85867312532a6d4184e4108c83b24f4459cd%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="594" frameborder="0" scrolling="no"><a href="https://medium.com/media/667e42bb0fc55106b695f98f8733a49d/href">https://medium.com/media/667e42bb0fc55106b695f98f8733a49d/href</a></iframe><blockquote><em>So when you think of getting a website, think about how you will engage people, make them comfortable and then eventually nudge them to do something. A good product designer can help you figure this out.</em></blockquote><p>You can learn more about what product designers do in my article below.</p><p><a href="https://medium.com/@gytismark/what-do-others-think-product-designers-do-vs-what-we-actually-do-57ab717bdf65">What do others think product designers do vs what we actually do</a></p><p><strong>Thanks for reading!</strong></p><p>Learn more about us at <a href="http://www.gytismark.com/">GytisMark</a> if you want to get in contact or find more useful articles!</p><p>Edited by <a href="https://medium.com/u/3b536ec228a9">Adele Mark</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ce2be50c1ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What do others think product designers do vs what we actually do]]></title>
            <link>https://medium.com/@gytismark/what-do-others-think-product-designers-do-vs-what-we-actually-do-57ab717bdf65?source=rss-cb8554375d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/57ab717bdf65</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-designer]]></category>
            <category><![CDATA[heuristic-evaluation]]></category>
            <category><![CDATA[competitive-research]]></category>
            <category><![CDATA[usability-testing]]></category>
            <dc:creator><![CDATA[Gytis Markevičius]]></dc:creator>
            <pubDate>Fri, 01 Apr 2022 11:23:52 GMT</pubDate>
            <atom:updated>2022-05-02T12:46:57.001Z</atom:updated>
            <content:encoded><![CDATA[<h4>“I couldn’t work as a product/UX designer because I am not that creative.” Rings a bell, doesn’t it?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*benFGeCpA8LnI8-7" /><figcaption>Photo by <a href="https://unsplash.com/@thesaboo?utm_source=medium&amp;utm_medium=referral">Sascha Bosshard</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I recently asked a former client why he hired me for the job. One of the main reasons was that I had an artistic background (I played instruments, painted, and so forth). After hearing that, the opening quote resurfaced as I remembered developers and managers saying the same thing repeatedly. It got me thinking about how non-designers perceive our métier.</p><p>This article aims to give non-designers a more wholesome view of who we are and what we actually do.</p><h3>So what is the problem?</h3><p>After spending many years educating myself on being an effective product designer, it bugs me whenever creativity wins over work experience, knowledge or design skills when landing a job. (I don’t expect everyone to feel the same).</p><p>Think of it this way. You work out five days a week and people say that you are in good shape because you have good genes. How does that make you feel? Call me crazy, but I think working out has something to do with being fit as well.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fjc1Fu8DXTV184%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fjc1Fu8DXTV184%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fjc1Fu8DXTV184%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="181" frameborder="0" scrolling="no"><a href="https://medium.com/media/644106971bfe5651b0c74ee43f914395/href">https://medium.com/media/644106971bfe5651b0c74ee43f914395/href</a></iframe><p>So, <em>all I am saying is</em> that even though having a creative background is helpful, the years that I have spent practising and sharpening my skills is what brings value to the table.</p><h3>What I actually do</h3><p>The misunderstanding probably comes from not seeing the whole story of what a product designer does and how he works. Let’s have a closer look.</p><p>As a product designer, I protect the interest of users AND businesses alike (i.e. what I do). It is not an easy task to accomplish as the objectives of both parties usually have different end goals.</p><p>To make both parties happy, I soak up all the information I can get (research) to generate and test ideas and measure them against a business and user goals (i.e. how I do it).</p><p>Success heavily depends on the ability to communicate with the rest of the product team and involve stakeholders at the right time.</p><h3>What I actually (detailed version)</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F2L3CDIUD1h9StO4xQg%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F2L3CDIUD1h9StO4xQg%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F2L3CDIUD1h9StO4xQg%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="222" frameborder="0" scrolling="no"><a href="https://medium.com/media/cb295b861abca6bea31a98e0aa564c52/href">https://medium.com/media/cb295b861abca6bea31a98e0aa564c52/href</a></iframe><p>I generate, collect and analyse a lot of different data sources as part of project discovery, like:</p><ul><li>usability testing;</li><li>heuristic evaluation;</li><li>marketing reports;</li><li>competitive research;</li><li>demographics;</li><li>business roadmap;</li><li>market trends;</li><li>technical requirements;</li><li>future growth plans etc.;</li></ul><p>Analysis of such data helps to understand where the product stands in the market and how it performs against existing business and user goals. In turn, it helps to set the product development objectives going forward. I then complete the missing parts like user personas, competitive research and user journeys.</p><p>Once I know where the product stands in the market (only applicable for existing products), together with the team, we start creating ideas to improve the product by developing new features or improving existing ones.</p><p>I then put thoughts on paper through writing, sketching and high-fidelity design, testing all of them as early as possible.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxT5LMNTLldGyADxzgI%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxT5LMNTLldGyADxzgI%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FxT5LMNTLldGyADxzgI%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="328" frameborder="0" scrolling="no"><a href="https://medium.com/media/076e448db12fda44e43e5cfd715563c7/href">https://medium.com/media/076e448db12fda44e43e5cfd715563c7/href</a></iframe><p>Once the team implements new designs, we do real-world testing that restarts the cycle and takes me back to analysing new data.</p><h3>The summary of what I (product designer) actually do</h3><p>I use many methods and proven practices to review data, create tests and strategic plans, and examine technical requirements and business agendas to design better, more effective products.</p><p>The actual design is just one part of many in the product (re)designing process. It is easy to fixate on the visual that everyone sees. It’s similar to spotting a code that a developer writes or an ad that a marketer creates — what people see is just the tip of the iceberg.</p><h3>The essence of product design</h3><p>In short, designers are problem solvers. While there is a significant amount of overlap with fine arts, the main difference is that our task is to create functional and useful first, good looking second.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FUKkes2qN2T70s%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FUKkes2qN2T70s%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FUKkes2qN2T70s%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="375" frameborder="0" scrolling="no"><a href="https://medium.com/media/548a7c1118cb123de0a3c44f069572bf/href">https://medium.com/media/548a7c1118cb123de0a3c44f069572bf/href</a></iframe><p>Don’t get me wrong. Good looks can perform a function, but it is often not an essential part of a designer’s work. It has to bring some measurable results and not just look pretty; otherwise, you can hang it on the wall.</p><h3>The bottom line</h3><p>We follow certain processes and possess a lot of knowledge about what we do, which is complemented by years of work experience.</p><p>While the creative background helps to have an open mind, it should not be the sole deciding factor when picking a product designer for your next project.</p><p><strong>Thanks for reading!</strong></p><p>Learn more about us at <a href="http://www.gytismark.com/">GytisMark</a> if you want to get in contact or find more useful articles!</p><p>Edited by <a href="https://medium.com/u/3b536ec228a9">Adele Mark</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57ab717bdf65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating fallback plans, or what if it doesn’t go as planned?]]></title>
            <link>https://medium.com/@gytismark/creating-fallback-plans-or-what-if-it-doesnt-go-as-planned-7fc4051a93bc?source=rss-cb8554375d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fc4051a93bc</guid>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-features]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <dc:creator><![CDATA[Gytis Markevičius]]></dc:creator>
            <pubDate>Fri, 25 Feb 2022 09:47:28 GMT</pubDate>
            <atom:updated>2022-05-02T12:47:33.852Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="What to do if your new product doesn’t work as planned?" src="https://cdn-images-1.medium.com/max/1024/0*QDgw2h2x7Qx5nvTw" /><figcaption>Photo by <a href="https://unsplash.com/@profwicks?utm_source=medium&amp;utm_medium=referral">Ben Wicks</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What to do if your new product doesn’t work as planned?</h3><h4>Sending an email invite to your friend (i.e. referral) via email that goes to their spam folder is not very useful, neither to the sender nor to the receiver and especially not to the business.</h4><p>How to plan for when things don’t go as planned? A simple answer — create backup plans. In plain English, provide alternative ways of achieving the same result.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3o7btPCcdNniyf0ArS%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fcbc-comedy-what-3o7btPCcdNniyf0ArS&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExYnl6dDE2aDZyMmt0MjhiMGkzMWhodmt2b2pkYmRjZ211OTUzMGYzdCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2F3o7btPCcdNniyf0ArS%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/b2a1a85d2bcf1b28fa624e978625a39d/href">https://medium.com/media/b2a1a85d2bcf1b28fa624e978625a39d/href</a></iframe><h3><strong>How?</strong></h3><p>The critical part of designing fallback plans is to ensure that they take advantage of other functionality to accomplish the same thing.</p><p>Suppose email lands in the spam folder, and the user needs another way to send the invitation link. A simple alternative is the “copy invitation link” functionality because it relies on a different feature and uses various channels to reach the recipient.</p><p>In this case, after copying the link user can share it via any form of communication like social media or even text message. Thus the user has more control and wider choice, and it provides a more personal way of achieving the result.</p><p>In other words, it is an entirely different way of achieving the intended result if other ways fail somewhere along the way.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F8SrFK6yJDmbtiE7P6l%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F8SrFK6yJDmbtiE7P6l%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F8SrFK6yJDmbtiE7P6l%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="243" frameborder="0" scrolling="no"><a href="https://medium.com/media/f688256c3ba9d53753f36ff99e67f020/href">https://medium.com/media/f688256c3ba9d53753f36ff99e67f020/href</a></iframe><h3><strong>What if</strong></h3><p>What if the user doesn’t see the invite link button? If that happens, we can make it more prominent OR create another way of accomplishing the task. That may seem like going down the rabbit hole, and sometimes it is precisely that.</p><p>At some point, you need to stop because you may start making up some unrealistic cases that have a 0.000001% chance of ever happening (the number is not statistically proven). Low probability does not deny possibility but let’s use some common sense here.</p><p>I usually go for three fallback scenarios. It rarely needs more. However, if it requires more, it could mean that you have made some bad decisions earlier and need to go back to the drawing board. If you decide to design more than two ways to do a single task, it pays to consider development time. Please don’t overdo it because developers might come for you when you sleep.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl4FGH7jsiciu4tmaA%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl4FGH7jsiciu4tmaA%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fl4FGH7jsiciu4tmaA%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="217" frameborder="0" scrolling="no"><a href="https://medium.com/media/ab89088f67aee21d3899a40238fa30e0/href">https://medium.com/media/ab89088f67aee21d3899a40238fa30e0/href</a></iframe><p><strong>Other examples</strong></p><blockquote>Most features in a product should have at least two ways of using it.</blockquote><p>Think of search, for example. When you visit an online store, you usually have at least two options to find what you are looking for. You can use either the navigation or the search field.</p><p>The same principle is used for most core features like signing up (manual vs via social media), adding items to a basket (from home vs from details page) or paying (card vs PayPal).</p><p>More minor features like adding your profile photo (browse pc vs upload vs past link), creating new items in a table (plus icon vs dedicated button) or cancelling a popup (X icon in the corner vs button vs click outside the box).</p><p>All of them have at least two ways of achieving the same thing. Tailoring to different preferences improves usability because you may not see the little X icon, but you might notice the “Cancel” button instead and vice versa.</p><p>They usually come with these prescriptions when using standard features, but you need to add a plan B whenever you create something new.</p><p>Using standard features usually “come” with these prescriptions, but if you create something new, you will need to add a plan B purposefully.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl3vR6aasfs0Ae3qdG%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl3vR6aasfs0Ae3qdG%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fl3vR6aasfs0Ae3qdG%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="359" frameborder="0" scrolling="no"><a href="https://medium.com/media/efefe10a2d83f40dca95dc8a5ec4ca4a/href">https://medium.com/media/efefe10a2d83f40dca95dc8a5ec4ca4a/href</a></iframe><h3><strong>Simple action plan</strong></h3><p>In short, identify the core features and don’t forget to look at the new ones you have created. If it is an integral part of achieving a specific task, you should find at least one other way to enable users to do it.</p><blockquote>Remember to make it simple and obvious. New features have an especially high risk of being misinterpreted, hence having a fallback plan minimises the risk of users misunderstanding features and bouncing from the app.</blockquote><h3><strong>Takeaways</strong></h3><p>So here you go.</p><ul><li>Always consider at least two scenarios for the essential tasks of your application.</li><li>Users can behave in mysterious ways but don’t chase the rabbit into the hole.</li><li>Pay close attention to new features you create.</li><li>If in doubt, use common sense and standard practices.</li><li>Be conscious of development efforts.</li></ul><p>Thanks for reading!</p><p>Learn more about us at <a href="http://www.gytismark.com/">GytisMark</a> if you want to get in contact or find more cool articles!</p><p>Edited by <a href="https://medium.com/u/3b536ec228a9">Adele Mark</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fc4051a93bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to know if you are right?]]></title>
            <link>https://medium.com/@gytismark/how-to-know-if-you-are-right-e2866f850167?source=rss-cb8554375d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2866f850167</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[testing-framework]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Gytis Markevičius]]></dc:creator>
            <pubDate>Tue, 20 Jul 2021 13:13:00 GMT</pubDate>
            <atom:updated>2021-07-20T13:13:00.706Z</atom:updated>
            <content:encoded><![CDATA[<p>I have recently read a good summary about user testing. It is from the book called Influence by Robert B. Cialdini, PhD, and it points out something self-evident yet profound. It says that people determine what is correct by checking out what other people think is correct. It sounded wrong the first time I read it because I always thought that the right way to check if you are correct is to use scientific methods. Then I read it a few more times until it occurred that while it is not science grade, it is very true in everyday life, and I think it is true with user testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jTNBgCg21qnct1xB6Fs8JA.jpeg" /></figure><p>When we do qualitative user testing, we are essentially interested in what people think and how they react to our designs. So, we are ultimately testing if our answer to users’ problems matches theirs. Having this thought in my mind helps me to put things in a simpler perspective. We may think that we have found THE SOLUTION, but until we see that they actually find it useful, we cannot know for sure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2866f850167" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting better goals with great UX]]></title>
            <link>https://medium.com/@gytismark/setting-better-goals-with-great-ux-7147e2edb7d7?source=rss-cb8554375d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7147e2edb7d7</guid>
            <category><![CDATA[ixdonline]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Gytis Markevičius]]></dc:creator>
            <pubDate>Tue, 14 Jul 2020 09:41:57 GMT</pubDate>
            <atom:updated>2020-09-17T12:20:15.259Z</atom:updated>
            <content:encoded><![CDATA[<p>We all hope for the best, but hopes alone don’t change a thing. The recipe for success is relatively simple: make small smart choices every day for the rest of your life, and you will achieve great things. However, staying consistent can be challenging. We often need some help to plan, to make smart choices and to keep on track.</p><p>In the following project, I wanted to learn more about how people set goals and how they aim to achieve them. Can great user experience (UX) help people to get better at these things?</p><p>I will take you through my process. <strong>The goal:</strong> create an application that helps people to set better goals and achieve better results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*29b_AqGrQwf24jdPhHdDvQ.jpeg" /></figure><h3>1. Seeing the problem from up close</h3><blockquote><em>As Yogi Berra once said: you can observe a lot just by watching.</em></blockquote><p>Motivation is easily one of the most intriguing and unclear subjects in human psychology. We all want to stay consistent with our new morning routine or to save more money. In the end, it comes down to how consistent and motivated we are. These two factors were also apparent in user interviews. With all the best reasons to do something, users still failed to stick with the new regime. The biggest problem is that they didn’t know why.</p><p>The truth lies somewhere within Jim Rohn’s words, I guess. “What’s easy to do, is also easy not to do.”</p><p>The people I interviewed walked me through their failed attempts to set goals or stick with a new routine. I noted down about 30 apparent reasons for the breakdown, 5 of which were present across all participants and scenarios.</p><ul><li>Lack of simple step by step plan to reach their goals</li><li>Lack of positive reinforcement from the outside once it gets hard</li><li>Feeling alone</li><li>Not seeing/feeling instant benefits or sudden change at the beginning</li><li>Intrusive apps’ notifications are annoying instead of being helpful or engaging</li></ul><p>In short, people care about two things:</p><ol><li>How to set appropriate goals and make a plan that is easy to follow?</li><li>How to track the incremental progress in a motivating way?</li></ol><p>From all the ways to address these problems, I narrowed down to 4 overlapping solutions.</p><ul><li><strong>Setting clear, descriptive goals that help to uncover the main motivation.</strong> This also helps to see if the goal is worth achieving.</li><li><strong>Setting milestones and deadlines with consequences.</strong> Milestones will help to see the incremental changes over time while deadliness (with option to bet and thus increase motivation) will help to stay on track.</li><li><strong>Partnering with someone.</strong> Being accountable to other people instead of feeling alone could increase inner motivation.</li><li><strong>Learning from credible sources of information.</strong> Community tested and approved techniques and resources could help to set realistic expectations, plan better and be more consistent as a result.</li></ul><h3>2. Visualising possible solutions</h3><p>A product never exists in a vacuum. Storyboards help to put the solution in the context and convey the essence of the idea to other decision-makers.</p><p>Once the context is clear, I used paper prototypes to outline the main functionality of the product on a screen by screen basis. It is a quick and dirty way of seeing what is working and what challenges I need to address next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dI-K2PnGNZ1eCm-Y7vFp3A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YfIJl4erw25EoOS7uzrUgw.jpeg" /><figcaption>Scenario 1. Stay motivated by finding a goal-seeking partner that keeps you accountable by weekly calls.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8w9A_DPSn4gXX4S4pl-5Gw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-fZrEWd5Ip2ZrF1yEp-BHg.jpeg" /><figcaption>Scenario 2. Set goal strategy by reading useful resources recommended by the community.</figcaption></figure><h3>3. Fixing big mistakes early</h3><p>Design can succeed or fail in many ways. A good rule of thumb is to do as much testing as you can, as soon as you can. Going through your design with Jacob Nielsen’s Design Heuristics in mind is an excellent place to start.</p><p>This initial clean up helps to identify and fix significant issues of usability, navigation, and UX early on. Having this in your process usually makes future user testing much more fruitful.</p><p>An evaluation revealed that the app should provide more feedback. It is challenging to strike a perfect balance of showing just enough before it becomes annoying and thus dismissed. The evaluation also revealed a lack of flexibility and customisation. Pre-sets are great for new users, but more knowledgeable users could benefit from personalisation.</p><h3>4. Building the digital prototype</h3><p>After testing paper prototypes, it was time to build a digital version. I used the Figma online prototyping tool to outline the low fidelity screens and build upon them as I progress to develop the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*mBtXxeF5OS8DO029IMtqPA.png" /></figure><h3>5. Testing</h3><p>Further in-person testing yielded smaller but necessary improvements until the screen flow was ready for online testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rA2v02BdkhUFOUXeCe7Ptw.png" /></figure><p>Online testing confirmed that the solution addresses the core problems as intended. Goal setting is clear and straightforward, with just enough context and relevant resources provided for better strategies. Finding a partner to be supported by and be accountable for is also quick and easy. Additionally, testers appreciated clean and intuitive navigation, as well as the overall execution of the app.</p><p>Fine-tuning the product later in progress can take a long time, especially if it is not appropriately measured. To avoid biases, I used A/B testing to make a data-driven decision on any future changes.</p><p>I have finally finished the prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uWCkBvs98uAfvgDENtHDKg.png" /><figcaption>Setting clear, descriptive goals that help to uncover the primary motivation.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*WZODy4zu4GeA0MWyqKfmCg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*8B3D4wc2-etXqDlgU6q9DQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*L4gD8B_5qD3TQDS_Lm4Qig.jpeg" /></figure><h3>Overview</h3><p>My observations are centred around achieving goals. I wanted to know how people adopt new habits or change old ones, how they set goals and aim to accomplish them. People I have observed had a hard time staying consistent and motivated. They wanted to achieve more but didn’t know where and how to start. Therefore, my project focuses on helping users to set clear, defined and attainable goals with real and meaningful motivation. Furthermore, the project provides community curated resources and allow them to find a partner with similar interests to keep them accountable.</p><p><em>Edited by </em><a href="https://medium.com/u/3b536ec228a9"><em>Adele Mark</em></a></p><p>Thank you for reading. I hope you found it useful. 🙂</p><p>Read the full case study at <a href="http://www.gytismark.com/">www.gytismark.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7147e2edb7d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to improve specification document process (case study)]]></title>
            <link>https://medium.com/@gytismark/how-to-improve-specification-document-process-case-study-57758534afe8?source=rss-cb8554375d0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/57758534afe8</guid>
            <category><![CDATA[specification-document]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Gytis Markevičius]]></dc:creator>
            <pubDate>Thu, 23 Apr 2020 13:44:53 GMT</pubDate>
            <atom:updated>2020-09-17T12:20:33.460Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to improve specification document process remotely (case study)</h3><p>I was called to audit and improve the writing process of specification document (further referred to as spec) because of the slow turnaround and collaboration issues between different departments.</p><p>Before jumping into it, let’s agree on what the <strong>specification document</strong> is and what it is for. While it may vary slightly, the specification document in this company was a file used to document technical aspects of the application. It was designed to outline the requirements and fundamental architecture of the app and used as a primary resource for the following work.</p><h3>1. Diagnose before prescribing</h3><p>At first sight, the internal spec writing process seemed complex. So I dug deeper to understand how it works and which parts of the process are faulty and cause problems later on.</p><p>In a nutshell, the process looked something like this: the technical lead would build the first draft with the client and then pass it on to the design and development team that would use it as a blueprint to develop the product. Essentially, it was supposed to align everyone’s expectations. So far, so good, right? Not exactly. Companies are pretty good at sweeping their problems under the carpet, so to an unsuspecting visitor, everything may seem in order. I needed more information, meaning more research had to be done. The first place I looked at was the powerhouse of the company that keep the wheels turning — the developers. After talking with them, I found that it may take anywhere from few weeks up to a few months for them to see the first draft of the spec. It would then take another week or so for everyone to familiarise with it and only a couple days to give feedback. I then continued interviewing the design team that would create a separate document with use cases, user interfaces and mockups upon receiving the initial spec. Their wait time was about the same as developers (see figure 1). Needless to say that the two documents produced by the technical lead and design team looked very different. The development team would then use both sources during development. The documents would then get updated asynchronously leading to all kinds of misunderstandings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8lNq7pDu6TfL0RHSDZKLrA.png" /><figcaption>Figure 1. The initial spec writing process</figcaption></figure><p>The process looked like the relay race where only a single person can hold a baton at a given time while others impatiently wait for their turn. What was supposed to be a quick race seemed like a marathon instead. In the end, it seemed like the first and the last member of the team participated in different races altogether wasting everyone’s time and causing miscommunication on both ends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Ly3556n4E5b-1D3Sp-4Sw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@bradencollum?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Braden Collum</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>2. Finding the right problem to solve</h3><p>Before jumping into solutions we needed to identify the <strong>main problem that would generate the most value</strong>. After a quick brainstorming session followed by a quick vote, we have identified several important problems.</p><ul><li>Lack of transparency;</li><li>Lack of collaboration between both technical and design teams;</li><li>Unclear process;</li><li>Two different documents to work from (one too many);</li><li>Not effective feedback loop;</li></ul><p>I like to look for connections and ways to solve multiple problems by solving just a few. If you dig deep enough to find the root problem this suddenly becomes possible. After some discussion, it became apparent that the complete <strong><em>visibility</em></strong> of the process would allow to <strong><em>collaborate</em></strong> on a single document and share <strong><em>feedback</em></strong> sooner.</p><h3>3. The solution</h3><p>There is always more than one way to solve the problem. Initially, we noted all possible solutions and then sorted all of them by how much effort it will require and how much value it would bring (see figure 2 below). Then we selected the ones that would bring the most value and require the least effort. That showed us the optimal steps to the solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sQrecGBI4MKuJBl_bfcDbg.png" /><figcaption>Figure 2. Value vs effort</figcaption></figure><p>The <strong>first</strong> step was to set up a “work in progress” folder where the team would put all moving parts of the spec (client needs, technical requirements/limitations and design assets). The folder was to host all resources in one place providing complete visibility of the current state of the spec. This allows designers and developers to ideate, prototype and test the ideas to fail quickly and provide valuable feedback. This would work in cycles slowly moulding itself into a single document. One file to rule them all (for all the fans out there)!</p><p>The <strong>second</strong> step was to design a process that would facilitate collaboration and sharing feedback. For people to collaborate effectively, they need a defined goal (check), milestones (set by the product managers — check), reasons to do it (check) and support to stay on track (management was more than happy to keep the tabs, so — check). To get the ball rolling, I suggested getting developers and designers on a few initial client calls. This helps to understand what the client is looking for and makes the team feel like an integral part of the process from the get-go.</p><p>I left the rest to sort out for themselves. Mainly because we, people in general, are much more likely to continue on a path that we have chosen ourselves. Even though we have not outlined a detailed process to follow (just a basic framework), with transparency and collaboration in place, it was no longer a problem.</p><h3>4. Overview</h3><p>Bit by bit everything started to fall into place. Transparency allowed everyone to contribute to the overall development from day one. The newly implemented design cycles (i.e. ideate, prototype, test) helped to improve the initial ideas while they were still on paper. In the end, the overall spec writing process became almost twice as fast and yelled about 25% fewer issues down the road, therefore, became more effective (see figure 3). Previously purely technical document was now infused with user flows, diagrams and mockups. The overall perception changed from an isolated document to a document owned by everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u9KayGq6nCubbVnOuUJbqw.png" /><figcaption>Figure 3. The improved spec writing process (before and after)</figcaption></figure><p>When we allow smart people to take ownership and work on a common goal great things can happen.</p><p><em>Edited by </em><a href="https://medium.com/u/3b536ec228a9"><em>Adele Mark</em></a></p><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57758534afe8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>