Naming Product Goals Weak Development Team 
Roman Pichler
SEPTEMBER 7, 2021
I therefore recommend applying a different product roadmapping approach and using goal-oriented roadmaps , which are also called outcome-based. As their name suggests, these roadmaps focus on product goals or outcomes such as acquiring customers , increasing engagement , and future-proofing the product by removing technical debt.
Roman Pichler
MAY 11, 2021
Instead, you should engage the stakeholders, leverage their expertise, and generate as much buy-in as possible , as I explain in more detail in my article “ Stakeholder Management Tips for Product People.” ” But do not allow people to dominate and tell you what to do, and don’t agree to a weak compromise.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Roman Pichler
FEBRUARY 14, 2023
Listen to the audio version of this article: [link] 1 Complement Scrum with a Product Discovery and Strategy Process Scrum is a simple framework that helps teams develop successful products. Continue the discovery and strategy work while the product is being developed. But don’t stop there.
Roman Pichler
JUNE 1, 2020
The first one carries the risk of being a feature broker and offering a product that has a weak value proposition, gives rise to a poor user experience, and consists of a loose collection of features. A stakeholder is anyone who has a stake in your product, who is affected by it, or who shows an interest in the offering.
Roman Pichler
APRIL 5, 2022
For product strategy and roadmap meetings, I recommend involving the key stakeholders , for example, someone from sales, marketing, support, and finance, as well as development team representatives—ideally members who know about the user experience (UX), architecture, and technologies. State objective and agenda.
Roman Pichler
APRIL 1, 2020
Here is why: We routinely interact with individuals who have different perspectives, interest, and needs, such as users, customers, stakeholders , development team members. Users don’t always have the same wants and needs as customers, and the ideas of the stakeholders and dev team may diverge.
Roman Pichler
APRIL 1, 2020
Here is why: We routinely interact with individuals who have different perspectives, interest, and needs, such as users, customers, stakeholders , development team members. Users don’t always have the same wants and needs as customers, and the ideas of the stakeholders and dev team may diverge.
Expert insights. Personalized for you.
322 
Let's personalize your content