In the dynamic world of product development, success often rests in the capable hands of a Product Owner. From our experience, good <b>Product Owners play a vital role</b> in steering projects towards triumph.  As our development teams collaborate closely with clients, we advocate for the appointment of a dedicated Product Owner on their side. Why? Because we recognize that the Product Owner’s influence can <b>elevate the project</b> and secure <b>a final product with value</b>.  However, the path to success is not without its challenges. A Product Owner must posses three traits: <ol><li style="font-weight: 400;" aria-level="1">A visionary mindset - They must have a product vision, know the business domain, and be able to communicate it to the team.</li><li style="font-weight: 400;" aria-level="1">A vested interest - They must have dedicated time in the project, collaborating with both the development team and internal stakeholders to grasp the intricacies of their needs.</li><li style="font-weight: 400;" aria-level="1">An engaging leadership - They must engage users throughout the process, while also being empowered to make crucial decisions that will shape the final product.</li></ol> If this sounds like you - you’re an ideal Product Owner. <a href="https://appsilon.com/#contact" target="_blank" rel="noopener">Contact us</a> to discover how you’ll make all the difference in your product’s success.  If you have a project in mind and question the need for a Product Owner, join us as we explore two compelling stories from two real partnerships. One is an unfortunate tale of an Unsuccessful Product Owner and the other is our favorite story - the Successful Product Owner. We’ll provide valuable insights and guidance for Product Owners seeking to overcome obstacles and achieve better outcomes. Table of Contents: <ul><li><a href="#success"><strong>Success in Development</strong> is a Product of Ownership</a></li><li><a href="#challenges">Product Owners and Their Impacts on <strong>Challenging Projects</strong></a></li><li><a href="#code">Contrasting Product Owner <strong>Strategies for Product Release</strong></a></li></ul> <hr /> <img class="aligncenter size-medium wp-image-20029" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b01ae3923c12912d3dfd44_project-planning-product-owner-gantt-chart.svg" alt="project planning product owner gantt chart" width="400" height="175" /> <h2 id="success">Success in Development is a Product of Ownership</h2> The stories begin the same for both Product Owners. Picture two companies, each on the cusp of a new software venture, seeking a trusted partner to craft cutting-edge R/Shiny dashboards. They discover Appsilon, a team that matches their needs and is <a href="https://clutch.co/profile/appsilon-r-shiny-machine-learning#reviews" target="_blank" rel="noopener">well-known for technical expertise and project guidance</a>.  After <a href="https://appsilon.com/#contact" target="_blank" rel="noopener">reaching out</a>, a discovery call is set. When the cooperation discussions begin, Appsilon suggests appointing a Product Owner—a proposition that piqued the Company's curiosity. Despite being new to this concept, they embrace the idea, sealing the deal, and commencing their collaboration. Little did they know that this seemingly small decision would lead to two distinct outcomes—a revealing tale of an Unsuccessful Product Owner and an inspiring account of a Successful Product Owner. <h3>Unsuccessful Product Owner</h3> The<i> Unsuccessful Product Owner</i>, let's call him Bob, belonged to a team entirely unrelated to the application’s intended users. The application’s concept was entirely new to Bob, and he found himself scrambling to fill the knowledge gaps. To compound matters, Bob had joined the Company merely  a month ago, transitioning from an entirely different domain.  As a result, the entire project proved to be very stressful for the Unsuccessful Product Owner. While the team diligently delivered functionalities, Bob struggled to provide timely feedback. The constantly shifting priorities only added to his burden, with requests for new functionalities promptly taking precedence and disrupting the sprint backlog. This environment made it challenging for the development team to maintain their focus. Furthermore, three months into the project, a significant setback emerged - the data format underwent significant changes. Consequently, the development team had to invest an additional month to adapt the application to the new format. During a company meeting, Bob  was informed that there will be a new data provider. Unfortunately, he did not connect this critical information to the app that he was responsible for.  <h3>Successful Product Owner</h3> The <i>Successful Product Owner, </i>let’s call her Jane<i>,</i> knew the idea and desired purpose for the application long before the project began. The vision was so ingrained in her mind that it felt like it was her very own idea. Not only did she grasp the core problem that Users were encountering, but Jane had also personally experienced those challenges in the past. In fact, she had previously worked in the same position as the target Users. Armed with this unique perspective, Jane knew precisely how the app could provide meaningful solutions and make a positive impact. Jane had also excellent knowledge of the domain. Having spent most of her life working in this area, she was the go-to person when her peers had questions. Additionally, Jane was working at the Company long enough to be able to connect the dots: she knew different people from different areas, knew  when changes in the Company would affect the problem that the app is solving, and knew to whom to promote the app and where to look for help. Thanks to Jane’s extensive knowledge and past experience, she was able to easily explain the app vision to the development team and establish full alignment between all stakeholders. And when a process change was planned in the Company, she quickly spotted its impact on the current problem that the app was solving and was able to adjust the course of the project to ensure it would remain useful for the users. <img class="aligncenter size-medium wp-image-20025" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b01ae5f638169cb253df3c_new-r-shiny-app-features-for-product-owner.svg" alt="new r shiny app features for product owner" width="400" height="175" /> <h2 id="challenges">Product Owners and Their Impacts on Challenging Projects</h2> The project continues with its routines, as well as some challenges. Two Product Owners, two different approaches to handling challenges. Let’s explore their contrasting journeys to find the art of product ownership and discover the impact they had on their respective projects. <blockquote>User expectations change. That's OK. Follow these <a href="https://appsilon.com/ux-design-of-shiny-apps-7-steps-to-design-dashboards-people-love/" target="_blank" rel="noopener">7 steps to stay on track and develop decision-support tools your users will love</a>.</blockquote> <h3>Unsuccessful Product Owner</h3> Bob, the<i> Unsuccessful Product Owner,</i> had many priorities within his organization. Because of that, he struggled to  fully concentrate on the app. He barely found time to test it himself. Nonetheless, Bob tried to attend review meetings regularly, believing it would help him maintain  control over the  development process. Once developers started asking questions about the new functionality, but Bob didn’t know the answers himself. He assured his team he would return with  answers soon. However, once Bob disconnected from the meeting, other company priorities took priority for him. Despite the developers’ attempts to contact him, Bob remained unresponsive, leaving them with no choice but to make decisions on their own as the deadline drew near. Armed with best intentions, but limited knowledge of the users, they delivered a functionality that ultimately proved to be of little use.  <h3>Successful Product Owner</h3> Jane, the<i> Successful Product Owner,</i> was dedicated to app development. With the full support of her manager, she allocated three days a week, to focus entirely on the app. This availability allowed her to actively participate in scrum meetings, work extensively with the app herself , and offer the team valuable feedback that could be quickly addressed. Moreover, Jane readily accommodated ad hoc calls with developers, ensuring they had the necessary context and clarity on requirements whenever needed. Her close collaboration with the team fostered a streamlined development process and empowered the team to deliver exceptional results on time..  During the Product Owner’s absence on holidays, the team continued work without any blockers. Because of the time that Jane spent with the team previously, everyone had a unified understanding of the goal and the users’ needs. As a result, the developers could make certain development decisions themselves. When Jane returned, the mutual trust established resulted in autonomous, successful development. <img class="aligncenter size-medium wp-image-20027" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b01ae6f37e8990539dd3b2_owning-data-science-product-delivery.svg" alt="owning data science product delivery" width="400" height="175" /> <h2 id="strategies">Contrasting Product Owner Strategies for Product Release</h2> Every app, at some stage, reaches the point when it can finally be showcased to the users. How the two Product Owners approach that is reflected in two completely different ways.  <blockquote>Don't let the challenges of project delivery keep you from success. <a href="https://appsilon.com/software-project-delivery-management/" target="_blank" rel="noopener">Ensure smooth software project delivery with a Delivery Manager</a>.</blockquote> In the next section, we’ll see the divergent approaches of Bob and Jane as they introduce their respective apps to the users, and how their distinct strategies influence the final product. <h3>Unsuccessful Product Owner</h3> Bob, the<i> Unsuccessful Product Owner, </i>remained unsure of the target audience for the app  until it was almost ready. When he finally identified the users, he hesitated to show them the app until each and every backlog task was closed. Bob believed that if an unfinished app was presented, the users would lose interest in it and never come back.  Finally, when the app was ‘ready’, Bob organized a meeting for its presentation. Unfortunately, only 5 out of the 20 people invited attended the session. During the session, there was a lot of feedback. Users were raising items that weren’t clear for them and some key functionalities were missing. When Bob returned to the development team, it became evident that several changes requested by the users would require substantial time to implement. These alterations significantly impacted the core of the app, with many elements already built on top of it. Consequently, Bob needed to find an additional budget for the app development in order to apply the users’ feedback. When the new round of development started, the Product Owner simply relayed all the user feedback to the team. Some requests seemed to contradict each other, while others posed significant challenges by complicating the user interface. The team needed clarification and context, but Bob insisted, “just do what the users want, that’s the only way to make them use the app.” When the app was finally ready and deployed to production, a surprising revelation surfaced - the app proved to be excessively complex, demanding extensive training for every new user. After <a href="https://appsilon.github.io/shiny.telemetry/" target="_blank" rel="noopener">analyzing the user stats</a>, most of the users were only using a mere 5% of the functionality, while a staggering 50% of the functionality had never been used. <h3>Successful Product Owner</h3> Jane, the <i>Successful Product Owner, </i>engaged the user from the start of the project. Even before the development team began their work, Jane was proactively conducting interviews with the users, diligently collecting information about their pain points and needs. This early involvement with the users laid the foundation for a user-centric approach that would shape the app’s development.  Later during the development phase, Jane invited users to test the app. In the process, she managed to cultivate an atmosphere of excitement and anticipation around the app’s progress. Jane was collecting feedback and discussing it with the development team, so that the changes could be addressed promptly. By communicating changes and engaging users along the way, the users saw that they had a real impact on the shape of the app. This gave the users a sense of connection and deepened their engagement with the project. Though Jane was collecting a lot of feedback, she analyzed each piece to discern what should be within  scope of the app, what could be deferred for future updates, and what was interesting but not immediately applicable. This strategic approach allowed the team to stay focused on the main goal of the app while ensuring a clean and user-friendly interface.  As a result, the first release provided the users with the most important features.  When the app was released, Jane organized a meeting, and all the stakeholders showed up. There were no surprises, as the users’ feedback had been regularly addressed. Right after launch the app adoption hit its targets. The successful outcome was a testament to Jane’s proactive approach in incorporating user input and setting the stage for a smooth, well-received app release.  <img class="aligncenter size-medium wp-image-20023" src="https://webflow-prod-assets.s3.amazonaws.com/6525256482c9e9a06c7a9d3c%2F65b01ae8e7ac33b972b399e2_delivering-accurate-results.svg" alt="delivering accurate results with product owner" width="400" height="175" /> <h2>Effective Product Ownership Insights in App Development</h2> This is where the story ends for the <i>Unsuccessful Product Owner</i> - the app is now in production, but its result is far from impactful. The Company is already contemplating shutting it down and replacing it with a set of apps that offer better usability.  For the <i>Successful Product Owner</i> this milestone marks the beginning of a new chapter - the app garners immense success. It's promoted within the company with internal recognition. Along the healthy lifetime of the app, it is discovered that other markets would also like to leverage it. Jane, the <i>Product Owner</i>, earned a well-deserved promotion. It’s not easy to be a Product Owner. We understand this challenge, and we are committed to help the Product Owner achieve success. We make sure that each project has a dedicated <a href="https://appsilon.com/software-project-delivery-management/" target="_blank" rel="noopener">Delivery Manager</a> - an experienced professional in Product Management - whose primary goal is to support and guide you in elevating your product to new heights. With our team by your side, you can confidently navigate the intricacies of successful product ownership and drive your project towards exceptional outcomes.  If you want confidence in getting results, we’re here to deliver. <a href="https://appsilon.com/#contact" target="_blank" rel="noopener">Let’s talk</a>.