<?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[Siam Computing Thoughts - Medium]]></title>
        <description><![CDATA[Thoughts and theories as we build world class technology products for our clients. - Medium]]></description>
        <link>https://medium.com/siam-computing-thoughts?source=rss----9af082d1f58d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Siam Computing Thoughts - Medium</title>
            <link>https://medium.com/siam-computing-thoughts?source=rss----9af082d1f58d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 17:08:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/siam-computing-thoughts" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[4 Quick & Dirty Ways to Build an MVP]]></title>
            <link>https://medium.com/siam-computing-thoughts/4-non-technical-ways-to-build-an-mvp-6aab4f9449f5?source=rss----9af082d1f58d---4</link>
            <guid isPermaLink="false">https://medium.com/p/6aab4f9449f5</guid>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Sivasankari]]></dc:creator>
            <pubDate>Fri, 15 Jul 2016 11:30:37 GMT</pubDate>
            <atom:updated>2016-06-27T06:21:46.786Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ArYzrlsR8xX4VSGGr52Wkw.png" /></figure><p>Alright, people put your thinking caps on cause you’re in for a one hell of a lesson on MVPs. This will make you a lot smarter, educated and most of all, an <strong>improved entrepreneur</strong>. First, let’s hit the basics and look at what the champ of The Lean Startup has to say about MVP.</p><blockquote>“A Minimum Viable Product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.”</blockquote><blockquote>-Eric Ries</blockquote><p>Don’t confuse the phrase ‘least effort’ with your laziness because it means putting in smart efforts. The reason to build a product <strong>should be really clear</strong> to you in the beginning or you shouldn’t bother wasting time. MVP methodology is a savior for entrepreneurs who want to get more done in less time. No need to reinvent the wheel, we’ll show you how it works.</p><h4>Make a perfect landing with a landing page</h4><p>If you love social media and are highly active on it then this is for you. Joel Gascoigne’s story will inspire you. His web app didn’t launch on day one. He was smart enough to get feedback for his not even ready product.</p><p>He used a two page website (landing page) to test whether people were interested in his product or not. Due to his active participation on Twitter, he had built himself a good reputation. When he shared his landing page from a Tweet, people jumped in to see what he had to offer. By doing this, he saw a glimmer of hope that there actually was demand for a product like Buffer. But he didn’t stop there ! After validating the interest about the product, he also tested (with another landing page) whether people would be interested in <em>paying for the product</em>. It worked, so he took the next step. Within seven weeks he built his first web app and chrome extension.</p><p>Have a look at the simple design that was used to highlight the core features of Buffer</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/0*roEVR_BUDrJQWlsW.png" /></figure><h4>Facebook Group/Page</h4><p>Another mind boggling idea is here at your disposal. Who would have thought Facebook could solidify the foundation of your startup. Bill Boorman put it perfectly, “Facebook is where people live.” You know this, people are using Facebook to sell things we can’t even imagine! Why would you want to ignore an opportunity like this? You don’t have the same financial assets as big companies so here, you can start free of cost. It doesn’t matter if you’re using a concentrated group or a business page to expose your products, it works really fine.</p><p>The various marketing tools on Facebook will help you to reach your target audience. Skip the idea of building an expensive website, if your customers start to buy from your page right away you can think about a shopping cart for the future. The core idea here is to find out NOW if people are really going to buy what you’re offering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/0*YgHaG5cOWUUeS8wa.png" /></figure><h4>Whatsapp</h4><p>What once started as a hobby transformed into a one of a kind MVP. Kabeer Biswas put the ball straight out of the park with his Bangalore-based company Dunzo. Here’s the rub. His startup works on the idea of providing goods and services to people through the medium of WhatsApp.</p><p>He and his co founders gave an interesting spin to the local e-commerce industry. They didn’t develop an app beforehand : instead, they started by telling users to send their request simply through a phone number, via WhatsApp. That’s it! A pigeon stuck in your balcony ? Recently shattered your phone’s glass? Don’t worry, Dunzo comes to the rescue only with a small commission charge. Read what Kabeer had to say about his superb idea:</p><p>“All these apps-based hyperlocal startups look like a web product. What we are trying to prove is that mobile is a replacement of what you see, what you hear and where you are”</p><p>After getting a lot of positive feedback for Dunzo, they were able to successfully raise enough capital to take his product to new heights. They are progressively improving their products but catch here is to identify what he did in the beginning.</p><p>He got out in front of people, showed them what he wanted to do and took enough steps to steer away from other mobile based e-commerce apps.</p><h4>Video</h4><p>Like all entrepreneurs, the founder of Dropbox faced the challenge to show venture capitalists his software was “the next big thing”. But he didn’t give up! To avoid the risk of waking up after years of development with a product nobody wanted, Drew Houston did something unexpectedly easy: he made a video. Why did he do so ? To <strong>validate the existence of the demand for his product!</strong></p><p>The video was placed on a landing page so this cuts out the cost of investing in complicated lead funnels. Have you ever imagined this company may have never been successful without <a href="https://www.youtube.com/watch?v=7QmCUDHpNzE">this thing</a> ?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*yfkxlQibFZER6-S8kTYLIA.jpeg" /></figure><p>He narrated the process so brilliantly over this small video, which targeted at a <strong>community of technology early adopters</strong>, on the Digg website. Why there ? Because it was an active community, that he was a part of! He knew what would make them smile, and that it was a great place to get feedback. As he moved his mouse to various files on his screen, there were full of in-jokes and humorous references. This was appreciated a lot by the viewers; what you don’t like jokes? Remember, the habit of going the extra mile always works.</p><p>Drew recounted, “It drove hundreds of thousands of people to the website. Our <strong>beta waiting list</strong> went from 5,000 people to 75,000 people literally overnight. It totally blew us away.”</p><p>The chain reaction started by the video gained instant stardom for Dropbox. <strong>You think MVP is all about creating products? Think again!</strong> You can start by creating a video of your idea or product (even if your first shippable product is not ready) and correct your course accordingly. So to sum it up, find out a cheap but effective way to make sure your target customers<strong> say they are interested in your product. </strong>Get back to Eric Ries’ definition: this is already an MVP !</p><h4>Don’t wait to build your 1st Shippable Product</h4><p>Momentum is everything in the startup world, and the Dropbox founder got really lucky to be able to ship his product at the same time he showed it for the first time. But we believe it may be risky to have developed something at such an early stage, without having fulfilled these customer development steps. Don’t build it to early on, but build it as soon as you actually see you can build a business out of it! This is the second type of MVP: the <strong>first shippable product</strong> that is delivered and will actually be used by the end users.</p><p>Providing superior customer experience is your goal. Fellow entrepreneurs, you need to understand that you just can’t be doing what other people are doing and expect that the audience would be interested in using your product.</p><p>Your goal is to test your fundamental business hypotheses. <strong>Just begin and don’t think about going all bling</strong>. It would only increase your costs and even lead to a higher risk of failure. Rather, we suggest that you <strong>Build your first shippable product the Lean Startup Way</strong>. It should include only the very core features that your users want to use, so that you can start measuring the feedback and make changes according to the requirements of your customers.</p><h4>You’re building a business, not just a product</h4><p>See, writing code to build your product is not the only way to build an MVP, and we believe it is definitely not the first thing you need to do. Your product is for your customers; not a showpiece which boasts your ability to write code. Products fail because their <strong>creators focus on what they want rather than what their customer wants</strong>. Adopt a user-focused point of view by interacting with the users and putting yourself in their shoes.</p><p>Think of a new way to put your MVP across the customers or perhaps you could use a landing page just like Drew and his team did. Whatever it is, make sure you’re in the know and are capable enough to measure the workability of your strategy. After this first MVP has shown some traction, then you know you may end up having a chance to build a business out of it! Figure out a business model, and <strong>don’t wait to put your first shippable product in the hands of your users!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6aab4f9449f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/siam-computing-thoughts/4-non-technical-ways-to-build-an-mvp-6aab4f9449f5">4 Quick &amp; Dirty Ways to Build an MVP</a> was originally published in <a href="https://medium.com/siam-computing-thoughts">Siam Computing Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to love your developers — 101]]></title>
            <link>https://medium.com/siam-computing-thoughts/how-to-love-your-developers-101-5f59196f976b?source=rss----9af082d1f58d---4</link>
            <guid isPermaLink="false">https://medium.com/p/5f59196f976b</guid>
            <category><![CDATA[client-relationship]]></category>
            <category><![CDATA[web-project-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Khuze Siam]]></dc:creator>
            <pubDate>Tue, 07 Jun 2016 17:55:50 GMT</pubDate>
            <atom:updated>2016-06-25T10:04:47.356Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YPPbMRUKghUgUMg3DGYmKQ.jpeg" /></figure><p>I run a development agency at <a href="http://siamcomputing.com/">Siam Computing</a> and over the course of 4 years have had my share of clients. Some who have been great while some who have been, let’s say, not so nice.</p><p>Sometimes, developers and clients have this love-hate relationship, and I have always wondered how things go from being rosy eyed : ‘thou shalt do no wrong’ to a gut wrenching ‘spit in your mouth’ state.</p><p>I had originally titled this article ‘How not to hate your developers’ but realised that the problem is on both sides of the table. Since software development unlike other manufacturing industries deals with some form of human behavior it is much harder to encapsulate all the details that would sum up a project.</p><p>Here are a few things that I have learnt in my experience so far —</p><h3>The ‘Dating’ Period</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*___Wz1Fsrp6H-N-Zw3oa1g.jpeg" /></figure><p>It&#39;s easy to gloss over the details in a bid to get a project off the ground or to score a new client. Most clients have a high level idea of what they want, but it&#39;s the details that really screws up the relationship. It&#39;s important to think from the end users perspective and ask the right questions.</p><p>Also, most businesses these day run on some form of information technology. As a client, if you are building a business that depends on IT , it&#39;s important to analyse your dev partners on grounds more than just their technical competence , for instance —</p><ul><li>Are they prompt in their correspondence?</li><li>Do they understand why you are building it and not just what you are building</li><li>For the small things that aren&#39;t well laid out, can you trust them to take the right decision for your business.</li><li>Since they are in the ‘field’ , will they be able to advice you on the latest in technology and advise you to take decisions accordingly?</li><li><a href="http://www.joelonsoftware.com/articles/fog0000000043.html">What kind of development process do they follow?</a></li></ul><p>As a client, when you are in your ‘dating’ period, try having a more holistic view of who you are going to partner with, not all the criteria above may apply but think of this time as a means to getting to know the culture and approach of a dev agency.</p><p>Likewise for devs it is important to evaluate a client and take a conscious decision if that project/client is right for you. It is important to know if a client treats you like an equal partner in this relationship and is empathetic towards the nuances of software development.</p><h3>Requirements Gathering</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Qex7X0LoRohcZt4iq-Chdg.jpeg" /></figure><p>The holy grail of software development is the requirements document. Agreed that with the advent of agile development, a concrete requirements document is a thing of the past, even then it is important to have a clear idea about the direction the project will take.</p><p>In my experience, requirements can go awry for several reasons —</p><ul><li><strong>Insufficient client involvement</strong><br>Be wary of a client that isn’t involved in the project. More often than not, this leads to late realisation of what they actually want and make the project go into a never ending talespin.</li><li><strong>Changing business goals<br></strong>It is important to have a larger vision while commissioning a software for development. It’s easy to fall in the trap of ‘let’s do this for the time being’ but being more cognisant towards the overall shape your organisation is taking and building an application towards that will help in the long term.</li><li><strong>Multiple decision makers<br></strong>As they say, ‘Too many cooks spoil the broth’. It is absolutely imperative to have one person call the shots at the end of the day. With too many people donning the hat , the requirements could end up getting spread too thin and the software not doing anything specific.</li><li><strong>Lack of domain knowledge<br></strong>Not having enough experience in a particular domain before building an application around it can have a severe impact, especially if it&#39;s a new business. Having domain knowledge enables you to ask the right questions which eases the process of discovery.</li><li><strong>Scope creep</strong><br>Changing requirements because of lack of apparent impact is one of the most often touted reasons for requirements getting distorted. So many times clients make changes to their requirements because they feel that the impact is fairly minimum. Overtime, such repeated changes lead to scope creep. I believe the onus is on the dev to be more conscious towards accepting changes and layout the overall impact towards making repeated changes.</li></ul><p>Its crucial to freeze requirement at some stage to avoid rework. In large projects, 20–30% of cost goes towards rework because of poorly defined requirements. It&#39;s highly frustrating as a software developer to keep making tweaks to the architecture which eventually leads to a buggy application with lots of overwrites and poorly written code.</p><h3>Estimate</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*rQzkbJ0PAEs3JdRJ5JP_PA.gif" /></figure><p>Let&#39;s talk money.</p><p>Don&#39;t commit if you arent sure. Being shy about what it&#39;s actually going to cost to build something or not speaking up while there is a change in requirements doesn&#39;t help anybody. Be open about concerns you might have and communicate the same.</p><p>My grandpa once told me that even if i was doing something free for a client, create an invoice for the amount you would have actually charged and give a 100% discount. This way, the person who benefited from your service knows the value of what they are getting.</p><p>As developers, it is important to be constantly in touch with the value of your work and be able to communicate that value to your client. This helps the client put things in perspective and reduce scope creep.</p><h3>Communication</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*-ZWpxtE115DdZ_z-Ixcd_w.gif" /></figure><p>Be empathetic while communicating with your peers in a project. Everybody has their own lingo when it comes to technology and both clients as well as devs should take the extra effort to express themselves well and ensure the other person has understood what is needed.</p><p>In software engineering, we have a concept of being ‘<a href="https://en.wikipedia.org/wiki/Don%27t_repeat_yourself">DRY</a>’ i.e — don&#39;t repeat yourself. However, it&#39;s a crime to apply the same concept while managing software development. Clear, concise and constant communication is essential.</p><h3>Manage expectations</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*5lVkCtFpSsySzx-si8Ascg.gif" /></figure><p>Telling a client a feature cannot be built because it is out of scope is a hard thing to do , but it&#39;s something that has to be done. Its better to swallow the bitter pill and keep your client in touch with whats achievable rather than overcommitting under pressure and then eventually regretting it.</p><p>Being open and transparent about the state of a project not only allow you to focus but also helps your client prepare for any eventualities and avoid last minute disappointment.</p><h3>Build in iterations</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hr4U2XGIUiLGN0vFrMm51w.png" /></figure><p>Often times clients can get enamoured by features from several different sites and want everything together. Not only does that complicate your scope of work, it can also be detrimental to the user experience. Having small achievable milestones keeps the scope manageable and gives clarity of whats actually required as the application gets built.</p><p>For startups, whose ideas are really raw to begin with, I strongly recommend <a href="http://siamcomputing.com/building-an-mvp-the-lean-startup-way/">building an mvp first</a> and then spiralling out as the product gets more traction.</p><h3>Have things written down</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*o4EXafF5iwh3-hHSz5CH6Q.jpeg" /></figure><p><a href="https://en.wikipedia.org/wiki/Chinese_whispers">Chinese whispers</a> are fun but let&#39;s avoid them when building a custom application. Having stuff written down helps keep everyone on the same page and avoid being in a situation where it ends up being one person’s word against the other.</p><p>It does not always have to be long elaborate documents that can take forever to write, it could be something as simple as a basecamp discussion to a simple todo list that you and your client share.</p><h3>Summing it up</h3><p>Software development is all about how humans interact with each other to build something out of just a simple thought, so its natural that the whole thing can get quite complicated. But following some of the simple pointers mentioned here can help in a long way. Of Course, what i have highlighted is just the tip of the iceberg and there are several other nuances to managing and building a successful application. Stay tuned for more on the topic.</p><p>Let me know your thoughts and experiences working with clients/devs in the comment section below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f59196f976b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/siam-computing-thoughts/how-to-love-your-developers-101-5f59196f976b">How to love your developers — 101</a> was originally published in <a href="https://medium.com/siam-computing-thoughts">Siam Computing Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building an MVP the Lean Startup Way]]></title>
            <link>https://medium.com/siam-computing-thoughts/building-an-mvp-the-lean-startup-way-67840ca3b322?source=rss----9af082d1f58d---4</link>
            <guid isPermaLink="false">https://medium.com/p/67840ca3b322</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[mvp]]></category>
            <dc:creator><![CDATA[Sivasankari]]></dc:creator>
            <pubDate>Fri, 27 May 2016 13:18:55 GMT</pubDate>
            <atom:updated>2016-05-27T13:39:47.512Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TxKhAs5F1jBKPYNCgpVcPg.jpeg" /></figure><p>Congratulations on putting that idea to work, yes, it takes a lots of guts to get on the path to entrepreneurship. Okay, so problem number one! You probably are flooded with too many ideas and advices. But the ground reality is that you don’t want too many of them to screw up your venture, so calm down now. Of all the advices that people have given you, you might want to check the ones given below.</p><h3>Customer First</h3><p>The vein of any business is customers. Is your idea good enough to drive customers? Is there a demand for your idea out there? If there is, what target audience are you catering? These questions will build the foundation of your business and give it a sturdy beginning.</p><blockquote>“User experience is everything. It always has been, but it’s undervalued and underinvested in. If you don’t know user-centered design, study it. Hire people who know it. Obsess over it. Live and breathe it. Get your whole company on board.”</blockquote><blockquote>– Evan Williams, Co-Founder, Twitter</blockquote><p>Evan Williams said it right, user experience is everything! Your idea and implementation should revolve around your users. Too many startups begin to build a product without ever letting their customers use it. Let your customers be a part of your business since day one, let potential target audience know you’re building a so and so product. It will determine if the prospective customers will be interested or not.</p><p>Go out in the market and start asking people what they feel about your idea. Conduct surveys and talk to them face to face if you have the opportunity. You’ll really get to find the core of the problems; start working on their solution right away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2LkIFT0pfKLdv76v.jpeg" /></figure><h3>Fail Fast , Move Forward , Iterate</h3><p>Start building, don’t wait. This is the key to making a name in your industry. You can correct the course as you go along. Don’t believe us? Read the quote:</p><blockquote>“You don’t learn to walk by following rules. You learn by doing and falling over.”</blockquote><blockquote>– Richard Branson, Virgin Group Founder</blockquote><p>Developing a MVP (Minimum viable product) solely means continuously improving the product for higher user satisfaction. That’s how your business will grow, that’s how you will save tons of capital. The question is, how will you do it? We tell our fellow entrepreneurs to work smarter instead of harder. Your whole team should be aware of the fact that, apart from saving your hard earned capital, their duty will be to tailor-make an efficient process which revolves around the development of a super responsive product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/0*wPlBJBIGnKy8x1YO.jpeg" /></figure><h3>Objectives, Not Features</h3><blockquote><em>“A thousand no’s for every yes”</em></blockquote><blockquote><em>– Apple Inc.</em></blockquote><p>Having the right focus and prioritising what’s most important will help you build an effective MVP.</p><p>Just keep in mind to make it as simple as possible. At this MVP stage, it’s not about the product, it’s about your objectives. There is no need to add features which aren’t necessary in the beginning. Just find the features which will help you realise if you actually solve your customer’s problem the way you intended to.</p><p>Measure this impact, learn from it, and tweak your product until you find the tractions points where your customers get actually addicted to your solution. You should know in advance what you want to learn, not to get all over the place. This is the Build-Measure-Learn feedback loop, that will help you hustle in the right direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0QM4LY9SbxVNJxqg.jpg" /></figure><h3>Do It Right or Die Trying</h3><p>Here is the catch; user satisfaction will not come in the first attempt. However, we believe that it is not impossible.</p><p>Most startups which start building their products end up all frustrated. The reason behind this lies in the fact that they’re unsuccessful in creating a measurement system which analyzes the process in detail. If you are unable to find out about how well your prototype is doing, then you might as well consider that all efforts may go down the drain.</p><p>You need to identify weaknesses in the MVP and without any delay, start working on a better MVP based on the feedback. If needed, set a new value proposition, new measurements systems, to take your product with a new outlook.</p><h3>Stay Focused and Get Things Done</h3><p>Together, we will be focusing on strategies that will focus on this customer understanding. But hey, don’t forget, you’ll have to hustle hard to get your voice heard! That’s the only way it is done, don’t forget the old school lesson of entrepreneurship, which is (drumroll please!!), persistence of course.</p><p>So get yourself together now and be proud, you’re about to do something critically challenging. If all this rings a bell, <a href="http://siamcomputing.com/work/">check out our portfolio</a> and see what we’ve done for entrepreneurs like you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67840ca3b322" width="1" height="1" alt=""><hr><p><a href="https://medium.com/siam-computing-thoughts/building-an-mvp-the-lean-startup-way-67840ca3b322">Building an MVP the Lean Startup Way</a> was originally published in <a href="https://medium.com/siam-computing-thoughts">Siam Computing Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>