# How to Follow Through on Promises You Make in One-on-Ones

> Review the support you promised in one-on-ones. Separate your undertaking from the result it should help achieve, then give a clear update and agree next steps.

- URL: https://www.hemory.com/blog/searchable-memory/manager-commitment-follow-up/
- Language: English (en)
- Author: Hemory Team
- Published: 2026-11-04
- Last updated: 2026-11-04
- Summary: Follow through on manager commitments by recovering the accepted undertaking, checking current evidence and separating the promised action from its intended outcome. A fictional review-notice example shows a completed inquiry with an organizer response still pending. Hemory supplies captured context for a manager follow-up note; the teammate’s idea remains unassigned.
- Tags: manager commitments, one-on-one follow-up, manager support

In your last one-on-one, you said you would ask why review invitations were arriving so late. You sent the question, but the organizer has not replied. At the next meeting, saying nothing leaves your teammate unsure whether you followed up; saying you fixed the problem would go beyond what happened.

Prepare a short update on the support you promised. Establish the undertaking, check what you did, and distinguish that action from the outcome your teammate needs. Hemory can preserve the original exchange so you can return to the actual promise instead of relying on a vague memory that you offered to help.

## Start with your own undertaking

Look for what you accepted responsibility for: asking a question, making an introduction, reviewing a draft, or arranging support. Keep its scope and any stated timing or condition.

“I'll ask the organizer about earlier notice” is a commitment to ask. It is not a guarantee that invitations will change. “I can help if you send the draft” is an offer with a prerequisite; check whether it became an accepted next step and whether the draft arrived.

A teammate's suggestion is different again. If they proposed a written preview but did not volunteer to create it, do not turn that idea into their overdue task.

For the wider meeting agenda, see [preparing for a recurring one-on-one](/blog/searchable-memory/prepare-for-a-one-on-one/). This guide focuses on the promises you bring back as the manager.

## Recover the exchange, including the response

Use relevant notes and conversations from your working relationship. For discussions captured with Hemory, transcripts and organized Memory can retain an offer or qualification that never became a formal task. Summaries, people, topics, and the timeline can help you locate it.

For a known conversation, ask a follow-up question such as: “What did I agree to do about review notice, and did we set timing?” Check the response if it changes whether something was an offer, an accepted undertaking, or an idea to explore.

Keep the review tied to the work and support discussed. A few remarks do not establish someone's motivation or personality. The point is to give an accurate account of your follow-through and invite an update on the issue.

## Check your action separately from the intended result

Use current evidence to establish what happened after the promise: the message you sent, a reply, an introduction, or the person's confirmation. Missing conversation updates do not prove that you failed to act.

| What you promised | What establishes your action | What may still need checking |
|---|---|---|
| Ask about earlier review notice | You sent the question to the organizer | The response and whether notice improves |
| Review a draft after receiving it | The draft arrived and your feedback was shared | Whether the feedback answered the need |
| Make an introduction | You connected the people as agreed | Whether they need help arranging the conversation |
| Seek an approval | You submitted the request | The approval outcome |

A completed action can leave the wider issue open. Conversely, if you have not taken the promised step, say that plainly and agree what happens next. Do not invent a date just to make the update look settled.

## Example: the inquiry is complete, but the scheduling issue remains open

This fictional example illustrates the method. It is not an actual employee record or Hemory output.

During a one-on-one, Priya says late review invitations make it difficult to plan her day. You say, “I'll ask the organizer about giving more notice,” and Priya thanks you. She also suggests a short written preview before reviews, without accepting responsibility for implementing it.

Before the next meeting, your sent message confirms that you asked the organizer. No response has arrived. You have no current evidence that invitations have changed.

| Point | Supported update | Useful next conversation |
|---|---|---|
| Your undertaking | You asked the organizer as promised | Explain that the response is pending |
| Review notice | Its current effect on Priya is not yet known | Ask whether it is still disrupting her work |
| Written preview | An idea, with no implementation owner agreed | Explore whether it would help and what a trial would involve |

A useful opening is:

> I asked the organizer about giving more notice and am waiting for a reply. Has the timing changed for you, or is it still making planning difficult? You also mentioned a written preview—would that help with the next review?

This gives Priya a factual update and room to correct your understanding. It does not claim the issue is fixed or ask why she has not implemented an idea she never owned.

If you propose to follow up with the organizer again, record that as a new next step once agreed. Keep it distinct from the original promise to ask, which you have already fulfilled.

## Ask a connected agent to prepare your follow-up note

When several discussions are relevant, a compatible AI agent connected to Hemory can help draft the note from available context. Supply current messages or task updates separately when it cannot access them.

```text
Prepare my manager follow-up note for the next one-on-one with Priya.
Use relevant Hemory discussions and the current updates I provide.

Identify the support I actually committed to, including timing or
conditions where established. Compare each undertaking with current
evidence of what I did. Keep my action separate from the wider outcome.

Draft a factual update and an open question about what Priya needs now.
Do not assign her an idea she did not accept, infer personal traits,
or treat a missing reply as proof that I never sent the request.
```

Review whether the draft describes your promise accurately. The benefit is less manual reconstruction before you decide what help to offer now.

## Keep a short record of the follow-through

```text
Concern or support request:
What I agreed to do:
Timing or prerequisite, if agreed:
What I have done and its current evidence:
Response or wider outcome still pending:
Update to give:
Question about the teammate's needs now:
New next step, owner, and timing once agreed:
```

Bring the update into the one-on-one without making it the whole agenda. Ask what the teammate wants to cover, and adjust if something more pressing has emerged.

Afterward, put new agreements in the work process you use. Capture the discussion with [Hemory](/features/) when you want to preserve it, so you can listen closely and still return to the conditions on the support you offered.

## FAQ

### Is my promise complete if the intended outcome has not happened?

Check what you agreed to do. Asking for a decision and obtaining it are different undertakings. Report both your completed action and the remaining outcome clearly.

### What if I have not followed through?

Acknowledge the specific step that remains, check whether it is still useful, and agree a realistic next action. Keep a proposed date separate until it is accepted.

### Should every idea from the teammate become a task?

No. Preserve it as an idea until someone accepts a next step. The guide to [decisions, commitments, and ideas](/blog/searchable-memory/decisions-commitments-and-ideas/) explains how to keep those distinctions in working notes.