An innovation day helps showcase employee projects and select ideas for further work. We break down the program, zones, criteria and handover to a pilot.
An innovation day often turns into a long showcase of projects: the authors presented, the guests left, and the decision about the next step remained in an email thread. We put this format together differently — we link the purpose of the meeting, the participant route, the selection criteria and the pilot owner in advance.
Every week at Aventura we break down working formats for corporate events: the program, the venue, the team and the details that influence the outcome.
Why does a company need an Innovation Day?
In short: an Innovation Day is needed to showcase employees' ideas in a single managed format, gather questions from colleagues, and select several directions for further validation. The event does not replace the work process. It helps quickly connect idea authors, experts, and managers around a clear next task.
Start with the decision that should emerge after the event. For example: select ideas for an internal pilot, gather feedback on new products, or find projects between departments. One meeting can address several tasks, but one of them must be the main one.
We capture this task in the brief. There we also specify the participants, venue constraints, the required level of confidentiality, and the decision-making method. Such a framework protects the program from turning into a long series of presentations.
Event concept: a showcase plus working selection
Answer: a working concept combines an open showcase of projects with a separate track for discussion and selection. A participant first grasps the idea in a few minutes, then asks a question, marks their interest, and, if needed, goes to a short pitch before experts.
Different modes of participation are suitable for the showcase and the business part. The project author answers questions at their stand, while the expert joins at a separate time. We link the project card with the relevant experts in advance so the conversation continues after the general program.
It is better to conduct the selection in a separate zone or in a separate time slot. This way, visitors can freely explore the projects, and the expert group gets a calm space for comparison. The format can be linked to a strategic session program for a company if the ideas need to be part of a broader change plan.
Subscribe to Aventura's Telegram channel, if you want to receive new breakdowns without unnecessary noise.
Zones for the participant route
In short: the basic route consists of a registration and navigation zone, a project showcase, a place for short talks, meeting points, and a quiet zone. The set changes depending on the number of guests and the event goals, but each zone must have one clear function.
The table brings together the key points of the section: Zone, What happens, What to prepare. Use it as a quick reference when preparing the event.
| Zone | What happens | What to prepare |
|---|---|---|
| Entrance and navigation | the participant receives the route and rules | registration, badge, map |
| Project showcase | authors present ideas and answer questions | cards, mockups, author timings |
| Pitch stage | several teams briefly present their projects | screen, timer, microphone, moderator |
| Expert zone | ideas are discussed according to common criteria | tables, evaluation forms, secretary |
| Quiet zone | the participant reads materials and talks without a stage | seats for quiet conversation |
| Next step | owners and agreements are recorded | decision template and calendar |
We check in advance whether the routes of guests, authors, and the technical team overlap. For distributed teams, it is useful to provide a separate digital route. In a hybrid conference for branches, an online participant needs the same access to questions, materials, and outcomes as a person in the room.
Agenda: from registration to the next step
In essence: the program should guide participants from understanding the task to discussion and decision. We allocate time for registration, shared context, a self-guided tour of projects, short pitches, expert selection, and announcing next steps.
An example framework that can be easily shortened or expanded:
- Registration and introductory navigation. The participant understands the purpose of the meeting and the rules of the route.
- Opening by a manager. Briefly explains what task the company is solving through the innovation day.
- Project showcase. Teams work at their stations, and guests choose the areas of interest.
- Pitch session. The moderator sets the same time limit and monitors questions.
- Break and negotiations. Experts clarify details that were not included in the presentations.
- Selection. The commission fills out a single form and records controversial issues.
- Finale. The organizer announces not only the selected ideas but also the date of the next working meeting.
The rehearsal is not for memorizing the text. It checks the timing of transitions, audibility, visibility of materials, and the authors' readiness for questions. We separately run through plan B in case of a speaker delay, demonstration failure, or a change in the composition of experts.
How to select ideas without bias?
Practical answer: the selection criteria are announced before the start of the defenses and are applied equally to all projects. For a basic matrix, it is sufficient to evaluate the benefit to the company, the clarity of the problem, the feasibility of the first step, the resource requirement, and the team's readiness.
The table summarizes the key points of the section: Criterion, Expert group question, Decision after evaluation. Use it as a quick guide when preparing the event.
| Criterion | Expert group question | Decision after evaluation |
|---|---|---|
| Benefit | what task of the company does the idea solve? | clarify the effect and the target audience |
| Problem | is there a clear user and their difficulty? | conduct a short check |
| First step | can a small pilot be formulated? | define the pilot's scope |
| Resources | what people, data, and venues are needed? | assemble a working group |
| Team | who is responsible for moving the idea forward? | appoint an owner |
| Risks | what could stop the check? | record limitations and control method |
Do not mix the evaluation of the idea and the evaluation of the presentation. A good delivery helps to hear the project, but it should not automatically outweigh benefit and feasibility. The secretary collects scores and comments, and the moderator brings discrepancies up for a short discussion.
Team roles and areas of responsibility
In short: an innovation day should have separate owners for content, production, guest journey, technology, and post-event decisions. One leader holds the overall framework but does not have to simultaneously moderate the stage, greet guests, and collect feedback.
We assign roles in a responsibility table:
- project manager approves the goal, budget outline, and final decision;
- innovation curator collects projects and checks their descriptions;
- producer is responsible for the venue, contractors, timing, and plan B;
- moderator keeps the stage pace and turns questions into a working conversation;
- expert group evaluates ideas using a single matrix;
- secretary records scores, decisions, and owners of next steps.
Before the opening, the team walks the route through the eyes of a participant. This helps find empty signs, conflicting timings, and points where the project author does not know where to lead the guest.
How to account for safety and accessibility?
In short: safety and accessibility are checked along the entire route, from the invitation to leaving the venue. A participant needs clear instructions, free passage, access to materials in several formats, and the opportunity to ask a question without stage pressure.
To check safety, we look at the entry and exit plan, flow of people, power supply for demonstrations, placement of structures, work of contractors, and the procedure for changes in the program. HSE guidance recommends distributing responsibility in advance, assessing risks, and checking how the agreed measures work.
Accessibility starts with communication. We inform in advance about the route, time, format of materials, and how to get help. The venue needs readable navigation, quiet conversation areas, subtitles or a text version of presentations, and a clear channel for questions. W3C accessibility principles are useful as a general check of the ability to perceive and use information.
Transferring Selected Ideas into the Pilot
In short: the finale of the innovation day should end with a decision card for each selected idea. The card specifies the owner, the first testable step, the required resources, the meeting deadline, and the criterion by which the team will understand that the pilot is worth continuing.
During the next work cycle, we send participants a short summary: which ideas were selected, which questions remain, who is leading the next step, and when there will be an update. We separately thank the authors of projects that were not selected for the pilot. This maintains trust in the format and does not turn the selection into a closed competition.
A pilot does not have to be large. It is often more sensible to start by testing a single assumption, talking to a user, or running a test on a limited group. After that, the manager gets material for a decision: continue, change the task, or stop the direction.
How to Connect an Innovation Day to a Business Objective?
In short: an innovation day benefits the business when its purpose, guest list, and decision criteria are tied to a specific company objective. At the start, it is enough to answer three questions: what we want to change, whose ideas we need, and what decision we will make after the event.
Frequently Asked Questions
Start with the decision that should emerge after the event. For example: select ideas for an internal pilot, gather feedback on new products, or find projects between departments. One meeting can address several tasks, but one of them must be the main one.
Different modes of participation are suitable for the showcase and the business part. The project author answers questions at their station, while an expert joins at a separate time. We link the project card with the necessary experts in advance so that the conversation continues after the general program.
We check in advance whether the routes of guests, authors, and the technical team intersect. For distributed teams, it is useful to provide a separate digital route. In a hybrid conference for branches, an online participant needs the same access to questions, materials, and outcomes as a person in the room.
An example framework that can easily be shortened or expanded:
Do not mix the evaluation of the idea and the evaluation of the presentation. A good presentation helps the project be heard, but it should not automatically outweigh usefulness and feasibility. The secretary collects scores and comments, and the moderator brings discrepancies to a short discussion.
We distribute roles in a responsibility table:
At Aventura, we start with a brief, then assemble the concept, route, team, and budget. If you need to organize a turnkey corporate, business, or client event - discuss the task and request a quote. In the request, it is useful to specify the city, approximate number of participants, date, and purpose of the meeting.
Sources
- HSE - Event safety
- HSE - Managing an event
- HSE - Getting started
- W3C - Introduction to Web Accessibility
- W3C - Accessibility Standards Overview
Contents
Was this article helpful?
