How To Set Up A Hackathon

How to Run a Successful Corporate Hackathon

Corporate Hackathons provide a nifty way to inspire teams and promote creativity, collaboration, and innovative thinking. Read below a detailed guide on how to set a hackathon to best serve your strategy and goals.

If run properly, a serial of hackathons can establish a stream of valuable ideas. It can also accept a significant cultural effect on your team, potentially awakening an experimentation and innovation mindset

This article explains unlike types of hackathons. It presents how to ready the objectives, success criteria, and other important aspects of your hackathon.

According to Wikipedia,a hackathon is defined as " …a design sprint-like event in which computer programmers and others involved in software development, including graphic designers, interface designers, project managers, and others, often including field of study-matter-experts, collaborate intensively on software projects"

In practice, it is ofttimes used to depict any thought-generation initiative with or without functional software deliverables.

My definition would be:

An intensive, software-centric ideation, prototyping and presentation claiming on known or unknown bug or opportunities.

Intensive in the above definition implies a time-boxed process asking participants for the 'impossible' — to come up with novel solutions to item problems or innovative ideas and prototypes regarding new business organisation opportunities.

Hackathons are applied science-driven and primarily about software — hence thesoftware-centric element in the definition. A Hackathon is very demanding on participants — it requires not simplygreat technical and coding skills but besides ideation andpresentation skills.

Participants are asked to come with great ideas, codify a prototype and prioritize wisely; then self-organize and execute — practice quick enquiry, prepare resources, write code, reuse existing components and systems and finally gear up a presentation — all in a time-boxed scenario. The Hackathon may exist focusing on known problems or business organisation opportunities or technologies (stated upfront) or it could be open to any ideas with no particular constraints.

                        → Check also: Building an MVP: How to define the commencement example of your product                                              

1. Defining your Hackathon

Having a clear definition of your hackathon event (style, processes, objectives, awards) is key for its success. The major attributes defining your hackathon are:

1. Date, duration,lead fourth dimension, and venues. Especially the lead-time is important in order to allow participants to get prepared by discussing ideas, teams, and collaboration scenarios. Depending on the instance and the size of the corporation/ involved team, in that location should be a lead time of a few weeks.

2. Participation rules: the logic defining who is eligible to participate (for case full-time employees from item teams, venues, etc.)

3. Minimum Deliverable: the type of deliverable required for a successful submission — for example,is it a functional prototype + source code?a predictive model? a pitch video? this is primal information that can accept a pregnant impact on the participation rates

4. Context: the focus of the event in terms of technologies, particular business problems to be solved. For instance, it could be a Data hackathon or Robotics or AR/VR; or whatsoever technology, while focusing on a item class of bug.

5. Scope: is it an internal, visitor-wide, or public event? A private hackathon could target particular teams or the entire corporation. A public hackathon accepts participants exterior the corporation.

6. Assessment criteria and procedure: the rules, priorities, and processes in gild to evaluate submissions (is there a voting procedure, a panel of experts? what are the dimensions to apply when evaluating an thought?)

7. Accolade: number of winners and type of laurels

Setting the objectives, defining 'Success'

Typically, a Hackathon upshot is expected to deliver at least a ready of interesting, novel ideas.Ideally, there should exist a few outstanding concepts, perchance with a prototype and quick proof of the concept/technology involved.

Across the obvious objective — to generate high-value actionable business ideas and product concepts— there is another attribute related to theteam dynamics and the innovation mentality: a peachy hackathon should boost the innovation culture and farther establish the thought-sharing, effective collaboration, and creativeness, driven by the enthusiasm towards a shared goal.

Employees take a cracking opportunity to detect technologies, teams and demonstrate their skills and talents outside their typical job description; Corporations have the opportunity to identify talent, feel powerful teams being set, and capture valuable feedback.

How is success divers?

Success criteria depend on the detail context — business, manufacture, size of the corporation, timing, etc. In all cases, though KPIs can be defined on some or all of the following:

1. Participation charge per unit: this is an obvious indicator of one aspect of the success of the event — how employees responded to the 'call to innovate'. The percentage over the total number of employees depends of course on the nature of the hackathon, the timing, the focus, etc. The target should be set later on analyzing similar events within the same corporation.

2. The volume of Ideas: the volume of ideas generated is likewise pregnant, particularly when analyzed confronting additional metadata (bank check also:principles of a great ideation platform)

3. Percent ofActionable Ideas : the percentage of actionable ideas (those who are promising or worth further investment from a business organisation point of view) is a good indicator of success.

4. Percentage of Business opportunities: those promising ideas which — after post-processing — proved to exist valuable business organization opportunities worth further investment.

5. Percentage of IP-generating projects: those projects who are eligible and valuable for patent protection.

6. Conversion rates: the whole batch of ideas/concepts/projects generated should exist monitored as a 'cohort' against time. This style ideas originated from a item hackathon outcome simply delivering value simply later on a menses of time, will be too measured as a successful effect.

