<?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 Debi Ndindjock on Medium]]></title>
        <description><![CDATA[Stories by Debi Ndindjock on Medium]]></description>
        <link>https://medium.com/@DebiTerry?source=rss-bf9effa79e2e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AO2Rv02qcmKL6MS5heB1Jg.jpeg</url>
            <title>Stories by Debi Ndindjock on Medium</title>
            <link>https://medium.com/@DebiTerry?source=rss-bf9effa79e2e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:28:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@DebiTerry/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[Think Big. Design Small.]]></title>
            <link>https://medium.com/@DebiTerry/think-big-design-small-d5321084239f?source=rss-bf9effa79e2e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5321084239f</guid>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Debi Ndindjock]]></dc:creator>
            <pubDate>Wed, 28 Mar 2018 19:56:17 GMT</pubDate>
            <atom:updated>2018-03-29T16:00:10.757Z</atom:updated>
            <content:encoded><![CDATA[<h4>Compartmentalized design and the journey to overcome it</h4><p>This is a story of the time my team ambitiously, and maybe naively, set out to build a single tool to estimate prices across the <a href="https://dev-console.stage1.bluemix.net/catalog/">IBM Cloud portfolio</a>. Currently, our catalog offers 170+ services ranging from bare metal and serverless computing, to hyperscale infrastructure and blockchain, to name a few.</p><p>We started off with nothing but a hunch that it would be a great benefit to our customers to quickly and easily know what it would cost them to engage in the Cloud at varying degrees. At the time, the estimation process involved a handful of stand-alone calculators within our platform, with the added task of consolidating their output.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RSoGc4NrbKyT6ar5." /><figcaption>A mishmash of pricing calculators on the platform</figcaption></figure><h4>We knew we could do better</h4><p>Marketing teams and what we call Core IBM Cloud embarked on a joint venture to build a new price estimation tool. We recently released the first installment of the<a href="https://console.bluemix.net/pricing/"> IBM Cloud Pricing Calculator</a>. I’d like to share some of the lessons we learned that pertain to design of multi-part products, and life in general, but that may be a reach.</p><p>We carried out internal UX audits of the current pricing tools. This exercise revealed some cringe-worthy pain points, which in-turn provided great fodder for improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*800cIWHxlhbqmK8z." /><figcaption>Journey Map of a former price estimation experience :-(</figcaption></figure><h4>Our customers use our products in concert</h4><p>During a preliminary interview with a customer, they expressed a need to size the cost of a solution that was comprised of multiple services. While this in itself was not a new revelation, conducting customer interviews helped us better understand what the experience really was like. We also employed the use of tools like <a href="https://www.fullstory.com/">Full Story</a> and <a href="https://amplitude.com/">Amplitude</a> to qualify and quantify what we were hearing.</p><p>In the same way that a car owner services their vehicle using oil, tires, wipers etc. sourced from different manufacturers, a comprehensive cloud solution involves the coming together of many disparate yet connected parts.</p><p>A customer, for example, using <a href="https://console.bluemix.net/catalog/services/apache-spark">Apache Spark</a> for large-scale data processing, may summon the powers of big data optimization found in <a href="https://console.bluemix.net/catalog/infrastructure/object-storage-group">Object Storage</a>, and then further pair it with <a href="https://console.bluemix.net/catalog/services/analytics-engine?customCreatePageKey=catalog-custom-key-3xx1iv07">Analytics Engine</a> to develop and deploy analytics applications.</p><p>Just like in the car example, there is a need for a seamless pricing experience across multiple products.</p><h4>Seeing the forest despite the trees</h4><p>We started by reaching out to various product teams to better understand their offerings. They are intrinsically involved in their products and therefore understand the nuances of their configurations and pricing better than we do.</p><p>During this collaboration, it became evident that many of the teams viewed their products in isolation. While as an organization we have worked tirelessly to break down silos, human nature insists on us seeing what is immediately in front of us. These teams are ingrained in their products day-to-day, which is valuable to building a deep understanding, but risky to playing well with others.</p><p>My colleague and design leader Jeoff Wilks brilliantly addresses closing the gap in broken user experiences between teams in his article <a href="https://uxdesign.cc/when-great-product-teams-ship-broken-ux-4-steps-to-mind-the-gap-bfdf6f150f8b">When Great Product Teams Ship Broken UX</a>.</p><h4>Understanding the journey</h4><blockquote>“If you do not know where you come from, <br>then you don’t know where you are, <br>and if you don’t know where you are, <br>then you don’t know where you’re going. <br>And if you don’t know where you’re going, <br>you’re probably going wrong.”</blockquote><blockquote>Terry Pratchett</blockquote><p>To create a seamless experience it is necessary to know where a user is coming from prior to landing on your product, and also where they go to when they leave. This is why, even after the new Pricing Calculator has been released, we have continued to monitor the estimation journey. Using my current favorite tool “User Paths” in <a href="https://amplitude.com/">Amplitude</a>, we are able to identify those glaring transitions between workflows and work to smooth them out for a cleaner experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z6BdrfDqvNGaw_cr." /><figcaption>Pricing Calculator User Paths</figcaption></figure><h4>All things equal?</h4><p>Consistency is the most famous principle of design. It is essential in improving learnability and eliminating confusion. For this reason, we chose to maintain consistent patterns across the calculator.</p><p>As we gained a better understanding of the products, we discovered some significant differences in pricing models, largely due to differences in their respective technologies. Some products operate in a pretty straightforward paradigm: configure this here, tweak that there, and voila! a price. Others like <a href="https://console.bluemix.net/catalog/infrastructure/object-storage-group">Cloud Object Storage</a> are more complex.</p><p>How do you represent these different products within the same tool in a way that does not feel disjointed?</p><blockquote>As designers, we need to ask ourselves:<br> “When should we deviate from established patterns, and what are the compelling reasons to do so?”</blockquote><p>I often tell my kids that we don’t have to match, but let us at least look like we are going to the same place. Similarly, rather than insisting on being matchy-matchy, we made deliberate choices to deviate from patterns based on an understanding of specific use cases. With the help of our awesome Design System <a href="http://www.carbondesignsystem.com/">(Carbon</a>) team, we delicately incorporated alternative patterns.</p><h4>Duplicated experiences</h4><p>The other issue we needed to keep an eye on was duplicated experiences, or even worse, conflicting ones. This was a risk we ran not only for our users, but also with our design and development teams repeating labor where not necessary. This problem is explained clearly (and hilariously!) by Henry Latham in his article <a href="https://uxplanet.org/how-to-save-ui-designers-front-end-developers-up-to-50-of-their-time-39a30254ec05">How to Save UI Designers &amp; Front End Developers up to 50% of Their Time</a>.</p><blockquote>Requiring users to resubmit the same specifications for every single one of their intents would be downright evil.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eCj6212ZITzH7rpY." /><figcaption>Repetitive and repetitive</figcaption></figure><p>The journey toward generating a pricing estimate might begin on a <a href="https://www.ibm.com/cloud/products/">general information page.</a> The user might then be curious about the cost and make their way to <a href="https://www.ibm.com/cloud/pricing">pricing</a>. From there they may choose to estimate the cost of a product based on usage. If they like the price, they may choose to enter into a relationship with us by way of a purchase of sorts, followed by configuring their product, and the journey could go on and on.</p><p>If someone on the calculator likes the price estimated to them and would like to make a purchase, we should use the information entered in the calculator to initiate the process, instead of making them to enter it again. Truth be told, the Pricing Calculator is simply a pared down version of the provisioning experience. Working all the pieces in concert makes for a smoother ride.</p><h4>Reducing Friction</h4><p>As we continue to work on the new Pricing Calculator we are discovering areas where we can make the experience feel even more cohesive.</p><blockquote>Rather than taking users to the calculator, let’s bring the calculator to them</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1N30qCn94S7RzPKo." /><figcaption>Modular design produces “dishable” components</figcaption></figure><p>If, for example, a user on a product page would like to figure out how much it would cost them based on their estimated usage, we could enable them to make this calculation on the spot.</p><p>Looking at the larger experience, we have identified multiple opportunities to embed the calculator as a module. This small addition to the design will enable users to accomplish their price calculations without being bounced from page to page.</p><h4>So what’s next?</h4><p>We are gradually adding more product categories to the calculator, especially infrastructure ones like storage and network, but this time with a heightened awareness of the end-to-end estimation experience.</p><p>We realize that making money-related decisions is rarely a one-person exercise as it often involves discussions with finance teams and co-workers within an organization. To smooth the transition toward collaboration, we will soon be adding the ability to download and share estimates directly from the Pricing Calculator.</p><p>To further close the divide between the estimation experience and the purchasing experience, we hope to soon give our customers the ability to purchase products they have estimated on the spot.</p><blockquote>We are also going back to users for additional feedback on the delivered product as well as analyzing conversion funnels. So far both look promising.</blockquote><p>Users who estimate the cost of services are increasingly inquiring about provisioning them and actually going on to create services.</p><p>As we continue to assess the bigger picture, our commitment is to make the price calculation experience even more seamless and painless.</p><p><a href="https://dev-console.stage1.bluemix.net/pricing/">See the IBM Cloud Pricing Calculator here</a></p><p><strong>Shout outs:</strong><br>Robert James<br>Charles Black<br>Kevin Hazard<br>Michael Vendivel<br>Josh Johnson<br>Brendan Fitzpatrick<br>Taylor Aitken<br>Ryan Edgell<br>Jeroen Schaftenaar<br><br>…….. and many more</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5321084239f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>