Brainstorming Techniques That Actually Generate Ideas
Five structured methods for getting past the blank page. We’ll show you how to run brainstorming sessions that produce real, usable ideas instead of generic suggestions.
Read MoreBreaking down the five-stage design thinking process. This is how companies approach innovation problems — and you can use it too.
Design thinking isn’t just for designers anymore. It’s a practical problem-solving approach that companies like Apple, Google, and countless startups use to tackle complex challenges. The framework shifts focus from just finding quick solutions to really understanding what people need.
You’ll find it’s particularly useful when you’re stuck. When traditional brainstorming isn’t working and you need a structured way forward, design thinking provides that roadmap. It’s been refined over decades by IDEO, Stanford’s d.school, and innovation teams worldwide.
Design thinking follows a deliberate sequence. Each stage builds on the previous one, and you’ll often loop back — that’s completely normal and actually encouraged.
Start by understanding the people you’re solving for. Not what you think they need — what they actually experience. You’ll conduct interviews, observe behavior, and listen for the unstated problems.
Synthesize what you’ve learned into a clear problem statement. This isn’t the obvious surface problem — it’s the root issue. You’re reframing the challenge in a way that opens up new solution possibilities.
Generate ideas without judgment. Quantity matters here. You’re looking for volume and variety, not polish. Sketching, wild brainstorming, and building on others’ ideas all happen in this stage.
Build something tangible. It doesn’t need to be perfect — rough and testable is better. A prototype might be a sketch, a role-play scenario, a cardboard mockup, or a simple digital version.
Put your prototype in front of real people. Gather feedback, observe how they interact, and learn what works and what doesn’t. This often sends you back to earlier stages — and that’s the point.
The empathy phase is where most teams get this wrong. They skip straight to solving without really understanding. But here’s what actually works: you spend time with the people you’re designing for.
Listen for what people don’t say. Watch what they struggle with. Ask “why” multiple times. You’re building mental models of their world, not collecting feature requests.
Real empathy changes everything. When you understand that a busy parent’s frustration isn’t about the product itself but about saving 10 minutes in their morning routine, you’ve found the actual problem. When you discover that your target user actually avoids using certain tools because of past negative experiences, you know what barriers you’re up against.
This stage typically takes 2-4 weeks for most projects. You’ll run interviews, create empathy maps, and build personas. Don’t rush it — the better your empathy work, the stronger your entire solution becomes.
The define phase is where design thinking really differs from standard problem-solving. You’re not just clarifying the problem — you’re reframing it entirely.
Example: A coffee shop thinks their problem is “customers want faster service.” But after empathy work, they discover the real issue is “customers feel invisible during their wait.” The solution shifts from speed to acknowledgment.
This reframing opens completely different solution paths. Instead of adding espresso machines, they train baristas to make eye contact and remember regulars’ names. Radically different, yet it addresses the actual problem.
You’ll create problem statements that follow this format: “How might we [action] so that [outcome]?” This phrasing keeps solutions open and acknowledges you’re exploring possibilities, not declaring absolute truths.
Here’s where design thinking becomes real and actionable. You’re moving from ideas to something you can actually test with users.
Sketches, paper mockups, and role-play scenarios. These are fast, cheap, and disposable. Perfect for exploring multiple directions quickly.
Digital wireframes, clickable prototypes, or functional mockups. You’re adding more detail while still staying flexible.
Polished versions that look almost final. These work best once you’ve validated the core concept through testing earlier prototypes.
Testing isn’t about proving you’re right. It’s about learning what you got wrong so you can improve. Most teams find that their first prototypes fail in predictable ways — and that’s exactly what you want to discover before investing heavily.
A single user testing session often generates more insights than three rounds of internal debates. You’ll see where people get confused, what they actually value, and what you completely missed.
Design thinking isn’t linear. You’ll loop back constantly. Testing reveals gaps. Those gaps send you back to ideate or even back to empathize. That’s not failure — that’s the process working exactly as designed.
Most successful solutions go through 3-5 iteration cycles minimum. Each loop, you’re getting closer to something that actually solves the problem.
Teams that resist this loop often end up with solutions nobody actually wants. They’ve optimized for what they think is the problem, not what the problem actually is. Design thinking forces you to stay honest about that distinction.
The beauty of this approach is it works at any scale. Whether you’re solving for a team of 5 or a market of 5 million, the framework keeps you grounded in actual user needs rather than assumptions.
You don’t need a massive budget or dedicated innovation team. Here’s how organizations of different sizes are actually using this:
Using rapid prototyping and constant testing to validate product-market fit. They’re often doing design thinking without even naming it — building, testing with users, learning, and pivoting.
Running structured design thinking workshops for innovation initiatives. It’s becoming standard practice in digital transformation and customer experience redesigns.
Using design thinking to solve social problems with limited resources. The empathy-first approach often reveals solutions that don’t require expensive interventions.
Applying design thinking to improve citizen services and policy implementation. It’s helping agencies understand what people actually need versus what bureaucracies assume they need.
Design thinking isn’t complicated, but it does require discipline. You won’t get results if you skip the empathy work or jump straight to solutions. The framework works precisely because it respects the problem-solving process.
Start with a real problem your organization or team is facing. Pick one challenge and commit to running through all five stages. You’ll be surprised how different your final solution looks compared to where you started. That’s not a failure of your initial thinking — that’s the framework working exactly as intended.
The organizations getting the best results aren’t the ones with the most money or the smartest people. They’re the ones that actually listen to their users and stay willing to be wrong. Design thinking gives you a structured way to do exactly that.
This article presents the design thinking framework as an educational resource for understanding innovation and problem-solving methodologies. While design thinking has been successfully applied across many industries and organizations, results and implementation will vary based on your specific context, team capability, and organizational readiness. Design thinking is a tool — its effectiveness depends on thoughtful application, genuine user engagement, and organizational commitment to the iterative process. This content is informational in nature and should be adapted to your unique circumstances. Every organization and problem is different, so consider consulting with experienced facilitators or innovation practitioners when implementing these frameworks in your environment.