Getting agreement on your product plans can be an uphill, bloody battle. As a product manager, you’re likely more immersed in your product and have the closest thing to a 360-degree view than nearly anyone else in your company. You know your customers. You know the market and what’s needed to sell and support your product. You know what engineering can, wants, and needs to do to keep things running. But you need stakeholder buy in, and, sometimes, formal approval.
6 min read
7 min read
Dante’s Inferno has nine circles of Hell. Fortunately, product teams don’t have to navigate them all to address their planning challenges without getting burned. The main goal of product planning is to identify and prioritize candidate features most likely to succeed in the market given resource and time constraints. How do you know what’s most likely to succeed? Validation.
3 min read
Product leaders: Ever been stuck in endless meetings trying to get your stakeholders to agree on priorities and feature ideas? It’s not our idea of fun either. We built stakeholder surveys in Obo so you can get more buy-in and more input with far fewer meetings.
Our customers love that they can use stakeholder surveys to quickly get input and buy-in to business and product priorities, feature value, and cost estimates -- all without long, contentious meetings. Your stakeholders will thank you, too.
3 min read
Lou Hayes, Jr. is not a software guy. He’s a self-described “Police Officer/Detective/Sergeant for a suburban Chicago police department” whose assignments include: Patrol, Field Training Officer, Criminal Investigations, Firearms & Tactics Training Unit, Crisis Intervention Team, and Tactical (SWAT + medical). Yeah, he’s impressive.
In the world of software and technology, we of course think we are the center of the universe. Spoiler alert - we’re not. I’ve followed Lou for years on Twitter because his world is so different from mine, and his insights always make me think. More often than not, they seem super applicable to tech.