notes · thoughts ·
Not knowing when it will end is harder than waiting
I began separating speed from predictability when collaboration felt frustrating. Someone waiting needs enough information to choose their next action.
When collaboration felt frustrating, I initially thought the other person was working too slowly. But even with a delay, I can do something else if I know where the work is blocked and when I can check again. What was harder was not knowing whether to keep waiting or start something else.
Distinguishing the two changed what I wanted to ask for. “Tell me enough about the current state to decide my next task” was more accurate than simply asking for it to be finished faster.
The person waiting needs choices too
An estimated completion time becomes hard to share if it is treated only as a promise that must be kept. If the duration is still unclear, it is enough to share what is uncertain and when another assessment will be possible. That information alone lets the person waiting adjust their plan.
“In progress” communicates a state, but not enough to guide the next action. What I can do differs depending on whether someone is waiting for input, has finished implementation and is checking it, or needs to rethink the approach itself.
A schedule change is also better shared when it happens than when the result is finally ready. Even without a result, the waiting person’s plan can change from that moment.
When the same friction repeats, I wonder whether asking people to be more considerate is enough. We can also change how we work by agreeing on checkpoints and sharing blockers early.
I try not to judge collaboration by speed alone. When I take on work, it matters that I do not leave others waiting without an explanation. Apart from who works faster, there is the work of making it possible to plan each other’s time.