Importance of Idea Generation in Software Development

Sometimes adopting a best practice for your organization means adopting the philosophy behind it, but not the practice itself. That’s how I view Google’s 20% time practice and its application at RightHand Robotics, Inc. For me, the goal behind 20% time was creating space for good ideas to surface. It’s based on the belief that good ideas come from anywhere and anyone. It gives people the latitude to be able develop their ideas, even if they have nothing to do with their assigned role. That concept has been a core philosophy I’ve brought with me to RightHand Robotics, Inc. But our approach is less about time allocation and more about making sure there are open channels for generating and developing great ideas. There are a few different ways we do that. We’re a Slack-heavy culture, which means we have many different channels for surfacing and documenting new ideas or observations. We also keep a “wish list” of ideas. These are ideas we think may be worth pursuing, but perhaps it’s not the right time yet. They could be marketing ideas, product ideas, engineering ideas, or even process improvement ideas - which we think are great, but which we can’t pursue at the time they arise. Keeping these repositories allows us to track and continually revisit good ideas, so that we’re more likely to unearth the right idea at the right time. Google taught me that it’s important for an organization to leave room for idea generation. But the methodology matters less than the principle itself. Regardless of your approach, empowering every member of your team to be an idea generator will leave the door open for innovation.

Ideation generates significant value in design. Yet businesses frequently hesitate to invest time, money, and personnel in this phase, often overlooking it as it falls between the strategic planning and development stages for many companies. In the double-diamond process, while many teams include it in the development phase, most do not continue refining their ideas from the problem-solving stage. Instead, they jump directly into coding, which is often the least adaptable testing method for validating the effectiveness of their design. Here's why teams run into ideation roadblocks: → Quantifying the value of creative ideas is difficult → There is no assigned team to iterate on ideas → Tracking time and resources in ideation is hard → Ideation's long-term value complicates cost analysis → Lack of metrics makes it hard to judge costs → Balancing idea quantity and quality is challenging → Cultural views may misjudge ideation costs Design teams should emphasize that generating ideas can be cost-effective and valuable. Providing measurable results makes their argument stronger and encourages collaboration among different groups. We built Helio for this purpose. I've seen a single checkbox lead to millions of dollars in lost revenue. The issue wasn't that it was coded incorrectly or a bug. Rather, it was because the development process overlooked the user's needs, failing to recognize why the checkbox was necessary in the first place. What's your experience? #productdesign #productdiscovery #innovation #uxresearch

Did We Forget About Creativity in Software Engineering? The most memorable breakthroughs I’ve seen didn’t come from a perfect process. They came from moments when someone felt safe enough to suggest an idea that sounded risky, odd, or incomplete and we decided to explore it anyway. Yet under the pressure to deliver and optimize, creativity can easily be overlooked. Exploring possibilities together sparks new ideas and strengthens the bond between team members. All Ideas Matter Everyone should feel free to contribute during brainstorming. Early ideas don't need to be perfect or practical. In the first stage of thinking, it's more important to explore than to evaluate. Give each contribution the same attention and respond with curiosity instead of criticism. That's how confidence grows and ideas evolve. Diversity Adds Spark The best insights come from the least expected viewpoints. Each of us approaches problems through a unique lens shaped by our background, experiences, and skills. Diverse teams avoid the comfort of agreement and create richer conversations leading to results no single person could design alone. Experimentation Keeps Us Moving Innovation depends on trying new things. When teams understand the boundaries of acceptable risk, they can take bold but thoughtful steps. A small experiment can reveal more than a long debate. Even when something fails, it brings new awareness to what might work next. Creativity isn't a luxury. It's what turns technical skill into meaningful progress. Once ideas are on the table, convergent thinking helps refine them until what remains is practical, valuable, and ready to grow. When we make room for experimentation and reflection alongside delivery, we rediscover not only new ways to build software but also new ways to grow as professionals.