<?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 Milan Vrekic on Medium]]></title>
        <description><![CDATA[Stories by Milan Vrekic on Medium]]></description>
        <link>https://medium.com/@milanvrekic?source=rss-e220df1cd88a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JIW4EgB67Ut8PHUGTHvNwQ.jpeg</url>
            <title>Stories by Milan Vrekic on Medium</title>
            <link>https://medium.com/@milanvrekic?source=rss-e220df1cd88a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:11:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@milanvrekic/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[Why you should love Rapid prototyping]]></title>
            <link>https://medium.com/milanvrekic/why-you-should-love-rapid-prototyping-3b1a27ac86cc?source=rss-e220df1cd88a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b1a27ac86cc</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[rapid-prototyping]]></category>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Milan Vrekic]]></dc:creator>
            <pubDate>Tue, 04 Jul 2017 00:14:06 GMT</pubDate>
            <atom:updated>2017-07-04T00:44:37.908Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UzPpNV5qSRzBzQMnR0iiZQ.jpeg" /></figure><p>Years ago, standard process for developing a product from the design perspective was to create: first, several low fidelity wire-frames; second, one high fidelity wire-frame; third, mockups and design specs after the mock-up sign-offs.</p><p>This worked well since the stakeholders could understand how the site would function without having to waste money building it first.</p><p>Now fast forward to today. Desktop Software is dying, websites are responsive, and mobile apps rule the day.</p><p><em>In 2017 Interaction design is the goal, and rapid prototyping is the way.</em></p><p>At TitanFile, back in 2011, we switched from traditional design process to rapid prototyping, and, consequently we gained about a 20% increase in productivity and deployment speed. We kept rapid prototyping with Zora and advocated it to the most of the Volta companies.</p><p>In the lines bellow I will try to outline the biggest benefits with rapid prototyping as a software development approach.</p><p><strong>Isn’t making a prototype a waste of time and money?</strong></p><p>Making a functional prototype used to take a lot of time. Not any more. Thanks to asset libraries, UI patterns and standardized interface elements you can put together a hi-fi mock-up with Photoshop or Sketch quickly and then make it interactive with tools such as inVision or libraries such as React.</p><p><strong>How does it work for designers?</strong></p><p>Wire-frames discourage designers from working with developers. The advantage of rapid prototyping is that designers often sit next to developers and literally work with them to change the design ad-hoc and see how their design behaves once it’s turned into code.</p><p>Once designers start to collaborate with developers, they will understand what’s possible with the front/back end that they’re using and they will be able to fully flesh out a thorough user experience. Designers definitely do not need to know how to code but they should know the lingo as this is called “Human-Computer Interaction” after all.</p><p><strong>How does it work for developers?</strong></p><p>Creating, documenting and annotating designs take a lot of work. Once that work is done it is very easy for designers to throw the SPEC over the fence to the developers, hang a big “mission accomplished” banner and move on to the next task.</p><p>With rapid prototyping, design specs are created ad-hoc as the prototype evolves. This ensures that design SPEC is a living document that always reflects up-to-date information and reduces the number of design kickbacks that developers have to fix later. If you are truly adventurous, you can use tools such as Axure which will automatically generate design specification for you.</p><p>By having designers work directly with developers we avoid scenarios such as when, if we have 10 hours to do something, we discover that something what “looks nice” will take 5 hours to do because there is a disconnect between design and developers.</p><p>Developers in sync with design; they work alongside in harmony, not one after another.</p><p><strong>How does it work for business?</strong></p><p>It is a lot easier to get actionable feedback from stakeholders once a device is in their hands and they can see exactly how the feature will look and work “in action” as opposed to on a computer screen.</p><p>Simply put: rapid prototyping communicates form and function better. Since wire-frames are static by nature, it is impossible to do any meaningful usability testing. Prototyping puts only the device screen glass between you and your users/stakeholders.</p><p><strong>How does it work for product?</strong></p><p>In the case of product management, users have trouble weighing the desirability of some theorized product with the feasibility of actually using the product. This is a result of a Psychological distance phenomena and it’s caused by human brain’s inability to predict how it will react in circumstances removed from the circumstances it is currently in.</p><p>In one of the Georgetown University experiments, users were presented with the wireframe concepts of two different alarm clocks: one simple clock with the alarm being its only feature, the other — more complex with features like reading the weather and traffic patterns to the user, among a dozen other features. Most people picked the product with the most features. However, when those products were actually produced and sold, almost all of the people in the study picked the simpler product. From a distance users prefer desirability, but up close prefer feasibility.</p><p>Rapid prototyping provides a shortcut to establishing what is feasible and how strong is the “Fingerspitzengefühl”.</p><p>The German word “Fingerspitzengefühl” is almost impossible to translate 100% to English. The closest translation to English would be “that fingertip feeling”; it’s a quality you cannot precisely express, but which you know is there.</p><p>Rapid prototyping allows you to feel how a user would feel before you go too deep down the development rabbit hole.</p><p><strong>How much should you prototype?</strong></p><p>Simply put — You should prototype 20% of the feature where users will find 80% of the value.</p><p>If your job is to prototype a new search screen, focusing on nailing the interaction with and clarity of the search fields is a lot more valuable than tweaking the layout of the results.</p><p>You do not prototype everything at once.</p><p>Wire-frame approach de-risks the process by honing in on the winning design in passes (low-fi, hi-fi, mockups). Rapid prototyping reduces the risk by breaking down the process into steps: most valuable (and most risky) elements are prototyped first and supporting elements (such as CTA’s and entry/exit points) last.</p><p>In closing, I would like to leave one big caveat — make sure to communicate that prototypes are not finished features but merely one of many directions a feature can take. Sometimes this is achieved by just presenting multiple “lower effort” prototypes alongside the main candidate.</p><p>Stakeholders that understand this will not sidetrack the discussion by talking about colors or font sizes used, but appreciate the benefits rapid prototyping brings to reaching clarity faster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b1a27ac86cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/milanvrekic/why-you-should-love-rapid-prototyping-3b1a27ac86cc">Why you should love Rapid prototyping</a> was originally published in <a href="https://medium.com/milanvrekic">C:/Milan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to avoid boring people with sales demos]]></title>
            <link>https://medium.com/milanvrekic/how-to-do-sales-demos-19d5bdb12977?source=rss-e220df1cd88a------2</link>
            <guid isPermaLink="false">https://medium.com/p/19d5bdb12977</guid>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[demo]]></category>
            <dc:creator><![CDATA[Milan Vrekic]]></dc:creator>
            <pubDate>Fri, 11 Oct 2013 00:11:17 GMT</pubDate>
            <atom:updated>2017-04-24T15:49:06.666Z</atom:updated>
            <content:encoded><![CDATA[<p>Your demo should boil down to one of the following four propositions:</p><p>- <em>Cheaper</em><br>- <em>Better</em><br>- <em>Faster</em><br>- <em>Could not be done before!</em></p><p>At the end of sales presentation do not forget to ask something to effect “is there anything I should be asking that I did not ask?”<br>The answer will usually clearly define if you have hit the pain point with them or not.</p><p>For each sales demo clearly define:</p><p><em>Meeting Location</em></p><p><em>Meeting date</em></p><p><em>Start and end times</em> (so people know how much time to budget, often sales demos are canceled as prospective clients think they would take too long)</p><p><em>Meeting objective</em> (Is your target to get a pilot deployment, purchase Order…)</p><p>Ask your internal champion to provide you with real problems organization has, prior to meeting. You should then use <strong>those</strong> problems to illustrate a solution in your demo.</p><p>If you will be giving promo material or printouts — do it at the end of the demo, so they don’t jump ahead of you and make assumptions.</p><p>As a rule of thumb, you will be interrupted during the demo with questions.</p><p>Great questions you should answer right away, good questions you should answer later and stupid questions you should still answer (you don’t want to insult a potential client) but answer them at the end. You can say something like “That is a valid point, I will talk more about that at the end of the demo”</p><p>How do you know a great question you ask? Great question is a question that leads into next slide or into the next few slides.</p><p>If you are demoing at a trade show, develop several “60 second” demos that you can present to prospects based on their specific needs.</p><p>Good luck demoing!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*tx2FJdzi5h2fYGszT5f93g.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19d5bdb12977" width="1" height="1" alt=""><hr><p><a href="https://medium.com/milanvrekic/how-to-do-sales-demos-19d5bdb12977">How to avoid boring people with sales demos</a> was originally published in <a href="https://medium.com/milanvrekic">C:/Milan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Few notes on the Freemium business model]]></title>
            <link>https://medium.com/milanvrekic/few-notes-on-the-freemium-business-model-dfdcb1666c58?source=rss-e220df1cd88a------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfdcb1666c58</guid>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[freemium]]></category>
            <dc:creator><![CDATA[Milan Vrekic]]></dc:creator>
            <pubDate>Mon, 07 Oct 2013 19:24:33 GMT</pubDate>
            <atom:updated>2017-04-24T14:25:59.355Z</atom:updated>
            <content:encoded><![CDATA[<h3>A few notes on the Freemium business model</h3><p>Freemium is sexy and easy. When I say sexy, I mean that most of the recent BIG funding came for the companies doing freemium (look at Hootsuite for example) and when I say easy I mean that it is way to easy for founders not to think too much about their pricing and cost structure and just declare that they will do freemium instead.</p><p>There are some clear Pros for the Freemium: Press loves it, it is easy to get early adopters, you get to leverage passive advertising, and you build brand power A LOT faster than in the licensing model. However, that comes at a cost. That cost is a smaller paying user base, higher support costs (all those free users will all the time on their hands will be the major drag on support), free ones rarely convert (3% is considered a better rate in the industry) and you can hurt your positioning.</p><p>Before you commit to freemium, you should think and answer the following questions:</p><p>How can you monetize “free” users if they never convert into paying customers?</p><p>Can “free” users somehow benefit your paying customers? (example of this is linkedIn, paid profiles would be useless without all those millions of free accounts to look at)</p><p>Can you gain actionable market intelligence from “free” users?</p><p>Can you benefit from a “nothing attracts a crowd like a crowd” notion of a large user base? (this often is an asset if the play from the get go is an acquisition by a 3rd party and not revenue)</p><p>What is an average cost of a “free” user on an annual basis? You noticed by this point that I never wrote free. just “free” as only thing that is free is cheese in the mousetrap.</p><p>You should play with the model a bit and see what works the best. For example, you could give everyone 30 days of all-access on all features, then once they get used to the good stuff, kick them down to the lower plan and sell them on the value add features on a per-feature basis. This would dis-incentivise (did I spell that correctly?) people to signup for the free plan in the first place.</p><p>In B2B play, it is more about the time required to setup and learn the product, than money the customer would save with freemium. Free in B2B is often perceived as having zero value. A startup offering a “free” version of the product that their business is build on would appear to be less stable than the one offering the same product for a fee (the “how do they make money? will they be around next year?” question).</p><p>There is a simple formula that you can use to figure out potential customers from a freemium model: Addressable market x Reach % x Signup % x 3%</p><p>Example case would be 4200 employees in course-ware industry in Canada x 30% that we can reach x 25% of them who sign up x 3% that convert to paying (3% is the industry standard in B2B SaaS.)</p><p>Dropbox succeeded in freemium as they literally have every business out there as their potential client. Those are big numbers…</p><p>Increasing price, would allow you to get more revenue with less active clients, but larger average sales price is also more risk for client. More risk for the client results in more clients wanting personal relationship with the vendor and that costs money.</p><p>With TitanFile our risk of losing serious confidential data stored on our servers increased sales complexity, and so did increasing the cost (more people then had to approve the purchase).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*0hbBzIjqnXUQ_XVgIzikpQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfdcb1666c58" width="1" height="1" alt=""><hr><p><a href="https://medium.com/milanvrekic/few-notes-on-the-freemium-business-model-dfdcb1666c58">Few notes on the Freemium business model</a> was originally published in <a href="https://medium.com/milanvrekic">C:/Milan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Essentials of SaaS Marketing]]></title>
            <link>https://medium.com/@milanvrekic/essentials-of-saas-marketing-82697e4a9d37?source=rss-e220df1cd88a------2</link>
            <guid isPermaLink="false">https://medium.com/p/82697e4a9d37</guid>
            <dc:creator><![CDATA[Milan Vrekic]]></dc:creator>
            <pubDate>Mon, 07 Oct 2013 00:02:59 GMT</pubDate>
            <atom:updated>2013-10-07T00:02:59.185Z</atom:updated>
            <content:encoded><![CDATA[<h4>Some things I have learned over the last few years building our SaaS product, working with SaaS companies at Volta and hanging out with the “cool marketing kids” around Halifax (mostly former Radian6 crowd)</h4><p>In a SaaS product environment, customers are always looking for signs whether they can trust their vendor. Make this an important part of your corporate identity. When you are seeking for those first few early adopters, you must understand that those people are investing in your company as much as in your product. You should allocate resources to build a corporate identity that projects trust. Some practical examples are public uptime status pages (like <a href="https://status.github.com)/">https://status.github.com)</a> or photos, names and emails of team members on the about us page etc.</p><p>You should also have a section that wins over IT professionals and managers with hard data. If you go to the <a href="http://www.salesforce.com/ca/crm/editions-pricing.jsp?d=70130000000rynQ&amp;internal=true">Salesforce pricing page</a>, you will see how they do a great job there by providing a ”Download the full edition comparison chart” document.</p><p>Your existing customers will come up for renewal once their subscription expires. Do not try to bill them without letting them know that you will renew their subscription (no brainer) but also do not make a mistake of assuming that all of them will just happily renew their subscription so that you can focus on the new client acquisition. Always treat clients that are on their last leg of subscription as prospective clients. This means, engage them, remind them of the value they are receiving and ensure their renewal goes flawlessly.</p><p>Sales and marketing for client acquisition will be your largest expense in a “true” SaaS startup. Monitor these carefully on a daily basis.</p><p>There is a common pattern among founding teams. Teams that are strong on business side do better in B2B play while teams that are strong technically do better on the B2C side. Technical teams too easily fall in the trap of promoting features. Business savvy founders know better so they promote experiences.</p><p>Selling on price never ideal but if you must sell on lower price understand that customers value reliability, ease of use and flexibility as much as they do lower cost.</p><p>Look for distribution partners only when you are already making money. I have made this mistake way too many times.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82697e4a9d37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sell for 3 months ahead]]></title>
            <link>https://medium.com/milanvrekic/sell-for-3-months-ahead-de23b13148e?source=rss-e220df1cd88a------2</link>
            <guid isPermaLink="false">https://medium.com/p/de23b13148e</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[titan-file]]></category>
            <category><![CDATA[features]]></category>
            <dc:creator><![CDATA[Milan Vrekic]]></dc:creator>
            <pubDate>Sun, 28 Apr 2013 00:22:51 GMT</pubDate>
            <atom:updated>2017-04-24T14:24:09.567Z</atom:updated>
            <content:encoded><![CDATA[<p>When selling enterprise software, your solution needs to not only solve a problem, but still make sense after 3 months of “imaginary use”.</p><p>No one says “looks good for now! I am sure you will add rest of the features we need on time” no, they fast forward 3 months in their heads and make a decision.</p><p>This is why a lot of MVPs (Minimum Viable Products) fail. In a sense, they are not “true” MVP’s.</p><p>A “true” MVP has a limited set of features, but the features it has are thought trough and function well in a scope of a solution.</p><p>Here is an example: at TitanFile we have a files panel that lists all the files belonging to the associated user. It was rolled out without an in-panel search capability with a premise that “by the time users need it, we will have it”. Time went on and as we got more users, different things took priority. Needless to say, in-panel search was not there when users needed it.</p><p>Feature creep is real and hides behind every “wouldn’t it be cool if…” So if you want to build enterprise software, start by building less — but better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*imOtUTyARjYk-EiYs9a8GQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de23b13148e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/milanvrekic/sell-for-3-months-ahead-de23b13148e">Sell for 3 months ahead</a> was originally published in <a href="https://medium.com/milanvrekic">C:/Milan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some of our Learnings from the Fundraising Process]]></title>
            <link>https://medium.com/milanvrekic/some-of-our-learnings-from-the-fundraising-process-e8a7c2e11401?source=rss-e220df1cd88a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8a7c2e11401</guid>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[investors]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Milan Vrekic]]></dc:creator>
            <pubDate>Thu, 18 Apr 2013 01:21:51 GMT</pubDate>
            <atom:updated>2017-04-24T14:12:39.130Z</atom:updated>
            <content:encoded><![CDATA[<h3>Some of our Learning from the Fundraising Process</h3><p>This is my take on the fundraising process, based on our experience at TitanFile; We have raised $1.5M total.</p><p>When fundraising, you need to “paint the picture” and show the vision of the company future. If you are looking for a large round (VC) your vision really has to be large enough to move a dial (often a test question is, “how big you think this can be?” and if your answer is less than 100 million in revenue within 5 years they will show you the doors).</p><p>When it comes to methodology, fundraising is a full time job and you need to approach it as such. Cold emailing investors is usually a one-way ticket to self-select yourself out. There is noting better than an introduction to an investor from an Entrepreneur that investor has already invested in, or someone that investor already knows and trusts who can vouch for you.</p><p>Do your homework. Make a spreadsheet of investors you want to go after and do research. Most of the investment firm web sites will say what kind of investments are they making (industry, size…) how involved they are with the companies (board, introductions etc)<br>and how the process generally goes. Be vary of those who do not have that information transparently in clear view. If possible, try to connect with someone from the companies that the investor already invested in. LinkedIn is great for that. Ask the Entrepreneur<br>openly what his experience with that particular investor or investment firm is, you will get frank answers.</p><p>You should count on 3 months minimum and 6 to 8 months maximum to close the round. Do not raise during summer. Just don’t.</p><p>That is a mistake a lot of people raising their first round make (we did too) as everyone is away on vacations.</p><p>Investment deals are like fruit baskets, if they stay on the open for too long they will rot. Or at least investors will think that the deal is rotten (ie. “This company has been looking for an investment for 9 months now, there must be something wrong with them”).</p><p>The first term sheet is the most important one. Investors are people like you and me. They wake up in the morning, put their pants on and go to work. Since Investors are people like you and me, that also means that they follow heard mentality. Once you get the first term sheet — rest will fall in line, no one wants to be the first there. Once you get that term sheet from Innovacorp, it’s a race against the clock and you need to keep the momentum going. Gust.com is a great way to find more investors and so is <a href="http://angeli.st/">http://angeli.st</a></p><p>Make sure to take all the press clippings and press articles about your product and team with you as investors will always seek external validation but DO NOT include them in the pitch deck. Send them over after there is some definite interest. If you do not have clients to validate you, press is a great option B (i.e. “Someone else also thinks this is a good idea so I won’t look like a fool if I invest and this fails”) but no amount of press will replace a referenceable, paying client.</p><p>Cash-flow analysis and projections are important but the exact numbers are not that important. It’s really a litmus test of how crazy you are. Going from 100k to 500k in revenue from year one to two is reasonable. Going from 100k to 100 million in a year is not. Once you close a round It will be months before you figure out where your head is and where your ass is. Also, NEVER use words such as “our estimates are conservative” :)</p><p>You should always aim to raise 6 months more than you need.</p><p>Idea is that it will take another 6 months to close the next financing round if you need one, so it is always better to have extra cash in the bank. No one ever had a headache from too much money, but a lot of people had a lot of headaches about having too little. Keep in mind that you need to be able to explain and justify your valuation. If you say 1 Million — cool, if you say 10 million — cool. It is really up to you convince an investor that your valuation is “correct” (ie. “each engineer ads 500k to valuation, Our MBA guy takes away 250k from valuation, we have X patents that add another 1 Million, we already have signed purchase orders for Y and that adds another 5 million etc.).</p><p>Finally, deal is not closed until cash is in the bank.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ImTzpkMdMm90ZMOB6KWJPQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8a7c2e11401" width="1" height="1" alt=""><hr><p><a href="https://medium.com/milanvrekic/some-of-our-learnings-from-the-fundraising-process-e8a7c2e11401">Some of our Learnings from the Fundraising Process</a> was originally published in <a href="https://medium.com/milanvrekic">C:/Milan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Painkillers, Vitamins and habit in product design]]></title>
            <link>https://medium.com/milanvrekic/painkillers-vitamins-and-habit-in-product-design-6daca080a4ac?source=rss-e220df1cd88a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6daca080a4ac</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Milan Vrekic]]></dc:creator>
            <pubDate>Sun, 17 Mar 2013 16:45:32 GMT</pubDate>
            <atom:updated>2017-04-24T14:19:35.086Z</atom:updated>
            <content:encoded><![CDATA[<p>If you talk to an early stage VC or an Angel Investor, they will often ask you to declare if you product is a “Painkiller or a Vitamin” product. What they mean by this analogy is “does your product solve a pain or you are making something that is solved — better”</p><p>There is really no sharp divide between solutions that are “vitamins” and solutions that are “painkillers”. It’s more of a continuum.</p><p>“Painkiller” products by definition have a quantifiable market, they can be monetized from the get-go and they solve a pain people know they have.</p><p>“Vitamin” products in contrast, appeal to the emotional need, not efficiency; they usually have an unknown market at the launch and they often start with “<em>Wouldn’t it be cool if…</em>”</p><p>If we look at some of the largest web applications on the internet today (<em>Facebook, Pinterest, Instagram, Twitter…</em>) it is easy to state that those products are “Vitamin” products as they have no pain component to them. If I said that the very first time you saw Facebook you could not see yourself using it more than once in a while — you would most likely agree.</p><p>Now, what Facebook and the best examples of the “Vitamin” products do well, is engage in a habit creating behaviour where the user comes to the web-site for pleasure seeking behaviour and over the time, the habit becomes so strong that <strong>NOT</strong> using the product becomes a pain. This is easy to illustrate again using the Facebook example: Just think about how you feel when you see a new message notification and you do not know who is it from?</p><p>For our brain, unknown is a fascination. We are wired to connect cause and effect. Similar effect is exploited successfuly by some of the biggest dating sites. You create your profile for free, you receive a message from someone and in order to see the message, you have to upgrade your subscription.</p><p>The brilliance of these companies is that over the time, they build habits that create the pain and then — sell you the remedy; combining the nature of both, “Vitamin” and “Painkiller” attributes in a company.</p><p>So, if you have a “vitamin” product, how do you add a bit of a “painkiller” in the product design cycle?</p><p>1.) Implement variable reward. Intermittent rewards <strong>INCREASE</strong> the response rate (did someone say gambling?) and the main driver is <a href="http://en.wikipedia.org/wiki/Dopamine">dopamine</a>. Every time you receive an unexpected reward -your dopamine levels spike. Great practical example of this is Pinterest. Pinterest is designed in a way that entices you to scroll. One scroll is all they need to start the habit building process. Each scroll is a chance to be rewarded with a picture (pin) of something you like… so you just keep scrolling… When rewards are predictable, they become less rewarding. Zynga games are a good example of this, they have massive initial adoption rates and also a huge churn rate shortly after.</p><p>2.) Understand the motives for desired behaviour and build triggers to exploit them. People have seeking and avoiding motivators. Seeking motivators are pleasure, hope and acceptance. Avoiding motivators are pain, fear and rejection. Your triggers (popups, emails, calls to action…) must align with the right motivator. People join Facebook to seek social acceptance from their friends and avoid rejection by the group (think of all the Facebook organized events and parties that you know about just because of Facebook).</p><p>3.) Increase the action potential by making it easier to perform a desired action. Doing is easier than thinking. To understand this better, look into the<a href="http://www.behaviormodel.org/"> Dr. BJ Fogg Behaviour model grid</a>. Great example of this is evolution of the dropbox and twitter home page over the years:</p><p>4.) Negative emotions are painful and people will seek a “painkiller” to alleviate them. Depressed people <a href="http://www.nydailynews.com/life-style/health/depressed-people-surf-web-differently-check-mail-compulsively-watch-lot-videos-quickly-switch-multiple-internet-applications-article-1.1098496">check email more often</a>. You can make an argument that email is what makes them depressed but a more likely explanation is that they check email looking for something that would “lift” their mood. This is where good UX comes into play, in competing products, identify negative experiences that would result in negative emotions and make sure that your product addresses those from the get-go.</p><p>This is by all means not a comprehensive list but it will get you started and pointed in the right direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UykmVC2jQf_ug75oAUAmOA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6daca080a4ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/milanvrekic/painkillers-vitamins-and-habit-in-product-design-6daca080a4ac">Painkillers, Vitamins and habit in product design</a> was originally published in <a href="https://medium.com/milanvrekic">C:/Milan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Startups, this is how to do great sales demos]]></title>
            <link>https://medium.com/milanvrekic/startups-this-is-how-to-do-great-sales-demos-c5305e308d33?source=rss-e220df1cd88a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5305e308d33</guid>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Milan Vrekic]]></dc:creator>
            <pubDate>Sat, 25 Aug 2012 14:06:00 GMT</pubDate>
            <atom:updated>2017-04-24T14:15:45.233Z</atom:updated>
            <content:encoded><![CDATA[<p>We believe that a startup has no business hiring sales people before founders can close sales on their own. If you cannot sell your product, chances our other people won’t be either. So here are some things we learned, that helped us close some decent deals in the last 12 months:</p><p>1.) Your sales pitch needs to clearly communicate at least one of the four positive measures:</p><p>- Our product is cheaper (than what client is already using; least valuable point)<br>- Our product is better (needs to be quantifiable better)<br>- Our product is faster (value of this point fluctuates with the type of business)<br>- Our product lets you do things you could not do before (most valuable point)</p><p>Unless you are Wall mart or Costco — you do not want compete on price. Ever. There will always be someone out there, who can (and will) undercut you.</p><p>Sales people, especially founders doing sales. Assume too much about their clients. Finish your sales pitch always with “Is there anything else I should ask that I did not ask?”</p><p>You will be amazed with the feedback you will get. In our case, they would volunteer information about problems they currently have, their existing solutions (your competitors), their needs, etc..</p><p>For example, from one of our sales pitches “When we currently try to share with “X” department from our mobile device using “Y” product (competitor) we do not know if they have received it?”</p><p>From that one sentence, we learn that they share information internally (with another “X” department), they use mobile devices (therefore should be pitched mobile apps as a sales point) and we learn that our competitor “Y” is lacking a feature they need.</p><p>2.) No one wants to waste time, so prior to each meeting clearly define:</p><p>- Meeting location (It is always better to meet at a neutral location — like a bar or a coffee shop but that is rarely an option, next best thing is clients office, and finally — your office)</p><p>- Meeting date (try to get Tuesdays, Tuesdays are ideal. While people are most eager on Mondays, they are also too busy. Fridays are bad. People (most of them) mentally check out come Friday.</p><p>- Start and end times (this will give client an idea on how much of their time you will take. A lot of meetings get dropped or declined because potential client is afraid you will just take up too much of their time and they will be too polite to kick you out).</p><p>- Meeting objective (is this a meeting to learn more about the client and “feel” if the person you are meeting can serve as “internal champion” that is, someone who will “push” for adoption of the product from within, or is it a meeting to show your solution to larger audience)</p><p>- Specific roles (Understand the chain of command in the company you are going into. LinkedIn is a great tool to map out “who reports to who” and how a chain of ddecision making might work)</p><p>Oh, and always be nice to executive assistants (secretaries in the “old speak”). They will in most cases be the gate keeper. Many of the ones we spoke to, outlasted two or more CEO’s. They often hold huge power and knowledge about the company and internal processes. Befriend them.</p><p>3.) Internal champion will almost always be someone who is not a newbie at the company (he has too much to risk) or a C level executive (they are too busy). So you should look for your internal champion in the middle management. That is, people who are high enough on the corporate ladder so that their jobs are safe if you turn out to be a DUD but have a lot to gain if they promote a solution that results in success.</p><p>Once you find an internal champion, ask him for real-world problems company is facing in their work and then use those examples to illustrate the use of your product in a demo to solve those problems. People will be able to instantly relate.</p><p>4.) Give promo material at the end. If you give it out at the start of your demo, your audience will jump ahead of you and form conclusions and assumptions that you then have to spend extra time explaining/debunking.</p><p>5.) During your sales demo, there will always be questions. There is such a thing as a “dumb” question. There is in fact also a “great” question and a “good” question. “Great” questions you should answer right away as they will usually speak to benefits of your product/solution. “Good” question you should answer at the end of your demo and “dumb” ones… you should still answer them but at the very end, if there is time (after the “good” questions).</p><p>So how do you define a “great” question? It is usually a question that leads to the next product screen or next slide (if powerpoint is your thing…)</p><p>6.) You should work on developing a series of “60 second sales pitches” that are targeted at specific problems in your target market. Very often, you will have only a short time to pitch a prospect and if you know their business (most likely you will exchange business cards…yes people still do that…sorry <a href="https://bu.mp/">bump app</a>) you will be able to pitch them on solving their specific need rather than giving a bland “We make business awesome” pitch.</p><p>7) It is ok to hear “No”. The most competitive companies close about 15% of deals that come their way. and 70% of all prospects will NEVER buy from ANYONE. Learning how to identify those is more art than science. You will get better at it with time.</p><p>Happy prospecting and demoing! I am looking forward to my commission cheque ;)</p><figure><img alt="Salepic" src="https://cdn-images-1.medium.com/max/496/0*m5bhKDvN7Z1zGrZL.jpg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5305e308d33" width="1" height="1" alt=""><hr><p><a href="https://medium.com/milanvrekic/startups-this-is-how-to-do-great-sales-demos-c5305e308d33">Startups, this is how to do great sales demos</a> was originally published in <a href="https://medium.com/milanvrekic">C:/Milan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[15 things we learned about interface design as developers]]></title>
            <link>https://medium.com/milanvrekic/15-things-we-learned-about-interface-design-as-developers-5c12490d3a68?source=rss-e220df1cd88a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c12490d3a68</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[titan-file]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Milan Vrekic]]></dc:creator>
            <pubDate>Wed, 22 Aug 2012 04:46:00 GMT</pubDate>
            <atom:updated>2017-04-24T14:14:33.728Z</atom:updated>
            <content:encoded><![CDATA[<p>As developers who realized that no one will care about our product or clients more than ourselves, we took the design of our new product iteration onto ourselves. These are the 15 things we learned about user interface design in the process:</p><p>1.) Use patterns as much as possible. You can even use groups and white space to create patterns.</p><p>2.) Things that are close together should belong together. Look at the example remote bellow. Buttons form logical groups based on their functions.</p><figure><img alt="Np4001remote-600" src="https://cdn-images-1.medium.com/max/600/0*JKIePDpaJtmCNP3x." /></figure><p>3.) 9% of all men are color blind. Use <a href="http://vischeck.com/">vischeck.com</a> to check how your site, or web app looks to those people.</p><p>4.) Whenever possible, use progressive disclosure. Principle of progressive disclosure dictates that the user should be provided only the information he needs at that time. More information on screen increases chances for confusion and ultimately — inaction.</p><p>5.) If you must make tradeoffs between clicks and thinking. Use more clicks and less thinking.</p><p>6.) People are more motivated as they get closer to a goal. Example: Coffee shop has two types of stamp cards. Card A with 10 stamp slots and card B with 12 stamp slots but 2 already pre-stamped. Card B is set to perform much better. People will focus on what remains to be done vs. what is already completed.</p><p>7.) All error messages should tell people what they did wrong. Explain the problem and instruct user how to correct it. Error messages should be written in active, not passive voice. Never make the user feel stupid by making an error message sound accusatory.</p><p>Example of a really bad iTunes error message:</p><figure><img alt="Tumblr_l5ss78whhg1qcytnmo1_1280" src="https://cdn-images-1.medium.com/max/554/0*Pf61-vPbqrUE3WzE." /></figure><p>…and a really good one:</p><figure><img alt="Picture_48" src="https://cdn-images-1.medium.com/max/500/0*FN6Rl7RAm6ktTq-H.png" /></figure><p>8.) If people are doing a boring task, raise the level of arousal with colors, sounds and movement but be careful not to overdo it.</p><p>9.) If people are doing a difficult task, decrease the level of arousal by eliminating any distracting elements such as colors, sounds or movement.</p><p>10.) Make your forms cache non-confidential information (such as text areas and text boxes) real-time. So that in case user is interrupted he can continue later. If it is worth user entering — it is worth app remembering.</p><p>11.) Never give a blank slate. Once they sign-up, make sure that the first step is not theirs but yours. It is not an accident that Dropbox pre-creates a welcome file for each new user.</p><p>12.) If you design for the extreme scenarios, the middle will often take care of itself.</p><p>13.) Avoid unnecessary reporting. There is no need for a “good job” notification every time a user performs a task successfuly.</p><p>14.) Feedback has to be constant and instantaneous. It can be a sound you hear when you press a button or a light you see when you receive a message.</p><p>15.) Color is a communication tool. Use of color should be unobtrusive. If you are making an app people will use on a daily basis you cannot make the background yellow or buttons pink. Colors must respect and fit in the environment.</p><p>Our new app (soon to be out)</p><figure><img alt="Titanfile_draft_passport" src="https://cdn-images-1.medium.com/max/1000/0*tXwvC3fHq4fAjzi-." /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c12490d3a68" width="1" height="1" alt=""><hr><p><a href="https://medium.com/milanvrekic/15-things-we-learned-about-interface-design-as-developers-5c12490d3a68">15 things we learned about interface design as developers</a> was originally published in <a href="https://medium.com/milanvrekic">C:/Milan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secretive or open dialog when it comes to products-in-development?]]></title>
            <link>https://medium.com/milanvrekic/secretive-or-open-dialog-when-it-comes-to-products-in-development-9d240fa4d1a0?source=rss-e220df1cd88a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d240fa4d1a0</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[pr]]></category>
            <category><![CDATA[stealth]]></category>
            <dc:creator><![CDATA[Milan Vrekic]]></dc:creator>
            <pubDate>Sat, 07 Jul 2012 19:49:00 GMT</pubDate>
            <atom:updated>2017-04-24T10:30:36.875Z</atom:updated>
            <content:encoded><![CDATA[<p>“Stealth mode” of product development is in my opinion reserved for two kinds of founders:</p><p>1.) <em>Insider Founders</em>. That is, founders who are certain, beyond doubt that they are building something people want. These founders usually have big insight into a small segment of market or particular insight into behavioural patters of a certain groups of users. These founders are usually people who got their experience working in senior management or engineering roles at established companies.</p><p>2.) <em>Visionary founders</em>. That is, founders who have had past successful exists and have built <em>solutions for problems people did not know they had</em>.</p><p>If you are aware of the problem in a particular market, but do not know yet how the solution looks like — you are much better off being open about the problem you are addressing and how your solution will address the problem. The risk/benefit ratio is shifted in your favour as likelihood that someone will provide feedback and/or insight that will improve your solution is much, much greater than someone “stealing your idea”, unless of course, you are in the pure IP play.</p><p><strong>From the PR perspective:</strong></p><p>If you are building a consumer product and need a lot of social validation by the way of press — going public with it is the way to go for few reasons:</p><p>1.) Everyone loves to break a good story first. Especially if your product shows potential for the “next big thing”. Going public with it will ensure that by the time you launch, you have at least several relationships in place with journalists and media that will continue to cover your startup as the months go by.</p><p>2.) You get the leverage smaller press against a bigger one. No one wants to be wrong. If you have been covered in a local paper, chances are that regional paper will be quite interested in covering you (again, because of social validation, “<em>someone else said this is good stuff, so, chances are that this will be a flop are lesser</em>”) and then in turn, if you get covered by a regional paper, you can leverage that to get national coverage etc.</p><p>This however, is not true in the case of a visionary founder, where the mystique of “proven child” working on “something revolutionary” outweighs everything ( Simple proof in point — Kevin Rose and Milk inc.)</p><p><strong>From the psychological perspective:</strong></p><p>It is shown and proven over and over, that <a href="http://en.wikipedia.org/wiki/Deferred_gratification">delaying gratification</a> results in increased rate of successfully completed tasks and projects.</p><p>What that means practically is that by telling people (and press) about the project you are working on and receiving praise and positive feedback will result in you receiving immediate gratification from recognition of your idea and end in a lot of cases with founder being bored by the idea and project (“<em>I already got the praise for minimal effort placed in the project so far, all the hard work I yet have to put in it will not result in the same level of praise again, so I might as well move on to something new..”</em>)</p><p>By “going stealth” and keeping the project a secret until the release, you are delaying gratification and increasing the chances that the project will in fact — be completed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d240fa4d1a0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/milanvrekic/secretive-or-open-dialog-when-it-comes-to-products-in-development-9d240fa4d1a0">Secretive or open dialog when it comes to products-in-development?</a> was originally published in <a href="https://medium.com/milanvrekic">C:/Milan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>