Techniques For Encouraging Experimentation At Work

I am constantly thinking about how to foster innovation in my product organization. Building teams that are experts at execution is the easy part—when there’s a clear problem, product orgs are great at coming up with smart solutions. But it’s impossible to optimize your way into innovation. You can’t only rely on incremental improvement to keep growing. You need to come up with new problem spaces, rather than just finding better solutions to the same old problems. So, how do we come up with those new spaces? Here are a few things I’m trying at Duolingo: 1. Innovation needs a high-energy environment, and a slow process will kill a great idea. So I always ask myself: Can we remove some of the organizational barriers here? Do managers from seven different teams really need to say yes on every project? Seeking consensus across the company—rather than just keeping everyone informed—can be a major deterrent to innovation. 2. Similarly, beware of defaulting to “following up.” If product meetings are on a weekly cadence, every time you do this, you are allocating seven days to a task that might only need two. We try to avoid this and promote a sense of urgency, which is essential for innovative ideas to turn into successes. 3. Figure out the right incentive. Most product orgs reward team members whose ideas have measurable business impact, which works in most contexts. But once you’ve found product-market fit, it is often easiest to generate impact through smaller wins. So, naturally, if your org tends to only reward impact, you have effectively incentivized constant optimization of existing features instead of innovation. In the short term things will look great, but over time your product becomes stale. I try to show my teams that we value and reward bigger ideas. If someone sticks their neck out on a new concept, we should highlight that—even if it didn’t pan out. Big swings should be celebrated, even if we didn’t win, because there are valuable learnings there. 4. Look for innovative thinkers with a history of zero-to-one feature work. There are lots of amazing product managers out there, but not many focus on new problem domains. If a PM has created something new from scratch and done it well, that’s a good sign. An even better sign: if they show excitement about and gravitate toward that kind of work. If that sounds like you—if you’re a product manager who wants to think big picture and try out big ideas in a fast-paced environment with a stellar mission—we want you on our team. We’re hiring a Director of Product Management: https://lnkd.in/dQnWqmDZ #productthoughts #innovation #productmanagement #zerotoone

In a world where most leaders focus on individual performance, collective psychological context determines what's truly possible. According to Deloitte's 2024 study, organizations with psychologically safe environments see 41% higher innovation and 38% better talent retention. Here are three ways you can leverage psychological safety for extraordinary team results: 👉 Create "failure celebration" rituals. Publicly acknowledging mistakes transforms the risk psychology of your entire team. Design structured processes that recognize learning from setbacks as a core organizational strength. 👉 Implement "idea equality" protocols. Separate concept evaluation from originator status to unleash true perspective diversity. Create discussion frameworks where every voice has equal weight, regardless of hierarchical position. 👉 Practice "curiosity responses”. Replace judgment with genuine inquiry when challenges arise. Build neural safety by responding with questions that explore understanding before concluding. Neuroscience confirms this approach works: psychologically safe environments trigger oxytocin release, enhancing trust, creativity, and collaborative problem-solving at a neurological level. Your team's exceptional performance isn't built on individual brilliance—it emerges from an environment where collective intelligence naturally flourishes. Coaching can help; let's chat. Follow Joshua Miller #workplace #performance #coachingtips

Most companies claim they embrace failure. But walk into their Monday meetings, and watch people scramble to hide their missteps. I've seen it countless times. The same leaders who preach 'fail fast' are the first to demand explanations for every setback. Here's the uncomfortable truth:  Innovation dies in environments where people feel safer playing it safe. But there's a difference between reckless failure and strategic experimentation. Let me show you exactly how to build a culture that genuinely embraces productive failure: 𝐂𝐡𝐚𝐧𝐠𝐞 𝐲𝐨𝐮𝐫 𝐩𝐨𝐬𝐭-𝐦𝐨𝐫𝐭𝐞𝐦 𝐦𝐞𝐞𝐭𝐢𝐧𝐠𝐬 Stop asking "Who's fault was this?" and start asking: "𝘞𝘩𝘢𝘵 𝘩𝘺𝘱𝘰𝘵𝘩𝘦𝘴𝘪𝘴 𝘸𝘦𝘳𝘦 𝘸𝘦 𝘵𝘦𝘴𝘵𝘪𝘯𝘨?" "𝘞𝘩𝘢𝘵 𝘴𝘱𝘦𝘤𝘪𝘧𝘪𝘤 𝘥𝘢𝘵𝘢 𝘥𝘪𝘥 𝘵𝘩𝘪𝘴 𝘧𝘢𝘪𝘭𝘶𝘳𝘦 𝘨𝘪𝘷𝘦 𝘶𝘴?" "𝘏𝘰𝘸 𝘤𝘢𝘯 𝘸𝘦 𝘶𝘴𝘦 𝘵𝘩𝘪𝘴 𝘪𝘯𝘧𝘰𝘳𝘮𝘢𝘵𝘪𝘰𝘯 𝘧𝘰𝘳 𝘰𝘶𝘳 𝘯𝘦𝘹𝘵 𝘪𝘵𝘦𝘳𝘢𝘵𝘪𝘰𝘯?" 𝐂𝐫𝐞𝐚𝐭𝐞 '𝐞𝐱𝐩𝐞𝐫𝐢𝐦𝐞𝐧𝐭 𝐬𝐡𝐨𝐰𝐜𝐚𝐬𝐞𝐬' Monthly meetings where teams present their failed experiments and the insights gained. The key? Leaders must go first. Share your own failures openly, specifically, and without sugar-coating. 𝐈𝐦𝐩𝐥𝐞𝐦𝐞𝐧𝐭 𝐭𝐡𝐞 "24-𝐡𝐨𝐮𝐫 𝐫𝐮𝐥𝐞" After any setback, give teams 24 hours to vent/process. Then require them to present three specific learnings and two potential next steps. This transforms failure from a dead end into a data point. Most "innovative" teams are just risk-averse businesses in disguise. They've mastered innovation theater, not actual innovation. Don't let your people think they need permission to innovate. Instead, start building systems and a culture that make innovation inevitable.

