<?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 Mark Levinson on Medium]]></title>
        <description><![CDATA[Stories by Mark Levinson on Medium]]></description>
        <link>https://medium.com/@marklevi?source=rss-88e3209dbb4a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8EbTW8KkiZFDO8ydfI9JzA.jpeg</url>
            <title>Stories by Mark Levinson on Medium</title>
            <link>https://medium.com/@marklevi?source=rss-88e3209dbb4a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:26:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marklevi/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[5 common problems in SaaS onboarding design]]></title>
            <link>https://medium.com/@marklevi/5-common-problems-in-saas-onboarding-design-a8efd4525fee?source=rss-88e3209dbb4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8efd4525fee</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Mark Levinson]]></dc:creator>
            <pubDate>Thu, 12 Jan 2023 11:36:24 GMT</pubDate>
            <atom:updated>2023-01-21T15:23:46.668Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*crom08LQVL5WZjG9I8tZqw.jpeg" /></figure><p>SaaS onboarding wizards are often a battleground between different stakeholders. C-suite guys want the final result out as fast as possible. Product managers want improved metrics in each individual step. Designers advocate for a good user experience and quality UI design. Marketers want the most sales with the highest margins. With each department pulling in a different direction it’s not easy to stay consistent and on point. Pulling off a good onboarding is a complex challenge.</p><p>I’ve been <a href="http://www.marklevi.com/">designing</a> and A/B testing onboarding wizards for several hyper-growth companies like <a href="https://sayata.com/">Sayata</a>, <a href="https://komodor.com/">Komodor</a>, <a href="http://www.datricks.com/">Datricks</a>, <a href="https://www.hedge-tech.com/">Hedgetech</a>, <a href="https://www.anymaint.com/">Anymaint</a>, and others. In my experience, good user experience design for the onboarding stage should be a top priority. <br>Here are my top 5 SaaS onboarding mistakes that may cause your conversion rates to drop.</p><h4>Too long</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qU97oBjhqE7zTDkNbCsxaA.jpeg" /></figure><p>Onboarding takes time, both for the user to walk through and the company to design and develop. A lengthy process can be a drain on resources and can discourage users from using the product, so why do it? In a competitive market, a long onboarding process can be a disadvantage for a company as users may choose a competitor with a faster, easier onboarding process.<br>Long processes, not just at the onboarding stage, create frustration, and you will lose users at every step of the onboarding process. Every innocent question or form field — will take away a percentage of your users. It’s 2023, no one has patience, and attention spans are as short as they ever were.</p><h4>Too many choices</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s9a5nd203ZoFvWoufeDlqA.jpeg" /></figure><p>Giving too many choices can overwhelm users and make them feel uncertain about which option is best for them. This can lead to indecision and a delay in completing the onboarding process. Having too many choices can lead to decision paralysis, where users become overwhelmed and unable to make a choice at all. This can result in users abandoning the onboarding process altogether.<br>“Don’t make me think” is my favorite UX mantra. If you are making them think — they will leave!</p><h4>Too complicated</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nnHvb7pMTtXN0U-zsueUSQ.jpeg" /></figure><p>A complex onboarding process can be difficult for users to understand and can lead to confusion and a lack of confidence in using the product.<br>If your onboarding requires high technical abilities, special access (being an administrator), and additional software or plugins —this will also lower the chances for your SaaS. These obstacles can make you lose a large portion of your users.</p><h4>Too easy to leave</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w0EpFRhwrWzI0fCO3ArL6g.jpeg" /></figure><p>It is crucial to keep users engaged in the onboarding process and prevent them from navigating away from it by following links to other pages or tabs. If users are able to easily leave the onboarding wizard, it may result in a higher drop-off rate as they may abandon the process before completing it. Allowing breaks, linking to external pages, or viewing other content during the onboarding process can hinder users’ progress and understanding of the product. If the onboarding process is disrupted, users may not fully comprehend how to use the product, leading to a lack of confidence and lower satisfaction, ultimately resulting in a lower adoption rate.</p><h4>Too strict</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ml2vjMCixPyXZt5GPKGjxQ.jpeg" /></figure><p>A strict onboarding wizard that doesn’t allow users to skip steps or move at their own pace can be frustrating and time-consuming. Such a rigid onboarding process, which requires users to complete all steps in a specific order, or fill out long forms, can lead to antagonism and high drop-off rates. All of these factors contribute to a negative user experience, which can damage the company’s reputation and discourage potential users from trying the product. It is important for SaaS companies to strive for a balance in their onboarding process, allowing users the flexibility to move at their own pace while still guiding them through the necessary steps to effectively learn how to use the product.</p><p>In summary, the wrong kind of SaaS onboarding can lead to user overwhelm, confusion, decision paralysis, and a lower overall conversion rate. And we don’t like low conversion rates.<br>It is essential for companies to strike a balance and offer a manageable number of options during the onboarding process, keeping the users focused and engaged throughout. By creating a positive and enjoyable onboarding experience, SaaS companies can increase adoption and retention and improve their overall success. Onboarding is like wrapping paper, and your product is the gift. Make your SaaS onboarding light, short, and easy to get through.</p><h4>Keep in touch</h4><p>My name is Mark and I’m a freelance Product Designer with over 10 years of experience. I provide UX UI design for startups, hyper-growth companies, and tech entrepreneurs. If you need design work or a consultation <a href="/service/mailto:contact@marklevi.com">contact me via email</a>, or visit my <a href="http://www.marklevi.com/">website</a>, <a href="http://www.instagram.com/marklevidesign">Instagram</a>, or <a href="https://www.linkedin.com/in/marklevi7/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8efd4525fee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Increasing SaaS agent installs by 17% at Komodor.io]]></title>
            <link>https://medium.com/@marklevi/increasing-saas-agent-installs-by-17-at-komodor-io-b4e9f327a362?source=rss-88e3209dbb4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4e9f327a362</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Mark Levinson]]></dc:creator>
            <pubDate>Thu, 29 Sep 2022 12:01:54 GMT</pubDate>
            <atom:updated>2022-09-29T12:01:54.750Z</atom:updated>
            <content:encoded><![CDATA[<h4>I was part of the team that improved agent install rate by developing a sandbox environment, adding more screens to the sign-up flow, UX witing, product design, and magic.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7iD81_OLkeTC81SkRtra3w.jpeg" /></figure><h4>Introduction</h4><p>Most modern apps live in the cloud, and are divided into many small pieces. Komodor is a tool that tracks changes in these pieces and helps find and solve problems caused by those changes. Komodor saves developers many hours of work, but it requires an installation. There was an ongoing attempt in the company to switch from a manual installation with a sales representative support to self-served installation.</p><h4>What was wrong</h4><p>The users hesitated too much about installing our agent (they still do). After the first week of rolling out Komodors’ self-serve installation, we discovered a significant drop-off in Komodors’ onboarding process, up to 88% of users did not do what we wanted them to do–install the agent on their system. Agent install is a developer-only territory, requiring familiarity with Helm environment and commands (That black screen with code all developers seem to fancy so much). So a big technological barrier here. The solution was split into 3 parts.</p><h3>1. Sandbox development</h3><h4>What was the problem?</h4><p>Komodor is complex, it’s a tool that requires the level of knowledge and familiarity of a mid-level developer. Komodors’ sign-up mandates a helm command install of an agent, and no one likes to install things on their system including skilled developers. When a developer sees a requirement to install something, they hesitate. The install helm command may interfere with their servers, system, and god knows what else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B4ISOM-NdEaUbTyK_Tv78g.png" /><figcaption>A long helm command needs to be pasted into Terminal (black screen) just to see Komodor in action</figcaption></figure><h4>What we did</h4><p>We implemented a sandbox environment that allowed to “play” with Komodor without installing anything. So we removed the psychological barrier of installation by showing the product in its full functionality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9IAK-k_6acDSChcSy5NB_A.png" /><figcaption>Komodors’ sandbox is just like the real product with demo data</figcaption></figure><h4>How it improved the situation</h4><p>It’s pure psychology: a test drive in a car convinces a potential buyer to purchase much better than just looking at that car from the outside! It’s much easier to arrive at a decision to install an agent after getting to feel the product, to give it a test drive. The sandbox allowed the hesitant user to give Komodor a test drive, after which they were better convinced to install.</p><h3><strong>2. Agent install modal</strong></h3><h4>What was the problem?</h4><p>The install modal was overcrowded with too many texts of different sizes and colors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lxl_PliqXwzeIFP38boh0A.png" /><figcaption>Install Cluster modal, before upgrade</figcaption></figure><h4>What we did</h4><p>Simplified the texts, and added some reminders that the agent is read-only. I basically removed everything I could from there…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a2r2_zobJ5Hi9PNZNfxX_Q.png" /><figcaption>Install Cluster modal, after my redesign. This version was not used eventually, but it’s my personal favorite</figcaption></figure><h4>How it improved the situation</h4><p>Even developers prefer to <a href="https://medium.com/@marklevi/write-less-ade5108fee">read less</a>, so by giving them less text to read we improved the conversion at this step. Also, if you know that the agent is read-only, meaning it’s non-destructive, it makes you feel safer about installing it. Design-wise I minimized the number of text styles and types of CTAs.</p><h3>3. An extra screen in the sign-up process brought the conversion up!</h3><p>The availability of a test-drive version was not evident enough, so we added an extra screen to the sign-up with a choice. It’s completely counterintuitive for any UX designer to add steps to the sign-up. All designers know — the fewer clicks to achieve a job the better. But, we took the shot and we won! The illustrations alone for this step took me a few days, I tested the balance between the illustrations, buttons, and texts. It looks like a simple screen, and it is, but it’s a turning point in the flow of signing up a user and its role in our mission’s success is very high.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8h0_ARiPjtLRZviTRZRNAw.png" /><figcaption>The extra screen added to the sign-up process</figcaption></figure><h3>Bringing it all together</h3><p>So to loop it all together I added a sandbox call to action to the website, install CTA to the sandbox, and an extra step at the sign-up process to allow a test drive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GCrhoK-xR1J14KGAsIEz3Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pYKno77LFEk57DV9jYdieQ.png" /><figcaption>Sign-up user flow before and after sandbox implementation</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tzomTXjOoqmMA5hjwK-4wQ.png" /><figcaption>Install CTA in the sandbox</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cERVCYEN1mVFQM4vFvzc9A.png" /><figcaption>Website sandbox cta</figcaption></figure><h3>Summary</h3><p>It never ceases to amaze me how product and UX upgrades can help grow business success. We are looking at a 17% improvement in just 2 weeks since launch! While each step described here is crucial, combining them together was as important. The flows are now interconnected, allowing for a lot of flexibility while keeping the eyes on the prize–agent install. We are promoting agent installs by showing a product demo (sandbox), showing the value and giving a glimpse of what will be possible if you do decide to install.</p><h4>Project credits</h4><p>UX/UI Designer: <a href="http://www.marklevi.com/"><strong>Mark Levinson</strong></a> (that’s me)<br>Product manager: <strong>Ben Rosenfeld</strong><br>Art director: <strong>Roy Weinberg</strong></p><h4>Keep in touch</h4><p>If you liked this article you can always <a href="/service/mailto:marklevi7@gmail.com">drop me a line</a>, visit my <a href="http://www.marklevi.com/">website</a>, or my <a href="http://www.instagram.com/marklevidesign">Instagram</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4e9f327a362" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Commenting on design. How to write constructive design comments.]]></title>
            <link>https://medium.com/@marklevi/commenting-on-design-how-to-write-constructive-design-comments-c40b38ae70e4?source=rss-88e3209dbb4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c40b38ae70e4</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[comment]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Mark Levinson]]></dc:creator>
            <pubDate>Sun, 19 Sep 2021 09:24:33 GMT</pubDate>
            <atom:updated>2021-09-19T09:24:33.569Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9aqkumoqzgyT3El9mvPJcA.png" /></figure><p>While working on a piece of graphic design–website, app, or any other piece, the designer and the client will need to communicate through text at some point in time, discussing little graphic details and correcting copy. This written communication can be a great tool to advance a design project, or it can be a source of frustration.</p><p>Most changes and iterations in a piece of design are small: design corrections or text changes. It is best to use a visual tool for this kind of work — Invision, Zeplin, Figma, or adding comments to a PDF. The main goal in such bit-by-bit communication is to be as precise as possible, to avoid misunderstandings, frustration, and to minimize the number of iterations. What you, as a client, want is to fix each issue in one sitting. Your designer wants this too.</p><p>Trust me, nobody wants to deliberate over button shadows or text size more than needed. We are here to make things happen, to move things forward. This is why what you write in that little comment is so important.</p><p>Here are some examples of good and bad versions of design comments:</p><p><strong>Bad: </strong>Capitalize this text<strong>.</strong></p><p><strong>Good</strong>: Change to “See How You Can Improve”.</p><p><strong>Why</strong>: If you ask to capitalize a piece of text, there are three variations of what you could get three variants:<br>1. SEE HOW YOU CAN IMPROVE<br>2. See how you can improve<br>3. See How You Can Improve<br>If you want a specific variation, type it in full.</p><p><strong>Bad</strong>: Make it the same as in the previous slide.</p><p><strong>Good</strong>: Copy style from here: <a href="http://www.link.com/new">www.link.com/new</a></p><p><strong>Why</strong>: Since the slide order can change, it is better to link directly to the reference. What you mean by the word “same” is only obvious to you.</p><p><strong>Bad</strong>: Change to the other color.</p><p><strong>Good</strong>: Change to green.</p><p><strong>Why</strong>: what you think of as “the other color” may differ from what a designer thinks. To avoid confusion, use a precise color name, or hex code #54FFE5 (Pro tip: designers love hex codes).</p><p><strong>Bad:</strong> Make this button the same size as the other screen.</p><p><strong>Good:</strong> Make this button the same size as here: <a href="http://www.link.com/new2">www.link.com/new2</a></p><p><strong>Why:</strong> Designers hop from screen to screen when going through your design comments. What you mean by “other screen” is only obvious to you. Do attach a link to your reference, or a screenshot.</p><p><strong>Bad:</strong> Wrong color! I told you about this before, read the previous comments!</p><p><strong>Good:</strong> Change to green.</p><p><strong>Why:</strong> Human error is common. Forgive your designer and just ask again for the same thing in the same tone and wording. Getting emotional in the comments is counter-productive.<br><strong>Pro tip:</strong> if you feel that you are misunderstood more than once–call.</p><p><strong>Bad</strong>: Copy new text from the doc.</p><p><strong>Good</strong>: Change to: ”Buy at your local store”</p><p><strong>Why</strong>: When addressing a single text correction, do the extra work and copy-paste the full sentence. Instead of directing the designer to a document and making him/her look for the correct copy, just paste the desired copy inside the comment. This way, you minimize potential mistakes and iterations. Note that when you do have a document with many fields of text, and they all need to be changed, it is OK to ask to copy-paste all of them in one comment.</p><h3>Emojis, stickers, reactions</h3><p>Emojis are a great way to add emotion and fun to communication inside the project. I use them all the time and encourage my clients to do it too. It’s much easier to express fun, acceptance, or frustration with a smiley face than in plain text. I have not yet seen an overuse or a misuse of emojis, stickers, or reactions in a professional environment. Prove me wrong?</p><h3>In conclusion</h3><p>Here is a round-up of everything above:</p><ul><li>Use copy-pastable content.</li><li>Link directly to your reference.</li><li>Use visual aids, links, arrows, screenshots when possible.</li><li>Precision, precision, and more precision.</li><li>Use emoji to vent and express emotion.</li><li>If you feel misunderstood more than once — call.</li></ul><p>The use of textual communication is growing in product teams, and we use text all the time, so let’s do our best and keep it classy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c40b38ae70e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zorgtech CMMS Software Redesign]]></title>
            <link>https://medium.com/@marklevi/zorgtech-cmms-software-redesign-bf34c5fa1143?source=rss-88e3209dbb4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf34c5fa1143</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Mark Levinson]]></dc:creator>
            <pubDate>Tue, 11 Sep 2018 15:07:50 GMT</pubDate>
            <atom:updated>2018-12-30T08:06:00.735Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h5kQYe-FpClyvsAK.png" /></figure><p>It turns out low-tech industries, factories, workshops, etc use software too! They all undergo a change called “industry 4.0” and as the name suggests — they employ software as part of their reorganisation and tendency for effectiveness.</p><p>Zorgtech has been making tailored software according to demand. Having connections in the industrial world they managed to collect some clients and created software specifically for their needs. It was a tailor made solution that had to fit the specific processes in a production line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/0*_w5xdodYcucM4SNr.png" /><figcaption>GANNT style chart of a plastic mold production facility</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/0*Rq9T-Ic-tFDQr9zD.png" /><figcaption>Device card of an HP Indigo printers factory</figcaption></figure><h3>What was the problem</h3><p>New clients were hard to get. The software looked poor. It was designed by developers, and potential users had a hard time with it (most workers on factories are non-tech guys).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W_DDGJ_EpNrFlq7I.png" /><figcaption>Old zorgtech software</figcaption></figure><p>Non-tech guys don’t like to learn, don’t like to work with a screen, and don’t like to do extra tasks like filling forms and clicking buttons. A cumbersome computer system was a poor match for an analog paperwork reports they had to fill on the production floor (many times skipping it altogether). It was easier for them to keep working with paper reports, same went for their managers and factory owners and CEOs.</p><p>That, of course, affected the effectiveness and the ability to analyze the production in order to optimize it. They needed a software, but a much simpler one. So the task was to give it to them.</p><h3>Challenge accepted</h3><p>Another challenge was the conditions in which the software development and integration has been done. There was no funding. There was no time for looking at the big picture, and there was a need to give solutions to the existing clients and new ones. Every client was different, their production line worked in a different manner and the fields themselves were various — from <a href="http://deltatech.co.il/">Hewlett Packard printers maintenance</a> to a <a href="https://www.facebook.com/UgiyaBakery/">boutique cookie factory</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/0*NFNR3RpVhoLI9B5o.png" /><figcaption>Dashboard for Indigo printers assembly rooms</figcaption></figure><p>During design, I had to understand each factory processes, terminology and structure to give the UX UI solution they needed. I always emphasise and insist on such a <a href="https://marklevi.com/know-your-subject/">deep dive into the matter</a>.</p><p>Luckily, I had a front man — Vladimir, a manager and engineer with vast experience in the industrial field, who would “take me by the hand”, so to speak, and explain to me, with patience, about each factory, their products, the kind of workers, the kind of tasks and the results of their work in real life and inside of the software.</p><h3>Design Process</h3><p>At first, we focused on few clients and their main production floor. Then on a single screen that a worker would interact with. So the main screens were for the management and the “working screens” — for workers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*_ORBqrO102YkheGWz53HKw.png" /><figcaption>Wireframes and sketches for one of the clients</figcaption></figure><p>Then I went through a usual UX process of figuring out users, creating personas, mapping their needs and motivation, understanding the setup in the factory and the interaction between the units and departments.</p><p>After this we started implementing existing pre-set screens onto different clients’ projects with tweaks. This allowed the design to stay lean and development was fast because the starting point solved most of the issues.</p><h3>How we invented a super-scrum process.</h3><p>Product design, or UX UI design, both presume an integration between the designer, developers and clients, spanning across weeks (agile and scrum). The client feedback loop is built into the design process. But in our case we had to improvise in a different manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*QUJzfb6puqahYNJj.gif" /><figcaption>Hovering art director — every designers’ nightmare</figcaption></figure><p>Vladimir would study the field, and we designed during short online meetings, with screen sharing sessions via <a href="http://www.teamviewer.com/">TeamViewer</a>. That was the only way to present feasible results with a very tight budget and timeframe. It was not easy for me, but it worked. Integration of two minds, working simultaneously on a single task produced the design that satisfied the clients without keeping them in the loop in the short term. Their feedback took weeks, but our development took few hours each time!</p><h3>How design effected sales</h3><p>Sales became easier. New clients would agree to give it a try after only taking a look at a couple of screens. That never happened before with an old design. Vladimir got several new clients and we had more breathing space for keeping the design and finessing the details.</p><p>That was a total win! I was so pleased hearing about each new sale as if I made it myself.</p><p>Every product needs marketing. So a marketing kit was created with everything that was required — business cards, website, flyers, presentations etc. It’s not exactly product design but it sells the product.</p><h3>Next steps for Zorgtech.</h3><p>Next steps for Vladimir and his team, including myself, is to upgrade the technology of the software. Web based solution will probably be our choice.</p><p>The redesign works. It has been proven multiple times and we both are very pleased, so are the users. Now, it’s time for optimisation.</p><p><em>Originally published at </em><a href="https://marklevi.com/zorgtech-software-redesign/"><em>marklevi.com</em></a><em> on September 11, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf34c5fa1143" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Write less.]]></title>
            <link>https://medium.com/@marklevi/write-less-ade5108fee?source=rss-88e3209dbb4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ade5108fee</guid>
            <category><![CDATA[copywriting]]></category>
            <category><![CDATA[text]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Mark Levinson]]></dc:creator>
            <pubDate>Mon, 27 Nov 2017 15:28:36 GMT</pubDate>
            <atom:updated>2017-11-27T15:30:23.637Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MTevzTgziRK6q_Ko.jpg" /><figcaption>Best text is no text</figcaption></figure><p>Internet users today are overwhelmed with different kinds of information. This is why keeping your copywriting short and clear, is an important part of modern graphic and product design. Long chapters will repulse your readers or website visitors. Too much text can become a block between a website visitor and buyer, between a TL;DR by-passer and a loyal user.</p><p>Internet users are overwhelmed with information. This is why short, precise texts are a good way to keep your users focused.</p><p>Internet users don’t read. Write shorter texts.</p><p>Write less.</p><p><em>Originally published at </em><a href="https://marklevi.com/write-less/"><em>marklevi.com</em></a><em> on November 27, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ade5108fee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Application overdose]]></title>
            <link>https://medium.com/@marklevi/application-overdose-177863728fd1?source=rss-88e3209dbb4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/177863728fd1</guid>
            <category><![CDATA[andoid]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[iphone]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Mark Levinson]]></dc:creator>
            <pubDate>Wed, 02 Aug 2017 21:04:39 GMT</pubDate>
            <atom:updated>2017-08-02T21:08:46.659Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/829/1*D5eyuWdszb9Ba1iJGbL5IA.jpeg" /><figcaption>There is just too many apps</figcaption></figure><p>Is it just me, or are there too many apps on my phone?</p><p>Is it just me, or that every service I use has an app and pushes me to install it and use it.</p><p>Is it just me, or my attention is filled with notifications from multiple sources and I cannot differentiate between the important one’s and entertainment that can wait for later.</p><p>Is it just me or Apps have become the plague of the mobile age.</p><p>There is too many for my little (or not so little brain). There even was a study about how our brain remembers the location of items on a virtual screen as a physical location. Well this means that my iPhone is a huge medieval castle, so full of rooms and halls that even the help finds it hard to navigate. And as a king of this “castle” I want to take control back. So what do I do? Folders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/0*DbZqzCZxfsRJ5HTh.png" /><figcaption>Folders as an organization attempt</figcaption></figure><p>Now my iPhone is a stack of folders, the amount of “halls” in my pocket size virtual castle gets smaller, but now I have to think every time what folder to open, and spend my time opening and closing them in order to find what I’m looking for. The architect of my new castle gets fired and I move on to the next idea: color coding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qlnqdu8bv3z3MwWz.jpg" /><figcaption>Color coding icons just creates more mess</figcaption></figure><p>This looks really pretty. The new “castle architect” is a painter that loves order and when I look at my new screen order I smile because it’s so well arranged. I know by heart that Dropbox and facebook are blue in color so I will know where to navigate each time I need something. But wait. What color is <a href="https://www.spotify.com/">Spotify</a>? Green or black? When it comes to apps that are not so often used — I find myself browsing through all the colorful screens cursing my new “architect” and soon he it dismissed.</p><p>Putting the most used apps in the first desktop screen, the less used in the next and so on also does not quite work when the amount exceeds 3 screens.</p><p>I am frustrated. The king is not pleased.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*ocxeJWZz-4tGOlPZ.gif" /></figure><p>Back in the day I interviewed to a nifty startup that was called <a href="https://www.crunchbase.com/organization/everythingme#/entity">everything.me</a>. It seems like they are now <a href="http://tech.eu/brief/israeli-startup-everythingme-shuts-down/">shut down</a>. Everything.me was supposed to solve the app overdose problem by creating an Android launched with apps as a service; Now there is a new rise of startups dealing with “app as a service” trend. This means the apps are not individually installed on a device but rather appear when needed / searched or adressed in another way. This seems cool to me, but there is a way to go until this happens. In the meanwhile I’ll sleep in a tent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=177863728fd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX UI design for startups in real life]]></title>
            <link>https://medium.com/@marklevi/https-medium-com-marklevi-ux-ui-design-for-startups-in-real-life-910ad0bf366e?source=rss-88e3209dbb4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/910ad0bf366e</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Mark Levinson]]></dc:creator>
            <pubDate>Fri, 09 Jun 2017 16:44:22 GMT</pubDate>
            <atom:updated>2017-11-17T08:01:01.340Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*csTyF8yeXoY_M979.jpeg" /></figure><p>Coming from an art <a href="http://www.bezalel.ac.il/en/">and design academy</a> I was very eager and naive about design processes in general. Working at design agencies shattered my academic perception of the <a href="http://designers.hubspot.com/blog/graphic-designer-design-process-tips">design process</a>. After a few years in different design agencies, when I switched to startups and digital product design (aka UX UI) I’ve noticed, again, that I have to adjust. It’s completely the opposite of what I was taught in the arts academy. It also differed tremendously from design and advertising agency approach to things. It was a bit crazy, very interesting and constantly changing. It was really hard to digest, agree with and implement at first, but getting to know the people and the goals behind every decision helped me adjust, my <a href="http://www.hongkiat.com/blog/designers-ego/">designer-ego</a> was tamed and I now feel competent to write about this, so here goes.</p><h3>Startups vs agencies</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XvhkLpHD0xXXeAZzWaBhlw.jpeg" /></figure><p>In a design agency, the product is design itself. In an advertising agency the product is the marketing message with a design “sauce” all over it. This is great and very clear to those coming to an agency to become a better designer or art-director. However, in startups this is different. Here design is not a “sauce” anymore. It’s a mandatory and integral part of the product. The product (app, website, e-shop or web-interface) need to appeal, it needs to get the user’s attention and solve their problems. That’s why it’s crucial to have design integrated in decision making, including strategic and tactical development of the product. As a designer you should attend management-level meetings that have to do with project goals, development, marketing strategy, audience etc. If you see that the next planned feature will not add to the overall experience — you should point it out. If you think that a feature next in line is TL;DR or not interesting to the user or just plain boring — speak up.</p><h3>Working in a lean/agile environment in a startup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N8L4193et75tNxxqS0koJQ.png" /></figure><p>Most startups today, big and small, tend to work according to one of the methods — agile or lean process of development.</p><p>These allow fast delivery of a product upgrades and testing in real life what works and what does not. As a designer you will be the first to know of the coming features and the first to make appropriate design changes. Usually the rush and craziness of scrum and two-week sprints of development don’t affect the designers, but sometimes they do, so be prepared to stay extra hours sometimes. This is what a startup is all about — making fast movements in a fast-paced market.</p><h3>Working in a monetizing startup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UGYrty3qagJPDRt_c3P5xA.png" /></figure><p>At one point or another a startup decides it’s time to monetize. When this happens — priorities start to change from the head (CEO and stakeholders) down to focus on BI, metrics, advertisement, optimization etc. All tasks go through “will this bring in cash?” filters.</p><p>When a designer is summoned to solve <a href="http://marklevi.com/project/90min-com/">monetization tasks</a> — always do involve a marketing specialist and don’t try to take it all on yourself. You are not a marketing specialist (unless you are, then ask for a double salary), and marketing decisions cannot be your sole responsibility.<br> <br> Tasks in a monetizing startup become more repetitive and changes more subtle, up to a point when it seems like everything is about money and not users, which made me personally feel uncomfortable.<br> <br> With others this period may be a time to chill, recharge and focus on productivity and technique.</p><h3>Delivering faster</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*41UPuImXAzMZhk0wsgHElw.jpeg" /></figure><p>All startups are different, and each one strikes as a completely different challenge. But most of them do feel like a race.</p><p>As much as I love to do the classic design process for a product–it almost never happens. Usually the client appears with half-done design. Sometimes they come after a really bad experience with another designer. Sometimes they did the whole design DIY for a year or so and it looks like a disaster. Many times the client has no idea what the difference is between UX and UI. The list goes on, but the message is–don’t expect perfect because there is no such thing in this field. Expect interesting stories and business ideas. Expect ground-breaking technologies. Expect big missions like making smart cities or solar power plants.<br> <br> As a freelancer and an employee in a startup I always arrived at different points of the product cycle. Sometimes there where wireframes ready. Sometimes the brand was in the middle of a redesign process when the previous designer suddenly left. Many times there already was a working prototype or live product which I was asked to “make look good”. As I said before, most tech people do not distinguish between UX and UI and tend to mix them together when discussing or requesting a design solution. So a good designer listens, figures out what the person describing the problem actually means to convey and then uses the needed tools to solve the problem. Do not try to focus and adhere to the classic “design thinking” model, it does not work in the real world of high-tech, instead focus on one task at a time, make sure you do see the whole picture and try to get results fast mostly relying on your gut feelings.</p><ul><li>When a new widget or another small improvement is requited it’s OK sometimes to skip wireframes. Its is a great idea to whiteboard wireframes during a feature discussion, then take a photo of the board and work from that as a guideline to a final design.</li><li>Use pre-made icons from different icon-sets, stock images, templates and anything else that can shorten your delivery time. You can finesse the details later when the design is approved, and even some parts can be changed in the middle of development.</li><li>Use the “style you like” queston when you are not sure about clients’ preferences and don’t have time or budget for multiple design sketches.</li><li>Good artists copy, great artists steal. Using solutions from someone else’s design work is OK as long as it’s not a total rip-off</li><li>When a design does not translate well to development and looks off–sit down next to the developer and explain in words what you meant to happen on screen. Personal communication solves problems way faster in this case.</li></ul><p>Where is that fine line between rip-off and inspiration–everyone should decide for themselves.</p><h3>Leading the way</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DGYWhLiGlUvXprJ8hBGj7g.jpeg" /></figure><p>Many may not know it, or agree, but design actually defines the product and dictates what the development should or should not do.</p><p>This does not mean you get to boss people around. This means you need to develop communication skills and persuasion to be able to talk people into what you want, why, and how it will benefit the company goals.<br> <br> Developers and designers alike are rather lazy people, so you will hear a lot of “but it will take me a long time to implement” or “can we not do it, I already have a ready solution for it and it works just fine”. See, developers think in terms of “working vs not working”. They are engineers by their nature, and it’s a good thing when the product works. But, there is a but. If a product works but is uncomfortable for the user — it will not be used. It will not get popular, it will be neglected, the firm will lose clients, money and investments. Plain and simple. So the designer in a startup is an ambassador of good design, usability and the voice of the user in general. It’s OK to go against management about this too — just do it tastefully and rationally explain your decisions and concerns. Emphasize the user-friendly, user-centered and conversion/audience gains that your suggestion will bring, and management will listen.</p><h3>Summarizing</h3><p>Working with startups is a unique experience that can take time to get used to. The environment is dynamic, the deadlines are tight and sometimes is seems like no one is listening to you. Having said that–there is nothing like being part of something new and groundbreaking, feeling the passion and the desire to make it in the world, absorbing the fighter spirit and sometimes dealing with spartan conditions. The lessons learned from a startup world cannot be learned from anywhere else, and this definitely is a worthy ride. Keep cool, develop good communication, always try to attend as many meetings as possible to understand the strategy and goals better and you will be just fine!</p><p><em>Originally published at </em><a href="http://marklevi.com/ux-ui-startups/"><em>marklevi.com</em></a><em> on June 9, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=910ad0bf366e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Illustrator to a web font. Creating custom scalable web-icons]]></title>
            <link>https://medium.com/@marklevi/from-illustrator-to-a-web-font-creating-custom-scalable-web-icons-mark-levi-design-1c47a536e434?source=rss-88e3209dbb4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c47a536e434</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[icons]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Mark Levinson]]></dc:creator>
            <pubDate>Sun, 17 Nov 2013 13:35:55 GMT</pubDate>
            <atom:updated>2017-11-27T15:44:57.249Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Rq9FXfe4Jx5n5SAzxfOCGg.png" /><figcaption>Editable web icon</figcaption></figure><p><strong>State of affairs: </strong>We want to make a switch to an icon font, and replace the .PNG sprites. Trying to achieve that with minimum effort and if possible no additional software we searched for a web-app to help us.</p><h4>Research:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*2ErJoVtfsIMyxSFY08gj_g.png" /></figure><p>There is a ton of software and free or demo apps that can help you get your way and add some nice pre-designed vector icons to your project (like <a href="http://fontawesome.io/icons/">fontawesome</a>). However being a perfectionist using pre-designed icons did not satisfy me. What I wanted is a way to translate the exact vector icons I developed in illustrator and photoshop into a web-font and that seemed to be impossible without an expensive font-editing software.</p><h4>Solution:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*TGLcTfTQSOH48gYDDI73Rg.png" /></figure><p>And then we found <a href="http://icomoon.io/app">icomoon app</a>. This baby can take custom .SVG files, combine them with pre-designed icons from several extensive libraries and export them into a custom web-font. Then the session can be stored and donloaded as a .JSON file, making it possible to edit in the future. All free, no strings attached. This is perfect!</p><p>(Note, the font-export button is at the bottom)</p><h4>This is how we do it now:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*giFbyxfHFcqdSOFE_S_8gg.png" /></figure><p>Now I open a sheet in illustrator, exporting every icon to a separate .SVG file, and importing them in <a href="http://icomoon.io/app">icomoon</a>.</p><p>Front-end dev’s call every icon by it’s code like so:</p><p>&lt;a class=”prev ficon icon-arrow-left”&gt;&lt;/a&gt;</p><p>And voila, now we have scaleable and custom icons all over the website, easily scalable to fit mobile, tablet and desktop view.</p><p>Check them all out here: <a href="http://www.ftbpro.com/">www.ftbpro.com</a></p><p><em>Originally published at </em><a href="http://marklevi.com/from-illustrator-to-a-web-font-creating-custom-scalable-web-icons/"><em>marklevi.com</em></a><em> on November 17, 2013.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c47a536e434" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>