The briefing ended. Who owns the next step?

An analyst asks for a demonstration. A product leader offers supporting data. Someone mentions a useful customer example. The call ends with several possible next steps, but the calendar entry only records that the briefing happened.

This is where a useful conversation can lose momentum. Preparing and delivering the briefing took effort; completing the commitments requires its own process. Every agreed action needs a clear description, an owner and a way to tell whether it has actually happened.

Capture what was said

Assign responsibility for the record before the meeting. The person leading the presentation should not also have to reconstruct every question and commitment afterwards. Keep the team small enough for a focused discussion, while making sure someone captures the substance.

Separate the analyst’s questions, explicit requests, the company’s commitments and the team’s interpretation. “Asked how the product works in a regulated environment” is a useful record. “Very impressed by our compliance story” is a judgement that needs evidence and may obscure the question the team still has to answer.

The same distinction matters for follow-up. An analyst requesting a demo is different from the vendor offering one. Record the difference so a suggestion does not become an assumed appointment.

Turn a commitment into an action

“Send more information” leaves too much open. State which information, the question it addresses, who will prepare it and who will send it. Where a date was agreed, preserve it. Where there was no external deadline, choose an internal target and label it accordingly.

For a meeting, track the steps separately. A scheduling request is progress. A proposed time is further progress. A confirmed appointment and a completed demonstration are different states. Recording them accurately makes stalled actions easier to identify.

Consider an illustrative example: an analyst asks to see a particular workflow. The product lead owns the demonstration content; the coordinator owns scheduling; the AR lead checks that the session answers the original request. One person remains accountable for moving the overall action to completion. Shared involvement should not leave accountability unclear.

The follow-up record

• Origin: briefing date, analyst and organisation.
• Request: the question or agreed action, stated precisely.
• Status of agreement: requested, offered or awaiting clarification.
• Owner: the person accountable for completion.
• Dependencies: contributors, approvals or information needed.
• Timing: agreed external date or clearly labelled internal target.
• Progress: the latest action and its date.
• Completion evidence: the sent material, confirmed outcome or completed meeting.

Review the open commitments

Make the action record part of the regular account review. Check whether requested material has been sent, whether scheduling has moved and whether an unanswered question needs another owner. If an action is no longer appropriate, close it with a reason rather than allowing it to disappear.

Keep the analyst’s time in mind. Follow-up should address the original request with relevant material. A large attachment pack or repeated scheduling messages will not compensate for an unclear answer.

Briefing counts show that conversations took place. A record of completed commitments shows whether the organisation did what it said it would do. That is a practical standard an AR team can manage, review and improve after every call.

Explore the wider guidance in the Kea AR Knowledge Map.

Share this article