It isn't an experiment if it can't fail One of the warmup exercises I run for my workshops is to have people write down or draw what their biggest fear is with regards to running experiments in their organizations. Their responses often illustrate that far too few of us work in environments where it is safe to fail. "That we run out of patience with management" "It fails and my boss thinks I'm stupid" There is a big difference between Fail Safe and Safe to Fail in organizations. Fail Safe implies an organization that is designed to prevent failure and emphasize control. There are systems where this is applicable, often when both the problem and solution are known (and nothing changes). Safe to Fail on the other hand, acknowledges that a failure is inevitable and is designed to absorb these failures without significant impact. Here we identify and map the risk, then run experiments to address our riskiest assumptions. It is my belief that leaders are ultimately responsible for the environment of their organizations and I'm not convinced this fear of experimentation is intentional. There are several ways leaders can begin to create an environment of Safe to Fail inside their organizations:   👉 Promote an open dialogue where employees feel comfortable sharing ideas, asking questions, and expressing concerns without fear of retribution. 👉 Openly share stories of failures, lessons learned, and how these experiences contributed to growth. This helps demystify failure and frames it as a valuable learning opportunity. 👉 Recognize and reward not just successful outcomes but also the willingness to take calculated risks and experiment, even when the results are not as expected. 👉 Actively participate in experimentation, showcasing their commitment to a safe-to-fail environment. Leadership behavior sets the tone for the rest of the organization. 👉 Ensure that failures are met with constructive feedback rather than blame. This helps maintain morale and encourages ongoing risk-taking. 👉 Shift from traditional performance metrics that focus solely on success rates to metrics that value learning, experimentation volume, and adaptability. 👉 Share stories and data that highlight how experiments, even those that didn’t go as planned, contributed to the organization’s strategic goals. If you've made this shift in your organization, what has worked for you?

HOW TO CREATE SAFE SPACES FOR UNSAFE IDEAS You hire brilliant people and tell them to innovate. Then you make it impossible for them to do so. Most companies develop an immune system that rejects new ideas like they're some kind of virus. Here are the five innovation killers you need to spot and eliminate: KILLER #1: DEMANDING CRYSTAL BALL ACCURACY You want detailed business cases for projects that are inherently uncertain. The fix: Create different approval processes for exploration vs. execution. Exploration projects get smaller budgets and you measure success by what you learn, not what you earn. KILLER #2: BEING SCARED OF EVERYTHING Your processes are designed to avoid any downside risk, which also kills any upside potential. The fix: Separate "experiments you can't afford to mess up" from "experiments you can't afford not to try." Different projects, different comfort levels with risk. KILLER #3: MAKING INNOVATION FIGHT FOR SCRAPS Innovation projects have to compete with your proven money-makers for resources. The fix: Set aside dedicated innovation resources. 10% of engineering time, 5% of budget, just for projects where you don't know what'll happen. KILLER #4: JUDGING EVERYTHING ON QUARTERLY RESULTS You evaluate innovation projects on the same timelines as your day-to-day operations. The fix: Innovation gets measured by learning cycles, not calendar quarters. Success is about insights you gain, not deadlines you hit. KILLER #5: THINKING FAILURE MEANS SOMEONE SCREWED UP You define success as "execute the original plan perfectly." The fix: Success becomes "figure out what works as fast as possible." Changing direction gets celebrated, not punished. The framework that can transform your innovation culture: EXPLORE → EXPERIMENT → EXECUTE EXPLORE PHASE: Small budget, big questions. Win = quality insights. EXPERIMENT PHASE: Medium budget, specific hunches. Win = fast validation (or fast failure). EXECUTE PHASE: Full budget, proven concept. Win = flawless delivery. Different phases, different rules, different ways to win. Companies don't lack innovative ideas. They lack innovative environments. QUESTIONS TO DIAGNOSE YOUR INNOVATION IMMUNE SYSTEM: ❓How many good ideas die in approval meetings instead of real-world tests? ❓What percentage of your "failed" projects actually teach you something valuable? ❓How long does it take to get approval for a $10K experiment vs. a $10K efficiency upgrade? ❓Do your best people feel comfortable pitching risky ideas? If your best employee came to you tomorrow with a risky but potentially game-changing idea, would they feel safe pitching it? *** I’m Jennifer Kamara, founder of Kamara Life Design. Enjoy this? Repost to share with your network, and follow me for actionable strategies to design businesses and lives with meaning. Want to go from good to world-class? Join our community of subscribers today: https://lnkd.in/d6TT6fX5