<?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 Varun Vohra on Medium]]></title>
        <description><![CDATA[Stories by Varun Vohra on Medium]]></description>
        <link>https://medium.com/@varunvohra?source=rss-d4d6eb75da47------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5YWPcoBZv7qYQNM78HXOUA.jpeg</url>
            <title>Stories by Varun Vohra on Medium</title>
            <link>https://medium.com/@varunvohra?source=rss-d4d6eb75da47------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:18:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@varunvohra/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[One simple hack to increase empathy and ownership in teams]]></title>
            <link>https://medium.com/@varunvohra/one-simple-hack-to-increase-empathy-and-ownership-in-teams-ad897d4daeb9?source=rss-d4d6eb75da47------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad897d4daeb9</guid>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[ownership]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Varun Vohra]]></dc:creator>
            <pubDate>Fri, 19 Jul 2019 05:21:40 GMT</pubDate>
            <atom:updated>2019-07-19T05:21:40.286Z</atom:updated>
            <content:encoded><![CDATA[<h3>One simple hack to increase empathy and ownership your team</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wIQfq8E1nqhh8iI0_ifR5Q.jpeg" /></figure><p>Culture eats strategy for breakfast. Yes, we all get it. Now what?</p><p>As any entrepreneur or business leader will tell you, proactively crafting a productive culture, one that is also geared towards high growth, is quite the task. Preventing it from diluting as you scale — that’s a next level challenge. Startups tend to put together their own <em>culture code</em> of sorts. It’s basically a set of values that strongly define who they are and who they want to be. These lists can range from three to ten values, sometimes even more.</p><p>I recommend against making this list too long. Three to five is the ideal number, preferably just three — making them memorable and easy to propagate. The best company cultures I’ve encountered are always great because of their <em>strength</em> not their complexity or nuances. That is to say, regardless of what core values a team has, it performs well when everyone strongly believes and aligns with those values.</p><p>In reality, a teams (or startups) culture is rarely ever shaped by what’s written on their walls or the contents of their culture code. It is shaped by what leaders signal to be acceptable and unacceptable behaviour. By extension, leaders’ own actions send the strongest signals and if they don’t match their words, well that’s all together a different problem. Regardless of what values your team or startup may have, there are 2 that I’ve found to be very commonly held — empathy and ownership.</p><p>Why? Because a culture with high levels of ownership and empathy is very important for high growth startups. Everything is in chaos, things are breaking everywhere because with fast growth comes the need to evolve people, processes and technology. In this situation it’s often easier for people to have lower empathy and over time, develop lower ownership. To that end, I’ve found that instituting a simple rule within your team can go a long way to reinforcing both these values.</p><h3>Don’t point out a problem until and unless you have at least one viable solution for it.</h3><p>Easy enough, isn’t it? Enforcing this practical rule has helped me a lot in ensuring my teams worked well together with high levels of ownership. In all honesty, this was not a “first principles” solution. It was a just reaction to me struggling with several of my teams complaining a lot about everything and losing objectivity and productivity.</p><p>It started when a sudden growth spurt caused my team to double in size. With more than half the team having just come in, and us having to deliver incrementally more impact, there wasn’t enough time to have everyone ramp-up, develop bonds and then start collaborating. We needed to hit the ground running, so we did. Well, kind of.</p><p>A couple of months into this journey, the quarter was closing out and we just weren’t able to get our shit together. People across functions and teams seemed to have an excuse for most things — “I can’t finish because ABC hasn’t done XYZ” or “The way LMN has done this means that we won’t be able to do PQR”. It was driving me nuts. In hindsight, it was a lack of sufficient communication both top-down and laterally within the teams. While trying to figure out what to do, I decided I was tired of hearing why something couldn’t be done or why something wasn’t working. So I enforced this new rule.</p><p>It worked. Within a week, I found that people had begun collaborating much more. There were new relationships being forged and suddenly things started moving. Suffice it to say that the next quarter had very visible impact, the teams did great. Since then, I’ve used this as a “team policy” more than a couple of times, and it’s helped everyone including myself from losing ownership and empathy.</p><p>In reality, it works because it forces team mates to do two things whenever they encounter a problem:</p><ol><li>Understand why the problem exists</li><li>Learn about how their cross-functional team mates work and what challenges they face</li></ol><p>Without these two, it’s unlikely that people will identify a viable solution. The first step of understanding the problem tends to foster a natural sense of ownership. You can’t just see an issue and say “Hey this is a problem (for someone else to solve)”, you need to get involved and go deeper into why it exists and how you can possibly solve it. The second step is a by-product of needing to understand a problem and brainstorm viable solutions for it. Most often, people would share problems that are outside their area of expertise or functional control to address. Now, they had to find time to sit with their teammates and learn more about the issue and it’s current solutions if any. This naturally led to greater empathy within the team, especially for one-another.</p><p>My personal experiences with this hack so far have been positive. If you’ve tried this or something similar in your company, I’d love to hear how it went. <br>If not, do try this out and let me know how it went :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad897d4daeb9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The most overlooked trait when hiring for startups]]></title>
            <link>https://medium.com/@varunvohra/the-most-overlooked-trait-when-hiring-for-startups-be9214954c17?source=rss-d4d6eb75da47------2</link>
            <guid isPermaLink="false">https://medium.com/p/be9214954c17</guid>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[hiring-tips]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[hiring-for-startup]]></category>
            <dc:creator><![CDATA[Varun Vohra]]></dc:creator>
            <pubDate>Mon, 15 Jul 2019 05:42:12 GMT</pubDate>
            <atom:updated>2024-07-09T03:29:25.878Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sVd-1GJJozTJ3ElCFw6IQw.jpeg" /></figure><p>For the past 9 years, I’ve been building teams at startups. For the first 5 years it was for my own 100% bootstrapped, B2B services business. For the next 4 years it was for the company we sold our first venture to — a B2C healthcare product startup with $200M+ in funding. Over that time I’ve found very few “universal truths”, you know — things that are almost always applicable in any scenario. One of those is “that no matter what business, industry, scale or geography you’re in, pulling together the right team is always a top priority”.</p><p>In this time period, I’ve taken somewhere between 3000–3500 interviews. <br>Many mistakes were made and I’ve also found some amazing people to work with. Naturally, I’ve read loads about hiring. Ways to find talent, evaluate talent, take un-biased interviews, trait vs behavioural vs past performance, etc.</p><p>I’ve never before written about it myself, largely because most of my learnings have come from great content already published by many people across the world and making my own mistakes. Today, however, another story caught my eye — <a href="https://medium.com/@nicolascole77/what-makes-a-great-startup-employee-these-9-traits-4ae53c69f0e9">What makes a great startup employee? These 9 traits</a>, written by <a href="https://medium.com/u/7c10a61aa346">Nicolas Cole</a>. He’s put together a great list and it reads really well.</p><h4>But there is one trait that I think is missing. One trait that I don’t recall reading about in all this time across many different publications. <strong><em>Autodidacticism</em></strong>.</h4><p>Think about it. Skill sets are re-invented regularly. Most startups aren’t doing different things, they are doing things differently. Cut and dry, copy and paste approaches rarely work in such environments. Even when they do, they stop working in a short period of time because companies pivot or processes need to evolve. Change is the only constant.</p><p>In that environment, most teams don’t have dedicated senior members who are domain / subject matter experts across everything. Even when there is great, experienced talent, the shortage of time and ever expanding ToDo lists preclude any dependable mentoring and training. People figure out what needs to be done and then <em>figure out how to do it</em>. Yes, it’s usually that simple.</p><p>In engineering teams in particular, I’ve found autodidacticism to be an invaluable trait, but the need is no less significant across other functions. People who are self learners go and find the best way to do something, experiment with new tools, technologies, processes, approaches all the time.</p><p>Continuous learning in a chaotic environment is challenging for everyone, but people who embrace it tend to make great startup team members.</p><p>Side Note: — It’s easy to conflate autodidacticism with “self-starter” and while there is similarity or correlation between these traits, they are not the same. I’ve seen instances where high ownership individuals pick up work all over the place and take on projects themselves that they know how to execute and later get stumped on tasks that require crossing ‘unknown ground’ so to speak.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be9214954c17" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Identifying  Great Engineers (10x or otherwise)]]></title>
            <link>https://medium.com/@varunvohra/identifying-great-engineers-10x-or-otherwise-ff89d4cbdf22?source=rss-d4d6eb75da47------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff89d4cbdf22</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[talent-acquisition]]></category>
            <dc:creator><![CDATA[Varun Vohra]]></dc:creator>
            <pubDate>Sat, 13 Jul 2019 07:07:46 GMT</pubDate>
            <atom:updated>2019-07-16T17:46:19.421Z</atom:updated>
            <content:encoded><![CDATA[<h3>Identifying Great Engineers (10x or otherwise)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*csqpgoE3UUyh-aUsqycOfw.jpeg" /></figure><p>Lately, the internet has blown up with <a href="https://twitter.com/ashleymayer/status/1150536868162953216">memes of the 10x</a> individual — a mythical creature 10-times better than the average individual of their kind. One of them is the 10x engineer. But as luck would have it, the 10x engineer is a real creature, and contrary to what the memes would have you believe, he (and it’s usually a ‘he’) can’t fart rainbows and certainly can’t find Chuck Norris. Nonetheless, while it’s hard to accurately pin down the numerical difference, a single person can produce more and better results than multiple individuals in many creative (non-procedural) roles, and this is the idea behind the “10x engineer” as well. Some engineers have been known to deliver significantly higher impact in their roles than their counterparts.</p><p>Recently, Shekhar Kirani, an investor at Accel India, <a href="https://twitter.com/skirani/status/1149302828420067328">tweeted about the 10x engineer</a>. He raised a very important question: how do you spot one? Unfortunately, his answers simply highlight the bias and distortion of context around engineering talent.</p><h3>Specifically, they’re not reliable indicators of performance. They are low emotional-quotient (EQ) stereotypes found in TV shows.</h3><p>To be sure, there are two kinds of engineering roles: the individual contributor (IC) who becomes an architect, and the people-manager (PM) who, well, manages people. Kirani was talking about ICs in general while some of the responses (<a href="https://twitter.com/BriannaWu/status/1150087966079049730">like this one</a>) describe PM-type engineers. While we need both kinds of engineers to build a great team and product, the 10x engineer usually pertains to the IC.</p><p>For every amazing engineer with the ‘easy-to-spot’ traits that Kirani lists out, you’re likely to find four or five that have the same traits but not the same professional ability. This is because great engineers tend to have overdeveloped IQ and an underdeveloped EQ (especially in India, from personal experience) in the early stages of their careers (first 5–10 years). This isn’t to say these individuals were born like this, rather that Indian engineering colleges prioritise intellectual development over emotional development. So it’s commonplace to find engineering graduates of average ability and with an underdeveloped EQ.</p><p>This is also why it’s dangerous to use this as a proxy for potential or capability, because mis-identifying them can cause toxic outcomes for the rest of the team even as it will fail to contribute productively to your business or product.</p><p>While there probably isn’t a one-size-fits-all description of what greatness is in any field. As a proxy, here are the six common traits of most great engineers, basis my experience so far.</p><ol><li><strong>They read and think more than they write code</strong>. Apart from the first couple of weeks learning something brand new (which is filled with excitement and lots of learning-by-doing-and-breaking) people who spend more hours in a day reading and thinking, make better engineers. They don’t find it a challenge to write code, learn syntax, alter configurations, implement a new library, etc. They find their challenges in identifying the underlying nature of problems, in studying them to discover the nuances that need to be accounted for when developing a robust solution.</li><li><strong>They make great mentors.</strong> An underdeveloped EQ, often coupled with no desire to improve it, makes them bad managers and multitaskers and possibly even bad leaders (though most fortune 500 CEOs have traits reflecting lower EQ scores). They do however excel at mentoring another bright engineer. One-on-one. They even enjoy it. They also tend to develop a Batman and Robin vibe with some of their mentees — where they prefer to work with someone rather than alone.</li><li><strong>They test their own code.</strong> Partly due to an eagerness to see their work brought to life and partly from a desire to spot and rectify their own mistakes. They take bugs reported by testers and in production very personally. They are embarrassed by downtimes and production issues in systems owned by them. These traits naturally drive them to excellence over time, regardless of what they knew or didn’t when they got started. I’ve never heard a great engineer say, “We need more testers in the team”.</li><li><strong>They are confident in their basics and always curious for new specifics.</strong> Whether learning new technologies, solving new business problems or building new features — they are very quick to understand the fundamentals of the statement and always eager to dive into the specifics. Those nuances are what gives them an opportunity to think and create. This enables them to simplify the codebase and increase re-usability. The rest is just gravy.</li><li><strong>They make career decisions differently. </strong>They usually revel in the strength of challenges presented to them at work. The more they are challenged, the more they rise to the occasion. They often don’t care enough about business metrics in and of themselves. They don’t like marketing but always want to tackle problems of scale because they will be new and unique to every product. Team size, compensation, office perks, etc are usually not strong considerations at all in making decisions (but can sometimes can be helpful in generating initial interest). They will care about how the company views quality over speed, what scale the platform has, how architectural decisions are made in the company, etc.</li><li><strong>They find time to refactor their own code.</strong> Early in their careers, great engineers try to obsess over perfection of their code, attempting to refactor it before they even write it. With some maturity, they stop doing this and always write code in the best way they know how at any given moment of time. Though what sets them apart in this regard is that they often find time to refactor their old code. No one asks them to. No one gives them free time to do so. I think it’s simply a form of OCD, when they learn a better way to do something, they automatically think about where else in their older code this would have worked better. Then it’s just a matter of time before they go back and make those changes quietly, for their own satisfaction.</li></ol><h4>Please don’t judge engineers by their choice of laptop themes, text editors or based on their introversion.</h4><p>Identifying great talent is by no means a science, I don’t believe it can (at least as of 2019) be codified and repeated without human intervention. Hopefully these pointers will help non-technical folks in the ecosystem spot great engineers and gain a better understanding of and working relationship with them.</p><p>Finally, let me say that I have limited experience. I’ve been programming for about 13 years and hiring and building teams for 9 years. The views expressed here are entirely based on that experience and I make no claims to having a silver bullet or holy grail for finding or acquiring great engineers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff89d4cbdf22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 simple thumb-rules to help prioritise your minimum viable product (MVP)]]></title>
            <link>https://medium.com/@varunvohra/factors-in-making-an-mvp-d4c3db37ee97?source=rss-d4d6eb75da47------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4c3db37ee97</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <dc:creator><![CDATA[Varun Vohra]]></dc:creator>
            <pubDate>Fri, 11 Nov 2016 04:12:31 GMT</pubDate>
            <atom:updated>2019-07-16T04:29:04.147Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ObNXgmvKaewVQ-PqmelfA.jpeg" /></figure><p>The <a href="http://theleanstartup.com/">lean startup</a>, <a href="http://agilemanifesto.org/">agile workflow</a> and <a href="http://en.wikipedia.org/wiki/Minimum_viable_product">minimum viable product</a> (MVP) are all the rage in the software startup community. Over the last five years, I&#39;ve seen them go from underground buzz words discussed only by a cabal or two, to <a href="http://www.techrepublic.com/blog/tech-decision-maker/pmis-agile-certified-practitioner-a-cert-is-born/">mainstream adoption</a>. There have always been and always will be, naysayers to any revolution that emerges. The lean business and agile methodologies are neither passing fads nor marginal utility concepts (such as: <a href="http://www.businessnewsdaily.com/7233-snapchat-marketing-business.html">how you can use snapchat for business</a>!) — they are at the core of how modern business works and will work for the coming decades.</p><p>While the Lean Startup and MVP principles have taken center stage, there is chatter around a concept called <a href="https://medium.com/@mcjohnson/the-minimum-lovable-product-f9cc5c0bdda">minimum loveable product</a> (MLP), which is centered around the fact that most software is meant to be consumed by humans and ‘viable’ isn&#39;t an appropriate state. It may be a likely candidate for the buzzword of 2015 but that remains to be seen. Rand Fishkin, the cofounder of <a href="http://moz.com/">Moz</a>, coined yet another term — the <a href="http://thenextweb.com/dd/2014/10/22/maximizing-minimum-viable-product-get-high-results-without-releasing-minimal-product/">exceptional viable product</a> (EVP), which has an interesting take about ensuring that the MVP is polished before it’s launched publicly.</p><p>It’s started to feel like much ado about nothing. As someone who actually builds software (and a lot of it with and for startups), these concepts have become increasingly difficult to differentiate between and put into practical use during the early stages of software creation. At <a href="http://genii.in/">Genii</a>, we have been following an MVP approach for a long time, and the challenges that arise while a product is evolving from the concept stage to it’s public launch tend to be similar across products. There have been countless conversations and heated debates, all of which have led to a set of useful questions that I believe every product manager should ask themselves when taking product decisions.</p><p><em>To be perfectly clear: this is not a rigid set of rules to be adhered to, rather a checklist of different approaches for product managers as they think about adding and removing features for a MVP. They are not in any particular order.</em></p><ol><li><strong>How much does it hurt?</strong></li></ol><p>Software generally creates alternative workflows for user behaviours that pre-exist offline (in some cases, new software creates brand new behaviours). Typically in good software, these new workflows are simpler than their offline counterparts. When deciding about a particular feature, think about the existing solution that users have and determine how significant the challenges present are. Taking user interviews is a good way to ascertain this since as an individual you won&#39;t always have the correct perspective. The more the pain, the more important the feature should be.</p><p><strong>2. The empty room scenario</strong></p><p>There are plenty of features that have exponentially higher value as they are used over time. Take GMail for example, one of the most significant features is the awesome search. When a user has been using his or her email account for a couple of days, how much do they really use or care about the search? Take another example, reports and graphs for student performance in a software targeted at schools — these would become far more useful as time passes and more data is available on each student. Sometimes, every customer will find a feature useful but if it’s likely to be used only after a certain time, you may want to leave it out of your MVP.</p><p><strong>3. Relative frequency of usage</strong></p><p>Far more useful for secondary or tertiary user stories (features), it’s a good idea to look at how often a user will access or use a certain feature. Take for example a site-wide ‘notifications’ feature. Within this, you could have desktop alerts, automatic updation (without page reload), archival and viewing, filtering or segmentation of the notifications. Unless notifications is one of the most used features, it might not be a good idea to build all that out in the MVP. Let people use the product with basic notifications and their behaviour will tell you exactly how you can improve or add to the feature.</p><p><strong>4. Will multiple actors use this feature?</strong></p><p>Some software products have different types of users, either by the well known role based categorisation or by the more user experience centric profile based categorisation. When deciding if a feature should be built sooner rather than later, it’s useful to consider what percentage of your potential users as well as what different types of users will it impact.</p><p><strong>5. How much is it worth to the decision maker?</strong></p><p>Now I know most purist product managers will flame me for adding this into the mix, but sometimes (more so for business-to-business and enterprise products) the only reason to ensure a feature makes it into your MVP is the perceived value it has for the person(s) responsible for making the purchase decision. A common example, iPad based analytics which would only be used by the CEO or a handful of users out of hundreds could help the sales team convince a potential customer to buy.</p><p>I&#39;ve left out other criteria that are and should be regularly used to make product decisions, I don&#39;t believe it’s possible to create a complete list— after all, this isn&#39;t an algorithmic process. Generally, startups have passionate founders who take the final call on how their product will evolve and what will or won&#39;t make it into the MVP. However, what many startups don&#39;t have is a seasoned product manager — someone who lies at the intersection of user psychology, customer feedback, interface design, technology and sales. That’s a lot to ask from a single team member, and yet, that’s the role.</p><p><em>Note: All products are subject to the constraints of launch timelines and development costs, and as such they always play a role in determining what the MVP looks like. However, most of those decisions tend to be more quantitative than qualitative which is why I&#39;ve avoided speaking of them in this article.</em></p><p>I&#39;d love to discuss this further so feel free to leave a comment about what factors you take into consideration when defining a solid MVP.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4c3db37ee97" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thinking through your technology choices.]]></title>
            <link>https://medium.com/@varunvohra/technology-stacks-e12cefa75e94?source=rss-d4d6eb75da47------2</link>
            <guid isPermaLink="false">https://medium.com/p/e12cefa75e94</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Varun Vohra]]></dc:creator>
            <pubDate>Fri, 27 May 2016 05:56:01 GMT</pubDate>
            <atom:updated>2016-05-27T06:00:02.096Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*LAOhusePGVvYZDq9vqvzlg.png" /><figcaption>Decision trees can be oh so beautiful. Alas, not always helpful!</figcaption></figure><p>Over the past several years, I&#39;ve built and launched multiple software products for a number of clients. Many of them were consumer facing web applications, while a few were business tools meant for internal use. All of them were on the cloud, no exceptions. Between them I&#39;ve used many different technologies and 4 core languages, namely Ruby, PHP, C# and JavaScript. Do you know what each and every one of these products had in common? The people behind the products (entrepreneurs, CXOs, small business owners, product heads), all asked me this question:</p><blockquote>What technology should we use for this new product we&#39;re building?</blockquote><p>No one has ever failed to ask me this question, that too with the tone of utmost importance. Even when there is a technologist behind the idea, with a pre-existing belief that this question has a right answer (which they know), they still ask. After years of repetition, it has just become annoying. Do you know another thing that each and every one of the products I&#39;ve built had in common?</p><p><em>Not one of their customers gave a damn about the technology that was used.<br></em><strong><em>Not one.</em></strong></p><p>Nowadays, when people ask me what technologies they should use for their product, I just don&#39;t know how to answer. Truth be told, while customers don&#39;t care about your technology choices, those choices <strong><em>do</em></strong> matter for your project or startup.</p><h4>Don&#39;t let it matter for the wrong reasons.</h4><p>Whenever I&#39;ve had a conversation on technology stacks, the reasons why people believe it matters seem legit. It’s amazing (and I&#39;m thankful) that no one has actually said to me that their end users will care about it. However, the concerns that arise when discussing technology choices tend to fall squarely into a few popular categories.</p><p><strong>Viability:</strong> Can this be done using this technology?</p><p>The answer is almost always ‘Yes’. A good idea, especially in the world of web and cloud based applications, can be built using almost any technology. In the past 3 years, only one exception comes to mind. I had to build a <em>cryptographic algorithm validation tool that needed to work in kernel space </em>for which the only real choice was using C. Now if that’s the kind of product or app you&#39;re looking to build, there might be some limitations, if not — the world is your oyster.</p><p><strong>Scalability:</strong> Will this technology be able to handle a 100 million users?</p><p>This is a genuine concern that many founders / project owners have. The internet is filled examples of products that started out well and failed to reach critical mass because of constant outages and technical failures. What they probably don&#39;t know is that engineering quality, infrastructure and application architecture determine scalability and reliability far more than the underlying technology used to build the product.</p><p><strong>Reliability: </strong>Have other successful products been built using this tech?</p><p>Every technology has pros and cons which you will have to make your peace with. Some offer speed of development while others offer more robust testing frameworks. From everything I know right now, there is no proven correlation between the technology used and the success of a project / startup.</p><p>There is only one real reason why your technology stack is important — <strong><em>different technologies have different engineering cultures</em></strong>.</p><p>Good engineers care about the technology they use. Their views on workflows, relevance of testing/spec writing/documentation/community contributions all get strongly influenced by the technology they use. For example, engineers that work primarily in .NET technologies will typically not value open source software the same way that engineers that use Node.js would.</p><p>In the end, the technology you choose impacts your team’s culture. Like all team building and culture creation, this is an upfront decision that has long term effect since it’s difficult to change. If you have a CTO or technical cofounder, go with the technology that he or she is most comfortable with. If you don&#39;t have a technical partner helping you make this decision, try using relevant business metrics to make one.</p><p><em>Personally, I love the MEAN and Ruby on Rails tech stacks and the engineering cultures associated with them. If you want to know more about why, you can check out these </em><a href="https://www.youtube.com/playlist?list=PL2BD1EBB51965F61C"><em>9 short videos</em></a><em> on youtube ☺</em></p><h4>Making an informed decision isn&#39;t easy.</h4><p>If you&#39;re reading past this point, I&#39;ll assume that you (and your partners / team) don&#39;t have a technology background. If you have an existing team, please don’t worry about choosing a technology — just roll with whatever they are happy and comfortable with. Focus instead on things that will affect the success of your product or venture. When you&#39;re just starting out and there is no existing team in place, there are four key factors you can look at to help you decide.</p><p><strong>Community</strong></p><p>The size of the community for a particular technology plays an important role in determining how many ready-to-use libraries, components, integrations are readily available online for your team to use. Even more significantly, it impacts the speed with which your team will be able to overcome technical hurdles — all engineers help their fellow engineers (it’s like the bro code). An easy way to discover the size of the community is to visit stackoverflow.com and check how many users follow a particular technology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/0*_kXw3wd5XKHUxhFi." /><figcaption>some of the most popular technology ‘tags’ on stackoverflow</figcaption></figure><p><strong>Hiring</strong></p><p>Finding good talent is always a challenge and you don&#39;t want your technology choices to further increase the difficulty of assembling a great team. Having said that, if you choose a cutting edge technology, you might be able to attract some very talented engineers since they won&#39;t get many opportunities to work in those technologies in other organizations. One of the simplest ways to discover the size of the talent pool for a technology is to search for it on popular job boards. Keep in mind that you need to search within geographic constraints since concentrations of technology specializations are not the same everywhere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/0*LZMiNtptc7nEsRBU." /><figcaption>naukri.com results for nodejs devs in mumbai</figcaption></figure><p><strong>Costs</strong></p><p>Like with any marketplace, the economics of supply and demand are always at play in the job market. So when you find fewer people with a certain skill, it’s almost certain that they will come at higher price points. The nice thing about this is that they tend to be better engineers since technologies that aren&#39;t extremely popular are usually self-taught and not the first language that they learn. The other factor of cost is license fees. Proprietary technologies such as .NET or Oracle, even Windows, come with costs attached to their commercial use. These license fees may seem affordable in the early stages, but as your business scales they can really hurt, even more so when you meet a competitor that mentions his/her open source stack costing nothing at all.</p><p><strong>Time to market</strong></p><p>While always an important consideration, time to market becomes even more important if you&#39;re a startup or an early mover in an industry. Certain technologies have frameworks and functionalities that enable them to build web apps faster than others. Other aspects might suffer in such choices, but as I&#39;ve already mentioned, any choice you make comes with a business trade-off. For example, Ruby on Rails as a framework makes rapid prototyping easier for web applications while some Java based frameworks make it a more time consuming process.</p><p>Technology choices matter, but they aren&#39;t critical to your success. I hope after reading this you decide to spend a limited amount of time on making this choice and focus your efforts on defining your MVP, marketing your product or raising the capital you&#39;ll need to sustain yourself till you make it big. Be clear on the engineering culture you want and the right technology will find you.</p><p>Lastly, remember that <a href="http://www.wikiwand.com/en/Divorce_demography">statistically</a> picking a technology is like marriage, there’s more than a 50–50 chance you&#39;ll find someone younger and sexier before the decade’s up.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e12cefa75e94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Entrepreneurship in India: Batteries Not Included.]]></title>
            <link>https://medium.com/@varunvohra/entrepreneurship-in-india-batteries-not-included-513b7359a08a?source=rss-d4d6eb75da47------2</link>
            <guid isPermaLink="false">https://medium.com/p/513b7359a08a</guid>
            <dc:creator><![CDATA[Varun Vohra]]></dc:creator>
            <pubDate>Wed, 07 Jan 2015 06:34:21 GMT</pubDate>
            <atom:updated>2015-01-07T08:51:40.805Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XkE2VUsGSNF8ZtRh5ZpCeg.jpeg" /></figure><p>At 23, out of college I decided to start a software company in Mumbai and was supercharged by all the news I read online on TechCrunch, Mashable, Hacker News, etc. The geek in me, who remains enthusiastic to date, said, “This should be easy. I can hack together anything!”.</p><p>My close friend and business partner, a designer, could make anything look beautiful. After that, we would find some people to join us in our crazy mission and then we&#39;d go get some funding. Clients, convinced of our genius, would roll in and inevitably we&#39;d be left with figuring out the cool and smart things we could say when the press came calling. All the new and young billionaires being minted in Silicon Valley only reaffirmed my confidence in this vision — that I would retire by 30, having done my part, and pocketed billions along the way.</p><p>Ha. Today, that vision seems so idealistic and unencumbered by reality, and yet without that fearlessness (read: ignorance) I probably never would have started <a href="http://genii.in/">Genii</a>. Still, there are things I wish someone had told me back then, not to deter me from starting my own venture but rather to prepare me for some of the challenges that are specific to starting up in India and not the valley. Looking back, and being surrounded today by entrepreneurs, hackers, investors, and visionaries creating new realities, there are a few things that every person trying to startup in India should know are just different.</p><p><strong>Don’t ‘change the world’, solve a real problem.</strong></p><p>I love the concept of <a href="http://www.opentable.com/">Open Table</a> and often wanted such a product in India. We actually brainstormed about attempting to do it ourselves. Each member in the team listed down their 10 favourite places to eat in the city and we checked 45 restaurants (there were overlaps) for three key requirements and this is what we found. Please note, this is in Mumbai — the commercial capital and largest city in India.</p><ul><li>A computer with sales software (24 out of 45 had)</li><li>An internet connection (18 out of 45 had)</li><li>A process or practice for reserving tables (24 out of 45 had)</li></ul><p>My key takeaway from this was that India is a developing country and there are far too many real world, schlep-filled, non-software problems that need solving, for example: training waiters in computer skills or improving internet connectivity.</p><p>This is why in the past decade, broadly, investors in India tend to not buy the ‘this will change the world’ Kool-Aid, though I believe it will improve a lot in the coming years. Also, in India, investments are spread far more widely across industries than in the valley, which focuses primarily on technology.</p><p>Solve a real problem that customers in India will pay for today, not some day in the future. This basically rules out most ‘social network’ like ideas, which need years of user growth before you can even begin to effectively monetize the platform. Keep in mind that I&#39;m talking about revenues, not profits. If you can show an investor revenue growth with profitability on the horizon, there’s game there.</p><p><strong>Grow like Jack’s beanstalk!</strong></p><p>At Genii, we’ve kept a firm 100% to 150% year on year growth rate. I believed that doubling the business was a good pace,<a href="http://techcrunch.com/2013/08/24/how-fast-should-you-be-growing/">many articles</a> I’ve read about start ups (barring truly disruptive ones like Facebook and Google) indicated that 80% to 130% growth rate for the first five years is very respectable.</p><p>Because of the growing economy, interest rates are 5 to 6 times higher than in the USA. What this means for entrepreneurs is that an investor in India will expect a much higher yearly growth rate / return on his/her money than one in the valley, and so should you. For context, a couple of the consumer centric companies that I know and recently had a series A / B / C round, had insane growth curves — like 15% every month (ie 535% annual growth). For more on why this matters, look up <a href="http://www.forbes.com/2004/01/27/0127artofstartmidas04.html">cash-on-cash return</a> and cost of capital.</p><p>There’s a positive corollary to this though: India is a nascent market for most ideas and the scope for growth is also proportionately higher.</p><p><strong>Don&#39;t take public utilities for granted.</strong></p><p>India has been and will likely remain an Agricultural economy for the foreseeable future. It follows naturally that technology can and should be pushing the known boundaries of agriculture in the country. It isn’t. In Europe and America, <a href="http://worldagritech.rethinkevents.com/technologyshowcases">agri-tech startups</a> are doing crazy things — from cloud based supply chain management to real time crop monitoring. But in rural parts of India, access to electricity, computers and internet connectivity is extremely limited, so these are just not going to fly, yet.</p><p>India has power outages in every major city; one such incident at the wrong time can cause your startup serious damage. Network connectivity is limited, even within urban areas. India has a handful of newly seeded accelerators and incubators for start-ups, but it’s still rare to see someone give advice and office space for equity.</p><p>These things are really important because an idea that worked in the States might have an even stronger use case in India, but it would be a loss-making business if the required infrastructure is missing or shaky. Be sure to isolate your startup from as much of this as possible, ie have a secondary internet connection, use laptops that won&#39;t go off as soon as the electricity dies, etc.</p><p><strong>Bro, is there a cheaper one, maybe from China?</strong></p><p>Indians are raised to be price sensitive; they significantly prioritise price over quality and are willing to haggle and walk away from deals. Clients will frequently cite American companies, saying things like “It should work like this, see Facebook has that feature” or “The app should be designed like Tinder”. At the same time, blissfully ignoring that those companies had and paid for some of the best talent in the world!</p><p>Costs are lower in India, and that is leveraged by many an American company by outsourcing work to here, but you can only ever get what you paid for — something many customers in India don&#39;t fully comprehend. While the trend is skewing positive in the long run, when compared to the States, Indian consumers are still averse to paying for software. Indian companies, however, are not as averse to paying for technology — ease of sales is important when deciding what you&#39;re going to do.</p><p>Find a business model that doesn’t depend on price differentiation, if you don&#39;t, sooner or later, you will lose out to a chinese company.</p><p><strong>1,000,000 Graduates = 100 passionate and capable millennials</strong></p><p>Enough has been spoken about <a href="https://www.google.co.in/search?q=start-ups+needing+to+have+a+strong+culture&amp;oq=start-ups+needing+to+have+a+strong+culture">start-ups needing to have a strong culture</a>, and in the Valley there are some common traits which appeal to me personally: honesty, transparency, autonomy, accountability, flatter organisation structures, etc. Culture is determined by a collective of people, not one person, and in India much of the younger workforce don’t value startups despite their immense role in an active economy. There’s also a pervading ‘chalta hai’ attitude of mediocrity in most rungs of society which you have to push past.</p><p>However, there are plenty of professional, intelligent, and motivated people around — it’s just harder to find them and motivate them to risk a startup life. I&#39;m hopeful that the well-published successes of <a href="https://www.zomato.com/">Zomato</a>, <a href="http://www.flipkart.com/">Flipkart</a> etc. are painting a new — more attractive — picture which bodes well for the ecosystem.</p><p><strong>Start a company regardless.</strong></p><p>A a child, what I wanted more than anything was a remote controlled Batmobile with blue lights that glowed. My heart leapt when I saw the wrapped present — my very own Batmobile. The world was a blur around me as I opened the box and pulled the toy out. It didn&#39;t work. After minutes of panic, despair and frantic fiddling with the toy, I finally read on the side of the box — “Batteries not included”. I hated it then, and hate it still, the jarring difference between my expectations and reality. The fact is, had I known that batteries wouldn’t be included, I would have still bought the toy, much same way I would have still started Genii having known these things.</p><p>These are just some of the geographic challenges to tackle intelligently and persevere through. There are opportunities in India like few others in the world; access to technology, capital, and intelligence are easier now than they&#39;ve ever been in my short lifetime.</p><p>All of this is based on my limited experience, do share your thoughts on starting up in India in the comments section below.</p><p>The original article can be seen <a href="http://genii.in/posts/entrepreneurship-in-india-batteries-not-included">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=513b7359a08a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>