Use Claude to turn 1:1 notes into talking points
Your 1:1 is in ten minutes and your notes say “test account??” and “demo – A asked”. Claude can turn them into neutral talking points and a timed agenda, including the thing you promised last week and haven’t done.
What you'll make
a short table of topics, each with its source note and one neutral question, and a timed agenda that leaves room for the other person’s topics.
What you'll need
Claude (the method also works in ChatGPT, Gemini or Copilot), your notes about the work and the support needed, and about 15 minutes. Leave out health, pay, complaints and disciplinary information; removing a name may not make a situation anonymous. This is for preparing a conversation, not for judging performance or making employment decisions.
Example result.
Priority order I owe A (N3) – Which part of the guide needs it first?
Test account blocking the guide (N4) – What help is needed to get it?
Request to lead the demo (N5) – What would you need to prepare?
1. Gather only what the meeting needs
Bring the current work topics, any support needed, your own outstanding commitments and anything the colleague has raised. Add the meeting length and how much time you want to keep for their own agenda. A few clear lines are enough.
Short numbers or dates help you find the evidence later. Keep facts separate from your questions or assumptions, and don’t fill gaps with guesses about why something happened.
Why this works: Claude can only be as fair as the notes. A guess written as a fact becomes a question with a verdict in it.
What you should see: a short list of facts, including at least one thing you owe.
2. Ask for neutral talking points
In a new chat, paste this prompt with your notes:
Use only the notes below to prepare a short set of talking points
for a 1:1. For each topic give: the topic, its source note, one
neutral question about the work or support needed, and any missing
context.
Include commitments I owe the colleague. Keep facts separate from
questions. Do not infer personality, motivation, wellbeing or
performance. Do not recommend an employment decision. If information
is missing, mark it as missing rather than filling it in.
[Paste your notes.]
[Paste your notes.] means the lines from step 1.
Why this works: including your commitments stops the agenda being one-sided. Neutral questions keep a blocker from turning into a verdict about the person.
What you should see: three to five topics, each pointing to a note, with your own promise among them.
3. Turn the points into a timed agenda
In the same chat, ask for the agenda once you’ve checked the points.
Using the checked talking points, draft a one-page agenda for a
[total minutes]-minute meeting. Put my outstanding commitments first.
Reserve at least [reserved minutes] for the colleague's own topics.
Show time ranges that add up to the meeting length and keep the
source note for each item. Do not add new facts, promises or dates.
[total minutes] is the meeting length; [reserved minutes] is the time kept for their topics.
Why this works: a time budget makes the colleague’s space concrete. Without it, their ten minutes is usually the first thing to go.
What you should see: time ranges that add up exactly. Check the arithmetic yourself; if it overruns, ask Claude to shorten it while keeping your commitment and the reserved minutes.
Check the result
- Your outstanding commitment is on the list, near the top.
- Every topic traces to a note, and topics with no source are gone.
- Missing dates and details are still marked as missing.
- The agenda adds up and keeps the reserved time.
The usual failure: a question picks up a judgement the notes don’t contain, such as “Why haven’t you taken ownership?” or “Why are you avoiding the task?”. Read each question and ask: would I be comfortable if the colleague saw the note it came from beside it?
Audit the questions against my notes. For each question, name its
source note and identify any judgement or assumption it adds. Rewrite
those as neutral questions about the work or support needed. Remove
questions with no source. Do not infer a person's motives or
performance.
Check the rewrite against the notes yourself, rather than taking Claude’s own audit as proof.
Worked example: a handover guide
Fictional example. The manager’s notes:
N1: Meeting length: 30 minutes
N2: Colleague A is preparing a handover guide
N3: I promised a clear priority order last Tuesday and have not sent it
N4: The guide is waiting for a test account from another team
N5: A asked to lead the next product demo
N6: Leave at least 10 minutes for whatever A wants to discuss
The first draft asked: “Why are you avoiding the handover guide?” Nothing in the notes says A is avoiding anything; N4 says the guide is waiting for a test account. After the audit prompt, the talking points were:
- Priority order I owe A (N2, N3). Question: which part of the guide needs the priority order first? Missing: my delivery date.
- Test account blocking the guide (N2, N4). Question: what help is needed to get the test account? Missing: who can supply it, and when.
- Request to lead the demo (N5). Question: what would you need to prepare? Missing: demo date.
The agenda: 0–5 minutes, the priority order I owe; 5–15, A’s own topics; 15–25, the test account and the demo; 25–30, note any actions actually agreed. That adds up to 30 and keeps A’s ten minutes.
What mattered:
- The manager’s promise came first. N3 is easy to leave out of your own notes, and it’s often the most useful thing in the meeting.
- The blocker stayed a blocker. The repaired question follows N4; the original invented a motive.
- Questions aren’t commitments. Nothing here is agreed until the people involved agree it in the meeting.
Try it
Protect the colleague’s part of the conversation
Move manager-led minutes and see how much remains in the 30-minute meeting.
At least 10 minutes reserved for colleague topics
10 minutes remain from the 30-minute total.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Draft a follow-up from what was actually agreed
After the meeting, write fresh notes of who agreed to do what, and any date agreed. Preparation questions don’t become actions just because they were on the agenda.
Use only these post-meeting notes to draft a short follow-up table:
action, agreed owner, agreed date and source note. Keep missing dates
as "to agree". Do not import anything from the preparation agenda or
add a deadline. Put unresolved details in a separate section.
[Paste your notes of what was agreed.]
For example, with these fictional notes:
F1: I agreed to send the priority order by Thursday 8 October.
F2: I agreed to ask the other team about the test account. No date agreed.
F3: A will draft a demo outline. No date agreed.
The test-account row should read “Me | to agree | F2”. If it picks up the 8 October deadline from F1, correct it before sending anything.
Keep the instructions in a Claude Project
For a repeated task, open Projects, choose + New Project and name it “1:1 preparation”. On Team or Enterprise, choose Keep it private. Then choose Set project instructions, paste the rules from the step 2 prompt (only the notes supplied, no inferred motives or performance, missing means missing) and select Save instructions.
Each time, start a new chat in the Project and paste the current notes. Don’t rely on earlier chats as the source, and don’t build an employee-history file in the project’s knowledge. If Projects aren’t available, paste the rules at the start of a normal chat.