Internal experts conference in 2026

We break down the full cycle of an internal experts conference: from collecting topics and preparing speakers to a multi-track program, recording, and knowledge base.

A strong internal experts conference begins long before the stage. A company needs to find useful topics, separate experience from a general department presentation, help authors prepare material, and decide in advance what will remain after the presentation. At Aventura, we view such an event as an entry point into the knowledge-sharing cycle. A talk should lead to clear material, a working contact, or a next action.

Если задача уже стоит в плане, запросите смету на конференцию внутренних экспертов. We will clarify audiences, thematic areas, number of tracks, recording mode, and the set of materials before developing the scenario.

What is an internal experts conference?

An internal experts conference is an in-person or hybrid program where employees share verifiable professional experience with colleagues. They present working approaches, solutions, limitations, and conclusions that emerged within a specific organization. The company collects topics, conducts a substantive selection, prepares authors, organizes discussion, and preserves applicable results in the accepted knowledge system.

A speaker can be an engineer, technologist, analyst, salesperson, lawyer, project manager, or back-office specialist. A permanent teaching role is not required. Value is created by subject matter knowledge and the willingness to adapt it for the audience.

Форум внутренних тренеров отвечает на другой вопрос: как обучать коллег, проектировать занятие, работать с группой и оценивать учебный результат. The Experts Conference focuses on what the company wants to transfer between functions.. An internal trainer can help the author with methodology, but does not replace the subject-matter expert.

One external talk does not change the nature of the event. An invited specialist can provide an industry framework, while internal authors will show how the topic works in the company’s context. The core of the program is still built on internal knowledge and connections.

Goals and outcome: what should change after the event

The conference goal describes the further use of knowledge, not the fact of holding it. A suitable formulation connects the audience, topics, artifacts, and the next step: collect applicable cases, introduce departments to experts, update internal instructions, or open work on shared problems. The formula “hold a conference and increase engagement” is too broad for the scenario and evaluation.

We start with four questions:

1. What knowledge is currently locked inside individual teams?
2. Who needs it for work or decisions?
3. In what form can it be safely passed on?
4. Who is responsible for applying and updating the material after the event?

The answers help choose the scale. Sometimes one general track and several deep dives are needed. In another company, parallel sessions for different functions are more useful. The number of rooms should not become a goal in itself.

We define the boundaries separately. A conference does not replace ongoing training, document management, or the work of communities of practice. It creates a point of concentration: employees find authors, compare approaches, and agree on what will go into working materials.

Preparation can be run as organizing a corporate forum, if the program includes a shared context, thematic sections, work with speakers, and a shared package of results. At the start, it is also useful to align the brief for the corporate forum: audiences, roles, venue, tracks, equipment, and expected artifacts.

How to run a call for papers?

Call for papers - это управляемый сбор тем, а не просьба прислать готовые презентации. На первом шаге программному комитету важно понять проблему, аудиторию, главный тезис, практическую основу и ограничения. Качество слайдов и уверенность выступления проверяются позже. Такой порядок расширяет круг авторов и не отсекает сильный опыт из-за слабой первой подачи.

В положении о сборе заявок мы советуем указать:

• the purpose of the conference and audiences;
• thematic tracks and acceptable formats;
• application fields and selection criteria;
• review, editing, and rehearsal stages;
• privacy, recording and publication rules;
• decision timelines and feedback flow;
• the author's obligations after the topic is accepted.

Карточка заявки может содержать рабочее название, аудиторию, проблему, ключевой тезис, опыт или данные, ограничения, ожидаемый результат для слушателя, соавторов и желаемый формат. Готовую презентацию лучше не требовать: сначала проверяется идея.

Процесс сбора удобно вести последовательно:

1. Define tracks. The team sets boundaries and examples of suitable topics.
2. Open a short form. Authors do not need to prepare a talk before the first decision.
3. Hold introductory meetings. Potential speakers can refine their idea and find a co-author.
4. Conduct an initial screening. The team flags duplicates, sensitive information, and overly broad wording.
5. Submit topics for review. All reviewers use a single criteria form.
6. Communicate the decision. The author receives a clear next step, not just a single word “accepted” or “rejected”.

Назначение сверху допустимо для обязательного сообщения руководства, но оно не должно подменять открытый сбор. Иначе сотрудники быстро понимают, что программа была распределена заранее, и перестают приносить новые темы.

