<?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 Seyitan Ogunleye on Medium]]></title>
        <description><![CDATA[Stories by Seyitan Ogunleye on Medium]]></description>
        <link>https://medium.com/@ogunleye.seyitan?source=rss-aa92cd4fc15a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sIUnMQOkGHDPeQvC_REmxQ.png</url>
            <title>Stories by Seyitan Ogunleye on Medium</title>
            <link>https://medium.com/@ogunleye.seyitan?source=rss-aa92cd4fc15a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:17:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ogunleye.seyitan/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[From Idea to App in Days: Exploring Cloud Development as a Non-Coder]]></title>
            <link>https://medium.com/@ogunleye.seyitan/from-idea-to-app-in-days-exploring-cloud-development-as-a-non-coder-1f99c737277b?source=rss-aa92cd4fc15a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f99c737277b</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Seyitan Ogunleye]]></dc:creator>
            <pubDate>Tue, 03 Jun 2025 09:15:55 GMT</pubDate>
            <atom:updated>2025-06-03T09:15:55.139Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>How I built my first app in a Cloud Development Environment with no coding experience</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WNuzwoUTk3PRKfl4Z0yaQA.png" /><figcaption>Go from idea to lauch.</figcaption></figure><p>Not too long ago, I took a course titled <em>“AI for Product Growth”</em> as part of a work training initiative. I wasn’t sure what to expect, but I left that class with a head full of inspiration. For the first time, I truly understood the possibilities that lie at the intersection of AI and product development. We covered a lot: GPTs, the industrial revolutions, AI and NLP, tooling with chatbots, cloud development environments (CDEs), and even AI readiness assessment. But one thing stuck with me — CDEs and the power they offer for building.</p><p>Fast forward a few weeks, and I came across an email from one of my favorite newsletters, <em>Making Product Sense</em> by Jacob. His article <a href="https://www.theglimpse.co/p/the-rise-of-fast-saas?utm_source=substack&amp;publication_id=304424&amp;post_id=160977788&amp;utm_medium=email&amp;utm_content=share&amp;utm_campaign=email-share&amp;isFreemail=true&amp;r=oe7oi&amp;triedRedirect=true"><em>The Rise of Fast SaaS</em></a> broke things wide open for me. He didn’t just talk about the theory behind vibecoding, he tested it. He compared different CDEs and even shared how he built something from scratch. It gave me the push I needed.</p><h3>Getting Started: Hitting Walls and Finding Workarounds</h3><p>I decided to stop overthinking and just start. My goal was simple: build a personal portfolio. At first, I planned to use tools I was familiar with like Notion and Figma, but then I realized this was a great learning opportunity. I started with Lovable (a CDE mentioned at the training). The promise of no-code was comforting, especially since my coding knowledge is minimal. But I hit a wall, quickly. Database management completely stumped me. I couldn’t figure out how to manage assets on GitHub. I spent days stuck.</p><p>Back to Jacob’s article I went, and there it was, the key insight. Among the tools he reviewed, only one really handled database management alongside the other essentials: Replit.</p><p>Here’s a good comparison chart from <a href="https://substack.com/redirect/5e00c683-a49b-44a5-b38d-56c45a065640?j=eyJ1Ijoib2U3b2kifQ.YozBgn1tn81ufwfpnItGdrf6Ycef_eWaSRJqoC6IJww">Lenny’s Newsletter</a> referenced in Jacob’s article that shows what each tool supports.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZD3G3sHlA0gOJAcfeeiUlw.jpeg" /></figure><h3>Making It Work on Replit</h3><p>I already had a Replit account, so I logged in and gave it a shot. Replit uses something called “checkpoints,” milestones you can revert to. You need Replit coins to use them, and there’s a cap unless you subscribe. I also discovered Replit AI agents that helped troubleshoot and suggest solutions in real-time.</p><p>Despite the limitations, I made it work. I had an almost-ready portfolio site after a few days of learning, tweaking, debugging, and ultimately subscribing. The sense of accomplishment was massive. Not because I wrote thousands of lines of code (I didn’t), but because I went from idea to execution without a technical background.</p><h3>The Journey Continues</h3><p>Since then, I’ve started using CDEs more regularly, not just for personal projects but at work too. These tools have helped me reimagine how I approach prototyping and even build fully functional platforms for my team. The opportunities here are endless. I can now think beyond static mockups and actually bring ideas to life fast.</p><h3>Key Takeaways for New Vibecoders</h3><p>If you’re curious about vibecoding or cloud development environments, here are some tips:</p><ul><li><strong>Start small.</strong> Don’t aim to build a unicorn SaaS on your first try. A portfolio, blog, or internal tool is a great place to start.</li><li><strong>Choose the right platform.</strong> Replit worked for me because of its built-in AI agent and user-friendly interface. Others might prefer Lovable, Bolt, Railway, or CodeSandbox depending on their use case.</li><li><strong>Expect to learn.</strong> Even in a no-code/low-code environment, you’ll hit challenges. That’s part of the process.</li><li><strong>Use checkpoints wisely.</strong> On platforms like Replit, these are precious.</li><li><strong>Don’t be afraid to pay.</strong> The learning and output are worth the small investment if you’re serious.</li></ul><p>I went from knowing almost nothing about coding to shipping a usable project in days. If I can do it, so can you.</p><p>Let the vibecoding begin.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f99c737277b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Consumer-Centric Financial Products: A Product Manager’s Perspective]]></title>
            <link>https://medium.com/@ogunleye.seyitan/building-consumer-centric-financial-products-a-product-managers-perspective-e4c9bd6a538d?source=rss-aa92cd4fc15a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4c9bd6a538d</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[financial-services]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Seyitan Ogunleye]]></dc:creator>
            <pubDate>Wed, 28 Aug 2024 12:31:53 GMT</pubDate>
            <atom:updated>2024-08-29T07:56:01.954Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xDwDHFl_wWkh5IAIB7g86g.jpeg" /></figure><p>As a product manager who has worked within the financial services sector over the years, I have seen products being built with various motivations and the resulting impact on the product’s performance.</p><p>Today, relatable examples such as Revolut and Monzo indicate the importance of creating financial products that prioritize consumer needs and experiences. We can see why consumer-centricity is not just a buzzword but a critical product differentiator. This article delves into strategies for developing such products, drawing from my experiences and observations.</p><p>There are 4 pillars to creating a customer-centric product. The first one is <strong>Understanding Consumer Needs</strong>.</p><p>The foundation of any consumer-centric product is a deep understanding of the consumers. This involves:</p><p>1. Consumer Research and Feedback: Regularly conducting surveys, focus groups, and one-on-one interviews to gather insights into consumer pain points, preferences, and expectations. It does not always have to be a formal interview, it can take the form of regular discussions with your target users. For instance, while working with the mobile payment group in my previous role, we implemented a quarterly survey system that helped us identify issues with our mobile banking app’s user interface, leading to a major redesign that significantly improved user satisfaction.</p><p>2. Consumer Journey Mapping: Analysing the entire consumer journey to identify touchpoints where consumers interact with the product and potential areas for improvement. In another of my previous roles, we mapped out the journey of opening a savings account and discovered that the process was cumbersome. Simplifying it resulted in a 20% increase in new account openings within six months.</p><p>The second pillar for creating a customer-centric product is <strong>Leveraging Technology.</strong></p><p>Technology plays a vital role in creating seamless and personalized experiences. Here are some strategies I have implemented in the past:</p><p>1. Digital Transformation: Embracing digital channels to offer services that are accessible anytime, anywhere. For example, the introduction of various self-service avenues allowed consumers to perform transactions via a platform rather than the brick-and-mortar mediums available at the time, increasing convenience and engagement.</p><p>2. Personalization through Data Analytics: Using data analytics to offer personalized products and services. I have been part of a project where we developed an AI-driven recommendation engine that analysed transaction data to suggest tailored financial products to consumers, such as loans or investment opportunities, enhancing the relevance of what we were selling to our users and improving the uptake of those offerings.</p><p>The third is <strong>Enhancing Consumer Experience.</strong></p><p>A positive consumer experience is crucial for retention and loyalty.</p><p>If a product is not serving you well, you are more likely to stop using it or switch to a competitor brand. To promote retention and loyalty, your product needs to stand out by meeting all your users’ needs; in the context of the product, proactively and efficiently.</p><p>For this, we focus on the following areas:</p><p>1. User-Friendly Design: Ensuring that all digital interfaces are intuitive and easy to navigate. I once led a mobile app redesign, the focus was on achieving on a clean, user-friendly interface. The effort resulted in a 30% increase in active users.</p><p>2. Proactive Consumer Support: Offering robust consumer support through multiple channels, including chatbots, live chat, and call centres. Being able to get answers to questions and queries as users navigate your product will go a long way in improving consumer satisfaction.</p><p>Finally, the fourth pillar for creating a customer-centric product is <strong>Agile Product Development</strong>.</p><p>Adopting an agile approach to product development allows for flexibility and quick responses to consumer feedback. Key practices include:</p><p>1. Iterative Development: Releasing product features in small, manageable increments and iterating based on consumer feedback. This was particularly effective in a previous role, where we rolled out a new budgeting tool in our mobile app and refined it based on user feedback in successive updates.</p><p>2. Cross-Functional Teams: Collaborating across departments to ensure all aspects of the product, from design to marketing, are aligned with consumer needs. Every team has valuable insights driven by their expertise to help facilitate faster problem-solving.</p><p>Conclusion</p><p>Building consumer-centric financial products requires a deep understanding of consumer needs, leveraging technology, enhancing the consumer experience, and adopting agile development practices. From my experience, these strategies are highly important in creating products that not only meet but exceed consumer expectations. As the financial industry continues to evolve, staying attuned to consumer needs and embracing innovation will be key to sustaining a competitive advantage.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4c9bd6a538d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>