RECO
    Back to blog
    Organizational Development

    A Conversation Culture in 90 Days: How SMEs Make AI Transcription the Default Without Resistance

    Mag. Paul H. SchindlerMag. Paul H. SchindlerCEO, RECOPublished Last edited 5 min read

    A documentation tool that people have to switch on before every meeting is, after a few weeks, used only by those who wanted it anyway. The endless loop shows how recorded outcomes support later discussions. For SMEs, the challenge is making knowledge preservation a lawful, agreed routine and knowledge transfer a visible use of the records, so documentation is not merely another task. The technology is rarely the reason. Anyone who has to decide before each team meeting whether to record it will skip it on busy days. And a service business has no shortage of busy days.

    My argument in this post: AI-supported conversation documentation only becomes part of a company's conversation culture once it is the default. On is the normal state, and the exception needs a reason. I lay out how I would approach that shift as a 90-day roadmap in three phases.

    The objection: a default sounds like coercion

    Managing directors and works councils often push back that voluntary use builds acceptance while a default breeds resistance. That objection mixes up two things. A default decides what happens when nobody makes a choice. It takes away nobody's right to say no.

    So I separate two levels:

    • Meeting types follow the default. A team that wants to hold its weekly meeting without documentation gives a reason once, for example because HR matters come up there.
    • People keep their choice. Any participant can decline for a single conversation without justifying it in front of the team.

    Only this separation makes a default stick. One person who feels ambushed can turn the mood of a whole team. For audio recordings you also need a sound legal basis and the works council on board, as explained in Documenting employee conversations.

    Before day 0: three questions and a baseline

    Before kick-off, management and HR should have answered three questions:

    • Which meeting types gain the most from documentation? Obvious candidates are team check-ins, project updates, handovers and decision meetings.
    • Which conversations stay out on purpose? Confidential HR measures, meetings with employee representatives, anything touching health.
    • Who will champion the project, and who will slow it down?

    What is easy to forget is a baseline. To show change on day 90, you need to know where you stood on day 0. I would count for one week in the pilot teams:

    • How many internal meetings happen per week, and how many have notes someone could find?
    • How often does someone ask about something already discussed? A tally sheet will do.
    • How long does a new hire take to complete a first task without asking for help?

    Days 0–30: rules anyone can explain in one sentence

    The first phase decides whether staff trust the project. By day 30, four things should be in place:

    • An agreement with the works council and data protection: what is captured, who sees what, how long it is kept and who may delete it.
    • A message to everyone on which conversations are affected and how to opt out.
    • The default rule in one sentence, for example: "Internal meetings of the pilot teams run with RECO, team leads give a reason when they exempt a whole meeting type, and anyone can decline for an individual conversation."
    • A short training for managers on preparation, working with the notes, and raising the topic with their team.

    A useful test for day 30: ask three randomly chosen colleagues what happens with the conversations. Three different answers mean the communication isn't finished.

    Days 31–60: pilot with three to five teams

    Now the benefit has to show. Pick teams that coordinate a lot internally and are visible across the company, such as consulting, a project team, a department head and customer success.

    In these teams, the default applies to:

    • weekly team check-ins
    • project updates and status meetings
    • feedback rounds and employee reviews, provided both sides agree
    • handovers for holidays or role changes

    Whether the pilot holds depends on the managers. One who says in the next meeting "According to Tuesday's notes, we agreed that …" shows that the documentation gets read. One who never opens the notes ends the rollout before it starts.

    One example from practice is AAZB, the Akademie für angewandte Zukunftsbildung, which has trained coaches, consultants and trainers for more than ten years. There, meetings, team check-ins and stand-ups run with RECO. The result is a knowledge base in which 92% of conversation content is searchable, and new colleagues find their footing faster. What interests me most is the choice of meetings: the unspectacular, recurring ones. In my assessment, those are exactly the ones an opt-in model drops first, because nothing special hangs on any single one of them.

    Days 61–90: from pilot to way of working

    Now the pilot becomes the rule for the whole company:

    • rollout to all teams and locations, in waves rather than on one go-live date
    • integration with calendars, Microsoft Teams or Google Meet, the CRM and onboarding materials
    • RECO in onboarding, so new hires see documentation as normal from day one
    • three metrics reported monthly from now on

    What to measure on day 90

    This is where the baseline pays off. I would stick to three numbers:

    • Coverage, the share of internal meetings with findable notes, compared with the baseline. If it has barely moved, the default isn't really a default yet.
    • Follow-up questions, using the same tally sheet as in the baseline week.
    • Ramp-up, the time until a new hire completes a first task independently.

    I would not measure satisfaction with the tool. It says little about whether knowledge is actually being passed on.

    Why rollouts fail

    • Managers who don't use the notes themselves.
    • Unclear rules for sensitive conversations. One rumor about an HR conversation recorded without asking can cost more trust than many good team meetings build.
    • No link to concrete occasions such as onboarding or handovers. Then the tool stays an extra that disappears the first time schedules get tight.

    If I could give only one piece of advice: write the default rule so it fits on an index card, and put the right to decline on the same card. Then everyone knows what applies.

    Sources

    Frequently asked questions

    Can an internal meeting be recorded without every participant agreeing?+

    For audio recordings, assume the answer is no. In Germany, recording the privately spoken word without authorization is a criminal offense under section 201 of the Criminal Code (StGB), and under data protection law every processing operation needs a legal basis under Art. 6 GDPR. In practice, everyone present knows in advance and can decline for that conversation. Written minutes of outcomes, which companies have always kept, are a different matter. This is not legal advice.

    What happens if management and the works council cannot agree?+

    In Germany, for matters under section 87(1) of the Works Constitution Act (BetrVG), the conciliation board decides, and its ruling replaces the agreement (section 87(2) BetrVG). In Austria, for data systems under section 96a of the Labour Constitution Act (ArbVG), the arbitration board can replace the works council's missing consent. For control systems that affect human dignity (section 96(1) no. 3 ArbVG), the law provides no such route. Both routes take time and strain the relationship. If you involve the works council before day 0, you will rarely need either. Not legal advice.

    Related articles

    In a 30 minute software demo we show you how RECO secures and transfers knowledge in your company. Request a demo now and we'll get back to you with a proposed time.