Checking In One Month Later
A month later, Mia checks whether the agreement has improved coordination and asks Leo and Jack what still needs adjustment. They review a recent handoff and agree on one small refinement.
Dialogue12

Thanks for making time, both of you. It’s been a month since we agreed on clearer task ownership and documented handoffs. Before we adjust anything, how has coordination been in practice?
Better overall. I’m not having to guess as often about who’s handling what, and the updates have helped. We still had a snag on Tuesday, though, when the revised figures came through late.
That’s fair. I sent them as soon as I’d finished checking the source file. I was concerned that sharing unverified figures would create more confusion, but I can see how the delay affected your work.
Let’s look at that handoff itself. Leo, what did you need at the time? And Jack, what were you trying to protect by waiting until the figures were checked?
I needed an early signal that the numbers were still being checked. I’d built my next steps around the original timeline, so the silence made it hard to tell whether I should keep going or pause.
I was trying to avoid sending figures that might change, but I could have flagged the delay without sharing the numbers themselves. I didn’t realize you were waiting on that decision to proceed.
So the agreement is working, but there’s a gap between documenting the final handoff and communicating while work is still in progress. Does that capture it for both of you?
Yes. I don’t need provisional numbers; I just need a heads-up if the delivery time is likely to change, especially when that affects a dependent task.
That’s reasonable. I can send a brief status note as soon as I know the check is taking longer than expected, then follow up with the verified figures and the handoff record.
Let’s make that our small refinement: flag a likely delay as soon as it’s apparent, and give an estimated delivery time if you can. We’ll review how it works at our next check-in.
Agreed. That gives me enough information to reprioritize without asking Jack to compromise the accuracy of the figures.
Agreed. The handoff process is clearer now, and this should make the timing clearer, too. I’ll start with the next set of figures.
Vocabulary7
- task ownership
Responsibility for managing or completing a particular task. Here, clearer ownership helps everyone know who is handling each part of the work.
- documented handoffs
Written records of how work or information is passed from one person to another. The phrase emphasizes that the transfer is recorded, not just discussed.
- a snag
A small problem or unexpected difficulty. In this context, it refers to a delay that disrupted the work.
- flagged the delay
Communicated or pointed out that something was delayed. It can be used when someone needs to alert others to a problem early.
- provisional numbers
Numbers that are temporary and may change after further checking. Here, Leo says he does not need unverified figures.
- reprioritize
To change the order of tasks according to what is most important or urgent. Leo can do this when he knows a delivery time is likely to change.
- as soon as it’s apparent
As soon as something becomes clear or noticeable. This phrase sets an expectation for communicating a delay promptly.
Key Sentences8
- 1
Before we adjust anything, how has coordination been in practice?
A useful way to invite feedback before changing an agreement or process. You can reuse “How has [something] been in practice?” to ask how a plan is working in real situations.
- 2
I’m not having to guess as often about who’s handling what, and the updates have helped.
This sentence gives balanced feedback by describing a specific improvement. Use “I’m not having to [do something] as often” to explain how a change has helped.
- 3
I was concerned that sharing unverified figures would create more confusion, but I can see how the delay affected your work.
This acknowledges someone’s reasoning while recognizing the impact on another person. It is useful for expressing your intention without dismissing the other person’s experience.
- 4
I needed an early signal that the numbers were still being checked.
A concise way to explain what information would have helped. You can adapt “I needed an early signal that…” to describe a communication need.
- 5
I didn’t realize you were waiting on that decision to proceed.
This shows that you now understand how your decision affected someone else’s work. Use “I didn’t realize you were waiting on…” to acknowledge a missed dependency.
- 6
So the agreement is working, but there’s a gap between documenting the final handoff and communicating while work is still in progress.
This summarizes what is working and identifies a remaining issue without assigning blame. It is a useful structure for reviewing a process: “X is working, but there’s a gap between A and B.”
- 7
Let’s make that our small refinement: flag a likely delay as soon as it’s apparent, and give an estimated delivery time if you can.
This turns discussion into a clear, practical adjustment. Use “Let’s make that our…” to propose a specific next step, and “if you can” to keep the request flexible.
- 8
That gives me enough information to reprioritize without asking Jack to compromise the accuracy of the figures.
This explains how the adjustment helps while respecting another person’s responsibility. It is useful for showing that a solution meets one person’s needs without sacrificing an important standard.