The Design Thinking Framework

Four stages.
Real change.

FIDS is how students transform frustration into action. Feel the problem, Imagine solutions, Do the work, Share the story — a structured path from empathy to impact, built for the K-12 classroom.

Feel Imagine Do
Stage 01
F
Feel
What issue in your community do you care about?
Stage 02
I
Imagine
What could change look like?
Stage 03
D
Do
Make it happen.
Stage 04
S
Share
Tell your story.

Classroom activities for every stage

Practical, grade-appropriate activities with differentiated tips for K-2, 3-5, and 6-8 classrooms. No special materials required.

F Feel

Build empathy. Notice what's wrong.

Before students can solve problems, they need to feel them. This stage develops the emotional intelligence and observation skills that turn bystanders into changemakers.

Community Walk & Wonder Journal
K–2 3–5 6–8

Students walk their neighborhood (or school) with a "Wonder Journal" — a simple notebook where they draw or write three things that bother them, three things they love, and one question they have. Back in class, they share observations and begin identifying patterns of need.

Grade-level tips
K–2 Use drawings only. Provide sentence frames: "I noticed ___. It made me feel ___."
3–5 Add a "Who is affected?" column. Introduce the word "empathy" and discuss what it means to walk in someone else's shoes.
6–8 Assign 5 community interviews before the next class. Students must ask: "What's the hardest part of living here?" Debrief patterns across responses.
The Empathy Map
3–5 6–8

Students choose one person affected by a community issue and fill out a four-quadrant map: what does this person Say, Think, Do, and Feel? This structured exercise builds perspective-taking before jumping to solutions.

Grade-level tips
3–5 Start with a familiar example (a new student, a school janitor) before moving to a community figure. Work in pairs to reduce intimidation.
6–8 Require students to conduct a real interview before completing the map. Challenge them to find contradictions between what people say vs. what they do.
One-Sentence Problem Statement
K–2 3–5 6–8

The capstone of the Feel stage. Students craft a single sentence that captures the problem they want to change: "[Person] needs [thing] because [insight]." This forces specificity and prevents vague projects that affect "everyone."

Grade-level tips
K–2 Provide fill-in-the-blank: "I want to help ___ because ___." Accept drawings alongside words.
3–5 Show 3 example statements (good and bad) and ask students to rank them. Good statements name a specific person, not a vague group.
6–8 Introduce the concept of "root cause vs. symptom." Challenge students to ask "why?" five times to get past surface-level problems.
I Imagine

Dream big. Then get specific.

Imagination is a skill, not a trait. This stage gives students structured tools to generate bold ideas, evaluate them honestly, and converge on a plan worth executing.

Crazy 8s Brainstorm
K–2 3–5 6–8

Fold a sheet of paper into 8 panels. Set a timer for 8 minutes. Students sketch one idea per panel — no judgment, no explaining, just generating. The goal is volume over quality. After, they circle their top idea and explain why.

Grade-level tips
K–2 Reduce to 4 panels and 4 minutes. Let students use stickers, stamps, or cut-outs. Celebrate the most imaginative idea, not the most "realistic" one.
3–5 After sharing, group similar ideas on a sticky note wall. Look for clusters — they reveal what the class cares most about solving.
6–8 Add a constraint round: generate 8 more ideas but each must cost zero dollars. Constraints push creative thinking beyond the obvious.
The "How Might We" Question Sprint
3–5 6–8

Transform the problem statement into "How might we ___?" questions. Students write as many HMW questions as they can in 10 minutes on individual sticky notes, then vote on the most interesting ones to explore. The phrasing intentionally holds possibility open.

Grade-level tips
3–5 Model five HMW questions before students generate their own. Provide the stem pre-printed on sticky notes so they focus on the idea, not the format.
6–8 After voting, challenge the top-voted question: "Is it too narrow? Too broad?" Teach students to reframe until the question feels generative but focused.
Solution Decision Matrix
3–5 6–8

Students list their top 3 ideas and score each on three dimensions: Impact (will this actually help?), Feasibility (can we actually do it?), and Excitement (do we care enough to see it through?). The highest total score isn't always the winner — discussion is the point.

Grade-level tips
3–5 Replace numbers with thumbs (👍 👍👍 👍👍👍) for scoring. Focus discussion on feasibility — kids often dream bigger than time allows.
6–8 Add a "Who else is already doing this?" column. Researching similar efforts teaches that iteration beats starting from scratch, and collaboration > competition.
D Do

