​​​​​Goal: Clearly establish purpose and area(s) of consideration.

 

Description: Seneca once said that “If one does not know to which port one is sailing, no wind is favorable.” It is essential that you establish the goal of the technology roadmap in the first stage – that is to say, if the roadmap is successfully implemented, what would it accomplish. For instance, if your business wishes to grow 10x in size over the next 2-3 years, the roadmap will be dramatically different than if you wish to have a 10% growth year after year. If you wish to do business in one location in the United States, the technology needs are dramatically different than if you wish to do business in a variety of countries with offices spread throughout the world. It is essential that we start with the end in mind and select and use our tools to achieve the desired goal; we certainly do not want to find the latest tools that are being offered, hope they are the right ones for the job, and end up as the proverbial person who has a hammer and so sees nails everywhere. We will use our breadth of knowledge in the technology industry to guarantee that you are considering which tools are right for the job. 

 

After establishing the “why” behind the roadmap project, we establish “what” the roadmap is expected to do. While “defining the technology roadmap” may seem like a tempting definition to use for the project, it leaves room for varying interpretations. Best practices in Project Management methodology suggest that we spend time carefully defining what is considered in and out of scope, and what the objectives are that we wish to accomplish during the project. When dealing with a technology roadmap, this means that we anticipate questions such as whether the roadmap simply identifies the requisite technologies we wish to use, or if we will develop high level requirements for the various technology components. While custom software often plays a role in complex roadmaps, do we wish to develop new technologies? Or would that be considered out of scope? A good scope, written concisely, will take up at least 2-3 pages of content, and give clear examples of what is in and out of scope for the project. Establishing the scope early on, ensures a smoother project, builds a common vision, and establishes boundaries to prevent diffusion of effort from the project’s inception. We assist in defining the scope for your project by guiding you through our questionnaire about what should be addressed in the project to build a common vision and boundaries of what this project will address.

  •  
    Technology Roadmap
  •  
    Technology Roadmap