Ever marvel why your groups wrestle to innovate past their roadmap? They’re seemingly too busy preserving the lights on to step again and rethink what’s attainable.
I get it — I’ve spent 20 years in software program, continuously balancing the pull of delivering identified outcomes towards the necessity to discover what’s subsequent. It’s a tricky tradeoff, however one I’ve wrestled with lengthy sufficient to know this: in case you don’t create area for innovation, it received’t occur.
At G2, we’ve advanced our strategy over time, beginning with one thing easy — giving folks the respiration room to deal with concepts they wished that they had time for. That small shift grew into one thing a lot larger: a two-week hackathon experiment that has repeatedly advanced.
On this article, I’ll stroll you thru that journey — not as a prescriptive playbook, however as an invite to experiment in your individual method. As a result of innovation isn’t about having the right technique — it’s about making area for what’s attainable.
G2’s journey to innovation: chore week to hackathons
Each experiment begins with a speculation. However in software program supply, there’s one other vital issue: the urge for food for that experiment. How a lot time are we keen to spend money on exploring the unknown?
The reply to that’s normally dictated by the corporate’s stage and tradition. Some organizations have by no means seen innovation performed properly, making the thought of groups spending every week or extra in unstructured work a tough no.
And truthfully, I get it. Betting on an undefined final result can really feel dangerous. However does that imply innovation is out of attain? By no means. Begin smaller. Are you able to carve out a day? A day? Show the worth in increments, and over time, that urge for food will develop.
At G2, I used to be lucky to work with founders who already noticed the worth of innovation, which meant we began with a bigger urge for food. However that didn’t imply we all the time obtained it proper. Our journey, from chore week to the ultimate hackathon, has been stuffed with classes, iterations, and sudden turns, every shaping how we foster innovation immediately.
Chore week: the respiration pause
Within the early days, our strategy to innovation wasn’t about constructing the following huge factor — it was about catching our breath. Our groups had been pushing arduous to ship options, however in that relentless drive, we weren’t all the time leaving the codebase in a state that inspired long-term innovation. So, we carved out time to return, refactor, and clear up patterns: a chore week. We principally applied a reset button for the code.
Nonetheless, this effort revealed that one of many greatest obstacles to innovation isn’t only a lack of time — it’s the technical debt that makes future innovation more durable. If you transfer quick however don’t repeatedly form the code into one thing maintainable and extensible, you create friction for each future concept.
Whereas this strategy helped us enhance our code high quality, it didn’t spark a lot inspiration. Nothing groundbreaking got here out of it, simply small quality-of-life enhancements that made improvement somewhat simpler. In some methods, it even despatched the incorrect message: it was okay to ship subpar code so long as we had a “chore week” to scrub it up later. It was a crucial first step, however we shortly realized that if we wished to push actual innovation ahead, we wanted a distinct strategy. Dev week was created to fill that position.
Dev week: the innovation summit
As G2 grew, so did the necessity for alignment. Scaling an organization introduces extra processes, and whereas construction is critical, it will probably additionally mess with the artistic vitality that drives actual innovation. We began listening to a constant theme from our groups: they wished area to discover concepts outdoors the roadmap.
On the identical time, we didn’t wish to absolutely abandon the advantages of our authentic “chore week” mentality — some engineers nonetheless valued time to enhance the codebase. So, we advanced.
The end result was what we first known as “Dev Week”, which ultimately turned the “Innovation Summit.” It was an unstructured, two-week occasion the place self-selected groups may discover new concepts, experiment with rising applied sciences, and construct one thing actual.
On the finish of the 2 weeks, groups showcased their work, and immediately, we noticed wins. One of many greatest early successes? An integration that introduced G2 actions instantly into Slack. This was one thing that wasn’t on the roadmap however delivered instant worth.
However whereas this strategy unlocked creativity, it had its personal challenges. Many nice concepts by no means noticed the sunshine of day. Even once we beloved what groups constructed, we struggled to shut the loop and produce these improvements into manufacturing. As quickly because the Innovation Summit ended, we went again to “common” work, and lots of initiatives merely light into the background.
The inspiration was there. The educational was there. However we weren’t realizing the complete affect of those improvements. We would have liked to discover a solution to bridge the hole between artistic exploration and actual, lasting outcomes. That’s once we launched hackathons to carry these concepts to life.
Hackathons: bridging innovation and affect
As vitality and urge for food for innovation grew, so did our ambition. We had seen the spark that unstructured exploration may generate, however we wished to take it a step additional — to not solely encourage our groups but in addition drive actual enterprise affect. This led us to our subsequent evolution: the G2 hackathon.
Hackathons aren’t new; the tech trade has lengthy used them to drive breakthrough concepts. Nonetheless, at G2, we wished to refine the components to reconcile open-ended creativity with a deal with outcomes. The important thing shift? C-level buy-in. We introduced our executives in as judges, making certain alignment between the boldest concepts and the outcomes that may drive the enterprise ahead. We discovered main success in the best way we selected to run our hackathons, and as all the time, sharing is caring.
How G2 runs a hackathon
At G2, our hackathons are designed to strike the right steadiness between artistic freedom and enterprise affect. Right here’s how we construction them to maximise each engagement and outcomes:
A transparent however open-ended theme
Every hackathon kicks off with a guiding theme — broad sufficient to spark creativity however centered sufficient to drive significant outcomes. For instance, our “Encourage Buyer Love” theme inspired groups to discover methods to boost the shopper expertise whereas preserving the end result aligned with enterprise targets.
Group formation with goal
As soon as we collect individuals, each in-person and distant, we deal with forming groups that blend views and expertise ranges. This isn’t nearly getting folks collectively; it’s about fostering new collaborations and making certain every crew has the suitable mix of abilities to carry an concept to life.
Quick-paced ideation and execution
Because the hackathon begins, groups shortly register their concepts to decide to a course. From there, they’ve two weeks to experiment, construct, and refine their ideas. The aim isn’t simply to brainstorm; it’s to ship one thing tangible by the tip.
Govt-level judging of actual affect
On the finish of the hackathon, groups current their initiatives to a panel of cross-functional executives. The profitable concepts aren’t nearly technical ingenuity; they’re judged closely on how confidently they will affect enterprise targets.
Recognition, rewards, and subsequent steps
The highest three groups win financial prizes and ongoing help to show their concepts into actuality. Nevertheless it doesn’t cease there. We amplify their work throughout the corporate and on social media, making it clear that these improvements matter and have the potential to form the way forward for G2.
This construction ensures that hackathons aren’t simply enjoyable facet initiatives however a core driver of innovation at G2. By combining inspiration, execution, and recognition, we make area for groundbreaking concepts to take root and thrive.
The actual affect of hackathons
This strategy labored. By hanging the suitable steadiness between pleasure and focus, we began seeing actual, tangible product enhancements emerge from our hackathons.
A few of the greatest successes embrace:
- Nudges in my.G2: This helps clients shortly floor what’s most necessary and streamline evaluate assortment.
- G2 built-in affect: Seeing the affect of G2’s knowledge in a advertising and gross sales movement turned a actuality by means of getting the complete circle view from some companion integrations.
- AI-powered automation: AI-powered automation, equivalent to producing touchdown pages and AI-assisted evaluate responses, have grow to be central to our product expertise.
However, as all the time, there have been challenges. Not each nice concept made it to clients. Competing priorities meant that some extremely promising initiatives stalled out, and we needed to rethink the way to maintain momentum past the hackathon. We additionally realized that whereas structured themes helped align innovation with enterprise targets, they generally constrained the type of far-out, moonshot concepts that would redefine our future.
To steadiness this, we cut up time between the hackathon and Innovation Summit. Hackathons stay centered on delivering tangible outcomes, whereas Innovation Summit offers area for open-ended exploration.
And that’s the place we’re immediately — a continuously evolving tradition of innovation. We now know that actual affect doesn’t come from a single occasion or course of however from regularly making area for daring considering. And as we transfer ahead, we’ll continue to learn, iterating, and discovering new methods to push the boundaries of what’s attainable.
Life hack
G2’s journey exhibits that innovation isn’t a one-time initiative; it’s a mindset. It requires fixed experimentation, not simply in devoted occasions however in how groups strategy their work every single day. We’ve seen this shift firsthand, with groups naturally carving out moments of innovation inside their common cycles. The result’s extra engaged groups and a extra sustainable path to persistently high-impact outcomes.
Undecided the place to begin with launching your individual hackathon? Begin the place you may. Determine the funding you’ve got management over and launch an innovation occasion — irrespective of how small. Give groups the liberty to discover, however set a transparent aim for measuring affect. Have fun the wins to construct momentum and develop that funding over time. And most significantly, by no means cease experimenting.
Able to dive into extra G2 tech information? Be taught extra about The Grand Delusion and why cybersecurity retains failing.
Edited by Supanna Das