Take action. Learn by doing.

This is where plans meet reality. Students build, run, and iterate on their project — and encounter the gap between ideas and execution that defines real-world learning.

Project Roadmap & Role Assignment
K–2 3–5 6–8

Teams build a simple project roadmap on a whiteboard or poster: three milestones, clear roles (Leader, Researcher, Builder, Communicator), and a "What could go wrong?" risk column. The process of planning surfaces disagreements early — before they derail the project.

Grade-level tips
K–2 Use a visual "job board" with picture cards for each role. Rotate roles weekly so every student experiences leadership.
3–5 Introduce a "check-in day" every week where teams share one thing that worked and one thing that didn't. Normalize setbacks as data, not failure.
6–8 Assign a "devil's advocate" role in each team — someone whose job is to challenge assumptions. This prevents groupthink and builds resilience before obstacles arise.
Prototype & Test Loop
3–5 6–8

Before committing to a full project, teams build a low-fidelity prototype (cardboard, paper, a single event, or a mock flyer) and test it with 3 real people from the community. They capture feedback in a "What worked / What confused / What we'd change" grid, then iterate.

Grade-level tips
3–5 Have students test with a partner class or younger students first. Peer feedback is less intimidating than adult feedback and builds testing habits.
6–8 Require a community partner (local organization, business, city council) to be part of at least one test session. Real stakes sharpen preparation.
The "Did It Work?" Reflection
K–2 3–5 6–8

After running the project, teams answer three questions: What was the actual impact? How do we know? What would we do differently? This structured debrief prevents the common trap of celebrating completion instead of examining effect.

Grade-level tips
K–2 Use a "happy/sad/meh" face scale. Have students draw before/after pictures of the problem to make impact visible and concrete.
3–5 Introduce simple metrics: How many people did we reach? How many said it helped? Numbers make impact real for kids who can count but haven't yet thought in data.
6–8 Require a before/after survey of the community members they targeted. Even 5 responses teaches the discipline of measuring outcomes, not just outputs.
S Share

Tell the story. Inspire others.

Change doesn't scale until it's shared. This stage teaches students to document, present, and communicate their work in ways that move people — a skill that outlasts the project itself.

The Change Story Poster
K–2 3–5 6–8

Teams create a visual narrative poster with four panels — Problem, Our Idea, What We Did, What Changed — displayed at a school-wide "Impact Fair." The constraint of four panels forces students to identify what actually mattered in their project and discard the noise.

Grade-level tips
K–2 Use photographs from each project phase. K-2 students are proud of photos of themselves in action — it makes the abstract tangible and the sharing joyful.
3–5 Add a "What's next?" panel. Projects rarely end — encourage students to plan one follow-up action that the next class could continue.
6–8 Invite community partners, parents, and local officials to the Impact Fair. Public audience = public stakes. Students prepare for questions, not just applause.
2-Minute Pitch Presentation
3–5 6–8

Each team delivers a timed, structured 2-minute pitch to a panel of community members: the problem (30 sec), the solution (30 sec), the result (30 sec), and the ask — what do they need to go further? (30 sec). The ask teaches students that sharing is not just reporting, it's requesting support.

Grade-level tips
3–5 Practice with a "Shark Tank" classroom simulation first. Let students ask questions of each other — giving feedback is as valuable as receiving it.
6–8 Require each presenter to open with a personal story — the moment they felt the problem themselves. Stories activate emotion; data backs it up. Both are required.
Documentation for Future Classes
3–5 6–8

Teams produce a brief "project guide" — a one-page document written for the next class that wants to tackle the same issue. It includes what they learned, what resources they found, who their community contacts are, and what they'd do differently. This is sharing as institutional memory.

Grade-level tips
3–5 Frame this as a letter to a future student. "Dear next year's 4th grader…" is less intimidating than "write a report" and more likely to be genuinely useful.
6–8 File the guide in the school library or submit it as a DFC project entry. Real archiving creates real accountability — and teaches that documentation is part of the work, not an afterthought.

Ready to start your first FIDS project?

Register to submit projects, track your class's progress through each stage, and connect with Design for Change USA.

Register to submit your first project →

Free for educators. No credit card required.