<?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 Ritesh Nagpal on Medium]]></title>
        <description><![CDATA[Stories by Ritesh Nagpal on Medium]]></description>
        <link>https://medium.com/@ritesh_nagpal?source=rss-8a818e6653c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-ex89-fPxJE-GrEI.jpg</url>
            <title>Stories by Ritesh Nagpal on Medium</title>
            <link>https://medium.com/@ritesh_nagpal?source=rss-8a818e6653c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:28:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ritesh_nagpal/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[The very first brand!]]></title>
            <link>https://medium.com/@ritesh_nagpal/the-very-first-brand-2666adb35a4d?source=rss-8a818e6653c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/2666adb35a4d</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Ritesh Nagpal]]></dc:creator>
            <pubDate>Sat, 30 Apr 2016 08:46:00 GMT</pubDate>
            <atom:updated>2016-04-30T04:30:15.302Z</atom:updated>
            <content:encoded><![CDATA[<p>The biggest irony of a start-up ecosystem is that everybody wants to go to heaven but no body wants to die. It all sounds very exciting to work at a challenging place, but sacrificing the current salary from the stable job is not easy. The features of the new product sounds too appealing and fitting ones requirements, but most of the customers are not very comfortable with risking hard-earned money on some geeks. Even the investors face the same dilemma of choosing the potential start-up from the huge list of funding applications they get on the daily basis. <br> <br>Apart from building the dream product or service in limited budget, all the founders have to manage the daunting situation of attracting their first few employees, the first set of customers and the first angle investors. Most of the founders consider their business idea to be the first major brand that attracts the attention. However, the fact is that the very first brand a start-up has is its founders.</p><p>The potential employees, customers and investors look out for the trust-worthy founders who can actually make the idea work. There is always a fine line between genius and insanity, and in a way, the traits of the founders tell a lot about the future of a start-up. Here are some pseudo v/s real traits of this first brand.</p><h4><strong>Academic record v/s Street Smartness</strong></h4><p>To larger extend, no educational system measures street smartness very accurately. Don’t get carried away with the multiple degrees or academic records a founder has. Always look for the basic street smartness that is needed to stir the company from the initial garage days to a successful company.</p><h4>Experienced v/s novice</h4><p>Age is another deceiving factor when it comes to evaluating the capability of the founders. One school of thought supports energetic, young, fresh out of college guys while other vouches for the experienced lot. A good founder is always ready to learn yet confident enough to articulate his/her ideas to the world. Listen to the founder to know more about this.</p><h4>Speaker v/s Listener</h4><p>Founders are generally full of ideas and always ready to pitch in the unique business idea that they are having. However the real trait is to have good listening capability. An idea goes through lots of improvisation on the execution lane. Unless the founders are good listener to customer needs, market demands and technical challenges, they may probably fail to make necessary amendments to their ideas.</p><h4>Dreamer v/s Visionary</h4><p>Most of the literature on start-ups and the celebrity founders advocate dreamers. However, being a dreamer doesn’t take anyone closer to success. The real difference comes from converting a dream into a vision. A clear vision that can lead set of people to make thing happen. Ultimately it’s not just about thinking big, it’s about making it work on a grand scale.</p><h4>Business sense v/s Common Sense</h4><p>Many revolutionary start-ups are not actually built on contemporary business sense. Let it be the product features, pricing, payment models or customer interactions most of the successful start-up’s business models could not have made perfect business sense initially. By sticking to the common sense, they have made all the differences. The same is true for a founder. It doesn’t require an MBA degree to establish a good business, but common sense will do just fine.</p><h4>Creator v/s Destroyer</h4><p>Creativity &amp; entrepreneurship are generally considered similar. A person who is good at creating a product or service is treated as a good candidate for a successful start-up founder. In a start-up journey, failure is the only constant companion one has. One may require to scrap the idea and start afresh or look for an alternative. While evaluating a founder, always look for his or her ability to destroy something that he or she has created. Moving on is the only survival instinct that keeps a start-up floating in the initial days.</p><h4><em>Junoon v/s Jugad</em></h4><p><em>Junoon </em>or passion is another misleading trait that is connected with a potential founder, however the key trait is to have <em>Jugad </em>or resourcefulness. More than 50% of the hurdles one comes across in running a start-up is non-technical and not related to the central business idea. Be it hiring or finding a suitable office space, the most time consuming problems of a start-up require deep out-of-the box and quick thinking. Passion alone is not helpful here. One needs to be extremely resourceful to make it work.</p><p>For a very long time, the founders of a start-up remain the only brand of the company. Gradually the products and services start speaking for the company and the founders become mere brand ambassadors. The transition from being the only brand of the company to be one of the brand ambassadors of the company is the true measurement of the success of a founder.</p><p><em>Originally published at </em><a href="http://howstartupworks.blogspot.in/2015/01/the-very-first-brand.html"><em>howstartupworks.blogspot.in</em></a><em> on April 30, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2666adb35a4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Defective By Design : 5 Tips for Better Product Management]]></title>
            <link>https://medium.com/@ritesh_nagpal/defective-by-design-5-tips-for-better-product-management-9fdab6dd1b46?source=rss-8a818e6653c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fdab6dd1b46</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[mvp]]></category>
            <dc:creator><![CDATA[Ritesh Nagpal]]></dc:creator>
            <pubDate>Tue, 26 Apr 2016 19:01:04 GMT</pubDate>
            <atom:updated>2016-04-26T19:01:04.030Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever come across a product that is defective by design? It leaves a bad taste in your mouth, no matter how many engineering hours have been spent on that product. Here are 5 tips to ensure that your product doesn’t fall in that category.</p><h3>MVP v/s POC</h3><p>MVP, is the highly misunderstood concept in the start-up world. Theoretically, it is a minimum viable product that can be released to the end customers. However, to reduce the feature set and time-to-market, key features are jeopardized and the end customer gets a product that is defective by design.</p><p>Proof of Concept (POC) is a small bridging task that proves that the entire product/services will work out. It is not a complete product itself. It is just a validation that assumes that all other parts of the product/services are working as expected. In most of the new product or services, the majority of innovation happens at integrating different pieces or defining bridging technology. While this is the most important part of the product/but, but not a complete product itself. The POCs should just be treated as the first step to the product development and not the complete product itself.</p><p>While defining your MVP, always keep in mind that a MVP compromises on the features but not on the purpose of the product. The picture* below summarizes it perfectly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*L5kPy5xHrrrSbN7F.png" /></figure><h3>Plurality of Customers</h3><p>In a simplistic form of product development, the features are defined keeping the end-customer in mind. However, the complex nature of business enforces several unseen customers in the ecosystem. If these unseen customers are neglected during the product definition, you may end up with a product that works pretty well with the end-customer but fails to reach them. Lets take example of a glass break detector. Thinking about the end-customer, you might have designed the aspect ratio, basic features, on-off LED sequence etc for the product, but is your product really ready for a system integrator for adding it into a security panel? Have you ensured that integration APIs are following a standard protocol? Have you considered the installation team as your customer and provided them all the details for mounting the sensor or some LED sequences to ensure that they get some feedback while configuring the sensor?</p><p>There are always more than one customer of your product. And a good product, as well as MVP, should cater all of their needs.</p><h3>WTFM</h3><p>A software developer is aware of a very common term, RTFM (Read The F**king Manual). Lately the complex nature of software and branching philosophy of software manual have made user-manuals so out of fashion. If you have no idea what am I talking about, try reading MSDN API guide. The rise of open-source community has also made user manuals almost extinct. The philosophy of easy design are also pushing more and more efforts on having a user-manual free product. As a product manager/developer, if you are also planning to join the current trend and save efforts on writing a user-manual, consider the following points:</p><ul><li>Unlike open-source community, your product is still not available to the open public. It doesn’t have the big enough user-base who can help others to ‘understand’ your product.</li><li>If you are aiming at your design to do all the work and avoid user-manual altogether, you must spend enough budget on design. You are the better judge of the budget you have allocated for the design, so take a bet :)</li></ul><p>To summarize, just Write The F**king Manual and make sure that all the developers, testers, users, sellers, distributors and support engineers understand your product. You don’t need to stick to the plain old style of writing verbose documents, understand your customers and create the content accordingly. It could be a flow-chart, a presentation, a video, a document, a form or a website, but just WTFM.</p><h3>Simple is Smart</h3><p>Keeping it simple is the simplest advice for your product development. But believe me it is the most difficult one to follow. Don’t create a product to out-smart your customers or impress your investors or demonstrate your superior development skills. Keep it simple because simple is the new smart. If your product is not simplifying any of the existing method/product or philosophy, you should probably not launch that product. Period.</p><h3>User Interface v/s User Experience</h3><p>Fortunately, our decade appreciates the importance of good design. Gone are the days, when a basic working product was more than sufficient. A good amount of efforts are spent on defining a good interface, decide the right color combination, the correct theme for the product. The overall budget on user-interface has grown multi-fold in the last decade. However, a good user interface is not a cure of the bad user experience. The overall user experience, starting from buying to getting the support, should be considered from the early stages of the product development.</p><p>Hopefully, you will find these guidelines relevant to your product development. Feel free to share your experience on avoiding a product which is defective by design.</p><p><strong>*I have found this beautiful picture perfectly depicting MVP on LinkedIn but couldn’t locate the original source. If you are aware of the original source, please let me know.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fdab6dd1b46" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>