We publish breakdowns of corporate and business formats in Aventura's Telegram channel.

Content review and program committee

Review проверяет полезность и безопасность содержания до производства доклада. Рецензенты смотрят на соответствие цели, ясность тезиса, предметную достоверность, применимость, ограничения и риск раскрытия. Программный комитет затем собирает цельную программу: разводит повторы, меняет форматы и определяет, какие материалы лучше оставить в базе знаний без сценического выступления.

Статус автора не заменяет критерии. A function lead can propose an important topic, but the program must explain who needs it and why.. An employee without public speaking experience can bring strong material and prepare it together with an editor.

A conflict of interest must be noted before a reviewer is appointed. A direct manager, co-author, or participant in the contested project can provide a useful comment, but must not single-handedly decide the fate of the proposal.

Feedback must be specific. Phrases like “doesn’t grab attention” and “needs more punch” do not help. The reviewer writes where the audience is unclear, which conclusion is unsupported, what needs to be anonymized, and which part can be applied by other teams.

Architecture of a multi-track program

Tracks are built around the participant’s choice logic, not around available rooms. The name of a track must explain the topic, level, and audience. We first sort accepted proposals into thematic lines, then check for repetitions, transitions, and conflicts, and only after that assemble the grid. This way the schedule supports the content rather than dictating it.

For tracks, you can choose one of the principles that is clear to the participant:

• professional function: production, sales, data, product;
• task type: client, quality, automation, risk management;
• depth level: introductory overview, practice, deep dive;
• process stage: problem, solution, implementation, support;
• work format: short case studies, demonstrations, clinics, and consultations.

In one program, it is better not to mix different principles without explanation. If the first track is named by function, the second by role, and the third by format, it is difficult for the participant to compare the options.

The program committee is not obliged to give a stage to every strong proposal. A narrow debrief may work better as a closed consultation. Several similar cases are useful to combine into a panel or clinic where participants compare solutions on the same issues.

Для такого проекта подходит организация делового мероприятия: содержание, сценарий, площадка и работа со спикерами собираются в одном производственном контуре.

How to prepare internal speakers?

Preparation starts with the thesis, not with slide design. The expert formulates one main idea, describes the initial situation, shows the solution and evidence, names limitations, and ends with the next action for the audience. An editor helps maintain this throughline. A subject-matter reviewer is responsible for content, not for stage form.

The workflow might look like this:

1. Уточнить аудиторию и одну главную мысль.
2. Проверить факты, цифры, права на материалы и режим раскрытия.
3. Собрать логику: контекст, решение, доказательства, ограничения, вывод.
4. Убрать внутренние сокращения или объяснить их при первом употреблении.
5. Подготовить черновик материалов в доступном формате.
6. Провести содержательную репетицию с таймером и вопросами.
7. Доработать структуру после обратной связи тестовой аудитории.
8. Выполнить технический прогон на реальном оборудовании или платформе.
9. Зафиксировать правила записи, публикации и обновления материала.

The best specialist is not automatically the best speaker. But a weak first delivery does not mean the topic should be lost. Sometimes the author needs a co-author, an interview with an editor, or another format: a demo, a conversation with a moderator, a whiteboard breakdown.

Time for preparation must appear in the work calendar. A presentation that an employee assembles at night without the manager's support almost inevitably goes through review and rehearsal too late.

Moderators rehearse too. They know the session theses, prepare linking questions in advance, and understand which topics cannot be discussed publicly. Their task is to help the audience see connections, not to repeat the speakers' biographies.

Execution, hybrid format, and run of show

On the day of the conference, the content, technical and coordination teams work from a single script. It contains final versions of presentations, speaker appearances, questions, transitions, recording modes, backup solutions, and an owner for every change. Live discussion does not cancel the script: the team must understand who can change the order and how to bring the program back on track.

Before the stream opens, the coordinator checks the authors' presence, materials and approvals. The moderator receives session cards. The technical team uses only approved files so as not to search for a new version before going live.

Для параллельных секций особенно важна единая навигация. Названия треков и залов совпадают в приглашении, программе, указателях, экранах и цифровом интерфейсе. Вопросы без ответа фиксируются и передаются владельцу, а не исчезают после закрытия секции.

Если часть аудитории подключается дистанционно, гибридный формат конференции проектируется как отдельный маршрут. Онлайн-модератор следит за чатом и очередью вопросов. Реплики из зала повторяются в микрофон. Материалы доступны удалённым участникам, а резервный канал проверяется до события.

