<?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 Neche Ibekendu on Medium]]></title>
        <description><![CDATA[Stories by Neche Ibekendu on Medium]]></description>
        <link>https://medium.com/@nechekendu?source=rss-2ce9c28329ae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CMg1XpZaqI7V4YtzrMHMpw@2x.jpeg</url>
            <title>Stories by Neche Ibekendu on Medium</title>
            <link>https://medium.com/@nechekendu?source=rss-2ce9c28329ae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:52:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nechekendu/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 Habits That Keep Me Effective as a Product Delivery Lead]]></title>
            <link>https://medium.com/@nechekendu/the-habits-that-keep-me-effective-as-a-product-delivery-lead-d189c2fd55f7?source=rss-2ce9c28329ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/d189c2fd55f7</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Neche Ibekendu]]></dc:creator>
            <pubDate>Fri, 15 May 2026 17:50:31 GMT</pubDate>
            <atom:updated>2026-05-15T17:50:31.551Z</atom:updated>
            <content:encoded><![CDATA[<p>One thing I have learned working in fintech is this: the moment you stop learning, you start falling behind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mAnf5lHktLfrmX-409il-Q.jpeg" /><figcaption>In July 2024, we launched Payaza 2.0. This photo captures me alongside my colleagues as we unveiled the platform’s new features and improvements to our customers.</figcaption></figure><p>Products evolve. Customer expectations change. Regulations shift. Technology moves fast. What worked six months ago may already be outdated today. As a Product Delivery Lead, I have realized that staying effective is not just about managing delivery timelines or launching features. It is about building habits that keep you sharp, adaptable, and connected to both your team and the product itself.</p><p>Over time, there are a few things I have become very intentional about: practices that help me stay on the learning curve while also driving strong execution and product outcomes.</p><h3>Don’t Ignore New Information</h3><p>Sometimes, the most valuable product insight comes from the most random places.</p><p>It could happen during a sprint meeting. A casual conversation with a colleague. A customer complaint. A product demo.</p><p>When I hear or notice something interesting, I usually go deeper into it. I like understanding the “why” behind things. Instances are</p><ul><li>Why does this approach work?</li><li>Why are users reacting this way?</li><li>What problem is it really solving?</li></ul><p>I have found that curiosity is one of the most significant advantages in a career or in life. The more curious you are, the easier it becomes to spot opportunities, identify risks early, and connect ideas across products and teams.</p><p>A lot of excellent product thinking starts with simply paying attention.</p><h3>Empathy Makes the Team</h3><p>Delivery environments can get intense. Deadlines, bugs, changing priorities, and stakeholder pressure can all be overwhelming. That is why I believe empathy inside a sprint squad matters more than people sometimes realize.</p><p>Engineers are thinking about scalability and implementation challenges. Designers are considering usability and experience. Operations teams care about process efficiency. Business teams are focused on growth and revenue. Everyone is carrying different pressures.</p><p>When people feel understood, collaboration becomes easier. Conversations become more productive. Teams solve problems faster instead of working defensively.</p><p>I have seen firsthand that teams perform better when people are patient with each other, communicate openly, and genuinely try to understand where others are coming from.</p><p>Strong delivery is not just about processes. It is also about people.</p><h3>Embrace Feedback, Regardless of Role</h3><p>One mindset that has helped me a lot is removing the idea that learning only comes from senior people.</p><p>Some of the best insights I have received came from people who were simply close to the problem:</p><ul><li>A customer support agent explaining recurring complaints</li><li>An engineer pointing out a hidden technical risk</li><li>A junior PM asking a question nobody considered</li><li>An operations staff member identifying a process gap</li><li>A customer describing frustration in the simplest way possible</li></ul><p><strong><em>Good ideas are not attached to job titles.</em></strong></p><p>The moment you become too senior to learn from others, you limit your growth. In product delivery, being open-minded helps you make better decisions because you see the product from multiple angles, not just your perspective.</p><h3>Feedback Helps Me Improve Faster</h3><p>I genuinely value feedback, even when it is uncomfortable.</p><p>Not every feedback will be accurate, but I think there is always something useful to learn from how people experience your leadership, communication, or execution style.</p><p>Over time, feedback has helped me to:</p><ul><li>communicate more clearly,</li><li>manage stakeholders better,</li><li>improve sprint collaboration,</li><li>and identify blind spots earlier.</li></ul><p>The best teams I have worked with were not perfect. They were teams that were willing to listen, adjust, and improve continuously.</p><h3>Intentional Learning</h3><p>Every product leader should have some form of learning roadmap, both personally and for their team.</p><p>For me, that means continuously improving my understanding of:</p><ul><li>Payments,</li><li>Product strategy and Distribution</li><li>Operations and user behavior</li><li>Leadership,</li><li>Data and emerging technology trends.</li></ul><p>For the team, it means creating opportunities for shared learning:</p><ul><li>Retrospectives,</li><li>Product brainstorming sessions,</li><li>Knowledge-sharing sessions,</li><li>Honest conversations about what is working and what is not.</li></ul><p>Being a Product Delivery Lead goes beyond managing timelines and releases. It requires adaptability, curiosity, emotional intelligence, collaboration, and continuous growth.</p><p><strong>The reality is that the learning curve in technology never stops.</strong></p><p>However, by remaining curious, building empathetic teams, staying open to learning, embracing feedback, and intentionally developing both yourself and your team, it becomes easier to navigate complexity while driving successful product outcomes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d189c2fd55f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Year on the Ground: Building a Fintech Bridge in the Republic of Benin]]></title>
            <link>https://medium.com/@nechekendu/a-year-on-the-ground-building-a-fintech-bridge-in-the-republic-of-benin-42452d30bbe3?source=rss-2ce9c28329ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/42452d30bbe3</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[africa]]></category>
            <category><![CDATA[global-payments]]></category>
            <category><![CDATA[payment-gateway]]></category>
            <category><![CDATA[mobile-payments]]></category>
            <dc:creator><![CDATA[Neche Ibekendu]]></dc:creator>
            <pubDate>Wed, 24 Sep 2025 19:08:15 GMT</pubDate>
            <atom:updated>2025-09-24T19:08:15.943Z</atom:updated>
            <content:encoded><![CDATA[<p><em>An opaque journey becomes a life-changing and purposeful one..</em></p><p>Bienvenue!!<br>I arrived in the Republic of Benin, a country I had never set foot in, and certainly not with the weight of a country manager’s crown. My mission: to launch and scale fintech operations in a market that was, to me, largely a blank and foreign slate. What followed was a year of learning, adaptation, and an immersive dive into the unique world of payments in the Francophone region in Africa.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z7s4OcY6iMrrXiKiVrcouA.jpeg" /><figcaption>A picture taken by me; in the centre you will see a flag of the Republic of Benin</figcaption></figure><p>My first observation was the simplicity of Benin’s financial landscape, which happened the next day after I had arrived. Unlike the often cumbersome processes I was used to in Lagos, Nigeria, with setting up a bank account, setting up a mobile money account was astonishingly easy, straightforward, and fast.</p><p>All I needed was a valid ID and 200 XOF ($0.33) cash. This interaction took place at a simple kiosk in front of my hotel, where a mobile network agent swiftly created an account for me, instantly enabling me to send and receive mobile payments. It was an impactful first impression, highlighting the remarkable accessibility of financial services for the average person.</p><blockquote>Unlike in Nigeria, opening even a basic Tier 1 bank account requires a full suite of KYC documents, including a government-issued ID, proof of address, and your Bank Verification Number (BVN).</blockquote><p>This ease of use, however, would later impact my journey as an individual and a representative of my company.</p><p>My initial months were a whirlwind of administrative tasks. My team and I worked tirelessly to lay the groundwork for our operations. The biggest hurdle we faced was navigating the regulatory environment. Under the regulations of the BCEAO (Central Bank of West African States), any company seeking to operate as a payment processing platform in the Republic of Benin must secure a license. This process often takes time; it is not a fast process. It can take months—we knew we couldn’t afford to wait, as we had a market available. This is where strategic partnerships became the cornerstone of our market entry strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nGG1LSgD172Hu78grUxjVQ.jpeg" /><figcaption>In this image, you see a display of available mobile network providers that are in the momo payments sector. This carries information of my favorite icecream business in Cotonou.</figcaption></figure><p><strong>Strategic Partnerships<br></strong>The quest for the right partners was a meticulous one. We scoured the market for payment platforms and traditional banks that not only had the necessary licenses but also whose business goals and technological capabilities aligned with ours. We needed partners who understood our vision and were willing to work collaboratively. After careful due diligence, we found a few platforms that checked all our boxes. The next phase was integration, a complex process of connecting our systems to theirs to ensure seamless payment processing.</p><p>With partnerships secured and integrations complete, we were finally ready for work. However, the true challenges had just begun. Benin, while vibrant, is a relatively small market. The landscape is dominated by a few key players, and competition is fierce. The reality of operating in this environment meant that simply having a license or a strategic partnership wasn’t enough. We had to prove our value proposition every single day. The “hurdle” I mentioned in my initial notes was the daily grind of building a business from the ground up in a competitive, yet developing, digital economy.</p><p>The past 12 months have been a masterclass in resilience and strategic thinking. I’ve learned that success in fintech in a market like Benin isn’t just about having the best technology. It’s about building trust, putting your users’ satisfaction at the forefront of your daily effort, forging strong relationships, and understanding the unique nuances of local consumer behavior.</p><p>The journey has been challenging but also incredibly rewarding. From that first arrival to the daily rhythm of managing a thriving operation, I have gained an invaluable understanding of what it takes to bring digital payments to a new frontier. The heavy crown I wore a year ago now feels a little lighter, not because the job is easier, but because the journey has transformed me into a more capable and confident leader.</p><p>As we look toward our second year, we are not just building a business; we are scaling our impact. And on a personal front, I’m committed to bridging the language gap even further, aiming for a B2 level in French to better connect with our partners and the community we serve.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42452d30bbe3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Agile Methodology is best for Product Management]]></title>
            <link>https://medium.com/@nechekendu/why-agile-methodology-is-best-for-product-management-a7ab5296e7ee?source=rss-2ce9c28329ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7ab5296e7ee</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[lean-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Neche Ibekendu]]></dc:creator>
            <pubDate>Fri, 22 Oct 2021 15:36:43 GMT</pubDate>
            <atom:updated>2021-10-22T15:36:43.131Z</atom:updated>
            <content:encoded><![CDATA[<p>In search of a better way to develop products and software , Agile Methodology will give you an efficient, quicker and quality product.</p><p><strong>What is Agile Methodology?</strong></p><p>Agile methodology is an approach used for developing products by breaking up the process into different stages for easy collaboration. It is also a way to develop and iterate a product without wasting resources.</p><p>Products that are developed using agile methodology have their requirements delivered iteratively and incrementally throughout the process</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/463/1*NVx0emFFuU22kjuqT7GB-w.png" /><figcaption><a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fwww.business2community.com%2Fstartups%2Fadvantages-of-agile-product-methodology-for-fast-growing-startups-enterprises-02394643&amp;psig=AOvVaw311q_LSdWM2RvUErck1PSe&amp;ust=1634998144218000&amp;source=images&amp;cd=vfe&amp;ved=2ahUKEwjkqIPumN7zAhUPsxoKHdadB4sQr4kDegUIARDWAQ">Visual representation of how agile works</a></figcaption></figure><p><strong>Why Agile Methodology?</strong></p><p>Agile has become the most preferred approach to deliver a quality product efficiently. Agile focuses on the building and planning throughout the development process and ensures that risk management is low.</p><p>Here are 5 reasons why you should try agile, if you haven’t:</p><ol><li><strong>Collaborative Culture</strong></li></ol><p>Agile has made it possible for different teams working directly or indirectly on a project toget together as they keep learning and growing with time during the product execution.</p><p>2.<strong> Quality Product</strong></p><p>Testing is a necessary part to do throughout every phase of the product development. This makes the quality of the final product to be good.</p><p>3.<strong> Increased Flexibility</strong></p><p>Teamwork achieved in smaller groups will give constant feedback to the client involved in the planning process. This allows implementation of change as mistakes will be made, hence increasing flexibility during this course.</p><p>4. <strong>Minimal Risk</strong></p><p>Any project that uses agile framework have very low chance to be successful. Most projects do not fail. There are continuous feedback and changes made to enable products not to fail.</p><p>5. <strong>Customer Satisfaction</strong></p><p>With agile, customers are involved in the planning process stage to stage, making changes according to their feedback. You’ll be able to deliver accordingly and ensure the final product meets their requirements.</p><p><strong>Creating a suitable Agile Environment</strong></p><p>For agile to be adopted, its<em> modus operandi</em> for you and your team members has to be convenient with your organization’s culture. It enables good performance and an accommodative working place.</p><p>Implementing an agile approach on different teams; those working on the product and those not working directly on the team product will impact the organization by yielding a successful result. It is an experimental display of working to promote ideas, change, and process results.</p><p>Here’s how to ensure a working environment is agile</p><ol><li>Get everyone on board. Interactions between your team members, having discussions about their challenges, follow-up of user stories created amongst the team. These should have priority over processes and tools.</li><li>If there is a change or a situation with the customer’s requirements, it’s right for a conducive agile environment to respond to it rather than following or executing an already set plan.</li><li>Always put your customer first. Collaborating with your customer, listening to their ideas, and working together to make changes would create a good agile environment than following a contract negotiation made beforehand.</li><li>Do less paperwork and focus on delivering functioning products that have passed every requirement. Stakeholders and executives believe documentation and paperwork should always come first. It shouldn’t be the case.</li><li>Communicate the company’s vision and always provide constructive feedback when needed. It will help team members to have good communication and always be ready to speak when faced with challenges.</li></ol><p>Recently, agile methodology can get implemented in some companies in most industries like Finance, Insurance amongst others now make use of it. Some of the popular companies that use agile are Google, Amazon, Netflix, Spotify, and Cisco. Hardware teams use agile product development and engineering to save time, money and improve end products.</p><p>In conclusion, the agile methodology may not solve all our product management problems, but it’s a better approach to an efficient and successful product.</p><p>Here are some resources that you will find insightful if you want to learn more about agile methodology, you can visit these links:</p><ul><li><a href="https://wrike.com/project-management-guide/agile-project-management-tools-techniques/">Agile Project Management Tools &amp; Techniques</a></li><li><a href="https://kissflow.com/project/agile/benefits-of-agile/">9 Key Benefits of Using the Agile Methodology</a></li><li><a href="https://www.quora.com/What-is-agile-environment">What is agile environment?</a></li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZ9QbYZh1YXY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZ9QbYZh1YXY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZ9QbYZh1YXY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f94f0a2173cc9761388ebb917e5f6ea8/href">https://medium.com/media/f94f0a2173cc9761388ebb917e5f6ea8/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7ab5296e7ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>