Product lines sunset. Your teams need a space to experiment, learn, and review alternatives for a short period. You want to improve your product line organization. The feedback we receive from our users form the basis of how we improve our software. This is no exception.

Deciding what products and features to offer to your customers requires a clear understanding of your markets. Once you identify market segments, you can propose different product configurations to meet each segment's needs. You can perform an analysis of your products side-by-side against your competition in each segment to see how the segment is being served and find opportunities for new and improved products.

Does this sound familiar? You're deep into a new product development process and heads down working on executing the product plan. Suddenly, you realize discrepancies in the products and feature definitions, the timelines to launch them, and their configurations. A myriad of spreadsheets, text documents, and presentation files stored in different places make it confusing to navigate as you are not sure what the latest approved decisions and definitions are. This means that now is the time to stop what you're doing and jump into the 'data scramble' and send a deluge of emails to product planning and product management teams to get the answers you need with a definitive picture of the product line.