AMA: Splunk Director of Product Management, Richard Shum on Product Roadmap & Prioritization

When I prioritize or stack rank a list of items, I typically find it helpful to understand how each item can (a) deliver customer impact and (b) increase engineering happ...

Before jumping into the "must do" work, it's best to understand the reason for doing the work. Sometimes the "must do" work is warranted. For example, compliance could ...

Ideas can come from many places. They include customer feedback calls, customer troubleshooting sessions, customer submitted ideas (at Splunk, we have an idea submission ...

Say exactly that "We're pivoting our product. There are a lot of unknowns and it's difficult to plan too far out." It's perfectly fine to communicate honestly. If there's...

In my mind, several groups of stakeholders often influence the roadmap. They include your customers (both internal and external), your product team (e.g., engineering, de...

It's always good to review roadmaps with leadership on an ongoing basis. These touchpoints allow you to keep your leadership informed and give you the opportunity to soli...

Who to focus on often depends on the maturity of the product. At the beginning stages of the product, we focus heavily on prospective users. When the product is mature, w...