What is a primary objective when discussing current state vs. future state in a Discovery phase?

The primary objective of discussing the current state versus the future state during the Discovery phase is to determine what functionality the customer would like to adopt. This phase is crucial for understanding the client's needs and expectations, allowing the team to identify gaps between the existing capabilities and the desired outcomes. By focusing on the future state, stakeholders can articulate their goals, desired features, and overall vision for the transformation that they seek. This ensures that the developed solution aligns closely with the customer's aspirations and requirements, paving the way for successful implementation.

While the elimination of manual processes, cost comparisons, and reviews of past project successes may also be relevant in different contexts, they do not capture the primary aim of the Discovery phase as effectively as identifying desired functionality does. Understanding what functionality the customer wants is essential for guiding the design and development process toward a solution that truly meets their needs.