Meeting & Follow-up Management

The problem

Client meetings, team reviews and planning sessions end with agreements, but the list of who does what is often unclear. Notes are taken by one person and shared late, or not at all. Actions agreed by the group belong to nobody in particular.

The next meeting starts with the same open questions, and clients notice when a promised follow-up does not arrive. A client who hears "we will send that over" three meetings in a row starts to doubt the rest of the plan, however good the work is.

Picture a monthly client review that runs ten minutes over. The last item, a call with the client's technical team, is agreed in the final two minutes as people are leaving. Everyone nods. The person taking notes writes "set up IT call" without a name. The project lead assumes the engagement manager will book it, and the engagement manager assumes the project lead will. Three weeks later, at the next review, the client asks how the call went.

The cost is rarely one missed action. It is the slow erosion of the meeting itself. When follow-ups do not happen, people stop trusting that agreements will stick, meetings get longer, and more decisions are reopened instead of acted on.

What GeniOS is designed to surface

In pilot, the aim is for GeniOS to read meeting notes and the calendar together with email and chat, and send the manager a clear follow-up picture soon after each meeting.

• Agreed actions. Actions agreed in each meeting, with a proposed owner and date.
• Actions with no owner. Raised soon after the meeting ends, while everyone still remembers the discussion.
• Client follow-ups. Follow-ups promised to clients or other teams that have not gone out.
• Open before the next meeting. What is still open before the next meeting with the same people, so it starts with progress instead of questions.

As with all GeniOS intelligence, a person stays in charge: nothing is sent or changed until someone approves it. A manager can delegate an unowned action to a named person, or hand the drafting of a follow-up email to an agent and approve it before it goes out. For the wider link between meeting decisions and the work that follows across teams, see Meeting-to-Execution; for preparing leadership meetings, see Board Meeting Preparation.

A worked example

Example at a generic company. Names, dates and numbers are made up to explain the idea.

An engagement manager at a consulting firm runs a monthly review with a client. The meeting agrees on three actions: a revised timeline, a cost estimate and a call with the client's IT team.

The engagement manager has four other client meetings that week. The notes are in a shared document, and the IT call line has no name next to it. In most months this would surface at the next review, when the client asks about it.

Here is how it would look in pilot: an hour later, the manager receives one note showing the timeline and the cost estimate have owners and dates, while the IT call has no owner, and suggesting the project lead book it by Friday. The manager delegates the booking to the project lead, who proposes three times to the client's IT lead the same afternoon. On Thursday a second note confirms the revised timeline went to the client and the cost estimate is still in draft, due Friday. By the next review, all three actions are closed, each on proof: the sent timeline, the sent estimate and the meeting on the calendar.

How teams use it day to day

The routine is built around the meeting itself, with a short check after it and another before the next one.

1. Keep notes where they are

   Take meeting notes the way the team already does; there is no new template to fill in.

2. Check owners within the hour

   Soon after the meeting, review the agreed actions and name an owner for any action that has none.

3. Approve client follow-ups

   Delegate follow-up emails to a person or a drafting agent and approve each one before it is sent.

4. Watch the open items

   During the week, respond to notes about actions near their date with Done, Later or Delegate.

5. Open the next meeting with progress

   Before the next meeting with the same people, look at what closed and what is still open.

Where it applies

These are application areas where this use case can apply, not a list of current deployments. Our design partner work so far is in manufacturing, with Vaultex.

The use case applies wherever meetings produce promises to clients or colleagues. Professional services and consulting firms run client reviews; software and education businesses run customer and partner calls; real estate and construction teams run site and project reviews; media teams run editorial and client planning sessions. Administration, operations, sales and customer success teams would see the follow-ups that come out of them.

• Domains: Administration, Operations, Sales, Customer Success & Support
• Industries: Professional Services & Consulting, SaaS & Technology, Real Estate & Construction, Education & EdTech, Media & Publishing
• Roles: Managers

Status

Pilot We are shaping this use case with design partners now, and it is not yet a finished part of the product. If this is a problem you have, talk to us about shaping it with us. Design partners help us decide how soon after a meeting the first follow-up picture is most useful.