<?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 Titilayo Adeyemi on Medium]]></title>
        <description><![CDATA[Stories by Titilayo Adeyemi on Medium]]></description>
        <link>https://medium.com/@titijay.tj?source=rss-57c4b0284d9f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*s2RImRV6_AcvLyUK8NNUXQ.jpeg</url>
            <title>Stories by Titilayo Adeyemi on Medium</title>
            <link>https://medium.com/@titijay.tj?source=rss-57c4b0284d9f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:47:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@titijay.tj/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 Implementation: My Product development process]]></title>
            <link>https://medium.com/@titijay.tj/from-idea-to-implementation-my-product-development-process-73fd14c96210?source=rss-57c4b0284d9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/73fd14c96210</guid>
            <category><![CDATA[sdlc]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management-tool]]></category>
            <category><![CDATA[sdlc-process]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Titilayo Adeyemi]]></dc:creator>
            <pubDate>Thu, 30 Mar 2023 10:18:59 GMT</pubDate>
            <atom:updated>2023-03-30T10:18:59.616Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m sure most people think software development requires a meticulous step-by-step process but usually, it’s different events happening simultaneously in each “phase”. I call it “beautiful chaos” and in seven steps I’m going to show how I build products.</p><p>The <strong>first step </strong>is<strong> Ideation</strong>. We start with a group discussion around the user problem we’re trying to solve or the underlying idea of the product we are about to build. The Team will align on a high-level approach and what will contribute to company revenue. The purpose of this meeting is to ensure everyone understands the product vision.</p><p>The <strong>second </strong>is <strong>data gathering</strong>, findings are made on competitors and products similar to what we are trying to build. The necessary information is put together and then presented to the cross-functional team. This leads to the <strong>third step</strong>, the <strong>Prioritization + Problem framing approach</strong>, where the team decides on what to build, how best to and when based on inputs from all stakeholders.</p><p>After this, <strong>Requirements</strong> are created and reviewed, and necessary <strong>research</strong> is carried out. <strong>This fourth step</strong> is the thread that holds the whole process together. This is done simultaneously with the remaining flow of the product software development lifecycle. This is usually the conclusion of the product plan because by now the product plan outlines the product’s features, the development process, and the timeline.</p><p><strong>The fifth step is</strong> <strong>Design, </strong>which<strong> </strong>involves creating a user interface that is both functional and visually appealing. At the stage, we work closely with the design team to create wireframes and prototypes to ensure that the user interface meets the user’s needs and expectations.</p><p><strong>Reviews</strong> are the <strong>sixth step</strong> but they can be general involving the cross-functional team or specific to the stage of development like Technical design review, where engineering and design work together to ensure the best high-fidelity designs are created at the end of the day. There’s also a post-launch review which is done to analyse the user’s reactions and feedback.</p><p>In the <strong>seventh</strong> <strong>step, Quality Assurance </strong>tests are done before the product is launched, it’s essential to ensure that it’s free of bugs and meets quality standards.</p><p>The eighth and<strong> final step</strong> is the<strong> Launch</strong>. In this stage, we work with the marketing team to create a launch plan that includes product positioning, target audience, and promotional activities.</p><p>If you are not a fan of big blocks of text, here’s a schematic that summarizes the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rT_bEleXKn3zOCHiB9l-4w.jpeg" /></figure><p>In conclusion, the software development lifecycle is a complex process that requires careful planning, execution, and continuous improvement. One thing I have realised is that as a product manager while following basic practices like being customer-centric, data-driven, etc is important, being flexible to accommodate the surprises that come in the SDLC is equally as important.</p><p>The goal is always to ensure that the product meets the user’s needs and expectations and delivers value to the organization while ensuring effectiveness and due diligence throughout the development process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73fd14c96210" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Idea to Implementation: How Product Managers Can Master Leadership and Execution.]]></title>
            <link>https://medium.com/@titijay.tj/from-idea-to-implementation-how-product-managers-can-master-leadership-and-execution-c6678861c661?source=rss-57c4b0284d9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6678861c661</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[execution]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-management-career]]></category>
            <dc:creator><![CDATA[Titilayo Adeyemi]]></dc:creator>
            <pubDate>Mon, 13 Mar 2023 11:33:16 GMT</pubDate>
            <atom:updated>2023-03-13T11:33:16.774Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Qh2lSHkhTbKCG9Fw3eOBRA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Markus Spiske</a> on <a href="https://unsplash.com/photos/QozzJpFZ2lg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>On many days being a product manager feels like navigating an endless maze of ideation, while trying to carve a path to success through thoughtful execution. This reality is something Luis Urzúa must have been very familiar with but unlike you and me, he was not a product manager.</p><p>Luis Urzua was a miner; one whose leadership not only saved 33 miners from certain death but can also serve as an example for us as product managers. In 2010, the San Jose copper-gold mine collapsed, trapping 33 miners over 700 meters underground. A hopeless situation in many ways, but Urzúa’s leadership and execution were critical elements that aided the miners’ survival.</p><p>Urzua immediately recognized the seriousness of the situation and organized the men for a long-term survival situation, helping them cope mentally with the situation. He made detailed maps of the area to help with the rescue effort and coordinated closely with engineers on the surface. When asked about his experience, he referred to it as “a really long day”. Lol, can you relate?</p><p>We can learn a lot from Urzúa’s example. While our work may not involve life-or-death situations, it does require effective leadership. As product managers, our primary focus is on product discovery — working with designers and engineers to come up with solutions that are <strong>valuable, usable, feasible, and viable.</strong> This is the core of our job, and it takes up a significant portion of our time each day.</p><p>However, we also need to manage projects and teams to ensure that our products are delivered successfully. This requires us to make difficult decisions and manage conflict, which can be challenging especially when you are the bad cop on the team on most days.</p><p>To master our role, we need to focus on delivering results. This means thinking like an owner and committing to outcomes, rather than just a list of activities. We need to be comfortable with conflict and able to make tough decisions that may not be popular with everyone.</p><p>One way to ensure that we can focus on product discovery while also managing projects and teams is to team up with a delivery manager who can take on some of the project management responsibilities. However, some product managers may be reluctant to give up this responsibility, which can lead to a lack of focus on the core job of product discovery.</p><p>In an organization like a startup where you may be wearing different hats, you may need to share some of the responsibility with the team because everyone at some point will be wearing more than one hat in that environment.</p><p>Ultimately, product managers need to be able to find a balance to deliver successful products. By focusing on product discovery, committing to outcomes, and being comfortable with conflict, we can learn from examples like Luis Urzúa and become effective product managers who deliver results.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6678861c661" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>