<?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 Gideon Adeyemi on Medium]]></title>
        <description><![CDATA[Stories by Gideon Adeyemi on Medium]]></description>
        <link>https://medium.com/@progee?source=rss-96b7ece9e873------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EBcdHerd6ZhojZE_5e9FmQ.png</url>
            <title>Stories by Gideon Adeyemi on Medium</title>
            <link>https://medium.com/@progee?source=rss-96b7ece9e873------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 06:05:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@progee/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[Building A Viable Product — Chunk The Process and Listen]]></title>
            <link>https://progee.medium.com/building-a-viable-product-chunk-the-process-and-listen-b3ee693062a8?source=rss-96b7ece9e873------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3ee693062a8</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Gideon Adeyemi]]></dc:creator>
            <pubDate>Tue, 28 Jun 2022 12:23:01 GMT</pubDate>
            <atom:updated>2022-06-28T12:25:58.487Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building A Viable Product — Chunk The Process and Listen</h3><p>When launching a product, your aim should be to launch something that people are happy to use and pay for. What this means is that going live with the minimum but effective features will ensure that your product is something that people would be happy to use, and for you it means minimum resources too. You can then begin to build additional features stemming from customers feedback, rather than on what you think they want.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fdUCmE2PMNa_pnFzJv6DxQ.png" /><figcaption>Chunk &amp; Listen!!!</figcaption></figure><p>Here, I’ll be describing how to launch with a small product and grow from there by listening to your customers.</p><h3><strong>Deciding On What To Launch</strong></h3><p>Companies without the resources to build a complete version of their product should release their product early with only the minimum features. On going live they will receive feedback and criticism on their product early. This helps to save time and cash for progressive development since they have an end-goal while sales may also help raise funds for the completion of the full product.</p><p>But this raises a lot of questions and objections. What is the perfect level of quality to include in it? How long (time) should you spend on it? Will your target users get onboard or not?</p><p>You might be starting small, but you need to write down a list of features that will make up your small but well formed product offering, something that people would be happy to use because it brings them value. To launch your product, I suggest that these two main things be considered:</p><ul><li>Who are my target customers?</li><li>What problems will this product solve?</li></ul><p>For Pennee, our target market was small business owners. The aim was to increase the speed of growth of their business with products tailored to provide them with business finance and help them understand their cash flow through visuals and analytics to foster better decision making. We started with the first customers we had in mind; majority being social media businesses and Freelancers: business owners who have access to an android or IOS device and can use it. This was an audience we knew well and importantly where people who knew us. I always advise that if you are building a product you target a market you already are well known in; this will make it easier to market, and for people to trust you.</p><p>We wanted it to be quick, so we handled the major features that will solve the problem of our target customers which was giving them access to loans and showing them what cashflow looks like in all their business accounts.</p><p>That was it. As we kept building, more ideas came to mind, so many features and possibilities, but we kept our use case and our customers in mind while continuously streamlining features until we had something that felt viable yet was as small as it could be.</p><h3><strong>If It Solves The Problem; Launch It!</strong></h3><p>Now that your product has been developed, you should launch with pride. You might have had lots of features that you wish your product had, but your customers don’t know that. If your target customer exists and has the problems that you’ve identified and your product solves these problems, then selling it to them won’t be hard. An advantage of launching quickly is that you can test whether all of those things work as you have planned and check if they are true before spending any more time and resources.</p><p>Market and sell the product as it is now, make sure you are accurate in presenting the scope of the product and the problems it will solve. When people start to use it you’ll start to get suggestions and requests for features. Some of the things you have already identified will likely come up as requests; but in my experience, customers will have needs that you didn’t even think about, and they will be very happy to tell you about them.</p><h3><strong>Build Right</strong></h3><p>The term MVP has been wrongly used to justify sub-standard product experiences where quality is discarded for the sake of speed.</p><p>When building something entirely new, a prototype with bugs can be good for learning. But in the present day it doesn’t work in most cases, you’ll be competing in spaces where other product owners have already set the standard for quality, in this case a poor experience can produce wrong results.</p><p>If you’re the first to market, then you might be able to get away with releasing a buggy build. But if you’re coming as a new product in a saturated space, as most companies are nowadays, discarding quality can strongly affect your growth and result in bad reputation.</p><p>As much as you are trying to build fast, build right!</p><h3><strong>If They Are Willing To Pay For Your Product; Listen to Them!</strong></h3><p>Understand your users and their various breeds.</p><p>The early adopters are special types of customers willing to take a risk on your new product or service. They can immediately see its potential to solve a critical problem — and they have the budget to purchase it if it’s priced. Not all customers fit this profile.</p><p>Characteristics of these users include:</p><ul><li>They have a problem that your product will solve.</li><li>They know that they have this problem.</li><li>They’ve been searching for a solution, and are in dire need of it.</li><li>They have already tried ineffective solutions.</li><li>They can quickly acquire the funds needed to afford a product that can solve their problem.</li></ul><p>This set of customers are not buying your product, they’re buying your vision. There’s absolutely no one who is under the assumption that the first version of a product is the final solution.</p><p>The major thing to note when building MVPs is that a deficient product will not impress anyone, neither the early adopters nor normal users. The early adopters may help with initial activities around your product, signups, users and customers, but they won’t be loyal to a poor performing product.</p><p>Products that fail to give their users that “Wow” effect and a feeling of satisfaction will churn their user and customer base as quickly as they acquired them.</p><p>You will always have people who are keen to tell you exactly what you should build for them. Getting to launch means that you can start getting feature requests and ideas from your active customers. Requests from people who are excited to use or pay for your product are far more valuable than requests from people who are not. Actively using a product or paying for it changes a person’s relationship to it and to the company building it. The customer feels reasonable asking for the service and features that they would expect as a dedicated user.</p><h3><strong>Choose The Features That Matter Without Straying Off Your Core Use Case</strong></h3><p>Understanding your core use case and the initial problems your product is intended to solve is very important when deciding which features to add to the product. Try your best not to stray from your product’s vision, even after a while from launching the first version of Pennee’s product the basic way people use our product has not changed, instead the product has improved.</p><p>There would be no good reason to add a feature if it will complicate your basic use case. You need to be open to telling customers that the additions they are asking for wouldn’t fit the product, and understand that some of those users might go elsewhere. You can’t please everyone.</p><p>Getting feature requests from users after a successful launch can’t be avoided. Although this is superb! But it can be overwhelming. The important questions are “how do I even begin to provide all of these new features”, and how do I explain to my users why their requests will not be immediately added or even added at all?</p><p>At Pennee we have always been clear to our users that the features that benefit the largest volume of users will be prioritized. We review requests that our users have sent back to us through different means and look for the feature demands that can be found in what people are trying to do with the product. The results are then studied and weighed in level of importance with respect to our core use case, this then helps us to infer if a feature is needed, where it is needed, and when it can be included.</p><h3>Be Aware! It Doesn’t Always Increase Sales</h3><p>I’ve always been of the notion that new features will increase sales, I mean… why not? It’s new, It’s what they want — why won’t the sales increase rapidly.</p><p>But I learnt, it took me a while to understand that adding a new feature is not a big marketing win. We’ve added some nice and frequently requested features to Pennee over time. But, going live with new features has never spiked sales.</p><p>This doesn’t mean adding features is not important. You need to understand that existing users appreciate new features: This makes it evident to them that the product is actively being improved for the sole purpose of their satisfaction. However, placing your target at acquiring new users when a new feature is launched is not the best approach in my experience. Instead, channel more energy into your marketing activities and on finding new customers and users, in addition to developing new features that make existing users want to refer you to more customers. This way your model is balanced and you can continue to serve your users while acquiring new ones and growing organically.</p><h3>In Conclusion</h3><p>Building in chunks, having a clear idea of who your target customer is and of the problems that your product is intended to solve, is a great way to launch a product. The quality of your product is much more than beautiful interfaces or your product’s performance. Deep understanding of your customers, paying attention to the tiny aspects of your products and ensuring you have the trust of your ideal users goes a long way in improving your product’s quality.</p><p>As you keep building, do not forget your target users. Add new features as this helps you continuously satisfy your existing users and makes your product useful to a broader market.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3ee693062a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>