A panel ends with pages of notes, but one question is still hard to answer: where did the speakers actually agree, and where were they talking about different things?
A viewpoint map organizes a panel by question, then records each speaker's claim, reason, scope, and unresolved evidence. It helps you compare positions without turning every difference into a disagreement or every repeated phrase into a consensus.
This method works with notes, a transcript, or a recording you are permitted to review. The panel and quotations below are entirely fictional. They are not customer material or output from a Recolx product.
Capture each claim before combining speakers
Begin with one claim at a time. A claim is what a speaker wants the audience to accept, not every example or background sentence around it.
Keep the source position beside the claim. A timestamp, transcript line, or page reference lets you reopen the context. If you paraphrase, label it as a paraphrase. Quotation marks should contain the speaker's words, not a smoother version you wrote later.
Listen for limits. “This worked for experienced facilitators in our pilot” is narrower than “this works for every training program.” Preserve words such as sometimes, for beginners, and when support is available.
If the passage is unclear, record the uncertainty. Do not finish the speaker's argument from what sounds likely.
Build one small card for each position
A useful claim card needs only five parts:
- Question: the issue the speaker is addressing.
- Claim: the position, in the speaker's words or a faithful paraphrase.
- Reason: why the speaker gives that answer.
- Support: the example, observation, or source offered in the panel.
- Scope or unknown: where the claim applies and what remains unestablished.
Reason and support are not the same. “Practice matters because people need to try the task” is a reason. A described workshop where participants completed an exercise is an example. If the speaker provides no support, write “not provided in this passage” rather than inventing one.
The card is a comparison aid, not a verdict on who is correct. Evaluating the evidence may require material beyond the panel.
Group the cards by question, not speaking order
A chronological summary often reads: Speaker A said this, then Speaker B said that, then Speaker C added something else. It preserves sequence but can hide the relationship between their ideas.
Purdue OWL's guide to synthesizing sources distinguishes synthesis from summary. It recommends grouping material by topic, making relationships clear, and retaining outlying perspectives rather than forcing sources to fit.
For panel notes, use the same narrow principle: put responses to the same question together. Then label the relationship you can actually support:
- Agreement: the speakers make compatible claims about the same issue.
- Disagreement: their claims cannot both guide the same choice under the stated conditions.
- Different scope: they address different people, stages, or constraints.
- Unclear: the record does not establish the relationship.
Do not force a relationship just because two speakers used the same word. “Feedback” could mean comments during practice for one person and a manager's review a week later for another.
Example: three speakers on workplace training
This example, including every name and quotation, is fictional. A moderator asks: “What should teams prioritize when introducing a new internal process?”
Ari: “Give people a short walkthrough before the first session, so the basic terms do not consume the live discussion.”
Bo: “People need to attempt one realistic task during the session. Watching the steps is not the same as doing them.”
Cam: “Managers need a follow-up check after the session, because a process can look clear in training and break in the work environment.”
A weak summary might say: “The panel agreed that training should include a walkthrough, practice, and manager follow-up.” That sentence sounds tidy, but the panel record does not show that each speaker endorsed all three parts.
A viewpoint map is more precise:
- Before the session — Ari: provide a short walkthrough. Reason: preserve live time for discussion. Support: no example or result is provided in this excerpt. Unknown: which participants need the walkthrough.
- During the session — Bo: include one realistic attempt. Reason: observation does not demonstrate performance. Support: no measured outcome is stated. Unknown: how the task should be assessed.
- After the session — Cam: check application in the work setting. Reason: clarity during training may not carry into practice. Support: no specific case is described here. Unknown: who conducts the check and what counts as a problem.
The clearest relationship is different scope: before, during, and after the session. Their suggestions could form a sequence, but the panel has not approved that sequence. A follow-up question could ask each speaker how their recommendation relates to the other stages.
There may also be a shared concern—that hearing an explanation alone is insufficient—but even that should be described as an interpretation unless the speakers confirm it.
Write a synthesis that keeps the edges visible
After mapping the cards, write one or two sentences about the relationship, followed by the important limitation:
The speakers focus on different stages of adoption: Ari prepares participants before a session, Bo emphasizes practice during it, and Cam looks for problems after people return to work. The excerpt does not establish whether they support one combined program, and none provides outcome data in this passage.
This is more useful than three disconnected mini-summaries, but it does not pretend the panel reached a decision.
If you plan to share the map, reopen the relevant passages and check names, claims, negatives, and scope. Our guide to taking usable lecture notes can help with source markers during the session. Store the reviewed map beside its source links using the principles in the searchable notes guide.
Start with one panel question and three claims. If a relationship cannot be supported, label it unclear and keep the question for later instead of manufacturing agreement.
By Recolx Editorial. Published September 18, 2026.
