We return to Develop methods when we need to: (select all that are true)Group of answer choicesRevisit our users' Journey MapBrainstorm more features for our prototypeDo more researchBetter understand the context of the problemAdd depth and fidelity to our prototypeTest again or with different stakeholdersSummarize test resultsEvaluate & possibly rephrase our How Might We in light of testing

We return to Develop methods when we need to:

1. Better understand the context of the problem: Developing methods can help us gain a deeper understanding of the problem we are trying to solve. This can involve further research, analysis, and exploration of the problem space.

2. Do more research: If our initial research did not provide enough information or if new questions have arisen, we may need to return to the Develop phase to conduct additional research.

3. Revisit our users' Journey Map: The user journey map is a tool that helps us understand the user's experience. If we need to revisit or revise this map, we may need to return to the Develop phase.

4. Brainstorm more features for our prototype: If we need to add more features to our prototype, we may need to return to the Develop phase to brainstorm and design these features.

5. Add depth and fidelity to our prototype: If our prototype needs more detail or if we want to make it more realistic, we may need to return to the Develop phase.

6. Test again or with different stakeholders: If our initial testing did not provide enough information or if we want to test our solution with different stakeholders, we may need to return to the Develop phase.

7. Summarize test results: After testing, we may need to return to the Develop phase to analyze and summarize our test results.

8. Evaluate & possibly rephrase our How Might We in light of testing: If our testing has led us to reconsider our problem statement (the "How Might We"), we may need to return to the Develop phase to rephrase it.