Job description • What makes a good product • Organizing software product ideas • Elimination round • Score the survivors • Describing product ideas • Creating a roadmap • Resource commitment • Reading • Communication
Convincing your customer and your own development team that this new idea is worth it.
Responsibility without any actual authority
Who should be involved in the discussion?
Role doesn’t qualify, but customer exposure. Anyone having direct exposure to customer reality. Sales hearing, support investigating failures, engineer processing requirements.
It’s all about delivering a cohesive product with well defined boundaries.
Avoid death by preference.
Every optional feature, configuration switch is hidden cost.
There is no small change. Do not use effort as a reason to make a product.
Group by customer impact:
Group by domain:
Can you
in under 70 chars each?
Combination of a minimal press release and acceptance criterias.
Establish scope + create narrative:
Define completion:
Mission, vision, strategy, roadmap
Product vision should fit in company vision.
Product one-pagers and roadmap go to leadership for resource commitment.
Start reading here: How to get into product management
Email:
#sw #communication