<?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"><channel><title><![CDATA[Untitled Publication]]></title><description><![CDATA[Untitled Publication]]></description><link>https://oluwatobio.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sun, 06 Sep 2026 20:11:54 GMT</lastBuildDate><atom:link href="https://oluwatobio.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How to Set Realistic Goals as a Product Manager]]></title><description><![CDATA[As a Product Manager (PM), setting realistic goals is one of the most critical aspects of your role. Goals define the direction for your team, shape the product roadmap, and influence stakeholders’ expectations. Setting unrealistic goals can lead to ...]]></description><link>https://oluwatobio.hashnode.dev/how-to-set-realistic-goals-as-a-product-manager</link><guid isPermaLink="true">https://oluwatobio.hashnode.dev/how-to-set-realistic-goals-as-a-product-manager</guid><category><![CDATA[Product Management]]></category><category><![CDATA[Productivity]]></category><category><![CDATA[life]]></category><category><![CDATA[production]]></category><dc:creator><![CDATA[Oluwatobi Oni]]></dc:creator><pubDate>Fri, 30 Aug 2024 19:00:17 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1725042735466/7b9b9f16-ad36-4e2f-8338-ef79fef62453.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>As a Product Manager (PM), setting realistic goals is one of the most critical aspects of your role. Goals define the direction for your team, shape the product roadmap, and influence stakeholders’ expectations. Setting unrealistic goals can lead to frustration, missed deadlines, and lost trust, while realistic goals help your team stay focused, motivated, and on track for success. Here’s how to set achievable and effective goals as a PM:</p>
<ol>
<li>Understand the Bigger Picture</li>
</ol>
<p>Before you dive into specific goals, take a step back and understand the broader business context. Align your product goals with the company’s vision, mission, and objectives. Ask yourself:</p>
<ul>
<li><p>What are the company’s long-term goals?</p>
</li>
<li><p>How does this product contribute to those goals?</p>
</li>
<li><p>What market or customer needs are you solving?</p>
</li>
</ul>
<p>By ensuring your goals align with the company’s strategy, you can create a solid foundation for prioritising work that matters.</p>
<p>2. Incorporate SMART Criteria</p>
<p>A widely used framework for setting achievable goals is the SMART method. Ensure your goals are:</p>
<ul>
<li><p>Specific: Clearly define the goal with enough detail that anyone can understand the objective. Ambiguity leads to confusion and misalignment.</p>
</li>
<li><p>Measurable: Establish how progress will be tracked. Whether it’s product adoption, revenue, or customer satisfaction, measurable goals help you stay focused and evaluate success.</p>
</li>
<li><p>Achievable: Evaluate your resources, team capacity, and timeline to ensure the goal is realistic. Set goals that stretch your team but remain attainable.</p>
</li>
<li><p>Relevant: Your goals should directly contribute to the success of the product and the company’s vision. If a goal isn’t relevant, it’s not worth pursuing.</p>
</li>
<li><p>Time-bound: Define a clear deadline or time frame. Open-ended goals can lead to delays and lack of accountability.</p>
</li>
</ul>
<p><em>Example: Instead of saying, “Improve the product’s user experience,” try something like, “Increase user satisfaction scores by 15% in the next quarter through improved onboarding and reducing bug reports.”</em></p>
<p>3. Collaborate with Cross-Functional Teams</p>
<p>From experience, I feel this is one of the most important steps. As a PM, you work with teams across engineering, design, marketing, and sales. Collaborating with these teams early helps set goals that are realistic from both a technical and resource standpoint. Engage in discussions to:</p>
<ul>
<li><p>Understand technical constraints and feasibility.</p>
</li>
<li><p>Align on timelines that the development team can realistically meet.</p>
</li>
<li><p>Consider market dynamics that may impact marketing and sales efforts.</p>
</li>
</ul>
<p>Open communication with cross-functional teams helps prevent overcommitting or setting goals that don’t reflect real-world capabilities. Setting goals without considering the team’s capacity will often make the team look like a failure</p>
<p>4. Leverage Data and Customer Insights</p>
<p>Data-driven goals are not only realistic but also provide a strong foundation for decision-making. Use analytics and customer feedback to understand your product’s performance, user behaviour, and pain points.</p>
<p>5. Break Goals into Manageable Milestones</p>
<p>Big, ambitious goals are essential, but they can be overwhelming for the team. To avoid this, break large goals into smaller, manageable milestones. Each milestone serves as a checkpoint and keeps the team motivated by providing frequent opportunities for progress tracking and celebration.</p>
<p>6. Balance Short-Term Wins with Long-Term Vision</p>
<p>While it’s important to deliver quick wins to show progress, you also need to keep an eye on the long-term vision of your product. Setting only short-term goals can lead to feature bloat or a product that doesn’t evolve with market needs. Similarly, focusing too much on long-term goals can lead to missed opportunities for quick improvements or market responsiveness. Balance your goals by:</p>
<ul>
<li><p>Setting tactical goals (short-term) that drive immediate value.</p>
</li>
<li><p>Keeping strategic goals (long-term) aligned with the broader product vision.</p>
</li>
</ul>
<p>This balance ensures that your team delivers value consistently while moving toward the larger vision.</p>
<p>7. Account for Risks and Uncertainties</p>
<p>This is one step that most PMs fail to consider while setting goals. Every product roadmap has risks and uncertainties — whether it’s technical challenges, market shifts, or unexpected resource constraints. Acknowledging these factors early on allows you to set realistic goals while building contingencies. Include buffer time for unexpected delays and always have a plan B in case things don’t go as expected.</p>
<p>8. Regularly Review and Adjust Goals</p>
<p>The product landscape is constantly evolving, and so should your goals. Regularly review progress against your goals and be willing to adjust them if necessary. Market conditions, customer feedback, or new company priorities can all impact the relevance of a goal. Schedule periodic check-ins with your team and stakeholders to:</p>
<ul>
<li><p>Assess whether goals are still realistic given current circumstances.</p>
</li>
<li><p>Reprioritize work based on new developments.</p>
</li>
<li><p>Celebrate progress and course-correct when needed.</p>
</li>
</ul>
<p>Thank you for reading till the end. I’m Oluwatobi, a Product Manager and Designer. I’m dedicating myself to sharing what I’ve learned so far on this product management journey, hoping to help future and fellow product managers along the way. If you also have any PM tips for me, feel free to leave a comment below!</p>
<p>In the meantime, follow me on <a target="_blank" href="http://www.linkedin.com/in/oluwatobioni1">LinkedIn</a> and <a target="_blank" href="https://medium.com/@oluwatobioni96">Medium</a> to stay tuned for upcoming articles. Chat with you soon!</p>
<p>Image credit: <a target="_blank" href="https://www.freepik.com/premium-photo/human-hand-writing-achieve-your-goals-blackboard_16986109.htm">Freepik</a></p>
]]></content:encoded></item><item><title><![CDATA[Why a Failed Product Launch Could Be Your Best Opportunity Yet]]></title><description><![CDATA[In product management, not many things are as painful as a failed product launch. The countless hours spent brainstorming, planning, and developing can culminate in an event that unfortunately, falls short of expectations. It is easy to perceive a fa...]]></description><link>https://oluwatobio.hashnode.dev/why-a-failed-product-launch-could-be-your-best-opportunity-yet</link><guid isPermaLink="true">https://oluwatobio.hashnode.dev/why-a-failed-product-launch-could-be-your-best-opportunity-yet</guid><category><![CDATA[Product Management]]></category><category><![CDATA[pm]]></category><category><![CDATA[product]]></category><category><![CDATA[Productivity]]></category><category><![CDATA[Product launch]]></category><category><![CDATA[launch]]></category><dc:creator><![CDATA[Oluwatobi Oni]]></dc:creator><pubDate>Fri, 09 Aug 2024 18:34:16 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1723205129286/b6753e04-dba3-4b25-bfbf-bcb04d9a5085.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In product management, not many things are as painful as a failed product launch. The countless hours spent brainstorming, planning, and developing can culminate in an event that unfortunately, falls short of expectations. It is easy to perceive a failed product launch as an ultimate setback for a product, but seasoned product managers know better. In fact, they understand that a failed product launch doesn't necessarily equate to a failed product. Instead, it presents an invaluable opportunity for learning and growth.</p>
<p>A failed product or feature, especially in a startup striving to establish its market presence, can indeed feel like a major blow. However, as the product manager in charge, <em>Don’t Panic!</em>  It is crucial to resist the urge to dwell solely on the failed outcome and instead focus on reflection. What went wrong? What needs to be done differently? What lessons can be learned moving forward? By addressing these questions, product managers can turn a disappointing outcome into a stepping stone toward eventual success. </p>
<p>Here are the steps you should take to address a failed launch:</p>
<p>1. Understand Failure:</p>
<p>Before diving into the aftermath of a failed product launch, it's crucial to understand why launches sometimes miss the mark. There are various reasons why a product might fail to meet the set goals upon release. It could be due to technical issues, inadequate market research, or simply failing to meet customer needs and expectations. It is important to analyse this together with all the teams involved in the product launch process. and get several feedback. Regardless of the cause, failure provides valuable insights into what went wrong and how to improve moving forward.</p>
<p>2. Embracing Failure as a Learning Opportunity:</p>
<p>While it's natural to feel disappointed in the aftermath of a failed product launch, it's essential to shift focus from dwelling on what went wrong to understanding why it happened. Personally, my words are “What’s the way forward now guys?” Encourage your team to conduct a thorough post-mortem analysis, brainstorming and examining every aspect of the product launch process. What were the key challenges encountered? Were there any warning signs that were overlooked? Was the launch rushed? By asking these questions, you can uncover valuable lessons that will inform future product development efforts.</p>
<p>3. Iterating and Refining:</p>
<p>One of the greatest advantages of experiencing a failed product launch is the opportunity it presents for iteration and refinement. Armed with insights gained from post-mortem analysis, product managers can work with their teams to make necessary adjustments and improvements to the product. This might involve refining the product features, addressing any technical issues that may have arisen or revising the marketing strategy. By embracing a mindset of continuous improvement, you can transform a failed product launch into a stepping stone towards success.</p>
<p>4. Communicating Transparently:</p>
<p>When a launched product fails, effective communication is paramount. Be transparent with your team, stakeholders, and customers about what went wrong and the steps you're taking to address the issues. This demonstrates accountability and builds trust, both internally and externally. Additionally, solicit feedback from customers and incorporate their insights into your product development process. By involving them in the journey, you not only foster a sense of ownership but also increase the likelihood of delivering a product that resonates with their needs.</p>
<p>5. Celebrating Progress:</p>
<p>Finally, it's essential to celebrate progress, no matter how minor it may seem. Recognise the efforts of your team in identifying and addressing the challenges that led to the failed product launch. By acknowledging their hard work and commitment to improvement, you foster a culture of resilience and innovation within your organisation.</p>
<p>Thank you for reading till the end. I'm Oluwatobi, a Product Manager and Designer. I'm dedicating myself to sharing what I've learned so far on this product management journey, hoping to help future and fellow product managers along the way. If you also have any PM tips for me, feel free to leave a comment below!</p>
<p>In the meantime, follow me on <a target="_blank" href="http://www.linkedin.com/in/oluwatobioni1">LinkedIn</a> and <a target="_blank" href="https://oluwatobio.hashnode.dev/">Hashnode</a> to stay tuned for upcoming articles. Chat with you soon!</p>
<p>Image credit: <a target="_blank" href="https://www.freepik.com/free-vector/flat-hand-drawn-people-starting-business-project-illustration_12552771.htm#fromView=search&amp;page=2&amp;position=0&amp;uuid=c1780a96-5ae6-409e-8557-a5030f49a8a6">Freepik</a></p>
]]></content:encoded></item><item><title><![CDATA[As a PM, Are You for the Management or for the Team?]]></title><description><![CDATA[As a Product Manager (PM), you often find yourself in a unique and sometimes challenging position, balancing the needs and expectations of both management and the team. This dual allegiance can create a complex dynamic, but it's crucial for the succe...]]></description><link>https://oluwatobio.hashnode.dev/as-a-pm-are-you-for-the-management-or-for-the-team</link><guid isPermaLink="true">https://oluwatobio.hashnode.dev/as-a-pm-are-you-for-the-management-or-for-the-team</guid><category><![CDATA[pm]]></category><category><![CDATA[Product Management]]></category><category><![CDATA[product manager]]></category><category><![CDATA[product development]]></category><category><![CDATA[management]]></category><dc:creator><![CDATA[Oluwatobi Oni]]></dc:creator><pubDate>Fri, 19 Jul 2024 18:58:01 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1721367339724/906862bc-2dc9-4a9b-8edd-5c6843b84bd2.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>As a Product Manager (PM), you often find yourself in a unique and sometimes challenging position, balancing the needs and expectations of both management and the team. This dual allegiance can create a complex dynamic, but it's crucial for the success of the product and the well-being of the team. So, are you for the management or for the team? The answer is both, and here's why.</p>
<p><strong>For the Management</strong></p>
<p>Your role as a PM involves translating the strategic vision and business goals set by the management into actionable plans. This means:</p>
<ul>
<li><p>Ensuring that the product aligns with the company’s overall strategy and objectives.</p>
</li>
<li><p>Regularly updating management on progress, challenges, and successes. This requires transparency and clear communication.</p>
</li>
</ul>
<p>Management relies on you to deliver a product that drives growth, meets market demands, and contributes to the company’s bottom line. All these need to be done within the timeline agreed upon. Your ability to communicate effectively with management and demonstrate how the product aligns with their vision is critical.</p>
<p><strong>For the Team</strong></p>
<p>On the flip side, you are also the advocate and leader of your product team. This entails:</p>
<ul>
<li><p>Providing the team with a clear product vision and well-defined goals to guide their work.</p>
</li>
<li><p>Identifying and addressing any barriers that might impede the team’s progress, whether they are technical, logistical, or interpersonal.</p>
</li>
<li><p>Creating an environment that encourages teamwork, innovation, and open communication.</p>
</li>
</ul>
<p><strong>Your team looks to you for direction, support, and motivation.</strong> You must ensure they have the resources, information, and encouragement they need to succeed.</p>
<p>How Then Can We Balance The Two</p>
<p>To be honest, I am also still a work in progress. Balancing the needs of management and the team is no small feat, but it is essential for a successful PM. Here are some strategies I’ve realised to manage this balance effectively:</p>
<p>1. Transparent Communication</p>
<p>With Management: Keep management informed with regular updates on the product’s progress, including both achievements and challenges. Be honest about what is realistic and what isn’t.</p>
<p>With the Team: Communicate the rationale behind management’s decisions and how they impact the product. This helps the team understand the bigger picture and stay motivated.</p>
<p>2. Prioritise Wisely</p>
<p>Align Goals: Ensure that the team’s goals are aligned with the company’s strategic objectives. This alignment makes it easier to justify decisions and prioritise tasks.</p>
<p>Flexibility: Be prepared to adjust priorities based on feedback from both management and the team. Flexibility is key to navigating changing demands and constraints.</p>
<p>3. Advocate for the Team</p>
<p>Advocate for the necessary resources, tools, and time the team needs to deliver quality work. This might involve negotiating with management to ensure the team isn’t overburdened.</p>
<p>Recognition and Support: Highlight the team’s achievements to management. Recognize their hard work and contributions, and ensure they feel valued and supported.</p>
<p>4. Manage Expectations</p>
<p>Realistic Timelines: Set realistic timelines and manage expectations on both sides. Avoid overpromising to management or setting unrealistic deadlines for the team. This is actually very important.</p>
<p>Clear Boundaries: Define clear boundaries for what can and cannot be done within a given timeframe or with available resources. This helps prevent burnout and maintains morale.</p>
<p>5. Foster a Collaborative Culture</p>
<p>Cross-Functional Collaboration: Encourage collaboration between different departments and functions. This not only helps in aligning goals but also in understanding different perspectives and constraints.</p>
<p>Empowerment: Empower your team to take ownership of their work and make decisions within their domain. This fosters a sense of responsibility and commitment.</p>
<p>Whew, you made it to the end! Thanks for hanging in there. I'm Oluwatobi, a Product Manager and Designer. This is actually my first attempt at writing PM wisdom, so I hope it wasn't too confusing. I'm dedicating myself to sharing what I've learned so far on this product management journey, hoping to help future and fellow product managers along the way. If you also have any PM tips for me, feel free to leave a comment below!</p>
<p>In the meantime, follow me on <a target="_blank" href="http://www.linkedin.com/in/oluwatobioni1">LinkedIn</a> and <a target="_blank" href="https://oluwatobio.hashnode.dev/">Hashnode</a> to stay tuned for upcoming articles. Chat with you soon! 😎</p>
]]></content:encoded></item><item><title><![CDATA[Solving Real Problems: A Design Thinking Journey]]></title><description><![CDATA[In the world of design, success hinges on more than just aesthetics—it's about identifying real problems and crafting innovative solutions. Join me on a journey through the principles of design thinking as we delve into a captivating UX case study: R...]]></description><link>https://oluwatobio.hashnode.dev/solving-real-problems-a-design-thinking-journey</link><guid isPermaLink="true">https://oluwatobio.hashnode.dev/solving-real-problems-a-design-thinking-journey</guid><category><![CDATA[design thinking]]></category><category><![CDATA[Problem Solving]]></category><category><![CDATA[User Research]]></category><category><![CDATA[user-centered design]]></category><category><![CDATA[Case Study]]></category><dc:creator><![CDATA[Oluwatobi Oni]]></dc:creator><pubDate>Fri, 29 Sep 2023 17:31:10 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1696008514094/814cba19-f77e-4641-901d-6327eda33d5b.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In the world of design, success hinges on more than just aesthetics—it's about identifying real problems and crafting innovative solutions. Join me on a journey through the principles of design thinking as we delve into a captivating UX case study: <a target="_blank" href="https://uxdesign.cc/the-new-york-times-timely-app-concept-27efe88e5d4b"><em>Redesigning the New York Times app</em>.</a> This insightful review dissects just three pillars of design thinking to uncover how a team of designers navigated the intricate landscape of user dissatisfaction, competition, and content relevance. Below are some of the insights from the case study</p>
<ol>
<li><p>Problem Identification: Identifying the problem is the first step in the design thinking process. It ensures that designers focus on solving real issues rather than perceived ones. In this case, the team recognized key issues with the existing app such as user dissatisfaction, competition, and content relevance problems which guided the entire design process toward addressing these critical issues effectively. This thorough problem analysis is essential in the design thinking process.</p>
</li>
<li><p>User-Centred Approach: Design thinking emphasises empathy for the end-users. By conducting research into the habits and preferences of young users, the design team gained valuable insights. This user-centred approach ensures that the final solution caters to the actual needs and behaviours of the target audience, increasing the likelihood of its success.</p>
</li>
<li><p>Iterative Design: Iteration is a fundamental aspect of design thinking. Generating multiple concepts and testing them with different groups ensures that the final solution is refined and improved over time. It allows designers to learn from failures and adapt their approach based on user feedback, increasing the likelihood of success. The team generated multiple concepts and tested them with different groups to validate ideas. The iterative design process ensures that the final solution is both sustainable and viable.</p>
</li>
</ol>
<p><strong><em>Thank you for reading! 😊</em></strong></p>
]]></content:encoded></item></channel></rss>