Typical Discovery Workshop Format
Product Problem Statement and Assumptions
WWT works with key stakeholders to clearly define what problem the identified edge application is looking to solve. Once this is established, WWT will determine a set of base assumptions about the solution to develop a foundation on which the journey map and design can be built.
We work with customers to identify the personas consuming the identified edge application to ensure users' needs are being met, ensuring the success of the application as it is rolled out.
Leveraging the information gathered to this point, we work with key stakeholders to establish a solution roadmap. This journey is dynamic, but establishing the initial roadmap gives customers and WWT a path to design features of the application itself.
Identify Business Outcomes and Feature Set
With the problem identified, we work with customers to establish measurable business outcomes that can be tied to the application throughout the development process. These business outcomes are key to determining which features need to be included in the edge application and truly drive value to the business.
Hypothesis Creation and Prioritization
With a clear vision and problem statement, the design process can begin. Taking the feature set necessary to meet the business outcomes, we work with customers to determine a hypothesis on the next steps and prioritize those steps to start achieving the identified business outcomes.
The last part of the workshop is where the application starts to come to life. Leveraging the prioritization established, WWT works with customer stakeholders to design different aspects of the application at a high-level and determine the necessary technology to start creating a valid proof of concept for the edge application.