<?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 Erez on Medium]]></title>
        <description><![CDATA[Stories by Erez on Medium]]></description>
        <link>https://medium.com/@erezroso?source=rss-a626524e5d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ZDVcjqYWfigusRAl.jpeg</url>
            <title>Stories by Erez on Medium</title>
            <link>https://medium.com/@erezroso?source=rss-a626524e5d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:03:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@erezroso/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[How Strong Companies Can Weather A Crisis: The Ten Pillars That Got Us Through]]></title>
            <link>https://medium.com/@erezroso/how-strong-companies-can-weather-a-crisis-the-ten-pillars-that-got-us-through-3ef1b46f2a0c?source=rss-a626524e5d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ef1b46f2a0c</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Erez]]></dc:creator>
            <pubDate>Tue, 04 Apr 2017 00:40:54 GMT</pubDate>
            <atom:updated>2017-04-04T01:22:50.795Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi there, I’m Erez. CEO and co-founder of a startup called Rollout.io.</p><p>Here is my story and lessons learned from dealing with a major crisis our startup went through.</p><p><strong>A little background<br></strong>For the past two years Rollout has been providing a solution that lets iOS developers instantly patch bugs in live apps without the need to go through the App store review process. (<a href="https://rollout.io/blog/updating-apps-without-app-store/">yes, this is legit</a>)</p><p>As a startup, we’ve been going down a fairly expected growth path. $3.5 million in funding, 12 employees across three time zones. Hundreds of Happy customers, and our SDK is installed on over 50M devices.</p><p>Then, starting on the morning of March 7 Apple basically told all of our customers to remove our SDK, saying it was a violation of their license agreement. You can learn more about that <a href="https://rollout.io/blog/rollout-statement-on-apple-guidelines/">here</a> and <a href="https://rollout.io/blog/open-letter-to-apple-secure-javascript-injection-ios/">here</a>.</p><p>A few hours later a <a href="https://news.ycombinator.com/item?id=13817557">Hacker News thread</a> on the issue reached the first page on Hacker News and we started getting tons of inquiries on our website, followed by a lot of attention from the media.</p><p>This could have been fatal to our company. Instead, because we were prepared, we emerged even stronger.</p><p>Here are the ten pillars that held us up:</p><ol><li><strong>Capture Creativity<br></strong>When you’re busy with day-to-day work, it can be hard to come up with out-of-the-box ideas. On the other hand, when your back is up against the wall and the adrenaline is pumping, is often when the most creative ideas are born. <br><br>Make sure you capture those ideas. Even if you can’t run with them during the crisis, it’s great to revisit them later to get your creative juices flowing.</li><li><strong>Assemble an Awesome Team <br></strong>I know it’s a cliche, but it’s true.<br> <br>Your team truly is your biggest asset. Our team is distributed between San Francisco, New York and Tel Aviv. When the news broke it was morning in SF and already night time in Tel Aviv. It was immediately clear that this was an all-hands-on-deck situation. We knew we had to react quickly, but at the same time not panic. The whole team rose up to the challenge and we worked together as a team, leveraging each person’s strength.<br> <br>First we tried to decipher Apple’s outreach, but we still had many open questions. Had something changed? Why now? What exactly was Apple conveying in its message (they raised a few different points) What can we do right now to address Apple’s concerns?<br><br>Keep in mind that at this stage we were working with almost no information besides the email our customers forwarded to us. We quickly had to react to customers and the media while assessing what we can do on the product side to address Apple’s email. The team had to be agile, creative and fearless through this process.<br><br>When this happened, we were already on a very tight schedule to release our new product, a <a href="http://info.rollout.io/coming-soon/">continuous feature release system for mobile apps.</a> The team had to stop everything and and focus on this event.<br><br>When an event like this happens, you need a team that will be willing to work around the clock, be positive, and focus on “what needs to be done”. For me, one of the bright sides of the whole experience, was how well the team performed when faced with such event.</li><li><strong>Clear Mission<br></strong>Our vision at Rollout has always been to help mobile app developers move faster. Our first product lets developers fix issues in live apps instantly. About half a year ago we started working on a new product which goes beyond the issue of fixing production bugs and addresses the broader problem of developing and deploying new mobile features quickly and safely.<br><br>Having a clear mission gave us the ability to look beyond the crisis we were currently going through, and provided the shared direction we needed when making tough decisions.<br><br>Without a shared vision that we could agree on, it would have been difficult to reach consensus regarding the actions we needed to take during the storm.</li><li><strong>Work with a Supportive Board and Investors<br></strong>The least stressful call was actually to our investors. Calling them each individually allowed me to have a personal conversation with each of them, opposed to a conference call. They are not only experienced investors, but also seasoned entrepreneurs and they fully understand the rollercoaster ride that startups can go through. They did not panic, pressure us for answers, or ask us to lower our burn rate. They were extremely reassuring, and in a calming voice helped us turn a crisis into an opportunity. They kept reinforcing that they too, fully believe in our mission, and our plans and encouraged us to be bold.</li><li><strong>Select The Right PR Firm<br></strong>When the $#!+ hits the fan, you need to be able to call your PR firm to get guidance no matter what time it is. As it turns, we signed up with a new <a href="http://www.lightspeedpr.com/">PR agency</a> just one week before all hell broke lose. We chose them because we felt they will be a good fit for our culture of focus and speed. Little did we know that just a week later, we would get a chance to test our decision to go with them. Time was truly of the essence and we needed to answer our customers, the media, and even the trolls. <br><br>Our PR firm was on top of it immediately to help us get clarity on the message we wanted to convey. They also understand the media very well, what they are looking for, and guided us with help on what we should or shouldn’t say. As a CEO of a start up company, I was always very reluctant to hire a PR agency. After all, budgets are tight, and every dollar spent should have a clear ROI, but boy, am I happy I decided to spend that dollar.</li><li><strong>Select The Right Law Firm<br></strong>As the CEO, one of the first things that was on my mind was to figure out if there were any liabilities from Apple or our customers. Issues like this can kill a company and I needed to know ASAP if the company was exposed in any way. I called our lawyers at 11pm their time with an initial update. One hour later we were on a conference call with the relevant partner in the law firm. Impressive.</li><li><strong>Foster Happy Customers<br></strong>Bringing real value to our customers and providing excellent, personal support pays off when an unexpected crisis hits. The most heartwarming and supportive comments came from our customers. Here are a few examples:<br><br>“Thanks for the update. Good luck, let us know what comes out of it…”<br><br>“Hey guys…i know you have a lot on your plate right now with this apple stuff. hang in there.”<br><br>“I saw the news about Apple rejecting apps with Rollout : They’re making a huge mistake. Services like Rollout are improving the quality of apps in their store….”<br><br>“Regardless of what happens, you’ve got a team of geniuses over there and I’m sure you’ll land on your feet.”</li><li><strong>Focus<br></strong>When you’re on the front page of Hacker News, and the media is already writing a one-sided story, it’s easy to get distracted. Everyone needs to understand what’s truly important and what’s just noise, and distinguish between what we should react to and what to just ignore.<br><br>We saw many incorrect comments and stories about Rollout’s tech and about Apple’s guidelines but we just had to ignore them and focus on what’s really important — our customers, our outreach to Apple and our coming product launch.</li><li><strong>Awesome Life Partner<br></strong>It really helps if you have an awesome partner. Building a successful startup is hard work and time consuming. Throw in an emergency, and the intensity grows exponentially.<br><br>When my wife heard me tell my co-founder over the phone — “We’re in a code red”, she understood that for the next few days I wasn’t going to be available and that she’ll need to handle everything else on her own. Having a partner that understands you and gives you the space to do what you need is imperative.<br><br>I haven’t quite built a great company yet, but I finally understand why so many speeches start with the speaker thanking their partner.</li><li><strong>Don’t Panic<br></strong>Douglas Adams was right. You’ll get through this. <br>Particularly if you are in a management position, it’s important that you set the proper tone for your employees, partners, and customers. Don’t make light of the situation, but show that you have a plan for emerging from it.</li></ol><p>This situation tested every element of our company, and as a result we have emerged even stronger than we were going in. Hopefully your company never has to deal with what we did. But if you ever do, these pillars can only help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ef1b46f2a0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You are validating your product wrong, why Rollout.io asked the right customers the wrong questions]]></title>
            <link>https://medium.com/@erezroso/you-are-validating-your-product-wrong-why-rollout-io-asked-the-right-customers-the-wrong-questions-911d31db18b4?source=rss-a626524e5d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/911d31db18b4</guid>
            <dc:creator><![CDATA[Erez]]></dc:creator>
            <pubDate>Wed, 10 Sep 2014 11:55:03 GMT</pubDate>
            <atom:updated>2014-09-16T15:00:03.669Z</atom:updated>
            <content:encoded><![CDATA[<h3>You are validating your product The wrong way</h3><h4>How we asked the right customers the wrong questions</h4><p>When we started <a href="http://rollout.io/"><em>Rollout.io</em></a>, we wanted to help mobile developers (especially iOS developers) deal with the “pain” associated with the long mobile release cycle. More specifically, help mobile developers deal with bugs and quality issues in production. Fixing or changing anything in their mobile app would require them to go through the full release cycle every time even during ‘panic mode’.</p><p>The problem can be summarized in a couple of questions: What do mobile developers do when they discover they have a bug or crash in production, and what are the damages?</p><p>The typical answer we get is that it’s a nightmare— fix the bug in ‘panic mode’, rush the Q&amp;A process or even skip it altogether, release to the AppStore using the “expedite review” service, wait, answer outraged customers, see the bad reviews, wait some more, try to figure out if you have connections in Apple that can help speed the process, nail-biting, stop all user acquisitions campaigns, more waiting, find Apple review team on Facebook and try to contact them (true story), try to solve the problem from the backend side, and more. If you&#39;re lucky, the damages are minor, but in a lot of cases the <a href="http://blog.rollout.io/2014/07/infographic-bugs-and-issues-in-mobile-apps/">damages to you mobile company are huge.</a></p><p>The waiting time for a release cycle in this ‘panic mode’ can be anywhere from 24 hours to a few days, and in some cases even weeks. And then of course you still hope that your new release is not buggy as well (since you rushed the QA), otherwise the entire process will happen again. You could say, “it wont happen to me” but it happens when you least expect it, and it happens to big and small companies alike.</p><p>Our initial solution to the above problem was to let iOS developers package two versions in the same IPA file and allow the developer to remotely switch between them. The idea was that on each new release you will have your old stable release available to fall back to in case of a catastrophe, without going through the AppStore. Sounds good, no?</p><p>We decided to go directly to app companies and ask them about the problem and solution in order to make sure (=validate) that our product worth a buck. We built a question list that we kept updating, and tried talking to who ever we could find — indie developers, service companies, big companies, other SDK companies, etc. Here are part of the companies we talked to: <a href="http://www.viber.com/">Viber</a>, <a href="http://www.fring.com/">Fring</a>, <a href="http://www.magisto.com/">Magisto</a>, <a href="http://moment.me/">Moment.me</a>, <a href="http://www.for-each.com/">Foreach</a>, <a href="http://www.any.do/">Any.do</a>, <a href="http://www.askem.com/">Askem</a>, <a href="http://www.joytunes.com/">JoyTunes</a>, <a href="http://ringya.com/">Ringya</a>, <a href="http://www.mysupermarket.com/">MySuperMarket</a>, <a href="http://win.com/">Win.com</a>, <a href="http://www.bizzabo.com/">Bizzabo</a>, <a href="http://www.appmyday.com/">AppMyDay</a>, <a href="http://www.wibbitz.com/">Wibbitz</a>, <a href="http://www.yokee.tv/">Yokee</a>, and many many more…</p><p>Our customer discovery process had three major flaws which are listed below, eventually we managed to fix these flaws and as a result got invaluable insights that made us change <a href="http://www.rollout.io/">Rollout.io solution</a> completely.</p><p>Here are some of our mistakes and lessons we learned:</p><p><strong>Key Learning #1</strong></p><h3><strong>Separate the validation of the problem from the validation of the solution.</strong></h3><p>At the beginning our validation process mixed solution and problem in the same interview. This made it impossible understanding the feedback — did they just liked the solution, but did not have a real problem or they have a real problem but don’t like the solution, or both?</p><p>We wasted a lot of time and resources on the wrong solution. Only after we validated the problem separately from the solution we understood that the problem is very real and painful but our solution is bad (complex, deals with only very narrow use-cases, has some unresolved technical issues,etc), also our morale was fading away since it seemed that the “pain” is not large enough when the actual case was that the solution was not good enough.</p><p><strong>Key Learning #2</strong></p><h3><strong>Validating the problem is NOT asking it directly.</strong></h3><p>When we started our problem/solution validation process we asked many direct questions, such as: “Have you had production bugs ?”, “How many production bugs did you have ?”, “What was the impact of these bugs in production?”. As much as some of these questions are great they do not give you a clear image. Imagine getting the following answers — “Yes, we had production problems about 4 times a year, the impact was crazy, I would definitely pay at least 200$ a month for a solution”, seems like great validation of the problem, but in reality these type of customers want to please you, they know what you are doing and they do not want to make you feel bad (unintentionally).</p><p>The validation has to go deeper, in our case we needed to see how our potential customers deal with quality issues on their mobile app, how critical is mobile in their strategy and what are they doing today to avoid quality issues in production. Questions like — “How do you Q&amp;A ?”, “How many people are on the Q&amp;A team?”, “Which app crash reporter service do you use ?”, “How do you discover you have a production issue?”, “How are you tracking your bugs?”, “Which type of bugs did you have, can you elaborate ?”</p><p>After we started asking both type of questions (direct and indirect) we saw that in more than one case the answers would look something like this:</p><ol><li>Have you had production bugs? — Yes.</li><li>How many production bugs did you have? — About 4 times a year.</li></ol><p>3. What was the impact of these bugs in production? — The impact was crazy, I would definitely pay at least 200$ a month for a solution.</p><p><strong><em>(Up to here everything seems good)</em></strong></p><p>4. How do you Q&amp;A? — We do it internally, some of us use the app before we send it to the app store.</p><p>5. How many people are on the Q&amp;A team ?— no one is dedicated, the developers check.</p><p>6. Which app crash reporter service do you use — we do not use any crash reporter, we use the generic Apple crash reporter.</p><p>7. How do you discover you have a production issue? — We start getting complaints from users, we see the bad reviews, a friend tell us something is not working, etc.</p><p>8. How do you know why the app is crashing? — We do not check all the small issues, if it’s something big and most customers are affected we debug and release a new version ASAP.</p><p>As you can learn from the above more in-depth Q&amp;A, the company that answered does not address quality issues as a priority and <strong>getting validation to the problem from them is meaningless, even though the answers to the direct questions seemed very helpful and ״validating”</strong></p><p><strong>Bottom line: Do not pitch your idea to the customer, try to understand the routine (and find validation to the problem there)</strong></p><p><strong>Key Learning #3</strong></p><h3><strong>When trying to validate the solution, you have to put your potential customers in the position that <em>they </em>need to make a decision</strong></h3><p>So you validated the problem and sure it’s big and painful, now you are trying to validate the solution, you need somehow to make sure your solution is good enough and that you are in the right direction.</p><p>As in lesson #2, many potential customers would not tell you your solution suck, you need to make them make a decision, it can be payment, it can be some other type of commitments — such as a weekly meeting with the development team to start integrating the solution.</p><p>If they are not willing to commit to anything, either they do not have the problem or you solution is problematic.</p><p><strong><em>Conclusion</em></strong></p><p>The discovery process is an invaluable process but it needs to be done correctly, otherwise it creates noise and distractions with no real insights in regards to either the problem or the solution. Try to figure out the questions that will give you an answer you&#39;re not expecting. Drill down deeper, and get to the core. Don&#39;t offer a solution, ask for the customer to describe it for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=911d31db18b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>