Deep Dive: Problem ResearchActivities & Teaching Strategies
Active learning turns abstract problem research into a visible, collaborative process where students shift from passive observers to active problem-solvers. By moving, talking, and creating, they experience firsthand how real-world problems take shape in their own community, making the abstract concrete and the distant relatable.
Learning Objectives
- 1Analyze the information gathered to identify the core needs and constraints of a chosen problem.
- 2Evaluate the credibility and relevance of various research sources, distinguishing between primary and secondary data.
- 3Design a structured research plan outlining the specific questions to be answered and the methods for data collection.
- 4Synthesize research findings to articulate a clear and detailed problem statement for a technological solution.
Want a complete lesson plan with these objectives? Generate a Mission →
Gallery Walk: The Problem Wall
Students walk around the school and take photos or sketches of 'problems' (e.g., a messy bag area, a confusing sign). They post these on a wall and use sticky notes to vote on which ones could be solved with a digital tool.
Prepare & details
Explain what information we need to collect to fully understand our problem.
Facilitation Tip: During the Gallery Walk: The Problem Wall, post incomplete or vague problems as conversation starters to push students toward clarity and specificity.
Setup: Wall space or tables arranged around room perimeter
Materials: Large paper/poster boards, Markers, Sticky notes for feedback
Inquiry Circle: Stakeholder Mapping
Once a problem is chosen, groups draw a 'map' of everyone affected by it (the stakeholders). They discuss how the problem affects a student, a teacher, and a parent differently, ensuring their solution helps everyone.
Prepare & details
Evaluate the reliability of different sources of information.
Facilitation Tip: In Collaborative Investigation: Stakeholder Mapping, provide colored sticky notes to visually separate different user groups, making overlaps and gaps visible.
Setup: Groups at tables with access to source materials
Materials: Source material collection, Inquiry cycle worksheet, Question generation protocol, Findings presentation template
Think-Pair-Share: The Constraint Check
Students brainstorm their 'wildest' solutions to a problem. They then pair up to look at their 'constraints' (time, materials, skills) and narrow their ideas down to something they can actually build in the classroom.
Prepare & details
Design a research plan to gather relevant data.
Facilitation Tip: For Think-Pair-Share: The Constraint Check, give each pair a ‘constraint card’ with common limits (time, money, space) to anchor their discussion in reality.
Setup: Standard classroom seating; students turn to a neighbor
Materials: Discussion prompt (projected or printed), Optional: recording sheet for pairs
Teaching This Topic
Teach problem identification by modeling curiosity and skepticism. Ask students to challenge assumptions by asking ‘Why does this happen?’ and ‘Who feels this most?’ Avoid letting them jump to solutions too quickly—use sentence stems like ‘The problem is… because…’ to force them to explain the pain point before proposing fixes. Research shows that students who articulate problems clearly before researching are more focused and persistent in their work.
What to Expect
Successful learning looks like students who can clearly articulate a genuine community problem, identify who it affects, and explain why technology could help. They should move from vague ideas to specific, researchable challenges with defined users and constraints.
These activities are a starting point. A full mission is the experience.
- Complete facilitation script with teacher dialogue
- Printable student materials, ready for class
- Differentiation strategies for every learner
Watch Out for These Misconceptions
Common MisconceptionDuring Gallery Walk: The Problem Wall, watch for students who post problems that are too broad or global, like ‘Pollution is bad.’
What to Teach Instead
Redirect them by asking, ‘What specific place in our school or neighborhood shows this problem?’ and have them rewrite it as ‘Trash bins overflow in the Year 3 eating area by lunchtime.’
Common MisconceptionDuring Collaborative Investigation: Stakeholder Mapping, watch for students who only list people affected by the problem without considering who else might care or have power to help.
What to Teach Instead
Prompt them to add ‘secondary stakeholders’ like the school council or local council, using the mapping template’s three columns: directly affected, indirectly affected, and decision-makers.
Assessment Ideas
After Gallery Walk: The Problem Wall, provide students with a mixed list of problem statements (some clear, some vague). Ask them to circle the clearest one, then underline the specific details that make it researchable.
During Collaborative Investigation: Stakeholder Mapping, ask pairs to share one stakeholder group they identified and one assumption they made about that group. Listen for whether they’ve moved beyond obvious users (e.g., students) to include less obvious ones (e.g., cleaners, parents).
After Think-Pair-Share: The Constraint Check, collect their pairs’ top constraint and ask them to explain in one sentence why that constraint matters for their problem. Use their responses to identify common themes or gaps in their understanding of feasibility.
Extensions & Scaffolding
- Challenge: Ask early finishers to research one potential solution from a peer’s problem wall post and prepare a 60-second pitch for why it’s worth pursuing.
- Scaffolding: Provide sentence starters on the Problem Wall (e.g., ‘The problem is ______ because ______. It affects ______.’) for students who struggle to frame their thoughts.
- Deeper exploration: Have students interview a stakeholder from their mapped community to validate their problem and gather real user insights before moving to solution design.
Key Vocabulary
| Constraint | A limitation or restriction that affects the design or solution of a problem, such as time, materials, or budget. |
| Data | Facts and statistics collected together for reference or analysis, which help in understanding a problem fully. |
| Reliability | The quality of being trustworthy and dependable, referring to how accurate and consistent information from a source is. |
| Research Plan | A detailed outline of how a problem will be investigated, including research questions, methods, and expected outcomes. |
| User Needs | The specific requirements or desires of the people who will use or be affected by a technological solution. |
Suggested Methodologies
More in The Grand Challenge
Brainstorming Solutions for the Challenge
Teams brainstorm a wide range of potential digital or hybrid solutions for their identified problem.
2 methodologies
Planning the Digital Solution
Students plan the sequence of actions (algorithms) and the visual layout (user interface) for their digital solution.
2 methodologies
Developing the Digital Solution
Teams begin coding and building their digital solution using block-based programming or other tools.
2 methodologies
Adding Interactive Elements
Students incorporate interactive elements like buttons, sliders, or simple sensors (if available) to enhance their digital solution.
2 methodologies
Testing and Debugging the Solution
Teams rigorously test their solution, identify bugs, and refine their code and design.
2 methodologies
Ready to teach Deep Dive: Problem Research?
Generate a full mission with everything you need
Generate a Mission