I understand this struggle—having spent 20 years in software, I’ve often navigated the tension between delivering known outcomes and exploring new possibilities. It’s a challenging balance, but I’ve learned a crucial lesson: without creating space for innovation, it simply won’t occur.
At G2, we have gradually refined our approach, starting with a simple concept: granting teams the time to pursue ideas they previously felt they lacked time for. What began as a small initiative evolved into a bi-weekly hackathon experiment that has continually adapted.
This article will take you through our journey—not as a strict guide, but as an open invitation for you to try your own innovations. After all, true innovation isn’t about having the perfect plan; it’s about creating opportunities for new possibilities to emerge.
G2’s Innovation Path: From Chore Week to Hackathons
Every experiment begins with a hypothesis. In software delivery, however, another vital element is the willingness to invest time in exploring the unknown.
The willingness to experiment is typically influenced by a company’s stage and culture. Some organizations have little experience with successful innovation, making the idea of teams engaging in unstructured work for a week or more a difficult sell.
I completely understand this perspective. Committing to an uncertain outcome can feel risky. But does that mean innovation is unattainable? Absolutely not. Start smaller. Can you allocate a day? An afternoon? Validate the value in bits, and gradually, that readiness for innovation will expand.
Post Comment