A company executive can open the program or answer general questions. This block should be linked to the conference themes and next steps. Individual principles of dialogue are discussed in the material on a meeting between management and employees.

How to plan recording, privacy, and accessibility?

Режим записи определяют до принятия заявки. Автор и участники должны знать цель, состав фиксируемых данных, доступ, возможность скачивания, срок хранения и владельца файла. Закрытая ссылка сама по себе не решает вопрос приватности. Для чувствительного кейса можно выбрать закрытый трек, обезличивание, текстовый материал или полный запрет записи.

Company проверяет применимое право и внутренние политики отдельно. Технические настройки платформы помогают уведомить участников и ограничить доступ, но не заменяют правовую оценку.

Перед публикацией материалов мы задаём пять вопросов:

1. Why are recordings or data needed after the conference?
2. Who will receive the source file and the processed version?
3. Which fragments must not be displayed in search or the shared catalog?
4. When will access rights and storage requirements be reviewed?
5. Who is responsible for deleting, restricting, or updating the material?

Accessibility is planned before registration and slide creation. Participants need a way to communicate their needs. The venue, platform, microphones, materials, captions, and descriptions of significant visual information are part of the organizer's and speaker's brief. PDF should not be the only format if the material can be provided in an adaptable form.

Recording audience questions requires a microphone. Otherwise, the remark will not make it into the audio, captions, or final material. Automated transcription is reviewed before publication: it can distort terminology and retain accidental personal or confidential details.

Knowledge base and follow-up after the conference

A recording without a description and an owner rarely becomes a working knowledge base. A strong session needs a usable artifact: a maintained page, a guide, a checklist, a summary, answers to questions, a task, or a limited recording. The material is linked to processes and assigned a review date. The presentation remains a presentation layer, not the only source of truth.

The session card may include:

• title and brief summary;
• author and owner of the material;
• audience and background;
• date of the presentation and next review;
• outline and available materials;
• recording and transcript, if permitted;
• related processes, documents, and tasks;
• usage restrictions;
• answers to questions;
• status and access level.

It is useful to plan work on the publication in advance. A detailed roadmap is discussed in the article on post-conference content: from selecting recordings and editing to navigation and reuse.

We divide follow-up into four streams:

1. For participants. Materials, answers, and navigation of the knowledge base.
2. For speakers. Feedback, open questions, and a plan for updating the material.
3. For process owners. Decisions, tasks, pilots, and changes to working documents.
4. Программной команде. For the program team.

An email with photos does not close follow-up. If a session surfaced a useful solution, it gets an owner. If the takeaway is not applicable, the reason is also recorded. The next conference starts with checking previous commitments, not from a blank slate.

What to measure without invented benchmarks?

Универсального процента успешных заявок, просмотров или внедрения не существует. Метрики выбирают от исходной проблемы компании. Полезно видеть всю цепочку: сотрудники узнали о сборе тем, подали заявку, прошли review, подготовили материал, получили аудиторию, создали артефакт и связали его с рабочим действием.

Для call for papers можно смотреть число завершённых заявок, функции авторов, причины отказа и потребность в помощи до review. Для подготовки - прохождение содержательной проверки, репетиции, проверки фактов и технического прогона.

Для базы знаний важны владелец, дата пересмотра, связи с процессами и факты использования. Общий счётчик видео этого не показывает. Для follow-up мы смотрим открытые вопросы, назначенные действия и их статус.

Мы не делаем причинный вывод «конференция повысила производительность» по посещаемости или удовлетворённости. Для такого заявления нужны исходные показатели и отдельный дизайн оценки. В статье достаточно честно показать наблюдаемые результаты процесса.

Retrospective with action items, owners, and review deadlines. обсудите конференцию с намиIf you need to link call for papers, review, speaker preparation, a multi-track program, recording, and post-event materials into one project,

Sources

• Google re:Work: Employee-led learning principles and practice
• GitLab Handbook Usage
• NASA: Lessons Learned
• OpenReview: Conference Review Workflow Overview
• Toastmasters: Preparing a Speech
• W3C WAI: Making Events Accessible
• Zoom Support: Providing consent to be recorded
• Microsoft Learn: Manage Teams recording policies
• NIST Privacy Framework
• ICO: Data minimisation
• GOV.UK Service Manual: Agile tools and techniques
• WHO: Ensuring Accessibility