<?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 Jason Zippro on Medium]]></title>
        <description><![CDATA[Stories by Jason Zippro on Medium]]></description>
        <link>https://medium.com/@jasonzippro?source=rss-6c3225a3d3c0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LylZ8bZGItWAT7Li2Vq8uw.jpeg</url>
            <title>Stories by Jason Zippro on Medium</title>
            <link>https://medium.com/@jasonzippro?source=rss-6c3225a3d3c0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:11:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jasonzippro/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[Technology + Design: A Passion Presentation]]></title>
            <link>https://medium.com/@jasonzippro/technology-design-a-passion-presentation-faeac9782c9b?source=rss-6c3225a3d3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/faeac9782c9b</guid>
            <category><![CDATA[humanity]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Jason Zippro]]></dc:creator>
            <pubDate>Fri, 14 Apr 2023 15:46:33 GMT</pubDate>
            <atom:updated>2023-04-14T15:46:33.847Z</atom:updated>
            <content:encoded><![CDATA[<p>The following is a passion speech that I gave in my MBA program back in Spring of 2017. It’s pithy and to the point, but it still encapsulates my beliefs about technology and design. I do not own the rights to any of the images in the presentation, and I pull some of the language in the speech from sources that I no longer remember and can cite—if you hear any, please leave a comment, so I can cite them appropriately. Thank you.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fx4hPHRFTBHo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dx4hPHRFTBHo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fx4hPHRFTBHo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/72a8a7299f73acb8cf8be32260c08f3f/href">https://medium.com/media/72a8a7299f73acb8cf8be32260c08f3f/href</a></iframe><p>Growing up with an Italian mother means I’ve had a lot of really good food, but it also means that I was routinely exposed to a lot of the humanist art and literature of Renaissance Italy. Many of the names like Michelangelo, Botticelli, Brunelleschi, and Leonardo were names just as common in my home as perhaps George Washington or Thomas Jefferson. The humanist art, work, and designs filled my home.</p><p>My father was the son of a Dutch immigrant and a computer engineer and he filled our home with a lot of technology. In fact, at one point, we probably had twenty computers networked throughout my entire home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WycYItD02GpQV1aNGJYsyQ.png" /></figure><p>My passion lies at the intersection of these two influences technology and humanist design. I believe that these two are intimately connected to what makes us human because they allow us to more fully inhabit our lives and the world in which we live them.</p><p>A few examples;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0aXfZEcQxYA4GCGs0lIDqw.png" /></figure><p>Social — from handwritten letters</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GtNx_e18VhYPuAk-a7o_Eg.png" /></figure><p>to the Telegraph</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mSrbz-rmhYoYdXCmSdVXhw.png" /></figure><p>to telecommunications and the Internet,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OQh6uOG0GuFb-dYADsuxHQ.png" /></figure><p>technology has sped up and amplified our ability to communicate with each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FFUU2MpszUnUc0-PrOYjzw.png" /></figure><p>Another example is physical — mobile is not a technology; it is a natural state of the human being that we are just now really being able to design for.</p><p>From wearable tech</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y570iMfU6RxEeZgRxbQIpg.png" /></figure><p>to mobile devices, technology is no longer something that we have to go to, but something that we carry along with us,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yhgPflkcfWYHt20iQ_55DA.png" /></figure><p>and is becoming more and more something integrated within us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*REnwk3UxqsPCsSGuPPG6-A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mzae28Aehk82qB1mrkScOw.png" /></figure><p>Third, emotional — with every virtual social interaction we have, our bodies actually release oxytocin;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-isQbHbEQJJV2ZluDhQ9bw.png" /></figure><p>with every notification, dopamine; and as we visually track our progress and achieve our goals, our bodies actually release serotonin.</p><blockquote>We can use design to leverage our own physiology.</blockquote><p>Technology and design actually augment each other</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xqrTXSq8rK3NraIggixU6w.png" /></figure><p>because design without technology is really just wishful thinking,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YJTi8qxrR4AI_PJg6a0t5g.png" /></figure><p>and technology without humanist design is just complicated. I still can’t use these.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J7qn6cIVALBdCejCel1nsg.png" /></figure><p>But when you get both of them together, you get something that’s more than just simple and functional. You actually get something that’s innovative.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ODmm8dpVHQePFODnBvGymA.png" /></figure><p>I really love technology and humanist design. And as these two increase our capacity to live our own lives more fully and the world in which we live them, it is my belief that we as humankind will be more apt to preserve both.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TDBNhEgqdJmexxcQIfQTcQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=faeac9782c9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build Customer Trust in Your SaaS Product]]></title>
            <link>https://medium.com/@jasonzippro/how-to-build-customer-trust-in-your-saas-product-ae2e5b59a6e4?source=rss-6c3225a3d3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae2e5b59a6e4</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[b2b]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jason Zippro]]></dc:creator>
            <pubDate>Mon, 10 Apr 2023 19:13:16 GMT</pubDate>
            <atom:updated>2023-04-11T12:33:36.250Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sYuerSz6vJWrtl9l" /><figcaption>Photo by <a href="https://unsplash.com/@thatanimeweirdo?utm_source=medium&amp;utm_medium=referral">Laura Heimann</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong><em>The Gravel Pit of Despair</em></strong> became my not-so-affectionate pet name for the events that began on July 24th, 2019 at Grow.com. We rolled out a non-rollback-able code push that all but took down our application.</p><p>The ensuing 5 months were hell. Permissions broke and read-only users got access to data they weren’t supposed to, random screens of the application would periodically go blank with no perceivable pattern as to why, and performance lag would intermittently spike for similarly no apparent reason. A product and engineering team’s worst nightmare materialized.</p><p>This was the one and only time I’ve ever questioned my decision to work in Tech. It still gives me anxiety to think about it; but now, years later, I’m thankful for that experience. It was a brutal, months-long slog to dig ourselves out of that situation. The hardest part was earning back the trust of our customers and users.</p><blockquote><strong>The hardest part was earning back the trust of our customers and users.</strong></blockquote><p>As we worked to piece everything back together, I spearheaded a strategy to ensure we would never lose our customer’s trust again. I crafted a rudimentary framework. Then I attended HubSpot’s Inbound user conference later that year in September. HubSpot was a Series B investor in Grow and so I was invited to several portfolio company sessions where I was able to meet the HubSpot executive team.</p><p>In one of those sessions, HubSpot’s executive team shared a very similar experience they had only a few months earlier in April 2019. HubSpot quickly adopted a framework they called the Mainsail, which was similar to the framework I had been crafting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XBrOiYvHquZqTiWhCafVAg.jpeg" /><figcaption>Presentation slide of the Mainsail shared with HubSpot’s portfolio companies — Inbound 2019</figcaption></figure><p>The following is the resulting framework I built and implemented at Grow, which is partially influenced by HubSpot’s Mainsail framework.</p><h3>Customer Trust Framework Overview</h3><p>Just like Maslow’s Hierarchy of Needs, the framework was designed as a hierarchy of a customer’s basic needs. In essence, it is a prioritization framework to help product teams know categorically what work to do first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FYmdeMH4borPeb9WMjK1SQ.png" /><figcaption>Customer Trust — Hierarchy of Needs</figcaption></figure><p>The framework is meant to be worked from the bottom, up. You are wasting resources if you focus on a higher tier before a lower tier is sufficiently complete.</p><blockquote>You are wasting resources if you focus on a higher tier before a lower tier is sufficiently complete.</blockquote><p>For example, if you have a security breach, customers don’t care how performant your application is. Or if the buttons don’t work when you click on them (stability), then it doesn’t matter how intuitive your design is (usable).</p><p>With that being said, having each tier complete is table-stakes for today’s applications—you shouldn’t release a feature that doesn’t meet an acceptable standard for all the tiers.</p><p>Finally, keep in mind that this framework is primarily helpful in maintaining an existing product, but it is a crucial checklist for new products as well.</p><h3>The 3 Foundation Tiers</h3><p>These bottom three tiers are the foundation of your application. Your dev ops and development teams are primarily responsible for this layer. This layer usually deals with your infrastructural technologies, but will also include application elements like permissions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_0AkoIKrtepp7ecsDsN3FA.png" /><figcaption>Customer Trust—Foundation</figcaption></figure><h4>Secure, Private, Compliant</h4><p><strong>Secure and Private means that your application is architected so that what data and functionality shouldn’t be accessed, can’t be.</strong> It also means that customers have control over their data—what to share, with whom, when, and to what degree.</p><p>Ensure that you are compliant with the governmental laws in which each of your customers resides—for example, your EU customers require that you are GDPR compliant.</p><p>Like our previous example, no customer will care how slow your application is if you have a security breach. If this tier isn’t solid, you have no foundation to build on.</p><h4>Resilient</h4><p><strong>Resilience means that your application can recover after encountering problems.</strong> If your system encounters an unexpected situation, crashes, or hits some constraint, does it recover gracefully?</p><p>Your application is resilient if you’ve architected it to restore lost functionality quickly and automatically, while also preventing any lost data or work the customer was doing. In essence, have you minimized any negative customer impact when your system encounters problems?</p><p>Resilience comes before scaling because your customer won’t care if they can add 100x the amount of data or users onto your application if every time the application crashes, they lose all of their data.</p><h4>Scalable</h4><p>This is probably the most self-explanatory tier. <strong>Scalable means you can grow your customer base and their usage without having to rewrite your code to do so; and even better, without any manual effort.</strong></p><p>Additionally, it is important that you’ve thought through the costs of scaling—does the marginal cost of adding an additional customer stay the same or decrease? If not, your system may scale, but your business won’t.</p><p>A great question to ask is can your system scale if you were to 10x, 100x, and 1000x the number of customers and usage you currently have without having to re-architect your solution?</p><p>Scalability comes before stability because a customer won’t care if your application works if they can’t get all of the data or users they need onto your platform.</p><h3>The Middle 3 Tiers</h3><p>The middle three tiers are all interrelated, which we’ll describe shortly. Whereas the first three tiers dealt primarily with infrastructure, these three tiers deal directly with your application layer and the customer’s experience interacting with the UI. That’s why this layer is primarily owned by the Product Manager and Developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QRsb8tcggxNHQU4Hedn1_A.png" /><figcaption>Customer Trust—Middle Tiers</figcaption></figure><h4>Stable</h4><p><strong>Very simply, your application is stable when the application’s functionality works.</strong> When you click the “save” button, the application saves. When you click navigational ui, you are transitioned to the right place. When you type in the search box, results appear.</p><p>A key part of stability is that functionality works EVERY time. Keeping track of dead clicks and rage clicks is a good indication of how stable your application is. The question to ask yourself is does the functionality work when interacted with every time?</p><h4>Reliable</h4><p>Reliability is the next step after stability. Once functionality is working every time, then it should work in the same way every time. <strong>Reliability means you have set up consistency in behavior which builds trust by setting up and fulfilling an expectation.</strong></p><p>Here’s an example of an inconsistent experience. If you click an export button, it shouldn’t download to your browser some of the time, but then send you a file in an email other times. It should do one or the other every time, don’t surprise your user by switching it up.</p><p>The hardest part of reliability to get right is timing. When a user interacts with the UI, does it happen within the same amount of time consistently? For example, if a customer clicks the “Save” button, it shouldn’t take 1/10 of a second one time, but then take 10 seconds the next time. You need to set up an expectation both in terms of what a feature does, but how quickly as well.</p><h4>Performant</h4><p>Once your functionality works in the same way, at the same speed, nearly every time, then you can focus on performance. <strong>Performance means your application works quickly enough that your user doesn’t notice any lag in speed and consequently doesn’t lose their train of thought.</strong> Things should move so fast that your application doesn’t draw attention to itself.</p><p>How fast is fast enough? The Nielsen Norman Group has a great response to this:</p><blockquote>There are 3 main time limits (which are determined by human perceptual abilities) to keep in mind when optimizing web and application performance.</blockquote><blockquote><strong>0.1 second</strong> is about the limit for having the user feel that the system is <strong>reacting instantaneously</strong>, meaning that no special feedback is necessary except to display the result.</blockquote><blockquote><strong>1.0 second</strong> is about the limit for the <strong>user’s flow of thought</strong> to stay uninterrupted, even though the user will notice the delay. Normally, no special feedback is necessary during delays of more than 0.1 but less than 1.0 second, but the user does lose the feeling of operating directly on the data.</blockquote><blockquote><strong>10 seconds</strong> is about the limit for <strong>keeping the user’s attention</strong> focused on the dialogue. For longer delays, users will want to perform other tasks while waiting for the computer to finish, so they should be given feedback indicating when the computer expects to be done. Feedback during the delay is especially important if the response time is likely to be highly variable, since users will then not know what to expect.</blockquote><p>Read the full article: Response Times: The 3 Important Limits here:</p><p><a href="https://www.nngroup.com/articles/response-times-3-important-limits/">Response Time Limits: Article by Jakob Nielsen</a></p><h4>Stable → Reliable → Performant</h4><p>Here is a diagram to help explain how these middle three layers (Stable, Reliable, and Performant) are interrelated, which highlights why this particular progression matters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TzdHnR7NRxGE3DI_eU-luA.png" /></figure><p>If we were to graph the number of instances a particular action occurs by how long it takes for that action to occur in seconds, we would get a histogram where on the far left of the x-axis, we have “instantaneous” and on the far right “failure to occur.”</p><p>If a feature is unstable, then according to our definition, the particular action in the app isn’t working some portion of the time, an extreme case of this scenario is what you see in the following diagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*uw6VFXi7WSGB5YSmbGWCeg.png" /><figcaption>Unstable Functionality</figcaption></figure><p>As we make this action more stable, but not reliable, we would expect to see a shift to no longer having a high failure rate. However, we would still see that performance isn’t consistent. This is why we have a more normally distributed diagram, but the standard deviation is quite large.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*PcMr5na0ZoEn9ICpne3OLQ.png" /><figcaption>Stable Functionality, but not yet Reliable or Performant</figcaption></figure><p>As we make the action more reliable, but not performant, we see the standard deviation shrink more—meaning the time it takes the action to occur tends to be more consistent. This results in the diagram where we still have normally distributed occurrences, but tighter around the mean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/494/1*KJ82kC5SpWCQPVWpgGyPVg.png" /><figcaption>Stable &amp; Reliable Functionality, but not yet Performant</figcaption></figure><p>Finally, as we move to a more performant action, we keep the same normally distributed structure, but the mean drops and shifts closer to 0 (or instantaneous) on the x-axis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*D2nHMlZr6oQfBqWjUlIXbQ.png" /><figcaption>Stable, Reliable, and Performant Functionality</figcaption></figure><p>Hopefully this illustrates why this particular progression matters: we first want to reduce the failure rate (make an action stable), then reduce the standard deviation (make an action reliable), and then finally reduce the mean (make an action performant).</p><h3>The Top 2 Tiers</h3><p>The top of the pyramid is where most new PMs tend to spend the majority of their time—it is arguably the most fun part of Product Management and User Experience Design. There is so much written about these two, so I’ll only briefly touch on both.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fHlnruXBzeAM07Op3DCl7g.png" /><figcaption>Customer Trust—Top</figcaption></figure><h4>Usable</h4><p>Usability, in terms of a user’s trust in your platform, simply means that your user knows how to use your application—they can intuit where to go, what to do, and how to accomplish their desired behavior.</p><p>Kind of like an iceberg, all of the other tiers beneath the useable tier should never surface into the customer’s experience since they should “just work.”</p><p>Ideally, the UI should be so useable that the customer rarely, if ever, becomes cognitively aware of the interface they are interacting with.</p><h4>Pleasurable</h4><p>Pleasurable is often completely forgotten, but it is perhaps one of the best ways to build your customer’s trust. Pleasurable means working in your application delights your customer.</p><p>Cultivate a positive feeling when using your application. When a lapse in one of the lower tiers does occur (and yes, when it happens, not if), then thanks to the halo effect, your customer will be much more lenient and you will recover from any lost trust much more quickly because of the positive feeling they already had of your application.</p><h3>Final thoughts</h3><p>It is hard to recover a customer’s trust once you’ve lost it. In fact, I would dare say it’s almost impossible.</p><p>When something happens that strains customer trust, being fully transparent with customers and prioritizing the right things, at the right time, and communicating what you are doing, why you’re doing it, and how you’re doing it will go a long way in retaining your customer’s trust.</p><p>I hope this framework helps you determine how to prioritize work for your team.</p><p>Please let me know what you think by leaving comments. Frameworks are always in flux and can always be improved, so I’m eager to hear your thoughts.</p><p>Read more about HubSpot’s Mainsail in this post on HubSpot’s Product &amp; Engineering Blog:</p><p><a href="https://product.hubspot.com/blog/mainsail-framework">Charting a Steady Course: A Framework for Building a Secure, Reliable, Consumer-Grade Product</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae2e5b59a6e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>