When writing a company blog, it’s easy to focus on your product features and provide tips, tricks, or simply highlight what’s new. Instead, Heather McCloskey, Content Marketing Manager at ProductPlan, decided to write an article supporting the roles who are likely to use their product. In the article “3 Reasons Product Managers Quit (and How to Prevent It)”, Heather provided a lesson in talent retention and motivation. Not once does she try to cross-promote ProductPlan’s toolset, but rather focuses on delivering value to its market and users. By providing value and guidance to product owners and managers, Heather can reach future customers while enhancing the value of ProductPlan’s brand.
Heather identifies three key reasons why good product managers would leave for a better opportunity: The Team, The Manager, and The Product. The articlethen goes on to provide several suggestions for organizations on how to retain their product management talent. The post is genuine, not preachy, and speaks directly to their core demographic.
Why is this important? For some companies, the corporate blog is a communication tool for existing users. Using your blog to promote enhancements and partnerships is a valid and important strategy. However, in her article, Heather created a valuable message to ProductPlan’s target users that does not come across as a sales pitch. The content stands on its own and is ready for readers to share across all their social platforms. ProductPlan using this strategy is creating valuable content that strengthens its brand, positioning the company as supportive, thought leaders, and in tune with user needs. Isn’t this the message we want to convey for our products?
ProductPlan provides a collaboration platform to help Product Owners gather feedback to help build and manage their product roadmap and backlogs. Download our product management research to help define what is important to you and your product.
Traditional accounting practices are tailor made for waterfall project management. Organizations that have transitioned to the use of standing product teams using Agile and DevOps need to transform their accounting practices as well or they will leave valuable capital expenditure dollars on the table.
IBM is changing the terms of its ubiquitous Passport Advantage agreement to remove entitled discounts on over 5,000 on-premises software products, resulting in an immediate price increase for IBM Software & Support (S&S) across its vast customer landscape.
So you’ve gone Agile. You do daily scrums, retrospectives, and all the “right” Agile ceremonies. But still your organization isn’t quite convinced. It is now critical to balance the drivers and goals of both Agile and traditional thinking in order to achieve organizational success.
Do you feel like your Agile teams are treading water – going through the motions but never going anywhere? It’s a risk, and practices such as daily standups, retrospectives, and demonstrations need to be used wisely or you risk losing discipline to meeting fatigue.
Stakeholders expect the speed and responsiveness of product delivery does not come at the expense of quality. QA tools offer retailers the ability to continuously ensure both business and technical quality standards are upheld, but these tools should not be viewed as a silver bullet.
When trying to implement Agile as a defined process, Scrum turned BAs or other roles into order takers with the title “product owner.” This undermines the entire value proposition of product management.
No matter how good your product roadmap and backlog are, they are only as good as your audience’s ability to understand your vision and priority.
The scrum master is like the conductor of an orchestra, ensuring that every piece fits together at the right time to create something greater than the sum of the parts. You don’t have to know how to play each instrument, but you do have to understand what each part contributes to the overall masterpiece.
Tools are important to product teams, but only when they support solid people and processes.