<?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[GoToAssist Product Blog - Medium]]></title>
        <description><![CDATA[How we build GoToAssist - Medium]]></description>
        <link>https://medium.com/gotoassist-product-blog?source=rss----574d41514608---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>GoToAssist Product Blog - Medium</title>
            <link>https://medium.com/gotoassist-product-blog?source=rss----574d41514608---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:35:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/gotoassist-product-blog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Assisting new employees in the field]]></title>
            <link>https://medium.com/gotoassist-product-blog/assisting-new-employees-in-the-field-223956fd7e01?source=rss----574d41514608---4</link>
            <guid isPermaLink="false">https://medium.com/p/223956fd7e01</guid>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[logistics]]></category>
            <dc:creator><![CDATA[Jacob de Lichtenberg]]></dc:creator>
            <pubDate>Mon, 21 Mar 2016 15:21:16 GMT</pubDate>
            <atom:updated>2016-03-21T15:21:16.136Z</atom:updated>
            <content:encoded><![CDATA[<p>When you start working in a new position, most people are overwhelmed with information. Nowadays, even the most simple day jobs require employees to follow standard procedures and knowledge around what to do in specific situations. Most people can quickly learn the 80 % normal situations. But what about the 20% non-standard situations. These can normally be handled easily when you work on the same location, and can get help from colleagues. But happens if you have an entire staff of field workers?</p><h4>Example: The evolution of complexity in parcel delivery</h4><p>Any profitable delivery company or courier will have a workforce consisting mostly of field workers delivering parcels. Initially in the history of delivery, the documentation you had for actually having delivered a parcel was a signature on document.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*2DbrCzLdGtregBSDT7r_uA.jpeg" /><figcaption>Signatures on paper is so embarrassing for logistics/delivery companies that we had to find a stock photo to show this. No serious delivery company would show a picture of this anymore. It is all history.</figcaption></figure><p>Delivery companies were some of the first companies to implement handheld devices as PDA’s, palm pilots, and mobile devices to their field workers (deliverymen and couriers). Below is an example from the Canadian Post:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*A6wHZ_76uknqO7ZedH_14A.jpeg" /><figcaption>The PDA of Canadian Post.</figcaption></figure><p>Using these devices gave the possibility of tracking delivery, and gave their customers electronic evidence that parcel and goods had been delivered. With these devices, new possibilities and opportunities emerged for the delivery companies. Besides documentation, these devices could be used for all kinds of data logging. And many new procedures were created around the devices. Two main use cases are:</p><ul><li>“Parcel delivered”, where the customer signs and the deliveryman or courier logs the delivery.</li><li>“Customer not home”, where the courier finds the option on the device and logs that he was not able to handover the parcel.</li></ul><p>For most delivery companies these two scenarios cover 80% for the work. All new employees can learn that. But the last 20% consists of hundreds of other scenarios, most were developed for these devices. Scenarios such as:</p><ul><li>Customer refused to accept delivery</li><li>Customer ID seen</li><li>Parcel placed in front of door in agreement with sender</li><li>Address not found</li><li>Missing address information</li><li>Not delivered on time</li><li>Delivered express<br>…and the list goes on.</li></ul><p>These possibilities are hiding in a <em>UX nightmare </em>of large menus and lists. With the implementation of mass consumer devices like Android devices, the list of possibilities has just grown — including payment.<br>With these internal and non-intuitive apps new employees have to waste time navigating through all the possible options. This isn’t something something you’d want to be doing if you’re already late on your delivery route. As you can see below, the user interface can be quite complicated:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7u61TLwSBRS4aRMYFTBMvQ.jpeg" /><figcaption>New employees get confused by the endless possibilities.</figcaption></figure><p>Since the field worker have nowhere to get help before they get back to the office, the result is that new employees do nothing or put in the wrong data.</p><p>Over time, this lack of knowledge can turn into bad habits. While I worked in the delivery industry, this was a daily battle: Getting employees to actually do the right thing — because they never learned it due to being in the field.</p><p>To give you an idea of the consequence of putting in wrong data; it often means that the parcel will be unnecessarily redelivered (very costly) or returned (angry customer).</p><p>So what can you do to help field workers in a critical situation like this?</p><h4>Guide the new field worker in the moment of uncertainty</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ym6x3fbrw1lA291NPPF3g.jpeg" /><figcaption>By adding a simple help button, new delivery employees can get help to put in the right data in the moment of uncertainty.</figcaption></figure><p><a href="https://live.gotoassist.com/">GoToAssist Concierge</a> is a new product that can be used to solve the onboarding problem for field workers by providing the possibility to get help from the back office. Experts in the back office can guide the new employees directly on the screen, can help the field worker complete the right data entry in as fast as 20 seconds.</p><p>By adding a simple button, the new employee can directly contact the back office. The distribution manager or an experienced employee can quickly help the new field worker select the right category and continue on his route without faulty entries. Below we’ve shown how the back office (distribution manager or experienced employee) sees the mobile device of the new employee and can guide him directly in the situation he is in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ubPtQmr3z35a3nhpagajkQ.jpeg" /><figcaption>Experienced employee showing the new employee how the mobile app is used.</figcaption></figure><h4>Add it to your internal mobile apps today</h4><p>GoToAssist Concierge is free. Yes, you read that right. Why? Because we want to know what you think. As Concierge grows, you’ll be able to try new beta features and share feedback on how useful they are. Eventually, some of the beta functionality will be offered as part of a premium Concierge plan. But the free plan will still be free. The free plan includes unlimited users and up to 1,000 support sessions per month. It also provides three application keys, so you can add Concierge to three different mobile apps.</p><p>Learn more and sign up today at <a href="http://live.gotoassist.com/">http://live.gotoassist.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=223956fd7e01" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gotoassist-product-blog/assisting-new-employees-in-the-field-223956fd7e01">Assisting new employees in the field</a> was originally published in <a href="https://medium.com/gotoassist-product-blog">GoToAssist Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Democratizing the Mayday button]]></title>
            <link>https://medium.com/gotoassist-product-blog/democratizing-the-mayday-button-4ebc4a63c00b?source=rss----574d41514608---4</link>
            <guid isPermaLink="false">https://medium.com/p/4ebc4a63c00b</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Jacob de Lichtenberg]]></dc:creator>
            <pubDate>Tue, 23 Feb 2016 16:10:42 GMT</pubDate>
            <atom:updated>2016-03-02T13:30:26.374Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PxzIGNHxaAEkUNJOzo_1Cw.jpeg" /><figcaption>Amazon created a fantastic feature with their MayDay button. Now it is democratized and available for all who would like to give amazing customer service.</figcaption></figure><p>In September 2013, Amazon launched the “Mayday button” on their Kindle Fire tablets, giving customers direct access to tech support with a single tap.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FwwkxgwajCko%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DwwkxgwajCko&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FwwkxgwajCko%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/107f21da3d6207a79f090d6d0e31639e/href">https://medium.com/media/107f21da3d6207a79f090d6d0e31639e/href</a></iframe><p>Even the CEO of Amazon, Jeff Bezos, said in an <a href="http://www.theverge.com/2013/9/25/4766878/jeff-bezos-interview-amazon-kindle-hdx">interview with The Verge</a> that the Mayday button was “<strong>the greatest feature we’ve ever made</strong>.”</p><p>Working with support systems, we were expecting this concept to spread like wildfire. We saw a future where all apps would have such a button, where you could talk directly with customer care. In the “customer-focused future,” shoppers could get their questions answered easily online or on their mobile device, patients could get direct help from their doctors and banking customers could talk to their financial advisor with just a single click.</p><p>None of this happened. Despite Amazon’s success, one-click in-app support never moved beyond Amazon’s premises.</p><p>Therefore, we at Citrix GoToAssist decided to go on a quest to democratize the one-click support button.</p><h3>We’re giving away the one-click support button for free</h3><p>Our first decision was to make the basic functionality free. As the French say about democracy: “Liberté, égalité, fraternité” (i.e., liberty, equality, fraternity). You cannot democratize something if only companies with money can use it. It has to be equal for all. Therefore, we are <a href="https://live.gotoassist.com/">giving it away for free</a>. You can add the one-click support button to your app or your website.</p><p>We call the new product “Concierge” — as in a butler at a hotel. It does the same as the Mayday button:</p><ul><li>You can place the <strong>button in your app</strong></li><li>The customer taps the button to connect to support</li><li>The customer can <strong>see, hear or exchange chat messages </strong>with the support agent</li><li>The support <strong>agent can see </strong>and <strong>draw</strong> on the customer’s screen</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/334/1*YQDPc18WPCDqAV6gyTNFmw.gif" /><figcaption>The democratized on-click button during a help session.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*hA5OfsEPmlP8I-kABaC-Fg.jpeg" /><figcaption>The original Mayday button from Amazon during a help session.</figcaption></figure><h3>Why has it not been democratized before?</h3><p>We think there are several reasons why:</p><h4>Technical reasons</h4><p>Democratizing in-app support is actually quite difficult. We started fresh but soon bumped into many technical challenges. Some of the features, like video communication and voice, come out of the box quite easily using WebRTC technologies. But when you start looking at different versions of iOS, Android and web browsers, it can become quite difficult to deliver a seamless and consistent experience across them all. Since we were committed to the idea, we managed to, but many might have given up along the way.</p><h4>Ability to support this new type of interaction</h4><p>Offering video support can put a unique strain on a support team. Traditionally, support requests have all been taken by phone or chat, and introducing the new dynamic of video might be something organizations are not yet prepared for. But it’s worth the effort. The Amazon Mayday team takes pride in the quality of support they provide, and video adds a new competitive dimension that hasn’t really been seen before.</p><h4>Security reasons</h4><p>There are also a few security concerns, both from end users and organizations alike. For example, allowing the support agent to see the screen of a mobile device or browser window can risk data confidentiality. So to ease these concerns, we built Concierge to use a peer-to-peer connection, and we’ve been working to remove ourselves (GoToAssist) as the middle-man brokering the connection between the end user and support agent. We also restrict screen sharing to just the app the user is requesting support in. And for web sessions, the user can explicitly state what they want to share (full screen, browser window or just a single browser tab).</p><h4>Return on investment</h4><p>Do you track the support calls you receive from your mobile apps? How do you know if your mobile apps are causing you headaches and issues? Exactly. What isn’t measured cannot be improved. If you can’t measure it, how can you justify the ROI of providing Concierge-type functionality to your customers? As a result, we’re giving it away for free — enabling all organizations to provide this innovative style of support, measure what might currently be ignored and witness first-hand how it can set you apart from the competition.</p><h4>How can we give it away for free?</h4><p>We are giving Concierge away for free for a couple of reasons: First of all, we would like to learn. We would like to see how users use the product. Secondly, Citrix GoToAssist is an IT support product targeted at providing customer support for computer users. At some point, we hope to integrate Concierge into GoToAssist. We also hope that the product becomes so popular that some customers might request very specific features, such as very complex reports or integrations into ERP systems. The basic functionality of Concierge is free. At some point we will most likely integrate into other Citrix products to generate revenue in packages.</p><h3>How can I be part the Mayday democracy?</h3><p>The new democracy is called Concierge, and you can join us in our quest for providing amazing customer service here: <br><a href="https://live.gotoassist.com/signup">https://live.gotoassist.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ebc4a63c00b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gotoassist-product-blog/democratizing-the-mayday-button-4ebc4a63c00b">Democratizing the Mayday button</a> was originally published in <a href="https://medium.com/gotoassist-product-blog">GoToAssist Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A method to improve your websites’ conversion rate. For free.]]></title>
            <link>https://medium.com/gotoassist-product-blog/a-method-to-improve-your-websites-conversion-rates-for-free-6babdb5f6dde?source=rss----574d41514608---4</link>
            <guid isPermaLink="false">https://medium.com/p/6babdb5f6dde</guid>
            <category><![CDATA[checkout]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[conversion-rate]]></category>
            <dc:creator><![CDATA[Jacob de Lichtenberg]]></dc:creator>
            <pubDate>Mon, 15 Feb 2016 07:39:53 GMT</pubDate>
            <atom:updated>2016-03-02T13:31:26.621Z</atom:updated>
            <content:encoded><![CDATA[<p>There are many ways to <a href="https://blog.kissmetrics.com/40-checkout-page-strategies/">increase conversion rates</a> in your web store. You could improve website usability, create additional features or add discount/rewards, all of which are time consuming and costly ways to improve your website. And after these changes are done, you can split test to check for conversion improvement. You’ll get data, but if you are not communicating with customers, you’ll never know the real reason why they may have left your site.</p><p>Sometimes the reason for leaving is simply because there was a problem in the checkout flow. Maybe the website would not accept the customer’s address, credit card or a foreign character. (Being from Denmark, I have tried many times that the Ø in my address does not work.) The customer then leaves because of this problem, and you have no idea why. Sometimes it is the customer’s fault; sometimes it’s the website’s. But you don’t know.</p><p>We would like to offer you a cost-free feature that could solve any problem the customer might have with using your website. It will also give you a better understanding of why they might be leaving.</p><h4>What is the solution?</h4><p><strong>Live chat + Screen share</strong>: The solution is to give customers direct access to your support team AND give your support agents access to see the customers’ problems. You probably know the first option, live chat, which companies like Intercom, LivePerson, Zopim, Boldchat, and Olark provide. These are great services for product questions, but when it comes to understanding a problem that a customer is experiencing on your website, it can still be very difficult to grasp the situation.</p><p>That is where <strong>Concierge </strong>comes in. Concierge is a new, free product that allows you to not only chat live with customers but also see their screen. <br>In the example below, a customer is having problems with payment. He is trying to complete the order, but his credit card is not accepted. This might be a situation where the customer just moves to another store in annoyance. But in this example, the customer clicks the live support feature and says: “Your payment system doesn’t seem to work.” Then the support agent asks him to show his screen:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wpvI4eeDf80H6FJA3EB_AA.jpeg" /><figcaption>A customer is having a problem in the checkout page and asks for help.</figcaption></figure><p>Normally, a support agent would have a hard time knowing what the problem is. But with Concierge, he is able to see the customer’s screen and recognize that the numbers for the month and year have been accidentally switched. He can now guide the customer to finish his purchase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vi04J3waaOI_cx2ZKedauQ.jpeg" /><figcaption>A screen dump from inside Concierge: The support agents or website owner can chat with the customer while seeing the customer’s screen.</figcaption></figure><p>These pictures are actual screenshots of Concierge. In this last screenshot, the support agent can see exactly what the customer sees and what he does.</p><h4>Is it difficult to try?</h4><p>Adding this functionality to your website is quite easy. First you sign up, then you just need to copy-paste the following lines of code in your HTML file:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7e0816117d66394239d385d8bb53e08d/href">https://medium.com/media/7e0816117d66394239d385d8bb53e08d/href</a></iframe><p>Replace the XXX-xxx in the code above with a key from <a href="https://live.gotoassist.com/dashboard/keys">https://live.gotoassist.com/dashboard/keys</a> (to create a key press “+”. Insert this).</p><p>When the code is added, a button will appear, and if you are signed into Concierge, you will be able to get requests directly. Concierge is white label, so you can create any type of button and text you would like. In the code above, a green default button will be added saying “Chat with us”.</p><h4>How is it free?</h4><p>It might sound like madness to give away a service that other companies are making money on and add new screen-sharing features. So why are we giving it away for free?</p><p>First of all, we at Citrix GoToAssist come from the IT support world, and we have been doing screen sharing for many years. This kind of technology is old for us . But with new technologies, we really want to learn first and try to make money later. So, we have decided to give the product away free in the beginning— in the hope that the first users will provide us some feedback. The basic functionality, like website chat, website audio (you can also talk to the customer) and screen sharing is free. Later, we believe that some big customers will love the product so much that they will ask for integrations or other features, and at that point we might ask for payment for these new features.</p><p>If you would like to improve your conversation rate by giving customers live help AND help your own support agents better understand customer problems, try Concierge out. It’s free.</p><p>Go to <a href="http://live.gotoassist.com/"><strong>http://live.gotoassist.com/</strong></a> to sign up and start improving you conversion rates, while understanding and helping your customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6babdb5f6dde" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gotoassist-product-blog/a-method-to-improve-your-websites-conversion-rates-for-free-6babdb5f6dde">A method to improve your websites’ conversion rate. For free.</a> was originally published in <a href="https://medium.com/gotoassist-product-blog">GoToAssist Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Keeping a startup’s first customers excited]]></title>
            <link>https://medium.com/gotoassist-product-blog/keeping-a-startup-s-first-customers-excited-e50a98033db7?source=rss----574d41514608---4</link>
            <guid isPermaLink="false">https://medium.com/p/e50a98033db7</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup-marketing]]></category>
            <dc:creator><![CDATA[Jacob de Lichtenberg]]></dc:creator>
            <pubDate>Fri, 05 Feb 2016 15:08:32 GMT</pubDate>
            <atom:updated>2016-03-02T13:32:33.121Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9jxrpXGnpm1LpzJn1P6jYg.jpeg" /><figcaption>Fleye is an exciting new product: a drone that can fly safely in cities. To keep Fleye’s first customers excited, we are providing a free solution to create the best possible on boarding experience and help new customers get going.</figcaption></figure><p>Going from making a prototype to shipping the product to getting your first customers is an exciting time for most startups. The first customers — the early adopters and innovators — are often a mixture of very different personalities and competencies. Their responses often determine whether the product will grow and bring the next wave of customers (the majorities) on board, thereby making the startup a commercial success. So ensuring the first customers are excited is important.</p><h4>Helping customers get started</h4><p>Depending on your product, the early adopters are most interested during the purchase phase, but when the product arrives and onboarding starts, they meet some challenges. Something might be missing, or a setting might be wrong, hindering the product. Making sure everything is set up right might be fun for some customers, but for most, it is just an obstacle in the way.</p><p>As a startup, you should never forget to onboard your customers and guide them until they are fully up to speed. This is a critical moment in a startup’s customer life cycle, so we spend a lot of time thinking about the perfect onboarding experience. In our view, the ideal scenario is if your best friend helps you get started, ensuring everything works smoothly. We really wanted startups to be able to provide the same “best friend” onboarding experience, so we got to work:</p><h4>The “best friend” experience</h4><p>Let us imagine an example: You buy a new product like the Fleye — a safe flying drone:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*Gel0GusyjlS1DDMYyC-jww.jpeg" /></figure><p>Before you can start flying, you need to put it together or adjust something in the setup:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*fYrEBqb6GgHc5jOrwBKwLA.gif" /><figcaption>When getting started with a new product, Concierge can help through a “best friend” experience that lets startups get their customers up to speed, so they keep staying excited.</figcaption></figure><p>At this moment, you might be uncertain about what to do. This is when the best friend’s help is needed. The friend would stand next to you and see exactly what you are seeing, assisting you as you go. <br>But what if no is around to help? <br>We wanted to recreate this “best friend” experience for people who were not in the same room, and we came up with a free way to do it. With the flying app already open, you simply tap a single button, which connects you to someone who can help and shares your camera. You can then show what you are doing:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fNJ5qOypWG74JzN-knoEcQ.gif" /><figcaption>By using the app for the product, the startup can see exactly what the new customer’s challenge is.</figcaption></figure><p>Your friend on the other end can then see exactly what is going on or what might be wrong:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6wUeV039EfPz--Q9UhCDkA.gif" /><figcaption>The Startup (here represented by me — it is a screen dump) can help the customer directly.</figcaption></figure><p>By talking directly with you and seeing the same thing, your helper can get you up and running and keep you excited about the product. Which makes for a much friendlier customer experience.</p><h3>Its free — for the cost of learning</h3><blockquote>The best friend solution is called Concierge, and we are giving it away <strong>free</strong>.</blockquote><p>Yes, it is true. The best friend solution is called Concierge, and we are giving it away <strong>free</strong>. And that’s for a couple of reasons: First, we would like to learn. We want to see how people use the product. Therefore, the current functionality is free. Second, the product and its technology are entirely new for us. We are still working on improvements. The product works, but there might be small bits that are not super smooth yet. As you can tell from the picture above, when you turn the phone to landscape, you still see the screen vertically from the remote expert’s point of view. We are working on things like this, and they will gradually improve.</p><p>So what would we like in return for giving a free product away? <strong>Feedback</strong>. We want to know any challenges you might have and how you think we could make it even better.</p><p>If you want to use the product for free, sign up at <a href="https://live.gotoassist.com/signup"><strong>https://live.gotoassist.com/</strong></a></p><p>If you have a technical background, you can read the documentation for our app and web SDK here: <a href="https://live.gotoassist.com/explore-sdk">https://live.gotoassist.com/explore-sdk</a></p><p>Good luck with your customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e50a98033db7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gotoassist-product-blog/keeping-a-startup-s-first-customers-excited-e50a98033db7">Keeping a startup’s first customers excited</a> was originally published in <a href="https://medium.com/gotoassist-product-blog">GoToAssist Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A free tool for lean startup]]></title>
            <link>https://medium.com/gotoassist-product-blog/a-free-tool-for-lean-startup-e5048871821d?source=rss----574d41514608---4</link>
            <guid isPermaLink="false">https://medium.com/p/e5048871821d</guid>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[customer-service]]></category>
            <dc:creator><![CDATA[Jacob de Lichtenberg]]></dc:creator>
            <pubDate>Thu, 28 Jan 2016 13:52:09 GMT</pubDate>
            <atom:updated>2016-03-02T13:33:16.260Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9FDEJISHQdSwKwgSCxqYYw.jpeg" /><figcaption><em>The lean startup learning cycle as described by Boomtown Accelerator</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/230/1*8Rl7deXNQqNwsoIY0Q9CeQ.jpeg" /></figure><p>In his New York Times bestseller “The Lean Startup,” Eric Ries describes his method of entrepreneurship and how to create a successful startup. The method he presents is focused on building a minimal part of your product idea, which you then give to customers to get feedback and learn from. By doing so, you can avoid a typical startup pitfall: Startups often begin with an idea for a product that they think people want. They then spend months or years perfecting that product without ever showing it to the prospective customer. When they fail to reach broad uptake, it is often because they never spoke to prospective customers and determined whether or not their product idea was interesting.</p><p>The better approach is to build something simple and get feedback from customers fast. This is what Eric Ries calls the <strong>Build-Measure-Learn</strong> <strong>principle</strong>. It stems partly from his own experiences with IMVU.com, where his team developed a rough (but not complete) version of an instant messaging + 3D avatars product and released it full of bugs (worrying all the while about how customers would react to all the bugs). But after the launch, there were no customer reactions. They didn’t get the thousands of downloads they expected, and they didn’t know why. Their solution was to go into direct dialogue with the customers who were using the product — to understand what customers thought of it and how they could pivot the product to make it more attractive for the users. After that, it became a huge success.</p><h3><strong>Our tool to learn from customers</strong></h3><p>I have been very inspired by the lean startup methodology, and since we are working with SaaS products, it is extremely important for us to get input directly from customers in the context they are using the product. Therefore, we developed a product just for that, which we call Concierge. Let’s give a couple of thought examples:</p><h4><strong>The movie app</strong></h4><p>Imagine you have developed a movie app that shows film ratings and lets you connect to other friends to see their own scores for the movies. As a good lean startup enthusiast, you develop a minimal viable product and put it out to customers. You get a couple of downloads. But you do not know exactly what features you should develop next in order to attract new customers, keep your current customers and make them promoters for the product.</p><p>We developed Concierge so you can easily talk to customers. You basically drop a couple lines of code in the app, and you then have a direct communication channel. See the screen comparison below, where the feedback options were added on the right:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FmenTjgUzf8gYFQW07E76g.png" /><figcaption>An example of a new app where a startup can get direct input and learn from users</figcaption></figure><p>As you can see, you can both chat and talk directly with the customer. From your point of view, it would look something like this if a customer reached out to you:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h2_6v6VEzohpn57Zy8XoZQ.gif" /><figcaption>Concierge that lets you communicate with customers directly in your app. The most interesting aspect is the next picture, where you can actually see the users mobile screen.</figcaption></figure><p>On the left is an inbox, where you can pick up calls and talk directly with the customer. Here you can get valuable feedback. Maybe customers would like to click a “I want to watch this movie” button and have the app match them with friends who are also interested. Explaining this with just words can sometimes be very difficult for customers. It is often easier if you can actually see what is happening on the customer’s mobile device. So we added the option to remotely view the customer’s screen and draw on it. See below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YzPAAod-Ckgi8rvBhfnG5A.gif" /><figcaption>A screen dump of a session, where I can understand the customer’s suggestion and at the same time explain how the app works by drawing on the user’s screen. On the left is my iPhone. On the right: my Chrome browser, from where I can talk directly to the user. The user can see a video feed of me (optional), but I cannot see the user.</figcaption></figure><p>Here I am talking directly to the customer. We let you turn on the camera to make a more personal connection … but you do not have to do this.<br>Concierge is a great tool if you would like to get feedback for your mobile app. You actually only have to add the following code to your mobile project:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5566acaf9f3b0788a85ed590890c2eb0/href">https://medium.com/media/5566acaf9f3b0788a85ed590890c2eb0/href</a></iframe><h4>The travel startup</h4><p>Most companies don’t start with an app (even though that is increasingly the case), but almost all companies have a website. Our next thought example is a small startup selling travel packages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*CquPw0vz8lQ3hK9S3zO88Q.jpeg" /></figure><p>On the left you see a Danish travel agency called “Victor’s Grandma.” A trip to Ecuador costs around 6000 dollars from Denmark, so if a customer is unsure in any way, the small startup would like to know exactly what the customer is thinking and where their uncertainty is. By adding a very simple snippet of Concierge code to your website, you can place a button on your page that gives you the opportunity to talk directly with customers. That way, you can make sure they buy your travel package. <br>Again, getting in direct contact with your customers is very easy — just add the following lines to your HTML code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ed14b536f4bc5ce6dde23b054d13ee6a/href">https://medium.com/media/ed14b536f4bc5ce6dde23b054d13ee6a/href</a></iframe><h3>It’s free</h3><p>The technologies in Concierge are new for us in GoToAssist. With new technologies, we really want to learn first and try to make money later. So, we have decided to give the product away free to the first 500 customers — in the hope that they will provide feedback. The basic functionality, like website chat, website audio (you can also talk to the customer) and screen sharing, is free for everyone. But we believe that some big customers will love the product so much that they will ask for integrations or other features, and at that point we will ask for payment. For most startups, Concierge covers everything they need. In the free plan you’ll be able to host up to 1000 monthly customer sessions. If you have more than that number a month, you can always upgrade to a paid plan. But we haven’t met a startup yet that talks to more than 1000 customers every month. So for all intents and purposes, it’s free for startups.</p><h3>How do I get started?</h3><p>If you would like to read learn more or sign up, check out the GoToAssist website: <a href="https://www.gotoassist.com/remote-support/anytime/concierge">https://www.gotoassist.com/remote-support/anytime/concierge</a></p><p><strong>Good luck with your lean startup!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5048871821d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gotoassist-product-blog/a-free-tool-for-lean-startup-e5048871821d">A free tool for lean startup</a> was originally published in <a href="https://medium.com/gotoassist-product-blog">GoToAssist Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Sketch Symbols to Create Material Quick-Guides]]></title>
            <link>https://medium.com/gotoassist-product-blog/using-sketch-symbols-to-create-quick-guides-db3355cc7f75?source=rss----574d41514608---4</link>
            <guid isPermaLink="false">https://medium.com/p/db3355cc7f75</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Lloyd Humphreys]]></dc:creator>
            <pubDate>Mon, 19 Oct 2015 12:40:18 GMT</pubDate>
            <atom:updated>2015-10-19T13:30:50.602Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*tcTMXLeTQ-aFXc3KZ7sKOw.png" /><figcaption>On the left, my quick guides. On the right, Google’s Material guidelines</figcaption></figure><p>To me, the best thing about Sketch is the speed with which I can design something. I’ve been working with Material recently, and Google have laid out some great guidelines.</p><p>I often find myself creating quick-boxes to snap align stuff to, especially when designing for Material. We’ve all done it — but after discussing with some friends, I figured I’d write this because none had thought of doing it quite like this. After more tinkering, I created some fancier guides and made them Symbols so that I could more quickly drop them into whatever I’m working on.</p><h4>I never actually edit these Symbols, they’re purely guides.</h4><p>I just draw on top of them, or drop them in once I’m done roughing to get the alignments right. When done, delete symbols (or drop them into a group and hide it). Quick, dirty, easy!</p><p>My most commonly used quick-guide Symbol is the list item. I simply offset each to create the proper height, then middle align everything to that symbol.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*MLPVgOUd1T8NUmb9IvFXnA.png" /><figcaption>Offset cell heights</figcaption></figure><p>Below is an example of when I’ve given myself little hints as to how they should be used, reinforcing the correct metrics without having to reference back to the Material guidelines. I’m often jumping around between iOS, web, Android — this comes in very useful!</p><p>The red line is so I can quickly align text by holding alt+nudging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*0C69D9EpOyvqJbln_kb-cw.gif" /><figcaption>Notes within a quick-guide: With these headings, the top margin is ignored if it’s the first thing on the page, and only taken into account if it’s separating two groups.</figcaption></figure><p>The numbers aren’t really necessary, but I like to have them in there as reminders for when I’m doing math in the Size/Position fields.</p><p>I’ve created a few more of these across various documents when I’m working on something I know I’ll need to reproduce fairly often. I’m not a big fan of creating Symbols for UI elements, because I know I’ll rip them apart, change/delete stuff and then realise later that I’ve screwed up a design on a different artboard — I’ve done that enough that I’ve lost confidence in using them as such. This isn’t perfect. It’s just a compromise so I can move quickly.</p><p><a href="https://drive.google.com/file/d/0B_PLEYAb7eHfSVEzVGFFUzI1UU0/view?usp=sharing">Download the Sketch file to take a closer look!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db3355cc7f75" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gotoassist-product-blog/using-sketch-symbols-to-create-quick-guides-db3355cc7f75">Using Sketch Symbols to Create Material Quick-Guides</a> was originally published in <a href="https://medium.com/gotoassist-product-blog">GoToAssist Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microteams for Microservices]]></title>
            <link>https://medium.com/gotoassist-product-blog/microteams-for-microservices-683c396901d9?source=rss----574d41514608---4</link>
            <guid isPermaLink="false">https://medium.com/p/683c396901d9</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Jeremy Wells]]></dc:creator>
            <pubDate>Thu, 13 Aug 2015 10:57:51 GMT</pubDate>
            <atom:updated>2015-08-13T10:57:51.627Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l65hUU7XZgsDexg1INvOig.jpeg" /></figure><p>Over the course of this year the GoToAssist team in Copenhagen and Karlsruhe has been trying out a cross functional micro-team development process. This post explains what we were doing, what changed, and how it’s working for us now.</p><p>At the beginning of 2015 we had a completely new team working on GoToAssist Service Desk and related projects. We were in a new location, co-located and with mostly new members. Yet we were still struggling with the processes that were in place, designed for a small team of remote workers with a long relationship.</p><p>Something needed to change, and we were not sure what. So the first thing we did was to remove nearly all the processes. We had one large standup every day, and a subset of the team groomed stories and tasks. We let the chaos begin.</p><blockquote>It was a lot easier to be an expert on chaos […] mostly because it made really good patterns that you could put on a t-shirt.</blockquote><blockquote>Terry Pratchett</blockquote><h3>Architecture</h3><p>At the same time we were discussing new ideas for future architecture. Our new technical lead, Christian, had exciting ideas for a message driven microservices architecture that the new team had bought into. We were talking about isolated services, about not being concerned how each service was implemented so long as we knew the interface. Different engineering groups in the company have their technology preferences, and the new architecture lets us choose the technology, the tools, the method for each service.</p><p>The seeds of where we could go with processes were already forming in my mind.</p><h3>Split by language</h3><blockquote>“I wouldn’t say we went into this new process thinking it would work.”</blockquote><p>When our lack of process became too much for the team and management to bear, we decided to start running sprints again. We knew that a team of nearly 20 was too large. Our first attempt at a split was along domain lines. We had a team of Rails engineers, front-end engineers, iOS engineers, and we were to let the designers continue with their own processes as they were already working well.</p><p>So we created 3 backlogs, had 3 sprint planning sessions, and kept the giant standup.</p><p>I wouldn’t say we went into this new process thinking it would work. We knew the disadvantages of segregation. Something had to be done, and we couldn’t see clearly how to split into smaller teams. At that time we were mostly working on one project with some major features in the pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/237/1*oFneSMRXAVvlkyMgatiPdA.jpeg" /></figure><p>The cracks didn’t take long to appear. We’re still dealing with the fallout of this reorganisation <em>months after we stopped using it</em>. Features fell between the responsibilities of each team, and priorities could not match up.</p><p>We fell back into chaos, or should I say anarchy. It seemed to work better. However, during this chaos two things happened that set us on a new course.</p><h3>Hacking</h3><blockquote>write (a program) in a skilful or clever way</blockquote><p>We needed to deliver a concept feature in a short amount of time to evaluate it’s market potential. To achieve this, an internal team was formed that was cross-functional, including a project manager, designer, iOS engineer, QA engineer, front-end engineer and backend engineer. I wasn’t part of this team, but their success and the way that was achieved really solidified prior thoughts about what we should be doing. This team moved to sit together, and they pretty much excluded all outside influence in order to achieve their goal.</p><p>Then we had an annual company wide event called Hack Week. <a href="https://medium.com/gotoassist-product-blog/planning-ahead-taking-a-prototype-to-production-adcb247d5d43">I’ve written about Hack Week before</a>. We had a retrospective with the whole team after Hack Week where we discussed our feelings on how it went. The most obvious takeaway from that was how much satisfaction everyone got from working in a small team that included all the resources they needed.</p><blockquote>“Hack week? Are you all going horse riding?” — My wife</blockquote><h3>Split by feature</h3><p>It might seem obvious to split up into cross-functional teams that tackle a feature at a time. It’s often been at the back of my mind as an interesting way to work. However, it does not come that naturally. I’m not sure we could have done it sooner than we did; it required a level of comfort in the team, and features that could be worked on separately.</p><p>Working on a new architecture has helped a great deal. There’s a really good feeling of co-evolution between the technology architecture and the process.</p><p>Externally we have one process now, but internally each team is very different. The teams themselves can decide how to organise. My team has only 4 people, and we sit together. There’s not much need for much formal process, and our stand-ups are discussions. We know what we’re doing.</p><p>Another team whose stand-ups I attend could not be more different, and yet it also works well. It is a larger team with members in two offices, so meetings always involve a remote element. They have adopted a very strict scrum process, and they have a strong scrum master (Stephanie) who keeps the team operating smoothly.</p><p>The large team had an offsite in Berlin for several days, with everyone traveling to meet up and plan together, to get the momentum going.</p><p>My team had an offsite at my house where we had cream teas and drank beer.</p><h3>Werewolves</h3><p>Our new way of working is not a silver bullet. Success is still to be decided. It feels like we’re moving forward now, but there have been problems, and there will be more.</p><p>First of all, it took perseverance. Not everybody was happy when we split along these lines because they lost a level of knowledge into what everyone was doing. People liked the big stand-up with 20 people, it was fun. We’ve started a weekly catchup breakfast-meeting for the whole team, to try and recapture that.</p><p>In the beginning some people had too many responsibilities and were split over teams. We only have one manual tester, and two test automation engineers, and so we did have to rethink our roles a little. We’ve now settled that each person should be involved in no more than two teams, and preferably mainly working in just one.</p><p>I would like to see the current teams finish their work and then have us split and reform around new features. That hasn’t happened yet, and I’m sure that is going to be hard the first time. Maybe we’ll have to force that sooner than later, or maybe we’ll wait until it descends once more into chaos.</p><h3>Conclusion</h3><p>I believe that people are happier when they have some self-determination. We’ve folded that into our architecture — you can write your services in whatever language you like so long as it interfaces with the rest of the system. If it does not work out, each component part is small enough that we can deal with it.</p><p>Now we’ve folded the same principle into our development process. Your team can decide how it works, so long as it interfaces with the larger group. If it doesn’t work out; we can change the team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=683c396901d9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gotoassist-product-blog/microteams-for-microservices-683c396901d9">Microteams for Microservices</a> was originally published in <a href="https://medium.com/gotoassist-product-blog">GoToAssist Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Planning ahead: taking a prototype to production]]></title>
            <link>https://medium.com/gotoassist-product-blog/planning-ahead-taking-a-prototype-to-production-adcb247d5d43?source=rss----574d41514608---4</link>
            <guid isPermaLink="false">https://medium.com/p/adcb247d5d43</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[Jeremy Wells]]></dc:creator>
            <pubDate>Tue, 04 Aug 2015 14:13:40 GMT</pubDate>
            <atom:updated>2015-08-05T07:19:33.814Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N3vLRC0lkzj0XdJMSLz66g.png" /></figure><p>In May this year we held our annual hack week. This is an event where every member of the company can participate in building and presenting new ideas, big and small. It’s a great event and an opportunity to work outside the normal environment, with new people and new ideas.</p><p>This year I teamed up with a designer and a Rails engineer to create a project called <em>Superhero</em>. We prototyped it rapidly in Rails and ReactJS. The project won the internal “Best New Standalone Product” award, and so we’re now working to bring the idea to a larger audience. I won’t discuss the idea itself — this article is about how we hacked together a prototype in a way that allows for later progress.</p><h3>Technology Stack</h3><p>When it comes to choosing the technology for a hack week project, it is tempting to use the time to learn new things. That’s fine — but our goal was to have an idea up and running at the end of the week, not experiment with new technologies. As I’ve been working with NodeJS recently, my first thought was to use that as the platform. This made sense from the feature view as we knew that the product would benefit from realtime communications.</p><p>However, we knew we only had a week, and when demoing time is accounted for it’s really only 4 days. Given our skill set and our goals, it was easier to start with Rails. My requirement was that we could grow it later if we needed to.</p><p>So this is what we built on:</p><ul><li>Rails 4.2</li><li>MySQL</li><li>ReactJS via sprockets</li><li>websocket-rails</li></ul><p>We had quickly realised that to build fast, we needed to use what we knew and what we had. We knew Rails, we knew sprockets, and we had MySQL installed for other projects. <em>We wouldn’t have used any of these had we planned up front.</em></p><h3>Interface points</h3><p>I’ve spent much of my time recently designing and constructing services in a micro-service infrastructure. When you’re writing services you think about the interfaces a lot. Messages get passed around, and conventions become important.</p><p>When you write a monolithic application you don’t need to think about this sort of message passing and convention. You can make function calls any way you like and it’s easy to change the code later on. If you take this approach then adding features is easier for quite a while, but it will get harder and maintenance overhead will increase. At some point you might like to split the application up, and move in the micro-services direction. I’ve had experience with this; it’ll be a hard job.</p><p>As soon as we started with this project I was thinking about those interface points. How could we structure it in a way that would keep us iterating on a monolithic application for a week, but be able to break it down quickly if we took it further?</p><h3>Events</h3><p>From the outset, we wanted to make the user interface reactive. Every time a change occurred, events would be pushed via websockets. We started with a very simple pattern:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e9156ec714fdbf6cd55c1d047c78b183/href">https://medium.com/media/e9156ec714fdbf6cd55c1d047c78b183/href</a></iframe><p>Considering our deadline and the scope of our application, this seemed fine. But then we wanted to send emails too:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1f4fc54a59c131d3bd255eed805885cb/href">https://medium.com/media/1f4fc54a59c131d3bd255eed805885cb/href</a></iframe><p>Now insert your favourite refactoring comments here. Those things shouldn’t be in the controller, they should be in the model / a module / a service object.</p><h3>Shh…</h3><p>Recently I’ve been using the <a href="https://github.com/krisleech/wisper">wisper gem</a> in Ruby programs. It’s a really simple event system within the application. There are various ways to modularise a Rails application, with differences in complexity and testability. Starting up front with an event-based modularisation means that progressing to a services architecture is easier.</p><p>Here is a simple example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cb428fb0cbbe9558d70db0f1425e5f87/href">https://medium.com/media/cb428fb0cbbe9558d70db0f1425e5f87/href</a></iframe><p>Okay, so it’s not the best code in the world; it was still a hack week project. But now by following this pattern with every controller action, we’ve created a separation that allows for adding new subscribers without touching any other code, just like micro services.</p><h3>Background</h3><p>You’ve probably spotted that email being sent synchronously with the web request. Indeed we had several things going on that should happen in the background. For the purposes of our demo they were fine. We needed to address them straight after.</p><p>You might also have noticed that publishing happens with IDs, not objects. Wisper would support sending the object, but an asynchronous call would need to send primitives only. Sending the ID isn’t the best option, as it will require the receiving service to either connect to the database, or request the object via the API that we were exposing. A better option might be to serialize the object. However, this is a tradeoff of speed vs flexibility.</p><p>I installed the <a href="https://github.com/krisleech/wisper-sidekiq">wisper-sidekiq</a> gem. Now the subscribers can run in the background just by changing the subscription call:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/671987cd967c2ed34adbe2af29ba97d8/href">https://medium.com/media/671987cd967c2ed34adbe2af29ba97d8/href</a></iframe><p>Once again we get things done by only changing the subscribing service.</p><h3>Asset Pipeline</h3><p>I’ve never been a huge fan of sprockets, the default Rails asset system. It gets hard to understand what is happening when JavaScript files can be loaded from anywhere to appear in a combined file. However, it was very quick to get up and running with the <a href="https://github.com/reactjs/react-rails">react-rails</a> and <a href="https://github.com/TannerRogalsky/sprockets-es6">sprockets-es6</a> gems.</p><p>One of the first tasks I undertook after the hack week was to extract the JavaScript client code out of the Rails asset pipeline and have it compiled separately using webpack. This meant replacing all the global variables with requires:</p><pre>var { PageHeader, Grid, Row, Col, Navbar, Nav, NavItem, Badge, Glyphicon } = ReactBootstrap;</pre><p>Becomes:</p><pre>var React = require(&#39;react&#39;);<br>var { PageHeader, Grid, Row, Col, Navbar, Nav, NavItem, Badge, Glyphicon } = require(&#39;react-bootstrap&#39;);</pre><p>We had missed so many of these setup lines, which exposes the trouble with Sprockets and global variables. Had the file loading order changed, then things might have broken in unpredictable and hard to debug ways.</p><h3>Next steps</h3><p>Right now the application will be capable of scaling to a small number of real users. We’ll concentrate on features rather than improving its architecture. If it grows, then the next places to scale will be the search engine and the websocket notifications.</p><p>For search we’re using MySQL text queries. To upgrade we can drop in a new subscriber than publishes items to an external search service. That way we avoid changing the models and controllers.</p><p>Notifications can be solved in exactly the same way. A new subscriber would be able to publish to an external pub/sub service, like <a href="http://faye.jcoglan.com/">Faye</a>.</p><p>For each of these tasks there are various gems and existing conventions that provide this functionality. However, that would involve adding to the existing model and controller code, and we would end up with a tightly coupled system.</p><h3>Conclusion</h3><p>We’ve shown that we can create a monolithic application that behaves more like a set of micro-services. There are no model callbacks or complicated controller behaviour. When and if we move code out of the application into separately running processes there will be no big refactor.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adcb247d5d43" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gotoassist-product-blog/planning-ahead-taking-a-prototype-to-production-adcb247d5d43">Planning ahead: taking a prototype to production</a> was originally published in <a href="https://medium.com/gotoassist-product-blog">GoToAssist Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hacking your way into the future]]></title>
            <link>https://medium.com/gotoassist-product-blog/how-letting-people-do-whatever-they-want-can-create-entirely-new-business-opportunities-and-why-41011e680bb8?source=rss----574d41514608---4</link>
            <guid isPermaLink="false">https://medium.com/p/41011e680bb8</guid>
            <category><![CDATA[business-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[Jacob de Lichtenberg]]></dc:creator>
            <pubDate>Mon, 03 Aug 2015 12:50:30 GMT</pubDate>
            <atom:updated>2015-08-05T05:44:31.262Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ogxU4kQMfz7FDEBlHKHIpQ.jpeg" /></figure><p>Letting employees do whatever they want can create entirely new business opportunities — here’s how to avoid the pitfalls</p><p>It all sounds so simple: Be innovative and start doing the next big thing. But doing something new is often killed by the current business — before it even starts. In this article, we will look at how attempts to hack into the future can both fail and succeed.</p><h3>The wild west of development opportunities</h3><p>It is easy to understand why some industries become obsolete. For example, going from physical to digital photography made Kodak’s film market disappear. Kodak had the skills, resources, and network to conquer this market — but they didn’t. Nothing new in this, but the challenge remains the same for many large organizations in changing markets. How do you create the new while still running your current business?</p><p>One way is to look to the employees for solutions. When people are recruited for a company, you often hear about the 20% rule, where people are allowed to use 20% of their time on whatever they like in order to come up with something new. Often however, the 20% isn’t as free as initially anticipated: you have to apply for the projects you would like to do in this time, and the projects have to be approved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*Fm0D7sGtYJxQtqF37yA-RA.jpeg" /></figure><p>At Citrix, we do not have a 20% rule. Instead, we have <strong>Hack Week</strong>: Once a year, we create the wild west for five days. There are basically no rules for what you do during Hack Week. Leadership gives some ideas for direction, but for the most part people just do whatever they find interesting. The only requirement is that you present what you have done on the last day.</p><p>All kinds of office norms disappear: there are meetings, computers and people everywhere. Weird computer chips are set up in all rooms, toy cars drive around the office, groups compete for talent with breakfast and snack bounties — everybody is working hard on an idea they’re passionate about. Not far from the Mutiny environment in Halt and Catch Fire.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*oMO7QNsJ3v9sZnRt3nGvBA.jpeg" /><figcaption>Mutiny in Halt and Catch Fire. Somewhat similar to the Copenhagen Office during Hack Week. With less showing underwear, though.</figcaption></figure><p>Like Mutiny, this chaos actually creates a lot of ideas, which are developed into something demo-able.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qVZJtGNRsIcz8bUlq8Gb7Q.png" /><figcaption>Younes programmed a mobile device to track points and overlay static annotations</figcaption></figure><p>Friday is the demo day for Hack Week. It is a bit overwhelming to see 50 different hacks being presented in four hours, but the presentations and hacks keep interest with their creativity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vgcWldxDnfp-WvOY_yQ2mw.png" /><figcaption>Tobias put a raspberry pi onto a toy car to accept commands from his Android device</figcaption></figure><p>Everything from large business concepts to actual code are shown during the presentations. The presentations range from how to use tools in developing products, to add-ons to current products, to new standalone, BIG ideas. The big ideas might be something entirely different from Citrix’s current interests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gYSssEWb8bp4vthT69_4FA.png" /><figcaption>Marco and Stephanie presented an innovative tool for interactive presentations</figcaption></figure><h3>Hack Week hangover</h3><p>The questions that is far too often not asked is: <em>What happens after Hack Week</em>? What happens when everyone goes back to their daily work?</p><p><strong>Hacks on current products</strong>: Improvements to current products are the easy part. If a project from Hack Week fits into a current product, often the new feature finds its way into the product naturally. The idea lives happily ever after.</p><p><strong>Totally out-there ideas</strong>: Ideas where the employees have absolutely no knowledge about the business are almost always discarded if they do not show a gigantic potential. When someone suggest to make toys or washing machines, this is probably better suited to a startup or company with industry experience.</p><p><strong>New standalone ideas</strong>: The most interesting and challenging ideas are the brand-new ideas where the company has some knowledge about the industry and can envision a path for the product to succeed. This is also where most companies fail. Let’s explore why these ideas die so often:</p><h3>How to kill ideas</h3><p>When you have an idea for a new standalone product, coming from an event like Hack Week, companies are often accidental-experts at killing the ideas. Here are the main causes:</p><h4>Starved to death</h4><p>The problem is when you return to your normal work after Hack Week, you’ve got a mountain of daily tasks to get back to. The project creators are typically busy and stressed. If their idea is just a little uncertain, they will not have much time to develop the idea unless a top manager (or product owner) finds it interesting. The idea starves to death, as people are no longer working on it.</p><h4><strong>Processed to death</strong></h4><p>Some organizations set up a stage gate model in order to only let the best ideas proceed. The problem with this is that stage gate models are in nature about killing “bad” ideas, because it is very difficult to assess ideas at this early stage. And it becomes even worse when companies add this dangerous ingredient to the mix: middle-managers with no budget for innovation. These managers will sit in an innovation board because they have to, and their personal purpose is to look good in eyes of other managers. Admitting that you do not really know much about a product idea or suggested industry will basically never happen. It is much better to talk from your gut feeling about everything that is wrong. And this becomes a very effective way of killing ideas.</p><h4><strong>Penny-pinched to death</strong></h4><p>Creating something new takes time, manpower, and therefore, money. If it is possible to get any budget for new things, you have to go through a long process of applying for funds. The problem is that you often have to show a good version of a product or idea, and that takes time to create. Time you have not received funding for yet. And while you are working without funding, you are probably not moving fast enough, you’re losing interest from stakeholders, and every day that goes by is a day someone else outside the company could go to market first.</p><h3>What works for us</h3><p>Taking these ways of killing ideas and hacks into account, we must admit that we have accidentally both starved ideas to death and killed ideas with no budget. However, at Citrix we are making progress toward giving ideas more of a chance to grow and thrive. By systematically going through the ideas from Hack Week and encouraging some of the promising teams to keep working on their ideas, we have supported good hacks and allowed them to survive. It has been difficult, and we are still struggling. But some of the ideas are beginning to show up on the radar, mentioned by top mangers as big opportunities. Slowly the organizational wheels are starting to roll, and we have two opportunities from Hack Week for which we are applying for internal funding. Not peanuts — we are applying for millions.</p><p>So here is what we have learned, if you want to succeed as an organization in making a Hack Week project survive:</p><ul><li><strong>Communicate that Hack Week is longer than a week</strong>: If stakeholders think that Hack Week is over after a week, they’ll miss out on big opportunities. It is important to communicate that Hack Week can produce long term products, and that that’s the exact purpose of it.</li><li><strong>Convince, convince, convince</strong>: When you’re done, you have to convince people that it is a good idea. Sell it! You often need the communication skills of a designer or product manager to put in the right appearence or language in order to really convince upwards in the organization.</li><li><strong>Make someone responsible for innovation</strong>: You need a person with innovation as his or her responsibility to keep pushing the ideas of an event like this. If you do not have someone that fights to support innovation, ideas <em>will</em> starve to death. It will happen quickly, without you realizing.</li><li><strong>Carry on with a skunkworks project</strong>: Initially you may have to work under the radar. In order to ever obtain funding, a prototype needs to be in a shape that stakeholders can see true value in. Hack Week projects built in a week usually aren’t refined enough to show off and get funding. So initially, try working in secret — for the sake of your idea!</li></ul><p>These are some of our experiences on what works if you want to be innovative and move a large company into new business areas. We give 100% during Hack Week and keep our hacks alive afterwards, so we can get them to a state where we can have customers saying go or no-go. Instead of getting stuck in internal evaluations, we would much rather have the market decide whether our ideas deserve a shot.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41011e680bb8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gotoassist-product-blog/how-letting-people-do-whatever-they-want-can-create-entirely-new-business-opportunities-and-why-41011e680bb8">Hacking your way into the future</a> was originally published in <a href="https://medium.com/gotoassist-product-blog">GoToAssist Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using T-tests to benchmark page load performance]]></title>
            <link>https://medium.com/gotoassist-product-blog/using-t-tests-to-benchmark-page-load-performance-6f45faff091e?source=rss----574d41514608---4</link>
            <guid isPermaLink="false">https://medium.com/p/6f45faff091e</guid>
            <category><![CDATA[inferential-statistics]]></category>
            <category><![CDATA[performance-testing]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Nikita Barsukov]]></dc:creator>
            <pubDate>Tue, 28 Jul 2015 08:35:24 GMT</pubDate>
            <atom:updated>2015-07-28T08:58:47.073Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4bZI5GM4jbB6a2rP0lNB3g.jpeg" /></figure><p>I explore how to rigorously test page load times between and old and new versions of a page using statistical analysis.</p><blockquote>GoToAssist Service Desk is a service management tool. We’re writing about how we build and improve it. Read more at <a href="https://www.gotoassist.com/remote-support/remote-support/service-desk">gotoassist.com</a></blockquote><p>I’m a Quality Engineer at GoToAssist. Recently we rolled out a redesigned page with an overview of open incidents. We released it as a Labs feature first, meaning that administrators of a Service Desk account could opt-in to see the new layout. During this period, we perform tests and ensure that the feature performs as expected when rolled out to everybody.</p><p>One of things I needed to determine was how the new layout affected the loading time of the dashboard page. I could load the page with the new layout turned off and then on, and measure the loading time using Chrome Developer tools, or Firefox’s Firebug — but I decided to take a more rigorous approach using a statistics procedure called <a href="https://www.khanacademy.org/math/probability/statistics-inferential/hypothesis-testing/v/hypothesis-testing-and-p-values">hypothesis testing</a>.</p><h4>Formulating a null hypothesis</h4><p>A null hypothesis describes a situation where there is no difference between two experiments. In our case the null hypothesis would be <em>“There is no difference between the loading time of the incident dashboard in GoToAssist Service Desk with the old and new layout.”</em></p><h4>Designing and executing our experiment</h4><p>The next step would be to <strong>design and execute an experiment</strong> where we measure the loading time of a dashboard page in the browser. I wrote a simple script in Ruby using the library <a href="https://code.google.com/p/selenium/wiki/RubyBindings">Selenium Webdriver</a>. It launches Chrome browser, visits a Service Desk URL, logs in as test user and waits until the dashboard page is fully loaded. It measures time between submitting a log in form and getting all the incidents rendered on the page, and saves it to a file. This process is repeated 100 times.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/814bc044984ab201228209de4a6f9084/href">https://medium.com/media/814bc044984ab201228209de4a6f9084/href</a></iframe><p>This script is executed twice, once with the old layout, and once with the new layout.</p><p>Next step would be to <strong>run a statistical test</strong> on response times to calculate the probability that the difference between two variables is due to randomness. Also, we should create a density plot of response times to illustrate our findings. I used T-test as statistical test; the code itself was written in <a href="http://www.r-project.org/">R programming language</a>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/41daa03335d02bf27c090dd4b926cfee/href">https://medium.com/media/41daa03335d02bf27c090dd4b926cfee/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uXX5omjzE4S9dTk7tT4Upg.png" /></figure><p>The results of the performed t-test were as follows:</p><ul><li>Confidence level: 99%</li><li>T-score: -4.18727 , t-critical: -2.34711</li><li>P-value: 0.004401498%</li><li>Confidence interval (there’s 99% chance that true difference is between these numbers): -1.7199197 -0.4012059</li></ul><p>Thus we can reject null hypothesis with great certainty. The new layout that we rolled out indeed slowed down the loading time of the dashboard page in a browser. The probability that the difference is by chance (p-value) is negligibly small, and the mean loading time increased by almost full second.</p><p>Since this feature is currently an opt-in Labs Feature, we were able to fix it before it became a big issue. Our developers were quick to find the root cause and fix it. You can read more about how we use Labs Features to test new releases in Luke’s post <a href="https://medium.com/gotoassist-product-blog/leveraging-labs-features-for-a-better-end-user-experience-992a22a9cca4">here</a>.</p><p>Incidents on the new dashboard were loaded through a messaging system called Faye. We discovered that there were several extra connections to the message bus, which we removed. Additionally, all the incidents in the dashboard were loaded at once, without pagination or progressive loading. With several hundred incidents, loading time could be even slower. We reduced the number of incidents initially loaded, and implemented auto-loading of new incidents. Now, when the user scrolls down, new incidents are loaded and added to the bottom of the page. This reduces the initial payload and the overall loading time, only loading what’s necessary.</p><p>Here’s the plotted distribution of loading times after fixes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*is3XQ4t_EFbiPJ2obPzR_A.png" /></figure><p>In this experiment, mean loading time of our dashboard page was less by .8 seconds, with negligible p-level of 0.0001914% and 99% confidence interval of [0.3978129 1.2826293]. Indeed, our dashboard loads faster after our fixes.</p><p>We iterated and made these performance improvements <a href="http://blog.gotoassist.com/gotoassist-service-desk-v103-v110-web-release-notes/">available</a>; the feature now performs as well as we expected. It will soon be in the hands of all customers — we’ll write more about how we addressed the performance issues in a future post.</p><h4>Conclusion</h4><p>In this post I’ve described my usual approach to comparing performance metrics. There is nothing wrong with measuring, say, the loading time of a page before and after changes once. The problem with that is that there is a chance that the results are influenced by random factors, like cached assets in the browser.</p><blockquote><em>Repeated experiments in a controlled environment combined with formal statistical tests allow us to determine the real impact of changes on performance.</em></blockquote><p>Such techniques can be used in broad range of performance testing tasks. We can use statistical tests to compare loading times across different data centers, querying the speed of database clusters, API response time before and after performance tuning, and so on.</p><h4>Further reading</h4><ol><li>Courses in inferential statistics and hypothesis testing: the ones from <a href="https://www.udacity.com/course/intro-to-inferential-statistics--ud201">Udacity</a> and <a href="https://www.khanacademy.org/math/probability/statistics-inferential">Khan Academy</a> are the best I’ve read.</li><li><a href="https://msdn.microsoft.com/en-us/library/bb924375.aspx">Performance Testing Guidance for Web Applications</a> from Microsoft is a detailed and extensive manual on performance testing.</li><li><a href="http://tryr.codeschool.com/">Try R</a> is an excellent introduction to R, the most popular programming language for statistical calculations and plotting.</li></ol><p>Want to hear more about how we build GoToAssist? Follow our publication (and Nikita!) below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f45faff091e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gotoassist-product-blog/using-t-tests-to-benchmark-page-load-performance-6f45faff091e">Using T-tests to benchmark page load performance</a> was originally published in <a href="https://medium.com/gotoassist-product-blog">GoToAssist Product Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>