How Might We: Turn Problems Into Class Projects
A good "How might we" question can take a class from "this is annoying" to "let's fix it" in about ten minutes.

On this page
You ask students to brainstorm solutions, and you get one of two things: blank stares, or fifty ideas that have nothing to do with the actual problem. The trouble usually isn't the kids. It's that the question they're answering is either too big to grip or too narrow to be interesting.
That's exactly the gap a "How might we" question fills. It's a tiny phrase that does a surprising amount of work.
In this guide:
- What a "How might we" question actually is
- Why this small reframe gets better ideas out of students
- A step-by-step way to write one with your class
- A real example from a 5th grade classroom
- Variations, common mistakes, and quick answers to FAQs
What is a "How might we" question?
A "How might we" question (often shortened to HMW) is a way of phrasing a problem so it invites solutions instead of complaints. You take a frustration or an observation and rewrite it as an open, hopeful question.
It comes from IDEO's Design Thinking for Educators toolkit, where it sits between understanding a problem and brainstorming fixes for it. The structure is deliberate. "How" assumes a solution exists. "Might" gives permission to fail and try wild things. "We" makes it a shared job, not one kid's burden.
Here's the move in practice. Broad complaint: "Lunch is chaotic." Reframed: "How might we redesign the transition into the cafeteria so it feels calmer for fifth graders?" Same problem, completely different energy.
Why does it work?
It works because most brainstorms fail before they start, and HMW fixes the part that usually breaks: the framing of the problem itself.
According to IDEO's Design Thinking for Educators toolkit, the phrase is built to "open the door to ideation." Each word pulls its weight. "How" presumes there are answers, so students stop debating whether the problem is solvable and start looking for solutions. "Might" lowers the stakes, which matters a lot for students who freeze up when they think there's one right answer. "We" turns it collaborative.
There's also a Goldilocks effect. A question that's too broad ("How might we make school better?") gives students nowhere to stand. One that's too narrow ("How might we add a second trash can?") has only one answer. A well-framed HMW lives in the middle, specific enough to picture, open enough to explore.
And it separates two jobs that students tend to mash together: figuring out what the real problem is, and figuring out what to do about it. By the time you've written a sharp HMW, the hard thinking about the problem is already done.
How to run it, step by step
You can do this in about 30 minutes with sticky notes and chart paper. Here's the sequence the IDEO toolkit uses, in plain terms.
Name the broad concern out loud. Start with the messy version. "Group work always falls apart." "Nobody reads the feedback I write." Write it where everyone can see it. Don't polish it yet.
Dig into the why. Ask what's really going on underneath. What's the context? Who's affected? What's getting in the way? This is the step most people skip, and it's the one that produces a sharp question instead of a generic one.
Rewrite it as "How might we..." Take the underlying insight and phrase it as an open question. "How might we make sure every group member has a real job to do?"
Stress-test the question. Read it back and ask: is it too broad? Too narrow? If you could only answer it one way, tighten the problem. If you have no idea where to begin, narrow the scope or the audience.
Refine until it feels right. Adjust the wording. Naming a specific group ("for fifth graders," "during the first five minutes") often makes a vague question instantly usable.
Pick two to four to actually use. If you generated several HMW questions, choose the few worth brainstorming on. You don't need to chase all of them.
Then, and only then, brainstorm. Now you run the real ideation: defer judgment, go for quantity, build on each other's ideas, write silently first, then share round-robin. The HMW is the prompt that makes that brainstorm productive.
The thing to protect here is your own patience at step 2 and step 4. The toolkit is blunt about the teacher's job: resist accepting vague challenge statements. A weak question guarantees a weak brainstorm.
A real example: 5th grade, advisory time
Picture a 5th grade advisory class where the daily walk from the classroom to the cafeteria is a disaster. Kids are wound up, the line breaks apart, somebody gets bumped, and lunch starts with three students already upset.
The teacher writes the broad version on the board: "Lunch transitions are chaotic." Then she runs the dig-into-why step. Students notice it's worst right at the doorway, when everyone crowds the same spot, and that the noise makes the anxious kids more anxious. The underlying insight: they need a predictable routine that calms things down instead of revving them up.
So the class reframes it: "How might we redesign the transition into the cafeteria so it feels calmer for fifth graders?" They test it. Specific enough? Yes, it names the moment and the audience. Open enough? Yes, there are dozens of possible answers.
From there the brainstorm produces real ideas: a two-line system, a 30-second breathing cue at the door, a rotating "line leader" job, soft background music as a signal. The class picks one to try the next week. The whole thing took one advisory period, and the students owned the fix because they wrote the question.
Variations and when to use it
The basic HMW works almost anywhere, but a few tweaks help.
Student-generated vs. teacher-generated. With older students, hand them the whole process and let them write their own HMW. With younger ones, you might draft two or three options and let them choose and tweak.
As a project launcher. HMW is the natural front end of any project-based unit. Spend a session turning a real local issue into a HMW, then let the project answer it. It gives the work an authentic purpose instead of a worksheet feel.
As a quick discussion warm-up. You don't need a full design unit. Drop a single HMW on the board as a Do Now and brainstorm for five minutes. It's a fast way to surface ideas before a debate or a writing task.
Across subjects. Science: "How might we keep this habitat model alive for a week?" History: "How might we present both sides of this conflict fairly?" Math: "How might we use less material and still build a strong bridge?" The structure travels.
Common mistakes to avoid
Skipping the "why" step. If you jump straight from the complaint to the HMW, you'll get a question that just restates the complaint. The insight underneath is what makes it good.
Writing it too broad. "How might we improve our school?" sounds inspiring and gives students nothing to grab. Add an audience or a moment.
Writing it too narrow. If the question contains its own answer, there's nothing to brainstorm. "How might we buy more glue sticks?" is a shopping decision, not a design challenge.
Smuggling in a solution. "How might we use an app to..." has already decided the answer. Keep the question about the problem, not your favorite fix.
Rushing to ideas. The point of HMW is to slow down at the framing stage so the brainstorm later runs fast. Don't trade that away.
How UNI-FIED helps
If writing a sharp question for every topic sounds like one more prep task, that's fair. UNI-FIED builds routines like "How might we" into ready-to-teach activity cards for your specific topic and grade, so you get a well-framed challenge, the brainstorm structure, and the facilitation prompts already laid out. You spend your time coaching the conversation, not staring at a blank chart paper.
Frequently asked questions
How long does a "How might we" activity take? The framing part runs about 30 minutes. Add another 30 to 60 if you continue into a full brainstorm. As a quick warm-up, five minutes is plenty.
What grades does it work for? The IDEO toolkit pegs the framing work at roughly grade 4 and up, including with adults. Younger students can join in if you draft the question options for them to choose and adjust.
Do I need to teach the whole design thinking process first? No. HMW stands on its own as a reframing tool. It's most powerful inside a full design unit, but it's perfectly useful as a one-off.
What if the question my class writes is still bad? That's normal, and it's a teaching moment. Read it back and ask the two test questions: too broad, or too narrow? Adjusting one phrase usually fixes it.
Where can I learn more? The full method lives in IDEO and Riverdale's Design Thinking for Educators toolkit, which lays out all five phases and the methods inside each.
Try it the next time a student gripes about something in your room. Catch the complaint, ask why, and turn it into a "How might we" — you might be surprised how fast they start solving it.
Sources & further reading
Run this in your classroom tomorrow
UNI-FIED turns your topic, grade, and lesson length into ready-to-teach activity cards built on routines like this one — no prep, no curriculum change.
See how UNI-FIED worksRelated routines
Published September 8, 2026.