NILG.AI
Not a member? Sign up now
NILG.AI on Mar 15, 2026
Ever felt completely stuck on a nagging business problem? That’s where a surprisingly simple technique called How Might We (HMW) statements can be a game-changer. It’s all about reframing those frustrating challenges into exciting opportunities, pulling your team out of a problem-first mindset and into a solution-finding groove.
When we’re up against a tough obstacle, it's human nature to see it as a brick wall. We say things like, "Our manual data entry is slow and full of mistakes." It’s a statement of fact, but it feels like a dead end. This way of thinking keeps us trapped in just trying to patch up a broken process.
HMW statements completely flip the script. By turning the problem into an open-ended question, you create breathing room for new ideas to emerge. That frustrating data entry issue becomes something like, "How might we use AI to automate data entry and give our team time for more strategic work?" All of a sudden, the problem isn’t a barrier—it’s a launchpad for tangible innovation.
This isn't some new-fangled corporate jargon. The "How Might We" approach has a proven track record, first popularized by Procter & Gamble in the 1970s. It’s credited with helping them identify market opportunities and launch successful products by reframing challenges and slashing their ideation time significantly.
Fast forward to today, and you’ll find leading AI and data consulting firms using the same principle in their high-stakes strategy sessions. An executive team might kick off a brainstorm by asking, "How might we automate 40% of our operations managers' manual data tasks with predictive analytics?" This question immediately points the team toward a specific, high-impact business goal.
The real magic of a How Might We statement is that it shifts your team’s focus from obsessing over the problem to exploring potential solutions. It’s an open invitation to collaborate and ideate without the pressure of finding the one "right" answer right away.
This simple linguistic trick is incredibly powerful. It changes how you see the problem, helping you pinpoint the best places to make an impact. This idea is central to leverage thinking and finding leverage points in business systems. Instead of being bogged down by what you can't do, you and your team start to see all the things you could do.
To see this in action, let's look at how you can reframe common business roadblocks.
| Common Business Problem | Constraining Mindset | Empowering How Might We Statement |
|---|---|---|
| "Our customer churn rate is too high." | "We need to stop customers from leaving." | "How might we create a loyalty program that makes customers feel truly valued?" |
| "Our onboarding process is confusing for new hires." | "The onboarding manual is too long." | "How might we design an interactive and engaging first-week experience for new employees?" |
| "We can't keep up with support ticket volume." | "We need to hire more support agents." | "How might we use an AI chatbot to resolve 50% of common customer questions instantly?" |
This shift from a fixed problem to an open-ended question is more than just semantics. It creates a completely different psychological environment for your team.
This simple change in wording has a profound effect on team culture. It builds a sense of curiosity and shared ownership, making it safe for everyone to throw ideas into the ring without fear of being wrong. It's a foundational element in many modern business innovation models that are fueling growth and making companies more efficient.
Ever wonder why some how might we statements spark a wildfire of creative ideas while others just fizzle out? It's not magic. The secret is surprisingly simple, and it all comes down to the three little words that make up the phrase.
A perfectly crafted HMW statement is like a great expedition brief—it points your team toward a mountain peak but doesn’t dictate the exact trail they have to take. It gives them a clear goal but leaves room for them to forge their own creative path to the top.
Let's break down why this simple phrase is so effective.
Think of "How Might We" as a recipe for collaborative genius. Each word has a specific job to do, and together, they shift your team’s entire mindset from dwelling on problems to exploring possibilities.
How: This word immediately grounds the conversation in reality. It assumes a solution is out there and challenges the team to start thinking about how to get there. It’s practical, forward-looking, and cuts straight through any "it can't be done" roadblocks.
Might: This is where the magic happens. "Might" is an open invitation to play. It gives everyone permission to throw out ideas that are a little wild, half-baked, or not guaranteed to work. It takes the pressure off, encouraging a flood of suggestions, from the safe bets to the truly ambitious swings.
We: This little word is all about teamwork. It makes it clear that this is a shared challenge, not one person’s problem to solve. It pulls everyone into the conversation, fostering a sense of collective ownership and encouraging people to build on each other's ideas.
This structure isn't new; it has been battle-tested for decades. The legendary design firm IDEO made HMW statements famous, using them to drive measurable improvements in client innovation outcomes. For businesses in the AI and data space, the impact is just as real. A recent report found that teams using HMWs came up with 22% more actionable ideas per hour than those stuck in old-school brainstorming sessions. You can read more on how this framework unlocks creativity at dscout.
Okay, so you have the "How Might We" part down. But what comes next is just as crucial. The art is in finding that perfect sweet spot between being too broad and too narrow. Ask a question that's too vague, and you'll get a bunch of disconnected ideas. Get too specific, and you'll box your team in, killing creativity before it even starts.
A great HMW statement is broad enough for creative exploration but narrow enough to provide a solid launchpad. It's the difference between asking, "How might we make more money?" and "How might we use our customer data to create a new premium service?"
Let's say an AI consultancy is helping a client who's drowning in customer support tickets.
When you nail this balance, your HMWs become the most powerful tool in your innovation toolkit, consistently guiding your team toward breakthroughs that matter.
Alright, ready to roll up your sleeves and write some how might we statements? Now that you know what they look like, let's walk through how to turn those raw, messy insights into springboards for real innovation. This isn't about plucking ideas from thin air; it's a deliberate process for finding opportunity in everyday problems.
The whole thing breaks down into three main phases: gathering your raw materials, sharpening your focus with a point of view, and then unleashing your creativity to generate a ton of HMWs. Think of it like this: your insights are the ingredients, your point of view is the recipe, and your HMWs are all the different dishes you could create.
First things first, you can't ask good questions without understanding the problem on a deep level. This means you need to get out there and collect the raw material—the observations, frustrations, and data points that paint a clear picture of the challenge. Your job here is to listen, not to solve.
You can find great inputs from just about anywhere your business interacts with people or processes:
This simple structure is what turns a problem into an opportunity.
As you can see, "How" sets us up to think about solutions, "Might" gives us permission to explore wild ideas, and "We" keeps it collaborative. It’s a beautifully simple formula for reframing challenges.
Once you've collected your insights, it's time to make sense of them. The goal is to distill everything into a clear, actionable problem statement, which we call a Point of View (POV). A solid POV anchors your brainstorming session to a real user with a real need.
A great POV always has three key ingredients:
Put it all together, and you get a powerful statement: Our operations team needs a faster way to verify invoices because they spend half their day on manual validation, leading to burnout and delays. This becomes your North Star for everything that comes next.
Now for the fun part. With your POV as a launchpad, it's time to "explode" it into as many HMW statements as you can dream up. The name of the game here is quantity over quality. Don't filter, don't judge—just get every possible question out on the table.
Let’s stick with our example: Our operations team needs a faster way to verify invoices because they spend half their day on manual validation, leading to burnout and delays.
From that one sentence, you could generate all sorts of HMWs:
The magic of this step is that it forces you to think divergently. By asking a lot of different questions, you push past the obvious fixes and start exploring unexpected paths that can lead to truly creative solutions.
And this isn't just theory—it works. Well-crafted HMWs improve the quality of ideas, resulting in solutions that better address the core problem. For a data consulting business, this could mean framing a project with a question like, "How might we reduce process inefficiencies by 35% using computer vision for supply chain monitoring?" This grounds the work in a real business need and seriously cuts down on deployment risk. If you want to dive deeper, you can read more on how to frame effective questions that lead to real results.
When most people hear about How Might We statements, they immediately think of product design or UX workshops. But their real power is that they can spark innovation in any part of your business. Think of them as a universal translator for problem-solving, creating a shared language that everyone from the factory floor to the C-suite can understand and use.
The beauty of HMWs lies in their flexibility. They empower any team, no matter their function, to take their unique, day-to-day challenges and reframe them as exciting opportunities for growth. It’s all about shifting the mindset from "we can't because…" to the more optimistic "how might we…?"
Operations managers live in a world of constant firefighting. They're always looking for ways to make things run smoother, faster, and cheaper. HMW statements are a perfect tool for this environment, turning messy operational hurdles into clear, focused questions that actually lead to improvements.
Instead of getting bogged down by a problem like, "Our machine downtime is killing the production schedule," an operations leader can flip the script. The focus immediately shifts to finding proactive solutions.
Here's how that might look in an operations setting:
These questions don't just wallow in the problem; they point toward a specific goal and naturally open the door to solutions like AI-powered predictive maintenance or smart inventory systems. For a deeper look at this, exploring AI for operational efficiency with smart workflows is a great next step to see how these ideas become reality.
The table below shows just how adaptable the HMW framework is across different parts of a company.
| Business Department | Challenge | Sample How Might We Statement |
|---|---|---|
| Sales | Our sales cycle is too long, causing us to lose deals. | How might we shorten our sales cycle by 20% to close more deals faster? |
| Marketing | Our email campaigns have low open rates. | How might we personalize our email content to double engagement? |
| Finance | The monthly financial closing process is slow and prone to errors. | How might we automate our closing process to ensure 100% accuracy and cut the time by three days? |
| Customer Support | Customers are waiting too long for support responses. | How might we use an AI chatbot to resolve 50% of common customer queries instantly? |
As you can see, the core structure remains the same, but the focus shifts to solve the specific pains of each department, making it a truly versatile tool for any leader.
You might think that highly technical teams—like data scientists and AI engineers—don't need HMWs. After all, they live and breathe solutions. But HMWs play a crucial role here, too: they ensure that all that technical wizardry is aimed at solving the right business problems.
For these teams, an HMW statement acts as a bridge connecting a cool technical possibility to a real business need. It helps them prioritize projects and can even spark technical breakthroughs by framing the challenge in a more open-ended, creative way.
HMWs ensure that technical projects are not just impressive feats of engineering but are directly tied to creating tangible business value, like increasing revenue, cutting costs, or mitigating risk.
Check out these HMWs tailored for a data science team:
This approach keeps technical exploration focused and purposeful. And if you're curious about how AI can help protect your business, our article on how it can turn business risks into opportunities is a must-read.
Innovation isn't just about tech and processes; it's about people. Leaders in HR, training, and people operations can use HMWs to tackle complex challenges around employee engagement, skill gaps, and company culture.
This is especially true as more companies bring AI into their daily work. A huge hurdle is getting non-technical teams comfortable with these new tools. HMWs provide a human-centered way to brainstorm solutions that actually work for people.
When you encourage every department to use HMW statements, you build a consistent culture of innovation. People learn to see challenges not as frustrating roadblocks, but as the starting line for the next great idea.
Let's be honest, the best how might we statements rarely pop into someone's head while they're working alone. They're usually forged in the creative fire of a great workshop, where different minds come together to solve a problem. Your job as a facilitator is to channel that energy and turn a chaotic wall of sticky notes into a clear path forward.
A good HMW workshop is so much more than another brainstorming meeting. It's a structured session designed to pull out diverse ideas, get people thinking outside the box, and get the whole team aligned and excited.
The real work for a killer workshop starts way before anyone even enters the room. Solid prep is the difference between a session that lands with a thud and one that sparks real breakthroughs. If you skip this part, you’re basically asking for a chaotic meeting that wanders aimlessly.
First thing's first: define the scope. What are you actually trying to solve? Is it a nagging customer complaint? A clunky internal process that’s slowing everyone down? Or are you aiming for a big, blue-sky product idea? You need to be laser-focused. Start the workshop by clearly stating the core challenge or Point of View (POV) statement to get everyone's creative juices flowing in the right direction.
Next, get your hands on any relevant insights and share them beforehand. This could be anything from:
Send this info out a day or two early. It gives your team time to let the problem simmer, which almost always leads to better, more thoughtful ideas during the workshop itself. It’s a tiny step that pays huge dividends.
Okay, you've done your homework. Now it's time to run the actual session. As the facilitator, your main job is to create a space that feels safe and structured, where every single idea is welcomed and every person feels heard. The name of the game is quantity over quality at first—you want a flood of ideas before you start whittling them down.
A fantastic way to make sure everyone contributes is silent brainstorming. Instead of a verbal free-for-all where the loudest person wins, give everyone 10-15 minutes to quietly write their HMWs on sticky notes. This simple trick is a game-changer. It gives introverts and deep thinkers the space they need to contribute their best stuff without being talked over.
After the silent brainstorm, go around the room and have each person share their HMWs out loud as they stick them on a wall or whiteboard. This part is all about generating possibilities, so shut down any discussion or criticism. Just get the ideas up there for everyone to see.
Once the wall is covered in a rainbow of sticky notes, it's time to make sense of the beautiful mess you've created.
A wall full of ideas is a great start, but it’s not an action plan. This final phase is where you guide the team from a sea of possibilities to a handful of concrete priorities.
Start by clustering similar HMWs. As a group, start moving the sticky notes around, grouping them by theme. You’ll be surprised how quickly patterns emerge. Give each cluster a simple name that captures its essence, like "Automating Manual Tasks" or "Improving Customer Communication." This helps everyone digest the sheer volume of ideas.
With your ideas neatly clustered, it's time to pick the winners. A simple, democratic, and incredibly effective method for this is dot voting. Give every participant three to five sticky dots (or just let them draw dots with a marker). Ask them to place their votes on the HMW statements they think hold the most promise. You'll instantly see which ideas have the most buy-in from the group.
What’s the end result? You walk out of that room with two to three top-voted HMW statements. These aren't just random suggestions; they're collaboratively built and prioritized opportunities that your team is genuinely pumped to start working on.
While how might we statements are an incredible tool for sparking new ideas, a few common traps can easily stop your momentum cold. Think of this as your field guide for spotting these pitfalls early and steering your team back onto a productive path. Getting this right is what separates a feel-good brainstorming session from one that actually drives real innovation.
The most common mistake is making your HMW statement way too broad. A question like, "How might we increase profits?" feels important, sure, but it’s so huge it can leave your team completely paralyzed. It's like a tour guide telling you to "go explore North America" without a map—where do you even start? You'll probably end up going nowhere.
When the scope is too wide, you get a ton of vague, disconnected ideas that are almost impossible to act on. The fix? Add more context to narrow the focus. Instead of just "increase profits," reframe it around a specific pain point: "How might we reduce our operational costs by 15% in the next quarter?" Suddenly, your team has a clear, measurable target to aim for.
On the other hand, being too narrow is just as bad. An HMW statement that’s overly specific basically sneaks a solution right into the question, killing creativity before it even starts. For example, asking, "How might we add a blue button to the checkout page?" leaves zero room for any other ideas that might be better.
This kind of question assumes a solution without ever really digging into the problem. Maybe a button isn't the answer. Maybe the entire checkout flow needs a rethink.
An HMW statement should feel like an open door, not a narrow hallway. It should inspire a wide range of ideas, not funnel everyone toward a single, predetermined outcome. Your goal is to define the problem space, not the solution.
To avoid this trap, always bring it back to the core user need or business problem. Instead of the "blue button" question, a much better HMW would be: "How might we make the checkout process feel faster and more intuitive for our customers?" This simple tweak opens the door to countless possibilities.
This one is sneaky. Your team is full of smart problem-solvers, so it's only natural for them to want to find the answer right away. Someone will throw out a great HMW, and within seconds, someone else chimes in, "Oh! We could build an app for that!"
When this happens, you have to gently guide the conversation back to the HMW framework. Remind everyone that the goal right now isn't to find the one right answer, but to explore as many different questions and angles as we can. Jumping to a solution too early shuts down the divergent thinking that is so crucial to this process.
Before your organization plows ahead with big changes, you need to know if your team is actually ready for them. A great way to do this is by conducting a change readiness assessment to see how new initiatives will land.
Here’s a quick-and-dirty checklist of red flags to look for in your HMWs:
By keeping an eye out for these common missteps, you can ensure your how might we statements stay sharp, focused, and powerful enough to guide your team toward some truly creative breakthroughs.
Even after you get the hang of the basics, a few common questions tend to trip teams up when they first start using how might we statements. Let's tackle those head-on so you can clear those final hurdles and start brainstorming with confidence.
It's super common to get these two mixed up, but they play very different roles. Think of a problem statement (sometimes called a Point of View or POV) as your anchor. It defines a specific challenge you've uncovered. For example: "Busy professionals need a way to track expenses because they often lose receipts." It nails down the who, what, and why of the issue.
A How Might We statement takes that exact problem and flips it into a springboard for ideas. Using our example, the HMW becomes: "How might we help busy professionals track expenses effortlessly?" The problem statement gives you a solid foundation; the HMW statement is what launches you into creative problem-solving.
There’s no magic number, but when you're just starting out, the mantra is always quantity over quality. Seriously, don't get hung up on crafting the "perfect" question right away. A good, energetic workshop can easily churn out anywhere from 20 to over 100 HMWs from a single problem.
The whole point is to explore every possible angle you can think of—this is called divergent thinking. Once you have a massive list of questions, your team can switch gears. You'll start grouping similar ideas together and then vote on the top 2-3 HMWs that feel most promising. You have to go wide before you can narrow in on the best paths forward.
Think of it like this: The problem statement is your starting point on a map. The HMWs are all the potential paths you could take. The final, prioritized HMWs are the specific routes you’ll explore on your journey to a solution.
Absolutely! HMWs are fantastic for internal innovation, not just for customer-facing products. This makes them an incredibly valuable tool for any AI and data consulting business looking to improve how their clients operate.
Let’s say your team is getting bogged down by slow, manual reporting. You could frame it with questions like, "How might we automate our weekly sales report generation?" or "How might we make key business metrics accessible to everyone in real-time?" It’s a perfect approach for operations managers, HR leaders, and IT teams who want to make their internal workflows a whole lot smarter and more efficient.
Ready to turn your own business challenges into growth opportunities? At NILG.AI, we specialize in creating tailored AI solutions that drive efficiency and success. From strategic roadmaps to process automation, we provide a clear path to transform your operations. Discover how we can help you Request a proposal
Like this story?
Special offers, latest news and quality content in your inbox.
Mar 18, 2026 in Guide: Explainer
Discover how AI for customer service can transform your support operations. Learn practical strategies to reduce costs, improve satisfaction, and drive growth.
Mar 15, 2026 in Guide: Explainer
Discover how might we statements transform complex challenges into real opportunities. Learn practical crafting tips, workshops, and real-world examples.
Mar 1, 2026 in Guide: Explainer
Unsure what is conversational ai? This guide explains everything from core concepts to real-world business applications, benefits, and implementation roadmaps.
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |