choong pw

Looking back at my own journey in tech, from hackathons fueled by caffeine and sheer determination to leading teams pushing the boundaries of what’s possible, one thing has become crystal clear: innovation isn’t just about having great ideas; it’s about creating an environment where those ideas can flourish.

So, how do we build a culture of innovation? Let’s dive into eight key principles that I’ve found to be impactful, drawing from established management theories and real-world experiences.

Psychological Safety

Remember that time you had a brilliant idea in a meeting but hesitated to share it, fearing it might sound silly? We’ve all been there. Psychological safety is about creating a space where everyone feels comfortable taking interpersonal risks –  such as speaking up with ideas, questions, concerns, or mistakes. It’s about knowing you won’t be penalized for speaking up, even if your idea isn’t fully baked. Without this foundation, groundbreaking ideas remain hidden.

What this translate to? Leaders needs to lead by example, like able to be vulnerable, admit to mistakes, and valuing diverse opinions. This fosters open communication channels, foster constructive feedback, and, importantly, celebrate “intelligent failures” as learning opportunities.

Embrace Experimentation and Learning from Failure

In the world of software engineering, we often talk about “failing fast.” It’s a core tenet of Agile and Lean methodologies. Is an iterative process; you’re going to stumble. The key is to learn from those stumbles.

People who have worked with me know how open I am to experimenting with new processes and ideas. I never let personal opinion get in the way. Either we gain from getting better at it or we know what doesn’t work. I believe everyone fears rejection (including myself). If there is psychological safety, there is no reason not to experiment. That is technically how most innovation comes about.

One more thing. There are many times when we gave a shot at an experiment, and it sort of ended as a failure. The idea didn’t manage to see the light at the end of the tunnel, and that’s okay too. Make sure to get the team together for a post-mortem to document and share the learnings.

Foster Cross-Functional Collaboration

Ever notice how the most innovative solutions often arise when different disciplines collide? Siloed departments limit the flow of ideas. Drawing from concepts like “Team Topologies” and “Spotify Chapter Models”, it’s essential to break down those walls and foster collaboration. Diverse teams bring varied experiences and problem-solving approaches.

My role requires me to participate in many cross-functional calls. The visibility and exposure that I have gained from it are huge, and I strongly encourage it when you have the resources to do so. Probably this is why I always have some ideas for my hackathon projects.

Empower and Encourage Autonomy

Innovation often bubbles up from the ground level. Employees closest to day-to-day operations often have invaluable insights. Empowering them and giving them autonomy unlocks that potential. Even many of the popular management book such as “High Output Management” and “The Manager’s Path” emphasis a lot about delegation and distributed leadership.

As a leader/manager, we should learn to invest in 1-on-1 as this is a place for coaching and mentoring. Is also a place where both parties can be vulnerable without fear of being judged by others. Use the chance to provide feedback and inspire.

Resource Allocation for Innovation

Ideas are cheap; execution is everything. And execution requires resources (time to build). A culture of innovation also means putting its money where its mouth is. Allocating dedicated resources to support innovation activities. Assumed positive intention, I believe everyone wants to deliver value for the company. That said, if is personal after working hours, it should never be forced.

Another part of the resource is technical resources – such as lab tools and experts. Which usually is the more trivial stuff on the management eye.

Articulate a Clear Vision and Strategy

While bottom-up innovation is crucial, it needs direction. A clear vision and strategy, aligned with the organization’s goals, provide that focus.

Vision and strategy that is too narrow limits the creativity; while being too broad just makes its implementation too fragmented, and we won’t be getting anything good out of it. I have been at both ends of the straw, and it is really hard to find the willpower and motivation to innovate. We need to see progress every day, even the tiny one counts.

I have an exception for this though. As a product gets more depths (mature), even when the tiny details can impact a lot, that’s where I see being narrow makes some sense because of the specific experience we want it to achieve.

Recognize and Reward Innovative

The one thing I like about participating in hackathon is the reward. Being at a cheaper currency country, the risk/reward of some hackaton can be astounishing. It also serve as the driver to keep pushing for success.

Flipping back onto the organization scene. I do see having a formal and informal reward program is essential. Some of the big company that I got to know from my friends rewards them handsomely for each patent that they submit. Making it a win-win for the company and the employee. Alternatively, a less grand scheme would be to encourage peer recognition and share success stories widely.

Leadership as Champions

Lastly, I think culture change should start at the top. Leaders to champion innovation by creating the conditions for it to thrive. When leaders are visibly committed to innovation, it sends a powerful message throughout the organization. Their actions and behaviors do set the tone, as I personally had witnessed the glory of the shift of focusing on something else.

Like it or not, they are the key to providing sponsorship and support.

Takeaway

Building a culture of innovation isn’t a one-time project; it’s an ongoing journey. It requires commitment, intentionality, and a willingness to embrace failure. But the rewards – continuous improvement, adaptability, and long-term success – are well worth the effort.

PS** This article is crafted by the AI automation I am experimenting with – will share more details later. Nevertheless, this article has been reviewed and revised by me to maintain its authenticity.