Why CEOs Should Get Their Hands Dirty With Hackathons

There's one type of hackathon I really like to organise. At BeMyApp we call it the "Top 200" hackathon. Upper management from a large company comes together from around the world to develop a digital solution and, in doing so, gain a digital mindset.

This format brings senior leaders together in a setting where they can collaborate, align on priorities, and gain a closer understanding of digital work.

When they meet in one place, the company board often defines the new objectives for the year, ensuring everyone is aligned, and employees across the globe finally get to meet.

The event combines strategic alignment among top management, sharing best practices, and team building. But before we get into how it works, it's worth looking at who's actually in the room.

Who Participates in a “Top 200” Hackathon?

Within each company, you have the top managers, often referred to as the "top 200" (or top 50, top 100, depending on the size of the business). This group represents the senior decision-makers who set direction across the organization. These typically include:

• The CEO
• Communication executives
• Sales directors for each country
• The CTO
• The CFO
• The VPs

Executives in larger companies usually convene only once or twice a year.

How Does the Hackathon Work?

Here’s a basic rundown of a three-day event involving senior management, developers, and designers:

Day 1: Form Teams & Develop Ideas

Let’s say you have 200 people. On the first day, separate everyone into 15 teams. To each team, add one external developer and one designer. This is what makes the concepts and projects particularly interesting, because you have the VP or top managers suddenly working alongside an external developer.

The concept of a hackathon is explained, all the while highlighting the benefits of fast innovation. As they do so, the teams begin to form an idea for their project and start working on it.

To break up the work, they will often separate for an activity while the developers and designers continue working on the project.

Day 2: Develop and Refine the Project

With the initial ideas established on Day 1, teams continue developing their projects on Day 2. The external developers and designers continue working alongside the senior leaders, helping turn the teams’ ideas into a more developed project.

Day 3: Finalize the Pitch and Final Demo

By Day 3, also known as the final demo day, teams have three more hours to work on their pitch and finalize their presentation. This gives them time to bring together the work completed during the hackathon and prepare how they will present their project.

Why Hands-On Participation Matters for Executives

One of the benefits of this format is seeing the CEO of a billion-dollar company working alongside a designer, deliberating over the details of a banner. Executives are not necessarily accustomed to being involved in this type of hands-on work.

Seeing the Work at Every Level

These decisions are happening every day within their company, yet executives are not always exposed to them. Going behind the curtain to see what’s really going on is hugely beneficial to a company head. They suddenly see what’s involved at every level, at the “factory” level.

At La Poste, for example, I was told that every winter, in the week leading up to Christmas, the boss takes to personally delivering boxes to the public.

Get Your CEO Playing With Pixels Alongside a Young-Gun Designer

Managers need to understand the reality of where they work, at every level. Because we’re living in a digital world, designers, developers, and community managers are the modern-day “factory.”

If you take the principle that every company must have digital embedded in its DNA to become a digital company, you have to consider these employees highly valuable. That is why it’s good to have the top 200 participate in a hackathon and stay attuned to what’s happening at every level.

Experience the Digital World Firsthand

Put the CEO of a company, or some other high-positioned employee, in the environment of a hackathon. For the first time in their career, they’re making decisions about colours and banners or working with a prototyping tool.

Very quickly, they'll understand the digital world. They will be inspired to take these new learnings and mindset home. When they return, they’ll have the confidence to want to solve problems digitally. They’ve learned what’s possible.

Turning New Insights Into Action

A lot of managers might say, “We don’t launch new disruptive digital services because the gap is too wide between where we are and what we want to do. And we won’t make cash with it.”

However, after a hackathon, their tune changes to, “When can we do something? I want to do something.”

They might choose to go ahead with the project developed at the hackathon or start something else entirely. What kinds of projects might result from a hackathon? Apps, mostly.

But remember, the main objective isn't necessarily to launch new products, but to change the company mindset and inspire people to think digitally.

Interested in Running a Hackathon?

If you're considering hosting a hackathon, we can help you explore the right approach. You can also browse upcoming hackathon events to see what's happening around the world.

Have questions about how a hackathon works or what it involves? Get in touch with us to learn more. 

Contact Us →