You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please include the relevant information for each stage of the process.
1. Problem Scoping
- What is the exact problem?
- Is it symptomatic of some underlying issue?
- How do we know for sure it's a problem?
- Is this a problem for some but not others?
- How BIG is the problem? # of people / impact of problem (rats vs. dents)
Problem: Students are having difficulty following along with tutorial instructions and finding the right blocks to use.
Evidence this is a problem: Ran a user study and found that 8 out of 9 respondents ran into problems knowing which blocks to use. See OneNote
Impact of the Problem: Affects mostly beginners who are using tutorials. Impact is that users might be blocked when using tutorials to create games, get frustrated and never come back. Strategically, this represents a big blocker to our Learning Outcomes metrics (Tutorials Started/Completed)
At the end of this stage, determine if this is a Problem/Opportunity we want to solve now, later or never.
Yes, we want to solve this issue now. We may used a phased approach.
2. Brainstorming Solutions
What are some different options for a solution?
- Provide 2 or more options
- Think blue-sky, and think on-the-ground
- Get as visual as possible, but no polish (whiteboard sketches)
- Yes AND
Insert relevant information here or link to OneNote page or Figma...
3. Picking Ideas
Pick a couple ideas to move forward:
- What’s the minimum viable solution?
- What’s the best possible solution?
- How well do we think it solves the problem?
- How much work is it to implement?
- Is there a good/better/best or phased approach?
- How does it impact other parts of the product or user experience?
- Does this solution bring along any other benefits?
- Pros / Cons list can help narrow down ideas
Insert relevant information here...
4. Design Mock-ups
- Design wireframes or mock-ups for the selected ideas to test
- Designs may be passed off to engineering to implement, or directly used for Testing
- For big feature areas, may think about phased design approaches - North Star design vs. MVP design
Insert relevant information here or link to Figma or Design files...
5. Testing
- How will we know these solutions work?
- What evidence do we already have?
- What experiments do we need to run to collect this evidence?
- Telemetry, telemetry, telemetry
Insert relevant information here or link to User Study results, Kusto Dashboards, etc...
The text was updated successfully, but these errors were encountered:
Please include the relevant information for each stage of the process.
At the end of this stage, determine if this is a Problem/Opportunity we want to solve now, later or never.
Insert relevant information here or link to OneNote page or Figma...
Insert relevant information here...
Insert relevant information here or link to Figma or Design files...
Insert relevant information here or link to User Study results, Kusto Dashboards, etc...
The text was updated successfully, but these errors were encountered: