 SO we get customers to look at the critical few features that we will be building in the coming few releases. Rick: Please remember that our customers see SO many issues in the field currently, they are desperate to understand when and how we will be fixing these issues. With all the focus that we would be giving to the future, let's not forget our current woes, which we need to rectify to improve customer satisfaction. So we can understand that different stakeholders have different needs for information about the product under development. In an ideal product development environment, all these concerns get addressed with the technology roadmap of the product. The ways in which the product gets developed depends on the particular road-mapping process the product company actually may follow. Note We will be covering the possible processes for technology road mapping in more detail in Chapter 6. In short though, the way in which the roadmap gets developed may depend on some of the following aspects: Size of the organization. Smaller companies may prefer shorter and more informal processes for roadmap development. The number of stakeholders involved. For organizations like 3GPP, where there are many stakeholders actively participating in the road-mapping process, this means a very formal process governed by workshops to collect input, followed by detailed plans for incorporation of common elements into the roadmap for a standard, such as the materials and documentation recorded about a 3GPP Rel 12 RAN workshop (http://www.3gpp.org/news-events/3gpp-news/1266-Future-Radio-in-3GPP) Time and effort the organization is prepared to invest in the process. Position of the organization in the industry. Companies in leadership positions may like to publish their roadmaps in all channels and help shape the future and get their followers to align to the same. CHAPTER 4 NETWORK ROADMAPS Also the form in which the roadmaps could be expressed also varies a lot, depending on existing organizational practices and some of the factor