7. Opportunities for publicity: measures of 'media attending' as the result of the hackathon event

8. Team impact:as captured from formal feedback processes — a nifty source of insights is the opinions of the participants and stakeholders. This could allow quantitative and qualitative analysis from many different angles including the event on team dynamics and morale.

ii. Running the Hackathon

Hackathons typically have a pb time — a preparation phase, from the announcement of the event to the bodily 'hack-time', as explained beneath:

The 'design time'

This is about communicating the consequence to the employees, attracting attention, and enabling formal registration of interest.

Every bit soon every bit the Hackathon is announced, employees should have a sufficient lead time — typically a few weeks- to explore ideas, technologies, teams, and resource. This is an breezy preparation phase that should be supported past proper tools (systems to enable employees to structure their ideas, projects, teams; communicate their endeavor, enquire for advice or assist). In all cases you should:

1. Announce the hackathon with clear letters and strong sponsorship from the leadership

2. Frequently and consistently communicate updateson the timeline of the event, the number of participants, the availability of the resources

3. Provideself-service tools for employees to register, create projects, explore projects, form teams, explore technologies, etc.

4. Assign a small team tosupport the procedure

The 'run time'

This is where the magic happens — teams working intensively to align their ideas, define the 'production', execute, review, iterate;the most exciting and artistic part of the hackathon where employees forget their formal roles and titles and self-organize focusing on their mission: to create something novel and impactful. Depending on the definition of each event, in that location might be a video pitch requirement, alive pitching of the thought, or a alive demo of the product/ prototype. In all cases the importance of finer presenting the work washed is disquisitional. You should likewise:

1. Make certain that participants have defended time to work on their projects

2. Ensure that suitable concrete space and equipment is bachelor to all teams

The 'cess time'

Valid deliverables submitted by the teams are being assessed based on the protocol of the particular event. This could involve a voting procedure across the corporation, a panel of experts analyzing certain aspects of each projection, or a combination of both. In certain cases, actual customers could besides be involved and provide feedback on projects. Exist mindful of the following:

1. Selecting winners based onpopularitywithin the corporation is typicallybiased and probably misleading

2. The panel of experts should apply predefined dimensions like, for example, feasibility, level of innovation, expected business organization impact, the opportunity for intellectual belongings, and potential for differentiation.

Winners & Awards

Depending on the construction of the detail event, there could be a single winning team or multiple winners beyond different categories. Selecting the award for each case is also a very significant aspect of the Hackathon — typically awards are monetary (for example a bonus), symbolic (plaques, cubes, championship), or a slice of technology/device.

The virtually important though from a developer'southward point of view is resources and sponsorship to drive the product/idea to the side by side stage . This could be the most inspiring award of all — the power for the winning squad to use specialized resources (developers, equipment, software, services) — according to a suitable plan — and get prepared for a formal presentation of the outcome to the senior stakeholders, leaders and conclusion makers. This type of award can drive impressive success stories of 'hackathon projects moving to production' and attach additional purpose to the consequence.

three. Analyzing the Business organization Value

Hackathons are expected to generate actionable ideas (for case features for an existing product), strategic product concepts (a new production to consider and further experiment with), and process improvements (novel, more than efficient ways to practice things).

At the squad level, Hackathons provide a nifty fashion to inspire teams and promote creativity, collaboration, and innovative thinking. Programmed in the right way, hackathons can drive an important cultural shift within the team: theexperimentation & innovation mindset.

A gamification layer on top of hackathons can farther motivate and reward employees for existence innovative while staying aligned with the strategy of the corporation.

This article provides actionable guidance on how to define a expert Minimum Viable Production and how to avoid common mistakes and risks. If you are in the process of designing a product, establishing a product development function, or setting up a engineering science startup y'all will find essential information on how to approach the MVP development process.

A popular definition for the MVP is this one "… the minimum viable product (MVP) is a production with but plenty features to satisfy early customers, and to provide feedback for future development…"

Building neat products is a difficult and complex job — only also fascinating. It requires a assuming vision and, at the aforementioned time, a strong connection with reality. This commodity presents the key qualities of a great Product Leader.

In this article, our guest author Nur Karadeniz explains how every business depends on a complex organization of people, processes, and technologies. Nur presents how to harness a variety of experts to develop powerful ideas to address your chosen problem and assistance y'all consider how to examination and confirm the all-time ideas to implement.

User stories are simple, all the same extremely powerful constructs: they describe pieces of functionality from a user'due south point of view, expressed in a solid, meaty way. Read on how they can accelerate product evolution and innovation workshops.

George Krasadakis

George is a easily-on Engineering science & Innovation Leader and Consultant on the corporate innovation process and architecture. He has more than than two decades of experience in technology startups, consulting firms, and large-tech companies - including Microsoft (European Evolution Centre) and Accenture (Global Eye for Innovation).

https://www.theinnovationmode.com/george-krasadakis

Source: https://www.theinnovationmode.com/the-innovation-blog/how-to-run-a-successful-corporate-hackathon

Share this post