Do we have a well-defined objective and sufficient understanding of the related environment to guide and evaluate technology decision making?
Creating a well-defined objective among a new team can be time consuming. One of the consequences of this is that teams often rush through it and make dangerous assumptions about each person’s understanding of the purpose of the project. The team may make other dangerous assumptions related to who already knows what and how easy or difficult something may be to do. Moving forward without testing assumptions and ensuring the objective is collectively understood can be a shortcut to failure. Further, a clear statement of the objective is central to an alternatives analysis. Do we know enough about our users to make good choices? Knowing your users is key to choosing the correct technology for your project. Knowing when plans will need to be adjusted to ensure that all interested parties can participate, no matter their technological capability, is critical. Sometimes multiple strategies are not possible due to time or financial constraints. If this is the case, then priorities need to be
