<?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 Samuel Olusesi on Medium]]></title>
        <description><![CDATA[Stories by Samuel Olusesi on Medium]]></description>
        <link>https://medium.com/@samuelolusesi?source=rss-c190fc7eb2eb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NkjeHv9rgGs5eHJMHU0i9g.jpeg</url>
            <title>Stories by Samuel Olusesi on Medium</title>
            <link>https://medium.com/@samuelolusesi?source=rss-c190fc7eb2eb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:03:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@samuelolusesi/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[Product Documentation: Necessary or Too Much?]]></title>
            <link>https://medium.com/design-bootcamp/product-documentation-necessary-or-too-much-80a70e5dc454?source=rss-c190fc7eb2eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/80a70e5dc454</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[documentation]]></category>
            <dc:creator><![CDATA[Samuel Olusesi]]></dc:creator>
            <pubDate>Sat, 13 Dec 2025 00:45:43 GMT</pubDate>
            <atom:updated>2026-01-27T12:18:58.946Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is really long overdue, having experienced as a product manager, the negative effects of improper or no documentation, I thought to write this. Here is my humble contribution to the body of work in product management!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eS4QKmOuIVQrIsuMd4EwDA.png" /><figcaption>Image showing Product Documentation</figcaption></figure><p>The truth is that product management in real life is completely different from theoretical product management. Still, one thing is as important in practice as it is in theory, and that’s documentation.</p><p>I’ll start with two stories. I was leading the implementation of a referral feature to add virality to a product, which is a major pillar in Product Led Growth (PLG), and I had created the PRD and shared it with the product team to go through before our sprint planning session. But during the session, misalignment was coming up on the acceptance criteria, everyone had ideas on what would be considered as done for that feature, but with the help of documentation; I was able to recentre everyone, some tweaks needed to be made (as a PRD should ideally be a working document and not a static one), but we aligned and completed the feature implementation on time.</p><p>I’ve also had situations where I come into a product organization, and there’s basically no documentation and it was a big struggle; no context on how far they had gone or what was being worked on, a lot of misalignment everywhere and just by introducing agile methodologies primarily Scrum, better documentation and clear tasks for everyone linked to the overarching outcomes; delivery efficiency was significantly improved.</p><p>Now let’s give a definition for product documentation; Product documentation are artefacts created to do two things: ensure alignment and bring clarity concerning the product and in the product development process.</p><p><strong>Types of Product Documentation</strong></p><p>The two broad categories are System Documentation and User Documentation. Let’s see the breakdown below:</p><p><strong>System Documentation:</strong></p><p>This involves documentation created for internal teams, and for the sake of the product focus of this article, I’ll only be mentioning the ones used by Product Managers. Some examples are:</p><p><strong><em>Product Requirement Document (PRD)</em></strong><em>:</em> This is a major document for PMs, and it usually contains feature specifications, user stories, epics, acceptance criteria, success metrics, goals and details needed for product development. There’s usually some difference in different organisations, but the core is typically the same.</p><p><strong><em>Product Roadmaps</em></strong>: This is basically a working document to guide the evolution of a product over time. It should never be static, as user needs and market trends develop, so should roadmaps. Agility is a must as we operate in very dynamic environments. They can be of different types, but I’ll name two;</p><ul><li>High-level Roadmap — This typically articulates the high-level direction of a product without going into the specific details or features necessary to achieve those outcomes, i.e. in Q1, we plan to reduce fraud by 15% through KYC implementations. They flow along these lines and highlight the themes to be worked on.</li><li>Feature Roadmap — This is much more granular and goes in depth, into the features needed, and helps guide the engineering team in the development process.</li></ul><p><strong><em>Product Backlog</em></strong>: This is a living artefact that contains a prioritised list of all work items related to the product, including features, enhancements, bug fixes, and technical tasks. It reflects current product priorities and evolves continuously based on user feedback, business needs, and new learnings. While the structure and tooling may differ across organisations, the core purpose remains the same: to ensure the team is always working on the most valuable work next.</p><p><strong>User Documentation:</strong></p><p>This refers to documentation created to help end users understand, adopt, and use a product effectively. While these artefacts are often owned by support or growth teams, Product Managers play an important role in ensuring they accurately reflect product functionality and value.</p><p>Some common examples include:</p><p><strong><em>User Guides:</em> </strong>These provide step-by-step instructions for using the product or specific features. They are designed to help users complete tasks with minimal friction and gain confidence in using the product.</p><p><strong><em>Help Centre:</em> </strong>These are searchable, self-service resources that address common workflows and issues. They help users find answers quickly and reduce reliance on customer support.</p><p><strong><em>FAQs:</em> </strong>FAQs offer quick answers to common questions around product usage, limitations, pricing or policies. They are often a user’s first point of reference.</p><p><strong><em>Onboarding Documentation &amp; Product Tours</em>: </strong>These guide new users through their initial experience with the product, helping them reach value faster. Effective onboarding documentation plays a key role in activation and early retention.</p><p><strong><em>Release Notes:</em> </strong>These communicate product updates in a user-friendly way, focusing on what changed and why it matters to the user rather than internal implementation details.</p><p>In summary, I’ll say this: system and user documentation serve different audiences, but they work toward the same goal: building better products. System documentation ensures teams are aligned on what to build and how to build it, while user documentation ensures the value created is clearly understood and realised by users.</p><p>Together, they reduce ambiguity and enable teams to build efficiently. In fast-moving product environments, strong documentation isn’t a luxury but a necessary aspect of the product development process.</p><p>Till next time, keep learning and keep building.</p><p>Cheers 🥂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80a70e5dc454" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/product-documentation-necessary-or-too-much-80a70e5dc454">Product Documentation: Necessary or Too Much?</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Discovery]]></title>
            <link>https://samuelolusesi.medium.com/product-discovery-3345f3bbd129?source=rss-c190fc7eb2eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/3345f3bbd129</guid>
            <category><![CDATA[product-discovery-process]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-discovery]]></category>
            <dc:creator><![CDATA[Samuel Olusesi]]></dc:creator>
            <pubDate>Fri, 17 Jan 2025 15:27:58 GMT</pubDate>
            <atom:updated>2025-01-17T15:27:58.108Z</atom:updated>
            <content:encoded><![CDATA[<p>The basics of product discovery</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ynzVdRymff3kRNpJsvdAWg.jpeg" /><figcaption>Product Discovery Image</figcaption></figure><p><strong>Product discovery</strong> is a key step in creating great products. It helps teams focus on solving real problems for users instead of just adding “cool” features.</p><p>The process is all about understanding what users need and building solutions that work for them. It’s not just about launching features; it’s about creating products that bring real value.</p><p>Here’s what a good product discovery process achieves:</p><ol><li><strong>Business viability</strong> — The product makes money for the business and doesn’t cost more than it earns in the long run.</li><li><strong>Technical feasibility</strong> — The team can build the product using available tools and skills.</li><li><strong>User value</strong> — The product is easy to use and solves important problems for users.</li></ol><p>Product discovery should be ongoing and always come before building the product. This way, you can adapt based on feedback and stay agile.</p><h4><strong>The Process of Product Discovery</strong></h4><p>Here’s a step-by-step guide to doing product discovery:</p><ol><li><strong>Understand the Problem</strong></li></ol><p>Start by learning everything about the problem you want to solve. As a product manager, you should know the industry and the challenges inside out, whether it’s in supply chain, finance, or any other field.</p><p><strong>2. Talk to Users</strong></p><p>Find out what users really need by collecting data:</p><ul><li><strong>Interviews</strong>: Ask open-ended questions to learn how they solve the problem today, how much it costs them, and why it matters.</li><li><strong>Surveys</strong>: Use surveys or feedback from your sales and support teams.</li><li><strong>Support Tickets</strong>: Look at frequent issues reported by users to spot gaps in your product.</li></ul><p><strong>2. Brainstorm Solutions</strong></p><p>Once you understand the problem, gather your team to come up with ideas. Use prioritization methods like:</p><ul><li><strong>RICE</strong>: Rate ideas based on Reach, Impact, Confidence, and Effort.</li><li><strong>MoSCoW</strong>: Sort ideas into Must-haves, Should-haves, Could-haves, and Won’t-haves.</li></ul><p><strong>3. Create Prototypes</strong></p><p>Test your ideas by building simple versions of the product:</p><ul><li>Start with basic sketches or wireframes.</li><li>Move to detailed designs using tools like Figma or InVision as your ideas evolve.</li></ul><p><strong>4. Test Your Ideas</strong></p><p>Share your prototypes with real users to see how they work:</p><ul><li>Watch how users interact with your designs.</li><li>Run experiments, like A/B tests, to see what works best.</li><li>Collect feedback and refine your ideas based on what you learn.</li></ul><p><strong>5. Keep Learning</strong></p><p>Product discovery doesn’t end after launch. It’s a continuous process:</p><ul><li><strong>Feedback</strong>: Look at user reviews, adoption rates, and pain points after launch.</li><li><strong>Improve</strong>: Use what you learn to tweak and improve the product.</li><li><strong>Stay Connected</strong>: Keep talking to users and stakeholders to find new opportunities.</li></ul><p><strong>6. Work with Delivery Teams</strong></p><p>Make sure discovery insights are ready for the build phase:</p><ul><li>Write clear user stories that explain what needs to be done.</li><li>Work closely with developers to align on goals and scope.</li><li>Share updates with stakeholders to keep everyone on the same page.</li></ul><h4>In Conclusion…..</h4><p>Product discovery is the secret to building products that truly matter. By understanding problems, listening to users, and improving constantly, you can create products that meet business goals and make life better for users.</p><p>If you found this valuable, I’d love to hear your feedback and do feel free to share it with other product folks in your network.</p><p>Until next time, cheers! 🥂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3345f3bbd129" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Agile Methodology: A Beginner’s Guide]]></title>
            <link>https://medium.com/design-bootcamp/understanding-agile-methodology-a-beginners-guide-17629714c8ac?source=rss-c190fc7eb2eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/17629714c8ac</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile-development]]></category>
            <dc:creator><![CDATA[Samuel Olusesi]]></dc:creator>
            <pubDate>Sat, 16 Nov 2024 23:35:21 GMT</pubDate>
            <atom:updated>2026-01-27T12:18:54.365Z</atom:updated>
            <content:encoded><![CDATA[<p>A simplified breakdown of agile product development</p><figure><img alt="A Picture depicting agile in action" src="https://cdn-images-1.medium.com/max/684/1*CLbqVHR5hYre70AJg7g2pw.png" /><figcaption>Agile in action</figcaption></figure><p>In today’s tech ecosystem, the term “Agile” is commonly used. We hear about Agile coaches and various frameworks, from Scrum to Kanban. But for beginners in software development, it can be a bit overwhelming. This article aims to break down Agile in the simplest way possible, along with all the key terminologies.</p><p>Let’s start with a bit of history: <em>How did Agile come to be?</em></p><h3>The Evolution from Waterfall to Agile</h3><p>Before Agile, software development followed the Waterfall methodology. Waterfall was effective in its time, especially when user needs and market demands changed slowly before the digital age. It could be said to have been adapted from Henry Ford’s 1913 assembly line model, however; it was first documented in a 1970 paper titled “Managing the Development of Large Software Systems” by Winston W. Royce. It was inspired by the rigid, linear nature of manufacturing processes, including assembly lines, and was adapted to the context of software development, it was characterized by:</p><ul><li><strong>Linear Progression</strong>: Each task is completed in a specific order, with each phase finished before the next begins.</li><li><strong>Rigid Phases</strong>: The project is divided into distinct stages, such as requirements gathering, design, development, testing, and deployment.</li><li><strong>Fixed Requirements</strong>: Requirements are set at the start and rarely change once the project is underway.</li><li><strong>Heavy Documentation</strong>: Extensive documentation is produced in each phase.</li><li><strong>Limited Customer Involvement</strong>: Customers are usually involved only at the beginning and end of the process.</li><li><strong>Inflexibility</strong>: Waterfall doesn’t easily accommodate changes during the development process.</li></ul><p>While this approach worked for many years, the internet age introduced the need for faster development and more iterative feedback. This led to the rise of Agile.</p><h3>The Birth of Agile</h3><p>Agile was officially introduced in 2001 when 17 software developers created the <strong>Agile Manifesto</strong>. These technologists — Kent Beck, Mike Beedle, Arie Van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, and Dave Thomas — outlined four key principles for better software development:</p><ol><li><strong>Individuals and interactions over processes and tools</strong><br>People and teamwork come first. Collaboration and communication matter more than rigid processes or fancy tools.</li><li><strong>Working software over comprehensive documentation</strong><br>Delivering functional software is the top priority. While documentation is important, it shouldn’t slow down progress.</li><li><strong>Customer collaboration over contract negotiation</strong><br>Agile emphasizes working closely with customers throughout the development process, rather than sticking rigidly to a contract.</li><li><strong>Responding to change over following a plan</strong><br>Plans are helpful, but flexibility is key. Agile teams adapt quickly to changes, understanding that in tech, things often don’t go as originally planned.</li></ol><p>These principles laid the foundation for Agile methodologies, which focus on faster product development, quicker feedback loops, and flexibility to meet evolving market demands.</p><h3>What Agile is (and isn’t)</h3><p>While Agile promotes faster iterations, customer involvement, and flexibility, it’s important to note that being Agile doesn’t mean you abandon essential processes like documentation or customer interaction altogether. Agile is about finding the right balance to build the right product at the right pace.</p><h3>Popular Agile Methodologies: Scrum and Kanban</h3><p>Let’s take a look at two of the most widely used Agile frameworks: <strong>Scrum</strong> and <strong>Kanban</strong>.</p><h4>Scrum</h4><p>Scrum is a framework that uses time-boxed iterations, called <strong>Sprints</strong>, to deliver product increments. A Sprint typically lasts from 1 to 4 weeks, where the team works on specific tasks and reviews progress. Some key Scrum components include:</p><ol><li><strong>Scrum Roles</strong>:</li></ol><ul><li><strong>Product Owner</strong>: Represents stakeholders, prioritizes the product backlog, and ensures maximum value delivery. There’s some debate in the product management world about whether the Product Owner should be a separate role or handled by the Product Manager (since there’s no clear career path for Product Owners), but that’s a topic for another day.</li><li><strong>Scrum Master</strong>: Facilitates Scrum processes, removes impediments, and ensures adherence to Scrum principles.</li><li><strong>Development Team</strong>: Cross-functional professionals who develop the product increment.</li></ul><p>2. <strong>Artifacts</strong>:</p><ul><li><strong>Product Backlog</strong>: A prioritized list of work that needs to be done, and maintained by the Product Owner.</li><li><strong>Sprint Backlog</strong>: A subset of the Product Backlog that the team commits to completing in the current Sprint.</li><li><strong>Increment</strong>: The usable and potentially shippable product at the end of the Sprint.</li></ul><p>3. <strong>Events</strong>:</p><ul><li><strong>Sprint Planning</strong>: A meeting where the team decides what work will be done during the Sprint.</li><li><strong>Daily Scrum</strong>: A brief, 15-minute meeting where the team discusses progress and obstacles.</li><li><strong>Sprint Review</strong>: A meeting at the end of the Sprint to demonstrate the completed work and gather feedback.</li><li><strong>Sprint Retrospective</strong>: A reflection session where the team discusses what went well and what could be improved.</li></ul><h4>Kanban</h4><p>Kanban is another popular Agile framework that focuses on visualizing work and improving efficiency. Here are its key components:</p><ol><li><strong>Kanban Board</strong>: A visual tool that represents tasks as they move through various stages of completion (e.g., To Do, In Progress, Done).</li><li><strong>Work Items</strong>: Tasks or units of work that are visually represented as cards on the Kanban board.</li><li><strong>Work In Progress (WIP) Limits</strong>: A cap on the number of tasks that can be worked on at any one time, to prevent overload.</li><li><strong>Flow Management</strong>: Focuses on optimizing how tasks move through the system, using metrics like cycle time and lead time.</li><li><strong>Continuous Improvement</strong>: Encourages regular reviews to identify inefficiencies and improve workflows.</li><li><strong>Explicit Policies</strong>: Clearly defined rules on how work should be handled at each stage of the process.</li><li><strong>Pull System</strong>: Tasks are “pulled” into the workflow as capacity allows, rather than being pushed onto the team.</li></ol><h3>Other Agile Methodologies</h3><p>While Scrum and Kanban are the most common Agile methodologies, there are others worth exploring:</p><ul><li><strong>Extreme Programming (XP)</strong></li><li><strong>Lean Software Development</strong></li><li><strong>Crystal Methodologies</strong></li><li><strong>Dynamic Systems Development Method (DSDM)</strong></li><li><strong>Feature-Driven Development (FDD)</strong></li><li><strong>Agile Unified Process (AUP)</strong></li></ul><h3>The True Essence of Agile</h3><p>Adopting Agile isn’t about simply using a framework — it’s about creating value in a sustainable, iterative, and flexible way. As long as you’re delivering results that are aligned with market needs and able to adapt, even if you mix frameworks, you’re on the right track.</p><h3>Conclusion</h3><p>Agile is not a one-size-fits-all approach; it’s about finding what works for your team and project. Whether you’re using Scrum, Kanban, or a different methodology, the core values of Agile — flexibility, collaboration, and customer-centricity — will guide you to success.</p><p>That’s it for today’s deep dive.</p><p>Until next time, cheers! 🥂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17629714c8ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/understanding-agile-methodology-a-beginners-guide-17629714c8ac">Understanding Agile Methodology: A Beginner’s Guide</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User feedback is everything!]]></title>
            <link>https://medium.com/people-in-product/user-feedback-is-everything-24a784bb78f6?source=rss-c190fc7eb2eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/24a784bb78f6</guid>
            <category><![CDATA[user-feedback]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Samuel Olusesi]]></dc:creator>
            <pubDate>Fri, 23 Aug 2024 22:48:18 GMT</pubDate>
            <atom:updated>2024-08-26T09:10:48.032Z</atom:updated>
            <content:encoded><![CDATA[<h4>The power of user feedback and how it can transform the game for you; with real-world examples and use cases.</h4><figure><img alt="A picture showing feedback highlighted; with rating, comment, survey, opinion, response, idea and advice as ways to get it" src="https://cdn-images-1.medium.com/max/940/1*UcMPDNpLc-DCEtLDI5o-7w.jpeg" /></figure><p>A few weeks ago, something happened that transformed my view on user feedback and re-emphasized its importance. My team and I were working on a product feature for our B2B product, and we were brainstorming various aspects of it. Ideas and insights weren’t aligned, which could have led to hours of back and forth. However, I had user interview data with clear insights, we went to it and that settled it. We went with the insights interpreted from the user engagements and built out the feature accordingly.</p><p>That’s my personal story, and that’s not enough to drive the point home, so let’s talk about other tech companies and professionals who’ve found user feedback to be a game-changer:</p><p><strong>Instagram</strong>, for instance, started as a location-based check-in app called Burbn. But the founders noticed something interesting — users were more excited about the photo-sharing feature than anything else. So, they pivoted, focusing entirely on photos, and the rest is history. Instagram became one of the most popular social media platforms globally because they listened to what their users wanted.</p><p>Then there’s <strong>Dropbox</strong>. Initially, they faced a big challenge: users didn’t get what Dropbox was about. People found the concept of cloud storage a bit confusing. But instead of pushing through, Dropbox took this feedback to heart. They simplified their messaging and created an explainer video that clearly explained how the service worked. This move was a game-changer, leading to a massive boost in user adoption.</p><p>Lastly, <strong>Slack</strong> started as an internal communication tool for a gaming company. But user feedback was clear — the communication tool was the real hero, not the game. So, they decided to focus entirely on Slack as a standalone product. Fast forward to today, and Slack is a go-to collaboration platform for businesses, especially tech companies, worldwide.</p><p>These examples highlight the power of gathering and implementing user feedback.</p><p>Now that you see the impact of user feedback, let’s talk about the types and how you can apply them:</p><h4>1. Qualitative Feedback</h4><p>This involves direct interactions with users, ranging from user interviews to focus groups. While it’s not the most popular because it takes more effort, it’s definitely the most effective.</p><p><strong>Application:</strong></p><ul><li><strong>Conduct regular user interviews:</strong> Reach out directly to users and schedule meetings if you have direct access, which is ideal. Being part of sales and customer support conversations also allows you to interact directly with your product’s users.</li><li><strong>Focus Groups:</strong> Create an unbiased combination of different user personas for your product to gather feedback.</li></ul><h4>2. Quantitative Feedback</h4><p>This is typically gathered in larger quantities than qualitative feedback and usually includes surveys, user behavioural data, customer support tickets, and more.</p><p><strong>Application:</strong></p><ul><li><strong>Surveys:</strong> Send out regular surveys to your users to get feedback and insights for product improvement.</li><li><strong>Behavioural Data:</strong> Monitor user behaviour via data points within the product using various analytics tools like Mixpanel and Google Analytics.</li><li><strong>Customer Support Tickets:</strong> Tickets raised by users provide invaluable insights into the usability issues they face, which are crucial for the product development process.</li></ul><p><strong>Note:</strong> Not all feedback is valuable. There’s noise in there too. Sift out the non-essentials with quality data interpretation and your product sense — this improves as you advance in your product journey.</p><p>That’s all I have for this edition. I trust it’s proven or reinforced the importance of user feedback in product development.</p><p>There’s more to come to enhance your product journey and knowledge, so give me a follow and sign up for the newsletter to get updates when new content is dropped.</p><p>Till next time,</p><p>Cheers 🥂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24a784bb78f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/people-in-product/user-feedback-is-everything-24a784bb78f6">User feedback is everything!</a> was originally published in <a href="https://medium.com/people-in-product">People In Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s talk tech ]]></title>
            <link>https://medium.com/design-bootcamp/lets-talk-tech-6ecddddce1fa?source=rss-c190fc7eb2eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ecddddce1fa</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Samuel Olusesi]]></dc:creator>
            <pubDate>Sun, 07 Jul 2024 16:44:03 GMT</pubDate>
            <atom:updated>2024-07-07T19:03:53.635Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A picture showing product management at the intersection between UX, Tech and Business" src="https://cdn-images-1.medium.com/max/720/0*yt6fdbngtmCeqWJD" /><figcaption>Image depicting the position of product management</figcaption></figure><p>The growth of technology adoption in the last two decades has been astronomical, bringing process optimizations and lower operations costs for businesses and organizations in the long run.</p><p>This adoption frenzy has brought more job opportunities and an even, with remote working options fast becoming a preference for most professionals.</p><p>Some popular choices are:</p><ol><li>Product Design</li><li>Product Management</li><li>Data Analysis</li><li>Software Engineering</li><li>Scrum Master</li></ol><p>All these are great options if transitioning to tech has been top of mind, but I’ll zero in on Product Management for now. I successfully transitioned to Product Management by transferring skills from my professional background, highlighting the transferrable skills and getting a fundamental understanding of the role.</p><p>So what is Product Management?</p><p>A simple definition of a product manager is someone responsible for identifying and understanding the user’s needs and translating them into products that give value to both the user and the organization. As a PM, you’re at the intersection between User experience (UX), Tech and Business.</p><p>Some companies separate them into Technical product managers with a technical background either in design or engineering and Product managers or growth PMs responsible for a product’s business and strategy aspect. Product managers are different from Project Managers because product managers are concerned with the delivery of a valuable product, while project managers are focused on KPIs and product delivery on schedule.</p><p>So if you’re interested in a user-facing tech role, you should check out Product Management; here are a few tips that helped me and I’m sure would do the same for you:</p><ol><li><strong>Take a course on Product Management</strong>: This would give you a basic understanding of who a product manager is and what the role entails. This won’t give you everything but will get you started.</li><li><strong>Apply yourself</strong>: The next step is to apply yourself; this could come in the form of; volunteer work- reach out to your network online or offline and volunteer your skills in the building of a product to get practical experience or product teardowns — this is also a good one, so select a product in the industry you’d like to enter and analyze the product breaking it into different categories and analyzing the features based on them and round it up with a feature suggestion for improvement, and go in-depth on why the feature is important and even come up with wireframes to support your use-case (Whimsical or Miro are good for wireframing) I’ve attached a detailed tear-down I did of Youtube at the end of the article, you can use that as a template.</li><li><strong>Build a portfolio: </strong>Put together the products you’ve worked on as well as tear-downs in a digital portfolio, it gives an easy overview to assess the extent of your PM abilities, Notion is a good one for this as well, I’ll write a later article on how to create a portfolio on Notion, so watch out for that sometime later</li><li><strong>Put yourself out there</strong>: This goes without saying, you’re your greatest cheerleader, so cheerlead away!</li></ol><p><strong>P.S</strong>, here is the link to the Youtube Teardown as promised: <a href="https://medium.com/design-bootcamp/youtube-product-case-study-707d98a83eb5">https://medium.com/design-bootcamp/youtube-product-case-study-707d98a83eb5</a></p><p>That’s it for now, trust this helps on your journey into tech.</p><p>Let me know your thoughts on tech and product management, I’d love to hear from you.</p><p>Till next time, keep the faith, keep growing and keep building.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ecddddce1fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/lets-talk-tech-6ecddddce1fa">Let’s talk tech 🛫</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Navigate Stakeholder Management as a Product Manager]]></title>
            <link>https://medium.com/design-bootcamp/how-i-navigate-stakeholder-management-as-a-product-manager-d6ea78be26ac?source=rss-c190fc7eb2eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6ea78be26ac</guid>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Samuel Olusesi]]></dc:creator>
            <pubDate>Sat, 16 Mar 2024 13:07:01 GMT</pubDate>
            <atom:updated>2024-03-18T10:03:58.597Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An image of a white person holding a compass for navigation" src="https://cdn-images-1.medium.com/max/1024/1*LKT01bm042vmFhrctohFJQ.jpeg" /></figure><p>In this article, we’ll be going on a journey where we’ll discover how to navigate stakeholder management as product managers.</p><p>Think of me as your tour guide for the day, let’s jump right in!</p><p>This is going to be very conversational but let’s set some ground rules, most likely as a junior or associate product manager, you’ll have product leaders who’ll give strategic direction for the product. In some companies, this is a Chief Product Officer, Chief Technology Officer, VP of Product or even the CEO and as much as you’re a PM who owns the product, get comfortable with executing the strategy of your leaders.</p><p>I had a conversation with a senior product manager and he gave me some nuggets, let’s go through them together:</p><ol><li><strong>Data-centricity</strong> — This is letting data be the core of everything that needs to be done, especially when handling feature requests or feature prioritization; let data be at the centre, talk to your users, conduct user interviews frequently, utilize surveys for quantitative research, product analytics as well, for proper user journey mapping.</li><li><strong>Business-mindedness </strong>— Be obsessed with the money, know how your product makes money now and how it should do it ideally and let that be at the core of handling feature requests; does it improve or affect the health of the business, those should be guideposts for you.</li><li><strong>Good Product Leadership</strong>-<strong> </strong>This speaks for itself, the benefits of good leadership are evident in the efficiency of product teams, so in all you aspire to be a good product leader and look out for product leadership before taking a new role.</li></ol><p>Now how do all these tie together in stakeholder management; with <strong>better data</strong>, you can properly handle requests from stakeholders especially when it comes to saying NO, you just let the data speak for you, likewise pitching product or feature ideas, data is your best friend in those scenarios. The same applies to being <strong>business-minded, </strong>you’ll relate better with the stakeholders and management becomes easier. The last speaks for itself.</p><p>That sums it all up, simple but effective principles, use them and you’ll see the change.</p><p>Till next time,</p><p>Cheers 🥂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6ea78be26ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-i-navigate-stakeholder-management-as-a-product-manager-d6ea78be26ac">How I Navigate Stakeholder Management as a Product Manager</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How artificial intelligence is revolutionizing agriculture]]></title>
            <link>https://medium.com/design-bootcamp/artificial-intelligence-in-agriculture-a-revolution-in-the-making-cbbb71948d19?source=rss-c190fc7eb2eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbbb71948d19</guid>
            <category><![CDATA[agriculture-technology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[agriculture]]></category>
            <dc:creator><![CDATA[Samuel Olusesi]]></dc:creator>
            <pubDate>Fri, 01 Dec 2023 07:42:31 GMT</pubDate>
            <atom:updated>2024-11-29T08:35:28.604Z</atom:updated>
            <content:encoded><![CDATA[<h4>This article contains an explanation of artificial intelligence and its application in agriculture</h4><figure><img alt="Pictorial representation artificial intelligence in agriculture" src="https://cdn-images-1.medium.com/max/1024/1*KfjF5PZwpEs_uKW9qra3Xg.jpeg" /><figcaption>Application of AI in agriculture</figcaption></figure><h4><strong>Introduction</strong></h4><p>The agriculture industry, valued at $5 trillion globally, forms the bedrock of the world’s economy and sustenance. According to the World Bank, agriculture contributes 4% to the global GDP and up to 25% in developing nations, showcasing its critical importance. However, with the global population increasing by 70 million annually, traditional farming methods are struggling to keep up with growing food demands.</p><p>This is where <strong>Artificial Intelligence (AI)</strong> steps in, offering innovative solutions to challenges such as pest control, resource optimization, and supply chain efficiency. AI is transforming agriculture into a modern, data-driven, and sustainable sector.</p><h4><strong>The role of artificial intelligence in agriculture</strong></h4><p>Due to the rising global population and the need to increase food production, implementing advanced technology such as artificial intelligence isn’t just innovation but necessary to maximize limited resources and arable land.</p><p>The adoption of AI technology is assisting farmers in improving their efficiency, reducing negative environmental impacts, and controlling and managing any adverse natural disasters. The agriculture industry has openly and actively embraced AI to influence the overall output. Farmers benefit from the application of artificial intelligence to better interpret data insights such as temperature, precipitation, wind speed, sun radiation, and so on. The best aspect about using AI is that it will not eliminate the work of human farmers, but rather will improve their procedures.</p><p>AI is more than an advancement; it is a transformative force driving agriculture forward. By integrating AI-powered tools, farmers can achieve:</p><ul><li><strong>Efficient Resource Use</strong>: AI ensures optimal usage of land, water, and energy by analyzing data such as soil quality, crop health, and weather patterns.</li><li><strong>Improved Decision-Making</strong>: Predictive analytics and AI-driven insights enable farmers to plan crop cycles, reduce waste, and manage risks.</li><li><strong>Environmental Sustainability</strong>: AI helps reduce chemical usage and carbon footprints by enabling precise application of fertilizers and pesticides.</li></ul><p>AI doesn’t replace human farmers but enhances their capabilities, creating a synergy between technology and traditional expertise.</p><p>Now, let’s move into what we gain from applying artificial intelligence in agriculture</p><h4><strong>Benefits of AI in agriculture</strong></h4><p><strong>1. Data-Driven Insights</strong></p><p>AI leverages data to provide actionable insights that improve productivity. For example:</p><ul><li><strong>Predictive Analytics</strong>: AI forecasts crop yields and weather impacts, helping farmers prepare for challenges.</li><li><strong>Precision Farming</strong>: Data gathered from sensors and drones enables targeted interventions like irrigation and fertilization.</li></ul><p><strong>2. Optimized Resource Allocation</strong></p><p>AI tools analyze historical and real-time data to allocate resources efficiently. Benefits include:</p><ul><li>Reduced water usage through smart irrigation systems.</li><li>Minimization of pesticide application, reducing environmental harm.</li><li>Enhanced crop rotation strategies for sustainable yields.</li></ul><p><strong>3. Climate Resilience</strong></p><p>As climate change affects agricultural patterns, AI helps farmers adapt by:</p><ul><li>Monitoring soil moisture and temperature variations.</li><li>Providing early warnings for extreme weather events.</li><li>Designing climate-smart farming strategies.</li></ul><h4><strong>Application of AI in agriculture</strong></h4><p><strong>1. Robotics in Agriculture</strong></p><p>AI-powered robotics are streamlining labour-intensive processes, such as:</p><ul><li><strong>Weeding</strong>: Robots detect and remove weeds without harming crops.</li><li><strong>Seeding</strong>: Autonomous machines plant seeds at optimal depths and spacing.</li><li><strong>Harvesting</strong>: AI-equipped robots pick fruits and vegetables, improving speed and precision.</li></ul><p><strong>2. Precision Farming</strong></p><p>Precision agriculture involves using AI and IoT (Internet of Things) devices to optimize every farming stage. Key applications include:</p><ul><li><strong>Precision Irrigation</strong>: AI determines the exact amount of water needed for crops, reducing waste.</li><li><strong>Farm Management Software</strong>: Platforms integrate data on weather, soil, and markets to guide farmers.</li><li><strong>Predictive Analytics</strong>: AI predicts crop diseases and pest outbreaks, enabling timely interventions.</li></ul><p><strong>3. Supply Chain Optimization</strong></p><p>AI strengthens agricultural supply chains by:</p><ul><li>Tracking produce from farm to table, ensuring transparency.</li><li>Forecasting demand and preventing overproduction or shortages.</li><li>Enhancing logistics through predictive models for transport and storage.</li></ul><h4>Challenges of AI in Agriculture</h4><p>While AI has transformative potential, its adoption faces challenges, including:</p><ul><li><strong>High Costs</strong>: AI-powered tools and equipment are expensive for small-scale farmers.</li><li><strong>Limited Internet Connectivity</strong>: Rural areas often lack the connectivity needed for IoT devices.</li><li><strong>Data Privacy Concerns</strong>: Farmers may worry about sharing sensitive farm data with AI platforms.</li></ul><h4><strong>Conclusion</strong></h4><p>The application of artificial intelligence in agriculture has taken great strides globally and in Africa from Farming management software, supply chain optimization tools to robotics and so many more. The potential benefits are tremendous and it is truly a revolution in the making.</p><p>AI is not just transforming agriculture — it’s revolutionizing the global food system. As technology continues to evolve, its role in agriculture will only grow stronger, offering new ways to enhance productivity and sustainability.</p><p>You made it to the end!</p><p>Trust this helps and see you in the next article.</p><p>Cheers🥂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbbb71948d19" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/artificial-intelligence-in-agriculture-a-revolution-in-the-making-cbbb71948d19">How artificial intelligence is revolutionizing agriculture</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The effect of artificial intelligence on product development]]></title>
            <link>https://medium.com/people-in-product/the-effect-of-artificial-intelligence-on-product-development-7695e1f78144?source=rss-c190fc7eb2eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/7695e1f78144</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Samuel Olusesi]]></dc:creator>
            <pubDate>Wed, 06 Sep 2023 01:47:44 GMT</pubDate>
            <atom:updated>2023-12-12T14:38:10.062Z</atom:updated>
            <content:encoded><![CDATA[<p>This article involves a relatable discussion on the future of product development, leveraging AI from the eyes of a lifelong learner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OttdCGP_9myZLgnEkKnyRg.jpeg" /><figcaption>Artificial Intelligence</figcaption></figure><p>In today’s hyper-technologically driven world, we’ve seen technology&#39;s rapid integration and evolution across various industries and, more recently, the “AI surge”. Before we get into the thick of things;</p><p>What is Artificial Intelligence?</p><p>Artificial Intelligence is simulated human intelligence, enabling machines to think, act, and problem-solve with human-level intellect. It is currently characterized by certain tasks carried out by machines. Let’s look at a few of them below:</p><ol><li>Reasoning and Problem-Solving: AI systems can analyze information, make decisions, and solve complex problems based on data and predefined algorithms.</li><li>Machine Learning: AI systems can learn from data and improve their performance over time without being explicitly programmed. This subfield of AI involves algorithms that enable computers to recognize patterns, make predictions, and classify information.</li><li>Natural Language Processing (NLP): NLP allows machines to understand, interpret, and generate human language. It’s used in chatbots, virtual assistants, and language translation services.</li><li>Computer Vision: AI systems can interpret and process visual information from the world, such as images and videos. This is used in facial recognition, image classification, and autonomous vehicles.</li><li>Robotics: AI-driven robots can perform physical tasks in the real world, from manufacturing and assembly to healthcare and exploration.</li><li>Speech Recognition: AI can transcribe spoken language into text, enabling voice commands and dictation software.</li><li>Expert Systems: These are AI systems that emulate the decision-making abilities of a human expert in a specific domain, providing recommendations and solutions in fields like medicine and finance.</li><li>Deep Learning: A subset of machine learning, deep learning uses artificial neural networks inspired by the human brain to solve complex problems. It has been particularly effective in tasks like image and speech recognition.</li></ol><p>All the way to the impressive Large Language models (LLMs) that have been created like Open AI’s ChatGPT and Google’s Bard, completely revolutionizing the space, now that’s out of the way, let’s get into the effect of AI in product development.</p><p>Artificial Intelligence can enhance the development process cutting across various phases from ideation to launch, Let’s look at some of them below:</p><p><strong>Ideation and Validation:</strong> AI in the years to come could potentially play a crucial role in generating ideas and validating them effectively as well due to its ability to generate and sift through vast amounts of data in a relatively small timeframe, let’s see how this can be implemented:</p><ol><li>Market Analysis — AI algorithms can sift through vast amounts of data from various sources, including social media, market trends, and customer feedback, to identify emerging trends and market gaps. This data-driven approach enables businesses to make informed decisions on what products to develop.</li><li>Idea Creation — AI-powered tools can assist in brainstorming sessions by analyzing existing ideas and suggesting improvements or entirely new concepts. This collaborative process accelerates innovation and creativity.</li></ol><p><strong>Enhanced Wireframing and Prototyping:</strong> Incorporating AI can potentially streamline the design and prototyping of a product in a number of ways such as:</p><ol><li>Generative Design- AI can generate multiple design iterations based on predefined criteria. Engineers and designers can explore a multitude of options, optimizing for factors like performance, cost, and sustainability.</li><li>Rapid Prototyping- 3D printing and AI-driven algorithms enable rapid prototyping and iteration. This means that product developers can quickly test and refine their designs, reducing time-to-market.</li></ol><p><strong>Improving Decision-Making and Predictive Analytics: </strong>AI is excellent at processing and analyzing data, which is invaluable for making informed decisions throughout the product development lifecycle:</p><ol><li>Data-Driven Decision-Making- AI algorithms analyze real-time data from various sources, helping businesses make data-driven decisions about product features, pricing, and marketing strategies.</li><li>Predictive Analytics- AI can forecast demand, identify potential production bottlenecks, and optimize supply chains. This predictive capability ensures products are available when customers want them.</li></ol><p><strong>Enhanced User Experiences: </strong>There are various ways this is currently being implemented namely:</p><ol><li>Personalization- AI-driven recommendation systems and user profiling enable companies to offer personalized product experiences, increasing customer satisfaction and loyalty.</li><li>Chatbots and Virtual Assistants- AI-powered chatbots and virtual assistants provide real-time customer support, answering queries and troubleshooting issues, enhancing the overall user experience.</li></ol><p>The aforementioned are a few of the ways that artificial intelligence can enhance the product development process from the ideation phase to the launch of the product and this is just the tip of the iceberg when it comes to its potential application. This is a good development contrary to some opinions on it taking over some jobs which might be true but what’s more important is everyone learning how to incorporate it into their workflow to maintain relevance and that skill of adaptability will never be out of demand.</p><p>Till next time,</p><p>Cheers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7695e1f78144" width="1" height="1" alt=""><hr><p><a href="https://medium.com/people-in-product/the-effect-of-artificial-intelligence-on-product-development-7695e1f78144">The effect of artificial intelligence on product development</a> was originally published in <a href="https://medium.com/people-in-product">People In Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Youtube product case study]]></title>
            <link>https://medium.com/design-bootcamp/youtube-product-case-study-707d98a83eb5?source=rss-c190fc7eb2eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/707d98a83eb5</guid>
            <category><![CDATA[technical-article]]></category>
            <category><![CDATA[product-analysis]]></category>
            <category><![CDATA[product-case-study]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Samuel Olusesi]]></dc:creator>
            <pubDate>Sat, 08 Jul 2023 17:00:41 GMT</pubDate>
            <atom:updated>2023-07-18T01:13:27.520Z</atom:updated>
            <content:encoded><![CDATA[<p>A product analysis of the youtube application with a breakdown of its features and improvements that can be made to its features to enhance the overall user experience.</p><figure><img alt="Title of the article including the youtube logo and name of the author" src="https://cdn-images-1.medium.com/max/1024/1*eGYHiJvBKOdJ1_rwyp7XHA.png" /></figure><p>The elements of this article will include:</p><ol><li>Background of the product</li><li>User Personas</li><li>Product Design (encompassing user experience and user design)</li><li>Product Value</li><li>Suggested Feature Improvements</li></ol><p><strong>Background</strong></p><p>Youtube was founded on Valentine’s Day; February 14th, 2005 by three founders: <a href="https://en.wikipedia.org/wiki/Steve_Chen"><strong>Steve Chen</strong></a>, <a href="https://en.wikipedia.org/wiki/Chad_Hurley"><strong>Chad Hurley</strong></a> and <a href="https://en.wikipedia.org/wiki/Jawed_Karim"><strong>Jawed Karim</strong></a>. They all met at Paypal as they were colleagues. The idea of Youtube started as a result of reliable and easily accessible video distribution sites and the initial idea was for individuals to post videos and for others to comment on what they thought about it but, the founders had to pivot to a more general video-sharing model.</p><p>In November 2005, the game changed as they got funding worth $3.5 million with $8 million gotten later, allowing expansion and officially leaving the “Beta” status. Moving forward to October 2006, Youtube was acquired by Google for $1.65 billion, being called at the time; “The next step in the evolution of the internet”.</p><p>From then till a lot has changed in their product offering with a lot added and dropped over the years, from Youtube Red which is now Youtube Premium to Youtube music, Youtube shorts and other features to keep their competitive edge in the market. Youtube has had exponential growth from its inception till date with an estimated 2.6 billion active users by the end of 2022 which led to an estimated revenue of $30 billion in 2022. Currently, having a valuation of $140 — $300 billion, I would say they’ve done well so far and are on the path to greater success.</p><p><strong>User Personas</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a_Ge9DDJ2JI_uQ3qxdn0Ag.png" /><figcaption>User Persona for the Consumer User</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TTsmiJ7uNaXUfl2lKJwN5g.png" /><figcaption>User Persona for the Creator User</figcaption></figure><p><strong>Product Design</strong></p><p><em>User Experience (UX)</em></p><p>User Experience is characterized by understanding the user’s needs, values, abilities and also limitations and incorporating them into your product design to make your product useful, usable, desirable, findable, valuable, credible and accessible.</p><p>In analyzing user experience, there are three elements to focus on, namely;</p><ol><li>Product Usability — This metric can be best explained as how best a product delivers its intended value to the user. The purpose for creating Youtube was primarily for video distribution. They’ve delivered excellently on that so far, literally revolutionizing the industry and bringing in features such as Youtube live which transmits video in real-time has transformed the user experience, so if I was to give a rating out of 10, I would say they get a solid eight out of ten on the scale.</li><li>Product Value — This is determined by usefulness based on the user, it’s value gotten by the user from using youtube, yes because, the user flow for Youtube would be logging in, searching for the video with the keywords and getting the results, based on statistics, Youtube is the second most popular search engine after google which proves value being gotten by the users, giving a rating here as well would be a solid eight out of ten on the scale.</li><li>Accessibility — This should be scaled on two parts, accessibility of the product and its features to the user, which they’ve done well on, next should be the accessibility of users with each other is a pain point for users, business owners connecting with influencers on the platform is a hassle, also users interacting privately with each other on the platform is not possible and because of that I give a four out of ten.</li></ol><p><em>User Interface</em></p><p>This is measured with the popular saying “Form follows function” and the platform is well optimized for video with some newly introduced features like ambient mode which gives a more immersive experience with the video playing in the background surrounding the video pane, older features like full screen and cinema mode, reactions to videos, live chat, a sidebar that shows all the features available at your disposal as well and various other features not outlined here. Easy to use and interact with, I give a solid seven out of ten.</p><p><strong>Product Value</strong></p><p>This is going to be analyzed from a business perspective, for profit for both the founders and Google who acquired them.</p><p>Let’s start with the founders, after Steve Chen and Chad Hurley sold Youtube to Google for $1.65 billion, Steve Chen got 625,366 Google shares and 68,721 in trust as part of the sale, as of September 2021, the shares were almost valued at $1.77 billion.</p><p>While Chad Hurley received 694,087 Google shares directly and another 41,232 shares in a trust. According to The Wall Street Journal, Hurley’s share was valued at $345.6 million at Google’s closing stock price of $470.01 on February 7, 2007. While Jawed Karim though he played only an advisory role had 137,443 shares valued at $64.6 million as of 2007.</p><p>Google acquired Youtube for $1.65 billion in October 2006, as of 2022, Youtube was valued at $180 billion with a brand value of $23.89 billion. By these metrics, it can be said that Youtube has been a successful product over the years.</p><p><strong>Suggested Feature Improvements</strong></p><p>The suggested feature improvement I would like to suggest is an in-app messaging feature, to allow easy communication between users as that is a pain point for business owners looking to collaborate with creators and collaborations between creators as well.</p><p>Below are some deliverables to that effect:</p><p>I put together a PRD for the messaging feature with wireframes, user flows, user personas and all the works included, check it out here ⬇️</p><p><a href="https://docs.google.com/document/d/1apsPbrCSeq5HbcMNCRF6ZynpUjm5jr5Lh8YMX9TgTu4/edit?usp=sharing"><strong>YOUTUBE MESSAGING PRD</strong></a></p><p>Thank you for reading the article, if you’d like to connect, here’s my <a href="https://www.linkedin.com/in/samuel-olusesi-252185177/"><strong>LINKEDIN</strong></a> let’s chat over coffee.</p><p>Cheers 🥂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=707d98a83eb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/youtube-product-case-study-707d98a83eb5">Youtube product case study</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kuda mobile application case study]]></title>
            <link>https://medium.com/design-bootcamp/kuda-mobile-app-a-product-case-study-4750ba8e1d87?source=rss-c190fc7eb2eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4750ba8e1d87</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-case-study]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Samuel Olusesi]]></dc:creator>
            <pubDate>Wed, 14 Jun 2023 14:15:55 GMT</pubDate>
            <atom:updated>2023-07-18T01:13:24.795Z</atom:updated>
            <content:encoded><![CDATA[<p>A brief analysis of the Kuda mobile application and its features.</p><figure><img alt="Image showing the article title, application logo and name of author" src="https://cdn-images-1.medium.com/max/1024/1*t6cPGR5Q-Vl786TVCjvnVg.png" /></figure><p>This technical article is a product case study geared towards an analysis of the Kuda Bank mobile application focusing on four primary areas namely;</p><ol><li>Background</li><li>Product design (with a primary focus on the user interface)</li><li>User experience (UX)</li><li>Product Value (Product usefulness to users)</li></ol><p>The metrics to be used to measure success across these four chosen areas are:</p><ol><li>Adoption</li><li>User retention</li><li>Engagement</li></ol><p>Great! Now the foundation has been laid, let’s get into the details and start with the background of Kuda Bank.</p><p><strong>Background</strong></p><p>Kuda Bank was founded in 2016 by Babs Ogundeyi and Mustapha Musty, it originally started as Kudimoney, an online savings and lending platform. As an establishment, they envision revolutionizing and fully digitizing banking in Africa, beginning from Nigeria as its origin.</p><p>Because it’s a digital bank, that necessity created the Kuda Bank App which has user-friendly dashboard interfaces and quality value and with their unique selling proposition, it has made them stand out in their sector.</p><p>They were the first fully digital bank in Nigeria with no network of branches, this model has low operating costs and low cost for the customer and is void of the various charges customary to traditional banking outfits.</p><p>Time has revealed their growth and the fact their vision is worth believing in as shown in multiple successful funding rounds they’ve been a part of, from all indications, they are here to stay and make their dream of a digital Africa a reality.</p><p>Next, let’s take a look at the design of the mobile application.</p><p><strong>Product Design</strong></p><p>In my research into what makes a Product design good, I stumbled on a list of ten principles put together by a renowned German Industrial Designer; Dieter Rams, you can check him out <a href="https://en.wikipedia.org/wiki/Dieter_Rams"><strong>here</strong></a><strong>.</strong></p><p>He put it together beautifully and after discussing it with a colleague who happens to be a senior product designer, I’ve come to the conclusion that for a product to be deemed as designed properly, two things need to be considered;</p><ol><li>Usability</li><li>Aesthetics (Quality of the user interface)</li></ol><p>There is a saying in design; <strong><em>form follows function</em></strong>, meaning the aesthetics of the application as beautiful as it should be, shouldn’t interfere with the usability of the application, it should be determined by it.</p><p>Using these metrics, the Kuda Bank application design is excellent, from the user interface’s simplicity, not losing the core which is to be able to send and receive money, nice features have been developed around it e.g bank app icons, etc. To the all-round product design, I applaud it!</p><p>So does the product design drive user adoption, retention and engagement? with all said above, the answer is yes. Next, let’s look at the user experience.</p><p><strong>User Experience (UX)</strong></p><p>The user experience review is based on my personal extensive usage of the application and data gotten from a control group of constant users of the application and the use is seamless in sending and receiving money. The extra features are a nice touch as well like sending money in chat format also, the auto-saving feature of accounts already transferred to, etc. An excellent user experience.</p><p>The only issue is paying bills like buying data and electricity, it reverses a lot of times or sometimes it just doesn’t go. I believe the solution to this problem would be better integration with the Telecommunication companies and Electricity companies respectively to allow better seamless transactions between the two parties.</p><p>Based on this, I would say the UX drives user retention and engagement, not so much adoption.</p><p><strong>Product Value</strong></p><p>The value is the usefulness of the product as determined by the user and this can be measured by the average Time to Value of the application and based on my research it is on the upside based on the proper value delivery.</p><p>Based on this, the product value does drive user retention, adoption and engagement.</p><p><strong>Conclusion</strong></p><p>In conclusion, the Kuda Bank mobile application is an excellent product save some minor glitches to be worked on and has an excellent value offering and delivery.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4750ba8e1d87" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/kuda-mobile-app-a-product-case-study-4750ba8e1d87">Kuda mobile application case study</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>