<?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 Anuradha Gajanayaka on Medium]]></title>
        <description><![CDATA[Stories by Anuradha Gajanayaka on Medium]]></description>
        <link>https://medium.com/@acgajanayaka?source=rss-1a36cd7938e8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*dnbKpjn6LQwmilZ_.</url>
            <title>Stories by Anuradha Gajanayaka on Medium</title>
            <link>https://medium.com/@acgajanayaka?source=rss-1a36cd7938e8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:53:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@acgajanayaka/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[Buy extra 3 credits]]></title>
            <link>https://medium.com/@acgajanayaka/buy-extra-3-credits-e78d87a1f481?source=rss-1a36cd7938e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e78d87a1f481</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Anuradha Gajanayaka]]></dc:creator>
            <pubDate>Wed, 11 Apr 2018 05:40:51 GMT</pubDate>
            <atom:updated>2018-04-11T05:40:51.460Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U8XYJ9lFVLFXiZEVYX5HMA.jpeg" /></figure><p>If you are a audio book listener and using <a href="https://www.audible.com/">Audible.com</a>, I am sure you have came across this “buy extra 3 credits” button in Audible. It is a simple feature and require no attention. Nothing fancy about it at all.</p><p>But if you think a little bit deep on this you would realized that this <strong>simple button </strong>is a well thought feature by Audible. I am sure this button is an outcome of a hard &amp; lengthly thought process by Audible.</p><blockquote>As Leonardo da Vinci said “<strong>simplicity is the ultimate sophistication</strong>”.</blockquote><p>Below are few points why this feature is an outcome of a hard thinking process.</p><p><strong>No money involved — it is just credit</strong></p><p>The moment the word money get in to brain of anyone, some negative spark appears in the brain. So audible moved away from the word money whenever possible (not 100% for obvious reasons).</p><p>The concept of “credit” camouflages real money. Buying three credit costs $35.88 as per my last transaction. Why I say credit purchase is camouflage is; think of the two buttons below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/1*Rk54EPsWitxPni5HIMdyIg.png" /><figcaption>Button 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*AJx9vUKM_No_jCDt00C_lQ.png" /><figcaption>Button 2</figcaption></figure><p>In my view, users are more likely to click on the first button to buy 3 credit than the button labelled with money</p><p><strong>No overselling — It is there only when required</strong></p><p>This button appears only when you have ran out of credit.</p><p>The consumer the get the feeling that Audible is trying to help rather than selling. Why? This is how the thoughts are sequenced in user’s mind;</p><ol><li>There is a great book which I want to listen</li><li>Searched that in Audible library &amp; found that it is available</li><li>When trying to buy it, apparently credit is not available</li><li>So audible comes to help me offering to buy extra 3 credits. No money involved</li></ol><p>So Audible appears as a helper rather than a seller. This feeling is strong.</p><p><strong>Ease of use — Single click and a confirmation</strong></p><p>Buying 3 credits from the audible app require no lengthly confirmations. It requires only few clicks.</p><p>If this would require multiple steps, there would have been many people drop out in the middle of the process.</p><p><strong>Positioning of this button — It is position in easy to use area but not crowding the main space</strong></p><p>It is positioned in top of the screen where it is not that difficult to reach but not disturbing user’s main action of searching and buying books .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/293/1*n76Ot70QYTJc4_KO1FG-1w.jpeg" /><figcaption><a href="https://ux.stackexchange.com/questions/79596/mobile-hamburger-menu-location">https://ux.stackexchange.com/questions/79596/mobile-hamburger-menu-location</a></figcaption></figure><p>In summary, the “buy 3 credit” button is based on the notion that “Audible is helping the user than selling ”. They have carefully designed this button in a way this subtle difference is planted in the mind of the user</p><blockquote>Although it looks surprising, coming up with simple features take lot of effort behind the seen. <a href="https://www.ted.com/talks/margaret_gould_stewart_how_giant_websites_design_for_you_and_a_billion_others_too/transcript">In a TED talk</a>, Margaret Stewart, Facebook’s director of product design noted that it took 280 hours to design the Facebook “like button”.</blockquote><p>On a foot note, I have no idea what exact psychological concepts being used here. Would be great to learn those :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e78d87a1f481" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How frequently should you release software to production? — A mathematical view]]></title>
            <link>https://medium.com/@acgajanayaka/how-frequently-should-you-release-software-to-production-a-mathematical-view-1a3b56e16092?source=rss-1a36cd7938e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a3b56e16092</guid>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[cost-of-release]]></category>
            <category><![CDATA[software-release]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Anuradha Gajanayaka]]></dc:creator>
            <pubDate>Mon, 17 Jul 2017 04:01:01 GMT</pubDate>
            <atom:updated>2017-07-17T06:15:19.191Z</atom:updated>
            <content:encoded><![CDATA[<p>Everybody jumps in to the bandwagon of continuous delivery (CD) . CD has becomes so much marketed that every product manager wants to do CD without really considering whether it is beneficial or feasible.</p><p>This is an attempt to look at what is <strong>the optimum release frequency</strong> from a mathematical point of view. In other words, looking at whether CD is suitable for your product or not</p><p>Let’s tackled this question from a cost vs benefit perspective (a.k.a the economic point of view).</p><p><strong>Cost of releasing:</strong> This is how much money you have to spent to do a release. A release requires many additional efforts including regression testing, planning, deployment, etc. All these adds up to make cost of releasing.</p><p><strong>Benefits of releasing:</strong> This is very difficult to measure accurately but can be simplified as revenue generated from features released.</p><p>The costs and benefits of releasing will not be straight lines. Let’s look at them in bit detail.</p><p>In a simplified example, let’s assume single release costs 500 USD. If you release every day, then the total cost of releasing for a month is 500X30 as there will be 30 releases. If you perform releases every other day, the cost is 500X15 as there will be only 15 releases. So the cost of releasing goes down with increased release frequency.</p><p>The benefit of releasing also follows a different but somewhat similar pattern. In an over-simplified example, let’s assume that every work day from development team can generate average 500 USD revenue per day when released to production.</p><p><strong>If we release everyday;</strong> the release in day 1 would keep on generating 500 USD each day. The day 1 release would generate 500X30 USD worth of revenue for a month. There will be another release on 2nd day, 3rd day so forth. Second day release would generate 500X29 USD in addition to revenue generated by first release. If we keep on releasing each day, this would generate 120,000 USD for a month.</p><p>What if we <strong>release every other day not every day</strong>. The first release would happen on 2nd day of the month, the second release would happen on 4th day of the month, etc. But each release would <strong>start</strong> <strong>to</strong> generate 1000 USD (500X2) worth of revenue.</p><p>The following graph plots the above example situation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mqfizJS5_IoZ5fR2zm19pA.png" /><figcaption>Cost vs benefit of different release frequencies</figcaption></figure><p>The green graph is the total benefit (Revenue generated minus Cost) gained at different release frequencies.</p><p>What it shows is that for this product, releasing <strong>every 5days</strong> would provide the most benefit. Releasing less or at a higher frequency would generate potential loss to the product.</p><p>This does not go well with the concept of continuous delivery or deployment. If we release everyday the company loses money. <strong><em>But the situation is totally different if the cost of the release is reduced significantly.</em></strong></p><p>This is how the graph looks like if the cost of releasing is reduced by 10 fold</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*WBSEEA089m_g-3uNWxz-Bg.png" /><figcaption>When cost of releasing is reduced to 10%</figcaption></figure><h3>Conclusion</h3><p>As you can see, releasing every day is the most beneficial. So the conclusion is that if you can reduce the cost of releasing significantly, continuous delivery is the best option.</p><p>The cost of releasing can be reduced by test automation, building automated deployment pipeline, etc.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a3b56e16092" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>